Slide 1 Systems Engineering and Software Engineering Processes, Products, and People from a Standards Perspective (Subtitle: Stand on the Standards) A

Slide 1

Systems Engineering and Software EngineeringProcesses, Products, and People

from aStandards Perspective

(Subtitle: Stand on the Standards)

A Tutorial Presented to theHampton Roads Area and Southern Maryland Chapters of INCOSE

Systems Engineering Seminar 2003November 13, 2003

John O. ClarkChief Engineer

Warfare Systems EngineeringDefense Mission Systems

Northrop Grumman Information Technology

Slide 2

Overview

• Heritage of Systems Engineering and Software Engineering Standards

• What is a System?• What is Systems Engineering?• What is Systems Engineering Management?• Standards Process Overviews• User Scorecard• Standards Detailed Overviews• Future of Systems Engineering and Software

Engineering Standards• Recommendations & Summary

Revision A of Tutorial H04 Presented at the INCOSE 2003 Annual International Symposium

Washington, DCJune 30, 2003

Slide 3

• All EIA, IEEE, ANSI, and ISO/IEC copyright material has been removed from this version in order to provide this version in softcopy. Refer to the figures in the standards.

• INCOSE Systems Engineering Handbook, Version 2.0, July 2000, Copyright © 2002 by INCOSE, subject to the following restrictions: INCOSE use. Permission to reproduce this document and to prepare derivative works from this document for INCOSE use is granted, provided this copyright notice is included with all reproductions and derivative works.

Copyright Accreditation

Accreditation

From _________. Copyright ________. All rights reserved.

Slide 4

INCOSE & JOC

EIA/IS-632

1980

Instructions/Handbooks/

Manuals/Guides

IEEE 12201994

DIDs

ANSI/EIA-632

ISO/IEC15288

IEEE/EIA12207

MIL-STD-499A

MIL-STD-499

SystemsEngineering

ISO/IEC12207

MIL-STD-498

DOD-STD-2167

DOD-STD-2167A

DOD-STD-1703

DOD-STD-7935A

DIDs

MIL-STD-1679A

1985

1998 1994

1998 1994

1974 1969

1999-2002

1999

2002

1994

1987

1988

1988

1994

1995 1998

2003+

IEEE 1498/EIA 640

1995

(Draft)

(Trial Use)

(Interim)

(NotReleased)

Sec PerryLetterJan 1994

SoftwareEngineering

1968-

Data Item Descriptions

Primary Focus of this Tutorial

MIL-Std-499B

ISO/IEC1528812207

Harmon

2003+

MIL-STD-1679

1968-

ISO/IEC19760Guide

2003

CMMI

(SE-CM)

MIL-STD-961D

1995 Defense Specifications

ISO/IEC15288IEEE1220

Harmon

2003+

MIL-STDs to Commercial Stds to CMMs

Heritage of SE and SW Standards

EIA/IEEEJ-STD-016

1995

(Interim)

IEEE 12201998

EIA/IS-731

MIL-STD-961E

2003

Supercedes

Derived From

Slide 5

Dod-Std-2167A

Dod-Std-7935A

SoftwareEngineering

SystemsEngineering

Others ...

Dod-Std-1703

Mil-Std-498

EIA/IS 731SE Capab Model

1998

ISO/IEC15288

2002

1987

1988

1988

1994

ISO/IEC12207

1995IEEE/EIA

12207

1996

IEEE 1498/EIA 640

1995

(Draft)

Heritage of SE and SW Standards (cont)

Mil-Std-499

Mil-Std-499A

Mil-Std-499B

EIA/IS632

IEEE1220

1969 1974 1994

1994

1994 1998

(Trial Use)

EIA/IEEE J-Std-016

1995

(Interim)

(Interim)

INCOSE SEHandbook V2

2000

NAVAIRSE Guide

2003

CMMI

Updated From INCOSE SE Handbook. Copyright 2002. All rights reserved.

ANSI/EIA632

1998

Referenced In

Based On

DSMC/DMUSE Fundamentals

IEEE1220

1999

V2A

2004

INCOSE & JOC

2005

V3

Slide 6

Processes

People

SystemPro

duct

s

PeopleProducts Processes

System

From EIA/IS-632-1994. Copyright 1995 EIA. All rights reserved.

EIA/IS-632-1994

What is a System? (cont)

