Requirements Engineering

Info

• Analyze problems with an existing system (system-as-is)
• Identify objectives & opportunities for new system (system-to-be)
• Define functionalities of, constraints on, responsibilities in system-to-be,
• Specify all of these in a requirements document

Composed of:

• Inception
  • Start the process
• Development
  • Elicitation
    • Discover requirements
  • Analysis
    • Resolve conflicts through negotiation
  • Specification
    • Produce precise requirements document
  • Validation
    • Checked for consistency and completeness
• Management
  • Needs to evolve as contexts do

This is an iterative process where you cycle through these stages eliciting new requirements or changing requirements.

RE is hard because

• Broad scope
• Multiple concerns
• Multiple abstraction levels
• Multiple stakeholders
• Additional activities during process

RE is important because

• Legal impact
• Social impact
• Technical impact
• Impact on certification
• Impact on economy, security, safety

Related Topics

• Requirements Engineering Reference Model