Is An Integrated Set of Systems and SoftwareSystems … 12207:1995, SW Life Cycle Common Life Cycle Processes Unified Process Set Assessment & Governance ISO/IEC 12207:2008, SW Life

Is An Integrated Set of Systems and SoftwareSystems and Software Standards Possible?

Garry RoedlerGarry RoedlerUS Head of Delegation for ISO/IEC JTC1/SC7/WG7,US Head of Delegation for ISO/IEC JTC1/SC7/WG7,

US TAG TG7 Lead,US TAG TG7 Lead,

Senior Program Manager, Systems EngineeringSenior Program Manager, Systems Engineering

Lockheed Martin CorporationLockheed Martin Corporation

April 29, 2008

1

Agenda

• Problem, Causes, and Objectives

• Example of Steps Taken Towards the ObjectivesObjectives

• Assessment of Success

• What Is Still Needed?

2

The Problem• In the past, Systems and Software standards have

had different:– Terminology– Process sets

P t t– Process structures– Levels of prescription

Audiences– Audiences• These differences have been both between Systems

and Software and to some extent within eachand Software, and to some extent within each• The problem has been exacerbated by competing

standards in whole or partstandards, in whole or part

Lack of integration both within and across St d d D l t O i ti

3

Standards Development Organizations

The Cause• Culture

– “We’re different”– “Not invented here”

• Organizational g– Different teams, committees, etc.

• CompetitionCompetition– Many Standards Development Organizations

• Domains• Domains– Focused, narrow view often doesn’t look beyond the

domain for commonalitydomain for commonality

Many obstacles; some real, some perceived,

4

some self-made

The Impact• Less effective/efficient processes

– Not focused on leveraging commonalities – causes redundancyHas res lted in incompatibilities inconsistencies– Has resulted in incompatibilities, inconsistencies

• Less effective solutionsNot focused on a common approach to solve a problem/need– Not focused on a common approach to solve a problem/need

• Obstacle for:– Communicating (at all levels – disciplines teams etc )Communicating (at all levels disciplines, teams, etc.)– Working in integrated teams– Leveraging resources

• Stove-piping due to: – The incompatibilities, inconsistencies– Lack of leveraging commonalities

Impacts effectiveness and efficiency of the team5

Impacts effectiveness and efficiency of the team

The Objective• The objective is to make the standards

more usable together by achieving:more usable together by achieving:– Common vocabulary– Single integrated process setSingle, integrated process set– Single process structure– Jointly planned level of prescription– Jointly planned level of prescription – Suitable across the audiences

Accounts for considerations in wide range of– Accounts for considerations in wide range of domains and applications

Work to a common vision, agreements, and general process concepts

6

and general process concepts

Looking BackLooking Back

Framing the SituationFraming the Situation

7

Heritage of SE Standards & Models as of 2002"Lif l " h P h

ISO/IEC 12207

1995

ISO/IEC 12207 AM

2002

SW Stds

1969

"Life cycle" approach- Fixed phases / time- Document contents

Process approach - Objectives /purpose- Outcomes- Activities

N d t ifi d (Full Std)12207 AM(Full Std)

Stds

EIA / IS 632

1994

(I t i St d d)1974

Mil-Std-499 1998

EIA632

- No document specified

ISO/IEC 15288

2002

(Full Std)

ISO/IEC 19760

2003

(PDTR)

(Interim Standard)Mil-Std-

499A

1974

Mil-Std-499B

1994

1998

632(Full Std)

1994

HarmonizationCandidates

(Full Std) (PDTR)

SE Standards

(Not Released) IEEE 1220

(Full Std)

1994

(Trial Use)

IEEE 1220

2002

ISO/IEC 15504

(FDIS)20021998

EIA/IS 731

1994/96

INCOSE

SE Models

( )

2002

CMMI

(FDIS) EIA 731 SE CM

(Planned)

EIA/IS 731 SE CM

(Interim Standard)

SE CAM

(Industry Model) 1994/95

EPIC

LegendObsolete

Current, approved

8

SE/SW/IPPD

(Version 1.1)

SE-CMM

(Industry Model)SupersedesSource for

pp

In development

Example of Steps Taken Towards theTaken Towards the

