Software Configuration Management Fundamentals

The course provides a comprehensive look at SCM from Project Day-1 through operation and maintenance phases of a systems life cycle in compliance with DoD Directive 5000.1, ISO9000, ISO9001,SOX, CMMI, ISO, OMB Memorandum M-05-23, MIL-HDBK-61A and Sarbanes-Oxley Act Section 404. Build the foundation for process improvement through this integral software development and maintenance course. Successful completion required for SCM Certification eligibility.

STI offers Software Configuration Management Specialist Certification through our SCM curriculum. Prerequisites for certification include 230 SCM and 1230 ICM followed by an open book certification exam.

This is primarily ilt training This is a workshop seminar Courseware may be available for purchase This class may be available at a classroom in Seattle, WA, Contact System Technology Institute for more information

Course Level: introductory Duration: flexible Training Presented in: English

Throughout the course emphasis is focused on integrating SEI-CMM/CMMI compliant SCM functions, tailored to the specific needs of the organization and project. Both informal and formal SCM attributes are linked to the SEI-CMM/CMMI within each topic. Actual project case studies and exercises are utilized to give participants the opportunity to perform key SCM activities.

Impact Analysis/Assessment methods will be explained, describing how this process can assist Project Management, Software Development Management, Quality Assurance and Test Management by facilitating their proactive management of resource consumption of the project budget while mitigating risks associated with unwanted scope creep and schedule delays.

The course provides a comprehensive approach toward achieving organization wide implementation of SCM methods targeting SCM participation and support from day-1 of a development project through to the completion of the operation and maintenance phase of a delivered systems full-lifecycle.

Course Objectives

Participants will learn to implement detailed SCM functionality, policies and procedures, including:

• Defining and establishing detailed SCM functions.
• Writing/Implementing procedures and SCM Plans.
• Tailoring the SCM organization to a project.
• Designing and using change management forms.
• Auditing existing procedures and requirements.

Course Content

• Informal and Formal Controls.
• SCM Principles: Configuration Identification, Change Control, Verification, and Status Accounting.
• Documentation.
• Audits and Control Boards: Pre-Audit Preparations, Software Configuration Control Boards, and SCCB Operations.
• Software Inventory Controls: On-Line Environment, Vault Control, Disaster Recovery Vault Control, and COTS Software.
• Software CM Products: Software Build, and Software Libraries.
• Project Support Activity: Records Retention, and Bidding SCM Changes.
• SCM Special Interests: SCM Continuous Process Improvements, Subcontractor SCM, and Vendor Controls.
• Estimation Methods and Metrics for: Software CM, Hardware CM, and Documentation Management.
• Open Discussion on Current SCM Topics.

Who Should Attend

• Project Managers.
• Individuals with SCM responsibilities.
• Individuals who are affected by or interface with the SCM Organization (Quality,Logistics, Integration, Engineering, Test, and Data Management).

Course Content

1. Introduction and Overview
   • Review of course scope and objectives.
   • CM philosophy and controlling factors.
   • Definitions: Compared and constrasted.
2. Informal and Formal Controls
   • Defining informal and formal activities.
   • Progressing from informal to formal control.
   • Interfaces/tasks of development groups.
   • Step-by-step development and production.
   • Multi-program support capabilities.
   • The Capability Maturity Model (CMM & CMMI).
   • The Software Engineering Institute (SEI).
   • Writing CM plans for hardware and software (generic and specific).
3. SCM Principles
   • Configuration identification: Documents, software, databases, baselines, marking and labeling.
   • Change control: Techniques and strategies; Subscontracts and vendor controls.
   • Verification: Functional and physical characteristics; Audits and media backups.
   • Status accounting: Definition and purpose; Retention, data collected; Database tasking; Status record, tasks and reports; Correction action status accounting.
   • Documentation: Documentationt trees; Control boards and documentation matrixes; Change and release procedures; Authorization and engineering releases.
4. Audits and Control Boards
   • Pre-audit preparations: Management and SCM responsibilities; Auditors and contractor responsibilities.
   • Configuration control boards: Relationships, functions, agendas; Ground rules, membership responsibilities; Writing the SCCB charter.
   • Control board operations: Proposal review and impact assessment; Meetings, minutes, decisions; Directives, implementation and closure.
5. Software Inventory Controls
   • Establishing the SCM on-line environment: Creating baselines and files.
   • SCM software vault control.
   • Writing the vault procedure.
   • SCM off-site disaster vault control: Accessing and writing the vault procedure.
   • SW loaded to workstations: Restrictions; COTS, shareware, public domain; Defining and writing special usage procedures.
   • COTS software.
   • Software problem trouble reports: ID schemes, processing and tracking; Progression from informal to formal; Defining and writing PTR handling procedure.
6. Software CM Products
   • Software Build: Freezing and capturing baselines; Performing the build.
   • Software Libraries: Developmental, master, reusable; Defining and writing library procedures.
7. Program Support Activity
   • Records retention: Requirements; what to keep and how long.
   • Bidding SCM changes: Assessment of instructions and driving impacts.
   • Special considerations.
   • Metrics: Current and historical.
8. SCM Special Interests
   • SCM and continuous improvements: SCM as a support organization; SCM as a control/production organization.
   • Subcontractor and vendor control: Responsibilities and requirements; Accepting deliverable products; Change management, reviews and audits; Checklists.
9. Open Discussion on Current SCM Topics
   • An open forum that encourages participants to share both positive and negative real life experiences that have occurred "in the field." Topics typically include SCM automated tools and systems; SCM presentations to program management; SCM training to be provided to engineering; Improving working relationships and developmental environments.
10. Appendix
    • Document change control.
    • Configuration audits.
    • Supporting technical reviews.
    • Defense plant representative office.
    • Program level CCB's.
    • Interface management.
    • Software delivery media and labels.
    • Hardware and software relationships.
    • SOW and RFP.
    • Deviations and waivers.
    • Engineering change proposals.
    • Test support.
    • Supporting retrofit changes.
    • Contract interpretations.

Course Author

With 35 years of government and private industry experience in engineering support disciplines, Bruce Angstadt specializes in Software Process Improvement, Configuration Management and Technical Training. Since 1992 he has focused on Software Process Improvement activities (primarily Software Engineering Institute CMM Level 2 and Level 3). Mr. Angstadt has worked for Xerox as a Process Improvement Manager; for Harris Corporation as a Principal Integrated Logistics Support Manager; for Bell Laboratories as a Technical Instructor and Technical Writer; and for the U.S. Navy within the Naval Security Group. As a course author and principal instructor, Mr. Angstadt teaches Software Configuration Management courses for the System Technology Institute. As an independent consultant, Mr. Angstadt has worked with numerous corporations to implement their SCM organizations and to assist them in their advancement within the SEI CMM.

• Practical Implementation of Software Configuration Management