Previous Next Methods Allocation  
4.30 Elementary Method "Pseudocode" (PCODE)  

  4.30 Elementarmethode "Pseudocode" (PCODE)

Contents  
  • 1 Identification/Definition of the Method
  • 2 Brief Characteristic of the Method
  • 3 Limits of the Methods Application
  • 4 Specification of the Methods Allocation
  • 5 Interfaces
  • 6 Further Literature
  • 7 Functional Tool Requirements
  • 1 Identification/Definition of the Method

    /Schönthaler, 1990/ pp. 214-219

    2 Brief Characteristic of the Method

    Objective and Purpose

    The objective of the method "Pseudocode" (PCODE) is to describe the functionality of a module or of a procedure in a structured way. To realize this, the logic operation (control) is described with predefined word symbols which are mostly adopted from a structured programming language. Either textual descriptions or programming language notations are used for the simple statements.

    Means of Representation

    Control statements like

    may be represented both as text or as a graph.

    To be noted are:

  • Nassi-Shneiderman diagrams
  • action diagrams

    Operational Sequence

    In a top-down procedure the object is described on a relatively high level and by applying the control structures and colloquial phrases for conditions and statements.

    3 Limits of the Methods Application

    - not applicable -

    4 Specification of the Methods Allocation

    No. Activity Description
    4.1 SD5.1
    Description of
    SW Component/
    Module/
    Database
    In subproduct SW Design (Module).Realization of the SW Component/ SW Module the method Pseudocode is applied for the complete functional description of the SW Component/SW Module.

    Subproduct SW Design (Module).Realization of the SW Component/ SW Module is completely covered.

    The basic method Pseudocode is applied within the scope of the subproduct SW Design (Module).Exceptional Behavior to describe the error correction actions. Subproduct SW Design (Module).Exceptional Behavior is not completely covered. The documentation of the exceptional cases and of other required parts is not supported by the Pseudocode method.

    5 Interfaces

    No. Interface Observation Information in Annex 1
    5.1 PCODE-DNAV Mode and order of the data accesses defined in the DNAV - Data Navigation Modeling method have to be adjusted to the operational sequence description in PCODE. 4.7 Interface DNAV-PCODE
    5.2 PCODE-PIM The processes defined in the process interaction diagrams are taken into consideration during the PCODE generation in the detailed design. 4.15 Interface PCODE-PIM
    5.3 PCODE-STRD The basic method Pseudocode follows after the generation of the Structured Design and is applied for the specification of the modules. 4.16 Interface PCODE-STRD
    5.4 PCODE-STM The formulation by Pseudocode has to reflect the behavior specified for the individual processes by the state diagrams. 4.17 Interface PCODE-STM

    6 Further Literature

    /Martin, 1985 Diagramming Techniques for Analysts and Programmers
    /Martin, 1987/ Diagramming Standards for Analysts & Programmers
    /McMenamin, 1984/ Essential Systems Analysis
    /Schönthaler, 1990/ Software Entwicklungswerkzeuge: Methodische Grundlagen

    7 Functional Tool Requirements

    SSD10 - Supporting Component and Module Specification

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