Maturity Level 2:Managed Process Areas

Table of Contents (REQM)(PP)(PMC)(SAM)(MA)(PPQA)(CM)Q&A

Maturity Level 2 PAsDevelopment ProjectCustomer

Requirement Management

(REQM)(identify)(inconsistencies)

Requirements Must be DocumentedSimple as a memoElaborate as multi-volume specificationsAll changes must be documented, tracked, and verified throughout the life cycle of the system.

Barriers to REQMRequirements constantly change.Requirements are changed without appropriate coordination approval.Customers do not always recognize the need to document the requirements.Responsibility for Requirements Management is not clearly established.

Where Does REQM Stand?

Why Is REQM Important?Requirements management processes manage the requirements of a project to ensure thatThe correct requirements are identified and the inconsistencies between the requirements and the project plans and work product are resolved.Bidirectional traceability between the requirements and the product/product component are maintained.Any changes to the requirements are documented and the impact to the project are assessed.

What Are the Benefits of REQM?Agreement reached from requirements provider and receiver to ensure that the correct requirements are incorporated into the project plan.Requirement changes are effectively managed thru defined process. Traceability maintained between the requirements and the product facilitate the impact evaluation of changes as well as the verification of work-product.Requirements baseline are established as the basis for further product component requirements development.

SG 1

SG 1 (2)(specific practice, SP)SP 1.1 SP 1.2 SP 1.3 SP 1.4 SP 1.5

REQM Context

SP 1.1

SP 1.1 (2)1. 2. 3. 4. 1. 2. 3. 4.

SP 1.1 (3) ()

SP 1.1 (4):

SP 1.2

SP 1.2 (2)1. 2. 1. 2.

SP 1.3

SP 1.3 (2)1. 2. 3. 1. 2. 3. 4.

SP 1.4

SP 1.4 (2)1. 2. 1. ()2. 3. 4. (Traceability Matrix)

Horizontal traceabilityfunctions to functions and across interfaces. Vertical (bidirectional) traceabilitylife cycle phases design, software modules, testing,

Requirements vs. Requirements

(2)Requirements vs. Components

SP 1.5 (inconsistencies)

SP 1.5 (2)1. 2. (corrective actions) 1. 2. 3. 4.

RD (Requirements Development)transforming stakeholder needs into product requirementsTS (Technical Solution)the requirements processes are used, development of alternative solutions . Transforming requirements into technical solutionsPP (Project Planning)How project planning reflect requirements and revise change as requirements changePMC (Project Monitoring and Control)Tracking and controlling project activities related to requirements and taking appropriate corrective actionsRM (Risk Management)identifying and handling risks associated with requirements.CM (Configuration Management)baselines and controlling changes to configuration documention for requirements.

RD: Requirements DevelopmentTS: Technical SolutionPI: Product IntegrationVer: VerificationVal: Validation

ImportanceThere is a stable environment for managing the project.Inconsistencies between those requirements and the projects plans and work products are identified and resolved.Building to the correct requirements.You can assess which requirements and product components are affected by a proposed change.Unnecessary rework are eliminated.Traceability evaluating impact of change, in work product verification, , keep requirements and project work in synchronization.

REQM in Project

GG 2 GG2

GG 2 (2)(generic practice, GP)GP 2.1 (CO 1) GP 2.2 (AB 1) GP 2.3 (AB 2) GP 2.4 (AB 3) GP 2.5 (AB 4) GP 2.6 (DI 1) GP 2.7 (DI 2) GP 2.8 (DI 3) GP 2.9 (VE 1) GP 2.10 (VE 2)

GP 2.1

GP 2.2

GP 2.3 ()

GP 2.4

GP 2.5

GP 2.6

GP 2.7

GP 2.7 (2)

GP 2.8 ()

GP 2.9

GP 2.9 (2)

GP 2.10

GG 3 GG3GG3

GG 3 (2)(generic practice, GP)GP 3.1 GP 3.2

GP 3.1

GP 3.2

Project Plan

(PP)

SG 1 SP 1.1 (WBS)SP 1.2 SP 1.3 SP 1.4

SP 1.1 1. 2. 3. 1. 2. 3. ()4.

SP 1.1 (2)

SP 1.2 1. 2. 3. 4. 1. 2. 3. 4.

SP 1.2 (2) (Function points) (SLOC) (Class)(Object)

SP 1.3

SP 1.4 1. 2. 3. 1. 2. 3. ()

SP 1.4 (2)()(Delphi )()

SG 2 (specific practice, SP)SP 2.1 SP 2.2 SP 2.3 SP 2.4 SP 2.5 SP 2.6 SP 2.7

SP 2.1 1. 2. 3. 1. 2. 3. 4. 5. 6.

SP 2.1 (2) ()

SP 2.2 1. 2. 3. 1. 2. 3. 4.

