Previous Next Methods Allocation  
2 Introduction to the Methods Allocation  

  2. Einführung in die Methodenzuordnung

Contents  
  • 2 Introduction to the Methods Allocation
  • 2.1 Terminology
  • 2.2 Structure of the Methods Standard
  • 2.3 Method Overview
  • 2 Introduction to the Methods Allocation

    The Methods Allocation is not intended as a method manual. Therefore, the description of the methods is as brief as possible. More detailed descriptions can be found in the corresponding definitions and examples referred to.

    Various tools support a method often in different, customized versions. Since the Methods Allocation is not to define how certain tools are to be applied, tool-independent definitions must be set up. This implies that the Methods Allocation is limited to the base concept of the methods and does not define rules about the notation (symbols) within the diagrams and the precise syntax of text-related specifications, etc.

    Notations are defined within the scope of the operationalization.

    The Methods Allocation does not set up rules for activities for which the V-Model intends a flexible process. For example, this is true for the integration activities, SD7 - SW Integration and SD8 - System Integration, where the allocation of methods is "missing" in order to avoid an undesirable and unnecessary limitation of the implemented flexibility.

    The following sections explain the basing terminology of the Methods Allocation and the structure and description pattern used for the definition of methods.

    2.1 Terminology

    The following definition of terms is the basis used to describe, allocate, and delimit the methods of the Methods Allocation.

    2.1.1 Methods

    Main features of software engineering methods are: In this connection, either the procedure or the representation may be more important for individual methods (e. g. with regard to QA methods, representation means are of subordinated importance, the functional process is the core of the method; with regard to PM methods like BAR - Bar Plan, OGC - Organizational Chart, etc., it is the other way around).

    Software engineering methods are of different complexity and potential. Therefore, the differentiation into complex methods (also: combined methods; method groups) and in elementary methods (also: basic methods) is reasonable and will be specified in the following.

    2.1.2 Complex Methods

    The term complex methods refers to procedures including different methodical components and integrating them in an overall method. The methodological components as part of the complex methods are not automatically identical with the elementary methods as defined and used in the method allocation. This means that for a component "Information Modeling" from a complex method it must first be verified if the content of the specification matches elementary method ER - E/R Modeling. Ideally, both refer to the same definition source so the equivalent of the elementary method and the methodic components is easy to determine.

    Complex methods usually cover several aspects of the system (e. g. the functional aspect, the data aspect, etc.; see also Figure 1.1) and several activities of the development (e. g. analysis, preliminary design, etc.).

    Examples for complex methods are: SA, IEM

    As a whole, complex methods are not part of the Methods Standard. They are described in Annex 2.

    2.1.3 Elementary Methods

    The term elementary methods refers to the methodical procedures describing a specific, delimited aspect of the system (e. g. functional aspect, data aspect, etc.) and/or a certain section of the software development (e. g. analysis, preliminary design, etc.) or the accompanying activities (PM, CM, QA).

    In this connection, it is irrelevant whether the basic method is comprised of several steps and possibly generates several (sub-) results (example: DFM - Data Flow Modeling) or the basic method exactly generates one result (example: Decision Table Technique).

    Examples for basic methods are: ER - E/R Modeling, STM - State Transition Modeling

    Basic methods are allocated to individual V-Model activities and (sub-) products in the Methods Standard (see Figure 2.1).

    Figure 2.1
    Figure 2.1: Overview of Functions in Submodel SD

    When applying a complex method it must be represented within the scope of the operationalization that the methodical components of the complex method meet the requirements of the basic methods described in the Methods Allocation. To do so, the three steps described in chapter 1.3 Application of the Methods Allocation have to be carried out.

    2.1.4 Categories of Methods

    The term category of methods refers to those basic methods that apply different methodical approaches for the solution of a certain family of activities or problems. The common characteristics of these basic methods are defined in the Methods Allocation. The individual potential methods of each category are described in more detail in Annex 1 to the Methods Allocation.

    Examples for categories of methods are: design verification, estimation models, reliability models.

    To specify a category of methods in the Methods Allocation means that the application of one method is required from this category.

    2.1.5 Method Interfaces

    When applying several basic methods during the development process the reference points might occur in the following form: These reference points are referred to as Method Interfaces.

    Examples for method interfaces are: interface DFM - Data Flow Modeling - ER - E/R Modeling, interface CFM - Control Flow Modeling - STM - State Transition Modeling.

    The characterization of the method interfaces is part of the Methods Allocation. Annex 1 to the Methods Allocation includes a detailed description of the individual interfaces.

    2.2 Structure of the Methods Standard

    The basic elements of the Methods Allocation are the allocation tables of basic methods to (sub-) activities and (sub-) products of the V-Model as well as the descriptions of the individual basic methods.

    2.2.1 Allocation Tables

    Chapter 3 Allocation Tables of the Methods Allocation comprises the allocation tables that are structured according to the four submodels.

    The allocation tables have the following structure for each main or subactivity of the V-Model which are no further hierarchically partitioned (see Figure 2.2):

    Figure 2.2
    Figure 2.2: Methods Allocation, Allocation Table

    For the chapters of a product that is generated by the corresponding (sub-) activity the basic method which has to be applied during its generation is referred to.

    If the table does not include an entry for a V-Model (sub-) activity or for a V-Model product or chapter, no further regulation is required by the Methods Allocation beyond the V-Model.

    For each basic method a unique abbreviation exists which is used for the identification in the table entries. Chapter 2.3 Method Overview contains an overview of all these abbreviations.

    2.2.2 Explanation of Footnotes and Nomenclature in the Tables

    If one basic method is only to be used under certain conditions, a reference is made in the allocation table by means of a footnote. The number of the footnote is found right after the corresponding method.

    The text of the footnote informs about the manner of limitation.

    If several basic methods are listed for one (sub-) chapter it will be explained if these are alternatives or if the methods are required to be complementary:

    Subsequent to the allocation tables the footnote text passages are listed in chapter 3.5.

    If the entry into the left column of the table contains a Space " ", this refers to the fact that the methodological standardization does not refer to a certain product, but to the realization of the entire activity.

    2.2.3 Description of the Methods

    Chapter 4 of the Methods Standard includes the following additional information for each of the methods listed in the allocation tables:
    1. Identification/Definition of the Method
      Reference to a definitely to be complied definition of syntax and semantics.
    2. Brief Characteristic of the Method
      Description of objective and purpose, means of representation and operational sequence of the method.
    3. Limits of the Method Application
      Criteria when it is not advisable or only partly advisable to apply the method, or the application becomes limited within the scope of the V-Model.
    4. Specification of the Methods Allocation
      Here explanations are given of all those facts that are relevant for the application of a method at a certain stage in the V-Model.
    5. Interfaces
      Information about the interfaces to be considered to other basic methods.
    6. Further Literature

    2.3 Method Overview

    The following table contains a list of all abbreviations for basic methods and categories of methods used in the allocation tables (chapter 3). Furthermore, a reference is made to the corresponding description of the method in chapter 4.

    Abbrev. Method Name Reference
    to Method
    Description
    AUD Audit 4.1
    ACC Analysis of Covert Channels 4.2
    BAR Bar Plan (Chart) 4.3
    TREE Tree Diagram 4.4
    BBTD Black Box Test Case Design 4.5
    CRC Class Responsibility Collaboration 4.6
    DFM Data Flow Modeling 4.7
    DIAL Dialog Design Modeling 4.8
    DNAV Data Navigation Modeling 4.9
    DVER Design Verification 4.10
    ELH Entity Life History 4.11
    ER E/R Modeling 4.12
    DTAB Decision Table Technique 4.13
    EVT Earned Value Method 4.14
    EXPM Expertise Model 4.15
    FCTD Functional Decomposition 4.16
    FMEA Failure Mode Effect Analysis 4.17
    FNET Function Net Modeling 4.18
    FS Formal Specification 4.19
    IAM Interaction Modeling 4.20
    CFM Control Flow Modeling 4.21
    COM Class/Object Modeling 4.22
    LOGM Logical DB Modeling 4.23
    MODIAG Module Diagrams 4.24
    NORM Normalization 4.25
    NPT Network Planning Technique 4.26
    BA Benefit Analysis 4.27
    ODT Object Design Technique 4.28
    OGC Organizational Chart 4.29
    PCODE Pseudocode 4.30
    PRODIAG Process Diagrams 4.31
    PVER Program Verification 4.32
    PIM Process Interaction Modeling 4.33
    REV Review 4.34
    SIMU Simulation Models 4.35
    EMOD Estimation Models 4.36
    SSM Subsystem Modeling 4.37
    STAT Static Analysis 4.38
    STRD Structured Design 4.39
    SBM System Behavior Models 4.40
    T Test 4.41
    TRDA Trend Analysis 4.42
    UCM Use Case Modeling 4.43
    WBTD White Box Test Case Design 4.44
    STM State Transition Modeling 4.45
    STMO State Modeling in the OO Field 4.46
    RELM Reliability Models 4.47

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