EIA/IS-632 & JOCKey Terms

Slide 7

System/Subsystem Design Description (SSDD)System Specification (SS) (MIL-STD-961D)

Requirements

Requirement: “Noun shall verb.” Example: The car shall stop within 100 feet at 50 mph.

Functional PerformanceFunction: “Verb Noun.” Example: Stop Car or “Verb-ing.” Example: Stopping.

Component: “Noun.” Example: Brake.

Functions Components

System/Subsystem Specification (SSS)System Requirements Document (SRD)System Requirements Specification (SRS)

(SSDD/SS)

What is Systems Engineering? (cont)

JOCKey Terms and Relationships

Slide 8

• Functional Requirement: What?• Performance Requirement: How well?• Capability: A group of related requirements. Synonyms include

function, subject, object, or other term useful for presenting the requirements.

• Configuration Item (CI): Any item designated for Configuration Mgmt.• Preliminary Design: High-Level Design, one level below (inside) the CI.• Detailed Design: Low-Level Design, lowest level of the CI.• Validation: Right system?• Verification: System right?• Verification Methods: Analysis (including modeling and simulation),

Demonstration, Test, and Inspection.• Use Case: A scenario-driven functional thread through the system.• Decompose: Parse or separate.• Derive: Deduce (e.g., if a=b+c then c=a-b, or I’ll know it when I see it).• Synthesis: Design. Translate requirements (problems) into solutions.


JOCRelated Terms

Slide 9

• Requirements Trade Studies and

• Effectiveness Analysis, etc.

• Physical Design Trade Studies

• Effectiveness Analysis, etc.

Systems Analysis

Assessments• Functional Trade Studies and Assessments• Effectiveness Analysis, etc.

Requirements Analysis• Define Requirements• Define Interfaces• Decompose and Derive Requirements• Define Constraints & Conditions• Define Requirements Architecture• Establish Requirements Baseline

Functional Analysis & Allocation• Define Functions• Allocate Requirements to Functions• Define Functional Interfaces• Decompose Functions to Subfunctions• Allocate Decomposed and Derived Requirements to Subfunctions• Define Functional Architecture• Develop Functional Flow Block Diagrams• Establish Functional Baseline

Physical Design & Allocation• Define Subsystems and Components• Allocate Functions and Subfunctions to Subsystems and Components• Define Subsystem & Component Requirements• Define Subsystem & Component Interfaces• Establish Allocated Baseline• Define Physical Architecture• Develop Physical Flow Block Diagrams• Establish Physical/Product Baseline

JOC

Control

F11 F12 F31

F3F1

Sys

F2

I/F

I/F

I/F I/F

I/F

I/FF32R22 R21

R2R1

SysI/F I/F

R22R11 C1 C2 C3

Sub3Sub1

Sys

Sub2

I/F

I/F

I/F I/F

I/F

I/F

• Risk Management• Configuration & Data Management• Interface Management

• Performance-Based Progress Measurement: - SEMS/IMP & SEDS/IMS - TPMs & Metrics

- Technical Reviews- Earned Value

Design LoopRequirements Loop

Verification Loop

Requirements Architecture Functional Architecture Physical Architecture

• SOW, Deliverables• WBS, SBS, PBS• Work & Planning Packages

Processes, Architectures, and Baselines


and Assessments

Slide 10

1.0 2.0 3.0 4.0 5.0 6.0 7.0TOP

LEVEL F1 F2 F3 F4 F5 F6 F7

2ndLEVEL

1.0 1.1REF

F1 F1.1 OR

1.2

1.3

F1.2

F1.3

1.4

F1.4 AND

F1.5

F1.6

REF

2.0

F2

REF

1.4 1.4.1 1.4.2 1.4.3

F1.4 F1.4.1 F1.4.2 F1.4.33rd

LEVEL F1.5REFG

REF

F1.4.3

G

G

OR 1.4.3.3REF

Fnn

1.4.3.1

F1.4.3.1

1.4.3.2

F1.4.3.2

F1.4.3.3

4thLEVEL


Functional Flow Diagram (FFD) Example INCOSE SE HDBK

From INCOSE SE Handbook, Version 2.0, Copyright 2002 by INCOSE.

Slide 11


DSMCFunctional Flow Block Diagram (FFBD) Example

From DSMC SE Fundamentals, October 1999

Slide 12

Function

