copyright 2008 northrop grumman corporation 1 requirements engineering from a standards perspective...

1

Copyright 2008 Northrop Grumman Corporation

Requirements Engineering from a

Standards PerspectiveINCOSE Hampton Roads Area Chapter

Requirements Management and Analysis Seminar

November 4-5, 2008

John O. ClarkChief Engineer, CSEPNorthrop Grumman Corporation

2


All EIA, IEEE, ANSI, and ISO/IEC copyrighted material has been removed from this version in order to comply with the copyright owner’s requirements. Refer to the figures in the standards.

Copyright AcknowledgementAcknowledgement

3


Content

• Introduction– Purpose– SE Standards– In-Seat Warm-up Exercise– Key Terms– What is Systems Engineering?– What is a Requirement?

• Want is Requirements Management?

• What is the Requirements Engineering Process?– MIL-STD-499B, EIA/IS-632-1994– IEEE 1220-2005– ANSI/EIA-632-1998– ISO/IEC 15288-2008, IEEE Std 15288-2008– ISO/IEC TR 19760– ISO/IEC 12207-2008, IEEE Std 12207-2008

• Appendix – Acronyms

4


Purpose

• Introduce the systems engineering standards which include the requirements engineering processes

• Emphasize the requirements engineering processes from a “standards” perspective

• “Stand on the standards," as opposed to relying solely on other sources such as instructions, procedures, guides, textbooks, education, training, and even experience in performing requirements engineering functions

• Develop an appreciation for the different views of the requirements engineering process based on how each of the standards presents this view, thereby getting a more complete view

• Show the relationships between systems requirements engineering and software requirements engineering based on these standards

5


IEEE 1220

SE Standards

EIA/IS 632

ISO/IEC 15288

EIA 632

Le

vel o

f D

eta

il

Breadth of Scope

Provided with the permission of Sarah Sheard from Sheard, Sarah A., Software Productivity Consortium (SPC), and

Lake, Jerome G., Systems Management international (SMi), Systems Engineering Standards and Models Compared, July 1998.

Sheard and Lake

Scope and Detail of the SE Standards

6


In-Seat Warm-up Exercise

Instructions: Answer the following questions on your own without looking at the materials:– What is a requirement?

– Want is requirements analysis?

– What is requirements management?

– What is requirements engineering?

– What is the requirements engineering process?

Time: 5 minutes

JOC

7


• Capability: A group of related requirements raised to a higher level of abstraction. Synonyms include function, subject, object, or other term useful for presenting the requirements.

• Requirement: A condition for acceptance of the system.• Functional Requirement: What?• Performance Requirement: How well?• 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.• Architecture: Design or structure.

Key TermsJOC

8


Capability: “Verb Noun” Example: Transport personnel safely over land.Capability: “Verb Noun” Example: Transport personnel safely over land.

Requirement: “Noun shall verb.”

Example: The car shall stop within 100 feet at 50 mph, weigh less than 3000 lbs, and be green.

Functional (what) Performance (how well) Physical, Design, or Constraint

What is Systems Engineering?JOCKey Terms and Relationships

System Requirements Document (SRD)System Specification (SS) (MIL-STD-961E) System/Subsystem Specification (SSS)Software Requirements Specification (SRS)

System/Subsystem Design Description (SSDD)System Specification (SS) (MIL-STD-961E)Software Design Description (SDD)

Capabilities

Functions(SSDD/SS/SDD)

Components

Requirements

Operational Requirements Document (ORD)Initial Capabilities Document (ICD)Capabilities Development Document (CDD)

Mission Needs Statement (MNS)Operational Concept Document (OCD)System Threat Assessment Report (STAR)

Capability: “Verb Noun” Example: Transport personnel safely over land.




Function: “Verb Noun,” “Verb-ing,” or “Verb.” Examples: Stop Car, Stopping, or Stop.

Capability: “Verb Noun” Example: Transport personnel safely over land.




