Unit 3 Requirement Engineering
Unit 3 Requirement Engineering
(303105253)
Requirements Engineering
1. Requirements Elicitation
Goal: Gather and collect requirements from stakeholders.
Activities: Conduct interviews, workshops, surveys, and
observations to understand stakeholders' needs and expectations.
Outputs: Requirements elicitation document, stakeholder
requirements, user stories, use cases, etc.
Image source : Google
Cont…
2. Requirements Analysis
Goal: Analyze and refine gathered requirements for clarity,
completeness, consistency, and feasibility.
3. Requirements Specification
4. Requirements Validation
Goal: Ensure that the specified requirements are correct,
consistent, complete, and feasible.
Activities: Validate requirements through reviews,
walkthroughs, prototyping, simulations, and demonstrations.
5. Requirements Management
Goal: Manage changes to requirements throughout the software
development lifecycle.
Activities: Establish baselines for requirements, manage version
control, track changes, and ensure traceability between
requirements and other project artifacts.
Outputs: Baseline requirements document, traceability
matrix, change requests and impact analysis.
6. Requirements Communication
Goal: Ensure that requirements are clearly communicated to all
stakeholders.
Activities: Present requirements in formats understandable to
different stakeholders (e.g., technical specifications for
developers, user stories for users), conduct meetings and status
updates.
Outputs: Updated project documentation, meeting minutes,
communication plans.
7. Requirements Traceability
8. Requirements Evolution
https://www.slideshare.net/slideshow/uc-
workshop-v2/41862983
Requirements validation
What is Requirements Validation?
The process of checking that the requirements accurately reflect
the needs of the stakeholders.