Function

Function

Function

Function

1

2

3

4

5

Input

Output (F1)

(F2)

(F3)

(F4)

(F5)Output

Input

F1

F2

F1

F3

F1

F4

F1

F5

F1

F2

F1

F3

F2

F3

F2

F3

F2

F4

F2

F5

F3

F4

F2

F4

F1

F4

F3

F5

F2

F5

F1

F5

F4

F5

F3

F4

F3

F5

F4

F5

INCOSE SE HDBK


One Type of N2 Chart Using Functions


Cells are blank if no interface.

Other uses include interfaces between:• Systems• Spaces• Products• Processes• People, and• Organizations

Note: Doesn’t follow prior FFD example.

Slide 13


Another Type of N2 Chart Using Systems

System 1 System 2 System 3 System 4 System 5

JOC

Cells are blank if no interface.

Cells can contain interface direction, data, status, an X, etc.

System 1

System 2

System 3

System 4

System 5

S1 S1 S1 S1

S1

S1

S1

S1

S2 S2 S2 S2

S2

S2

S2

S2

S3

S3

S3

S3

S3 S3 S3 S3

S4

S4

S4

S4

S4 S4 S4 S4

S5

S5

S5

S5

S5S5S5S5

Slide 14

Accept Card

Accept PIN

DisplayIncorrect PIN

Accept Card

Accept PIN

DisplayMenu

DisplayPin

Request

DisplayIncorrect

PIN

DisplayMENU

ATM Card

PIN

ATM Card

PIN

Scenario 1 Bad PINScenario 2 Good PIN

DisplayPin

Request


Functional Thread Analysis / Use Cases


INCOSE SE HDBK

Requirements Specifications and Test Procedures can be written using Use Cases.

Slide 15


Functional - Physical Allocation Matrix Example DSMC

Can also be used for Requirements - Functional and Requirements - Physical allocations.

From DSMC SE Fundamentals, October 1999

Slide 16

• Waterfall (once through)• Evolutionary

– Incremental (end requirements known)–Spiral (end requirements not known)

• Iterative (small increments)• Combinations of Above


Systems Engineering Development Strategies

Slide 17

A

R F SS/HS PD

Iterations

PCATC/SV/FCATRCD

1 2 3 4 5 6 7 8 9

Increment 1 Reviews:

A: AlternativeR: RequirementsF: Functional

SS: Software SpecHS: Hardware SpecPD: Preliminary Design

CD: Critical DesignTR: Test ReadinessTC: Test Completion

SV: System VerificationFCA: Functional Configuration AuditPCA: Physical Configuration Audit

Requirements Analysis

Functional Analysis and Allocation

Synthesis/ Design

Systems Analysis

Control

Validation

Verification

JOC

Level of EffortProcess

Incremental and Iterative SE Process Example


A

R

F

PD/CD

TC/SV/FCA

PCA

TR

Increment 1

Itera

tion

Rev

iew

s:

Slide 18

USD (AT&L)

From Evolutionary Acquisition and Spiral Development, USD (AT&L), April 2002


Slide 19

Systems Engineering Management? (cont)

Work Breakdown Structure (WBS) Example

System Breakdown Structure (SBS)

Organizational Breakdown Structure (OBS)

(CWBS)

PROGRAM WORK BREAKDOWN STRUCTURE (PWBS)•• •

C/SCSC Joint Guide & JOC

From Cost/Schedule Control Systems Joint Implementation Guide, AFSCP 173-5 & DLAH 8315.2, October 1980. Also see MIL-HDBK-881.

JOCAdditions

Slide 20

AcquirerPMP

DMP&CMP

SEMPSEMP

PAP

Supplier/Developer

PMP

RMP I&TP

HSIP

ILSP

ILSP

TEMP

Acquirer Plan

Supplier/Developer Plan

DMP

RMP

SDP HDP CMP RM&AP TP IMP&IMS

CMP – Configuration Management PlanDMP – Data Management PlanHDP – Hardware Development PlanHSIP – Human Systems Integration PlanILSP – Integrated Logistics Support Plan IMP – Integrated Master PlanIMS – Integrated Master Schedule I&TP – Integration and Test Plan

PAP – Product Assurance PlanPMP – Program Management PlanRM&AP – Reliability, Maintainability & Availability Plan RMP – Risk Management PlanSDP – Software Development PlanSEMP – Systems Engineering Management Plan TEMP – Test and Evaluation Management PlanTP – Training Plan

