Requirements Engineering
Lecture 10
Requirements Management and
Changes
[email protected]
www.cs.put.poznan.pl/jnawrocki/require/
Copyright, 2003 © Jerzy R. Nawrocki
Introduction
Soft. Configuration Item (SCI)
if (a > b) SCI = “Information that is created as part of
the software engineering process.”
a-= b;
[R.Pressman]
Types of SCIs:
• computer programs (source code or
exec)
• documents (also requirem. specification)
18 27
• data (e.g. test cases)

J. Nawrocki, Requirements Management ..
Introduction
Baseline [IEEE 610-1990]
Specification
Design
Code
Test cases
A specification or product that
has been formally reviewed and
agreed upon,
that thereafter serves as the
basis for further development,
and
that can be changed only
through formal change control
procedures.
J. Nawrocki, Requirements Management ..
Introduction
Baseline or SCI?
FTR
Engineering
SCI
SCI
Change it!
Baseline
Change control
Baseline
J. Nawrocki, Requirements Management ..
Baseline library
SCCB
Soft. Configuration Control Board
SCCB
Authorises:
• the establishment of software baselines,
• the identification of configuration items,
• the creation of products from the baseline
library.
Represents the interests of the project
manager and all groups affected by
changes to baselines.
Reviews and authorises changes.
J. Nawrocki, Requirements Management ..
CMM & Change Management
Remove
2nd floor!
Ac5. Change requests & problem
reports for all SCIs are
• initiated,
• recorded,
• reviewed,
• approved, and
• tracked
according to a documented procedure.
J. Nawrocki, Requirements Management ..
CMM & Change Management
Change control
Change
request
Err
User
Change
request
S.C. Manager
Developer
Change
report
Decision
J. Nawrocki, Requirements Management ..
SCCB
CMM & Change Management
Change control
Change
request
Err
User
Change
request
S.C. Manager
Developer
Change
report
Decision
Change
order
P. Manager
J. Nawrocki, Requirements Management ..
SCCB
CMM & Change Management
Change request
Change request number: ............................
Sender: .........................................................
Sender’s e-mail: ...........................................
Date: ..............................................................
Urgency: ................. Importance: ..............
Description: .................................................
.......................................................................
.......................................................................
Evaluator: .....................................................
Evaluate by: ........... Type (in/external) .......
J. Nawrocki, Requirements Management ..
CMM & Change Management
Change report
Change request number: ..........................
Evaluator: ...................................................
Evaluator’s e-mail: .....................................
Date: ............................................................
Urgency: ................ Importance: ..............
Is the change justifiable? ..........................
Main risk factors: .......................................
Possible implementor: ..............................
Change implement. effort (expect): .........
Change evaluation effort (actual): ............
J. Nawrocki, Requirements Management ..
Overview of RE guidelines
Basic Interm Adv
36
21
9
The requirements document
8
-
-
Requirements elicitation
Describing requirements
6
5
4
6
2
1
1
1
-
System modelling
3
3
-
Requirements validation
4
3
1
Requirements management
4
3
2
RE for critical systems
2
3
4
Reqs analysis & negotiation
J. Nawrocki, Requirements Management ..
Basic guidelines
Requirements management
• Uniquely identify each
requirement
J. Nawrocki, Requirements Management ..
Basic guidelines
Requirements management
• Uniquely identify each
requirement
Tag
J. Nawrocki, Requirements Management ..
Basic guidelines
Requirements management
Requirements
Management Policy
• Uniquely identify each
requirement
Goal: Understand the
requirements
• Define policies for requirements
management
Obligatory practices:
1. Define specialised
terms using the
template available at
www.cs.put.poznan...
J. Nawrocki, Requirements Management ..
Basic guidelines
Requirements management
• Uniquely identify each
requirement
• Define policies for requirements
management
• Define traceability policies
J. Nawrocki, Requirements Management ..
Basic guidelines
Traceability policy
Problems
Visions
Requirements
(FURPS)
User
documentation
• Traceability information
• Who is responsible
Acceptance
test cases
Design
Code
J. Nawrocki, Requirements Management ..
Basic guidelines
Requirements management
• Uniquely identify each
requirement
• Define policies for requirements
management
• Define traceability policies
• Maintain a traceability manual
J. Nawrocki, Requirements Management ..
Intermediate guidelines
Requirements management
• Use a database to manage
requirements
• Define change management
policies
• Identify global system
requirements
J. Nawrocki, Requirements Management ..
Advanced guidelines
Requirements management
• Identify volatile requirements
• Record rejected requirements
J. Nawrocki, Requirements Management ..
Summary
CMM approach to changes
Requirements management
practices
J. Nawrocki, Requirements Management ..
Quality assessment
1. What is your general
impression? (1 - 6)
2. Was it too slow or too fast?
3. What important did you learn
during the lecture?
4. What to improve and how?
J. Nawrocki, Requirements Management ..