Requirement Engineering steps - Capturing the Requirement

Q.  Which is not a step of Requirement Engineering?
- Published on 24 Jul 15

a. Requirements elicitation
b. Requirements analysis
c. Requirements design
d. Requirements documentation

ANSWER: Requirements design


  • Nirja Shah   -Posted on 29 Oct 15
    - The activities involved in requirements engineering vary widely. They depend on the type of system being developed and the specific practices of the organization(s) involved. These may include:

    1. Requirements inception or requirements elicitation -
    2. Requirements identification - identifying new requirements
    3. Requirements analysis and negotiation - checking requirements and resolving stakeholder conflicts
    4. Requirements specification (software requirements specification; SRS) - documenting the requirements in a requirements document
    5. System modeling - deriving models of the system, often using a notation such as the Unified Modeling Language (UML)
    6. Requirements validation - checking that the documented requirements and models are consistent and meet stakeholder needs
    7. Requirements management - managing changes to the requirements as the system is developed and put into use

Post your comment / Share knowledge

Enter the code shown above:
(Note: If you cannot read the numbers in the above image, reload the page to generate a new one.)