![]() |
![]() |
![]() |
|
![]() |
|||
| PM 1.2: Definition of Project Criteria and Development Strategy |
PM1.2 - Projektkriterien und Entwicklungsstrategie festlegen
Contents
|
|
|
|---|
Product Flow
| From | Product | to | Methods | Tool Req. | Ext. Norms | |||
|---|---|---|---|---|---|---|---|---|
| Activity | State | Chapter | Title | Activity | State | |||
| External | - | All | Project Order | - | - |
/ISO IEC 12207/
Acquis. Proc.:
Mngmt. Proc.: |
||
| PM1.1 | being proc. | Existing | Project Manual | - | - | |||
| - | - | 2 | Project Manual.Project Description |
PM1.3 PM1.4 |
being proc. | |||
| - | - | 4 | Project Manual.Development Strategy | |||||
+ "Chapter" are extra columns from the original printed version of GD 250
Handling
Project criteria, in particular such having an impact on the tailoring, must be documented in the Project Manual. The criteria are to be derived from the external specifications, from meetings with all project members, and from contractor-internal conditions. Also to be determined are project-specific requirements and characteristics, like the degree of the required assessment coverage, preliminary classifications with regard to reliability (criticality and security), utilized development and SWMM environment or the use of a particular programming language.
The SWMM Concept of the System comprises an important project requirement and a decisive criterion for the tailoring. The project management has to generate a decision base already at the beginning of the development project; this decision base is to include the concept for further development of the product, the probability of changes and the SWMM Concept.
To do so the following questions have to be answered:
Normally, a number of technical marginal conditions that have an impact on the project are already known. These technical conditions and the way they influence the project development must be listed in the project description. The effects of these technical conditions or pre-results should be taken into consideration in PM1.3 - Generation of Project-Specific V-Model, within the scope of the customization of the activity descriptions or the technical deletion conditions.
It must be defined if the system to be generated is to be evaluated. Possibly existing specifications about IT security have to be adhered to.
Explanation
Roles
| Role | Participation | ||||||
|---|---|---|---|---|---|---|---|
| Project Leader | responsible
| Project Administrator |
cooperating
| QA Manager |
advising
| IT Representative |
advising
| |
Tools Requirements
External Norms
| Norm | Process | Chapter | Obs. |
|---|---|---|---|
| /ISO IEC 12207/ | Acquisition Process | Initiation | (s. Part 3 - ISO 3.2.1) |
| Management Process | Initiation and Scope Definition | (s. Part 3 - ISO 3.2.3) |
Links to the V-Model Mailinglist
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |