12207 SPIWG

An Introduction to IEEE/EIA 12207

498

2167A 1220 7

5000.1

9000

CMM

3405.1 J-016 1679

5000.2-R

by Software Engineering Process Office (SEPO - D12) Software Process Improvement Working Group (SPIWG) October 13, 1999

Software Engineering Process Office

12207 SPIWG

Outline
Background of IEEE/EIA 12207 Structure of the standard Its Life Cycle Processes 12207 vs. 2167A and 498 How it relates to the SW-CMM How to tailor it for your use

How to use it on a project

How to get a copy of it

Software Engineering Process Office

12207 SPIWG

Are there TWO 12207s? ISO/IEC 12207: Information Technology - Software Life Cycle Processes
published in 1995 by International Organization for Standardization International Electrotechnical Commission Provides common framework for developing and managing software
INTERNATIONAL STANDARD ISO/IEC Information technology Software life cycle processes ISO/IEC 12207: 1995(E)
1 1.1 Scope Purpose

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes the software portion of firmware. This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes. 1.2 Field of application

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation.
NOTE: The processes used during the software life cycle need to be compatible with the processes used during the system life cycle.

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains. This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. 1.3 Tailoring of the International Standard

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks.
NOTE: The processes used during the software life cycle need to be compatible with the processes.

IEEE/EIA 12207: Software Life Cycle Processes

published in 1998 by Institute of Electrical and Electronics Engineers Electronic Industries Association
Includes ISO/IEC 12207 in its entirety Adds clarifications, concepts, and guidelines to foster better understanding and application Adopted for use by DoD on May 27,1998 Designated by SSC SD for life cycle processes Software Engineering Process Office
INTERNATIONAL STANDARD ISO/IEC Information technology Software life cycle processes ISO/IEC 12207: 1995(E)
1 Scope

IEEE/EIA 12207.0-1996
(A Joint Standard Developed by IEEE and EIA)

Reproduced by GLOBAL ENGINEERING DOCUMENTS 1.1 Purpose With The Permission of IEEE Under Royalty Agreement

IEEE/EIA Standard

This International Standard establishes a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains software, a stand-alone software product, and software service and during the supply, development, operation, and maintenance of software products. Software includes the software portion of firmware. This International Standard also provides a process that can be employed for defining, controlling, and improving software life cycle processes.

Industry Implementation of 1.2 Field International of application Standard This International Standard ISO/IEC 12207 : 1995 establishes

a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of

a system that contains software, a stand-alone (ISO/IEC 12207) Standardoperation. software product, and software service and for Information during the supply, development, TechnologyNOTE: The processes used during the software life cycle need to be compatible with the processes used during the system life cycle.

Software life cycle processes This International Standard establishes

a common framework for software life cycle processes, with well-defined terminology, that can be referenced by the software industry. It contains processes, activities, and tasks that are to be applied during the acquisition of a system that contains. This International Standard establishes a common framework for software life cycle

processes, with well-defined terminology, that can be referenced by the software industry. March 1998 1.3 Tailoring of the International Standard

processes, with well-defined terminology, that can be referenced by the THE INSTITUTE OF ELECTRICAL ELECTRONIC INDUSTRIES ASSOCIATION It contains processes, activities, and tasks. AND ELECTRONICS ENGINEERING DEPARTMENT ENGINEERS, INC.

This International Standard establishes a common framework for software life cycle software industry.

NOTE: The processes used during the software life cycle need to be compatible with the processes.

12207 SPIWG

The Purpose of 12207

Establish a common framework for software life-cycle processes, with well-defined terminology that can be referenced by the software industry. To acquire, supply, develop, operate, and maintain software products
To define, control, and improve software life cycle processes

12207 provides industry a basis for software practices usable for both national and international business

Software Engineering Process Office

12207 SPIWG

IEEE/EIA 12207 Has Many Uses

To acquire, supply, develop, operate, and maintain software To support the above functions in the form of quality assurance, configuration management, joint reviews, audits, verification, validation, problem resolution, and documentation

To manage and improve the organizations processes and personnel