JOC


Plans Tree

Slide 21

JOC

NAVSEASE Policy

ProgramSEMP

ProgramSEMP

PEO-TSCTRM

PEO-TSCSEMP Hdbk

Sources

SEMP

EIA/IS-6321994

CDRL – Contract Data Requirements ListCMMI – Capability Maturity Model Integrated DOD – Department of Defense DSMC – Defense Systems Management CollegeINCOSE – International Council on SENAVAIR – Naval Air Systems Command

NAVSEA – Naval Sea Systems CommandPEO – Program Executive OfficeSEMP – Systems Engineering Management Plan SOW – Statement of WorkTRM – Technical Review ManualTSC – Theater Surface Combatants

INCOSESE Hdbk

DSMCSE Fund

IEEE 12201998

ContractSOW

DD 1423sCDRLs

OrganizationProcess

Document

PEO-TSCSE Ops Man

NAVAIRSE Guide

EIA-6321998

ISO 152882002

CMMIEIA-7311999

DOD5000

SDP

IEEE/EIAJ-STD-016

Heritage of the SEMP and SDP


Slide 22

Baselines

Performance

Requirements

Functional

Allocated

Developmental

Physical/Product

ORD, TLR

SSS, SRD, SRSExternal IRS

SSS, SRD, SRS

SSDD, SS, SRS, HRS,Internal IRS

HDD (Drawings)SDD, DBDD, IDD

SoftwareHardware

RR

FR

PDR

CDR

FCA/SVRPCA

FinalDocuments Reviews

JOCTechnical Baselines, Documents, and Reviews


Slide 23

FULL MENUReview Types:

Document Types:

A R F I PD CD TR TC FCA VR PCA

Studies SSSIRS

SSSIRS

SSDD

SDDHDDIDD

DBDD

SDDHDDIDD

DBDD

T PlnT Pro

T Rpt Rpt Rpt Rpt

ASR SRR SFR SPDR SCDR STRR STCR SVR SPCA

Studies SSSIRS

SSSIRS

SSDD

SSDD SSDD T PlnT Pro

Rpt RptRpt

FlowDown:

RollUp:

SSRR SSFR SSPDR SSCDR SSTRR SSTCR SSFCA SSPCA

SSS SSSIRS

SSDD

SSDD SSDD T PlnT Pro

T Rpt Rpt Rpt

FlowDown:

SSR/SWRR SWFR SWPDR SWCDR SWTRR SWTCR SWFCA SWPCA

SRS SRSIRS

SDDIDD

DBDD

SDDIDD

DBDD

T PlnT Pro

T Rpt Rpt Rpt

System RequirementsBaseline

SUBSYSTEMLEVEL

COMPONENTLEVEL

SYSTEMLEVEL

Systemrequirementsallocated tosubsystem

System Allocated BaselineSubsystem Requirements Baseline

=

Subsystemrequirementsallocated tocomponent

Subsystem Allocated BaselineComponent Requirements Baseline (e.g., Software Requirements Baseline)

=

JOC

RollUp:

ISR

Technical Baselines, Documents, and Reviews (cont)


Slide 24

Technical Review ASR SRR SFR SSR PDR CDR TRR TCR FCA SVR PCA ISR Baseline Document

PRB FRB PFB

FFB PAB FAB PPB

FPB

Concept Papers, etc. F U System Specification (SS/SRD/SRS) P F U U U External Interface Requirements Specifications (IRSs) P F U U U Subsystem Specifications (SSSs) P F U U U All Other Plans (PMP, SEMP, SDP, HDP, I&TP, QAP, etc.)

P F U U U

Systems Engineering Master Schedule (SEMS) / Integrated Master Plan (IMP)

P F U U U

Systems Engineering Detailed Schedule (SEDS) / Integrated Master Schedule (IMS)

P F U U U

System/Subsystem Design Descriptions (SSDDs) P F U U U Hardware Requirements Specifications (HRSs) P F U U U Software Requirements Specifications (SRSs) P F U U U Internal Interface Requirements Specifications (IRSs) P F U U U Software Design Descriptions (SDDs) P F U U U Interface Design Specifications (IDSs)/ Interface Design Descriptions (IDDs)

P F U U U

