Softwa的re Engineering Management.pptVIP

Software Engineering Management Software Configuration Management Change and confusion Change is inevitable when software is built! Change increases the level of confusion among software engineers who are working on a project Confusion arises when changes are NOT Analyzed before they are made Recorded before they are implemented Reported to those with a need to know Controlled in a manner that will improve quality and reduce error The “First Law of System Engineering Fundamental sources of change New biz or mkt conditions that dictate changes in product requirements or biz rules New customer needs that demand modification of data produced by information systems, functionality delivered by products, or services delivered by a computer-based system Reorganization and/or business downsizing that causes changes in project priorities or SE team structure Budgetary or scheduling constraints that cause a redefinition of the system or product What Are These Changes? Managing change To improve the ease with which changes can be accommodated Reduce the amount of effort expended when changes must be made Software Configuration Management (SCM) ...... an umbrella activity that is applied throughout the software process. Because changes can occur at any time, SCM activities are developed to (1) identify change (2) control change (3) ensure that change is being properly implemented (4) report change to others who may have an interest The primary responsibility is the control of change SCM Vs. Software maintenance Maintenance is a set of SE activities that occur after software has been delivered to the customer and put into operation SCM is a set of tracking and control activities that begin when a software project begins and terminate only when the software is taken out of operation What is Software Configuration? Items (such as programs, documents and data) that comprise of all information produced as part of the S/W process are collectively called a Software Configurat