To establish software management and engineering environments based upon the life cycle processes as adapted and tailored to serve business needs

To foster improved understanding between customers and vendors and among the parties involved in the life cycle of a software product
To facilitate world trade in software

- 12207.0 Forward Software Engineering Process Office

12207 SPIWG

Why Use Standards?

Establish uniform requirements for development and documentation Define a common framework for software life cycle processes Clarify the roles and interfaces of participants Clarify the types and contents of documentation Identify the tasks, phases, baselines, reviews, and documents needed Follow the lessons learned and best practices of the industry Avoid the pitfalls and problems of the past

Software Engineering Process Office

12207 SPIWG

Dont Get Caught in the Standards Quagmire

From the SPCs http://www.software.org/Quagmire/

Software Engineering Process Office

12207 SPIWG

The Evolution of Standards Affecting DoD Software Development

MIL-STD-1679A DOD-STD-2167A DOD-STD-7935A MIL-STD-498 Software Development Defense System Software Development AIS Documentation Standards Software Development and Documentation 1983 1988 1988 1994

(SecDef Perry Memo - June 1994)

ISO 9000 (series - on Quality Management, etc.) J-STD-016-1995 Software Development Acquirer-Supplier Agreement ISO/IEC 12207 Information Technology - Software Life Cycle Processes IEEE/EIA 12207 Software Life Cycle Processes 19911995

1996
1998

Software Engineering Process Office

12207 SPIWG

The Family Tree of Standards

DOD-STD-2167A Defense System Software Development Feb 88 ISO/IEC 12207 Software Life Cycle Processes Aug 95

ISO 12207

IEEE Stds

2167A
498 7935A
DOD-STD-7935A DoD Automated Information Systems (AIS) Documentation Standards Oct 88 MIL-STD-498 Software Development and Documentation Dec 94

016
J-STD-016-1995 (Trial Use) Software Life Cycle Processes, Software Development Sep 95

IEEE/EIA 12207
IEEE/EIA 12207.0-1996 IEEE/EIA 12207.1-1997 IEEE/EIA 12207.2-1997 Software Life Cycle Processes Mar/Apr 98

Software Engineering Process Office

12207 SPIWG

Outline of IEEE/EIA 12207.0: Software Life Cycle Processes

IEEE/EIA 12207.0-1996
Reproduced by GLOBAL ENGINEERING DOCUMENTS With The Permission of IEEE Under Royalty Agreement

(A Joint Standard Developed by IEEE and EIA)

IEEE/EIA Standard

Industry Implementation of International Standard ISO/IEC 12207 : 1995 (ISO/IEC 12207) Standard for Information TechnologySoftware life cycle processes

Forward
1. Scope 2. Normative references 3. Definitions

March 1998

THE INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, INC.

ELECTRONIC INDUSTRIES ASSOCIATION ENGINEERING DEPARTMENT

4. Application of this Standard

5. Primary processes 6. Supporting processes 7. Organizational processes Annexes A - D Annexes E - J

total: 85 pages

Software Engineering Process Office

10

12207 SPIWG

Outline of IEEE/EIA 12207.1: Software Life Cycle Processes - Life cycle data
IEEE/EIA 12207.0-1996
Reproduced by GLOBAL ENGINEERING DOCUMENTS With The Permission of IEEE Under Royalty Agreement

(A Joint Standard Developed by IEEE and EIA)

IEEE/EIA Standard

Forward 1. Scope 2. Normative references 3. Definitions 4. Life cycle data 5. Generic info item content guidelines

Industry Implementation of International Standard ISO/IEC 12207 : 1995 (ISO/IEC 12207) Standard for Information TechnologySoftware life cycle processes

March 1998

THE INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, INC.

ELECTRONIC INDUSTRIES ASSOCIATION ENGINEERING DEPARTMENT

6. Specific info item content guidelines

Annex A - References

total: 36 pages

Software Engineering Process Office

11

12207 SPIWG

Outline of IEEE/EIA 12207.2: Software Life Cycle Processes Implementation considerations

IEEE/EIA 12207.0-1996
Reproduced by GLOBAL ENGINEERING DOCUMENTS With The Permission of IEEE Under Royalty Agreement

