FAO.3 Cross Referencing V-Model Products and Activities to FAO Requirements




		FAO.3 Cross Referencing V-Model Products and Activities to FAO Requirements

BRH.3 Zuordnung der V-Modell-Produkte und -Aktivitäten zu den BRH-Forderungen

Chapter Brief Description of Requirement Met by
1.4.1 planning and use IT IT framework concept,
V-Model products
1.4.2 IT documentation, complete and non-overlapping V-Model, in general
1.4.3 computer-aided documentation Submodel CM
1.4.4 availability of documentation project-specific organizational regulations, CM
1.4.5 design, generation and content of documentation as well as distribution and archivation V-Model, in general,
especially Project Manual,
CM Plan
2 overall plan and coordination IT framework concept, contributions of V-Model to individual IT enterprises
3.1.1 IT enterprise objective of the V-Model
3.1.2 uniform procedure to be defined in writing V-Model, in general, especially Project Manual
3.2.1 responsibilities and procedures Project Manual,
Project Plan,
CM Plan,
QA Plan
3.2.2 overall IT plan phase model (outside V-Model)
3.3.1 preliminary and final investigation phase model (outside V-Model)
3.3.5 combination of preliminary and final investigation no requirement
3.3.6 documentation of results of preliminary and final investigation phase model (outside V-Model)
3.4.1.1 realization of an IT enterprise V-Model, in general
3.4.1.2 documentation of realization of an IT enterprise V-Model, in general
3.4.2 procurement of hardware and software PM2 - Placement/ Procurement,
scenario Application of Off-the-Shelf-Products
3.4.3 placing of development orders PM1.5 - Generation of Preliminary Plan,
PM4 - Detailed Planning,
application as a basis for contracts (Coordinating the V-Model in its Environment manual)
3.4.4.1 regulations for generation of programs V-Model, in general, especially Project Manual
3.4.4.2 structure of programs V-Model, in general
3.4.4.3 user-friendliness observance while processing submodel SD
3.4.4.4 process documentation V-Model products
3.4.5.1 test of IT procedures submodel QA
3.4.5.2 performing tests submodel QA
3.4.5.3 documentation of test results submodel QA
3.4.5.4 release (who is in charge) not regulated in V-Model
3.4.5.5 release certificate not regulated in V-Model
3.4.5.6 release (prerequisites) not regulated in V-Model, but mentioned in PM 6
3.4.5.7 release of externally developed procedures submodel QA
3.4.5.8 release to be defined in writing not regulated in V-Model
3.4.5.9 no modifications after release Submodel CM
3.4.6.1 no unauthorized modifications after integration into production environment Submodel CM
3.4.6.2 introducing an IT procedure SD9 - Transition to Utilization
3.4.6.3 consulting and training after introduction of procedure Operational Information
3.5.1 maintenance of procedures V-Model, in general
3.5.2 written rules for the fast elimination of errors CM Plan
3.5.3 documentation of changes CM3 - Change Management (Configuration Control)
4 operation of IT procedures not regulated in V-Model
5 success control not regulated in V-Model
6.1 control of procedure development QA3 - Process Assessment of Activites
6.2 checking correct application of procedures PM6 - Phase Review
7.2.1 threat and risk analysis SD1.6 - Threat and Risk Analysis,
SD2.1 - Technical System Design
7.2.2 technical and organizational measures SD1 - System Requirements Analysis,
SD2 - System Design,
in addition to IT framework concept

Chapter	Brief Description of Requirement	Met by
1.4.1	planning and use IT	IT framework concept, V-Model products
1.4.2	IT documentation, complete and non-overlapping	V-Model, in general
1.4.3	computer-aided documentation	Submodel CM
1.4.4	availability of documentation	project-specific organizational regulations, CM
1.4.5	design, generation and content of documentation as well as distribution and archivation	V-Model, in general, especially Project Manual, CM Plan
2	overall plan and coordination	IT framework concept, contributions of V-Model to individual IT enterprises
3.1.1	IT enterprise	objective of the V-Model
3.1.2	uniform procedure to be defined in writing	V-Model, in general, especially Project Manual
3.2.1	responsibilities and procedures	Project Manual, Project Plan, CM Plan, QA Plan
3.2.2	overall IT plan	phase model (outside V-Model)
3.3.1	preliminary and final investigation	phase model (outside V-Model)
3.3.5	combination of preliminary and final investigation	no requirement
3.3.6	documentation of results of preliminary and final investigation	phase model (outside V-Model)
3.4.1.1	realization of an IT enterprise	V-Model, in general
3.4.1.2	documentation of realization of an IT enterprise	V-Model, in general
3.4.2	procurement of hardware and software	PM2 - Placement/ Procurement, scenario Application of Off-the-Shelf-Products
3.4.3	placing of development orders	PM1.5 - Generation of Preliminary Plan, PM4 - Detailed Planning, application as a basis for contracts (Coordinating the V-Model in its Environment manual)
3.4.4.1	regulations for generation of programs	V-Model, in general, especially Project Manual
3.4.4.2	structure of programs	V-Model, in general
3.4.4.3	user-friendliness	observance while processing submodel SD
3.4.4.4	process documentation	V-Model products
3.4.5.1	test of IT procedures	submodel QA
3.4.5.2	performing tests	submodel QA
3.4.5.3	documentation of test results	submodel QA
3.4.5.4	release (who is in charge)	not regulated in V-Model
3.4.5.5	release certificate	not regulated in V-Model
3.4.5.6	release (prerequisites)	not regulated in V-Model, but mentioned in PM 6
3.4.5.7	release of externally developed procedures	submodel QA
3.4.5.8	release to be defined in writing	not regulated in V-Model
3.4.5.9	no modifications after release	Submodel CM
3.4.6.1	no unauthorized modifications after integration into production environment	Submodel CM
3.4.6.2	introducing an IT procedure	SD9 - Transition to Utilization
3.4.6.3	consulting and training after introduction of procedure	Operational Information
3.5.1	maintenance of procedures	V-Model, in general
3.5.2	written rules for the fast elimination of errors	CM Plan
3.5.3	documentation of changes	CM3 - Change Management (Configuration Control)
4	operation of IT procedures	not regulated in V-Model
5	success control	not regulated in V-Model
6.1	control of procedure development	QA3 - Process Assessment of Activites
6.2	checking correct application of procedures	PM6 - Phase Review
7.2.1	threat and risk analysis	SD1.6 - Threat and Risk Analysis, SD2.1 - Technical System Design
7.2.2	technical and organizational measures	SD1 - System Requirements Analysis, SD2 - System Design, in addition to IT framework concept

This page online • GDPA Online • Last Updated 03.Mar.2004 by C. Freericks