2003 Engineering Process Department SCM Team Managing Changes

2003 Engineering Process Department - SCM Team Managing Changes in the Real World Terrence Chou Global Director May 27, 2003

Outline • • Why Managing Changes? What’s the Changes? When to Manage Changes? Where to Manage Changes? How to Manage Changes? What Software Configuration Management Do? Q&A Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 2

Why Managing Changes? • Changes is inevitable when computer software is built • Changes increases the level of confusion among project’s software engineers • Lower the risk of project failure due to changes Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 3

What’s the Changes? • • • Market Requirement Document Product Requirement Document System Requirement Specification Design Specification Source Files (source code, bitmap, and etc) Test Specification (Test Plan/Test Case/Test Procedure) Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 4

What’s the Changes? • Four fundamental sources of change: – New business or market conditions dictate changes in product requirements or business rules – New customer needs demand modification of data produced by information system, functionality delivered by products, or services delivered by a computer-based system – Reorganization or business growth/downsizing causes changes in project priorities or software engineering team structure – Budgetary or scheduling constraints cause a redefinition of the system or product Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 5

When to Manage Changes? • Whenever there is a change request (CR), the changing then need to be managed • The request for change can occur at any time during the software process • Baselined Configuration Items (CIs) should always being manageable Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 6

Where to Manage Changes? • A project database is used to keep the changes – – – PVCS by Intersolv, 1993 Make by Bell LAB, 1975 SCCS by Rochkind, 1975 RCS by Richy, 1985 Cedar by Xerox PARC, 1970 Visual Source. Safe by Microsoft, 1997 Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 7

How to Manage Changes? Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 8

How to Manage Changes? Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 9

What Software Configuration Management Do? • Software Configuration Management (SCM) is an umbrella activity that is applied throughout the software process, the whole software life cycle. Because change can occur at any time, SCM activities are developed to help – – Identify change Control change Ensure that change is being properly implemented Report changes to others who may have an interest • Software support Software configuration mgmt. Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 10

Q&A Trend Micro CONFIDENTIAL - ENGINEERING DOCUMENT 11