1. T3: Enterprise Systems Modeling Fall 2013 Chin-Sheng Chen Florida International University

2. T3: Enterprise Systems Modeling Systems modeling tools Systems modeling tools –OMT –IDEF

3. References Object-oriented Modeling and Design, by James Rumbaugh, et al., Prentice Hall, 1995, ISBN-0-13-629841-9 Object-oriented Modeling and Design, by James Rumbaugh, et al., Prentice Hall, 1995, ISBN-0-13-629841-9 IDEF by KBSI, 2010 IDEF by KBSI, 2010

4. The ESE Framework – Re-visit Enterprise element WorkDecisionResourceInformation System facet Strategy Competency (capability) CapacityStructure Engineering activity SpecificationAnalysisDesignimplementation Performanc e measure QualityTimeCost Benefit (profit)

5. Traditional modeling tools Physical simulators Physical simulators –Use of physical (or in combination with virtual) devices Math modeling tools Math modeling tools –Math programming (system specifications) –Queuing networks (system performance) (Computer graphic) charting tools (Computer graphic) charting tools –ABC flow-charter –Visio

6. Computer-based simulation modeling tools Computer languages Computer languages –Java, VB, C# Macro programs Macro programs –GASP, GPSS –Simen, ARINA, SLAM –AutoMod, Quest Network Network –Petri Net, –Neural networks

7. Information systems modeling tools OMT OMT –Functional model –Object model –Dynamic model IDEF IDEF –IDEF0 (activities) –IDEF1x (information) –IDEF2x (dynamics)

8. IDEF Concept (1) IDEF (ICAM Definition) IDEF (ICAM Definition) –Developed by the US Air Force Integrated Computer Aided Manufacturing (ICAM) Programs in 1981 ICAM Objective ICAM Objective –To develop structured methods for applying computer technology to manufacturing and to better understand how best to improve manufacturing productivity

9. IDEF Concept (2) IDEF0 IDEF0 –An activity model of a manufacturing system and environment IDEF1 IDEF1 –An informational model of the system and environment IDEF2 IDEF2 –A dynamic model to describe time-varying system behavior

10. IDEF Concept (3) IDEF Methodology IDEF Methodology –Modeling process and tools, leading to creation of the three IDEF models IDEF0 (activities) IDEF0 (activities) IDEF1x (information) IDEF1x (information) IDEF2x (dynamics) IDEF2x (dynamics) Commercial IDEF software tools Commercial IDEF software tools –Design/IDEF by Meta Software Company –AI0WIN by Knowledge Based Systems Inc.

11. OMT Concepts (1) There are 4 system development stages: analysis, system design, implementation design, and implementation. There are 4 system development stages: analysis, system design, implementation design, and implementation. OMT is to capture the concepts of a system, rather than its implementation OMT is to capture the concepts of a system, rather than its implementation The three models are orthogonal parts of the description of a complete system and are cross- linked. The object model is most fundamental, because it describes what changes (or transforms) before when (dynamic model) or how (functional model) it changes. The three models are orthogonal parts of the description of a complete system and are cross- linked. The object model is most fundamental, because it describes what changes (or transforms) before when (dynamic model) or how (functional model) it changes.

12. OMT concepts (2) - common themes Abstraction, Abstraction, Encapsulation, Encapsulation, Combining data and behavior, Combining data and behavior, Sharing with emphasis on object structure (not procedure structure), and Sharing with emphasis on object structure (not procedure structure), and Synergy (consistence in terms of ID, classification, polymorphism, and inheritance) Synergy (consistence in terms of ID, classification, polymorphism, and inheritance)

13. OMT concepts (3) - Functional model It describes the data value transformations within a system. It describes the data value transformations within a system. The functional model contains data flow diagrams. The functional model contains data flow diagrams. –A data flow diagram is a graph whose nodes are processes and whose arcs are data flows.

14. OMT concepts (4) - object model It describes the static structure of the objects in a system and their relationships. It describes the static structure of the objects in a system and their relationships. The object model contains object diagrams. The object model contains object diagrams. –An object diagram is a graph whose nodes are object classes and whose arcs are relationships among classes.

15. OMT concepts (5) - Dynamic model It describes the aspects of a system that change over time and is used to specify and implement the control aspects of a system. It describes the aspects of a system that change over time and is used to specify and implement the control aspects of a system. The dynamic model contains state diagrams. The dynamic model contains state diagrams. –A state diagram is a graph whose nodes are states and whose arcs are transitions between states caused by events.

23. Relationship Between the Two Modeling Tools IDEF0/functional model IDEF0/functional model –The input to an activity is usually a user interface for data entry –The output to an activity is usually a user interface for a report, though the output may be a write/update to a database. –ICOM Material is an input object. Material is an input object. Product/process data are output objects. Product/process data are output objects. Rules/regulations and SOPs are constraints. Rules/regulations and SOPs are constraints. Resources/tools and methods are mechanisms. Resources/tools and methods are mechanisms. IDEF1/object model IDEF1/object model –The collection of the ICOM of an IDEF activity model constitutes an inclusive foundation for the object model. IDEF2/dynamics model IDEF2/dynamics model –Each object requires a state diagram to define/govern its life-cycle behavior. –A triggering event is associated with each transition from one state to another. One state may transform to multiple states, depending on the triggering event.