Engineering. CMMI for Development V.1.2 Module 3. M03/Engineering/v1.2

Size: px
Start display at page:

Download "Engineering. CMMI for Development V.1.2 Module 3. M03/Engineering/v1.2"

Transcription

1 Engineering CMMI for Development V.1.2 Module 3 M03/Engineering/v1.2

2 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v1.2 2 of 152

3 Module 03 / Engineering - Engineering (REQM, RD) - Building the Product (TS, PI) - Quality in Engineering (VAL, VER) MLx ML5 Process management OID Global Scope Project management Engineering Support CAR ML4 OPP QPM ML3 ML2 OPF OPD+IPPD OT IPM+IPPD RSKM PP PMC SAM RD TS PI VAL VER REQM DAR CM MA PPQA ML1 M03/Engineering/v1.2 3 of 152

4 Global Scope Managing The Project Project and Organizational Support Doing the Work of the Organization Product Development 1 Product Development 2 Managing Quantitatively Improvement Infrastructure M03/Engineering/v1.2 4 of 152

5 Global Scope Understanding the Work (RD, REQM) Managing The Project Project and Organizational Support Doing the Work of the Organization Product Development 1 Product Development 2 Managing Quantitatively Improvement Infrastructure M03/Engineering/v1.2 5 of 152

6 Product Development 1 Establishing and maintaining sets of requirements customer requirements product requirements product-component requirements managing the requirements as the product evolves M03/Engineering/v1.2 6 of 152

7 Product Development 1 Product Development 1 RD REQM Development Management RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate REQM SG 1 Manage M03/Engineering/v1.2 7 of 152

8 Global Scope Performing the Work (TS, PI, VER, VAL) Managing The Project Project and Organizational Support Doing the Work of the Organization Product Development 1 Product Development 2 Managing Quantitatively Improvement Infrastructure M03/Engineering/v1.2 8 of 152

9 Product Development 2 System / Product Development Designing the product and its components Managing the interfaces among the components between the product and the other products Building the components Integrating the components into the product Ensuring the requirements are satisfied Ensuring the product will perform as intended Delivering the product M03/Engineering/v1.2 9 of 152

10 Product Development 2 Product Development 2 TS PI VER VAL Technical Solution Product Integration Verification Validation TS SG 1 Select Product-Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design M03/Engineering/v of 152

11 Product Development 2 Product Development 2 TS PI VER VAL Technical Solution Product Integration Verification Validation PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product M03/Engineering/v of 152

12 Product Development 2 Product Development 2 TS PI VER VAL Technical Solution Product Integration Verification Validation VER SG 1 VER SG 2 VER SG 3 Prepare for Verification Perform Peer Reviews Verify Selected Work Products M03/Engineering/v of 152

13 Product Development 2 Product Development 2 TS PI VER VAL Technical Solution Product Integration Verification Validation VAL SG 1 Prepare for Validation VAL SG 2 Validate Product or Product Components M03/Engineering/v of 152

14 Product Development 2 Relationship to the Waterfall life cycle CMMI PAs are not generally aimed at describing phases of a Waterfall life cycle Engineering PAs are in a tight connection with Waterfall life cycle for product development Engineering PAs do not impose any specific model of applying Waterfall life cycle phases RD, TS, PI, VER, and VAL activities may take place recursively throughout the life cycle M03/Engineering/v of 152

15 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

16 Development Stakeholders' Needs Validated Customer Validated Product, Product-Component, and Interface TS RD Development RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

17 Development RD Development RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate GG 3 Institutionalize a Defined Process Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements M03/Engineering/v of 152

18 Development RD Development RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate GG 3 Institutionalize a Defined Process Customer requirements are refined and elaborated to develop product and productcomponent requirements M03/Engineering/v of 152

19 Development RD Development RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate GG 3 Institutionalize a Defined Process The requirements are analyzed and validated, and a definition of required functionality is developed M03/Engineering/v of 152

20 Development Additional Relevant Terminology Allocated Requirement Requirement that levies all or part of a higher level requirement (functionality, performance) on a lower level architectural or design component Derived Requirement Requirement that is not stated explicitly in the customer requirements, but are inferred from contextual requirements (law, standards, policies, etc.) reqirements needed to specify a product component M03/Engineering/v of 152

21 Development About functional decomposition RD allowes (or even undertakes) performing a functional decomposition of a system being analyzed, or product being developed Motivation: it is very rarely to expect that a project start off with a complete and precise specified knowledge of requirements M03/Engineering/v of 152

22 Development Stakeholders' Needs Validated Customer Validated Product, Product-Component, and Interface RD Development TS RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate M03/Engineering/v of 152

23 Development Stakeholders' Needs RD SG 1 Develop Customer RD SP 1.1 Elicit Needs RD SP 1.2 Develop the Customer Customer M03/Engineering/v of 152

24 Development Stakeholders' Needs Validated Customer Validated Product, Product-Component, and Interface RD Development TS RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate M03/Engineering/v of 152

25 Development Customer RD SG 2 Develop Product TS RD SP 2.1 Establish Product& Product-Component Selected Solutions RD SP 2.2 Allocate Product- Component RD SP 2.3 Identify Interface Product, Product- Component, and Interface M03/Engineering/v of 152

26 Development Stakeholders' Needs Validated Customer Validated Product, Product-Component, and Interface RD Development TS RD SG 1 Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate M03/Engineering/v of 152

27 Development Product, Product- Component, and Interface Customer RD SG 3 Analyze and Validate RD SP 3.1 Establish Operational Concepts & Scenarios RD SP 3.2 Establish Definition of Required Functionality RD SP 3.3 Analyze RD SP 3.5 Validate RD SP 3.4 Analyze to Achieve Balance Validated Customer Validated Product, Product- Component, and Interface M03/Engineering/v of 152

28 Development Specific Goals SG 1 Develop Customer Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements SG 2 Develop Product Customer requirements are refined and elaborated to develop product and product-component requirements SG 3 Analyze and Validate The requirements are analyzed and validated, and a definition of required functionality is developed M03/Engineering/v of 152

29 SG 1 Develop Customer Reqs. SP 1.1 Elicit stakeholder needs, expectations, constraints, and interfaces for all phases of the product life cycle Examples of techniques - include the following Technology demonstrations Interface control working groups Technical control working groups Interim project reviews Questionnaires, interviews, and operational scenarios obtained from end users Operational walkthroughs and end-user task analysis Prototypes and models Brainstorming M03/Engineering/v of 152

30 SG 1 Develop Customer Reqs. SP 1.1 Elicit stakeholder needs, expectations, constraints, and interfaces for all phases of the product life cycle Examples of techniques - include the following Quality Function Deployment Market surveys Beta testing Extraction from sources such as documents, standards, or specifications Observation of existing products, environments, and workflow patterns Use cases Business case analysis Reverse engineering (for legacy products) M03/Engineering/v of 152

31 SG 1 Develop Customer Reqs. SP 1.2 Transform stakeholder needs, expectations, constraints, and interfaces into customer requirements Typical Work Products Customer requirements Customer constraints on the conduct of verification Customer constraints on the conduct of validation M03/Engineering/v of 152

32 SG 2 Develop Product Reqs. SP 2.1 Establish and maintain product and product-component requirements, which are based on the customer requirements Typical Work Products Derived requirements Product requirements Product-component requirements M03/Engineering/v of 152

33 SG 2 Develop Product Reqs. SP 2.2 Allocate the requirements for each product component Typical Work Products Requirement allocation sheets Provisional requirement allocations Design constraints Derived requirements Relationships among derived requirements SP 2.3 Identify interface requirements Typical Work Products Interface requirements Examples of these interfaces include interfaces with test equipment, transportation systems, support systems, and manufacturing facilities M03/Engineering/v of 152

34 SG 3 Analyze and Validate Reqs. SP 3.1 Establish and maintain operational concepts and associated scenarios Typical Work Products Operational concept Product installation, operational, maintenance, and support concepts Disposal concepts Use cases Timeline scenarios New requirements M03/Engineering/v of 152

35 SG 3 Analyze and Validate Reqs. SP 3.2 Establish and maintain a definition of required functionality Typical Work Products Functional architecture Activity diagrams and use cases Object-oriented analysis with services identified M03/Engineering/v of 152

36 SG 3 Analyze and Validate Reqs. SP 3.3 Analyze requirements to ensure that they are necessary and sufficient Typical Work Products defects reports Proposed requirements changes to resolve defects Key requirements Technical performance measures SP 3.4 Analyze requirements to balance stakeholder needs and constraints Typical Work Products Assessment of risks related to requirements M03/Engineering/v of 152

