CS 5521 Configuration Management the problem Not a simple task! –Different versions of software usually is in the field during the life cycle –Different parts of the team are on different versions of the software and documents –The same release of a software product may have multiple versions consisting of different combinations of software components Configuration management is both a development and production issue

CS 5522 Workflow of CR (MR) Investigate CR Prepare & sched work package Implement changeUpdated Artifacts Prioritized work package Change Effort Approved Change Request rejected Notify CR owner Request info from CR owner Deferred Change Approved

CS 5523 Baseline A stable, controlled and agreed to configuration for software artifacts: a. modules b. documents c. build files d. tests Identifies one version of every element in the artifact.

CS 5524 Good Practices Store Artifacts in a secure repository Control and audit changes. Organize artifacts into versioned releases. Make sure software builds are reproducible. Integrate early and often. Assign software manufactures, not developers, to Software Configuration Management.

CS 5525 The Baseline IEEE - “reviewed and agreed upon basis for further development which can be changed only through formal control procedures” Contained in the baseline are configuration items: source, objects, requirements Configuration management maintains integrity of these artifacts Major error- retrace steps through code, design documents and requirements specification - TRACEABILITY

CS 5526 Configuration Management Tools Manage the workflow of CRs If item is to be changed, developer checks it out and item is locked to other users When item check back in revision history is stored All versions are recoverable Should be able to accommodate branching Configuration management tools are very sophisticated, keeps only the changes, the deltas and the remarks, timestamps and who did what. Release configuration is a baseline plus a set of changes.

CS 5527 Configuration Management Plan Main parts: Management: Activities: –Who is on Configuration Control Board? –What are their responsibilities? –What reports are required? –What data is collected? –What data is archived?

CS 5528 Modern Change Control

CS 5529 Versioning

CS Boehm’s Criteria Completeness- all components present and described completely - nothing pending Consistent- components do not conflict and specification does not conflict with external specifications --internal and external consistency. Each component must be traceable Feasibility- benefits must outweigh cost, risk analysis (safety-robotics) Testable - the system does what’s described

CS Versioned Components Reduces Complexity Easy to characterize Encourages Reuse Preserves Architecture Structure

CS 55212

CS 55213

CS 55214

CS Tips for Happy Developments Do the ‘right’ thing. Do what you say and say what you do. Scale documents, development formality, and testing to the product trustworthiness. Qualify Solutions Beware of unintended consequences- identify and manage risks Plan for problems. Test documents and salesware. Investigate all customer complaints Don’t expect to be able to bury test docs or design controversies if you get sued.

CS Over reaching Incorrect and “potentially false or misleading” claims were made by 65% of all the commerical software titles examined. Study by Industry Canada’s Competition Bureau, 1999

CS TOP BUSINESS ISSUES 66%: Recruiting qualified people 43%: Software quality 43%: Schedule delays 34%: Managing growth

CS TOP DEVELOPMENT ISSUES 1. Schedule overruns 2. Shortage of skilled staff 3. Poor requirements 4. Inaccurate project estimates

CS THE MBA PHENOMENON Most popular Masters program for mature students Applies across industry sectors Success based on a mix of hype and actual results

CS MBA CURRICULUM Software Engineering Specific: –Software engineering economics –Process (CMM) –Project management –Requirements management –Problem solving