Database Design Descriptions (DBDDs) P F U U U Hardware Design Descriptions / Drawings (HDDs) P F U U U Integration and Verification Plan (IVP) P F U U U Formal Qualification Test Plan (FQTP) P F U U U Formal Qualification Test Descriptions (FQTD) P F U U U Formal Qualification Test Report (FQTR) P F U U Software Product Specification (SPS) P F U U Software Version Description (SVD) P F U U Integration and Verification Report (IVR) P F U Interim System Review (ISR) Report F Legend: P = Preliminary; F = Final; U = Update; RB = Requirements Baseline; FB = Functional Baseline; AB = Allocated Baseline; PB = Product Baseline; ASR = Alternative Systems Review; SRR = System Requirements Review; SFR = System Functional Review; SSR = Software Specification Review; PDR = Preliminary Design Review; CDR = Critical Design Review; TRR = Test Readiness Review; TCR = Test Completion Review; FCA = Functional Configuration Audit; SVR = System Verification Review; PCA = Physical Configuration Audit; ISR = Interim System Review. Note: PPB = Preliminary Product Baseline = Developmental Baseline (DB). IRSs = all interface requirements specifications, and IDSs/IDDs = all interface design specifications or descriptions, regardless of which document (IRS/IDS/IDD) contains them.

JOCTechnical Baselines, Documents, and Reviews (cont)


Slide 25

System Spec(Incl IRSs)

Item Spec Software Spec Process Spec

Detail SpecDetail Spec

Material Spec

Detail SpecDetail Spec

SDDs

IDDs

DBDDs

Code

Proc Def Workmanship

Mat’l Def

Inspec Rqmts

Rqmts

Design

Drawings

Workmanship

Manuf Stds

Inspec Rqmts

Rqmts

TLR/ORD

OCD SSS External IRSs

External IDDsDBDD SSDD

HRSs SRSs Internal IRSs

HDDs SDDs Internal IDDs

Rqmts

Design

Rqmts

Design

Rqmts

TLR/ORD

TEMP SSS

System Test Plan

Hardware Test Plan Software Test Plan

Hardware Test Procedures Software Test Procedures

Hardware Test Reports Software Test Reports

Hardware Trouble Reports Software Trouble Reports

IEEE 1220-1998 DIDs, IEEE/EIA J-016, JOC

MIL-STD-961EDIDs, IEEE/EIA J-016, JOC

From IEEE 1220-1998. Copyright 1999 IEEE. All rights reserved.

Technical Document Trees


Slide 26

SSDD DID

NotesSystem-Wide

Design Decisions3.0

System Architecture Design

4.0

Req Trace5.0

Scope1.0

Ref Docs2.0

Concept ofExecution

4.2

Manual Ops4.1.X.3

SWCIs4.1.X.2

HWCIs4.1.X.1

HWCI Y4.1.X.1.Y

SWCI Y4.1.X.2.Y

MO Y4.1.X.3.Y

ID4.1.X.1.Y.1

Relationships4.1.X.1.Y.2

Alloc of Sys Reqs& Des Decisions

4.1.X.1.Y.3

Comp HWResources4.1.X.1.Y.4

Component X4.1.X

ID & Diags4.3.1

Interface X4.3.X

InterfaceDesign

4.3

System Components

4.1

Appxs

SSDD

System/Subsystem Design Description (SSDD)


Slide 27

• EIA/IS-632 Systems Engineering• IEEE 1220-1994 IEEE Trial-Use Standard for Application and

Management of the Systems Engineering Process• IEEE 1220-1998 IEEE Standard for Application and Management

of the Systems Engineering Process• ANSI/EIA-632 Processes for Engineering a System• ISO/IEC 15288 Systems Engineering – System Life Cycle

Processes• IEEE/EIA 12207 Industry Implementation of International

Standard ISO/IEC 12207:– IEEE/EIA 12207.0 Software Life Cycle Processes– IEEE/EIA 12207.1 Life Cycle Data– IEEE/EIA 12207.2 Implementation Considerations

• DoD 5000 (policy) – DoD 5000.1 The Defense Acquisition System– DoD 5000.2 Operation of the Defense Acquisition System– Interim Defense Acquisition Guidebook (formerly DoD 5000.2-R)

Standards Process Overviews

Slide 28

DOD 5000.2

DoD 5000

From New Signed DoD 5000.2, 12 May 2003

