Elicitation
->Proactively working with stakeholders to discover their needs, identify and negotiate potential conflicts, and establish a clear scope and boundaries for the project.
->Understanding the Problem and Its Domain
->Customer meetings is the most commonly used technique.
->Use context free questions to find out
->Interview cross section of users when many users are anticipated.
->Elicitation techniques
->A deeper understanding of the product and its interactions, identify requirements, define high-level architectural design, allocating requirements to architectural components, and identify additional conflicts that merge through considering architectural implementations and negotiating agreements between stakeholders.
->Information domain of problem must be presented & understood.
->Models depicting system information, functions, and behavior should be developed.
->Models and problems must be partitioned in a manner that uncovers detail in layers.
->Analysis proceeds from essential information toward implementation detail
->Must be traceable.
Specification
->Documents that capture the system and software req. in order to support their systematic review, evaluation, and approval. Document that describes the system to be developed in a format that can be reviewed, evaluated and approved in a systematic way.
->Separate functionality from implementation.
->A process-oriented specification language is needed.
->Specification must encompass the system containing the software component.
->Specification must encompass the environment.
->System specification is cognitive model.
->Specification must be operational.
->Must be tolerant of incompleteness and easy to add to.
->Specification must be localized and loosely coupled.
->Qualities of an Individual Requirement
->Qualities of the Set of Requirements
Validation
->Goes through the other four activities. Ensure the system meets stakeholders requirements through activities such as formal and informal reviews
->Types of validation
Management
->Starts from the moment the first requirements is elicited and ends only when the system is finally decommissioned. Requirement management includes software configuration management, traceability, impact analysis, and version control
->Requirements traceability
Ability to describe and follow the life of a requirement, in both a forward and backward direction.
->Change Requests
->Managed systematically
->Requirements attributes