Brief shortnote on Requirement elicitation and requirement analysis

- Requirement elicitation means gathering of requirements.

- Perhaps it is most difficult, critical, most error prone and most communication intensive aspect of software development.

- The most important goal of software requirement engineering is to find out what the customer really wants.

- The users need can be identify only by understanding expectation of the user from the developers.

- Requirements are gathered by asking the question to user and writing down their answers and their exceptions of the software that how he want to use software.

- Gathering the requirements of users is the most difficult part of the software development, because both developer and user have different mindset regarding the software.

- Here, communication of both the parties are the most essential for software product.

- There are number of requirement elicitation method.

https://en.wikipedia.org/wiki/Requirements_elicitation 

- Some people think that one methodology is always possible for all the software development process but generally it is not possible. Each software product required different methodology.

- Requirement analysis is the most important and essential activity after the requirement elicitation.

- This activity review all the requirements and may provide the entire system as graphical view.

- The requirement analysis are having the following four steps as shown in following fig.

i] Draw Context Diagram

- Context diagram is the model that defines the boundaries and interfaces of the proposed system with the external world.

- It defines the entities outside of the proposed system and may enters in the proposed system.

- The context diagram of the result management system are as follows

 

 ii] Development of prototype

- One effective way to realize what the customer  want is to construct a prototype.

- Until the customer is satisfied, we can use their feedback to continuously modify the prototype.

- Hence the prototype helps to client for the visualization of the complete system and better understanding of the requirements.

- When developers and users are not certain about some of the requirements, prototype helps both the parties to make final decision.

- The prototype should be built quickly and at relative low cost, hence it is always have limitations and would not be acceptable in the final system.

iii] Model the requirements

- This process usually consists of various graphical representations of the functions, data entries, external entries and relation between them.

- The graphical view may help to find out missing and in-consistence requirement.

iv] Finalized the requirements

- After modeling the requirements, we would have better understanding of the system behavior.

- Elicitation and analysis process have provided the better understanding insight to the system, now we have to finalized them in finalization mode.

- After this, the next step is to document the requirement in prescribed format.