Requirements

Engineering

222-Requirements-Elicitation-Questioning

The requirements document produced during this stage is ultimately part of what will determine the success and quality of a project. The end product will eventually be tested against meeting all requirements. 

Requirements Engineering Activities

 
elicitation.jpg

1

Elicitation

Communicating with customers and users to determine what their requirements are is important. Including all stakeholders early and often helps you determine your real needs vs your wants.

 

2

Analysis

Once the requirements have been gathered, they are analyzed to determine whether the stated requirements are unclear, incomplete, ambiguous, or contradictory, and then resolving these issues

A well written analysis will allow resources to be used efficiently, and allow the project to be able to accommodate general changes in requirements that are within the scope of the project without significantly affecting the time or cost.

requirements analysis.png
Screen Shot 2018-09-09 at 11.23.00 AM.pn
Modeling 

3

Requirements might be documented in various forms, such as natural-language documents, use cases, user stories, or process specifications.

This provides a better understanding of how different requirements relate to each other and simplifies and guides the development work to come.

4

Review

A review of the analysis and model is done with all stakeholders, to ensure everyone is on the same page moving forward, and an approval process is determined for future changes. 

Throughout the lifecycle of the project, the requirements are continually reviewed to ensure the project is conforming to them , and updates or changes go through the approval process to facilitate the smooth operation of the project.

Elicitation-and-Collaboration.png