Download - Requirements Change Management
![Page 1: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/1.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Requirements Change Management
30.10.2001
Tapani AaltioMarjo Kauppinen
Qure ProjectSoftware Business and Engineering Institute (SoberIT)
Helsinki University of Technology (HUT)
![Page 2: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/2.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Agenda
• Introduction
• Requirements Change Management Process
• Traceability
• Summary
![Page 3: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/3.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Introduction (1/3)
requirements definition
specification & design & coding &
testing
acceptance testing
requirements management
Requirements management is the process of managing changes to a system’s requirements [Kot98], and it is an important part of requirements engineering.
![Page 4: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/4.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Introduction (2/3)
• It is often the case that more than 50% of a system’s requirements
will be modified before it is put into service [Kot98].
• New requirements emerge and existing change due to
• errors
• increased understanding
• change in external circumstances.
![Page 5: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/5.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Introduction (3/3)
Changes to the requirements should be
documented and controlled formally.
Change management process ensures that
• changes are made systematically
•similar information is collected for each proposed change
•overall analysis is made about the costs, benefits and
timing
• the requirements document is updated.
![Page 6: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/6.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Requirements Change Management Process (1/5)
requirements change management
process
• updated user requirements document
• change history
recording analysing deciding implementing
• approved user requirements document
• change proposal
![Page 7: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/7.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Requirements Change Management Process (2/5)
Recording a change proposal:
• Stakeholders submit proposals for requirements changes using a
pre-defined form.
![Page 8: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/8.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Requirements Change Management Process (3/5)
Analysing a change request:
• The proposed change is analysed to see
• if it is valid. Sometimes stakeholders misunderstand the
requirements and suggest unnecessary changes.
• how many requirements and system components are affected
• how much it would cost, in both time and money, to make the
change
• what the benefits of the change are.
![Page 9: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/9.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Requirements Change Management Process (4/5)
Deciding on a change request:
• Change requests are considered formally by a group or a person
who decide whether or not the change should be accepted.
![Page 10: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/10.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Requirements Change Management Process (5/5)
Implementing a change:
• Updating the requirements document.
• Informing all the necessary people.
![Page 11: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/11.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Traceability
• Requirements cannot be managed effectively without
requirements traceability [Kot98].
• Traceability types [Som97]
• requirements - sources
• requirements - rationale
• requirements - requirements
• requirements - architecture
• requirements - test cases
![Page 12: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/12.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Summary (1/2)
User requirements
definitionUser requirements management
Design, coding and system testing
Acceptance testing
Requirements Engineering
Useful and Successful Products
![Page 13: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/13.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
Summary (2/2)
Systematic requirements change management ensures that
product development produces useful and succesful
systems.
![Page 14: Requirements Change Management](https://reader036.vdocument.in/reader036/viewer/2022082611/56812ed0550346895d9471a0/html5/thumbnails/14.jpg)
SoberITSoftware Business and Engineering Institute
HELSINKI UNIVERSITY OF TECHNOLOGY
References
• [Kot98] G. Kotonya and I. Sommerville, Requirements Engineering -
Processes and Techniques, John Wiley & Sons, New York, 1998.
• [Som97] I. Sommerville and P. Sawyer, Requirements Engineering - A
Good Practice Guide, John Wiley & Sons, New York, 1997.