37 SG 3 Analyze and Validate Reqs. SP 3.5 Validate requirements to ensure the resulting product will perform as intended in the user's environment Typical Work Products Record of analysis methods and results Note: SP 3.5 overlaps with VAL it stresses out a necessity to perform validation in RD M03/Engineering/v of 152

38 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

39 Management Tracebility Matrix REQM Management REQM SG 1 Manage GG 2 Institutionalize a Managed Process GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

40 Management are managed and inconsistencies with project plans and work products are identified Tracebility Matrix REQM Management REQM SG 1 Manage GG 2 Institutionalize a Managed Process GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

41 Management Additional Relevant Terminology Tracebility The evidence of an association between a requirement and its source requirement, implementation, and verification M03/Engineering/v of 152

42 Management Tracebility Matrix REQM Management REQM SG 1 Manage GG 2 Institutionalize a Managed Process GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

43 Management REQM SG 1 Manage REQM SP 1.1 Obtain an Understanding of REQM SP 1.2 Obtain Commitment to REQM SP 1.3 Manage Changes REQM SP 1.4 Maintain Bidirectional Tracebility of REQM SP 1.5 Identify Inconsistencies Between Project Work and Reqs. Tracebility Matrix M03/Engineering/v of 152

44 Management Specific Goals SG 1 Manage are managed and inconsistencies with project plans and work products are identified M03/Engineering/v of 152

45 SG 1 Manage SP 1.1 Develop an understanding with the requirements providers on the meaning of the requirements Typical Work Products Lists of criteria for distinguishing appropriate requirements providers Criteria for evaluation and acceptance of requirements Results of analyses against criteria An agreed-to set of requirements M03/Engineering/v of 152

46 SG 1 Manage SP 1.1 Develop an understanding with the requirements providers on the meaning of the requirements Examples of acceptance criteria include the following: Clearly and properly stated Complete Consistent with each other Uniquely identified Appropriate to implement Verifiable (testable) Traceable M03/Engineering/v of 152

47 SG 1 Manage SP 1.2 Obtain commitment to the requirements from the project participants Typical Work Products impact assessments Documented commitments to requirements and requirements changes M03/Engineering/v of 152

48 SG 1 Manage SP 1.3 Manage changes to the requirements as they evolve during the project Typical Work Products status database decision database M03/Engineering/v of 152

49 SG 1 Manage SP 1.4 Maintain bidirectional traceability among the requirements and the work products Typical Work Products Note traceability matrix tracking system decide what level of granularity is appropriate for a traceability matrix» too much detail can become overwhelming» too little detail makes the matrix worthless M03/Engineering/v of 152

50 SG 1 Manage SP 1.5 Identify inconsistencies between the project plans and work products and the requirements Typical Work Products Documentation of inconsistencies including sources, conditions, and rationale Corrective actions M03/Engineering/v of 152

51 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

52 Technical Solution Alternative Designs and Evaluation Criteria Design Detail & Documentation Developed Product RD TS PI DAR Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

53 Technical Solution TS Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process Product or product-component solutions are selected from alternative solutions M03/Engineering/v of 152

54 Technical Solution TS Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process Product or product-component designs are developed M03/Engineering/v of 152

55 Technical Solution TS Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process Product components, and associated support documentation, are implemented from their designs M03/Engineering/v of 152

56 Technical Solution Additional Relevant Terminology Product-related life-cycle processes Processes associated with a product throughout one or more phases of its life Sustainment The processes used to ensure that product can be utilized operationally by its end users / customers M03/Engineering/v of 152

57 Technical Solution Additional Relevant Terminology Operational concept Description of the way in which component is used Operational scenario A scenario of events and calls which shows how the component will be used Tech data package Set of documents appropriate to the product Architecture and product description and characteristics Interface requirements Physical characteristics and constraints M03/Engineering/v of 152

58 Technical Solution Alternative Designs and Evaluation Criteria Design Detail & Documentation Developed Product RD TS PI DAR Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

59 SAM Technical Solution RD TS SG 1 Select Product- Component Solutions DAR TS SP 1.1 Develop Alternative Solutions and Selection Criteria TS SP 1.2 Select Product- Component Solutions Alternative Solutions Selection Criteria New Technology Evaluations Selection Decisions Compliant with M03/Engineering/v of 152

60 Technical Solution Alternative Designs and Evaluation Criteria Design Detail & Documentation Developed Product RD TS PI DAR Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

61 RD Technical Solution TS SG 2 Develop the Design PI Selection Criteria Make/Buy Analysis TS SP 2.1 Develop the Product or Product Component TS SP 2.2 Establish a Technical Data Package Tech Data Package I/F Design Documentation I/F Specification I/F Control Documents Product Architecture Product Component Designs TS SP 2.3 Design Interfaces Using Criteria TS SP 2.4 Perform Make, Buy, or Reuse Analyses M03/Engineering/v of 152 PI

62 Technical Solution Alternative Designs and Evaluation Criteria Design Detail & Documentation Developed Product RD TS PI DAR Technical Solution TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

63 Technical Solution TS SG 3 Implement the Product Design TS SP 3.1 Implement the Design TS SP 3.2 Develop Product Support Documentation Parts Fabricated Software Coded Data Documented Processes Documented Facilities Constructed End-User Training Materials User's Manual Operator's Manual Maintenance Manual Online Help M03/Engineering/v of 152

64 Specific Goals Technical Solution SG 1 Select Product-Component Solutions Product or product-component solutions are selected from alternative solutions SG 2 Develop the Design Product or product-component designs are developed SG 3 Implement the Product Design Product components, and associated support documentation, are implemented from their designs M03/Engineering/v of 152

65 SG 1 Select Prod-Comp. Solns. SP 1.1 Develop alternative solutions and selection criteria Typical Work Products Alternative solution screening criteria Evaluations of new technologies Alternative solutions Selection criteria for final selection Evaluation reports of COTS products M03/Engineering/v of 152

66 SG 1 Select Prod-Comp. Solns. SP 1.2 Select the product component solutions that best satisfy the criteria established Typical Work Products Product-component selection decisions and rationale Documented relationships between requirements and product components Documented solutions, evaluations, and rationale M03/Engineering/v of 152

67 SG 2 Develop the Design SP 2.1 Develop a design for the product or product component Typical Work Products Product architecture Product-component designs Examples of techniques and methods that facilitate effective design include the following: Prototypes Structural models Object-oriented design Essential systems analysis Entity relationship models Design reuse Design patterns M03/Engineering/v of 152

68 SG 2 Develop the Design SP 2.2 Establish and maintain a technical data package Typical Work Products Technical data package M03/Engineering/v of 152

69 SG 2 Develop the Design SP 2.3 Design product-component interfaces using established criteria Typical Work Products Interface design specifications Interface control documents Interface specification criteria Rationale for selected interface design M03/Engineering/v of 152

70 SG 2 Develop the Design SP 2.4 Evaluate whether the product components should be developed, purchased, or reused based on established criteria Typical Work Products Criteria for design and product-component reuse Make-or-buy analyses Guidelines for choosing COTS product components M03/Engineering/v of 152

71 SG 3 Implement the Prod. Design SP 3.1 Implement the designs of the product components Typical Work Products Implemented design Examples of software coding criteria include the following: Modularity Clarity Simplicity Structured (e.g., no GOTOs, one entrance, and one exit) Maintainability M03/Engineering/v of 152

72 SG 3 Implement the Prod. Design SP 3.2 Develop and maintain the end-use documentation Typical Work Products End-user training materials User's manual Operator's manual Maintenance manual Online help When documentation may need to be revised change Design changes are made Product changes are made Documentation errors are identified Workaround fixes are identified M03/Engineering/v of 152

73 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

74 Product Integration Integration Sequence Integration Procedures and Criteria Integration Environment Assemblies Sub-assemblies TS DAR PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

75 Product Integration PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process Preparation fro product integration is conducted M03/Engineering/v of 152

76 Product Integration PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process The product-component interfaces, both internal and external, are compatible M03/Engineering/v of 152

77 Product Integration PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process Verified product components are assembled and the integrated, verified, and validated product is dilivered M03/Engineering/v of 152

78 Product Integration Integration Sequence Integration Procedures and Criteria Integration Environment Assemblies Sub-assemblies TS DAR PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

