Software Engineering I: Requirements

A collection of flashcards summarizing the key concepts and terminology surrounding requirements engineering in software development.

Requirements Engineering

The process of establishing the services that a customer requires from a system and the constraints under which it operates and is developed.

User Requirements

Statements in natural language plus diagrams of the services the system provides and its operational constraints, written for customers.

System Requirements

A structured document that sets out detailed descriptions of the system’s functions, services, and operational constraints, defining what should be implemented.

Functional Requirements

Statements of services the system should provide, how it should react to particular inputs, and how it should behave in various situations.

Non-functional Requirements

Constraints on the services or functions offered by the system, such as timing constraints and standards, often applying to the system as a whole.

Requirements Validation

The process of demonstrating that the requirements define the system that the customer really wants.

Stakeholders

Any person or organization affected by the system, with a legitimate interest in its outcome.

Agile Methods

Software development methods that favor iterative development and may express requirements as user stories, arguing that detailed requirements are often outdated.

Requirements Elicitation

The process of gathering information about required and existing systems, working with stakeholders to understand their needs.

Requirements Completeness

The principle that requirements should include descriptions of all facilities required without any conflicts or contradictions.