Previous Next V-Model Official Homepage by IABG  
Part 3: Collection of Manuals Homepage  
Tailoring Homepage  
T.4.3.4 Submodel SD  

  T.4.3.4 Submodell SE

Contents  
  • Table
  • Links to the V-Model Mailinglist

    • Table

    BT TT Activity Reason for Deletion Effects
    - - SD1 - System Requirements Analysis   
    SD1.1 - Recording of Actual Status and Analysis
  • This is a maintenance/modification project
  • The actual state has no impact on the new development.
    		• Chapter User Requirements.Actual Status and Current Analysis is omitted.
    SD1.2 - Description of Application System
  • The external specifications meet product design User Requirements.Preliminary System Description and User Requirements. IT Security Objective both with regard to the content and with regard to the form.
    		• Chapters User Requirements.Preliminary System Description and User Requirements. IT Security Objective are omitted.
    SD1.3 - Definition of Criticality and Quality Requirements
  • Apart from the functionality of the System to be developed, no other quality requirements are relevant. The System is used as a prototype to prove the feasibility. An assessment of the criticality is not required.
    		• Chapters User Requirements.Quality Requirements and User Requirements.Criticality of the System are omitted.
    SD1.4 - Definition of Marginal Conditions
  • Technical or organizational marginal conditions from a profession point of view are not expected. Requirements of a technical kind are sufficiently described in product Technical Requirements.
    		• Chapter User Requirements.Marginal Conditions is omitted.
    SD1.5 - User-Level System Structure
  • The external specifications meet product design User Requirements.Organizational Embedding, User Requirements.Utilization, and User Requirements.Description of the Functionality both with regard to the content and with regard to the form.
    		• Chapters User Requirements.Organizational Embedding, User Requirements.Utilization and User Requirements.Description of the Functionality are omitted.
    SD1.6 - Threat and Risk Analysis
  • The threat aspect is not relevant; in the case of system faults, only few risks are expected.
  • The regulations of the basic protection are observed (generally guaranteed on the level of the user organization) and neither classified data nor data related to a person are processed.
    		•  Chapters User Requirements.Threat and Risk Analysis and User Requirements.IT Security are omitted.
    SD1.7 - Realization of Requirements Controlling
  • The requirements can be realized economically.
    		• -
    SD1.8 - Generation of Software Maintenance and Modification Concept
  • This is a SWMM project and product SWMM Concept is available.
    		• Product SWMM Concept is an external product.
    - - SD2 - System Design   
    - - SD2.1 - Technical System Design   
    SD2.2 - Realization of Efficiency Analysis
  • Security aspects are not relevant.
    		•  Chapter System Architecture .IT Security Concept is omitted.
    SD2.3 - Investigation of Feasibility
  • Only one exists solution was created on the basis of sufficient experience with problems in connection with applications. The application and development environment is known and can be used by taking only a small development risk.
  • The approach for the solution must be specified or determined by means of preliminary studies.
    		•  Chapter System Architecture .Feasibility Studies is omitted.
    - SD2.4 - Allocation of User Requirements
  • The allocation of user requirements results from the description of the technical structure in activity SD2.1.
    		•  -
    - SD2.5 - Interface Description
  • The System to be developed does not include any complex interfaces.
    		•  Product Interface Description is omitted.
    - SD2.6 - Specification of System Integration
  • The integration can be deducted from the product System Architecture and does not require any further explanations.
    		• Product Integration Plan is omitted.
    SD3 - SW/HW Requirements Analysis
  • The required object is a SW Unit/HW Unit, and the external specifications meet the product design "Technical Requirements" both with regard to the content and with regard to the form.
    		• Product Technical Requirements is an external product.
    - SD3.1 - Definition of General Requirements from SW/HW Unit Point of View
  • General Requirements have already been sufficiently considered in activity SD2.1
    		• Activity SD2.1 must not be deleted.
    - SD3.2 - Specification of Requirements for External Interfaces of SW/HW Unit
  • The interfaces have already been sufficiently described in activity SD2.5.
    		•  Activity SD2.5 must not be deleted.
    SD3.3 - Definition of Requirements for the Functionality
  • The required object is a SW Unit/HW Unit, and the external specifications meet the chapter 5.2 of the product schema Technical Requirements.Overall Function of Element both with regard to the content and with regard to the form.
    		• The requirements for functionality come from "outside".
    - SD3.4 - Definition of Requirements for the Quality of the SW/HS Unit
  • Quality requirements were already sufficiently described for the system elements in product User Requirements.
    		• Chapter Technical Requirements.Quality Requirements is omitted.
    - SD3.5 - Definition of Requirements for the Development and SWMM Environment
  • The requirements for development and SWMM environment have already been sufficiently described in activity SD2.1
    		• Activity SD2.1 must not be deleted.
    SD4 - Preliminary SW Design
  • SW Unit is realized by an off-the-shelf product.
    		• Product SW Architecture is omitted.
    - - SD4.1 - SW Architecture Design   
    - SD4.2 - Design of Internal and External SW Interfaces
  • The interfaces have already been sufficiently described in activities SD2.5, SD3.2 or SD4.1-SW respectively.
    		•  -
    - SD4.3 - Specification of SW Integration
  • The integration can be derived from the product SW Architecture and does not require any explanation.
    		•  The description of the integration measures in product Integration Plan with regard to the SW Unit is omitted.
    SD5 - Detailed SW Design
  • SW Unit is realized with an off-the-shelf product.
  • The algorithms has already been sufficiently described in the SW Architecture.
    		• Product SW Design (Module/Database) is omitted.
    - SD5.1 - Description of SW Component/Module/Database
  • The realization (in form of a programming specification) of the SW Component/Module/Database has already been described in product "SW Architecture" , and the SW Component (SW Module/Database is neither critical nor complex.
    		• Chapter SW Design (Module).SW Component/SW Module Description/SW Design (Database).Database Description is omitted.
    - SD5.2 - Analysis of Resources and Time Requirements
  • The assessed module only requires a small part of the available resources, this is made plausible in a reconstructably way within the scope of the module document (SW design) (e. g. by a brief explanation).
    		• Chapter SW Design (Module).Characteristic Quantities/SW Design (Database).Characteristic Quantities is omitted.
    SD6 - SW Implementation
  • SW Unit is realized by an off-the-shelf product.
    		• Product Implementation Documents is omitted.
    - - SD6.1 - Coding of SW Modules   
    - - SD6.2 - Realization of Database   
    SD6.3 - Self-Assesment of the SW Module/Database
  • The Developer is in charge of the self assessment, it is not considered by the Project Leader in product Project Plan (allocation of time and resources).
    		• -
    SD7 - SW Integration
  • SW Unit is realized by an off-the-shelf product.
    		•  SW Integration is omitted.
    - SD7.1 - Integration into SW Component
  • The SW Architecture does not plan to include SW Components.
    		• -
    SD7.2 - Self-Assessment of SW Component
  • The Developer is in charge of the selftest, it is not considered by the Project Leader in product Project Plan (allocation of time and resources).
    		• -
    - - SD7.3 - Integration into SW Unit   
    SD 7.4-SW Self Assessment of SW Unit
  • The Developer is in charge of the selftest, it is not considered by the Project Leader in product Project Plan (allocation of time and resources).
    		• -
    - - SD8 - System Integration   
    - SD8.1 - Integration into System
  • The System only consists of one SW Unit.
    		• -
    SD8.2 - Self-Assessment of the System
  • The Developer is in charge of the selftest, it is not considered by the Project Leader in product Project Plan (allocation of time and resources).
    		• -
    - - SD8.3 - Product Supply   
    - - SD9 - Transition to Utilization   
    SD9.1 - Contribution to Support for Introduction
  • A contribution to support the introduction is not required.
    		• -
    SD9.2 - System Installation
  • The System is already developed in the final environment.
    		• -
    - - SD9.3 - Putting into Operation   

    Table T.27: Deletion of Activities for Submodel SD

    Links to the V-Model Mailinglist

    Mail 0578 - Re: Kenngrößen (578)

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