DataTerminology.comNEW
Eliciting, documenting, validating, and managing system requirements to align stakeholders and guide design throughout the development lifecycle.
DESCRIPTION
Requirements engineering structures how systems capture stakeholder needs and translate them into actionable specifications. It includes elicitation, analysis, prioritization, documentation, validation, and traceability. Practitioners balance functional and non-functional requirements, manage changes, and mitigate ambiguity with models and prototypes. Techniques range from interviews and workshops to formal modeling and scenarios. Effective requirements engineering reduces rework, ensures compliance, and supports agile delivery through user stories and acceptance criteria.
ALTERNATIVE DEFINITIONS
Wikipedia
Requirements engineering is the process of defining, documenting, and maintaining requirements in the engineering design process.
Highlights lifecycle focus on definition, documentation, and maintenance.
SEBoK (Systems Engineering Body of Knowledge)
Requirements engineering encompasses the activities for eliciting, analyzing, specifying, verifying, and managing requirements.
Enumerates core activities with emphasis on verification and management.
IEEE
This standard describes the processes and products involved in the engineering of requirements for systems and software products.
Defines formal process and artifacts per IEEE 29148.
RELATED TERMS
Requirements Elicitation Requirements Specification Requirements Validation Requirements Traceability Stakeholder Analysis User Story Acceptance Criteria Non-Functional Requirements Change Control Systems Engineering
COMPETING TERMS
Business Analysis Prototyping
KNOWLEDGE AREAS
Software Engineering Collaboration Data Management Data Architecture
TARGET AUDIENCE
Business Analyst Product Owner Software Architect IT Project Manager Scrum Master Data Architect
EXTERNAL SOURCES
- Wikipedia - Requirements engineering
- SEBoK - Comprehensive systems engineering overview
- ISO - Requirements engineering standard reference
- INCOSE - Systems Engineering Handbook guidance
TOP QUESTIONS
What is the purpose of Requirements Engineering?
It aligns stakeholder needs with implementable specifications, reducing ambiguity and rework. It guides design, testing, and acceptance throughout the project.
Category: Definition
How does Requirements Engineering fit in Agile?
Agile uses lightweight artifacts like user stories, acceptance criteria, and backlog refinement, with continual elicitation and validation across sprints.
Category: Opinion
What is traceability in Requirements Engineering?
Traceability links requirements to design, test cases, and changes, supporting impact analysis and compliance audits.
Category: Definition
What are common mistakes in Requirements Engineering?
Ambiguous language, missing non-functional requirements, inadequate stakeholder engagement, and poor change control cause scope creep and defects.
Category: Mistakes
How are requirements validated?
Through reviews, prototypes, acceptance tests, and stakeholder sign-off, ensuring they reflect real needs and constraints.
Category: Requirements
What is currently a hot topic in Requirements Engineering?
Model-based requirements and AI-assisted elicitation are emerging, with NLP used to detect ambiguity and conflicts.
Category: Topic
How do non-functional requirements impact architecture?
Performance, security, and reliability drive technology choices, patterns, and capacity planning; they often dominate architectural trade-offs.
Category: Opinion
What is the risk of poor Requirements Engineering?
Misaligned systems, costly rework, and compliance failures can result, threatening timelines and stakeholder trust.
Category: Risks
When should Requirements Engineering start and end?
It starts at project inception and continues throughout development via change management and validation.
Category: Management