![]() |
![]() |
![]() |
|
![]() |
|||
| SPM02 - Supporting Planning of the Project Organization |
LPM02 - Planung der Projektorganisation unterstützen
1 Allocation to V-Model and Methods Allocation
PM1.1 - Setting up the Project
Method
2 Brief Characteristics
3 Requirements
3.1 Requirements for Interfaces
| SPM02.I.1 | Granularity |
The exchange of control parameters with SWFM01 - Workflow Management is possible for individual closed function packages of the tool by means of a disclosed, documented interface.
|
SPM02.I.1 |
Input interface to SPM01 - Managing Project Resources
|
It is possible to integrate information to resources collected with SPM01 from the object management without further transformation in order to generate project organization plans.
|
|
3.2 Requirements for the Methods Support
| SPM02.M.1 | OGC - Organizational Chart | |
| SPM02.M.1.1 | Micro organization | |
| SPM02.M.1.1.1 | Controlled, centralized organization | The representation of a controlled, centralized organization structure of a project is possible (Chief Programmer Team). |
| SPM02.M.1.1.2 | Democratic, decentralized organization | The representation of a democratic, decentralized organization structure of a project is possible (Egoless Programmer Team). |
| SPM02.M.1.2 | Macro organization | |
| SPM02.M.1.2.1 | Project-type organization | It is possible to represent a project-type organization structure. |
| SPM02.M.1.2.2 | Line-staff organization | It is possible to represent a line-staff organization structure. |
| SPM02.M.1.2.3 | Matrix organization | It is possible to represent a matrix organization structure. |
3.3 Requirements for Functions
| SPM02.F.1 | Allocation of roles | It is possible to allocate the V-Model roles to the organizational units. |
| SPM02.F.2 | Multiple roles | An organizational unit can be in charge of several roles simultaneously; in this connection, all roles not compatible with each other are rejected. |
| SPM02.F.3 | Activity types | It is possible to allocate activity types to the organizational units, according to the roles in the V-Model. |
3.4 Other Requirements
| SPM02.O.1 | Upward compatibility | It must be possible to process objects generated with an older release of the tool with the later release of that tool, without loss of information and functionality. |
| SPM02.O.2 | Procedural command language | The tool has a procedural command language that can be applied by the user to generate and run macros or procedures. |
| SPM02.O.3 | Complexity | There is no limitation of the complexity caused by the tool itself. |
![]() |
![]() |
GDPA Online
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster
![]() |