Objectivesj

A Look at the JourneyA Look at the Journey for ISO/IEC JTC1/SC7

9

ISO/IEC JTC1/SC7 Harmonization ConceptAlignment of Stds Full Integration Concept2003

ISO/IEC 15288 2008ISO/IEC 15288:2002, System Life Cycle

ISO/IEC TR 24774:2006, Guidelines

for Process Def

ISO/IEC TR 24774:20xx, Guidelines

for Process Def

ISO/IEC 15288:2008, System Life Cycle

Processes

ISO/IEC 12207:2008

System Life Cycle Processes

ISO/IEC 12207:1995, SW Life Cycle

Common Life Cycle Processes

Unified Process SetAssessment & Governance

ISO/IEC 12207:2008, SW Life Cycle

Processes

ISO/IEC TR12207 AMD2:200412207 AMD1:2002

SW Life Cycle Processes

ISO/IEC TR

Processes

Discipline/Domain Unique Life Cycle

ProcessesISO/IEC TR 24748:2009, Guide to Life Cycle Mgt ISO/IEC

19760:2003, Guide to 15288 ISO/IEC

ISO/IEC TR 24748:2009, Guide to Life Cycle Mgt ISO/IEC TR

24748:20xx, Guide to Life Cycle Mgtto 15288

ISO/IEC 15271:1998, Guide

t 12207


to 15288

ISO/IEC

ISO/IEC 19760:20xx, Guide for System Appl.

to Life Cycle Mgt

Aligned Single Process

to 12207

Ad Hoc Support


to 12207

ISO/IEC xx:yy Oth A l G id

ISO/IEC 15271:20xx, Guide for SW Appl.

10

g gElaboration StandardsStandards Other Appl. Guides

Vocabulary (24765) and Documentation (15289)

Vocabulary (24765) and Documentation (15289)

Intended Relationships of Key System & Software Engineering Process Standards After Alignment

R i dOther Other

24748: Guide to Life Cycle Management

Revised Revised 15288:

Life cycle processes

f t

Revised 12207:

Life cycle processes

Other standards providing specific

practices for

Other standards providing details of

selected SW Sys/SW Scope

Other standards providing details of selected

15289:Document-

ation

for systems

(And associated

guide 19760)

for SW

(And associated

guide 15271)

pspecific

purposes

(e.g., 15026, System/SW

processesSys/SW Scope

system processesRevised

16326:ProjectMgmt g )guide 15271)

Assurance)

+Revised 15939:

Measure-ment

g

Revised 16085:RiskMgmt.

Common vocabulary, process architecture, and process description conventions

...

11Source: Adapted from chart of James Moore, MITRE.

Process Assessment (ISO/IEC 15504) and Quality Mgmt (ISO 9001, ISO/IEC 90003/24783)

Relations of Process Constructs among ISO/IEC 12207:1995 and its Amendments, 15288:2002, 15288:2008 & 12207:2008

12207:Amds 15288:200212207:1995 12207:2008 15288:2008

=Processes

P + O

Processes

P + O

Processes Processes

P + O

Processes

P + O

=Sub-Processes

P + ONew “groupings”

Activities Sub-Processes

P + OP + O P + O

Activities Activities

ActivitiesTasks Tasks Tasks

NotesLists Notes

PRM Annex

Notes

PRM Annex

12= means equals toP+O means Process + Outcomes

OptionalConstructP + O P + O

PRM Annex PRM AnnexFigure C.2

Source: Anatol Kark, National Research Council, Canada

Project Processes

Agreement Processes

Technical Processes

Structure of 15288:2002Enterprise Processes Project Processes Technical Processes

Supply Process(Clause 6.1.2)

Acquisition Process(Clause 6.1.1)

Project Assessment and Control Process

(Cl 6 3 2)

Project Planning Process(Clause 6.3.1)

Stakeholder Requirements Definition Process (Clause

6.4.1)

Requirements Analysis Process

(Cl 6 4 2)Enterprise Processes Project Processes

Project Planning Process

Technical Processes

Stakeholder Requirements Definition Process

( )

Decision Management Process

(Clause 6.3.3)

(Clause 6.3.2)

