Baseline – IEEE definition

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Formal Technical Reviews
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Software Configuration Management Speaker: Jerry Gao Ph.D. San Jose State University URL:
CSC 395 – Software Engineering Lecture 25: SCM –or– Expecting Change From Everything But Vending Machines.
Software Configuration Management (SCM)
TCS2411 Software Engineering1 Software Configuration Management “The only constant is change...”
Configuration Management
Chapter 27 Change Management
Software Configuration Management
Software Configuration Management (SCM)
CSSE 375 Software Construction and Evolution: Configuration Management
Configuration Management Avoiding Costly Confusion mostly stolen from Chapter 27 of Pressman.
Software Configuration Management (SCM)
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
Software Configuration Management
Software Configuration Management (SCM)
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
Software Quality Assurance
SOFTWARE CONFIGURATION MANAGEMENT. Change is inevitable when computer software is built. And change increases the level of confusion among software engineers.
Software Project Management
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Software Configuration Management (SCM). Product Developer Disciplines One view of the world is that there are three types of activities are required.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 29 Slide 1 Configuration management.
Management of Software Project CSM Software Configuration Management (SCM)
Configuration Management at CMM Level 2 Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi,
Software Configuration Management n Art of coordinating SW development to minimize confusion n Software quality assurance (umbrella) activity n Set of.
Objectives Understand Corrective, Perfective and Preventive maintenance Discuss the general concepts of software configuration management.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Configuration Management
Configuration Management (II) Copyright, 2000 © Jerzy R. Nawrocki Requirements.
Software Engineering Lecture 9: Configuration Management.
Requirements Management and Changes Copyright, 2003 © Jerzy R. Nawrocki Requirements.
Configuration & Build Management. Why Software Configuration Management ? The problem: Multiple people have to work on software that is changing More.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 27 Change Management Software Engineering: A Practitioner’s Approach, 6/e Chapter 27 Change.
Software Configuration Management (SCM)
Software Configuration Management -Subversion- RTLAB YuJin Park.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Configuration Management (SCM)
Configuration Management
Software Configuration Management
Software Configuration Management
Software Project Configuration Management
Software Configuration Management
Chapter 11: Software Configuration Management
Software Configuration Management
Software Engineering (CSI 321)
Software Engineering Lecture #41
Version Control Combination of procedures and tools to manage different versions of the software configuration. Configuration management allows the user.
Configuration Management
Software Configuration Management
Change Control Process—I
Chapter 27 Change Management
Chapter 29 Software Configuration Management
Lecture 3 Change Management
Chapter 29 Software Configuration Management
Configuration Management (managing change)
Software Configuration Management
Chapter 27 Change Management
Chapter 27 Change Management
Chapter 11: Software Configuration Management
Chapter 27 Change Management
Chapter # 6 Software Configuration Management
Chapter 27 Change Management
Software Engineering: A Practitioner’s Approach, 6/e Chapter 27 Change Management copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Software Engineering Lecture #28
Software Configuration Management
Presentation transcript:

Baseline – IEEE definition A specification or a 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.

Software Configuration Item (SCI) Information that is created as part of the software engineering process Typical SCIs Requirement Specs Design Specs Source code Test cases and recorded results User guides and Installation Manuals Executable programs Standards and procedures (C++ design guidelines)

Software Configuration Management Tasks Identification Version Control Change Control Configuration Auditing Reporting Identification: how does an organization identify and manage the many existing versions of a program in a manner that will enable changes to be accommodated efficiently? Version Control: how does an organization control changes before and after software is released to a customer? Change Control: who has responsibility for approving and ranking changes? Configuration auditing: how can we ensure that the changes have been made properly? Reporting: what mechanism is used to appraise others of changes that are made?

Identification How does an organization identify and manage the many existing versions of a program in a manner that will enable changes to be accommodated efficiently?

Version Control How does an organization control changes before and after software is released to a customer?

Change Control Who has the responsibility for approving and ranking changes?

Configuration Auditing How can we ensure that the changes have been made properly?

Reporting What mechanism is used to appraise others of changes that are made?

Configuration Identification Identify baseline Identify configurable software items At the minimum, all deliverables must be identified as configurable items- design, software, test cases, tutorials, user guides…

Version Evolution 1.3.1 1.3.2 Baseline Version Major change Major change 1.3 1.5 1.0 1.1 1.2 Minor change 1.4 1.6 Minor change 1.1.1 1.1.2

Version Control How does an organization control changes before and after software is released to a customer? What are the different components in this particular version?

Software Engineering II Lecture 33 Fakhar Lodhi

Recap