Previous Next Methods Allocation  
3 Allocation Tables  

Contents  
  • 3.1 Allocation Tables for Submodel SD
  • 3.2 Allocation Tables for Submodel QA
  • 3.3 Allocation Tables for Submodel CM
  • 3.4 Allocation Tables for Submodel PM
  • 3.5 List of Footnotes
  • 3.1 Allocation Tables for Submodel SD

    SD1.1 - Recording of Actual Status and Analysis
    User Requirements 2 Actual Status and Current Analysis ER (1) + DFM + FCTD + PRODIAG (2) + UCM (2) + STMO (3) + IAM (2)
    SD1.2 - Description of Application System
    User Requirements 3 IT Security Objective  
    6 User-level Requirements  
    6.1 Preliminary System Description DFM + CRC (2)+ COM (2)+ SSM (2)+ PRODIAG (2) + UCM (2) + STMO (3) + IAM (2)
    SD1.3 - Definition of Criticality and Quality Requirements
    User Requirements 6 User-level Requirements  
    6.4 Criticality of the System FMEA (5)
    6.7 Quality Requirements RELM (4)
    SD1.4 - Definition of Marginal Conditions
    User Requirements 7 Marginal Conditions COM (2) + CRC (2)+ PRODIAG (2) + UCM (2) + STMO (3) + IAM (2)
    SD1.5 - User-Level System Structure
    User Requirements 6 User-level Requirements  
    6.2 Organizational Embedding SSM (2)
    6.3 Utilization UCM (2)
    6.5 External Interfaces  
    6.6 Description of the Functionality SBM (6)/ FNET + ER (1) + DFM + FCTD + EXPM + CRC (2)+ COM (2)+ STMO (3) + IAM (2)
    SD1.6 - Threat and Risk Analysis
    User Requirements 4 Threat and Risk Analysis  
    5 IT Security  
    SD1.7 - Realization of Requirements Controlling
    Protocol      
    SD1.8 - Generation of Software Maintenance and Modification Concept
    SWMM Concept 2 Marginal Conditions  
    3 System Description  
    4 Evaluation with Regard to SWMM  
    5 SWMM Organization  
    5.1 Organizational Structure OGC
    5.2 Tasks and Responsibilities  
    5.3 Interfaces  
    6 SWMM Process  
    7 Resources  
    8 Making SWMM Ready to Work  
    9 Transition to Utilization BAR
    SD2.1 - Technical System Design
    System Architecture 2 System Structure  
    2.1 Representation of the Technical System Architecture  
    2.1.1 Technical System Structure CRC (2)+ COM (2)+ SSM (2)+ PRODIAG (2)
    2.1.2 Identification of Interfaces  
    2.2 Explanation of the Cooperation of Technical Elements IAM (2)
    3 Realization  
    3.1 Solution Proposals FCTD + CRC (2)+ COM (2)+ SSM (2)
    4 IT Security Concept  
    5 IT Security Model  
    Technical Requirements 2 General Requirements  
    3 Technical Requirements for the Overall System  
    5.x.1 Identification of the Element  
    5.x.2 Overall Function of Element COM (2)+ CRC (2)+ PRODIAG (2)
    5.x.3 Technical Requirements for the Interfaces COM (2)+ SSM (2)
    5.x.4 Quality Requirements  
    5.x.5 Technical Requirements for the Development and SWMM Environment  
    Interface Overview 2 System-External Interfaces DFM + COM (2)
    3 System-Internal Interfaces DFM + COM (2)+ SSM (2)
    SD2.2 - Realization of Efficiency Analysis
    System Architecture 4 IT Security Concept  
    SD2.3 - Investigation of Feasibility
    System Architecture 3 Realization  
    3.2 Feasibility Studies BA (1)+ SIMU (9)
    SD2.4 - Allocation of User Requirements
    System Architecture 2 System Structure  
    2.1 Representation of the Technical System Architecture  
    2.1.3 Requirements Allocation ER (10)
    SD2.5 - Interface Description
    Interface Description 2 Description of the interfaces COM (2)+ SSM (2)+ FS (11)+ DVER (12)+ ACC (13)+ STMO (3) + IAM (2)
    SD2.6 - Specification of System Integration
    Integration Plan 2 Integration Products and Strategies  
    3 Marginal Integration Conditions  
    4 Organization of the Integration  
    4.1 Integration Network Plan BAR (14)/ NPT
    4.2 Staff  
    4.3 Responsibilities  
    5 Integration Measures  
    5.1 Required Products  
    5.2 Integration Instructions DTAB (15)
    5.3 Special Measures  
    SD3.1 - Definition of General Requirements from SW/HW Unit Point of View
    Technical Requirements 2 General Requirements  
    5 Technical Requirements for SW Units/HW Units  
    5.1 Identification of the Element  
    SD3.2 - Specification of Requirements for External Interfaces of SW/HW Unit
    Technical Requirements 5 Technical Requirements for SW/HW Units  
    5.3 Technical Requirements for the Interfaces DFM + CFM (16)+ COM (2)+ IAM (2)+ STMO (3)
    5.3.1 Technical Requirements for the User Interface DIAL (17)
    5.3.2 Technical Requirements for Other Interfaces  
    SD 3.3 - Definition of Requirements for the Functionality
    Technical Requirements 5 Technical Requirements for SW/HW Units
    5.2 Overall Function of Element FCTD + SBM (6)/ FNET + DFM + ER (1) + ELH (18) + DTAB (15) + ELH (18) + STM (19)/ STMO (3) + COM (2) + CRC (2)+ IAM (2)
    SD 3.4 - Definition of Requirements for the Quality of the SW/HW Unit
    Technical Requirements 5 Technical Requirements for SW/HW Units  
    5.4 Quality Requirements  
    5.4.1 Criticality FMEA (5)
    5.4.2 Technical Requirements for the IT Security  
    5.4.3 Technical Requirements for Other Quality Characteristics RELM (4)
    SD 3.5 - Definition of Requirements for the Development and SWMM Environment
    Technical Requirements 5.5 Requirements for the Development and SWMM Environment PRODIAG (2)
    SD 4.1-SW - SW Architecture Design
    SW Architecture 2 Solution Proposals COM (2) + SSM (2) + MODIAG (2) + PRODIAG (2)
    3 Modularization/Database Design COM (2) + SSM (2)+ MODIAG (2) + PRODIAG (2)
    3.1 Overview of SW Components, SW Modules, Processes and Databases STRD (20) / ODT
    3.2 Individual Descriptions PIM (21) + STM (19) + FS (22) + DVER (12) + ACC (13)
    3.3 Dynamic Sequence Model PIM (21) + FS (22) + DVER (12) + ACC (13) + IAM (2)
    3.4 Criticality of the SW Components/SW Modules/Processes/ Databases  
    3.5 Other Design Decisions  
    4 Interfaces COM (2) + SSM (2)
    4.1 External Interfaces of the SW Unit  
    4.2 Internal Interfaces of the SW Unit  
    5 Requirements Allocation  
    Interface Overview 2 System-External Interfaces  
    3 System-Internal Interfaces MODIAG (2) + COM (2) + SSM (2)
    Operational Information
    SD 4.2-SW - Design of Internal and External SW Interfaces
    Interface Description 2 Description of the Interfaces COM (2) + FS (22) + DVER (12) + ACC (13) + STMO (3) + IAM (2)
    SD 4.3-SW - Specification of SW Integration
    Integration Plan 2 Integration Products and Strategies
    3 Marginal Integration Conditions  
    3.1 Integration/Assessment Environment  
    3.2 Priorities  
    3.3 Risks  
    3.4 Other Marginal Conditions  
    4 Organization of the Integration  
    4.1 Integration Network Plan BAR (14)/ NPT
    4.2 Staff  
    4.3 Responsibilities  
    5 Integration Measures  
    5.1 Required Products  
    5.2 Integration Rules DTAB (15)
    5.3 Special Measures  
    Operational Information
    SD 5.1-SW - Description of SW Component/Module/Database
    SW Design 2 SW Component/SW Module Description COM (2) + CRC (2) + MODIAG (2) + IAM (2) + FS (22) + DVER (12) + ACC (13)
    2.1 Characterization of the Task  
    2.2 Environment  
    2.3 Interfaces  
    2.4 Realization of the SW Component/SW Module PCODE + STMO (3)
    2.5 Local Data  
    2.6 Exceptional Behavior PCODE
    2 Database Description COM (2) + CRC (2)
    2.1 DBMS Name  
    2.2 Schema Definition LOGM + NORM + DNAV (2)
    Data Dictionary 2 Data Description FS (22) + DVER (12) + ACC (13)
    3 Data Realization FS (22) + DVER (12) + ACC (13)
    Operational Information
    SD 5.2-SW - Analysis of Resources and Time Requirements
    SW Design 3 Characteristic Quantities SIMU (9) + ACC (13)
    SD 6.1-SW - Coding of SW Modules
    Implementation Documents 2 Code PVER (24)+ ACC (13)
    3 Procedures  
    4 Listings/Protocols  
    SD 6.2-SW - Realization of Database
    Implementation Documents 2 Code PVER (24)+ ACC (13)
    3 Procedures  
    4 Listings/Protocols  
    SD 6.3-SW - Self-Assessment of the SW Module/Database
    Implementation Documents 2 Code PVER (24)+ ACC (13)
    3 Procedures  
    4 Listings/Protocols  
    SD 7-SW - SW Integration
    SD 8 - System Integration
    SD 9 - Transition to Utilization

    3.5 List of Footnotes

    1 Method ER is to be applied for information systems.
    2 The methods have to be applied in object-oriented developments.
    3 Method STMO is to be applied for the dynamic system modeling in object-oriented procedures.
    4 Method RELM is to be applied in case of high demands to realiability.
    5 Method FMEA is to be applied in case where reliability requirements are high.
    6 Method SBM is to be applied for realtime applications or respectively distributed systems with a high level of criticality. Method FNET is to be applied for information systems.
    7 Method EXPM is intended for knowledge-based systems.
    8 Method BA is to be applied if
    - a complex decision has to be made and if
    - that decision is not based on external factors (i.e. factors beyond the evaluation criteria)
    9 Method SIMU is to be applied if reliability requirements are high nd the use conditions are so complex that static investigations with regard to feasibility and resource requirements are not sufficient.
    10 Method ER is to be applied for Information Systems and only if modifications of the E/R models become necessary.
    11 Method FS is to be applied in case of special requirements with regard to correctness, e. g. based on very high criticality.
    12 A formal specification on two different abstraction levels is required for the application of DVER. Because of the great effort, the most critical portions of a specification have to be selected for which the DVER has to be applied. According to [ITSEC], method DVER is required for the proof of the formal security model with the evaluation level E4, for the proof of consistency between security model and preliminary design DVER is required with the evaluation level E6.
    13 Method ACC must be applied according to [ITSEC].
    14 Method NPT is to be applied if very complex call and integration relations among the functional units have to be taken into consideration which in particular break through the hierarchical top-down or botteom-down relations several times; otherwise method BAR is to be applied.
    15 Method DTAB is to be applied for the description of complex facts and circumstances.
    16 Method CFM is to be applied for event-driven systems in case it is required for the representation of the control flow based on a high complexity.
    17 Method DIAL is to be applied for dialogue functions with screen masks.
    18 Methodis to be applied for information systems.
    19 Method STD is to be applied if complex situations have to be considered during the run of the function or the process.
    20 Method ODT is to be applied for a realtime-oriented development with parallel processes; otherwise method STRD has to be applied.
    21 Method PIM is to be applied when the design contains several processes to be parallelly executed.
    22 Method FS is to be applied in case of special requirements to correctness, e. g. based on very high criticality. According to [ITSEC], FS is required for the description of the formal security model with the evaluation level E4, for the preliminary design FS is required with the evaluation level E6.
    23 Method DNAV is to be applied for hierarchical or network-like database types.
    24 Method PVER is to be applied in cases of special requirements to the correctness. A formal specification and a program that shall meet the specification are required for the application of PVER. Because of the great effort, the most critical program portions have to be selected for an application of PVER.
    25 Method BAR is to be applied if no complex arrangement relations and logical interdependences exist during the detailed planning; otherwise method NPT has to be applied.
    26 Methode STAT is to be applied if contents of the object to be assessed are structured according to a standard formalism.
    27 Method T is to be applied if contents of the object to be assessed are structured according to a specified formalism allowing a dynamic execution.
    28 Method SIMU is to be applied if the test cannot completely handle the performance and error proof since - among other things - special limitations, assumptions, and environmental conditions have to be taken into consideration.
    29 Method T is to be applied if automated assessment procedures are to be used.
    30 Method FMEA is to be applied if
    - high restrictive planned values (deadlines, costs) or
    - high requirements
    have to be fulfilled in the project.
    31 Method NPT is to be applied if complex arrangement relations and logical interdependences exist in the detailed planning.

    Previous Next GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster