Product Lifecycles (module 05)

SE Tutorial Product Lifecycles - 1version NDIA CMMI Conf v1.7© 2004 Kasse Initiatives, LLC

ProductProductLifecyclesLifecycles


OrganizationalOrganizationalBehaviorBehavior

�Life-cycle models model organizationalbehavior

�Behavior is characterized by products, whichmay be organized into phases formanageability

�Each phase is usually characterized by one ormore major products emerging from theorganization during that phase


Management Views ofManagement Views ofLifeLife--Cycle ProductsCycle Productsby Lifeby Life--Cycle PhasesCycle Phases

System Definition System Development System Deployment

Upper Management(Management)

Lower Management(Product)

Middle Management(Process)


Lower ManagementLower Management

�Lower Management (Project Management) –Lowest level of management:�Each phase of the lifecycle terminates with

completion of one of more major products�Intermediate products that represent components of

the finished product or checkpoints that areassociated with progress and productivity (earnedvalue) are also visible to this level of management

�Project Management is responsible for ensuring thequality of the product through various verificationand validation activities


Middle ManagementMiddle Management

�Middle Management�Has less responsibility, visibility and understanding

of intermediate products�Number of intermediate products shown to middle

management is reduced�Middle management focus is on process rather than

product�Middle management is concerned with integrating

product-level resources into a high-quality process


Senior ManagementSenior Management

�Senior Management�Senior Management is normally concerned with

integrating the process to achieve an organizationalgoal or a strategic purpose

�Senior Management requires even less visibility intointermediate products

�Senior Management is focused on the coordinationand integration of production and acquisition,research, Development,Test and Evaluation,planning, and marketing lifecycles


Research, Development,Research, Development,Test and Evaluation LifeTest and Evaluation Life--Cycle ModelCycle Model

BasicResearch

AppliedResearch

Test andEvaluation

Full ScaleDevelopment

ProductionSupport

Definition

Development

Deployment


Research, Development,Research, Development,Test and Evaluation LifeTest and Evaluation Life--Cycle ModelCycle Model -- 22

�A well-managed RDT&E program is oftenthought of as a tool for risk mitigation

�RDT&E lifecycle provides a framework withinwhich to manage research and development�The concept of the lifecycle can be defined

abstractly�3 major phases can be defined: definition,

development, deployment


A Closer Look at theA Closer Look at theRDT&E LifecycleRDT&E Lifecycle

�Definition Phase�Basic research is either well defined or non-well

defined�Well defined research is defensive, undertaken to

protect the organization’s market position frommarket competition

�Non-well defined research is more likely to result inproduct diversification


A Closer Look at theA Closer Look at theRDT&E LifecycleRDT&E Lifecycle -- 22

�Development Phase�Product is designed and built�Organizational constraints may be felt and reflect

the need for corporate change�Business processes may need to be realigned to

accommodate new production�Product-level insights cause iteration on the

requirements phase until an acceptable product isdefined and built� the development phase may be regarded as the

prototyping element of the requirements phase� at the end of the development phase, the

requirements will be more stable but not frozen


A Closer Look at theA Closer Look at theRDT&E LifecycleRDT&E Lifecycle -- 33

�Deployment Phase�Test and Evaluation provide the content for the

Deployment Phase�The goal of this phase is to deploy a useful model of

a potential product for the consideration ofmanagement

�The model provides information about the impactpotential upon the organization in terms of:� start-up costs� perturbation of existing functions� applicability of existing assets


CustomerView

SystemsEngineer

View

ContractorView

UserRequirements

System Specification

Built and Tested System

Built and Tested Subsystems

Built and Tested Components

Subsystem Specifications and Designs

Component Specifications and Designs

3 Views of the System3 Views of the System


3 Views of the3 Views of theSystemSystem -- 22

�Customer View�Associates system requirements with their

realization as a delivered system�This view is from the perspective of the stakeholders

whose consolidated input forms the customerrequirements

�A list of requirements are delivered and a finishedproduct that meets the requirements is expected



�Systems Engineering View�This layer represents the architectural model which

addresses the decomposition of the system-levelspecification into systems design and subsystemspecifications and designs

�The architectural model is the perspective of thesystems engineer who is interested in:� decomposing the whole into manageable parts� re-specifying and designing the parts� integrating the parts to compose the finished

system



�Contractor View�The lowest level couples component specifications

and designs with fully tested components�The implementation model is the perspective of the

contractor who is interested in component-levelspecifications, designs, and products

�The Systems Engineering must therefore:�Recognize the product or component as a system�Analyze the system requirements�Synthesize the system components


