GDPA Homepage  
Mapping IEEE1220 and V-Model  

Mapping IEEE1220 and V-Model

The standard IEEE 1220-1994 " IEEE Trial-Use Standard for Application and Management of the Systems Engineering Process", was issued for trial use in February 1995. In its abstract is written:

"The interdisciplinary tasks that are required throughout a system's life cycle to transform customer needs, requirements, and constraints into a system solution are defined. This standard applies to a performing activity within a enterprise that is responsible for developing a product design and establishing the life cycle infrastructure needed to provide for life cycle sustainment. It specifies the requirements for the systems engineering process and its application throughout the product life cycle. The requirements of this standards are applicable to new products as well as incremental enhancements to existing products".

The following table identifies for each task of IEEE 1220 the equivalent (partially equivalent) activity of the V-Model. This table is for research use only. The tasks of IEEE 1220 listed in this table are restricted to the first level of sub-activities.

IEEE 1220

V-Model

Remarks of the mapping in V-Model

1

Requirement Analysis

SD1

System Requirements Analysis

 

1.1

Define Customer Expectations

SD1.2

Description of Application System

Partially in the section "Handling" of SD1.2: "It is necessary to define which user-level tasks are to be supported by the System..." The overall horizon must point out the overall functionality to be covered in the final version and which priorities are expected in the course of the following development. "

1.2

Define Project and Enterprise Constraints

SD1.4

Definition of Marginal Conditions

Partially in the document User Requirements.Marginal Conditions: "recording of the user environment (structure and process organization, official regulations, decrees, laws, rules, and the like) recording of time and quantity listing (present processing times, throughput times, response times, waiting times, amount of data)

SD1.1

Recording of Actual Status and Analysis

Partially. Possible to be added.

1.3

Define External Constraints

SD1.4

Definition of Marginal Conditions

Partially in the document User Requirements.Marginal Conditions: "specifications from organization development for staff size, job plans, job descriptions, specifications from personnel laws (Civil Service Act, regulations governing industrial relations, worker participation, tariff contracts),

SD1.1

Recording of Actual Status and Analysis

Partially. Possible to be added.

1.4

Define Operational Scenarios

 

 

 

1.5

Define Measures of Effectiveness

SD1.3

Definition of Criticality and Quality Requirements

Partially in the document User Requirements.Quality Requirements

1.6

Define System Boundaries

 

 

 

1.7

Define Interfaces

SD1.5

User-Level System Structure

Partially in the document User Requirements.External Interfaces

1.8

Define Utilization Environments

 

 

 

1.9

Define Life-Cycle Process Concepts

PM1.3

PM1.3 - Generation of Project-Specific V-Model

 

1.10

Define Functional Requirements

SD1.2

Description of Application System

Partially in the section "Handling" of SD1.2: "An overall horizon must be specified for the system functionality within the scope of this activity. This is realized by means of a preliminary system description which is the background for all further refinements and additions of the User Requirements"

1.11

Define Performance Requirements

SD2.1

Technical System Design

Partially in document Technical Requirements

1.12

Define Modes of Operations

 

 

 

1.13

Define Technical Performance Measures

QA2.1

Definition of Assessment Methods and Criteria

 

1.14

Define Physical Characteristics

SD2.1

Technical System Design

 

1.15

Define Human Factors

SD1.1

Recording of Actual Status and Analysis

 

1.16

Establish Requirements Baseline

SD1.1

Recording of Actual Status and Analysis

 

SD1.2

Description of Application System

 

SD1.3

Definition of Criticality and Quality Requirements

 

SD1.4

Definition of Marginal Conditions

 

SD1.5

User-Level System Structure

 

SD1.6

Threat and Risk Analysis

 

2

Requirements Validation

 

 

 

2.1

Compare to Customer Expectations

SD2.4

Allocation of User Requirements

 

2.2

Compare to Enterprise & Project Constraints

SD1.7

Realization of Requirements Controlling

 

2.3

Compare to External Constraints

 

 

 

2.4

Identify Variances and Conflicts

QA5

QA Reporting

 

2.5

Validated Requirements Baseline

SD2.4

Allocation of User Requirements

 

3

Functional Analysis

 

 

 

3.1
(3.1.1, 3.1.2, 3.1.3)

Decompose System Functions

SD2.1

Technical System Design

 

SD2.5

Interface Description

 

SD3.1

Definition of General Requirements from SW/HW Unit Point of View

 

SD3.2

Specification of Requirements for External Interfaces of SW/HW Unit

 

SD3.3

Definition of Requirements for the Functionality

 

SD4.1

SW Architecture Design

 

SD4.2

Design of Internal and External SW Interfaces

 

3.2

Analyze Functional Behaviors

SD3.3

Definition of Requirements for the Functionality

 

3.2

Define Sub-functions States & Modes

 

 

 

3.4

Define Functional Timelines

SD5.2

Analysis of Resources and Time Requirements

 

3.5

Define Data & Control Flows

SD1.1

Recording of Actual Status and Analysis

 

SD1.2

Description of Application System

 

SD1.5

User-Level System Structure

 

SD2.1

Technical System Design

 

SD3.2

Specification of Requirements for External Interfaces of SW/HW Unit

 

SD3.3

Definition of Requirements for the Functionality

 

3.6

Define Functional Failure Modes & Effects

SD1.6

Threat and Risk Analysis

 

SD2.2

Realization of Efficiency Analysis

 

3.7

Define Hazard Monitoring Functions

SD1.6

Threat and Risk Analysis

 

SD2.2

Realization of Efficiency Analysis

 

3.8

Establish Functional Architecture

SD3.1

Definition of General Requirements from SW/HW Unit Point of View

 

SD4.1

SW Architecture Design

 

SD4.2

Design of Internal and External SW Interfaces

 

SD4.3

Specification of SW Integration

 

 

 

4

Functional Verification

 

 

 

4.1

Define Verification Procedures

QA2.4

Generation of Assessment Procedure

 

4.2
(4.2.1, 4.2.2, 4.2.3)

Conduct Verification Evaluation

QA4.2

Assessment of the Content of the Product

 

4.3

Identify Variances and Conflicts

SD5.2

Analysis of Resources and Time Requirements

 

QA5

QA Reporting

 

4.4

Verified Functional Architecture

QA4.2

Assessment of the Content of the Product

The functional architecture is also a product.

5

Synthesis

 

 

 

5.1

Group and Allocate Functions

SD5.1

Description of SW Component/Module/Database

 

5.3

Identify Physical Solution Alternatives

SD5.2

Analysis of Resources and Time Requirements

 

5.3

Assess Safety & Environmental Hazards

SD8.2

Self-Assessment of the System

 

QA4

Product Assessment

 

5.4

Assess Life-Cycle Quality Factors

QA4

Product Assessment

 

5.5

Assess Technology Requirements

QA4

Product Assessment

 

5.6

Allocate Physical & Performance Characteristics

 

 

limited for the alternative solutions define in 5.3

5.7

Define Physical Interfaces

SD4.2

Design of Internal and External SW Interfaces

 

5.8

Assess Standardization Opportunities

 

 

 

5.9

Assess Off-the-Shelf Availability

PM2

Placement/ Procurement

 

PM6

Phase Review

 

5.10

Assess Make or Buy Alternative

PM5

Cost/Benefit Analysis

 

5.11

Develop Models & Fabricate Prototypes

SD6

SW Implementation

 

5.12

Assess Failure Modes, Effects & Criticality

 

 

limited for the alternative solutions define in 5.3

5.13

Assess Testability Needs

QA4.1

Determination of Assessability

 

5.14

Assess Design Capacity to Evolve

SD3.5

