https://ubbcluj.sharepoint.com/sites/DanCHIOREAN/Shared Documents/General/Lecture2- Requirements Elicitation.pdf?CT=1685310870451&OR=ItemsView

Software Lifecycle Activities

Requirements

• high priority
  • addressed during analysis, design, and implementation
  • must be demonstrated
• medium priority
  • addressed during analysis and design
  • usually demonstrated in the second iteration
• low priority
  • addressed only during analysis
  • illustrates how the system is going to be used in the future with not yet available technology

Functional requirements

• describe
  • the interactions between the system and its environment independent from the implementation
  • user tasks that the system needs to support
• e.g. “An operator must be able to define a new game.“

Nonfunctional requirements

• describe
  • aspects not directly related to functional behavior
  • properties of the system or the domain
• quality requirements
  • Usability
  • Reliability
  • Performance
  • Supportability
• constraints (pseudo requirements)
  • Implementation
  • Interface
  • Operations
  • Packaging
• e.g. “The response time must be less than 1 second”

Requirements elicitation

• focuses on describing the purpose of the system
• the client, the developers, and the users identify a problem area and define a system that addresses the problem ⇒ requirements specification

types