79 DAR Product Integration PI SG 1 Prepare for Product Integration PI SP 1.1 Determine Integration Sequence PI SP 1.2 Establish the Product Integration Environment PI SP 1.3 Establish Product Integration Procedures and Criteria Integration Sequence Integration Procedures and Criteria Integration Environment TS M03/Engineering/v of 152

80 Product Integration Integration Sequence Integration Procedures and Criteria Integration Environment Assemblies Sub-assemblies TS DAR PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

81 Product Integration PI SG 2 Ensure Interface Compatibiliy PI SP 2.1 Review Interface Descriptions for Completeness PI SP 2.2 Manage Interfaces Integration Sequence Integration Procedures and Criteria Integration Environment M03/Engineering/v of 152 TS

82 Product Integration Integration Sequence Integration Procedures and Criteria Integration Environment Assemblies Sub-assemblies TS DAR PI Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Ensure Interface Compatibiliy PI SG 3 Assemble Product Components and Diliver the Product GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

83 PI SP 3.1 Confirm Readiness of Product Components for Integrat. Product Integration PI SG 3 Assemble Product Components and Diliver the Product PI SP 3.2 Assemble Product Components Integration Sequence `Integration Procedures and Criteria Integration Environment PI SP 3.3 Evaluate Assembled Product Components Assemblies Sub-assemblies PI SP 3.4 Package and Deliver the Product or Product Compon. TS M03/Engineering/v of 152

84 Specific Goals Product Integration SG 1 Prepare for Product Integration Preparation for product integration is conducted SG 2 Ensure Interface Compatibility The product-component interfaces, both internal and external, are compatible SG 3 Assemble Product Components and Deliver the Product Verified product components are assembled and the integrated, verified, and validated product is delivered M03/Engineering/v of 152

85 SG 1 Prepare for Product Integr. SP 1.1 Determine the product-component integration sequence Typical Work Products Product integration sequence Rationale for selecting or rejecting integration sequences SP 1.2 Establish and maintain the environment needed to support the integration of the product components Typical Work Products Verified environment for product integration Support documentation for the product integration environment M03/Engineering/v of 152

86 SG 1 Prepare for Product Integr. SP 1.3 Establish and maintain procedures and criteria for integration of the product components Typical Work Products Product integration procedures Product integration criteria M03/Engineering/v of 152

87 SG 2 Ensure Interface Compat. SP 2.1 Review interface descriptions for coverage and completeness Typical Work Products Note Categories of interfaces List of interfaces per category Mapping of the interfaces to the product components and product integration environment SP 2.1 describes a VER / VAL type activity it is slightly redundant with VER / VAL stresses out a necessity to perform VER / VAL in SG2 (there are good reasons) M03/Engineering/v of 152

88 SG 2 Ensure Interface Compat. SP 2.2 Manage internal and external interface definitions, designs, and changes for products and product components Typical Work Products Table of relationships among the product components and the external environment (e.g., main power supply, fastening product, computer bus system) Table of relationships between the different product components List of agreed-to interfaces defined for each pair of product components, when applicable Reports from the interface control working group meetings Action items for updating interfaces Application program interface (API) Updated interface description or agreement M03/Engineering/v of 152

89 SG 3 Assemble Product Components and Deliver the Product SP 3.1 Confirm, prior to assembly, that each product component required to assemble the product has been properly identified, functions according to its description, and that the product-component interfaces comply with the interface descriptions Typical Work Products Acceptance documents for the received product components Delivery receipts Checked packing lists Exception reports Waivers M03/Engineering/v of 152

90 SG 3 Assemble Product Components and Deliver the Product SP 3.2 Assemble product components according to the product integration sequence and available procedures Typical Work Products Assembled product or product components M03/Engineering/v of 152

91 SG 3 Assemble Product Components and Deliver the Product SP 3.3 Evaluate assembled product components for interface compatibility Typical Work Products Exception reports Interface evaluation reports Product integration summary reports Example results include the following: Any adaptation required to the integration procedure Any change to the product configuration (spare parts, new release) Evaluation procedure deviations M03/Engineering/v of 152

92 SG 3 Assemble Product Components and Deliver the Product SP 3.4 Package the assembled product or product component and deliver it to the appropriate customer Typical Work Products Packaged product or product components Delivery documentation M03/Engineering/v of 152

93 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

94 Verification Corrective Actions VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

95 Verification VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process Preparation for verification is conducted M03/Engineering/v of 152

96 Verification VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process Peer reviews are performed on selected work products M03/Engineering/v of 152

97 Verification VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process Selected work products are verified against their specified requirements M03/Engineering/v of 152

98 Verification Corrective Actions VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

99 Verification VER SG 1 Prepare for Verification VER SP 1.1 Select Work Products for Verification VER SP 1.2 Establish the Verification Environment VER SP 1.3 Establish Verification Procedures and Criteria Verification Environment Verification Procedures and Criteria List of Work Products Selected for Verification M03/Engineering/v of 152

100 Verification Corrective Actions VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

101 Verification VER SG 2 VER SP 2.1 Prepare For Peer Reviews VER SP 2.2 Conduct Peer Reviews Perform Peer Reviews VER SP 2.3 Analyze Peer Review Data Requirement for Data Collection Entry and Exit Criteria Peer Review Plan Review Results Review Issues Review Data Action Items M03/Engineering/v of 152

102 Verification Corrective Actions VER Verification VER SG 1 Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

103 Verification VER SG 3 Verify Selected Work Products VER SP 3.1 Perform Verification VER SP 3.2 Analyze Verification Results Verification Results Deficiencies Verification Data Corrective Actions M03/Engineering/v of 152

104 Specific Goals Verification SG 1 Prepare for Verification Preparation for verification is conducted. SG 2 Perform Peer Reviews Peer reviews are performed on selected work products. SG 3 Verify Selected Work Products Selected work products are verified against their specified requirements M03/Engineering/v of 152

105 SG 1 Prepare for Verification SP 1.1 Select the work products to be verified and the verification methods that will be used for each Typical Work Products Lists of work products selected for verification Verification methods for each selected work product Examples of verification methods include the following: Path coverage testing Load, stress, and performance testing Decision-table-based testing Functional-decomposition-based testing Test-case reuse Acceptance tests M03/Engineering/v of 152

106 SG 1 Prepare for Verification SP 1.2 Establish and maintain the environment needed to support verification Typical Work Products Verification environment SP 1.3 Establish and maintain verification procedures and criteria for the selected work products Typical Work Products Verification procedures Verification criteria M03/Engineering/v of 152

107 SG 2 Perform Peer Reviews SP 2.1 Prepare for peer reviews of selected work products Typical Work Products Peer review schedule Peer review checklist Entry and exit criteria for work products Criteria for requiring another peer review Peer review training material Selected work products to be reviewed Examples of types of peer reviews include the following: Inspections Structured walkthroughs Active reviews M03/Engineering/v of 152

108 SG 2 Perform Peer Reviews SP 2.1 Prepare for peer reviews of selected work products Note Peer reviews are covered by IEEE Std IEEE Standard for Software Reviews» the standard defines five types of software reviews, together with procedures required for the execution of each review type M03/Engineering/v of 152

109 SG 2 Perform Peer Reviews SP 2.2 Conduct peer reviews on selected work products and identify issues resulting from the peer review Typical Work Products Peer review results Peer review issues Peer review data SP 2.3 Analyze data about preparation, conduct, and results of the peer reviews Typical Work Products Peer review data Peer review action items M03/Engineering/v of 152

110 SG 3 Verify Selected Work Prods SP 3.1 Perform verification on the selected work products Typical Work Products Verification results Verification reports Demonstrations As-run procedures M03/Engineering/v of 152

111 SG 3 Verify Selected Work Prods SP 3.2 Analyze the results of all verification activities Typical Work Products Analysis report (such as statistics on performances, causal analysis of nonconformances, comparison of the behavior between the real product and models, and trends) Trouble reports Change requests for the verification methods, criteria, and environment M03/Engineering/v of 152

112 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

113 Validation RD Conformance Deficiencies VAL Validation VAL SG 1 Prepare for Validation VAL SG 2 Validate Product or Product Components GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

114 Validation VAL Validation VAL SG 1 Prepare for Validation VAL SG 2 Validate Product or Product Components GG 3 Institutionalize a Defined Process Preparation for validation is conducted M03/Engineering/v of 152

115 Validation VAL Validation VAL SG 1 Prepare for Validation VAL SG 2 Validate Product or Product Components GG 3 Institutionalize a Defined Process The product or product components are validated to ensure that they are suitable for use in their intended operating environment M03/Engineering/v of 152

116 Validation RD Conformance Deficiencies VAL Validation VAL SG 1 Prepare for Validation VAL SG 2 Validate Product or Product Components GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

117 Validation RD VAL SG 1 Prepare for Validation VAL SP 1.1 Select Products for Validation VAL SP 1.2 Establish the Validation Environment VAL SP 1.3 Establish Validation Procedures and Criteria Validation Environment and Criteria Validation Procedures and Criteria List of Products and Product Components Selected for Validation M03/Engineering/v of 152

118 Validation RD Conformance Deficiencies VAL Validation VAL SG 1 Prepare for Validation VAL SG 2 Validate Product or Product Components GG 3 Institutionalize a Defined Process M03/Engineering/v of 152

119 Validation RD VAL SG 2 Validate Product or Product Components VAL SP 2.1 Perform Validation VAL SP 2.1 Analyze Validation Results Validation Reports Validation Results Cross Reference Matrix As Run Procedures Log Operational Demonstrations Validation Deficiency Reports Validation Issues Procedure Change Request M03/Engineering/v of 152

120 Specific Goals Validation SG 1 Prepare for Validation Preparation for validation is conducted. SG 2 Validate Product or Product Components The product or product components are validated to ensure that they are suitable for use in their intended operating environment. M03/Engineering/v of 152

121 SG 1 Prepare for Validation SP 1.1 Select products and product components to be validated and the validation methods that will be used for each Typical Work Products Lists of products and product components selected for validation Validation methods for each product or product component for performing validation for each product or product component Validation constraints for each product or product component M03/Engineering/v of 152

122 SG 1 Prepare for Validation SP 1.1 Select products and product components to be validated and the validation methods that will be used for each Note Incremental validation should be planned and taken place along the way» according to test best practices» system test and other end-of-life-cycle activities should not be relied on to find all defects» end-of-development test simply confirms confidence in the product M03/Engineering/v of 152

123 SG 1 Prepare for Validation SP 1.2 Establish and maintain the environment needed to support validation Typical Work Products Validation environment M03/Engineering/v of 152

124 SG 1 Prepare for Validation SP 1.3 Establish and maintain procedures and criteria for validation Typical Work Products Validation procedures Validation criteria Test and evaluation procedures for maintenance, training, and support Examples of sources for validation criteria include the following: Product and product-component requirements Standards Customer acceptance criteria Environmental performance Thresholds of performance deviation M03/Engineering/v of 152

125 SG 2 Validate Product or Product Components SP 2.1 Perform validation on the selected products and product components Typical Work Products Validation reports Validation results Validation cross-reference matrix As-run procedures log Operational demonstrations SP 2.2 Analyze the results of the validation activities and identify issues Typical Work Products Validation deficiency reports Validation issues Procedure change request M03/Engineering/v of 152

126 Agenda Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

127 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis Design Implementation Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

128 Strategy SEP vs. CMMI Engineering Engineering Analysis The System Engineering Process Life Cycle Design Implementation Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

129 Strategy SEP vs. CMMI Engineering Conceptual Analysis Design The System Engineering Process Life Cycle Design Implementation Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

130 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis Implementation Design Design Implementation Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

131 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle System Integration Analysis Verification Design Implementation Validation Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

132 SEP vs. CMMI Engineering Strategy Engineering Analysis The System Engineering Process Life Cycle Conceptual Design Design Implementation Design System Integration Implementation Installation Verification Validation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

133 SEP vs. CMMI Engineering Strategy Engineering Analysis The System Engineering Process Life Cycle Design Implementation Installation Verification Exploitation & Evolution Validation Decommissioning M03/Engineering/v of 152

134 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis RD Design Development RD SG 1 Implementation Installation Develop Customer RD SG 2 Develop Product RD SG 3 Analyze and Validate Exploitation & Evolution Decommissioning M03/Engineering/v of 152

135 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis TS Design Technical Solution Implementation TS SG 1 Select Product- Component Solutions TS SG 2 Develop the Design TS SG 3 Implement the Product Design Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

136 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis PI Design Product Integration PI SG 1 Prepare for Product Integration PI SG 2 Implementation PI SG 3 Ensure Interface Assemble Product Compatibiliy Components and Diliver the Product Installation Exploitation & Evolution Decommissioning M03/Engineering/v of 152

137 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis VER Design Verification Implementation VER SG 1 Installation Prepare for Verification VER SG 2 Perform Peer Reviews VER SG 3 Verify Selected Work Products Exploitation & Evolution Decommissioning M03/Engineering/v of 152

138 SEP vs. CMMI Engineering Strategy The System Engineering Process Life Cycle Analysis VAL Design Validation Implementation VAL SG 1 Installation Prepare for Validation VAL SG 2 Validate Product or Product Components Exploitation & Evolution Decommissioning M03/Engineering/v of 152

139 SEP vs. CMMI Engineering The Management Process in System Eng. REQM Management Strategy Planning Phase Management Strategy Phase Planning Analysis & Commitment Engineering Analysis Exploitation & Evolution Decommissioning Phase Control Analysis & Phase Commitment M03/Engineering/v of 152

140 Summary Global scope RD Development REQM Product Development 1 (RD, Management REQM) TS PI VER VAL Product Development 2 (TS, PI, VER, VAL) Technical Solution Product Integration Verification Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

141 Summary Global scope RD Development REQM Management TS PI VER VAL Technical Solution RD SG1 Develop Customer RD SG2 Develop Product RD SG3 Analyze and Validate Product Integration Verification Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

142 Summary Global scope RD Development REQM Management TS Technical Solution PI VER VAL Product Integration REQM SG1 Manage Verification Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

143 Summary Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER VAL Verification TS SG1 Select Product-Component Solutions TS SG2 Develop The Design TS SG3 Imlement The Product Design Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

144 Summary Global scope RD Development REQM Management TS Technical Solution PI Product Integration VER Verification VAL Validation PI SG1 Prepare for Product Integration PI SG2 Ensure Interface Compatibility PI SG3 Assemble Product Components and Diliver the Product SE Process vs. CMMI Engineering M03/Engineering/v of 152

145 Global scope RD Summary Development REQM Management TS PI VER VAL Technical Solution Product Integration Verification Validation SE Process vs. CMMI Engineering VER SG1 Prepare for Verification VER SG2 Perform Peer Reviews VER SG3 Verify Selected Work Products M03/Engineering/v of 152

146 Summary Global scope RD Development REQM Management TS PI VER VAL Technical Solution VAL SG1 Prepare for Validation VAL SG2 Validate Selected Work Products Product Integration Verification Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

147 Summary Global scope RD Development REQM Management TS PI VER VAL Technical Solution The System Engineering Process (Life Cycle) Engineering Conceptual Product Design Integration and Implementation Design System Integration Verification, Validation The Management Process in System Engineering Validation SE Process vs. CMMI Engineering M03/Engineering/v of 152

148 Questions? M03/Engineering/v of 152

149 Review Questions 1. List the PAs belonging to Product Development List the PAs belonging to Product Development What is the purpose of RD? 4. What are the specific goals of RD? 5. Describe the notion of "allocated requirement". 6. Describe the notion of "derived requirement". 7. What are the specific practicies for RD SG3: "Analyze and Validate "? 8. What is the purpose of REQM? 9. What are the specific goals of REQM? 10. Describe the notion of "requirement traceability". 11. What are the specific practicies for REQM SG1: "Manage "? M03/Engineering/v of 152

150 Review Questions 12. What is the purpose of TS? 13. What are the specific goals of TS? 14. Describe the notion of "tech data package". 15. Discuss the differences between "operational scenario" and "operational concept". 16. What are the specific practicies for TS SG2: "Develop The Design"? 17. What is the purpose of PI? 18. What are the specific goals of PI? 19. What are the specific practicies for PI SG1: "Prepare for Product Integration"? 20. What are the specific practicies for PI SG2: "Ensure Interface Compatibility"? M03/Engineering/v of 152

151 Review Questions 21. What is the purpose of VER? 22. What are the specific goals of VER? 23. What are the specific practicies for VER SG2: "Perform Peer Reviews"? 24. What is the purpose of VAL? 25. What are the specific goals of VAL? 26. What are the specific practicies for VAL SG2: "Validate Product and Product Components"? 27. Discuss the nature of relationship between RD and TS. 28. Discuss the nature of relationship between RD and TS. 29. Discuss the nature of relationship between TS and PI. 30. Discuss the nature of relationship between PI and DAR. M03/Engineering/v of 152

152 Review Questions 31. Discuss the impact of RD on Engineering in System Engineering Process (SEP). 32. Which phases in SEP Life Cycle covers TS? 33. Which phases in SEP Life Cycle covers PI? 34. Which phases in SEP Life Cycle covers VER? 35. Which phases in SEP Life Cycle covers VAL? 36. Discuss the impact of REQM on SEP and Managament of SEP. M03/Engineering/v of 152

153 Engineering CMMI for Development V.1.2 Module 3 M03/Engineering/v1.2

A Global Overview of The Structure

A Global Overview of The Structure A Global Overview of The Structure CMMI for Development V.1.2 Module 2 M02/GO/v1.2 Agenda Overview of CMMI General Structure of CMMI CMMI Model Representations Generic Goals and Practices CMMI by PAs and

More information

CMMI for Technical Staff

CMMI for Technical Staff CMMI for Technical Staff SES CMMI Training Series April 7, 2009 Audio Conference #: Dial - 1-877-760-2042 Pass code - 147272 SM SEI and CMM Integration are service marks of Carnegie Mellon University CMM

More information

CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide

CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide processlabs CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide CMMI-DEV V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAR - Causal Analysis and Resolution...

More information

DORNERWORKS QUALITY SYSTEM

DORNERWORKS QUALITY SYSTEM DORNERWORKS QUALITY SYSTEM ALIGNMENT WITH CMMI INTRODUCTION Since its beginning, DornerWorks has had quality as one of our main goals. We have delivered solutions for over a dozen aircraft, including several

More information

CMMI for Acquisition Quick Reference

CMMI for Acquisition Quick Reference AGREEMENT MANAGEMENT PROJECT MANAGEMENT (ML2) The purpose of Agreement Management (AM) is to ensure that the supplier and the acquirer perform according to the terms of the supplier agreement. SG 1 The

More information

CMMI Version 1.2. Model Changes

CMMI Version 1.2. Model Changes Pittsburgh, PA 15213-3890 CMMI Version 1.2 Model Changes SM CMM Integration, IDEAL, and SCAMPI are service marks of Carnegie Mellon University. Capability Maturity Model, Capability Maturity Modeling,

More information

USAF Software Technology Support Center (STSC) STSC SPI Help Desk COM , DSN

USAF Software Technology Support Center (STSC) STSC SPI Help Desk COM , DSN This mapping was performed by the For all your Software Improvement (SPI) needs call the USAF Software Technology Support Center (STSC) STSC SPI Help Desk COM 801.777.7214, DSN 777.7214 E-mail: larry.w.smith@hill.af.mil

More information

CMMI for Services Quick Reference

CMMI for Services Quick Reference CAPACITY AND AVAILABILITY MANAGEMENT PROJECT & WORK MGMT (ML3) The purpose of Capacity and Availability Management (CAM) is to ensure effective service system performance and ensure that resources are

More information

8. CMMI Standards and Certifications

8. CMMI Standards and Certifications Computer Science and Software Engineering University of Wisconsin - Platteville 8. CMMI Standards and Certifications Yan Shi SE 3730 / CS 5730 Lecture Notes This note is partially based on http://www.sei.cmu.edu/reports/10tr033.pdf

More information

CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide

CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide processlabs CMMI-SVC V1.3 CMMI for Services Version 1.3 Quick Reference Guide CMMI-SVC V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAM - Capacity and Availability Management...

More information

9/24/2011 Sof o tw t a w re e P roc o e c s e s s s Mo M d o e d l e s l 1 Wh W a h t t i s i s a Pr P oc o ess s 2 1

9/24/2011 Sof o tw t a w re e P roc o e c s e s s s Mo M d o e d l e s l 1 Wh W a h t t i s i s a Pr P oc o ess s 2 1 Software Process Models 1 What is a Process 2 1 What is a Process? Given input, transforms it into output Consist of a set of activities Ordering among the activities (a partial order) Software Process

More information

Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination)

Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination) Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination) Neil Potter The Process Group neil@processgroup.com 1 Agenda Summary of PMBOK, CMMI

More information

Highlights of CMMI and SCAMPI 1.2 Changes

Highlights of CMMI and SCAMPI 1.2 Changes Highlights of CMMI and SCAMPI 1.2 Changes Presented By: Sandra Cepeda March 2007 Material adapted from CMMI Version 1.2 and Beyond by Mike Phillips, SEI and from Sampling Update to the CMMI Steering Group

More information

MTAT Software Engineering Management

MTAT Software Engineering Management MTAT.03.243 Software Engineering Management Lecture 16: Software Process Assessment Dietmar Pfahl Spring 2013 email: dietmar.pfahl@ut.ee Structure of Lecture 16 Process Assessment Origins: CMM & CMMI Process

More information

Strategies for Transitioning to CMMI-SVC

Strategies for Transitioning to CMMI-SVC Strategies for Transitioning to CMMI-SVC CMMI Technology Conference and User Group 16-19 November 2009 Rick Hefner, Ph.D. Northrop Grumman Corporation rick.hefner@ngc.com Topics The Business Case for Adopting

More information

CC and CMMI. An Approach to Integrate CC with Development

CC and CMMI. An Approach to Integrate CC with Development CC and CMMI An Approach to Integrate CC with Development Wolfgang Peter TÜV Informationstechnik GmbH -TÜViT - Contents 1. Status Quo 2. CMMI for Development 3. Striking Analogies 4. Combining Standards

More information

SOFTWARE ENGINEERING SOFTWARE PROCESS. Saulius Ragaišis.

SOFTWARE ENGINEERING SOFTWARE PROCESS. Saulius Ragaišis. SOFTWARE ENGINEERING SOFTWARE PROCESS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and provide an example,

More information

CMMI for Services (CMMI -SVC) Process Areas

CMMI for Services (CMMI -SVC) Process Areas CMMI for Services (CMMI -SVC) Process Areas SES CMMI Training Series August27, 2009 Dial - 1-877-760-2042 Pass code - 147272 SM SEI and CMM Integration are service marks of Carnegie Mellon University CMM

More information

Software technology 3. Process improvement models. BSc Course Dr. Katalin Balla

Software technology 3. Process improvement models. BSc Course Dr. Katalin Balla Software technology 3. Process improvement models BSc Course Dr. Katalin Balla Contents Process improvement models. Popular SPI models: CMM, SPICE, CMMI The Personal Software Process (PSP) and the Team

More information

Bill Smith, CEO Leading Edge Process Consultants LLC

Bill Smith, CEO Leading Edge Process Consultants LLC 9 th Annual National Defense Industrial Association CMMI Technology Conference and User Group November 18, 2009 Denver, Colorado, USA Bill Smith, CEO Leading Edge Process Consultants LLC www.cmmitraining.com

More information

Relationship between CMMI Maturity Levels and ISO/IEC Processes Capability Profiles

Relationship between CMMI Maturity Levels and ISO/IEC Processes Capability Profiles Relationship between CMMI Maturity Levels and ISO/IEC 15504 Processes Capability Profiles Antanas Mitašiūnas, Saulius Ragaišis Faculty of Mathematics and Informatics, Vilnius University, Lithuania Baltic

More information

The Rational Unified Process and the Capability Maturity Model Integrated Systems/Software Engineering

The Rational Unified Process and the Capability Maturity Model Integrated Systems/Software Engineering The Rational Unified Process and the Capability Maturity Model Integrated Systems/Software Engineering Brian Gallagher Lisa Brownsword SM CMMI and CMM Integration are service marks of Carnegie Mellon University.

More information

Software Process Assessment

Software Process Assessment Software Process Assessment A method of determining the effectiveness of the software process with a goal towards improving the process. Software Process Assessment Approaches Capability Maturity Model

More information

Lesson Learned from Cross Constellations and Multi Models Process Improvement Initiatives

Lesson Learned from Cross Constellations and Multi Models Process Improvement Initiatives Lesson Learned from Cross Constellations and Multi Models Process Improvement Initiatives Kobi Vider Picker K.V.P Consulting Kobi.Vider@hotmail.com +972522946676 Conceptual Structure and Elements Dashboards

More information

The Quality Paradigm. Quality Paradigm Elements

The Quality Paradigm. Quality Paradigm Elements The Quality Paradigm We shall build good ships here; at a profit if we can, at a loss if we must, but always good ships. motto used at Newport News Shipbuilding Quality Paradigm Elements Defining the nature

More information

Software Quality Assurance Framework (SQA) Yujuan Dou 窦玉娟 2008/11/28

Software Quality Assurance Framework (SQA) Yujuan Dou 窦玉娟 2008/11/28 Software Quality Assurance Framework (SQA) Yujuan Dou 窦玉娟 2008/11/28 Whole Course Plan Software Quality Assurance Framework Test Requirement Test Planning Test Case Design Test Execution and Defect Management

More information

CMMI V2.0 MODEL AT-A-GLANCE. Including the following views: Development Services Supplier Management. CMMI V2.0 outline BOOKLET FOR print.

CMMI V2.0 MODEL AT-A-GLANCE. Including the following views: Development Services Supplier Management. CMMI V2.0 outline BOOKLET FOR print. CMMI V.0 MODEL AT-A-GLANCE Including the following views: Development Services Supplier Management CMMI V.0 outline BOOKLET FOR print.indd CMMI V.0 An Integrated Product Suite Designed to meet the challenges

More information

The Issue of Performance Why Do you need a Maturity Level 5. Achieving the Organizational Business Objectives Through Optimized Operational Processes

The Issue of Performance Why Do you need a Maturity Level 5. Achieving the Organizational Business Objectives Through Optimized Operational Processes The Issue of Performance Why Do you need a Maturity Level 5 Achieving the Organizational Business Objectives Through Optimized Operational Processes CMMI ML 4 & 5 PAs Recap Quantitative Project Management

More information

What s New in V1.3. Judah Mogilensky Process Enhancement Partners, Inc.

What s New in V1.3. Judah Mogilensky Process Enhancement Partners, Inc. What s New in V1.3 Judah Mogilensky Process Enhancement Partners, Inc. 1 Acknowledgements This presentation is based, in part, on the CMMI V1.3 released materials, as well as on several presentations by

More information

Chapter 26 Process improvement

Chapter 26 Process improvement Chapter 26 Process improvement 1 Topics covered The process improvement process Process measurement Process analysis Process change The CMMI process improvement framework 2 Process improvement Many software

More information

Patricia A Eglin David Consulting Group

Patricia A Eglin David Consulting Group CMMI-SVC: What you need to know before you buy it Patricia A Eglin David Consulting Group Agenda What is a service? Process Areas/Continuous Representation Staged Representation CMMI-DEV versus CMMI-SVC

More information

Quest 2015 Webinar Series:

Quest 2015 Webinar Series: presents the Quest 2015 Webinar Series: You Want to Use SCRUM, You Are Told To Use CMMI-- How They Can Work Together Elegantly WEBINAR SERIES WEBINAR SERIES www.qaiquest.org/2015 Featuring Neil Potter

More information

Implementing Systems Engineering Processes to Balance Cost and Technical Performance

Implementing Systems Engineering Processes to Balance Cost and Technical Performance Implementing Systems Engineering Processes to Balance Cost and Technical Performance Dr. Mary Anne Herndon Transdyne Corporation Sandra Salars MEI Technologies October 26, 2005 Dr. Mary Anne Herndon 858-271-1615

More information

Measuring the Impact of RD and REQM CMMI Process Areas

Measuring the Impact of RD and REQM CMMI Process Areas Measuring the Impact of RD and REQM CMMI Process Areas Aldo Dagnino Director of Manufacturing Solutions Agenda Introduction CMMI Appraisal Results Methodology to Measure economic Benefits Conclusions Why

More information

version NDIA CMMI Conf 3.5 SE Tutorial RE - 1

version NDIA CMMI Conf 3.5 SE Tutorial RE - 1 Requirements Engineering SE Tutorial RE - 1 What Are Requirements? Customer s needs, expectations, and measures of effectiveness Items that are necessary, needed, or demanded Implicit or explicit criteria

More information

Generating Supportive Hypotheses

Generating Supportive Hypotheses Generating Supportive Hypotheses in Introducing Formal Methods using a Software Process Improvement Model S. KUSAKABE, H. LIN, Y. OMORI, and K. ARAKI Grad. Sch. of Info. Sci. & Elec. Eng., Kyushu University

More information

Update Observations of the Relationships between CMMI and ISO 9001:2000

Update Observations of the Relationships between CMMI and ISO 9001:2000 Update Observations of the Relationships between CMMI and ISO 9001:2000 September September 14, 14, 2005 2005 ASQ Section 509 - ISO 9000 Users Group Page 1 This presentation summaries points made and topics

More information

System Engineering Process Improvement using the CMMI in Large Space Programs

System Engineering Process Improvement using the CMMI in Large Space Programs SYSTEMS MISSILES & SPACE GROUP System Engineering Process Improvement using the CMMI in Large Space Programs Revital Goldberg, Sarit Assaraf Israel Aerospace Industries 13 th Annual System Engineering

More information

SCAMPI V1.1 Method Overview

SCAMPI V1.1 Method Overview Pittsburgh, PA 15213-3890 SCAMPI V1.1 Method Overview Charles J. Ryan Sponsored by the U.S. Department of Defense 2005 by Carnegie Mellon University Objectives Review key characteristics of SCAMPI. Describe

More information

This chapter illustrates the evolutionary differences between

This chapter illustrates the evolutionary differences between CHAPTER 6 Contents An integrated approach Two representations CMMI process area contents Process area upgrades and additions Project management concepts process areas Project Monitoring and Control Engineering

More information

Using the Equity in AS9100C to Implement CMMI-DEV Maturity Level 3

Using the Equity in AS9100C to Implement CMMI-DEV Maturity Level 3 CMMI Implementations in Small & Medium Organizations Using the Equity in AS9100C to Implement CMMI-DEV Maturity Level 3 Dr. Mary Anne Herndon Sandra Salars MEI Technologies, Inc. 1 Agenda AS9100C Overview

More information

Comparing Scrum And CMMI

Comparing Scrum And CMMI Comparing Scrum And CMMI How Can They Work Together Neil Potter The Process Group help@processgroup.com www.processgroup.com Version 1.0 1 Agenda Definition of Scrum Agile Principles Definition of CMMI

More information

SCRUM and the CMMI. The Wolf and the Lamb shall Feed Together

SCRUM and the CMMI. The Wolf and the Lamb shall Feed Together The Wolf and the Lamb shall Feed Together Dr. Tami Zemel Tangram Hi-Tech Ltd. Shlomi Oren Creo Israel Ltd. The Scrum is an agile, lightweight process developed as a mean to deal with ever changing requirements

More information

How to Assure your Subcontractors Quality with Cross Constellations and Multi Models Inspiration Continues Process Improvement Initiatives

How to Assure your Subcontractors Quality with Cross Constellations and Multi Models Inspiration Continues Process Improvement Initiatives How to Assure your Subcontractors Quality with Cross Constellations and Multi Models Inspiration Continues Process Improvement Initiatives Kobi Vider K.V.P Consulting Kobi.Vider@hotmail.com +972522946676

More information

Organizational Synthesis - CMMI, The Glue That Binds

Organizational Synthesis - CMMI, The Glue That Binds Organizational Synthesis - CMMI, The Glue That Binds Synthesizing: Business Process Model, ISO Standards, Life Cycle Management, Program Direction and CMMI into a Business Process Management System Eileen

More information

CMMI SM Mini- Assessments

CMMI SM Mini- Assessments CMMI SM Mini- Assessments Gary Natwick Harris Corporation Melbourne, Florida SM - CMMI is a service mark of Carnegie Mellon University next level solutions Gary Natwick - 1 Harris Corporation Government

More information

Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно)

Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно) Partner of: Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно) based on: Software Quality Management Models: Intro to Process Improvement (PI) [SEMP Program course, in collaboration

More information

High Maturity Practices in Quality Assurance Mechanisms for Quantitative Management (QM) and Continuous Process Improvement (CPI)

High Maturity Practices in Quality Assurance Mechanisms for Quantitative Management (QM) and Continuous Process Improvement (CPI) High Maturity Practices in Quality Assurance Mechanisms for Quantitative Management (QM) and Continuous Process Improvement (CPI) 1 Presentation Outline Mission Solutions Maturity Profile Quality Assurance

More information

Analyzing Resonance of Motivation in Software Development Process Training by Using FRAM (Work-in-progress)

Analyzing Resonance of Motivation in Software Development Process Training by Using FRAM (Work-in-progress) Analyzing Resonance of Motivation in Software Development Process Training by Using FRAM (Work-in-progress) Shigeru Kusakabe University of Nagasaki, Japan Jun. 13, 2018 Software (SW) Project & Process

More information

CMMI FOR SERVICES, THE PREFERRED CONSTELLATION WITHIN THE SOFTWARE TESTING FUNCTION OF A SOFTWARE ENGINEERING ORGANIZATION

CMMI FOR SERVICES, THE PREFERRED CONSTELLATION WITHIN THE SOFTWARE TESTING FUNCTION OF A SOFTWARE ENGINEERING ORGANIZATION CMMI FOR SERVICES, THE PREFERRED CONSTELLATION WITHIN THE SOFTWARE TESTING FUNCTION OF A SOFTWARE ENGINEERING ORGANIZATION NAME: Nestor K. Ovalle, PhD TITLE: Leadership & Corporate Change Consultant; CMMI

More information

CMMI Capability Maturity Model Integration [CMU SEI]

CMMI Capability Maturity Model Integration [CMU SEI] CMMI Capability Maturity Model Integration [CMU SEI] Generic Goals and Generic Practices Robin Alberto Castro Gil Information Services Director Universidad Icesi Cali Colombia http://www.icesi.edu.co/servicios_recursos_informacion/

More information

Software Quality Management. Kristian Sandahl

Software Quality Management. Kristian Sandahl Software Quality Management Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify

More information

A Real-Life Example of Appraising and Interpreting CMMI Services Maturity Level 2

A Real-Life Example of Appraising and Interpreting CMMI Services Maturity Level 2 A Real-Life Example of Appraising and Interpreting CMMI Services Maturity Level 2 Neil Potter The Process Group help@processgroup.com www.processgroup.com SM CMM Integration, IDEAL, and SCAMPI are service

More information

Using CMMI. Type of Work. IT solution development Software development IT solution integration IT solution deployment

Using CMMI. Type of Work. IT solution development Software development IT solution integration IT solution deployment Using CMMI Type of Work IT solution support / Help desk / Network support IT solution development Software development IT solution integration IT solution deployment Use COBIT/ITIL Use CMMI Levels 3-5

More information

Teuvo Suntio. Quality Development Tools. Professor of Power Electronics at University of Oulu. Electronic System Design A TS Rev. 1.

Teuvo Suntio. Quality Development Tools. Professor of Power Electronics at University of Oulu. Electronic System Design A TS Rev. 1. * * * Quality Development Tools Teuvo Suntio Professor of Power Electronics at University of Oulu Slide 1/25 Six Sigma: [1] S. G. Shina, Six Sigma for Electronics Design and Manufacturing, McGraw-Hill,

More information

! To solve problems. ! To take up new opportunities. ! Requirements - descriptions of. " Behavior. " Data. " Constraints (eg. cost and schedule)

! To solve problems. ! To take up new opportunities. ! Requirements - descriptions of.  Behavior.  Data.  Constraints (eg. cost and schedule) COMP3110/6311, Software Analysis and Design Why do we Develop Software? To solve problems To take up new opportunities The value of Requirements "#$"%&'(%)#*+"%#)&),'$&+)& '()#-&)'$./,0.&+%/&.%1"*(%2.%#

More information

Use of Competency Guidelines to Address CMMI GP 2.5

Use of Competency Guidelines to Address CMMI GP 2.5 Use of Competency Guidelines to Address CMMI GP 2.5 Mary E. Howard Raytheon Garland, Texas ALL RIGHTS RESERVED Generic Practice 2.5 Practice Train the people performing or supporting the process as needed.

More information

Software Quality Engineering Courses Offered by The Westfall Team

Software Quality Engineering Courses Offered by The Westfall Team Building Skills is a 3-day course that is a subset of our course. The course is designed to provide a fundamental knowledge base and practical skills for anyone interested in implementing or improving

More information

SE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering?

SE curriculum in CC2001 made by IEEE and ACM: What is Software Engineering? SE curriculum in CC2001 made by IEEE and ACM: Overview and Ideas for Our Work Katerina Zdravkova Institute of Informatics E-mail: Keti@ii.edu.mk What is Software Engineering? SE is the discipline concerned

More information

Process Improvement: CMMI

Process Improvement: CMMI Course "Softwareprozesse" Process Improvement: CMMI Lutz Prechelt Freie Universität Berlin, Institut für Informatik http://www.inf.fu-berlin.de/inst/ag-se/ Part 1: Process improvement, TQM, CMMI The 5

More information

Software Quality Engineering Courses Offered by The Westfall Team

Software Quality Engineering Courses Offered by The Westfall Team Courses is a 2-day course that is a subset of our course. The course is designed to provide an overview of techniques and practices. This course starts with an overview of software quality engineering

More information

An Embedded SCAMPI-C Appraisal at the National Security Agency. NDIA CMMI Technology Conference and User s Group November 15, 2007

An Embedded SCAMPI-C Appraisal at the National Security Agency. NDIA CMMI Technology Conference and User s Group November 15, 2007 An Embedded SCAMPI-C Appraisal at the National Security Agency NDIA CMMI Technology Conference and User s Group November 15, 2007 Joe Wickless Software Engineering Institute Acquisition Support Program

More information

Transitioning a Merged Organization to CMMI and a New OSSP. NDIA CMMI Technology Conference November 14, 2002

Transitioning a Merged Organization to CMMI and a New OSSP. NDIA CMMI Technology Conference November 14, 2002 Transitioning a Merged Organization to CMMI and a New OSSP NDIA CMMI Technology Conference November 14, 2002 Dr. Randy Walters Northrop Grumman Information Technology Defense Mission Systems Defense Mission

More information

Extending an Agile Method to Support Requirements Management and Development in Conformance to CMMI

Extending an Agile Method to Support Requirements Management and Development in Conformance to CMMI Extending an Agile Method to Support Requirements Management and Development in Conformance to CMMI Alexandre Lazaretti Zanatta 1, Patrícia Vilain 2 1 Instituto de Ciências Exatas e Geociências - Ciência

More information

PM Architecture Design as a Critical Success Factor in CMMI Model Implementation

PM Architecture Design as a Critical Success Factor in CMMI Model Implementation PM Architecture Design as a Critical Success Factor in CMMI Model Implementation November, 2007 Christen M. MacMillan, PMP Implementing CMMI into Your Organization Most CMMI efforts begin with noble intentions

More information

CMM,,mproving and,ntegrating

CMM,,mproving and,ntegrating Pittsburgh, PA 15213-3890 CMM,,mproving and,ntegrating Mike Phillips Mary Beth Chrissis Mike Konrad Sandy Shrum SM SCAMPI, SCAMPI Lead Appraiser, SEPG, and SEI are service marks of Carnegie Mellon University.,

More information

CMMI Level 2 for Practitioners: A Focused Course for Your Level 2 Efforts

CMMI Level 2 for Practitioners: A Focused Course for Your Level 2 Efforts CMMI Level 2 for Practitioners: A Focused Course for Your Level 2 Efforts Software Engineering Institute Carnegie Mellon University Pittsburgh, PA 15213 Mary Beth Chrissis May 27, 2009 Report Documentation

More information

CMMI GLOSSARY A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

CMMI GLOSSARY A B C D E F G H I J K L M N O P Q R S T U V W X Y Z http://www.tutorialspoint.com/cmmi/cmmi-glossary.htm CMMI GLOSSARY Copyright tutorialspoint.com Here is the list of all CMMI Terms arranged in alphabetical order. A direct link is given based on first

More information

Capability Maturity Model Integration (CMMI) V1.3 and Architecture-Centric Engineering

Capability Maturity Model Integration (CMMI) V1.3 and Architecture-Centric Engineering Capability Maturity Model Integration (CMMI) V1.3 and Architecture-Centric SATURN Conference May 17, 2011 San Francisco, CA Dr. Lawrence G. Jones Dr. Michael Konrad Software Institute Carnegie Mellon University

More information

Applying CMMI-SVC Process Areas to CMMI-DEV Projects

Applying CMMI-SVC Process Areas to CMMI-DEV Projects Applying CMMI-SVC Process Areas to CMMI-DEV Projects M. Lynn Penn Director Strategic Process Engineering Integrated Systems & Global Solutions Lockheed Martin Corporation November, 2011 Topics for Discussion

More information

Ogden Air Logistics Center

Ogden Air Logistics Center Ogden Air Logistics Center Making TSP Work at CMMI Level 5 C a r n e g i e M e l l o n S o f t w a r e E n g i n e e r i n g I n s t i t u t e David Webb Hill Air Force Base Jim Van Buren Draper Laboratory

More information

Project Management by Functional Capability. NDIA CMMI Technology Conference and User s Group November 15, 2007

Project Management by Functional Capability. NDIA CMMI Technology Conference and User s Group November 15, 2007 Project Management by Functional Capability NDIA CMMI Technology Conference and User s Group November 15, 2007 Fred Schenker Software Engineering Institute Bob Jacobs Computer Systems Center Inc. Goals

More information

Ingeniería de Requisitos con IRqA y los niveles 2 y 3 de CMMI. II Semana del CMMI Madrid, 3 de marzo de 2006

Ingeniería de Requisitos con IRqA y los niveles 2 y 3 de CMMI. II Semana del CMMI Madrid, 3 de marzo de 2006 Ingeniería de Requisitos con IRqA y los niveles 2 y 3 de CMMI II Semana del CMMI Madrid, 3 de marzo de 2006 Qué es IRqA? IRqA es el entorno gráfico de Ingeniería de Requisitos integrado IRqA en el ciclo

More information

Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно)

Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно) Partner of: Q.A. Осигуряване на качество на софтуера (2016/2017, редовно/задочно) based on: Software Quality Management Models: Intro to Process Improvement (PI) [SEMP Program course, in collaboration

More information

Requirements Analysis and Design Definition. Chapter Study Group Learning Materials

Requirements Analysis and Design Definition. Chapter Study Group Learning Materials Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this

More information

CMMI-SVC: A Cost-Effective Approach to Early Use

CMMI-SVC: A Cost-Effective Approach to Early Use CMMI-SVC: A Cost-Effective Approach to Early Use Part I: Overview of the CMMI for Services (CMMI-SVC) Part II: Case Study and potential application to the U.S. Army Software Engineering Center (SEC) CECOM

More information

Practical Application of the CMMI for Building a Strong Project Management Infrastructure

Practical Application of the CMMI for Building a Strong Project Management Infrastructure Practical Application of the CMMI and PMBOK for Building a Strong Project Management Infrastructure PMI - NAC and DAU 3 rd Annual Professional Development Symposium Von Braun Center Huntsville, Alabama

More information

Leveraging Your Service Quality Using ITIL V3, ISO and CMMI-SVC. Monday Half-Day Tutorial

Leveraging Your Service Quality Using ITIL V3, ISO and CMMI-SVC. Monday Half-Day Tutorial Leveraging Your Service Quality Using ITIL V3, ISO 20000 and CMMI-SVC Monday Half-Day Tutorial Definitions Service - Employment in duties or work for another The Challenge This situation where organization

More information

Process Improvement: CMMI

Process Improvement: CMMI Course "Softwareprozesse" Process Improvement: CMMI Lutz Prechelt Freie Universität Berlin, Institut für Informatik Part 1: Process improvement, TQM, CMMI The 5 CMMI Levels CMMI elements: goals, practices

More information

Interpretive Guidance: What We ve Learned

Interpretive Guidance: What We ve Learned Pittsburgh, PA 15213-3890 Interpretive Guidance: What We ve Learned Software Engineering Process Group Conference March 10, 2004 CMMI is registered in the U.S. Patent and Trademark Office by University.

More information

Requirements Verification and Validation

Requirements Verification and Validation SEG3101 (Fall 2010) Requirements Verification and Validation SE502: Software Requirements Engineering 1 Table of Contents Introduction to Requirements Verification and Validation Requirements Verification

More information

Integrated Class C Process Appraisals (ICPA)

Integrated Class C Process Appraisals (ICPA) Integrated Class C Process Appraisals (ICPA) Kent S. McClurg Raytheon Company Garland, TX 972 205-7415 Kent_S_McClurg@raytheon.com Suzanne N. Delcambre Raytheon Company Garland, TX 972 205-7967 Suzanne_N_Delcambre@raytheon.com

More information

Work Plan and IV&V Methodology

Work Plan and IV&V Methodology Work Plan and IV&V Methodology Technology initiatives and programs should engage with an IV&V process at the project planning phase in order to receive an unbiased, impartial view into the project planning,

More information

WORK PLAN AND IV&V METHODOLOGY Information Technology - Independent Verification and Validation RFP No IVV-B

WORK PLAN AND IV&V METHODOLOGY Information Technology - Independent Verification and Validation RFP No IVV-B 1. Work Plan & IV&V Methodology 1.1 Compass Solutions IV&V Approach The Compass Solutions Independent Verification and Validation approach is based on the Enterprise Performance Life Cycle (EPLC) framework

More information

Dependency Analysis between CMMI Process Areas

Dependency Analysis between CMMI Process Areas Dependency Analysis between CMMI Process Areas Paula Monteiro 1, Ricardo J. Machado 1, Rick Kazman 2, and Cristina Henriques 3 1 Universidade do Minho {pmonteiro,rmac}@dsi.uminho.pt 2 Software Engineering

More information

Measurement within the CMMI

Measurement within the CMMI Measurement within the CMMI 09 March 2004 SEPG 2004 Orlando, Florida Kent Johnson kent.johnson@teraquest.com Margaret Kulpa margaret.kulpa@agiledigm.com CMMI is registered in the U.S. Patent and Trademark

More information

Core Design Requirements At the start of a project, it is important to specify those parameters and properties that:

Core Design Requirements At the start of a project, it is important to specify those parameters and properties that: Design & Innovation Fundamentals Lecture 3 Requirements Analysis Design Process Expression of need Engineer translates need into a definition of problem, including statement of desired outcome Engineer

More information

What is important in CMMI and what are the interrelations among its elements?

What is important in CMMI and what are the interrelations among its elements? What is important in CMMI and what are the interrelations among its elements? Zádor Dániel Kelemen ODF Symposium, 28 June, 2011, Budapest Project: : Software quality assurance service-package for open

More information

CMMI v1.1 for a Service-Oriented Organization. By Steve Hall, Jeff Ricketts, Diane Simpson 16 November 2005

CMMI v1.1 for a Service-Oriented Organization. By Steve Hall, Jeff Ricketts, Diane Simpson 16 November 2005 CMMI v1.1 for a Service-Oriented Organization By Steve Hall, Jeff Ricketts, Diane Simpson 16 November 2005 Overview This presentation will describe how CMMI v1.1 was applied to Raytheon Company s Information

More information

CSE 435 Software Engineering. Sept 14, 2015

CSE 435 Software Engineering. Sept 14, 2015 CSE 435 Software Engineering Sept 14, 2015 What is Software Engineering Where Does the Software Engineer Fit In? Computer science: focusing on computer hardware, compilers, operating systems, and programming

More information

Marilyn Ginsberg-Finner Northrop Grumman Corporation

Marilyn Ginsberg-Finner Northrop Grumman Corporation CMMI for Services (CMMI-SVC) Cost-Effective Approaches to Early Use Presentation for DC/MD ASQ Software SIG, SSQ, and IEEE CS May 13 2009 Marilyn Ginsberg-Finner (Marilyn.Ginsberg-Finner@ngc.com) Northrop

More information

Objectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes

Objectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software

More information

Topics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering

Topics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software

More information

2005 PSM Users Group Conference Keystone, CO. Topic Introduction

2005 PSM Users Group Conference Keystone, CO. Topic Introduction The High Road to Measurement Maturity subtitled: Applying with Vengeance Speaker: Kevin Domzalski Organizational Process Optimization Lead Topic Introduction!Our Process Improvement Timeline "1989 Achieved

More information

Developed by: Steven Jacobs, Eck Doerry

Developed by: Steven Jacobs, Eck Doerry Developed by: Steven Jacobs, Eck Doerry 1 Consequences of Bad Requirements Engineering http://www.knovelblogs.com/2012/08/30/the-importance-of-requirements-engineering/ 2 Building an efficient organization

More information

Process Maturity Profile

Process Maturity Profile Carnegie Mellon Process Maturity Profile CMMI v1.1 SCAMPI SM v1.1 Class A Appraisal Results 2005 End-Year Update March 2006 We could not produce this report without the support of the organizations and

More information

Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1

Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be

More information

CLASS/YEAR: II MCA SUB.CODE&NAME: MC7303, SOFTWARE ENGINEERING. 1. Define Software Engineering. Software Engineering: 2. What is a process Framework? Process Framework: UNIT-I 2MARKS QUESTIONS AND ANSWERS

More information