(A Joint Standard Developed by IEEE and EIA)

IEEE/EIA Standard

Forward and introduction

Industry Implementation of International Standard ISO/IEC 12207 : 1995 (ISO/IEC 12207) Standard for Information TechnologySoftware life cycle processes

1. Scope
2. Normative references 3. Definitions 4. Application

March 1998

THE INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, INC.

ELECTRONIC INDUSTRIES ASSOCIATION ENGINEERING DEPARTMENT

5. Primary processes
6. Supporting processes 7. Organizational processes Annexes A - M
Repeats 12207.0 clauses with additional guidance total: 109 pages

Software Engineering Process Office

12

12207 SPIWG

Terminology used in 12207 (both of em)

17 Life Cycle Processes 5 Primary Processes 8 Supporting Processes 4 Organizational Processes

- 12207.0 5 - 12207.0 6 - 12207.0 7

Each Process is broken down into Activities Each Activity is broken down into Tasks Tasks reference Information Items (software products/documents) 84 items in matrix Generic guidelines for 7 categories Specific guidelines for 30
Aed repf dbmezrt

- 12207.1 4.3 - 12207.1 5 - 12207.1 6

(Note: = Clause/Section) Software Engineering Process Office

13

12207 SPIWG

12207s five Primary Life Cycle Processes

The primary processes define what the organization elements do during the software life cycle. Process Role 498 term Acquisition Acquirer - an organization that Acquirer procures a system or service Supplier - an organization that enters into contract with acquirer under terms of the contract Developer - organization that performs development during the life cycle process Maintainer - an organization that performs maintenance activities Operator - an organization that operates the system User - An individual or organization that uses the system for a specific function

Supply

Development

Developer

Maintenance Operation

(Support Agency)

(User)

Software Engineering Process Office

14

12207 SPIWG

Examples of Life Cycle Roles

Role

Teens Truck

Navy System

Acquirer (Buyer)
Supplier (Vendor) Developer Maintainer Operator User

Mom and Dad

Eds Car Lot Ford Motor

Systems Command, PD-xx

Systems Center D555 Cool Coders Corp. Systems Center D999 Pacific Fleet Ships watch team

Terrys Tuneup Shop Familys Teenagers A teenager

Software Engineering Process Office

15

12207 SPIWG

12207s Organizational and Supporting Processes

Organizational Life Cycle Processes - typically outside the realm of specific projects and contracts. Should be in place prior to performing primary processes. Management Infrastructure Improvement Training Supporting Processes - employed and executed by another process. Responsibility of the organization. Documentation Configuration Management Quality Assurance Verification Validation Joint Review Audit Problem Resolution
Software Engineering Process Office

16

12207 SPIWG

How The Life Cycle Processes Interact

ACQUISITION MAINTENANCE

contract

MANAGEMENT

OPERATION

SUPPLY

DEVELOPMENT

CM
QA

DOCUMENTATION
JOINT REVIEW

PROB. RES.
AUDIT

VERIFICATION
VALIDATION

SUPPORTING PROCESSES
INFRASTRUCTURE TRAINING IMPROVEMENT

ORGANIZATIONAL PROCESSES

Software Engineering Process Office

17

12207 SPIWG

The Three Software Life-Cycle Development Strategies

Program Strategy Define All Requirements First? Yes Yes No Multiple Development Cycles No Yes Yes Distribute Interim Software? No Maybe Yes

Once-Through (Waterfall)
Incremental (Preplanned Product Improvement)

Evolutionary

From IEEE/EIA 12207.2 Annex I

These are recommended by SSC SD as the basis for project planning and implementation.

Software Engineering Process Office

18

12207 SPIWG

A Sample 12207 Development Process

One example of applying 12207 to the Waterfall development strategy
Process Implementation Activity DPP, SDSD Software Qual Test Software IntegraSoftware tion SCR, T/VRR Code Software Item 1: Software & Test SIP,T/VPr Software Detailed Design EOCR, SCR,T/VPr, T/VRR Arch. Software Design Reqts. SRD, UDD Analysis Software SAD, SIDD, DBDD, T/VP Qual Test SRD, UDD Software IntegraSoftware tion Code Software Item 2: Software & Test Software Detailed Design Arch. Software Design Reqts. Analysis Hardware items

