Previous Next Methods Allocation  
4.8 Elementary Method "Dialog Design Modeling" (DIAL)  

  4.8 Elementarmethode "Dialog Design Modellierung" (DIAL)

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

    /Martin, 1987/ chap.16

    2 Brief Characteristic of the Method

    Objective and Purpose

    The objective of the method Dialog Design Modeling (DIAL) is to model the structure of a user dialog with screen masks. The layout of the screen masks will not be considered. The masks can only be structured into different types (e. g. type: input mask).

    Means of Representation

    Dialog diagrams are the means to represent the Dialog Design Modeling. With regard to possible notations see /Martin, 1987/ p. 318. In this connection the screen mask types are represented by certain symbols. Furthermore, the transition from one form to another is represented together with information about the transition event, as e. g. a selection by the user.

    Operational Sequence

    Based on the screen mask types relevant for the application, a dialog diagram has to be generated for each planned screen dialog process with the user. In this connection the initiations and alternative possibilities for the transitions between different mask types must be documented.

    Note: The dialog design can be improved and tested by prototyping, provided a preliminary design from the users point of view is available.

    3 Limits of the Methods Application

    - not applicable -

    4 Specification of the Methods Allocation

    No. Activity Description
    4.1 SD3.2 - Specification of Requirements for External Interfaces of SW/HW Unit Dialog Design Modeling is used to design the structure of dialog processes by defining the man-machine interface (mask type/user). DIAL only covers the logical calling sequence of different mask types in the subproduct Technical Requirements.Technical Requirements for the Interfaces with regard to the corresponding requirements for external SW interfaces. The layout of the masks as well as the operating and runtime behavior are not taken into consideration.

    5 Interfaces

    - not applicable -

    6 Literature

    /Martin, 1987/ Diagramming Standards for Analysts & Programmers
    /Ploenzke, 1991/ Ploenzke Informatik

    7 Functional Tool Requirements

    SSD02 - Supporting Specification of User Interfaces

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