SP 2.2 (2)

SP 2.3 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 1. 2. 3.

SP 2.4 1. WBS 2. WBS 3. 4. /5. /6. 1. 2. 3.

SP 2.5 1. 2. 3. ()1. 2. 3. 4.

SP 2.6

()

SP 2.7

SG 3 (specific practice, SP)SP 3.1 SP 3.2 SP 3.3

SP 3.1

SP 3.2 1. ()2. 3. 4. 5.

SP 3.3 1. 2. 1. 2. 3. 4. 5.

Project Monitor and Control

(PMC)

SG 1 (specific practice, SP)SP 1.1 SP 1.2 SP 1.3 SP 1.4 SP 1.5 SP 1.6 SP 1.7

SP 1.1

SP 1.1 (2)1. 2. 1. 2. 3. 4. 5. 6.

SP 1.1 (3)

SP 1.1 (4)()()

SP 1.2

SP 1.2 (2)1. ()2. 3.

SP 1.3

SP 1.3 (2)1. 2. 3.

SP 1.4

SP 1.4 (2)1. 2. 3.

SP 1.5

SP 1.5 (2)1. 2. 3.

SP 1.6

SP 1.6 (2)1. 2. 3. 4. 5. 6.

SP 1.7

SP 1.7 (2) 1. ()2. 3. 4. 5.

SG 2 (specific practice, SP)SP 2.1 SP 2.2 SP 2.3

SP 2.1 1. 2.

SP 2.1 (2)()

SP 2.2 1. 2. 3.

SP 2.2 (2)

SP 2.3 1. 2. 3.

Supplier Agreement Management

(SAM)

SG 1 (specific practice, SP)SP 1.1 SP 1.2 SP 1.3

SP 1.1

SP 1.2 1. 2. 3. 4. 5. 6. 1. 2. 3. 4. 5. 6.

SP 1.2 (2)

SP 1.3 1. 2. 3. 4. 1. 2. 3. 4. 5. 6.

SP 1.3 (2)

SG 2 (specific practice, SP)SP 2.1 SP 2.2 SP 2.3 SP 2.4

SP 2.1 1. 2. 3. 4. 5. 1. 2. 3. 4. 5. 6. 7.

SP 2.1 (2)/

SP 2.2 1. 2. 3. 4. 1. 2. 3. 4. 5. 6. 7. 8.

SP 2.2 (2)

SP 2.3 1. 2. 3. 1. 2. 3. 4. 5. 6. 7.

SP 2.4 1. 2. 3. 1. 2. 3. /

Measurement and Analysis

(MA)

SG 1 (specific practice, SP)SP 1.1 SP 1.2 SP 1.3 SP 1.4

SP 1.1 1. 2. 3. 4. 4. 5.

SP 1.2 1. 2. 3. 4.

SP 1.2 ()()()()(Earned Value)(SPI)(:)(/)

SP 1.3 1. 2. 1. 2. 3. 4. 5. 6. 7.

SP 1.4 1. 2. 1. 2. 3. 4. 5. 6.

SG 2 (specific practice, SP)SP 2.1 SP 2.2 SP 2.3 SP 2.4

SP 2.1 1. 2. 1. 2. 3.

SP 2.2 1. 2. 3. 4.

SP 2.3 1. 2. 3.

SP 2.3 (2)

SP 2.4 1. 2. 1. 2.

Process and Product Quality Assurance

(PPQA)

SG 1 (specific practice, SP) SP 1.1 SP 1.2

SP 1.1 1. 2. 3. 1. ()2. 3. 4. 5.

SP 1.1 (2)

SP 1.2 1. 2. 3. 1. 2. 3. 4. 5. 6. 7. 8.

SG 2 (specific practice, SP)SP 2.1 SP 2.2

SP 2.1 1. 2. 3. 1. 2. 3. 4. 5. 6. 7.

SP 2.2 1. 2. 3. 4. 1. 2.

Configuration Management

(CM)

SG 1 (specific practice, SP)SP 1.1 SP 1.2 SP 1.3

SP 1.1 1. 2. 3. 4. 5.

SP 1.1 (2)()

SP 1.1 (2)

SP 1.2 1. 2. 3. 1. 2. 3. 4. 5. 6. 7. 8.

SP 1.2 (2)()()()

SP 1.3 1. 2. 1. 2. 3. 4.

SG 2 (specific practice, SP)SP 2.1 SP 2.2

SP 2.1 1. 2. 3. 4.

SP 2.2 1. 2. (archives)1. 2. 3. 4. 5.

SG 3 (specific practice, SP)SP 3.1 SP 3.2

SP 3.1 1. 2. 3. 4. 5. 1. 2. 3. 4. 5. 6. ()

SP 3.2 1. 2. 1. 2. 3. 4. 5. 6.

Q&A