Software Installation

SARAD Sys Arch Design System Reqts Analysis SRS

System Integration
T/VPr T/VRR

System Qual Test

T/VRR SCR

Software Acceptance Support T/VRR SCR

Supporting Processes: Documentation, CM, QA, Verification, Validation, Joint Review, Audit, Problem resolution SCMP, SCMR, SCIR, SQAP, SQAR, SVRR, PR/PRR Organizational Processes: Management, Infrastructure, Improvement, Training

Software Engineering Process Office

19

12207 SPIWG

The 30 12207.1 Information Items

Descriptions Concept of operations description Database design description Software architecture description Software design description Software devel. standards descr. Software interface design descr. Software requirements description Sys. arch.& reqts. alloc. descr. User documentation description Plans Acquisition plan Development process plan Maintenance process plan Operation process plan Project management plan Software CM plan Software integration plan Software QA plan Test or validation plan Procedures Test or validation procedures Record Evaluation records Executable object code record Software configuration index record Software CM records Software QA records Source code record Report Problem report & prob. resolution report Software verification results report Test or validation results report Request Change request or modification request Specification System requirements specification

Software Engineering Process Office

20

12207 SPIWG

12207s Guidance for the Information Items

Guidance
12207.0: General output/artifact requirements within Process/activities/task descriptions 12207.1 4.3 Table 1: Available standards, guides, references for example and assistance on 84 information items

Example
5.3.1.4: The developer shall develop plans for conducting the activities of the development process. The plans should include (5 topics) For development process plan (5.3.1.4), see: J-STD-016 E.2.1: contents of Software Development Plan (like 498) IEEE 1074 Standard for Developing Software Life Cycle Processes IEEE 1074.1 Guide for Developing Software Life Cycle Processes and 2 others 5.2.2 A plan should include planning activities and tasks, schedules, estimates, risks, cost, interfaces, (20 topics) 6.5 The development process plan should include specific standards, methods, tools, actions associated with the development (8 topics)

12207.1 5: Generic content guidelines for 7 kinds of item: description, plan, procedure, record, report, request, specification 12207.1 6: Specific content guidelines for 30 information Items

Software Engineering Process Office

21

12207 SPIWG

12207s Management Process

An Organizational Life Cycle Process - 12207.0 7.1
Defines the basic activities of the management, including project management, related to the execution of a life cycle process. Activity Tasks 1 Initiation and .1 Establish the requirements for management scope definition .2 Check resources: personnel, materials, etc. .3 Modify requirements to achieve criteria 2 Planning .1 Plan efforts, schedules, tasks, duties, costs (in Management process plan) 3 Execution and .1 Implement plan to meet objectives control .2 Monitor process .3 Investigate and resolve problems .4 Report progress 4 Review and .1 Ensure products and plans are evaluated evaluation .2 Assess evaluation results 5 Closure .1 Determine when process is complete .2 Check results for completeness

Software Engineering Process Office

22

12207s Maintenance Process

A Primary Life Cycle Process - 12207.0 5.5

12207 SPIWG

Defines the basic activities of the maintainer: managing modifications to the software product to keep it current and in operational fitness.
Activity 1 Process Implementation Tasks Document maintenance activities (in Maintenance process plan). Document problem tracking procedures. Manage modifications to the system. 2 Problem and modification Analyze problem reports. Replicate or verify analysis problems. Develop modifications. Document problems, analysis, fixes (with Modification request). Get modifications approved per contract. 3 Modification implementation Document where changes are needed. Implement modifications (use Development Process). 4 Maintenance review/ Review integrity of modified system. Get approval for acceptance modifications per contract. 5 Migration Ensure products meet with this standard. Develop and use Migration Plan. Notify users of migration. Conduct parallel operations if needed. Notify all concerned, archive all records. Perform post-op review of changes. Keep data from old environment. 6 Software retirement Document plans for retirement. Notify all users of plans and activities. Conduct parallel operations. Notify all concerned, archive all records. Keep data from retired product per contract.

