230 likes | 440 Views
T3: Enterprise Systems Modeling. Fall 2013 Chin- Sheng Chen Florida International University. T3: Enterprise Systems Modeling. Systems modeling tools OMT IDEF. References. Object-oriented Modeling and Design , by James Rumbaugh , et al., Prentice Hall, 1995, ISBN-0-13-629841-9
E N D
T3: Enterprise Systems Modeling Fall 2013 Chin-Sheng Chen Florida International University
T3: Enterprise Systems Modeling • Systems modeling tools • OMT • IDEF
References • Object-oriented Modeling and Design, by James Rumbaugh, et al., Prentice Hall, 1995, ISBN-0-13-629841-9 • IDEF by KBSI, 2010
Traditional modeling tools • Physical simulators • Use of physical (or in combination with virtual) devices • Math modeling tools • Math programming (system specifications) • Queuing networks (system performance) • (Computer graphic) charting tools • ABC flow-charter • Visio
Computer-based simulation modeling tools • Computer languages • Java, VB, C# • Macro programs • GASP, GPSS • Simen, ARINA, SLAM • AutoMod, Quest • Network • Petri Net, • Neural networks
Information systems modeling tools • OMT • Functional model • Object model • Dynamic model • IDEF • IDEF0 (activities) • IDEF1x (information) • IDEF2x (dynamics)
IDEF Concept (1) • IDEF (ICAM Definition) • Developed by the US Air Force Integrated Computer Aided Manufacturing (ICAM) Programs in 1981 • ICAM Objective • To develop structured methods for applying computer technology to manufacturing and to better understand how best to improve manufacturing productivity
IDEF Concept (2) • IDEF0 • An activity model of a manufacturing system and environment • IDEF1 • An informational model of the system and environment • IDEF2 • A dynamic model to describe time-varying system behavior
IDEF Concept (3) • IDEF Methodology • Modeling process and tools, leading to creation of the three IDEF models • IDEF0 (activities) • IDEF1x (information) • IDEF2x (dynamics) • Commercial IDEF software tools • Design/IDEF by Meta Software Company • AI0WIN by Knowledge Based Systems Inc.
OMT Concepts (1) • 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 • 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.
OMT concepts (2) - common themes • Abstraction, • Encapsulation, • Combining data and behavior, • Sharing with emphasis on object structure (not procedure structure), and • Synergy (consistence in terms of ID, classification, polymorphism, and inheritance)
OMT concepts (3) - Functional model • It describes the data value transformations within a system. • The functional model contains data flow diagrams. • A data flow diagram is a graph whose nodes are processes and whose arcs are data flows.
OMT concepts (4) - object model • It describes the static structure of the objects in a system and their relationships. • The object model contains object diagrams. • An object diagram is a graph whose nodes are object classes and whose arcs are relationships among classes.
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. • 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.
Relationship Between the Two Modeling Tools • 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. • Product/process data are output objects. • Rules/regulations and SOPs are constraints. • Resources/tools and methods are mechanisms. • IDEF1/object model • The collection of the ICOM of an IDEF activity model constitutes an inclusive foundation for the object 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.