Requirements and Acquisition Process

AoA – Analysis of AlternativesICD – Initial Capabilities DocumentCDD – Capability Development DocumentCPD – Capability Production DocumentCD – Concept DecisionDAB – Defense Acquisition BoardMS – MilestoneNSS – National Security SystemsJROC – Joint Requirements Oversight Council DOTMLPF – Doctrine, Organization, Training, Material, Leadership, Personnel, Facilities.

Slide 29

StandardUser

EIA/IS-632-1994

IEEE1220-1994

ANSI/EIA-632-1998

IEEE 1220-1998

DSMC/DMU – 1999 √ √

EIA/IS-731 – 1999 √ √

NAVSEA PMS 465 CEC – 1999 √ √

NAVSEA PEO-TSC – 1999-2000 √ √

INCOSE – 2000 √ √

OSD OSJTF – 2001 √ √ √

NAVSEA PEO-TSC - 2001 √?

NAVSEA SE – 2002 √

NAVAIR SE – 2003 √ √

Total Score 5 3 4 or 5 4

Used Scorecard

JOC

Note: Later users generally tend to reference the later standards ( )

Slide 30

Standards Detailed Overviews

• EIA/IS-632 Systems Engineering• IEEE 1220-1998• ANSI/EIA-632• ISO/IEC 15288• IEEE/EIA 12207• DoD 5000

Slide 31

Product Baseline. .

MS 0

Phase 0 Phase I Phase II Phase III

MS I MS II MS III

Functional Baseline

Allocated Baseline

Technical Management Plan (TMP) Update Update Update

ASR SRR SFR SSR PDR CDR TRR FCA PCA

ENGINEERING CHANGEREVIEWS

OperationalRequirementDocument

(ORD)


(ORD)


(ORD)

SystemThreat

Assessment

SystemThreat

Assessment

SystemThreat

Assessment

MissionNeed

Statement

Concept System SubsystemsDeficiencyCorrection

Mods/ProductImprovements

System Performance Specification

Item Performance Specification

Item Detail Specification

Reassess Threat Reassess Threat Reassess Threat

Preplanned Product Improvement (P3I)

DraftGovernment

Approves

.Developmental

. Conceptual Performance Baseline

PROCESS INPUT• Customer Needs/ Objectives/ Requirements . . Mission/ Operations . . Measures of Effectiveness . . Environments . . Constraints • Technology Base• Prior Output Data• Program Decision Requirements• Requirements From Tailored Standards and Specifications

Requirements Analysis• Analyze Missions & Environments• Identify Functional Requirements• Define/Refine Performance & Design Constraint Requirements

Functional Analysis/Allocation• Decomposition is Lower-Level Functions• Allocate Performance & Other Limiting Requirements is Lower-Level Functions• Define/Refine Functional Interfaces (Internal/External)• Define/Refine/Integrate Functional Architecture

Requirements Loop

Systems Analysis& Control

Design Loop

Synthesis• Transform Architecture (Functional to Physical)• Define Alternative Product Concepts• Define/Refine Physical Interfaces (Internal/External)• Define Alternative Product & Process Solutions

PROCESS OUTPUT• Integrated Decision Data Base . . Decision Support Data . . System Functional Physical Architectures . . Specifications & Baseline• Baseline System Solution

Verification

• Select Preferred Alternatives• Trade-Off Studies• Effectiveness Analysis• Risk Management• Configuration Management• Interface Management• Data Management• Performance-Based• Progress Measurement . . SEMS . . TPM . . Technical Reviews




Requirements Loop


Design Loop



Verification





Requirements Loop


Design Loop



Verification





Requirements Loop


Design Loop



Verification





Requirements Loop


Design Loop



Verification


PEO-TSC SEMP HDBK

PEO-TSC

From PEO-TSC SEMP Handbook, TSCBT3HDBK 4810.1Rev 0, 2 August 1999

Slide 32

Standards Details

• EIA/IS-632• IEEE 1220-1998 IEEE Standard for Application and

Management of the Systems Engineering Process• ANSI/EIA-632• ISO/IEC 15288• IEEE/EIA 12207• DoD 5000

Slide 33

Standards Detailed Overview

• EIA/IS-632• IEEE 1220-1998• ANSI/EIA-632 Processes for Engineering a System • ISO/IEC 15288• IEEE/EIA 12207• DoD 5000

