Previous Next Methods Allocation  
Annex 2  
2.2 The complex Method IEM  

  IEM - Information Engineering Method

Contents  
  • 1 Brief Description
  • 2 Tabular Comparison
  • 3 Specification of the Allocation
  • 4 Literature
  • 1 Brief Description

    IEM (Information Engineering Method) consists of a set of coordinated concepts and methods for the integrated development of commercial software. IEM is predominantly applied for the design of information systems, from the planning to the generation of programs and databases. IEM supports the entire software development process within the scope of a phase concept with the following main phases: strategic information planning, user-level system analysis, technical system design, implementation. IEM requires a development database in which all the results derived from the various methods are counterchecked and consolidated so the development database is only comprised of assessed and consistent information.

    The methodical components of IEM are:

    2 Tabular Comparison

    The following table compares the basic methods of the GD 251 with the methodical components of IEM. In the case where there is no entry in the right column of the table, IEM has no corresponding component. Otherwise an entry refers to the corresponding part. In the IEM literature section 3 of the comparison contains explanations for the entries. Entries identified with (*) refer to basic methods completely covered by IEM. These are not further described in section 3.

    Comparison of the Basic Methods and the
    Methodological Components of IEM
    AUD - Audit  
    ACC - Analysis of Covert Channels (in Annex)  
    BAR - Bar Plan  
    TREE - Tree Diagram Decomposition Diagrams /Martin, 1987/ chap. 7 (*)
    BBTD - Black Box Test Case Design  
    CRC - Class Responsibility Collaboration  
    DIAL - Dialog Design Modeling Dialog Design Diagrams
    /Martin, 1987/ chap. 16 (*)
    /Martin, 1990b/ p. 76 (*)
    DFM - Data Flow Modeling Data Flow Diagrams
    /Martin, 1987/ chap. 9 (*)
    DNAV - Data Navigation Modeling Data Navigation Diagrams
    /Martin, 1987/ chap. 12 (*)
    DVER - Design Verification  
    ELH - Entity Life History Entity Life Cycles
    /Martin, 1987/ p. 306-307 (*)
    ER - E/R Modeling Entity Relationship Diagrams
    /Martin, 1987/ chap. 11 (*)
    /Martin, 1990a/ chap. 9 (*)
    DTAB - Decision Table Technique Decision Trees and Decision Tables
    /Martin, 1987/ p. 294-296 (*)
    EVT - Earned Value Method  
    EXPM - Expertise Model  
    FCTD - Functional Decomposition Decomposition Diagrams /Martin, 1987/ chap. 7 (*)
    FMEA - Failure Mode Effect Analysis  
    FNET - Function Net Modeling Dependency Diagrams
    /Martin, 1990a/ chap. 14
    FS - Formal Specification  
    IAM - Interaction Modeling  
    CFM - Control Flow Modeling  
    COM - Class/Object Modeling  
    LOGM - Logical DB Modeling Physical Database Design /Martin, 1990b/ chap. 15 S. 325-341
    MODIAG - Module Diagrams  
    NORM - Normalization Normalization /Martin, 1990a/ chap. 12 (*)
    NPT - Network Planning Technique  
    BA - Benefit Analysis  
    ODT - Object Design Technique  
    OGC - Organizational Chart  
    PCODE - Pseudocode Action Diagrams /Martin, 1990b/ Appendix II (*)
    PRODIAG - Process Diagrams  
    PVER - Program Verification  
    PIM - Process Interaction Modeling  
    REV - Review  
    SIMU - Simulation Models  
    EMOD - Estimation Models  
    SSM - Subsystem Modeling  
    STAT - Static Analysis  
    STRD - Structured Design Action Diagrams
    /Martin, 1990b/ Appendix II
    SBM - System Behavior Models  
    T - Test  
    TRDA - Trend Analysis  
    UCM - Use Case Modeling  
    WBTD - White Box Test Case Design  
    STM - State Transition Modeling State Transition Diagrams /Martin, 1987/ chap. 15 (*)
    STMO - State Modeling in the OO Field  
    RELM - Reliability Models  

    Table 2.2: Basic Methods-IEM

    3 Specification of the Allocation

    MethodCorresponding
    Component
    in IEM
    Explanation
    FNET
    Function Net Modeling
    Dependency Diagrams /Martin, 1990a/ chap. 14 The dependencies of functions are represented in IEM by means of "Process Dependency Diagrams". Apart from the dependencies of functions it is also possible to model how often a dependent function is to be executed and if the courses of functions are to exclude each other. It is also possible to model events that initialize certain functions. The functions of Process Dependency Diagrams can be linked with the data from the corresponding E/R model. The modeling of processes can be checked for completeness via Data Conversation Analysis, Data Model Completeness Analysis, Process Model Completeness Check.
    LOGM
    Logical DB Modeling
    DB Modeling in IEM is represented within the scope of the detailed database design (/Martin, 1990b/ chap. 15, pp. 325-341). In the IEM description, logical data modeling is handled together with the physical database design (chap. 15: "Physical Database Design" in /Martin, 1990b/). It lists the influence factors for the design of a DBMS-oriented data structure together with those required for a physical database design. A clear line between logical database modeling and physical database design is only drawn in the IEM modifications (e. g. by Ernst & Young within the scope of the product IEW/ADW). IEM does not include any rule systems used to transform E/R models into actual commercially available database systems. Such rule systems are only included in the modifications or upgrades of the method by software producers.
    STRD
    Structured Design
    In IEM, Structured Design is handled within the scope of modeling with action diagrams where Structure Charts are only taken into consideration thus far as they can be represented as special cases of Action Diagrams (/Martin, 1990b/ Appendix II). Modifications or upgrades of IEM with regard to STRD (e. g. by Ernst & Young) use classical Structure Charts according to /Yourdon-Constantine, 1979/ or else expand the Action Diagrams accordingly (e. g. James Martin Corporation with "Procedure Logic Design").

    4 Literature

    /Martin, 1987/ Diagramming Standards for Analysts & Programmers
    /Martin, 1989/ Information Engineering, Book I
    /Martin, 1990a/ Information Engineering, Book II
    /Martin, 1990b/ Information Engineering, Book III

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