Organizational I l t ti P

(Clause 6.4.2)

Architectural Design Process

(Clause 6.4.3)Enterprise Environment Management Process

Project Control Process

Project Assessment Process



Configuration Management Process

(Clause 6.3.5)

Risk Management Process (Clause 6.3.4)

OrganizationalProject-Enabling

ProcessesLife Cycle Model

Management Process

Implementation Process (Clause 6.4.4)

Integration Process(Clause 6.4.5)

Investment Management Process

System Life Cycle Processes Management

ProcessSystem Life Cycle

Decision-making Process

Project Control Process

Implementation Process

Integration Process

V ifi ti P

Information Management Process

(Clause 6.3.6)

(Clause 6.3.5)

Project Portfolio

Infrastructure Management Process

(Clause 6.2.2)

(Clause 6.2.1)

Measurement Process

Verification Process(Clause 6.4.6)

Transition Process

Process

Resource Management Process

Processes15288:2007

Risk Management Process


Verification Process

Transition Process

Validation ProcessHuman Resource

Management Process(Clause 6.2.4)

Project Portfolio Management Process

(Clause 6.2.3)

Measurement Process(Clause 6.3.7)

Validation Process(Clause 6.4.8)

(Clause 6.4.7)Quality Management Process

A t P


Management Process

Disposal Process

Operation Process

Maintenance Process

Quality Management Process

(Clause 6.2.5)

( )Operation Process

(Clause 6.4.9)

Maintenance Process(Clause 6.4.10)

Acquisition Process

Supply Process

Agreement Processes

13

p ( )

Disposal Process(Clause 6.4.11)

pp y


Project Processes

Agreement Processes

Technical Processes

Software Life Cycle ProcessesSW Implement-ation Processes

SW Support Processes

System Life Cycle Processes (15288)System Life Cycle Processes (12207)

Stakeholder Requirements Definition Process (Clause

6.4.1)



Supply Process(Cl 6 1 2)

Acquisition Process(Clause 6.1.1) From 5.3.1

From 5 3 4Software Requirements

Analysis Process

Software Implementation Process

(Clause 7.1.1)

Software Configuration Management Process

Software Documentation Management Process

(Clause 7.2.1)


System Requirements Analysis Process From 5 3 1


(Clause 6.3.3)

Control Process(Clause 6.3.2)

Organizational

(Clause 6.1.2) From 5.3.4

From 5.3.5S ft D t il d D i

Software Architectural Design Process(Clause 7.1.3)

Analysis Process(Clause 7.1.2)

S ft V ifi ti

Software Quality Assurance Process

(Clause 7.2.3)


Process(Clause 6.4.2)


(Clause 6.4.3)

System Architectural Design Process(Clause 6.4.3)

Analysis Process(Clause 6.4.2)

From 5.3.1

From 5.3.4


(Clause 6 3 5)


Life Cycle Model Management Process

(Clause 6 2 1)

Organizational Project-Enabling

ProcessesImplementation Process

(Clause 6.4.4)From 5.3.6

From 5.3.7Software Construction

Process(Clause 7 1 5)

Software Detailed Design Process

(Clause 7.1.4)

Software Validation Process

(Clause 7 2 5)

Software Verification Process

(Clause 7.2.4)7.1.1


System Integration Process

(Clause 6 4 5)

From 5.3.5

From 5.3.6

Measurement Process


(Clause 6.3.6)

(Clause 6.3.5)

Project Portfolio


(Clause 6.2.2)

(Clause 6.2.1)

From 5.3.8

Software Qualification

Software Integration Process

(Clause 7.1.6)

(Clause 7.1.5)

Software Audit Process

Software Review Process(Clause 7.2.6)

(Clause 7.2.5)


Transition ProcessSoftware Installation

System Qualification Testing Process

(Clause 6.4.6)

(Clause 6.4.5)

From 5.3.7

F 5 3 8Measurement Process(Clause 6.3.7)

Human Resource Management Process

(Clause 6.2.4)


Testing Process(Clause 7.1.7)

Software Problem Resolution Process

(Clause 7.2.8)

Software Audit Process(Clause 7.2.7)


Transition Process(Clause 6.4.7)Process(Clause 6.4.7)

