Paul R Croll Chair IEEE Software Engineering Standards

Paul R. Croll Chair, IEEE Software Engineering Standards Committee Vice Chair, ISO/IEC JTC 1/SC 7 U. S. TAG Eight Steps to Success in CMMI -Compliant Process Engineering: Strategies and Supporting Technology Computer Sciences Corporation 16 th pcroll@csc. com Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Annual Systems and Software Copyright 2004, Paul R. Croll, All rights reserved

8 Steps to Success In CMMI Compliant Process Engineering 1 5 Understand your business processes Build or Refine Your Process Architecture 2 6 Look to the CMMISM for Process Completeness Execute Your Processes 3 7 Look to 4 Framework Standards for Life Cycle Definition Measure Your Results - Modify Processes as Necessary 8 3 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved Look to Supporting Standards for Process Detail Confirm Your Status With Independent Appraisals 3 3 3 2

Step 1 – Understand your business processes 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 3

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

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 n u CA’s All. Fusion Modeling Suite n u http: //www. popkin. com/ Proforma Pro. Vision Modeling Suite n u http: //www. casewise. com/ Popkin System Architect n u http: //www. asapsoftware. com/ca/allfusion. pdf Casewise Corporate Modeler n u http: //www. bpmi. org/ http: //www. proformacorp. com/ Rational Suite® Analyst. Studio® n http: //www. rational. com/products/astudio/index. jsp 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 5

Step 2 - Look to the CMMI for Process Completeness 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 6

Strategy: Use the CMMI as a Guide to Process Completeness Determine if essential elements of your processes are missing or incomplete Process Management · · Organizational Process Focus Organizational Process Definition Organizational Training Organizational Process Performance · Organizational Innovation and Deployment Project Management · · · · Project Planning Project Monitoring and Control Supplier Agreement Management Integrated Project Management for IPPD Risk Management Integrated Teaming Integrated Supplier Management Quantitative Project Management Engineering · · · Requirements Management Requirements Development Technical Solution Product Integration Verification Validation Support · Configuration Management · Process and Product Quality Assurance · Measurement and Analysis · Decision Analysis and Resolution · Organizational Environment for Integration · Causal Analysis and Resolution 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 7

Technology: Use Tools and Information Assets to the Understand Your Business Processes in the CMMI Context l Checklists and Mapping Tables u l SEI CMMI Adoption. Web Page u l http: //seir. sei. cmu. edu/ Basic Support for Cooperative Work (BSCW) Shared Workspace u l http: //www. sei. cmu. edu/cmmi/adoption. html SEI Software Engineering Information Repository u l http: //www. stsc. hill. af. mil/consulting/cmmi/documents. html http: //jo. sei. cmu. edu/pub/english. cgi/0/323123 Yahoo! CMMI Process Improvement Discussion Group u http: //groups. yahoo. com/group/cmmi_process_improvement/ 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 8

Step 3 - Look to Framework Standards for Life Cycle Definition 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 9

Strategy: Use Process Framework Standards to Aid in Life Cycle Definition l Systems Life Cycle u l ISO/IEC 15288, Systems engineering — System life cycle processes Software Life Cycle u u ISO/IEC 12207, Standard for Information Technology —Software life cycle processes IEEE/EIA 12207. 0, Industry Implementation of International Standard ISO/IEC 12207: 1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes n n IEEE/EIA 12207. 1, Industry Implementation of International Standard ISO/IEC 12207: 1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes – Life Cycle Data IEEE/EIA 12207. 2, Industry Implementation of International Standard ISO/IEC 12207: 1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes – Implementation considerations 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 10

The ISO/IEC 15288 Systems Life Cycle Process Framework ENTERPRISE ENVIRONMENT MANAGEMENT INVESTMENT MANAGEMENT SYSTEM LIFE CYCLE MANAGEMENT RESOURCE MANAGEMENT SYSTEM LIFE CYCLE (25) ENTERPRISE(5) AGREEMENT (2) PROJECT (7) QUALITY MANAGEMENT ACQUISITION SUPPLY PROJECT PLANNING PROJECT ASSESSMENT PROJECT CONTROL DECISION MAKING RISK MANAGEMENT CONFIGURATION MANAGEMENT INFORMATION MANAGEMENT TECHNICAL (11) STAKEHOLDER REQUIREMENTS DEFINITION REQUIREMENTS ANALYSIS ARCHITECTURAL DESIGN IMPLEMENTATION INTEGRATION VERIFICATION TRANSITION VALIDATION OPERATION MAINTENANCE DISPOSAL 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 11

The IEEE/EIA 12207 Software Life Cycle Process Framework ACQUISITION SUPPLY DEVELOPMENT OPERATION SOFTWARE LIFE CYCLE (17+1) MAINTENANCE PRIMARY (5) SUPPORTING (8) DOCUMENTATION CONFIGURATION MANAGEMENT QUALITY ASSURANCE VERIFICATION VALIDATION JOINT REVIEW AUDIT PROBLEM RESOLUTION ORGANIZATIONAL (4) MANAGEMENT Source: Singh 97 INFRASTRUCTURE IMPROVEMENT TRAINING TAILORING 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 12

Relationship between ISO/IEC 15288 and ISO/IEC 12207 Project Planning Project Assessment Risk Management Decision Making Project Control Configuration Management Stakeholder Requirements Definition Validation Usability Information Management Operation Transition Maintenance Requirements Analysis Verification Architectural Design Integration Project processes Technical processes Disposal Implementation Enterprise Environment Management Hardware Implementation Investment Management Software Implementation Refer to ISO/IEC 12207 Human Task Implementation System Life Cycle Processes Management Enterprise processes Resource Management Quality Management Source: ISO/IEC JTC 1/SC 7/WG 7 N 0643, 2002 -10 -20, © ISO/IEC 2002. Acquisition Supply 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved Agreement processes 13

Step 4 – Look to Supporting Standards For Process Detail 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 14

Strategy: Use Supporting Standards as Best Practice Support for Your Defined System Life Cycle Life cycle progression ISO/IEC 15288 Life Cycle Model Stages Concept Development Production Utilization Support Retirement Increasing level of detail ISO/IEC 15288 system life cycle processes Activity level detail from a 2 nd Standard For example, ANSI/EIA 632 Task level detail from a 3 rd Standard For example, IEEE 1220 Activity level detail from a 4 th Standard Task level detail from a 5 th Standard A 1. ISO/IEC 15288 and other engineering standards 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved Source: Systems Engineering – A Guide for the application of ISO/IEC 15288 System Life Cycle Processes, ISO/IEC 19760, © ISO/IEC 2003. 15

Strategy: Use Supporting Standards as Best Practice Support for Your Defined Software Life Cycle Source: IEEE/EIA 12207. 1 -1997, © IEEE 1998. 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 16

CMMI SE/SW/IPPD/SS v 1. 1 Standards Mapping - Process Management ISO/IEC 15288, System Life Cycle Process Management Processes l IEEE 12207. 0, Software Life Cycle Processes EIA 632 - Processes for l Engineering a System SE/SW/IPPD/SSIEEE 12207. 1, Guide to Software Life CMMISM v 1. 1 Cycle Processes—Life Cycle Data IEEE 1220, Application and Process Area/Specific Practice l IEEE 12207. 2, Guide to Software Life Management of the Systems Cycle Processes—Implementation Engineering Process Considerations IEEE 1074, Developing Software Life Cycle Processes Framework Standards 1517 -1999, Reuse Processes l l l Supporting Standards 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 17

CMMI SE/SW/IPPD/SS v 1. 1 Standards Mapping – Project Management l l l l IEEE 1220, Application and Management of the Systems Engineering Process IEEE 1058, Software Project Management Plans IEEE 1490, A Guide to the Program Management Body of Knowledge IEEE 1062, Recommended Practice for Software Acquisition IEEE 1540, Risk Management IEEE 1028, Software Reviews l l ISO/IEC 15288, System Life Cycle Processes IEEE 12207. 0, Software Life Cycle Processes IEEE 12207. 1, Guide to Software Life Cycle Processes—Life Cycle Data IEEE 12207. 2, Guide to Software Life Cycle Processes—Implementation Considerations 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 18

CMMI SE/SW/IPPD/SS v 1. 1 Standards Mapping – Engineering l l l l l IEEE 1233, Guide for Developing System Requirements Specifications IEEE 1362, Guide for Concept of Operations Document IEEE 1471, Architectural Description of Software Intensive Systems IEEE 830, Software Requirements Specifications IEEE 1016, Software Design Descriptions IEEE 1012, Software Verification and Validation IEEE 1008, Software Unit Testing l l l l ISO/IEC 15288, System Life Cycle Processes IEEE 12207. 0, Software Life Cycle Processes IEEE 12207. 1, Guide to Software Life Cycle Processes—Life Cycle Data IEEE 12207. 2, Guide to Software Life Cycle Processes—Implementation Considerations IEEE 1228, Software Safety Plans IEEE 1063, Software User Documentation IEEE 1219, Software Maintenance IEEE 1320. 1, . 2, IDEF 0, IDEF 1 X 97 IEEE 1420. 1, Data Model for Reuse Library Interoperability 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 19

