Requirements Change Management

Slides:



Advertisements
Similar presentations
Software change management
Advertisements

Chapter 2 – Software Processes
Software Requirements
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
SWE Introduction to Software Engineering
SE 555 Software Requirements & Specification Requirements Management.
A Student Guide to Object- Orientated Development Chapter 2 Requirements for the Wheels case study system.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Requirements Engineering Process – 1
Information Technology Project Management
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes 1.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY Requirements Traceability Virve Leino QURE Project Software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
This chapter is extracted from Sommerville’s slides. Text book chapter
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management 1.
SoberIT Software Business and Engineering Institute HELSINKI UNIVERSITY OF TECHNOLOGY The current state of stakeholder-driven requirements engineering.
Lecture # 22 Software Evolution
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Chapter 6 Requirements Engineering Process.
Copyright © Jerzy R. Nawrocki Requirements Review Requirements Engineering & Project.
Software System Engineering: A tutorial
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Quality Model for Requirements Eng. Copyright, 2002 © Jerzy R. Nawrocki Quality.
Chapter 5 Defining and Managing Project and Product Scope Copyright 2012 John Wiley & Sons, Inc. 5-1.
Standard SRS Copyright, 2001 © Jerzy R. Nawrocki Requirements Engineering Lecture.
Requirements Elicitation. Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical.
CPSC 873 John D. McGregor Session 4 Requirements V & V - continued.
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Requirements Verification & Validation Requirements Engineering & Project Management.
Creator: ACSession No: 16 Slide No: 1Reviewer: SS CSE300Advanced Software EngineeringFebruary 2006 (Software Quality) Configuration Management CSE300 Advanced.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Good Practices of Requirements Eng. Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Intent Specification Intent Specification is used in SpecTRM
Chapter 101 The Design Process Chapter 10 Achieving Quality Through Continual Improvement Claude W. Burrill / Johannes Ledolter Published by John Wiley.
Lecture 7: Requirements Engineering
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Requirements Traceability Matrix
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Software Engineering, 8th edition. Chapter 7 1 Courtesy: ©Ian Sommerville 2006 March 20 th, 2008 Lecture # 12 Requirements Engineering Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Chapter 4 Requirements Engineering (3/3) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Requirements Validation
Requirements Engineering. Requirements engineering processes The processes used for RE vary widely depending on the application domain, the people involved.
Quality Model for RE Process Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
Requirements Engineering Requirements Management Lecture-25.
1 Software Requirements Engineering (CS 708) Dr. Ghulam Ahmad Farrukh.
1 Requirements Elicitation – 2 Lecture # Requirements Engineering Process Requirements Elicitation Requirements Analysis and Negotiation Requirements.
1 Requirements Analysis Lecture # Recap of Requirements Elicitation - 1 Requirements elicitation deals with discovering requirements for a software.
 The processes used for RE vary widely depending on the application domain, the people involved and the organisation developing the requirements.  However,
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
Software Development Module Code: CST 240 Chapter 6: Software Maintenance Al Khawarizmi International College, AL AIN, U.A.E Lecturer: Karamath Ateeq.
1 Requirements Management - II Lecture # Recap of Last Lecture We talked about requirements management and why is it necessary to manage requirements.
REQUIREMENTS ENGINEERING PROCESSES Chapter 6. Activities in Requirements Engineering processes  Requirements elicitation;  Requirements analysis; 
Fundamentals of Information Systems, Sixth Edition
Requirements Engineering (continued)
Requirements Traceability
Requirements Traceability
Software Configuration Management
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Introducing Requirements Change Management Process into ISO/IEC 12207
Extreme Programming.
Requirements Management - I
Requirements Traceability
Requirements Document
Presentation transcript:

Requirements Change Management 30.10.2001 Tapani Aaltio Marjo Kauppinen Qure Project Software Business and Engineering Institute (SoberIT) Helsinki University of Technology (HUT)

Agenda Introduction Requirements Change Management Process Traceability Summary

Introduction (1/3) specification & design & coding & testing acceptance testing requirements definition 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.

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.

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.

Requirements Change Management Process (1/5) approved user requirements document change proposal updated user requirements document change history requirements change management process recording analysing deciding implementing

Requirements Change Management Process (2/5) Recording a change proposal: Stakeholders submit proposals for requirements changes using a pre-defined form.

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.

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.

Requirements Change Management Process (5/5) Implementing a change: Updating the requirements document. Informing all the necessary people.

Traceability Requirements cannot be managed effectively without requirements traceability [Kot98]. Traceability types [Som97] requirements - sources requirements - rationale requirements - requirements requirements - architecture requirements - test cases

Useful and Successful Products Summary (1/2) Requirements Engineering Design, coding and system testing Acceptance testing User requirements definition User requirements management Useful and Successful Products

Summary (2/2) Systematic requirements change management ensures that product development produces useful and succesful systems.

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.