Software Acceptance Support Process

(Clause 6.4.8)

From 5.3.8


(Clause 6.2.5)

Domain Engineering Process

Reuse Program Management Process

Software Reuse ProcessesOperation Process

(Clause 6.4.9)

Maintenance Process(Clause 6 4 10)

Software Maintenance Process

Software Operation Process

(Clause 6.4.9)

14Reuse Asset


(Clause 7.3.1)g

(Clause 7.3.3)(Clause 6.4.10)


Software Disposal Process

(Clause 6.4.11)

(Clause 6.4.10)


Another way of looking at it:

E n te rp rise P ro ce sse s T e ch n ica l P ro ce sse s

System Life Cycle ProcessesTechnical Processes

Project Processes

Agreement Processes

System Life Cycle ProcessesTechnical Processes

Project Processes

Agreement Processes

Technical Processes

Project Processes

Agreement Processes

1. Processes common to both2. Processes similar between the two

15288

P ro je c t P la n n in g P ro ce ss

P ro je c t A sse ssm e n t P ro ce ss

P ro je c t C o n tro l P ro ce ss

E n te rp ris e E n v iro n m e n t M a n a g e m e n t P ro ce ss

In ve s tm e n t M a n a g em e n t P ro c e s s

S ys te m L ife C yc le P ro c e ss e sM a n a g e m e n t P ro ce ss

R e so u rc e M a n a g em e n tP

E n te rp rise P ro ce sse sS ta k e h o ld e r R e q u ire m e n ts

D e fin it io n P ro ce ssR e q u irem e n ts A n a lys is

P ro c e s sA rch ite c tu ra l D e s ig n

P ro ce s s

Im p lem e n ta tio n P roce ss

In te g ra tio n P ro c e ss

T e ch n ica l P ro ce sse sP ro je c tP ro ce sse s




(Clause 6.4.3)


(Clause 6.4.2)

Stakeholder Requirements Definition Process (Clause 6.4.1)


(Clause 6.3.5)



(Clause 6.3.3)


(Clause 6.3.2)



(Clause 6.2.1)

Project-Enabling Processes






(Clause 6.4.3)


(Clause 6.4.2)



(Clause 6.3.5)



(Clause 6.3.3)


(Clause 6.3.2)



(Clause 6.2.1)







(Clause 6.4.3)


(Clause 6.4.2)



(Clause 6.3.5)



(Clause 6.3.3)


(Clause 6.3.2)



(Clause 6.2.1)




15288D e c is io n -m a k in g

P ro ce ss

R isk M a n a g em e n tP ro ce ss

C o n fig u ra tio n M a n a g em e n t P ro ce ssA g re e m e n t P ro ce sse s

A cq u is itio n P ro c e s s

S u p p ly P ro ce s s

In fo rm a tio n M a n a g em e n t P ro ce ss

P ro c e s s

Q u a lity M a n a g e m e ntP ro c e s s

M a in te n a n c e P ro ce s s

O p e ra tio n P ro c e ss

V a lid a tio n P ro c e ss

V e rifica tio n P ro c e s s

T ra n s itio n P ro c e ss


Operation Process(Clause 6.4.9)


Transition Process(Clause 6.4.7)




(Clause 6.3.6)


(Clause 6.2.5)


(Clause 6.2.4)


(Clause 6.2.3)


(Clause 6.2.2)








(Clause 6.3.6)


(Clause 6.2.5)


(Clause 6.2.4)


(Clause 6.2.3)


(Clause 6.2.2)








(Clause 6.3.6)


(Clause 6.2.5)


(Clause 6.2.4)


(Clause 6.2.3)


(Clause 6.2.2)

5.1 Acquisition 6.1 Documentation

5. PRIMARYLIFE CYCLE PROCESSES

6. SUPPORTINGLIFE CYCLE PROCESSES

5.1 Acquisition5.1 Acquisition5.1 Acquisition 6.1 Documentation6.1 Documentation6.1 Documentation





S u p p ly P ro ce s s D is p o sa l P ro ce ss Disposal Process(Clause 6.4.11)



Technical Processes

System Life Cycle Processes Software Life Cycle ProcessesProject