CMMI SE/SW/IPPD/SS v 1. 1 Standards Mapping – Support l l l l IEEE 828, Software Configuration Management Plans IEEE 730, Software Quality Assurance Plans IEEE 982. 1, Dictionary of Measures to Produce Reliable Software IEEE 1045, Software Productivity Metrics IEEE 1061, Software Quality Metrics Methodology IEEE 1219, Software Maintenance l l ISO/IEC 15288, System Life Cycle Processes IEEE 12207. 0, Software Life Cycle Processes IEEE 12207. 1, Guide to Software Life Cycle Processes—Life Cycle Data IEEE 12207. 2, Guide to Software Life Cycle Processes—Implementation Considerations IEEE 1465 (ISO/IEC 12119) - Software Packages - Quality Requirements and Testing IEEE 14143. 1 (ISO/IEC 1443 -1) Functional Size Measurement - Part 1: Definition of Concepts 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 20

An Example - Requirements Development SP 2. 1 -1 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 u l IEEE/EIA 12207. 0, Software Life Cycle Processes u u l l Clause 5. 5. 3 - Requirements Analysis Process Clause 5. 3. 2 - System Requirements Analysis Clause 5. 3. 4 - Software requirements analysis IEEE 1233, Guide for Developing System Requirements Specifications IEEE 830, Software Requirements Specifications 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 21

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

An Example - Requirements Development 5. 3. 2. 1 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 l SP 2. 1 -1 Establish Product and documented. 5. 3. 4. 1 The developer shall establish and document software Product Component Requirements requirements, including the quality characteristics specifications, u Establish described below. . and maintain, from the a) Functional and capability specifications, including customer requirements, product and performance, physical characteristics, and environmental product component requirements l conditions under which the software item is to perform; essential to the software item; to product and product b) Interfaces external c) Qualification requirements; component effectiveness and d) Safety specifications, including those related to methods of affordability operation and maintenance, environmental influences, and personnel injury; e) Security specifications, including those related to compromise of sensitive information. . . l l Source: IEEE/EIA 12207. 0 -1997, © IEEE 2001. ISO/IEC 15288, System Life Cycle Processes u Clause 5. 5. 3 - Requirements Analysis Process IEEE/EIA 12207. 0, Software Life Cycle Processes u u Clause 5. 3. 2 - System Requirements Analysis Clause 5. 3. 4 - Software requirements analysis IEEE 1233, Guide for Developing System Requirements Specifications IEEE 830, Software Requirements Specifications 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 23

An Example - Requirements Development 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” 2. 1 -1 Establish Product and l ISO/IEC 15288, System Life Cycle SP or “industry wide; ” c) Avoiding requirements pitfalls (see 6. 4); Product Component Requirements d) Ensuring the readability of requirements, which entails the Processes following: u Clause 5. 5. 3 - Requirements Analysis u Establish and maintain, from the 1) Simple words/phrases/concepts; Process 2) Uniformcustomer requirements, product and arrangement and relationship; 3) Definition of unique words, symbols, and notations; product component requirements l IEEE/EIA 12207. 0, Software Life Cycle 4) The use of grammatically correct language and symbology. essential to product and product e) Ensuring testability. Processes component effectiveness and Example: Capability: Move people between Los Angeles and New York u Clause 5. 3. 2 - System Requirements affordability Analysis Condition: Cruising speed of 200 km/hr Constraint: Maximum speed of 300 km/hr u Clause 5. 3. 4 - Software requirements Well-formed requirement: This system should move people between Los Angeles and New York at an optimal cruising speed analysis of 200 km/hr with a maximum speed of 300 km/hr. l l Source: IEEE 1233 -1998, © IEEE 1998. IEEE 1233, Guide for Developing System Requirements Specifications IEEE 830, Software Requirements Specifications 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 24

An Example - Requirements Development SP 2. 1 -1 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 u l IEEE/EIA 12207. 0, Software Life Cycle Processes u u l l Clause 5. 5. 3 - Requirements Analysis Process Clause 5. 3. 2 - System Requirements Analysis Clause 5. 3. 4 - Software requirements analysis IEEE 1233, Guide for Developing System Requirements Specifications IEEE 830, Software Requirements Specifications Source: IEEE 1233 -1998, © IEEE 1998. 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 25

An Example - Requirements Development 5. 3. 2 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 l ISO/IEC 15288, System Life Cycle b) Exact 2. 1 -1 Establish Product and SP sequence of operations c) Responses to abnormal situations, including: Processes Product Component Requirements 1) Overflow 2) Communication facilities u Clause 5. 5. 3 - Requirements Analysis u Establish and maintain, from the 3) Error handling and recovery Process customer requirements, product and d) Effect of parameters product component requirements e) Relationship of outputs to inputs. . . l IEEE/EIA 12207. 0, Software Life Cycle 1) It mayessential to product and product requirements into be appropriate to partition the functional Processes subfunctions or subprocesses. This does component effectiveness and partitioned that way. not imply that the software design will also be u Clause 5. 3. 2 - System Requirements affordability 5. 3. 3 Performance requirements Analysis This subsection should specify both the static and the dynamic numerical requirements placed on the software or on human u Clause 5. 3. 4 - Software requirements interaction with the software as a whole. Static numerical analysis requirements may include the following: a) The number of terminals to be supported; IEEE 1233, Guide for Developing System b) The number of simultaneous users to be supported; l c) Amount and type of information to be handled. l Source: IEEE 830 -1998, © IEEE 1998. Requirements Specifications IEEE 830, Software Requirements Specifications 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 26

An Example - Requirements Development SP 2. 1 -1 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 u l IEEE/EIA 12207. 0, Software Life Cycle Processes u u l l Clause 5. 5. 3 - Requirements Analysis Process Clause 5. 3. 2 - System Requirements Analysis Clause 5. 3. 4 - Software requirements analysis IEEE 1233, Guide for Developing System Requirements Specifications IEEE 830, Software Requirements Specifications Source: IEEE 830 -1998, © IEEE 1998. 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 27

Technology: Use Mapping Tools and Reports to Select Supporting Standards and Identify Best Practice Detail l The IEEE CMMI Mapping Project u l The FAA-i. CMM Project u l http: //computer. org/standards/sesc/ http: //www 2. faa. gov/aio/Process. Engr/i. CMM/index. htm The Software Productivity Consortium’s Quagmap Tool u http: //www. software. org/pub/products/quagmap. asp 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 28

Step 5 – Build or Refine Your Process Architecture 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 29

Strategy: Use Best Practice Information to Build or Refine Your Process Architecture l l Existing process assets CMMISM gap identification Framework and Supporting Standards Industry and Do. D best practices u SEI CMMI Adoption Web Page n u SEI Software Engineering Information Repository n u http: //seir. sei. cmu. edu/ USAF Software Technology Support Center n u http: //www. sei. cmu. edu/cmmi/adoption. html http: //www. stsc. hill. af. mil Navy SPAWAR Systems Engineering Process Office n http: //sepo. spawar. navy. mil/sepo/index 2. html 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 30

Technology: Use Tools to Support Process Definition l CMMI Reference Card u l l l http: //www. sei. cmu. edu/cmmi/public ations/ref-card. pdf Process Asset Libraries Knowledge Portals pragma Systems Corporation’s process. Max 5 u http: //www. pragmasystems. com/max 5 fin. 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 31

16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved

Step 6 – Execute Your Processes 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 33

Strategy: Base Your Business Activities on Your Defined Processes l Institutionalize your processes u u l Train your workforce in your defined processes Incentivize both management and staff Check process performance u Goal Process Goal Process Results (GPR) n For a given set of results either goals or processes may be modified 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved Results 34

Technology: Use Tools to Facilitate Process Deployment, Training, and Execution l l l Process Asset Libraries Knowledge Portals Computer-Based Training (CBTs) Web-Based Training (WBT) Net-Based Collaboration u MS Windows Net. Meeting n u AT&T Web Meeting n u http: //www. microsoft. com/windows/netmeeting/default. asp http: //www. business. att. com/products/productdetails. jsp; jsessionid=PM 0 HJK 2 YN 2 ZQFLAZBYZCFEY? product. Id=wms_eu IBM Lotus Sametime n http: //www. lotus. com/products/lotussametime. nsf/wdocs/homepage 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 35

Step 7 – Measure Your Results Modify Processes as Necessary 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 36

Strategy: Establish an Active Measurement Program l For both Processes and Products: u u u Identify measurement objectives that are aligned with your business needs Choose specific measures, data collection and storage mechanisms, analysis techniques, and reporting and feedback mechanisms that support your measurement objectives Implement your measurement program Provide decision-makers with objective results that can be used in making informed decisions Periodically assess your measurement program to ensure that it is meeting current business needs 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 37

Technology: Use Tools to Support Measurement of Process Performance and Product Quality l l Spreadsheets Control Charts u l PSM Insight u l http: //www. distributive. com/solutions_maturitymodel. html SEI Software Engineering Measurement and Analysis Program u l http: //www. psmsc. com/PSMI. asp Distributive Software’s Data. Drill u l http: //www. isixsigma. com/st/control_charts/ http: //www. sei. cmu. edu/sema/welcome. html INCOSE Measurement Working Group u http: //www. incosemwg. org/ 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 38

Step 8 – Confirm Your Status With Independent Appraisals 3 3 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 39

Strategy: Select an Appraisal Style Suited to Your Process Improvement Objectives Attributes Usage Mode Class A • Benchmark • Baseline establishment Class B • Initial • Incremental • Self-assessment Class C • Quick Look • Incremental • Gap analysis Relative: • Cost/Duration • Confidence • Accuracy High Medium Low Rating? Yes No No http: //www. sei. cmu. edu/cmmi/appraisals. html 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 40

Technology: Use Process Appraisal Tools to Capture Appraisal Data and Facilitate Findings l l Checklists Spreadsheets Databases Integrated Systems Diagnostics’ Appraisal Wizard u l pragma Systems Corporation’s process. Max 5 u l http: //www. isd-inc. com/index. asp? q=1036& http: //www. pragmasystems. com/max 5 fin. htm SEI Transition Partner Appraisal Services u http: //www. sei. cmu. edu/collaborating/partnerstech. 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 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 41

8 Steps to Success In CMMI Compliant Process Engineering 1 5 Understand your business processes Build or Refine Your Process Architecture 2 6 Look to the CMMISM for Process Completeness Execute Your Processes 3 7 Look to 4 Framework Standards for Life Cycle Definition Measure Your Results - Modify Processes as Necessary 8 3 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved Look to Supporting Standards for Process Detail Confirm Your Status With Independent Appraisals 3 3 3 42

For More Information. . . Paul R. Croll Computer Sciences Corporation 5166 Potomac Drive King George, VA 22485 -5824 Phone: Fax: e-mail: +1 540. 644. 6224 +1 540. 663. 0276 pcroll@csc. com For IEEE Standards: http: //computer. org/standards/sesc/ http: //computer. org/cspress/CATALOG/st 01110. htm For ISO/IEC Standards: http: //saturne. info. uqam. ca/Labo_Recherche/Lrgl/sc 7/ 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 43

References CMMI -SE/SW/IPPD/SS, V 1. 1, CMMI for Systems Engineering/Software Engineering/Integrated Product and Process Development, and Supplier Sourcing Version 1. 1, CMMISM -SE/SW/IPPD/SS, V 1. 1, Continuous Representation. CMU/SEI-2002 -TR-011, ESC-TR-2002 -011, Carnegie Mellon University, Software Engineering Institute, Pittsburgh, PA, March 2002. IEEE Standard 830 -1998, Recommended Practice for Software Requirements Specifications, Institute of Electrical and Electronics Engineers, Inc. New York, NY, 1998. IEEE Standard 1233 -1998, Guide for Developing System Requirements Specifications, Institute of Electrical and Electronics Engineers, Inc. New York, NY, 1998. 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 44

References - 2 IEEE/EIA Standard 12207. 0 -1996, Industry Implementation of International Standard ISO/IEC 12207: 1995 — (ISO/IEC 12207) Standard for Information Technology —Software life cycle processes, Institute of Electrical and Electronics Engineers, Inc. New York, NY, 1998. IEEE/EIA Standard 12207. 1 -1997, Industry Implementation of International Standard ISO/IEC 12207: 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, 1998. IEEE/EIA Standard 12207. 2 -1997, Industry Implementation of International Standard ISO/IEC 12207: 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. 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 45

References - 3 ISO/IEC 15288: 2002, Systems Engineering — System Life Cycle Processes, ISO/IEC JTC 1/SC 7, 2002. ISO/IEC 19760: 2003, Systems Engineering – A Guide for the application of ISO/IEC 15288 System Life Cycle Processes, ISO/IEC JTC 1/SC 7, 2003. [Singh 97] Raghu Singh, An Introduction to International Standards ISO/IEC 12207, Software Life Cycle Processes, 1997. 16 th Annual Systems and Software Technology Conference – Track 6, IEEE Sponsored Track – 20 April 2004, 1605 -1650 Copyright 2004, Paul R. Croll, All rights reserved 46