Sub Component of Requirement Development <div class="text_exposed_root text_exposed">
Elicitation:
involves the actions we go through to understand users and discover their needs.</div><div class="text_exposed_root text_exposed"> </div><div class="text_exposed_root text_exposed">Good Practices :-
1.Define requirements development process
2.Define vision and scope
3.Identify user classes
4.Select product champions
5.Establish focus groups
6.Identify use cases
7.Identify system events and responses
8.Hold facilitated elicitation workshops
9.Observe users performing their jobs
10.Examine problem reports
11.Reuse requirements
  
Analysis:
involves creating multiple views of the requirements, such as prototypes, graphical analysis models, and tests. Other aspects of requirements analysis include negotiating priorities, searcing for missing requirements, evaluating technical feasibility and risk. </div><div class="text_exposed_root text_exposed">
Good Practices :-
1.Draw context diagram
2.Create prototypes
3.Analyze feasibility</div><div class="text_exposed_root text_exposed"><div class="text_exposed_root text_exposed" id="id_50257e3fe40211108921542"><div class="text_exposed_show">4.Prioritize requirements
5.Model the requirements
6.Create a data dictionary
7.Allocate requirements to subsystems
8.Apply Quality Function Deployment</div></div></div><div class="text_exposed_root text_exposed"><div class="text_exposed_root text_exposed">
Specification:
involves recording the various types of requirements information in forms that will facilitate communication among the project stakeholders. </div><div class="text_exposed_root text_exposed"> </div><div class="text_exposed_root text_exposed">Good Practices :-
1.Adopt SRS template
2.Identify sources of requirements
3.Uniquely label each requirement
4.Record business rules
5.Specify quality attributes</div><div class="text_exposed_root text_exposed">Validation:
ensures that requirements are correct, will satisfy customer needs, and have all the characteristics of high-quality requirements.
</div><div class="text_exposed_root text_exposed">Good Practices :-</div></div><div class="text_exposed_show">Validation might lead the analyst to rewrite some requirements specifications, to reassess the initial analysis, or to correct and refine the set of documented requirements.</div><div class="text_exposed_show"> </div>