Strategies and Technologies for CMMI SM -Compliant Process Engineering Paul R. Croll Chair, IEEE Software Engineering Standards Committee Vice Chair, ISO/IEC JTC1/SC7 U.S. TAG Computer Sciences Corporation

A Preparatory Exercise Paul R. Croll - 2

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll Steps to Success In CMMI SM - Compliant Process Engineering 1 Understand your business processes 2 Look to the CMMI SM for Process Completeness 3 Look to Framework Standards for Life Cycle Definition 4 Look to Supporting Standards for Process Detail 5 Build or Refine Your Process Architecture 6 Execute Your Processes 7 Measure Your Results - Modify Processes as Necessary Confirm Your Status With Independent Appraisals

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 5 Step 1 – Understand your business processes

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 6 Strategy: Your Business is Your Business – It’s Not CMMI SM Implementation l You must fully understand your business processes before you can address process completeness or process compliance. u What are your business processes? u Are they well-documented? u Are roles and responsibilities well-defined? u Are lines of authority well-defined? u Are internal and external interfaces well- defined? u Do your business processes satisfy your business goals? Decision Branch Else Branch Else Activity 1 Activity 2 Activity 5 Activity 4 Activity 3 Activity 6 End AND

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 7 Technology: Use Business Process Modeling Aids to Capture Your Business Processes l Automated tools can help you capture and understand your business processes. u Business Process Management Initiative – BPML 1.0 Specification u CA’s AllFusion Modeling Suite u Casewise Corporate Modeler u Popkin System Architect u Proforma ProVision Modeling Suite u Rational Suite® AnalystStudio® Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 8 Step 2 - Look to the CMMI SM for Process Completeness

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 9 Strategy: Use the CMMI SM as a Guide to Process Completeness Process ManagementEngineering  Organizational Process Focus  Requirements Management  Organizational Process Definition  Requirements Development  Organizational Training  Technical Solution  Organizational Process Performance  Product Integration  Verification  Organizational Innovation and Deployment  Validation Project ManagementSupport  Project Planning  Configuration Management  Project Monitoring and Control  Supplier Agreement Management  Process and Product Quality Assurance  Measurement and Analysis  Integrated Project Management for IPPD  Decision Analysis and Resolution  Risk Management   Integrated Teaming  Causal Analysis and Resolution  Quantitative Project Management Integrated Supplier Management  Organizational Environment for Integration Determine if essential elements of your processes are missing or incomplete

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 10 Technology: Use Tools and Information Assets to the Understand Your Business Processes in the CMMI SM Context l Checklists and Mapping Tables u l SEI CMMI AdoptionWeb Page u l SEI Software Engineering Information Repository u l Basic Support for Cooperative Work (BSCW) Shared Workspace u l Yahoo! CMMI Process Improvement Discussion Group u Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 11 Step 3 - Look to Framework Standards for Life Cycle Definition

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 12 Strategy: Use Process Framework Standards to Aid in Life Cycle Definition l Systems Life Cycle u ISO/IEC 15288, Systems engineering — System life cycle processes l Software Life Cycle u ISO/IEC 12207, Standard for Information Technology —Software life cycle processes u IEEE/EIA , Industry Implementation of International Standard ISO/IEC12207:1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes IEEE/EIA , Industry Implementation of International Standard ISO/IEC12207:1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes – Life Cycle Data IEEE/EIA , Industry Implementation of International Standard ISO/IEC12207:1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes – Implementation considerations

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 13 The ISO/IEC Systems Life Cycle Process Framework SYSTEM LIFE CYCLE PROJECT ASSESSMENT PROJECT PLANNING PROJECT CONTROL DECISION MAKING RISK MANAGEMENT CONFIGURATION MANAGEMENT INFORMATION MANAGEMENT ENTERPRISE(5) SYSTEM LIFE CYCLE MANAGEMENT RESOURCE MANAGEMENT QUALITY MANAGEMENT ENTERPRISE ENVIRONMENT MANAGEMENT INVESTMENT MANAGEMENT TECHNICAL (11) PROJECT (7) ACQUISITION SUPPLY AGREEMENT (2) TRANSITION STAKEHOLDER REQUIREMENTS DEFINITION REQUIREMENTS ANALYSIS ARCHITECTURAL DESIGN IMPLEMENTATION INTEGRATION VERIFICATION VALIDATION OPERATION MAINTENANCE DISPOSAL (25)

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 14 The IEEE/EIA Software Life Cycle Process Framework Source: Singh97 (17+1)

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 15 Relationship between ISO/IEC and ISO/IEC Hardware Implementation Software Implementation Refer to ISO/IEC Human Task Implementation Acquisition Supply Enterprise Environment Management Investment Management System Life Cycle Processes Management Resource Management Quality Management Implementation Stakeholder Requirements Definition Requirements Analysis Architectural Design Integration Verification Transition Validation Operation Disposal Maintenance Project Planning Project AssessmentProject Control Configuration Management Risk Management Decision Making Information Management Usability Source: ISO/IEC JTC 1/SC 7/WG 7 N0643, , © ISO/IEC2002. Project processes Enterprise processes Agreement processes Technical processes

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 16 Step 4 – Look to Supporting Standards For Process Detail

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 17 Strategy: Use Supporting Standards as Best Practice Support for Your Defined System Life Cycle Source: Systems Engineering – A Guide for the application of ISO/IEC System Life Cycle Processes, DTR 19760, © ISO/IEC2002. ConceptDevelopmentProductionUtilizationSupportRetirement ISO/IEC Life Cycle Model Stages ISO/IEC system life cycle processes Increasing level of detail Task Life cycle progression ConceptDevelopmentProductionUtilizationSupportRetirement ISO/IEC Life Cycle Model Stages ISO/IEC system life cycle processes Task level detail from a 3rd Standard For example, IEEE 1220 Increasing level of detail Life cycle progression Activity level detail from a 2nd Standard For example, ANSI/EIA 632 Activity level detail from a 4th Standard A1. ISO/IEC and other engineering standards Task level detail from a 5th Standard

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 18 Strategy: Use Supporting Standards as Best Practice Support for Your Defined Software Life Cycle Source: IEEE/EIA , © IEEE 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 19 CMMI SM SE/SW/IPPD/SS v1.1 Standards Mapping - Process Management  Process Management l EIA Processes for Engineering a System l IEEE 1220, Application and Management of the Systems Engineering Process l IEEE 1074, Developing Software Life Cycle Processes l , Reuse Processes l ISO/IEC 15288, System Life Cycle Processes l IEEE , Software Life Cycle Processes l IEEE , Guide to Software Life Cycle Processes—Life Cycle Data l IEEE , Guide to Software Life Cycle Processes—Implementation Considerations CMMI SM SE/SW/IPPD/SS v1.1 Process Area/Specific Practice Framework Standards Supporting Standards

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 20 CMMI SM SE/SW/IPPD/SS v1.1 Standards Mapping – Project Management  Project Management l IEEE 1220, Application and Management of the Systems Engineering Process l IEEE 1058, Software Project Management Plans l IEEE 1490, A Guide to the Program Management Body of Knowledge l IEEE 1062, Recommended Practice for Software Acquisition l IEEE 1540, Risk Management l IEEE 1028, Software Reviews l ISO/IEC 15288, System Life Cycle Processes l IEEE , Software Life Cycle Processes l IEEE , Guide to Software Life Cycle Processes—Life Cycle Data l IEEE , Guide to Software Life Cycle Processes—Implementation Considerations

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 21 CMMI SM SE/SW/IPPD/SS v1.1 Standards Mapping – Engineering  Engineering l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 1362, Guide for Concept of Operations Document l IEEE 1471, Architectural Description of Software Intensive Systems l IEEE 830, Software Requirements Specifications l IEEE 1016, Software Design Descriptions l IEEE 1012, Software Verification and Validation l IEEE 1008, Software Unit Testing l ISO/IEC 15288, System Life Cycle Processes l IEEE , Software Life Cycle Processes l IEEE , Guide to Software Life Cycle Processes—Life Cycle Data l IEEE , Guide to Software Life Cycle Processes—Implementation Considerations l IEEE 1228, Software Safety Plans l IEEE 1063, Software User Documentation l IEEE 1219, Software Maintenance l IEEE ,.2, IDEF0, IDEF1X97 l IEEE , Data Model for Reuse Library Interoperability

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 22 CMMI SM SE/SW/IPPD/SS v1.1 Standards Mapping – Support  Support l IEEE 828, Software Configuration Management Plans l IEEE 730, Software Quality Assurance Plans l IEEE 982.1, Dictionary of Measures to Produce Reliable Software l IEEE 1045, Software Productivity Metrics l IEEE 1061, Software Quality Metrics Methodology l IEEE 1219, Software Maintenance l ISO/IEC 15288, System Life Cycle Processes l IEEE , Software Life Cycle Processes l IEEE , Guide to Software Life Cycle Processes—Life Cycle Data l IEEE , Guide to Software Life Cycle Processes—Implementation Considerations l IEEE 1465 (ISO/IEC 12119) - Software Packages - Quality Requirements and Testing l IEEE (ISO/IEC ) - Functional Size Measurement - Part 1: Definition of Concepts

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 23 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 24 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications Requirements Analysis Process Purpose of the Requirements Analysis Process The purpose of the Requirements Analysis Process is to transform the stakeholder, requirement-driven view of desired services into a technical view of a required product that could deliver those services. This process builds a representation of a future system that will meet stakeholder requirements and that, as far as constraints permit, does not imply any specific implementation. It results in measurable system requirements that specify, from the developer’s perspective, what characteristics it is to possess and with what magnitude in order to satisfy stakeholder requirements Requirements Analysis Process Outcomes As a result of the successful implementation of the Requirements Analysis Process: a) The required characteristics, attributes, and functional and performance requirements for a product solution are specified. b) Constraints that will affect the architectural design of a system and the means to realize it are specified. c) The integrity and traceability of system requirements to stakeholder requirements is achieved.... Source: ISO/IEC CD FDIS, © ISO/IEC2002.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 25 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications The specific intended use of the system to be developed shall be analyzed to specify system requirements. The system requirements specification shall describe: functions and capabilities of the system; business, organizational and user requirements; safety, security, human-factors engineering (ergonomics), interface, operations, and maintenance requirements; design constraints and qualification requirements. The system requirements specification shall be documented The developer shall establish and document software requirements, including the quality characteristics specifications, described below.... a) Functional and capability specifications, including performance, physical characteristics, and environmental conditions under which the software item is to perform; b) Interfaces external to the software item; c) Qualification requirements; d) Safety specifications, including those related to methods of operation and maintenance, environmental influences, and personnel injury; e) Security specifications, including those related to compromise of sensitive information... Source: IEEE/EIA , © IEEE 2001.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 26 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications 7.2 Build a well-formed requirement The analysts carry out this subphase by doing the following: a) Ensuring that each requirement is a necessary, short, definitive statement of need (capability, constraints); b) Defining the appropriate conditions (quantitative or qualitative measures) for each requirement and avoiding adjectives such as “resistant” or “industry wide;” c) Avoiding requirements pitfalls (see 6.4); d) Ensuring the readability of requirements, which entails the following: 1) Simple words/phrases/concepts; 2) Uniform arrangement and relationship; 3) Definition of unique words, symbols, and notations; 4) The use of grammatically correct language and symbology. e) Ensuring testability. Example: Capability: Move people between Los Angeles and New York Condition: Cruising speed of 200 km/hr Constraint: Maximum speed of 300 km/hr Well-formed requirement: This system should move people between Los Angeles and New York at an optimal cruising speed of 200 km/hr with a maximum speed of 300 km/hr. Source: IEEE , © IEEE 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 27 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications Source: IEEE , © IEEE 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 28 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications Functions Functional requirements should define the fundamental actions that must take place in the software in accepting and processing the inputs and in processing and generating the outputs. These are generally listed as “shall” statements starting with “The system shall” These include: a) Validity checks on the inputs b) Exact sequence of operations c) Responses to abnormal situations, including: 1) Overflow 2) Communication facilities 3) Error handling and recovery d) Effect of parameters e) Relationship of outputs to inputs... 1) It may be appropriate to partition the functional requirements into subfunctions or subprocesses. This does not imply that the software design will also be partitioned that way Performance requirements This subsection should specify both the static and the dynamic numerical requirements placed on the soft- ware or on human interaction with the software as a whole. Static numerical requirements may include the following: a) The number of terminals to be supported; b) The number of simultaneous users to be supported; c) Amount and type of information to be handled. Source: IEEE , © IEEE 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 29 An Example - Requirements Development SP Establish Product and Product Component Requirements u Establish and maintain, from the customer requirements, product and product component requirements essential to product and product component effectiveness and affordability l ISO/IEC 15288, System Life Cycle Processes  Clause Requirements Analysis Process l IEEE/EIA , Software Life Cycle Processes u Clause System Requirements Analysis u Clause Software requirements analysis l IEEE 1233, Guide for Developing System Requirements Specifications l IEEE 830, Software Requirements Specifications Source: IEEE , © IEEE 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 30 Technology: Use Mapping Tools and Reports to Select Supporting Standards and Identify Best Practice Detail l The IEEE CMMI SM Mapping Project u l The FAA-iCMM  Project u l The Software Productivity Consortium’s Quagmap  Tool u Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 31 The IEEE CMMI SM Mapping Project – Background l Study Group on External Standards Coordination formed u Initial Task: Map the IEEE Software Engineering Standards Collection to the CMMI SM. l Software Productivity Consortium’s Quagmap  selected as the mapping tool. l License agreements for distribution of Standards and the Quagmap  tool to Study Group members negotiated and signed. l Results to be published on the SESC web site.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 32 The SPC Quagmap  Tool Source: Software Productivity Consortium

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 33 Framework A Framework B Quagmap  Information Structure Data Item … … Mapping Relationship Mapping Source: Software Productivity Consortium,

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 34 Quagmap  Mappings and Relationships l Mappings define how well one framework (the Source) meets the intent of the second (the Target) l Relationships define how well each source framework data item meets the intent of the associated target framework item[s] u [none] u Partial u Complete l Standards mappings are generally done in both directions Source: Software Productivity Consortium,

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 35 Quagmap  Reports l Framework: Description and all data items l Relationship: Source framework items and related data items from one or more target frameworks l Coverage: Target framework items and the source data items that meet them l Gap Identification: Target items not fully satisfied by the source data items l Inferred Mapping: Given a mapping from A:B, and B:C; what is a likely set of relationships from A:C? Source: Software Productivity Consortium,

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 36 Quagmap  Relationship Report Source: Software Productivity Consortium

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 37 How You Can Help... l Get involved in the mapping effort u Initial mapping u Peer reviewer l What you will receive u A Copyright Notice and License Agreement u An electronic copy of the standard(s) to be mapped the associated framework standard (s) u A copy of the Quagmap  tool u A mapping guide l How to get started u Contact me at: to let me know of your

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 38 Step 5 – Build or Refine Your Process Architecture

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 39 Strategy: Use Best Practice Information to Build or Refine Your Process Architecture l Existing process assets l CMMI SM gap identification l Framework and Supporting Standards l Industry and DoD best practices u SEI CMMI AdoptionWeb Page u SEI Software Engineering Information Repository u USAF Software Technology Support Center u Navy SPAWAR Systems Engineering Process Office Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 40 Technology: Use Tools to Support Process Definition l CMMI SM Reference Card u ations/ref-card.pdf ations/ref-card.pdf l Process Asset Libraries l Knowledge Portals l pragma Systems Corporation’s processMax 5 u 5fin.htm 5fin.htm Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 41

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 42 Step 6 – Execute Your Processes

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 43 Strategy: Base Your Business Activities on Your Defined Processes l Institutionalize your processes u Train your workforce in your defined processes u Incentivize both management and staff l Check process performance u Goal  Process  Results (GPR) A business-focused Plan  Do  Check  Act cycle For a given set of results either goals or processes may be modified Goal Results Process

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 44 Technology: Use Tools to Facilitate Process Deployment, Training, and Execution l Process Asset Libraries l Knowledge Portals l Computer-Based Training (CBTs) l Web-Based Training (WBT) l Net-Based Collaboration u MS Windows NetMeeting u AT&T Web Meeting HJK2YN2ZQFLAZBYZCFEY?productId=wms_eu HJK2YN2ZQFLAZBYZCFEY?productId=wms_eu u IBM Lotus Sametime Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 45 Step 7 – Measure Your Results - Modify Processes as Necessary

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 46 Strategy: Establish an Active Measurement Program l For both Processes and Products: u Identify measurement objectives that are aligned with your business needs u Choose specific measures, data collection and storage mechanisms, analysis techniques, and reporting and feedback mechanisms that support your measurement objectives u Implement your measurement program u Provide decision-makers with objective results that can be used in making informed decisions u Periodically assess your measurement program to ensure that it is meeting current business needs

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 47 Technology: Use Tools to Support Measurement of Process Performance and Product Quality l Spreadsheets l Control Charts u l PSM Insight u l Distributive Software’s DataDrill u l SEI Software Engineering Measurement and Analysis Program u l INCOSE Measurement Working Group u Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 48 Step 8 – Confirm Your Status With Independent Appraisals

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 49 Strategy: Select an Appraisal Style Suited to Your Process Improvement Objectives No YesRating? LowMediumHigh Relative: Cost/Duration Confidence Accuracy Quick Look Incremental Gap analysis Initial Incremental Self-assessment Benchmark Baseline establishment Usage Mode Class CClass BClass AAttributes

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 50 Technology: Use Process Appraisal Tools to Capture Appraisal Data and Facilitate Findings l Checklists l Spreadsheets l Databases l Integrated Systems Diagnostics’ Appraisal Wizard u l pragma Systems Corporation’s processMax 5 u l SEI Transition Partner Appraisal Services u tech.html#SCAMPI tech.html#SCAMPI Disclaimer: Tools and services mentioned are for example only. Such mention is not to be construed as an endorsement by the author, CSC, IEEE, ISO. or IEC

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll Steps to Success In CMMI SM - Compliant Process Engineering 1 Understand your business processes 2 Look to the CMMI SM for Process Completeness 3 Look to Framework Standards for Life Cycle Definition 4 Look to Supporting Standards for Process Detail 5 Build or Refine Your Process Architecture 6 Execute Your Processes 7 Measure Your Results - Modify Processes as Necessary Confirm Your Status With Independent Appraisals

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 52 For More Information... Paul R. Croll Computer Sciences Corporation 5166 Potomac Drive King George, VA Phone: Fax: For IEEE Standards: For ISO/IEC Standards:

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 53 References CMMI SM -SE/SW/IPPD/SS, V1.1, CMMI for Systems Engineering/Software Engineering/Integrated Product and Process Development, and Supplier Sourcing Version 1.1, CMMI SM -SE/SW/IPPD/SS, V1.1, Continuous Representation. CMU/SEI-CMU/SEI-2002-TR-011, ESC-TR , Carnegie Mellon University, Software Engineering Institute, Pittsburgh, PA, March IEEE Standard , Recommended Practice for Software Requirements Specifications, Institute of Electrical and Electronics Engineers, Inc. New York, NY, IEEE Standard , Guide for Developing System Requirements Specifications, Institute of Electrical and Electronics Engineers, Inc. New York, NY, 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 54 References - 2 IEEE/EIA Standard , Industry Implementation of International Standard ISO/IEC12207:1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes, Institute of Electrical and Electronics Engineers, Inc. New York, NY, IEEE/EIA Standard , Industry Implementation of International Standard ISO/IEC12207:1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes – Life cycle data, Institute of Electrical and Electronics Engineers, Inc. New York, NY, IEEE/EIA Standard , Industry Implementation of International Standard ISO/IEC12207:1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes – Implementation considerations, Institute of Electrical and Electronics Engineers, Inc. New York, NY, 1998.

Fifteenth Annual Software Technology Conference – Track 3 – 30 April 2003, Paul R. Croll - 55 References - 3 ISO/IEC FDIS:2002, Systems Engineering — System Life Cycle Processes, ISO/IEC JTC1/SC7, ISO/IEC DTR:2002, Systems Engineering – A Guide for the application of ISO/IEC System Life Cycle Processes, ISO/IEC JTC1/SC7, [Singh97] Raghu Singh, An Introduction to International Standards ISO/IEC 12207, Software Life Cycle Processes, 1997.