Software Engineering Process Office

23

12207 SPIWG

What about the Software Development Plan?

Management Process calls for plans for execution of the process.
12207.0 7.1.2.1 lists 9 topics for inclusion 12207.1 4.3 Table 1 includes Management process plan, refers to
IEEE 1058.1: Standard for Software Project Management Plans

12207.1 5.2 gives 20 items of Generic content of a Plan

Supply Process calls for project management plan(s)

12207.0 5.2.4.5 lists 15 topics to be considered 12207.1 4.3 Table 1 includes Project management plan, references include
IEEE 1058.1: Standard for Software Project Management Plans J-STD-016 E.2.1: contents of Software Development Plan (like 498) IEEE 1074 Standard for Developing Software Life Cycle Processes IEEE 1074.1 Guide for Developing Software Life Cycle Processes

12207.1 5.2 gives 20 items of Generic content of a Plan 12207.1 6.11 gives 18 items for Project management plan

Development Process calls for plans for conducting the activities of the development process
12207.0 5.3.1.4 lists 7 topics for inclusion 12207.1 4.3 Table 1 includes Development process plan, references include
ASTM E622 Guide for Developing Computerized Systems ASTM E1340 Guide for Rapid Prototyping of Computerized Systems J-STD-016 E.2.1: contents of Software Development Plan (like 498)

Software Engineering Process Office

12207.1 5.2 gives 20 items of Generic content of a Plan 12207.1 6.5 gives 13 items for Development process plan - may be part of Project management plan

24

12207 SPIWG

Can you Tailor 12207?

Software Engineering Process Office

25

12207 SPIWG

Tailoring 12207
12207 should be tailored for a project - no two projects are the same Tailoring considerations: Life cycle activity: prototyping, maintenance Software characteristics: COTS, reuse, embedded firmware Your orgs policies, languages, hardware reserve, culture Acquisition strategy: contract type, contractor involvement Life cycle strategy: waterfall, evolutionary, spiral, etc. The Tailoring Process (12207.0 Annex A) 1. Identify project environment - strategy, activity, requirements 2. Solicit inputs - from users, support team, potential bidders 3. Select processes, activities, documentation, responsibilities 4. Document tailoring decisions and rationale SEPOs guidance on tailoring: What CANT be tailored: the intent or objectives What CAN be tailored: number of phases/activities, roles, responsibilities, document formats, formality/frequency of reports or reviews
(see Tailoring Guidelines in Description of SSC SD Software Process Assets, at http://sepo.spawar.navy.mil/sepo/docs.html under OPD)

Software Engineering Process Office

26

12207 SPIWG

How does 12207 Compare to Previous Standards?

DOD-STD-2167A: Defense System Software Development
Published: 29 February 1988 Superseded by MIL-STD-498 on 5 December 1994 May still remain valid on many contracts

MIL-STD-498: Software Development and Documentation

Published: 5 December 1994 Cancelled: 27 May 1998. superseded by IEEE/EIA 12207. May still remain valid on many contracts.

SecDef Memo Specifications and Standards - A New Way of Doing Business

Issued 29 June 1994: Use performance and commercial specifications and standards in lieu of military specifications and standards, unless no practical alternative exists...

J-STD-016-1995: Software Development - Acquirer-Supplier Agreement

Published: 30 September 1995 as Trial Use Standard by IEEE/EIA Objective: replace MIL-STD with a non-government equivalent Almost identical to MIL-STD-498 with changes in traceability, terminology

Software Engineering Process Office

27

12207 SPIWG

DOD-STD-2167A Deliverables, Reviews, Baselines

PHASE

SYS REQTS ANALYSIS

SYSTEM DESIGN

SOFTWARE REQTS ANALYSIS

PRELIM DESIGN

DETAILED DESIGN

CODING CSC INTEG. CSC AND CSU AND TEST TESTING TESTING
SOURCE CODE LISTINGS SOURCE CODE

SYSTEM INTEG. AND TEST

PRELIM SYS SPEC DELIVERABLE PRODUCTS

SYSTEM SPEC

PRELIM SDD

DETAILED SDD

SYS/SEG DESIGN DOC

SOFTWARE TEST PLAN

UPDATED SOURCE CODE

PRELIM SW REQTS SPEC

PRELIM IFACE REQTS SOFTWARE DEVEL. PLAN

SOFTWARE REQTS SPEC

IFACE REQTS SPEC PRELIM IFACE DES DOC

SW TEST DESCR. (CASES)

IFACE DESIGN DOC

SW TEST DESCR. (PROC)

SW TEST REPORTS

OPERATION & SUPRT DOCS VERSION DESCR. DOC SOFTWARE

DEVELOPMENTAL CONFIGURATION PRODUCT REVIEWS AND AUDITS BASELINES SPEC

SRR

SDR
FUNCTIONAL BASELINE

SSR
ALLOCATED BASELINE

PDR

CDR

TRR

F/PCA
PRODUCT BASELINE

Software Engineering Process Office

28

12207 SPIWG

Sample MIL-STD-498 Life Cycle

Project planning and oversight SDP STP SIP/STrP Software Item Qual Test STR

Software Item 1:

SoftSoftware ware Reqts. Design Analysis SDD/IDD/DBDD SRS/IRS Software Item 2:

Software Impl. & Unit Test

Unit Integ/ Test STD

Prepare for Software Use Executable SW SVDs User/op manual

Sys Qual Test Unit Integ/ Test STD Software Item Qual Test SW/HW Item Integ/Test STD STR

SSDD/IDD System Design System Reqts. Analysis OCD SSS/IRS

SoftSoftware ware Reqts. Design Analysis SDD/IDD/DBDD SRS/IRS

Software Impl. & Unit Test

STR

Prepare for SW Transition Executable SW Source files SVDs SPSs Updated SSDDs Maint. manuals

Hardware item(s) (not covered by this standard)

Other ongoing activities: SQA, SCM, Reviews, Risk Management, Process Improvement, etc.

Software Engineering Process Office

29

12207 SPIWG

MIL-STD-498 Data Item Descriptions

and

J-STD-016-1995 Software Product Descriptions

Planning
Software Development Plan (SDP) Software Test Plan (STP) Software Installation Plan (SIP) Software Transition Plan STrP)