Function: “Verb Noun,” “Verb-ing,” or “Verb.” Examples: Stop Car, Stopping, or Stop.

Component: “Noun.” Example: Brake.

9


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

What is a Requirement? (cont)

Functional Thread Analysis / Use Cases

INCOSE SE HDBK

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

Provided with the permission of INCOSE from INCOSE SE Handbook, Version 2a. Copyright 2002, 2004 by INCOSE.

10


Technical Baselines, Documents, and Reviews

A/O – Alternative/OperationalCD – Critical Design

DBDD – Data Base Design Description

F – Functional

FCA – Functional Configuration Audit

HDD – Hardware Design Description

HRS- Hardware Requirements Specification

IDD – Interface Design Description

IRS – Interface Requirements Specification

ORD – Operational Requirements Document

PCA – Physical Configuration Audit

PD – Preliminary Design

TLR – Top Level Requirements

R – Requirements

What is Requirements Management?

Baselines

Performance

Requirements

Functional

Allocated

Developmental

Physical/Product

ORD / TLR

SRD / SS / SSSExternal IRS

SRD / SS / SSS

SSDD, SRS, HRS,Internal IRS

HDD (Drawings)SDD, DBDD, IDD

SoftwareHardware

R

F

PD

CD

FCA/VPCA

Documents Reviews

JOC

A/O

SDD – Software Design Description

SRD – System Requirements Document

SS – System Specification

SSS – System/Subsystem Specification

SRS – Software Requirements Specification

SSDD – System/Subsystem Design Specification

V – Verification

11


FULL MENUReview Types:

Document Types:

J. Clark

A R F IPD CD TR TC FCA VR PCA

ORD/ICD

S/SSIRS

S/SSIRS

S/SDD

SDDHDDIDD

DBDD

SDDHDDIDD

DBDD

T PlanT Proc

T Rpt Rpt Rpt Rpt

LOWEST CONFIGURATIO

N ITEMLEVEL

Subsystem Allocated Baseline =LCI Requirements Baseline(e.g., Software Requirements Baseline)

SWRR SWFR SWPDR SWCDR SWTRR SWTCR SWFCA SWPCA

SWRSIRS

SWRSIRS

SWDDIDD

DBDD

SWDDIDD

DBDD

T PlanT Proc

T Rpt FCA Rpt PCA Rpt

Technical Baselines, Documents, and Reviews for a System

SYSTEM

LEVEL

System Requirements

Baseline

Systemrequirementsallocated toSubsystems

ASR SRR SFR SPDR SCDR STRR STCR SVR SPCA

ORD/ICD

SSIRS

SSIRS

SDD SDD T PlanT Proc

T Rpt FCA Rpt PCA Rpt

Rqmts,Functions,& PrelimDesignFlow Down:

DetailedDesign, Verification& ValidationRoll Up:

ISR

SUBSYSTEMLEVEL

System Allocated Baseline =Subsystem Requirements Baseline

Subsystemrequirementsallocated to

Lowest ConfigurationItems (LCIs)

SubRR SubFR SubPDR SubCDR SubTRR SubTCR SubFCA SubPCA

SubSIRS

SubDD SubDD T PlanT Proc

T Rpt FCA Rpt PCA RptSubSIRS

ISubR

Rqmts,Functions,& PrelimDesignFlow Down:

DetailedDesign, Verification& ValidationRoll Up:

What is Requirements Management? (cont)

12


• MIL-STD-499B, EIA/IS-632-1994 Systems Engineering

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

• ANSI/EIA-632-1998 Processes for Engineering a System

• ISO/IEC 15288-2008, IEEE Std 15288-2008 Systems and Software Engineering – System Life Cycle Processes

• ISO/IEC 12207-2008, IEEE Std 12207-2008 Systems and Software Engineering – Software Life Cycle Processes

• ISO/IEC TR 19760 Systems Engineering – A guide for the Application of ISO/IEC 15288 (System Life Cycle Processes)

What is the Requirements Engineering Process?

13


JOC

•Requirements Trade Studies and Assessments

•Effectiveness Analysis, etc.

• Physical Design Trade Studies

• Effectiveness Analysis, etc.

Systems Analysis

• 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 Sub functions• Allocate Decomposed and Derived Requirements to Sub functions• Define Functional Architecture• Develop Functional Flow Block Diagrams• Establish Functional Baseline

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

Control

R22 R21

R2R1

SysI/F I/F

R22R11

• 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 ArchitectureFunctional Architecture Physical Architecture

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

Packages

and Assessments

I/F I/F

I/F

F11

F12 F21

F2F1

SysI/F

I/F

I/F

I/F

I/FF22 C1 C2 C3

Sub2Sub1

SysI/F

I/F

I/F

I/F

I/FC2

MIL-STD-499B and EIA/IS-632 (cont)John Clark Amplified Version

14


Summary

• Introduction– Purpose– SE Standards– In-Seat Warm-up Exercise– Key Terms– What is Systems Engineering?– What is a Requirement?

• Want is Requirements Management?

• What is the Requirements Engineering Process?– MIL-STD-499B, EIA/IS-632-1994– IEEE 1220-2005– ANSI/EIA-632-1998– ISO/IEC 15288-2008, IEEE Std 15288-2008– ISO/IEC TR 19760– ISO/IEC 12207-2008, IEEE Std 12207-2008

• Appendix – Acronyms

15


THE END!

For More Information Contact:

John O. Clark

Northrop Grumman Mission Systems

Command and Control Systems Division

Warfare Systems Engineering Department

468 Viking Drive

Virginia Beach, VA 23452-7308 USA

[email protected]

(757) 481-1504

16


AcronymsAcronym Description

A Alternative

Acq Acquisition

ACWP Actual Cost of Work Performed

AD Architectural Design

ANSI American National Standards Institute

AoA Analysis of Alternatives

AP Assessment Process

ASR Alternative System Review

AT&L Analysis, Technology and Logistics

ATM Automatic Teller Machine

BCWP Budgeted Cost of Work Performed

BCWS Budgeted Cost of Work Scheduled

C Component

CD Critical Design

CD Concept Decision

CDD Capability Development Document

CDR Critical Design Review

CDRL Contract Data Requirements List

CI Configuration Item

CM Configuration Management Plan

CMMI Capability Maturity Model Integrated

CP Control Process

CPD Capability Production Document

CSCI Computer Software Configuration Item

CV Cost Variance

CWBS Contract Work Breakdown Structure

DAB Defense Acquisition Board

DBDD Data Base Design Description

DID Data Item Description

Dis Disposal

DM Decision Making

DMP Data Management Plan

DMU Defense Management University

DOD-STD Department of Defense Standard

DOTMLPF Doctrine, Organization, Training, Material,

Leadership, Personnel, Facilities

DSMC Defense Systems Management College

EEM Enterprise Environment Management

EIA Electronic Industries Association

17


EPVP End Products Validation Process

EVM Earned Value Management

F Function, Functional

F Final

FAB Final Allocated Baseline

FCA Functional Configuration Audit

FFB Final Functional Baseline

FFBD Functional Flow Block Diagram

FFD Functional Flow Diagram

FOC Full On Capability

FOS Family of Systems

FPB Final Product Baseline

FRB Final Requirements Baseline

FRP Full Rate Production

FW Firmware

HDBK Handbook

HDD Hardware Design Description

HDP Hardware Development Plan

HS Hardware Specification

HSIP Human Systems Integration Plan

HW Hardware

HWCI Hardware Configuration Item

I Implementation

I&TP Integration and Test Plan

ICD Initial Capabilities Document

IDD Interface Design Specification

IEC International Electrotechnical Commission

IEEE Institute of Electrical and Electronic Engineers

ILSP Integrated Logistics Support Plan

IM Information Management,

Investment Management

IMP Integrated Master Plan

IMS Integrated Master Schedule

INCOSE International Council on Systems Engineering

Int Integration

IOC Initial Operational Capability

IOT&E Initial Operational Test and Evaluation

IP Implementation Process

IRS Interface Requirements Specification

Acronyms (cont)

18


ISO International Organization for Standardization

ISR Interim System Review

JOC John O. Clark

JROC Joint Requirements Oversight Council

LRIP Limited Rate Initial Production

MIL-STD Military Standard

MO Manual Operation

MS Milestone

MT Maintenance

N2 N x N

NAVAIR Naval Air Systems Command

NAVSEA Naval Sea Systems Command

NSS National Security Systems

OBS Organizational Breakdown Structure

OCD Operational Concepts Document

Op Operation

ORD Operational Requirements Document

OSD Office of the Secretary of Defense

OSJTF Open Systems Joint Task Force

P Preliminary

P3I Pre-Planned Product Improvement

PA Process Area

PAB Preliminary Allocated baseline

PAP Product Assurance Plan

PBS Product Breakdown Structure

PCA Physical Configuration Audit

PD Preliminary Design

PDR Preliminary Design Review

PEO Project Executive Officer

PFB Preliminary Functional Baseline

PIN Personal Identification Number

PMP Program Management Plan

PP Project Planning

PPB Preliminary Product Baseline

PRB Preliminary Requirements Baseline

PROC Process

PWBS Program Work Breakdown Structure

QM Quality Management

Acronyms (cont)

19


R Requirement

RA Requirements Analysis

RDP Requirements Definition Process

RESM Resource Management

RM&AP Reliability, Maintainability and Availability Plan

RMP Risk Management Plan

S System

SAP Systems Analysis Process

SBS System Breakdown Structure

SCDR System Critical Design Review

SDD Software Design Description

SDP Software Development Plan

SDP Solution Definition Process

SE Systems Engineering

SEDS Systems Engineering Detailed Schedule

SEMP Systems Engineering Master Plan

SEMS Systems Engineering Master Schedule

SFR System Functional Review

SLCM System Life Cycle Management Process

SOS System of Systems

SOW Statement of Work

SPCA System Physical Configuration Audit

SPDR System Preliminary Design Review

SR Stakeholder Requirements

SRD System Requirements Document

SRR System Requirements Review

SRS Software Requirements Specification

SS System Specification

SS Software Specification

SSCDR Subsystem Critical Design Review

SSDD System/Subsystem Design Description

SSFR Subsystem Functional Review

SSPDR Subsystem Preliminary Design Review

SSR Software Specification Review

SSRR Subsystem Requirements Review

SSS System/Subsystem Specification

STCR System Test Completion Review

STRR System Test Readiness Review

Acronyms (cont)

20


Sup Supply

SV System Verification

SV Schedule Variance

SVP System Verification Process

SVR System Verification Review

SW Software

SWCDR Software Critical Design Review

SWFCA Software Functional Configuration Audit

SWFR Software Functional Review

SWPCA Software Physical Configuration Audit

SWPDR Software Preliminary Design Review

SWRR Software Requirements Review

SWTCR Software Test Completion Review

SWTRR Software Te3st Readiness Review

T Pln Test Plan

T Proc Test Procedures

T Rpt Test Report

TC Test Completion

TEMP Test and Evaluation Management Plan

TLR Top Level Requirements

TP Training Plan

TP Transition to Use Process

TPM Technical Performance Measurement

TR Test Readiness

TRM Technical Review Manual

Trn Training

TSC Theater Surface Combatants

U Updated

USD Under Secretary of Defense

Val Validation

Ver Verification

WBS Work Breakdown Structure

Acronyms (cont)

21


copyright 2008 northrop grumman corporation 1 requirements engineering from a standards perspective...

Documents

copyright owners requirements

ieee std

isoiec tr

systems engineering

clark chief engineer

analysis seminar

appendix acronyms