ProcessesAgreement Processes

SW Implement-ation Processes

SW Support Processes

122075.3

5.4Operation

5 5

Development

5.2 Supply6.2 Configuration

Management

6.3 QualityAssurance

6.4 Verification

6.5 Validation

6.6 Joint Review

5.3

5.4Operation

5 5

Development

5.2 Supply

5.3

5.4Operation

5 5

Development

5.3

5.4Operation

5 5

Development

5.2 Supply5.2 Supply6.2 Configuration

Management


6.4 Verification

6.5 Validation

6.6 Joint Review

6.2 ConfigurationManagement

6.2 ConfigurationManagement


6.4 Verification

6.5 Validation

6.6 Joint Review


6.4 Verification

6.5 Validation

6.6 Joint Review

System Qualification

System Integration Process

(Clause 6.4.5)


System Architectural Design Process(Clause 6.4.3)

System Requirements Analysis Process

(Clause 6.4.2)


Information Management


(Clause 6.3.5)



(Clause 6.3.3)


(Clause 6.3.2)


Infrastructure


(Clause 6.2.1)




Software Integration

Software Construction Process

(Clause 7.1.5)

Software Detailed Design Process

(Clause 7.1.4)

Software Architectural Design Process(Clause 7.1.3)

Software Requirements Analysis Process

(Clause 7.1.2)

Software Implementation Process

(Clause 7.1.1)

Software Validation Process

(Clause 7.2.5)

Software Verification Process

(Clause 7.2.4)

Software Quality Assurance Process

(Clause 7.2.3)

Software Configuration Management Process

(Clause 7.2.2)

Software Documentation Management Process

(Clause 7.2.1)

Maintenance

5.5 6.7 Audit

6.8 Problem Resolution

7.1 Management

7.3 Improvement

7.2 Infrastructure

7.4 Training

7. ORGANIZATIONAL LIFE CYCLE PROCESSES

Maintenance

5.5

Maintenance

5.5

Maintenance

5.5 6.7 Audit

6.8 Problem Resolution

6.7 Audit6.7 Audit

6.8 Problem Resolution6.8 Problem Resolution

7.1 Management

7.3 Improvement

7.2 Infrastructure

7.4 Training

7. ORGANIZATIONAL LIFE CYCLE PROCESSES

Software Disposal Process

Software Maintenance Process

(Clause 6.4.10)

Software Operation Process

(Clause 6.4.9)

Software Acceptance Support Process

(Clause 6.4.8)

Software Installation Process

(Clause 6.4.7)

System Qualification Testing Process

(Clause 6.4.6)



(Clause 6.3.6)


(Clause 6.2.5)


(Clause 6.2.4)


(Clause 6.2.3)


(Clause 6.2.2)

Reuse AssetManagement Process

Domain Engineering Process

(Clause 7.3.1)

Software Qualification Testing Process

(Clause 7.1.7)

Software Integration Process

(Clause 7.1.6)

Reuse Program Management Process

(Clause 7.3.3)

Software Reuse Processes

Software Problem Resolution Process

(Clause 7.2.8)

Software Audit Process(Clause 7.2.7)

Software Review Process(Clause 7.2.6)

15

7.3 Improvement 7.4 Training7.3 Improvement 7.4 Training Process(Clause 6.4.11)


3. Processes unique to domainSource: Integration Study Group draft content – Richard Kitterman, Northrop Grumman

Usage Guidance for 15288 and 12207

• Nearly the same process models – 15288 describes the processes at the system level.– 12207 provides specializations of the same processes12207 provides specializations of the same processes

to software, and adds processes specific to software.

• Usage Guidance– System Focus – use 15288– System with SW elements – use 15288 and the SW

processes of 12207– SW product or service focus – use 12207

16

Supporting Guidance Changes

• ISO/IEC TR 24748, Guide to Life Cycle

• ISO/IEC TR 19760, Guide to ISO/IEC

• ISO/IEC TR 15271, Guide to ISO/IECGuide to Life Cycle

Management Guide to ISO/IEC 15288, System Life Cycle Processes

Guide to ISO/IEC 12207, Software Life Cycle Processes

– Common guidance and definitions for life cycle