Qualification Testing
Software Test Description (STD) Software Test Report (STR)

Maintenance
Software Product Specification (SPS) Software Version Description (SVD) Computer Programming Manual (CPM) Firmware Support Manual (FSM)

Concept and Requirements

Operational Concept Descr. (OCD) System/Subsystem Spec. (SSS) Interface Requirements Spec. (IRS) Software Requirements Spec. (SRS)

User/Operator
Software User Manual (SUM) Software Input/Output Manual (SIOM) Software Center Operator Manual (SCOM) Computer Operation Manual (COM)

Design
System/Subsys. Design Descr. (SSDD) Interface Design Description (IDD) Database Design Description (DBDD) Software Design Description (SDD)

MIL-STD-498 DIDs are still in effect! Software Engineering Process Office

30

12207 SPIWG

How do the Standards Compare?

Focus DoD-STD-2167A Defense software products 9 development phases, biased to waterfall MIL-STD-498 Defense software development process Expands planning, use. Waterfall, incremental, evolutionary 22 formal DIDs IEEE/EIA 12207 Enterprise processes Expands support. Once-through, incremental, evolutionary 30 Information Items - guides Similar to 498

Software life cycle

52 formal DIDs Document requirements Program Reviews

10 Formal Reviews 11 candidate mgmt. MIL-STD-1521B reviews, brief guidelines Limited Coverage for Scant planning, QA, CM, maint. Roles Government, Contractor Acquirer, Developer

Specified processes Acquirer,Supplier, Developer, Maintainer, Operator

Software Engineering Process Office

31

12207 SPIWG

How have the Development Activities Changed?

2167A Activities (9)
Sys reqts analysis System design Software reqts analysis Preliminary design Detailed design Coding & CSU testing CSC integr. & testing CSCI testing Sys integr. & testing Unit integration & test CSCI qual. testing CSCI/HWCI int. & test System qual testing Prep: software use Prep: software tranistion
Sware