Slide 34


• EIA/IS-632• IEEE 1220-1998• ANSI/EIA-632• ISO/IEC 15288 Systems Engineering – System Life

Cycle Processes• IEEE/EIA 12207• DoD 5000

Slide 35


• EIA/IS-632• ANSI/EIA-632• IEEE 1220-1998• ISO/IEC 15288• IEEE/EIA 12207 Industry Implementation of

International Standard ISO/IEC 12207:– IEEE/EIA 12207.0 Software Life Cycle Processes– IEEE/EIA 12207.1 Life Cycle Data– IEEE/EIA 12207.2 Implementation Considerations

• DoD 5000

Slide 36


• EIA/IS-632• IEEE 1220-1998• ANSI/EIA-632• ISO/IEC 15288• IEEE/EIA 12207• DoD 5000 (policy)

–DoD 5000.1 The Defense Acquisition System–DoD 5000.2 Operation of the Defense Acquisition

System– Interim Defense Acquisition Guidebook (formerly DoD

5000.2-R)

Slide 37

DOD 5000.2

DoD 5000


Requirements and Acquisition Process

AoA – Analysis of AlternativesICD – Initial Capabilities DocumentCDD – Capability Development DocumentCPD – Capability Production DocumentCD – Concept DecisionDAB – Defense Acquisition BoardMS – MilestoneNSS – National Security SystemsJROC – Joint Requirements Oversight Council DOTMLPF – Doctrine, Organization, Training, Material, Leadership, Personnel, Facilities.

Slide 38

USD AT&L

USD (AT&L)

From Evolutionary Acquisition and Spiral Development, USD (AT&L), April 2002

Slide 39

DoD 5000 (cont)

DOD 5000.2


Slide 40

INCOSE & JOC

EIA/IS-632

1980

Instructions/Handbooks/

Manuals/Guides

IEEE 12201994

DIDs

ANSI/EIA-632

ISO/IEC15288

IEEE/EIA12207

MIL-STD-499A

MIL-STD-499

SystemsEngineering

ISO/IEC12207

MIL-STD-498

DOD-STD-2167

DOD-STD-2167A

DOD-STD-1703

DOD-STD-7935A

DIDs

MIL-STD-1679A

1985

1998 1994

1998 1994

1974 1969

1999-2002

1999

2002

1994

1987

1988

1988

1994

1995 1998

2003+

IEEE 1498/EIA 640

1995

(Draft)

(Trial Use)

(Interim)

(NotReleased)

Sec PerryLetterJan 1994

SoftwareEngineering

1968-

Data Item Descriptions

Primary Focus of this Tutorial

MIL-Std-499B

ISO/IEC1528812207

Harmon

2003+

MIL-STD-1679

1968-

ISO/IEC19760Guide

2003

CMMI

(SE-CM)

MIL-STD-961D

1995 Defense Specifications

ISO/IEC15288IEEE1220

Harmon

2003+

MIL-STDs to Commercial Stds to CMMs

Future of SE and SW Standards

EIA/IEEEJ-STD-016

1995

(Interim)

IEEE 12201998

EIA/IS-731

MIL-STD-961E

2003

Supercedes

Derived From

Slide 41

Recommendations

• Stand on the Standards (Don’t Rely on Others)• Read, Understand, Select, Tailor, and Apply Them• Keep Abreast of Standards Evolution• Develop a Corporate and/or Project Tailored Set of

Processes, Product Templates, and SEMP• Map the Standards To and From the Processes,

Templates, and SEMP. Describe Any Tailoring.• Start with a Pilot Project• Refine the Processes, Templates, and SEMP• Have Fun!

JOC

Slide 42

Summary

• Heritage of Systems Engineering and Software Engineering Standards

• What is a System?• What is Systems Engineering?• What is Systems Engineering Management?• Standards Process Overviews• User Scorecard• Standards Detailed Overviews• Future of Systems Engineering and Software

Engineering Standards• Recommendations & Summary

Slide 43

Almost the End!

• Questions?JOC

Slide 44

THE END!

For More Information Contact:

John O. ClarkNorthrop Grumman Information TechnologyDefense Mission SystemsWarfare Systems Engineering468 Viking DriveVirginia Beach, VA 23452-7308 USA

[email protected]

(757) 534-4805 or (757) 481-1504