– Guidance specific to application of life cycle processes for

t

– Guidance specific to application of life cycle processes for

ftmanagement concepts

– Includes:

systems– Leverages 24748

rather than repeat

software– Leverages 24748

rather than repeat • Stages• Definitions• Life Cycle Models

its information – Common alignment

of information to

its information – Common alignment

of information to make it easy to use with the other guides

make it easy to use with the other guides

17

These Changes Will Provide an Integrated Set of Guidance for the Base Standards

Towards Full Integration• Study Group established

– Investigate scope and content of Integration Phase – Objective to achieve a fully harmonized view of the

system and software life cycle processesI t ti t id• Integration to consider:– Common purpose and outcomes

A hit t f th t d d– Architecture of the standards– Level of prescription of activities and tasks

Life cycle treatments– Life cycle treatments– Application to services and operations– Common verification and validation concepts– Common verification and validation concepts– Common configuration management concepts– Alignment with other applicable standards

18

Alignment with other applicable standards– Rationalization of application guides

A t fAssessment of SuccessSuccess

19

Current Alignment/Integration StatusFoundation

Overarching

ISO/IEC 24765Vocabulary

ISO/IEC 24748Guide to Life

Cycle MgtTerminology

ISO/IEC 19759SW Body ofKnowledge Joint Standard

with IEEE-CS

Legend

Life Cycle Processes

OverarchingFramework

ISO/IEC 15288System Life

ISO/IEC 12207Software Life

gy

ISO/IEC 26702Management of

In-process to be Joint IEEE-CS docs

Not joint work with IEEE-CS

Processes yCycle Processes Cycle Processes

Assessment/Governance

ISO/IEC 15504Process ISO 9000 Series

Quality Mgt

gSE Processes

ProcessISO/IEC 15939Measurement

ISO/IEC 16085Risk Mgt

ISO/IEC 16326Project Mgt

Governance Assessment Quality Mgt

ToolsISO/IEC xxxxxCM Tool ReqtsC

xxx

Test

ProcessElaborations

gj g

ISO/IEC 250xxSW Quality

ISO/IEC xxxxxReqts Engrg

ISO/IEC14764SW Maint

Application ISO/IEC 24783 ISO/IEC 90003

ToolsISO/IEC 24766RE Tool ReqtsIS

O/IE

CSW

TArtifact Supplemental

ApplicationGuides

ISO/IEC 19760Guide to 15288


ISO/IEC 24783Appl ISO 9000

to Systems


to SW

20

ArtifactDescriptions

ISO/IEC 42010ArchitectureDescription

SupplementalGuidance

ISO/IEC 24774Process

Definition

ISO/IEC 15289Documentation

But Is This Enough? • Advantages

– Drives to a more consistent set of standards– Provides for “interoperability” of these standards– Creates a better foundation for collaboration between Standards

Development Organizations (SDOs)Development Organizations (SDOs) • Work towards common or complementary/supplementary standards• Model has worked well with IEEE-CS and INCOSE

• But some issues still remain– Still allows for significant redundancy– Still need to account for specialized needs– Alignment does not ensure an integrated set of processes that

can be chosen as neededcan be chosen as needed• Integration phase must be completed to gain this benefit• Significant coordination/negotiation needed to drive more industry

buy in

21

buy-in

Wh t I StillWhat Is Still Needed?Needed?

22

Need a Common Taxonomy for Process Standards – One Candidate

Foundation

Overarching

ISO/IEC 24765Vocabulary

ISO/IEC 24748Guide to Life

Cycle MgtTerminology

ISO/IEC 19759SW Body ofKnowledge Joint Standard

with IEEE-CS

Legend

Life Cycle Processes

OverarchingFramework

ISO/IEC 15288System Life

ISO/IEC 12207Software Life

gy

ISO/IEC 26702Management of

In-process to be Joint IEEE-CS docs

Not joint work with IEEE-CS

Processes yCycle Processes Cycle Processes

Assessment/Governance

ISO/IEC 15504Process ISO 9000 Series

Quality Mgt

gSE Processes

ProcessISO/IEC 15939Measurement

ISO/IEC 16085Risk Mgt

ISO/IEC 16326Project Mgt

Governance Assessment Quality Mgt

ToolsISO/IEC xxxxxCM Tool ReqtsC

xxx

Test

ProcessElaborations

gj g

ISO/IEC 250xxSW Quality

ISO/IEC xxxxxReqts Engrg

ISO/IEC14764SW Maint

Application ISO/IEC 24783 ISO/IEC 90003

ToolsISO/IEC 24766RE Tool ReqtsIS

O/IE

CSW

TArtifact Supplemental

ApplicationGuides




to Systems


to SW

23

ArtifactDescriptions

ISO/IEC 42010ArchitectureDescription

SupplementalGuidance

ISO/IEC 24774Process

Definition

ISO/IEC 15289Documentation

The top layer contains the

Need a Common Taxonomy – Another Candidate24765

Vocabulary

24748 Guide to

TerminologyThe top layer contains the documents prescribing terms and vocabulary.

Thi l t i ( ll ) 24748 Guide to Life Cycle

Management

Overall Guide

This layer contains (usually) one document providing overall guidance for the entire collection.

This layer contains one or more 12207 SW Life Cycle

Processes

15288 System Life Cycle Processes

Principles

This layer contains one or more documents that describe principles of objectives for use of the standards in the collection.

15504 Process Assessment

15289 Life Cycle Data

16326 Project Management

Element Standards

This layer contains the detailed standards.

xxxxx Guide for Application to

Services

15271 Guide to 12207

Application Guides &

Supplements

This layer contains guides and supplements that give advice for using the standards in various situations.

24744 Life Cycle Process

DefinitionTechniques

This layer describes techniques that may be helpful in describing or implementing the provisions of the higher level documents.

xxxxx IDEF0

24An (incomplete) example of applying the layered approach to Life Cycle Process standards

Adapted from: James W. Moore, Software Engineering Standards: A Users Road Map, John Wiley & Sons, 1997 – Used with permission from James Moore..

Other Needs• Identification of related standards within

and between SDOsand between SDOs

• Tie more SDOs into integration efforts gthrough joint partnering agreements

• Establish long-term visions and plans to accomplish integration efforts

• Communicate, Cooperate, Collaborate

25

Looking to the FuturePossible structure15288 & 12207 H i ti P j t

ISO/IEC 15288 & 12207 Lif C l P

Possible structure

Foundation Standards for

15288 & 12207 Harmonization Project

Life Cycle Processes standards family

Top level Life Cycle Processes standard

- Common Guide(s) for A li ti

Standards for Process Def,

Vocab, Documentation

Lower level Life Cycle Processes standard(s)

Appliccationof Life Cycle Processes standard(s)

ISO/IEC15504Process

Assessment suite

- Unique per domain or disciplineISO 9000 family of

standards -Quality

Management Related

Processes standards

(ISO/IEC15939, etc )

gSystem

Related Processes standards

(ISO/IEC15939,


(ISO/IEC15939


Influence on and collaboration withexternal standardsetc.)( ,

etc.)(ISO/IEC15939, etc.)

standards(ISO/IEC15939,

etc.)

external standards(e.g., IEEE 1220

and EIA/ANSI 632)

26

The Concept is Proven – Now More Plans for Harmonized Standards and Collaboration Between SDOs are Needed

For More Information:

• Doug Thiele • James Moore– ISO/IEC JTC1/SC7 WG7

Convener– [email protected]

– Alignment Editor– [email protected]

• Cheryl Jonesg @ g• Garry Roedler

– ISO/IEC 15288 Project Editorj dl @l

Cheryl Jones– ISO/IEC 15288 Co-Editor– [email protected]

– [email protected]• Terry Doran

– ISO/IEC 12207 Project Editor

• Anatol Kark– ISO/IEC 12207 Co-Editor– [email protected]

– [email protected]• Dick Kitterman

ISO/IEC TR 24748 P j t

[email protected]

– ISO/IEC TR 24748 Project Editor

– [email protected]

27

Documents

Is An Integrated Set of Systems and SoftwareSystems … 12207:1995, SW Life Cycle Common Life Cycle Processes Unified Process Set Assessment & Governance ISO/IEC 12207:2008, SW Life