Software / SystemsSoftware / SystemsLifeLife--Cycle ModelsCycle Models


Systems ProductSystems ProductLifecycleLifecycle

CONCEPTUAL

DEFINITION

PRODUCTION

OERATIONALDIVESTMENT

DETERIORATIONMATURITY

MA

RK

ET

INTR

OD

UC

TION

GROWTHPUREBASICRESEARCH

DE

ATH

APPLIEDRESEARCH

INVE

STM

ENT

RET

UR

N

ROI

REVENUE

PROFIT

BREAKEVEN POINT

RESERCH ANDDEVELOPMENT

INVESTMENT


Definition of aDefinition of aProject LifecycleProject Lifecycle

CONCEPTUALPHASE

PLANNINGPHASE

DEFINITION& DESIGN

PHASE

IMPLEMENTATIONPHASE

CONVERSIONPHASE

PMD

RES

OU

RSE

S

PMO

REQUIREDRESOURCES


The Systems ApproachThe Systems Approach

Systems

REQUIREMENTS

REQUIREMENTS

REQUIREMENTS

REQUIREMENTS

ALTERNATIVE

ALTERNATIVE

ALTERNATIVE

ALTERNATIVE

ALTERNATIVE

ALTERNATIVE

ALTERNATIVE

ALTERNATIVE

Translation Analysis Trade Off Synthesis

Constraints* Legislative * Financial* Timing * Policy

Selection Criteria* Performance * Cost/Benefit* Response Time * Policy


CanoncialCanoncial LifeLife--CycleCycleModelModel


Canonical LifeCanonical Life--CycleCycleModelModel

�The canonical life-cycle model is described by thefollowing phases:�Feasibility Study�Project Initiation�Requirements Specification�Architectural Design�Detailed Design�Coding�Module Test (Unit Test)� Integration and Test�Systems Test�Acceptance Test�Operational Test�Operation (In-service and Maintenance)�Product Phaseout


Process DefinitionProcess DefinitionDiagramsDiagrams


002

035

DOCUMENTATIONPLAN

DEVELOPMENT

DEVELOPMENTPROJECT PLAN

DEVELOPMENT

CONTRACT

COMMERCIAL

PRODUCTDEVELOPMENT

START-UPProduct Idea

Research

Cust omer/Market ing

Requirement

Exist ingNon-product

Soft ware

FEASIBILITYSTUDY

APPOINTPROJECTMANAGER

APPOINTTECHNICAL

CONTROLLER

FEASIBILITYREPORT

DEVELOPMENT

FEASIBILITYREVIEW

PROPOSEDDEVELOPMENT PLAN

DEVELOPMENT

DEVELOPMENT

PROPOSEDUSER FUNCTIONSREQUIREMENTS STATEMENTFEASIBILITY REPORT

PRODUCTREVIEWBOARD

GOAHEAD

020 020

CM PLAN

CM

QUALITYPLAN

QA

DETERMINEMETHOD OF WORKINGPDD STDS& PROCS

DEVELOPMENT

FUNCTIONALDEFINITION

DEVELOPMENT

INITIALDESIGN

DEVELOPMENTTEST STRATEGYAND OUTLINE

TEST PLANDEVELOPMENT

PROJECTINITIATION

REVIEW

022036

030

032

140

034

021033

031

051

Process definition diagram(a) Feasibility study and project initiation phases


CONFIRMEDCONTRACTCOMM ERCIAL

ACCEPTANCE& USAGE PLAN

SUPPORT

0 32

0 30

DETAILEDPROJECT PLAN

DEVELOPMENT

DETAILEDQUALITY PLAN

QA

DRAFTTEST PLANDEVELOPMENT

OUTLINELASER MANUAL

DEVELOPMENT

DRAFTDESIGN

DEVELOPMENT

0 33

REQUIREMENTSPECIFICATION

DEVELOPMENT 0 41

0 51

1 42

0 34

0 35

DETAILEDCM PLAN

CM

1 70

OUTLINEMAINTENANCE

MANUALDEVELOPMENT

ACCEPTANCETEST SPEC

SUPPORT

INDEPENDENTTEST SPECTEST TEAM

INTEGRATIONTEST SPECDEVELOPMENT

DRAFTUSER MA NUAL

DEVELOPMENT

1 01

DESIGNSPECIFICATION

DEVELOPMENT 0 51

1 42

1 44

1 10

DRAFTOPERATIONS

MANUALDEVELOPMENT

1 45

1 01

ARCHITECTURALDESIGNREVIEW

0 220 52

REQUIREMENTSPECIFICATION

REVIEW

0 220 42

PROJECTINITIATION

REVIEW

0 220 36

QUALITY ASSURANCECONFIGURATION MANAGEMENT

TECHNICAL CONTROLCONFIRM METHODS OF WORKING

PROJECT MANAGEMENT PMTC

RQTS SPEC UPDATECMQA

Process definition diagram(b) Requirement and architectural design phases


0 91

PMTC

RQTS SPEC UPDATE

CM & QA

ARCHITECTURALDESIGNREVIEW

0 220 52

INDEPENDENTTEST DATA

TEST TEA M 1 001 01

1 45

DRA FTMA INTENA NCE

MA NUALDEVELOPM ENT

FULL DRAFTOPS MANUA LTECH AUT HOR 1 44

1 01

UNIT TESTDATA

DEVELOPM ENT

INTEGRATEDSOFTWARE

REVIEW

0 220 52

STR DES UPDATE

INTEGRA TIONTEST DATADEVELOPM ENT

FULL DRAFTUSERS MANUAL

TECH AUT HOR 1 42

UN IT T ESTRESULT S

D EV EL OPM EN T0 801 01

D ETAI LEDD ESI GN SP ECS

D EV EL OPM EN T

0 60

UNIT TESTSPECS

DEVELOPM ENT 0 80

INTEGRATIONTEST RESULTSDEV ELOPM ENT

O9 O1 01

D EV EL OPM EN T

0 7 10 7 2

DOCUM ENT EDCODED

M ODUL ESW AL K

TH ROU GH

0 6 1

UN ITTEST

REV IEW

0 80

COD EREA D ING

0 75

1 60

TRAINING NEEDSANALYSISSUPPORT

DEV ELOPMENTPRODUCT

DEV ELOPM ENT

INSTALLATIONNOTES

DEV ELOPM ENT1 43

0 811 02

STABLEREFERENCEVERSION OFSOFTWAREDEVELOPMENT

INT EGRAT IONAND TEST ING BY

DEVELOPM ENTTEA M

0 90repeat ed for each set of modules

0 901 01

Process definition diagram(c) Programming and integration phases


INDEPENDENTTESTING BYTEST TEAM 1 00

PM, TC, RS UPDATE, SD UPDATE, CM, QA

INTEGRATEDSOFTWARE

REVIEW

0 220 52

INSTALLATIONNOTES

SUPPORT 1 43

1 81

DRAFTTRAI NINGCOURSE

SUPPORT

QUALITY &RELIABILITY

REPORTQA 1 26

TESTEDSOFTWARE

REVIEW

0 221 03

ERRORCORRECTIONSDEVELOPMENT

0 91

PRODUCT TOTEST TEAM

CM1 31

1 74

DELIVERABLEPRODUCTSUPPORT

PREDELIVEREDPRODUCT TOTEST TEAM

CM1 31

PRODUCTTO SUPPORT

CM 1 31

USER MA NUALOPERATIONS MANUAL

MAINTENANCE MANUALTECH AUTHOR

1 421 441 45

1 01

INDEPENDENTTEST RESULTS

TEST TEAM

RETESTBY

TEST TEAM100

Process definition diagram(d) Integration test phase


QA

QUALITY &RELIA BILITY

REPORT1 26

PROJ ECTHISTORY

DOCUMENTDEVELOPMENT 0 14

PRODUCTOPERATION

REVIEW

PRODUCTCOMPLETION

REVIEW0 151 12

INCIDENTREPORTSUPPORT

1 71

1 61

TRAININGCOURSES

SUPPORT

FINALOPERATIONS

MANUALTECH AUTHOR

1 44

INSTALLATIONNOTES

SUPPORT1 43

1 42

FINAL USERMANUAL

TECH AUTHOR

ACCEPTANCETEST RESULTS

SUPPORT1 01

1 74

PACKAGEDSOFTWAREPRODUCTSUPPORT

1 45TECH AUTHOR

FINALMAINTENANCE

REPORT

SOFT WAREPROBLEMREPORT

CUST OMER1 72

CUSTOMERACCEPTANCE

REVIEW

1 11

TESTEDSOFTWARE

REVIEW

0 221 03

DEVELOPMENT ASSISTANCETOTECH AUTHORAND SUPPORT

PM, TC, RS/ SD UPDATES, CM, QA PM,TC, RS/ SD UPDATES, CM, QADEVT ASSISTANCE TO SUPPORT

PRODUCTPHASEOUT

PLANSUPPORT

1 76

PRODUCTPHASEOUT

REVIEW

EVALUATIONAND RESPONSETO CUSTOMERBY SUPPORT

TEAM

PLAN UPDATEUPDATE SOFTWARE

RELEASE UPDATED PRODUCTSUPPORT

1 741 75

SPRFILE

SUPPORT1 73

1 77

PRODUCT PHASEOUT

OPERATION

OPERATIONAL TEST PRODUCT COMPLETION

Process definition diagram(d) Product acceptance and operational phases


Systems / SoftwareSystems / SoftwareLifeLife--Cycle ModelsCycle Models


PROTO-TYPE 1

RA

CONCEPT OFOPERATION

RQTS PLANLIFE-CYCLEPLAN

RISK ANALYSIS

PROTOTYPE 2

SOFTWARERQTS

REQUIREMENTSVALIDATION

DEVELOPMENTPLAN

RISK ANALYSIS

PROTOTYPE 3

SOFTWAREPRODUCTDESIGN

DESIGN VALIDATIONAND VERIFICATION

INTEGRATIONAND TEST

OPERATIONALPROTOTYPE

RISK ANALYSIS

DETAILEDDESIGN

DETERMINEOBJECTIVES,ALTERNATIVES,CONSTRAINTS

CUMULATIVE COSTPROGRESSTHROUGHSTEPS EVALUATE ALTERNATIVES,

IDENTIFY, RESOLVE RISKS

PLANNEXT PHASES

DEVELOP VERIFYNEXT-LEVEL PRODUCT

IMPLEMENT-ATION

ACCEPTANCETEST

INTEGRATIONAND TEST

UNITTEST

CODE

COMMITMENT

PARTITION

Spiral ModelSpiral Model


VV--Model SoftwareModel SoftwareDevelopment LifecycleDevelopment Lifecycle

SDLCPhase

BaselinedPhase Products

Legend

Code Reading

Review

Test dataTest cases

Buildfiles

IntegrationPlan

Test casesTest data

Test casesTest data

Test casesTest data

Test casesTest data

Test casesTest data

Coding UnitTest

DetailedDesign Integration

ArchitecturalDesign

Integrationtest

Requirementsspecification

Acceptancetest

FeasibilityStudy

RequirementsDefinition

Operation Productphaseout

ProjectInitiation Operational

testProject

completion

Designspecification

IntegratedSoftware

Requirementsspecification

TestedSoftware

PlansUpdated

requirementsAcceptedSoftware

Statement ofRequirements

OperationalSoftware

CodeCodeCode

ModuledesignsModuledesignsModuledesigns

TestedmodulesTested

modulesTested

modules

Review

Walkthrough


Overlapping WaterfallOverlapping WaterfallSYSTEMREQUIREMENTS

SOFTWAREREQUIREMENTS

SYSTEMDESIGN

DETAILDESIGN

CODE &DEBUG

CODE &DEBUG

CODE &DEBUG

DETAILDESIGN

DETAILDESIGN

DETAILDESIGN

DEVELOPMENTTEST

DEVELOPMENTTEST

QUALIFICATION

DEVELOPMENTTEST

SYSTEMTEST

OPERATION

CODE &DEBUG

DEVELOPMENTTEST


Software plans andrequirements

Validation

Detailed design

Verification

Code

Unit test

Operations andmaintenance

Revalidation

Implementation

System test

Systemfeasibility

Validation

Systemfeasibility

Validation

Systemfeasibility

Validation

Systemfeasibility

Validation

Integration

ProductVerification

Systemfeasibility

Validation

Product design

Verification

Waterfall Model withWaterfall Model withStepwise V&VStepwise V&V


EVOLUTIONARYEVOLUTIONARYMODEL 1MODEL 1STST GenerationGeneration

Planning Risk AnalysisRisk analysis based on initialrequirements

Risk analysis basedon customer reaction

GO, NO-GO DECISION

Toward a Completed System

Initial software prototype

Engineered system

Next Level prototype

Customerevaluates

Initial requirementsgathering and

project planning

Customer EngineeringEvaluation


EVOLUTIONARYEVOLUTIONARYMODEL 2nd GenerationMODEL 2nd Generation

Concept Feasibility projects

Multi-entry pointevolutionary model

Planning Risk Analysis

GO, NO-GO AXIS

Engineering

Task region containinga task set appropriatefor a particular project

Customer InstallationEvaluation & Support

CustomerCommunications

New Applications

& Systems

Role-out Projects

Maintenance/Support Projects

III

III

IV


User InvolvementUser Involvementin Evolutionaryin EvolutionaryDevelopmentDevelopment

SET OBJCETIVES• PERFORMANCE• TECHNICAL• QUALITY

PREPAREEVOLUCTIONANRY

DEVELOPMENT PATH

USER FEEDBACK

USER

FEEDBACK

Repeat Until Complete

SECECT SYSTEMSARCHITECHTURE

ANALYZE RESULTS

DELIVER THEINCREMENT FOR USER

EVALUATION

CODE AND TESTINCREMENT

ENGINEER ANINCREMENT


IncrementalIncrementalDevelopmentDevelopmentProcessesProcesses

NeededProject (MNS)DevelopmentStrategy

Milestone0

High-Level FD/ORD(User Involved)Concept/DesignSystems EngineeringReuse Strategy IdentifyCOIC/CMF

ExecutingProcesses

Detailed Design(User Involved)Detailed Design(User Involved)

DeveloperTesting

User Review

OT&E

Accelerated Development(Code Generation)

Block 1

Block 2

Block 3

Block 4

Block 5

PartitionPlan andDefine

RepetitionSample

Reuse Library(Data, Specs,Designs,Methodologies,Tools)

BusinessModels andArchitecture

RequirementsOutsideCurrentBusiness Area

System Prototype(Risk Analysis)

EvaluatePrototype

User AcceptsPrototype

MilestoneI

MilestoneII

MilestoneIII

MilestoneIV


RADD MethodologyRADD MethodologyC

LIE

NT

BU

SIN

ES

S N

EE

DS

DEPLOYMENT

PROTOTYPE

DEVELOPMENT

WORKPRODUCT

ANALYSIS &ESTIMATE

DESIGN

TESTING

CHANGECONTROL


Software LifecycleSoftware LifecycleProcessesProcesses(ISO/IEC 12207)(ISO/IEC 12207)

�17 Processes grouped into three sets:�Primary Processes

� Acquisition� Supply� Development� Operation� Maintenance


Software LifecycleSoftware LifecycleProcessesProcesses(ISO/IEC 12207)(ISO/IEC 12207) -- 22

�Support Processes� Documentation� Configuration Management� Quality Assurance� Verification� Validation� Joint Review� Audit� Problem Resolution


Software LifecycleSoftware LifecycleProcessesProcesses(ISO/IEC 12207)(ISO/IEC 12207) -- 33

�Organizational Processes� Management� Infrastructure� Improvement� Training


The Process TreeThe Process Tree(ISO/IEC 12207)(ISO/IEC 12207)

LIFECYCLE

PRIMARY

SUPPORTING

ORGANIZATIONAL

TAILORING

DOCUMENTATIONCONFIGURATION MANAGEMENT

QUALITY ASSURANCEVERIFICATION

VALIDATIONJOINT REVIEW

AUDITPROBLEM RESOLUTION

ACQUISITIONSUPPLY

DEVELOPMENTOPERATION

MAINTENANCE

MANAGEMENT

INFRASTRUCTURE

IMPROVEMENTTRAINING


System LifecycleSystem LifecycleProcessesProcesses(ISO/IEC 15288)(ISO/IEC 15288)

�23 Processes grouped four sets:�Agreement Processes

� Acquisition� Supply

�Enterprise Processes� Enterprise Management Process� Investment Management Process� System Life Cycle Process Management Process� Resource Management Process


System LifecycleSystem LifecycleProcessesProcesses(ISO/IEC 15288)(ISO/IEC 15288) -- 22

�Project Management Processes� Planning Process� Assessment Process� Control Process� Decision Management Process� Risk Management Process� Configuration Management Process� Quality Management Process


System LifecycleSystem LifecycleProcessesProcesses(ISO/IEC 15288)(ISO/IEC 15288) -- 33

�Technical Processes� Stakeholder Needs Definition Process� Requirements Analysis Process� Architectural Design Process� Implementation Process� Integration Process� Verification Process� Transition Process� Validation Process� Operations Process� Disposal Process


A Concurrent EngineeringA Concurrent EngineeringLifeLife--Cycle ModelCycle Model

TC>CT

CETEAM

ConceptDevelopment

MarketAnalysis

Set, Cost,Target (CT)

FullProduction

Marketing andDistribution

RequirementsAnalysis

Specifications

Design

Implementation

Testing

Estimation of Total Cost (TC)


Specifications

Design

Implementation

Testing


Specifications

Design

Implementation

Testing

ManufacturingProcess

Development

ManufacturingSystem

Development

ProductDevelopment

Documents

Product Lifecycles (module 05)