498 Activities (13)

Proj. plan & oversight Establish dev. environ. Sys. reqts. analysis System design Software reqts analysis Software design

12207 Activities (13)

Process Implementation Sys. reqts. analysis Sys. arch. design Software reqts analysis Software arch. design Software detailed design

Software impl. & unit test Software code & test Software integration Software qual testing System integration System qual testing Software installation Software accept support

Software Engineering Process Office

32

12207 SPIWG

Have the Management Reviews changed?

DOD-STD-2167A Formal Reviews (10) MIL-STD-498 Joint Mgmt. Reviews (11) Software plan review Operational concept review System/subsys. reqts rev. System/subsys. design rev. Software reqts review IEEE/EIA 12207 Project mgmt. reviews (11) Software plan review Operational concept review System/subsys. reqts rev. System/subsys design rev. Software reqts. review Software design review Test readiness review Test results review -Software maintenance rev. Software supportability rev. Critical reqts. review (FCA in IEEE Std 1042) (PCA in IEEE Std 1042) -(see 12207.2 Annex G) (see also IEEE Std 1028)

System Reqts. Rev.(SRR) System Design Rev.(SDR) Software Spec. Rev. (SSR) Prelim Design Rev. (PDR) Critical Design Rev. (CDR) Test Readiness Rev. (TRR)

Software design review Test readiness review Test results review Production Readiness Rev(PRR) -Software usability review Software supportability rev. Critical reqts. review Functional Config Audit (FCA) Physical Config Audit (PCA) Formal Qual. Review (FQR) (see MIL-STD-1521B) (FCA in MIL-STD-973) (PCA in MIL-STD-973) (dropped by MIL-STD-073) (see 498 Appendix E)

Software Engineering Process Office

33

12207 SPIWG

Wordsmithing the Review and Document Names

DoD-STD-2167A Formal Reviews/ Related Documents System Reqts Review (SRR) System/Segment Spec System Design Review (SDR) System/Segment Spec Software Devel. Plan Software Reqts Spec Interface Reqts Spec Software Spec Review (SSR) Software Reqts Spec Interface Reqts Spec Software Test Plan Software Users Manual Prelim. Design Review (PDR) Software Design Document Interface Design Document Critical Design Review (CDR) Software Design Document Interface Design Document Software Test Description Test Readiness Review (TRR) Software Test Description Software Devel. Folders MIL-STD-498 Joint Mgmt. Reviews/ Related Documents System/subsys reqts. review System/subsystem spec System/subsys design review System/subsystem spec Software Devel. Plan Software Reqts Spec Interface Reqts Spec Software Reqts Review Software Reqts Spec Interface Reqts Spec Software Test Plan Software User Manual Software Design Review Software Design Descr. Interface Design Descr. Software Design Review Software Design Descr. Interface Design Descr. Software Test Descr. Test Readiness Review Software Test Description Software Devel. Folders IEEE/EIA 12207 Project Mgmt. Reviews/ Related Documents System/subsys reqts review System requirements spec System/subsys design review System reqts description Development process plan Software reqts description Software reqts description Software reqts review Software reqts description Software reqts description Software integration plan User documentation descr. Software design review Software arch description Software Iface design descr Software design review Software design description Software Iface design descr Test or validation procedures Test readiness review Test or validation procedures Software code & test record

* * * *

* * * * * * * * * * * * * * *

* * * * * *

* = Change from previous standard

- Software Management for Executives Guidebook

Software Engineering Process Office

34

12207 SPIWG

Comparing 12207 to the CMM for Software

CMM Key Process Area L2: Requirements Mgmt. Software Project Planing IEEE/EIA 12207.1 Development process, activity 2 and 4 Management process Development process, activity 1 Management process Quality assurance process Configuration management process Acquisition process Improvement process Improvement process Mgmt process, tailoring guidance Training process Development process Joint review process Joint review process

