|2.2 The complex Method IEM|
IEM - Information Engineering Method
The methodical components of IEM are:
Action Diagrams allow the representation of a functional or respectively module structure with successive hierarchical refinement up to the level of the program logic.
Decomposition Diagrams can be used for the hierarchical decomposition of business functions, processes, procedures, and program modules.
Dependency Diagrams are used to represent the dependencies of functions, processes, and procedures.
Data Flow Diagrams are used for the data flow modeling.
Data Analysis and Data Structure Diagrams are used for the bottom-up generation of data structures.
By utilizing the Entity-Relationship Diagrams it is possible to generate E/R models with binary relation types between entity types.
Data Navigation Diagrams can be used to represent the order and mode of the data accesses to the entity types of an E/R model.
Decision Trees and Decision Tables correspond to the requirements of the decision table technique (DTAB) of the Methods Standard.
With the help of the State Transition Diagrams it is possible to model the states of processes, in particular the states of real-time processes.
Dialog Design Diagrams are used for the design and representation of user dialogs.
Entity LifeCycles can be used to represent the life cycle of entity types via State Transition Diagrams.
Physical Database Design is used for the generation of physical data structures with logical DB modeling as interim step.
Normalization is used for the normalization of entity types. IEM was designed by J. Martin, adopted by various consulting companies, and slightly modified (Ernst & Young, J. Martin Corporation, Texas Instruments etc.). The present comparison refers to the IEM representation by J. Martin the way it is described in the following J. Martin books about Information Engineering: /Martin, 1987/, /Martin, 1989/, /Martin, 1990a/ and /Martin, 1990b/.
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||
/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||
/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|
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.|
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.|
|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").|
/Martin, 1987/ Diagramming Standards for Analysts & Programmers
|GDPA Online Last Updated 01.Jan.2002 Updated by Webmaster Last Revised 01.Jan.2002 Revised by Webmaster|