Requirements Engineering

Stage in which the technical software development staff will work on technical development staff will work on:

With Stakeholders:

1) Customers and end users of the system,
2) Engineers who develop or maintain other systems
other systems,
3) Business administrators,
4) System domain experts,
5) Employee representatives, etc.

To:

1) Establish requirements

Activities:

1) Understanding the application domain.
2) Collection of requirements.
3) Ranking.
4) Conflict resolution.
5) Prioritization.
6) Verification of requirements.

Validation is the review that the requirements
requirements are what the user wants.

Validation is important because an error in a
error in a requirement is very costly because it
because it implies changes in all the other
stages.

The user must visualize the system in
and imagine how it fits into his or her
it fits into their work.

Objectives:

Establish and maintain a document with the agreements between the customer and the development team about the customer's needs of the customer and what the system will do

Are the basis for:

estimating cost and time
planning activities

perform activities

track requirements

manage requirements

satisfy needs and requests

Requirements evolve because of:

1) Changes in a system's environment
2) The customer's better understanding of their
real needs

1) Validity verification
2) Consistency check
3) Integrity Verification
4) Realism check
5) Verifiability