 |
 |
 |
|
 |
|||
| PM 1.3: Generation of Project-Specific V-Model |
PM1.3 - Projektspezifisches V-Modell erstellen
 Contents
|
|
|
|---|
Product Flow
| From | Product | to | Methods | Tool Req. | Ext. Norms | |||
|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | |||
| External | - | All | V-Model | - | - |
/ISO IEC 12207/
Acquis. Proc.:
Supply Proc.:
Devlp. Proc.:
Doc. Proc.:
Mngmt. Proc.: |
||
| External | - | All | Project Order | - | - | |||
| PM1.1 PM1.2 |
being proc. | Existing | Project Manual | - | - | |||
| - | - | 3 | Project Manual.Overview | PM1.4 | being proc. | |||
| - | - | 5 | Project Manual.Project-Specific V-Model | SPM03 | ||||
| - | - | 7 | Project Manual.Participation of Customer | |||||
+ "Chapter" are extra columns from the original printed version of GD 250
Handling
The goal of this activity is to realize the project-specific customization of the V-Model. The result is documented in the Project Manual which is to be the basis for communications between customer and contractor (in the case of an external placement).
The Project Manual is generated in a number of substeps. The tender-relevant tailoring is comprised of the steps "Definition of the Form of the Project-Specific V-Model", "Selection and Customization of Activities and Products", and "Definition of Deletion Conditions for the Technical Tailoring". Substeps that are not mandatory have been marked as "optional".
* Definition of the Project-Specific V-Model
- generation of a project-specific V-Model as subset of the generic V-Model or
- referencing the V-Model activities and products
* Selection and Customization of Activities and Product
- selection of activity and product classes basically advisable for the project
It must be differentiated how far a project type defined in Part 3 Collection of Manuals conforms with the planned project. If no suitable project type can be found it is possible to use the deletion conditions in Part 3 Collection of Manuals. The aim is to define deletion conditions for the activity and product classes not relevant in the project. The reasons for the deletions are entered into the chapter Project Manual.Overview. Activity and product classes without deletion conditions have to be entered into the chapter Project Manual.Project-Specific V-Model - Customization of Activity Descriptions (optional)
The descriptions of the V-Model activities include case descriptions and differentiations of all possible project scenarios and conditions. In a real project these case differentiations can be omitted; the descriptions may refer to real project conditions. Frequently, technical facts or pre-results already exist. The activity descriptions should individually refer to them and also to the resulting consequences.
This means that all non-relevant parts of the descriptions of the activities, recommendations and explanations can be deleted. These deletions may make it necessary to adjust the wording of the descriptions. To the remaining text real project references may be added, like references to preliminary investigations, existing results, agreements or notes to whom (contractor, subcontractor) the activity is relevant. The latter is particularly important if only one common Project Manual is to be written for both contractor and subcontractor.
So, if the customer accepts the Project Manual, this also means that he accepts the deletions and text modifications.
* Definition of Deletion Conditions for the Technical Tailoring
When starting a project, it should already be determined under which conditions real instantiations of activity and product classes can be dropped in that project. Technical conditions from Part 3 Collection of Manuals ("Tailoring" manual) may be used for this. The deletion conditions relevant for the project must be applied for activities and products of the project-specific V-Model (chapter Project Manual.Overview), and, during the project in activity PM4 - Detailed Planning, to the individual activities.* Participation of Customer
If the customer participates in the project or not can be decided by himself. The activities/roles matrices must be customized, according to his requests and possibilities (see Part 3 Collection of Manuals, Concept of Roles in the V-Model manual). This information is of importance to the contractor so he knows where to expect possible opposition from the customer. Any other rights/responsibilities of the customer can be defined in the contract.* Generation of Overview of Contract-Related Specifications
The Project Manual must contain specifications relevant to the contract (activities and products to be realized or deleted, objects to be delivered, participation of the customer) in a clearly laid out form. Any products not to be delivered have to be considered as internal development documents.Also required is an agreement and assessment of the Project Manual between the customer (role Project Manager or Q Manager) and the QA Manager in the project with regard to completeness, clarity, and feasibility.
If the assessment is successful the Project Manual changes to state "accepted".
Explanation
The QA Plan lists for which activities and products the assessment activities (QA2 - Assessment Preparation and QA4 - Product Assessment) have to be realized in the project.
The Project Manual is (contrary to the Project Plan) a predominantly unchanging, static document.
Roles
| Role | Participation | ||||
|---|---|---|---|---|---|
| Project Leader | responsible
| Project Administrator |
cooperating
| QA Manager |
cooperating
| |
Tools Requirements
| Product | Functional Tools Requirements |
|---|---|
| Project Manual.Project-Specific V-Model | SPM03 - Supporting Tender-Relevant Tailoring |
External Norms
| Norm | Process | Chapter | Obs. |
|---|---|---|---|
| /ISO IEC 12207/ | Acquisition Process | Request-for-Proposal Preparation | (s. Part 3 - ISO 3.2.1) |
| Supply Process | Preparation of Response | (s. Part 3 - ISO 3.2.1) | |
| Development Process | Process Implementation | (s. Part 3 - ISO 3.2.1) | |
| Documentation Process | Process Implementation | (s. Part 3 - ISO 3.2.2) | |
| Management Process | Planning | (s. Part 3 - ISO 3.2.3) |
Links to the V-Model Mailinglist
Mail 0628 - Re: Tailoring / Individuelle Anpassungen (628)
|
|
|
This page online • GDPA Online • Last Updated 05.Feb.2002 by C. Freericks |