![]() |
|
| 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 |
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 |
|
|||||
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |