Textual Analysis

The textual analysis is based upon the fact that the user requirement are complete;  whereas most of the time what happens is that user or the customer is unable to fully define his requirements and misses out most of the details; in such circumstances if we adopt textual analysis technique we might miss out some very important system details....how do we rectify this problem?

Yes, most of the times, the user or customer is unable to define the complete requirements of the system and this issue may prove to be very costly and catastrophic if not dealt properly. One of the most difficult tasks during requirement engineering phase is to determine as if the requirements are complete or there is something missing. We cannot proceed towards the design or development of a system unless we have the complete and fully defined requirements in our hand therefore we need to make sure that we capture each and every requirement of the user before proceeding towards any further activity. In requirements engineering, requirements elicitation is the practice of obtaining the requirements of a system from users, customers and other stakeholders. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user and customer by just asking them what the system should do. This technique tries to give the answer of the question "What is missing?" so that it helps us to identify the missing requirements.