Proj. Track & Oversight Software QA Software CM Software Subctr. Mgmt. L3: Org. Process Focus Org Process Defn. Integ. Software Mgmt. Training Program Software Prod. Engr. Intergroup Coord. Peer Reviews

Software Engineering Process Office

35

12207 SPIWG

How do I Get Copies of 12207?

Hard copies of IEEE/EIA 12207 available from IEEE Print: 236 pages $182.00 IEEE Mbr: $146.00 PDF: $273.00 IEEE Mbr: $218.00

see http://standards.ieee.org
With IEEE username & password, download from
http://standards.ieee.org/catalog/olis/search.html

Review the Defense Automated Printing Service (DAPS) ASSIST Online webpage at http://astimage.daps.dla.mil/online/ IEEE/EIA 12207 can be downloaded to government users with DoD Single Stock Point accounts from http://assist.daps.mil/
Choose Assist Quick Search then Document Number = 12207

Hard copies of 12207 can be ordered from DAPS, see

http://www.stsc.hill.af.mil/DOC/std12207ad.doc

Review SSC Technical Library documents and suppliers at

http://iweb.spawar.navy.mil/services/sti/library/

Software Engineering Process Office

36

12207 SPIWG

How do I Get Copies of Other Standards?

MIL-STD-498 and DIDs on SEPOs webpage at
http://sepo.spawar.navy.mil/

DoD and other standards can be downloaded from the Defense Automated Printing Service (DAPS) ASSIST Online webpage at
http://astimage.daps.dla.mil/online/

Users have to register for many documents, but the Assist QuickSearch (lower right icon) can be used for the following: MIL-STD-498, all DIDs, and the cancellation notice available at
http://assist.daps.mil/ - choose Assist Quick Seach and enter document number

Hard copies of cancelled DOD specifications and standards can be obtained from the DoD Single Stock Point (DoDSSP) at
http://www.dodssp.daps.mil/

Review SSC Technical Library documents and suppliers at

http://iweb.spawar.navy.mil/services/sti/library/

Software Engineering Process Office

37

12207 SPIWG

The Cliff Notes: Overview of IEEE/EIA12207

(attached to this handout)

* * * *

13-page summary of all three volumes and annexes Tabular lists of processes, activities, tasks, and related info items Cross references: Info Item to activity - and vice versa Comparison of 498 activities to 12207 Comparison of program reviews among 2167A/1521B, 498, 12207 Comparison of documents among 2167A, 498, J-016, 12207

(also online at http://sepo.spawar.navy.mil/sepo/Standards.html )

Software Engineering Process Office

38

12207 SPIWG

SEPO Recommends:
Use IEEE/EIA 12207: It is the standard of DoD and SSC-SD

It models all major roles and interfaces

It achieves breadth of ISO/IEC 12207 and depth of MIL-STD-498 Relate 12207, the CMMs, ISO 9000, and other standards of interest to the activities within your project

Tailor all standards for your organization/project/contract

Reconcile conflicts of language and guidance within different standards related to the same activity

Software Engineering Process Office

39

12207 SPIWG

References
- Capability Maturity Model For Software, Version 1.1, SEI-93-TR-24, Feb. 1993.
On web at http://rbse.jsc.nasa.gov:80/cmm/

- IEEE Standards Collection: Software Engineering. 1997 Edition, Institute of Electrical and Electronics Engineers, Inc. New York, NY.
See http://www.ieee.org/prod_svcs.html

- 9000: Quality Management, International Organization for Standardization, 1994. See http://www.iso.ch/welcome.html - The ISO 9000 Implementation Manual, Omneo- Oliver Wight Publications, 1994. In SEPO library. - U.S. Software Lifecycle Process Standards, Crosstalk, July 1997. See
http://www.stsc.hill.af.mil/

- Defense Acquisition Policy - A More Flexible Management Approach. Program Manager magazine, July-August 1996. See
http://www.dsmc.dsm.mil/pubs/pdf/pm_articles96.htm

- Software Engineering Standards - A User's Road Map. IEEE Computer Society, Nov. 1997.
See http://www.computer.muni.cz/cspress/CATALOG/bp08008.htm

Software Engineering Process Office

40