1. Chapter 7 Review Requirements Engineering Processes
5 May 2008
Stephanie

2. Overview: Understand principle requirements and their relationships
Several techniques of requirements elicitation and analysis
Importance of requirements validation & requirements reviews
Requirements management is necessary
So: Our Projects.

3. 7.1: Feasibility Studies A short, focused study that aims to answer:
Does the system contribute to the overall objectives of the organization?
Can the system be implemented using current technology within $$ and time constraints?
Can the system be integrated with existing systems?

4. 7.1 … Information Assessment
How would the organization cope if this system were not implemented?
What are the problems with current processes and how would a new system help?
What direct contribution will the system make to business objectives and req’s?
Can information be transferred to and from other organizational systems?
Does the system require tech. that’s not been previously used in the org?
What must be supported by the system and what doesn’t?

5. 7.2: Requirements Elicitation and Analysis
Stakeholder: person or group who will be affected by the system (in/directly)
Can be difficult to have them identify requirements
Process:
Req’s discovery
Viewpoints (interactor, indirect, domain)
Interviewing
Scenarios
Use Cases
classification & organziation
prioritization and negotiation
documentation
Ethnography
An observational technique that can be used to understand social and organizational requirements
How people work together  more requirements

6. 7.3 Requirements Validation
Showing that the requirements actually define the system that the customer wants
Overlaps analysis (or finding problems)
Checks Include
Validity, Consistency, Completeness, Realism & Verifiability
Techniques
Requirements Reviews
Verifiability
Comprehensibility
Traceability
Adaptability
Prototyping
Test-Case Generation

7. 7.4: Requirements Management
The process of understanding and controlling changes to system requirements
Req’s often change after the system is delivered
A formal process & started with first draft of req’s doc
Enduring Req’s
Relatively stable & derived from core organization activity directly related to the system
Volatile Req’s
Change during system development or change after deployment

8. 7.4 … Requirements Management Planning
R.M. Planning
Identification
Change Management
(1) Problem Analysis & change specification; (2) Change analysis & costing; (3) Change Implementation
Traceability policies
(1) Source; (2) Requirements; (3) Design
CASE tool support
(1) Req’s Storage; (2) Change management; (3) Traceability management