Definition of Requirements for the Development and SWMM Environment

 

5.15

Finalize Design

SD5

Detailed SW Design

 

5.16

Initiate Evolutionary Development

SD6.1

Coding of SW Modules

 

SD6.2

Realization of Database

 

SD7.1

Integration into SW Component

 

SD7.3

Integration into SW Unit

 

SD8.1

Integration into System

 

PM8

Project Control

 

5.17

Produce Drawings & Semantics

SD5.1

Description of SW Component/Module/Database

 

SD 5.1-HW

Generation of Detailed Designs for HW Components/HW Modules

 

SD 5.2-HW

Generation of Engineering Drawing

 

5.18

Establish Physical Architecture

SD5

Detailed SW Design

 

SD 5-HW

Detailed HW Design

 

6

Physical Verification

 

 

 

6.1
(6.1.1, 6.1.2, 6.1.3)

Select Verification Approach

QA1.2

Generation the Assessment Plan

QA2

Assessment Preparation

 

6.2
(6.2.1, 6.2.2, 6.2.3)

Conduct Verification Evaluation

SD6.3

Self-Assesment of the SW Module/Database

 

SD7.2

Self-Assessment of SW Component

 

SD7.4

Self-Assessment of SW Unit

 

SD8.2

Self-Assessment of the System

 

QA4.2

Assessment of the Content of the Product

 

6.3

Identify Variance & Conflicts

QA5

QA Reporting

 

6.4

Verified Physical Architecture

QA4.2

Assessment of the Content of the Product

QA4.2

Assessment of the Content of the Product

QA4.2

Assessment of the Content of the Product

CM1.1

Generation the CM Plan

PM6

Phase Review

 

6.8

Develop Product Breakdown Structure(s)

SD5.1

Description of SW Component/Module/Database

7

System Analysis

SD1.7

Realization of Requirements Controlling

 

7.2

Assess Functional Alternatives

 

 

 

7.3

Assess Solution Alternatives

 

 

 

7.4

Identify Risk Factors

SD1.6

Threat and Risk Analysis

 

7.5

Define Trade-study Scope

PM1.2

Definition of Project Criteria and Development Strategy

 

7.5.1

Select Methodology & Success Criteria

PM1.2

Definition of Project Criteria and Development Strategy

 

7.5.2

Identify Alternatives

 

 

 

7.5.3

Establish Trade-study Environment

PM1.2

Definition of Project Criteria and Development Strategy

 

7.6
(7.6.1, 7.6.2, 7.6.3, 7.6.4)

Conduct Trade-study

PM5

Cost/Benefit Analysis

 

PM6

Phase Review

 

7.7

Select Risk Handling Options

PM7

Risk Management

 

7.8

Select Alternative Recommendation

 

 

 

7.9

Trade-offs & Impacts

 

 

 

7.10

Solution Effectiveness Assessment

 

 

 

8

Control

 

 

 

8.1
(8.1.1, 8.1.2, 8.1.3)

Design Capture

PM1.1

Setting up the Project

CM2

Product and Configuration Management

 

CM4.1

Data Administration

 

PM7

Risk Management

 

PM8

Project Control

 

8.3

Track System Analysis & Verification/Test Data

PM8

Project Control

 

PM9

Information Service/Reporting

PM8

Project Control

 

PM9

Information Service/Reporting

SD8.2

Self-Assessment of the System

 

8.6

Track Performance against Technical Plans

SD8.2

Self-Assessment of the System

 

8.7

Track Product & Process Metrics

SD8.2

Self-Assessment of the System

 

8.8

Update Specifications & Configuration Baselines

CM4.5

Update of CM Documentation

 

8.9

Update Requirement Views & Architecture

 

 

 

8.10

Update Technical Plans

 

 

 

8.11

Update Project Plans

PM9

Information Service/Reporting

 

8.12

Integrate Data Base

SD7.3

Integration into SW Unit

 

GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster