Report from the IEEE Computer Society WG on revision of the SCM Standard, IEEE Std 828

1. Report from the IEEE Computer Society WG on revision of the SCM Standard, IEEE Std 828 Mike Smith P828 WG Member Software and Systems Engineering Standards Committee

2. Context of the P828 Project • Existing IEEE Std 828-2005 is a standard for SCMPs • A previous standard for SCM processes, IEEE Std 1042 was withdrawn when it became outdated. One of its outstanding problems was its preference for a cascading branching model. • No standard currently exists to define the SCM processes needed for successful SWE. Software and Systems Engineering Standards Committee

3. The WG Team • The team was recruited from people who perform and/or oversee SCM functions professionally. • It represents • A national lab in the USA • Air traffic control in the UK • An Argentinean integration specialist for a multinational HW/SW manufacturer • SCM and release engineering experts for many comercial software product companies • The editor of CMCrossroads, the most active community of CM practitioners on the web. Software and Systems Engineering Standards Committee

4. Core Team Members • Bob Aiello, editor, CMCrossroads.com • Darrel Strom, SCM Practice Manager, Davenport Consulting • Diego Pamio, Integration Manager, Intel Argentina • Mike Smith, … • Ranata Johnson, SCM Resource Manager, Pacific Northwest National Labs • Chuck Walrad, Managing Director, Davenport Consulting, WG Chair Software and Systems Engineering Standards Committee

5. P828 WG Goals • Produce a draft standard that is usable and useful to the SWE community, in industry as well as government, in establishing successful SCM processes. • Assure harmony with key “anchor points”: • 122207 • 15288 • SEVOCAB (ISO/IEC 24765) • SWEBOK • CMMi Software and Systems Engineering Standards Committee

6. WG Challenges • The advent of SCM tools over the past 15+ years has helped to bring awareness of the need for SCM to a wide audience of SW engineering staff and managers • The evolution of the industry view of SCM and Release Engineering functions is not well-aligned with the traditional 4 core elements of CM: identification, control, auditing and accounting. Software and Systems Engineering Standards Committee

7. WG Challenges • SCM position descriptions include many activities outside of these 4 core elements, such as build engineering, which 12207, etc. categorize as developer functions. • Our challenge is to preserve the meaning of the 4 core elements of SCM and to meaningfully relate those to the SCM professional’s job description, as well as to those working in SWE organizations that have not established an SCM role/function. Software and Systems Engineering Standards Committee

8. WG Approach • Recruit practitioners from a spectrum of SWE environments • Jointly review 12207 and 15288 SWE processes and analyze to achieve common understanding. • Compare 828-2005 to the “anchor” documents and note any discrepancies. Software and Systems Engineering Standards Committee

9. WG Approach • Elicit practitioners’ professional experiences to relate to 12207/15288 processes • Develop content for 828 that shows how the 4 core elements of SCM apply across the SWLC • Consider ITIL processes in developing post-release SCM processes. • Review additions for consistency with the “anchor” documents. Software and Systems Engineering Standards Committee

10. WG Approach • Each of the 4 core elements of traditional SCM is supplemented with discussions of how that element applies to the major SWLC processes. • The discussions include the post-delivery processes, such as SW installation, operations, maintenance and disposal. Software and Systems Engineering Standards Committee

11. SCM Activity Varies Across the SWLC Identification Planning Merging Branching Change Control Planning Code Change Management Design Change Management Architecture Change Management Requirements Change Management Arch. Baseline Review Audits Planning Code Baseline Review FCA PCA Reqs. Baseline Review Design Baseline Review B.M. Planning Software Builds Release Notes R.M. Planning Software and Systems Engineering Standards Committee Product Packaging Service Packs Releases

12. SCM Activities Vary in Intensity over the SWLC PlanningProcess Coveringdifferent SCM Disciplines and non SCM-Disciplines (notshownhere) BaseliningProcess AppliedtodifferentBaselines in differentPhases Baseline CC Process Part of “ProgressReview” process SCM Status Accounting CI VersioningProcess AuditProcess Mirrors non SCM Discipline Audits Appliedtoaudittypes (BA, PCA, FCA) in differentphases BuildProcess ReleaseProcess Software and Systems Engineering Standards Committee

13. SCM Must Be Agnostic & Support Today’s SW Approaches, Like SOA Software and Systems Engineering Standards Committee

14. Example of Content (1- Section 3) • 3. SCM Planning & Management • Purpose of the Plan • Scope of the Plan • Overview of the Software Project • Configuration Items to be Included • Limitations & Assumptions Affecting the Plan • Definitions • References • SCM management • Project Organization • SCM responsibilities • Applicable policies, directives, and procedures • Management of the SCM process • SCM Activities for the Project • SCM Schedules • SCM Resources • SCM Plan Maintenance Structure of the Planning & Mgt Section is like the existing 828 Software and Systems Engineering Standards Committee

15. Example of Content (2- Section 4) • 4. Configuration identification • 4.1 Identifying configuration items • 4.2 Naming configuration items • 4.3 Acquiring configuration items • 4.4 How Configuration Identification Applies in the Software Life Cycle • 4.4.1 Software Requirements Analysis Process • 4.4.2 Software Design Process • 4.4.3, 4.4.4 Software construction and Integration Processes • 4.4.5 Software testing Process • 4.4.6 Software acceptance Process • 4.4.7 Software installation Process • 4.4.8 Software operation Process • 4.4.9 Software maintenance Process • 4.4.10 Software disposal Process The 4 core elements are explained for the technical SW implementation processes in 12207, section 7, and for the SW areas of section 6. - Software and Systems Engineering Standards Committee

16. Example of Content (3 - Section 6) • 6. Configuration status accounting • 6.1 Record and Analyze • 6.2 Provide Reports and Insight • 6.3 How Configuration Status Accounting Applies Over the Software Life Cycle • 6.3.1 Software requirements analysis • 6.3.2 Software design • 6.3.3 Software construction & integration • 6.3.4 Software Testing • 6.3.5 Software Acceptance • 6.3.6Software Installation • 6.3.7 Software Operation • 6.3.8 Software Maintenance • 6.3.9 Software Disposal The 4 core elements are explained for the technical SW implementation processes in 12207, section 7, and for the SW areas of section 6. - Software and Systems Engineering Standards Committee

17. Current Status • Approximately 70% of the intended content has been developed via contributions from individual team members • More development work is needed for the Operations, Maintenance and Disposal areas • A preliminary edit for consistency of voice is underway • Next Step is to re-review for harmony with 12207 and 15288. Software and Systems Engineering Standards Committee