T 3 Enterprise Systems Modeling Fall 2013 ChinSheng

  • Slides: 23
Download presentation
T 3: Enterprise Systems Modeling Fall 2013 Chin-Sheng Chen Florida International University

T 3: Enterprise Systems Modeling Fall 2013 Chin-Sheng Chen Florida International University

T 3: Enterprise Systems Modeling n Systems modeling tools – OMT – IDEF

T 3: Enterprise Systems Modeling n Systems modeling tools – OMT – IDEF

References Object-oriented Modeling and Design, by James Rumbaugh, et al. , Prentice Hall, 1995,

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

The ESE Framework – Re-visit Enterprise element Work Decision Resource Information System facet Strategy

The ESE Framework – Re-visit Enterprise element Work Decision Resource Information System facet Strategy Competency (capability) Capacity Structure Engineering Specification activity Analysis Design implementation Performanc Quality e measure Time Cost Benefit (profit)

Traditional modeling tools n Physical simulators – Use of physical (or in combination with

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

Computer-based simulation modeling tools n Computer languages – Java, VB, C# n Macro programs

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

Information systems modeling tools n OMT – Functional model – Object model – Dynamic

Information systems modeling tools n OMT – Functional model – Object model – Dynamic model n IDEF – IDEF 0 (activities) – IDEF 1 x (information) – IDEF 2 x (dynamics)

IDEF Concept (1) n IDEF (ICAM Definition) – Developed by the US Air Force

IDEF Concept (1) n IDEF (ICAM Definition) – Developed by the US Air Force Integrated Computer Aided Manufacturing (ICAM) Programs in 1981 n 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) n IDEF 0 – An activity model of a manufacturing system

IDEF Concept (2) n IDEF 0 – An activity model of a manufacturing system and environment n IDEF 1 – An informational model of the system and environment n IDEF 2 – A dynamic model to describe time-varying system behavior

IDEF Concept (3) n IDEF Methodology – Modeling process and tools, leading to creation

IDEF Concept (3) n IDEF Methodology – Modeling process and tools, leading to creation of the three IDEF models n IDEF 0 (activities) n IDEF 1 x (information) n IDEF 2 x (dynamics) n Commercial IDEF software tools – Design/IDEF by Meta Software Company – AI 0 WIN by Knowledge Based Systems Inc.

OMT Concepts (1) n n n There are 4 system development stages: analysis, system

OMT Concepts (1) n n n 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 crosslinked. 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 n n n Abstraction, Encapsulation, Combining data and

OMT concepts (2) - common themes n n n 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

OMT concepts (3) - Functional model It describes the data value transformations within a system. n The functional model contains data flow diagrams. n – 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

OMT concepts (4) - object model It describes the static structure of the objects in a system and their relationships. n The object model contains object diagrams. n – 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

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. n The dynamic model contains state diagrams. n – 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 n IDEF 0/functional model – The input to

Relationship Between the Two Modeling Tools n IDEF 0/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 n n n Material is an input object. Product/process data are output objects. Rules/regulations and SOPs are constraints. Resources/tools and methods are mechanisms. IDEF 1/object model – The collection of the ICOM of an IDEF activity model constitutes an inclusive foundation for the object model. n IDEF 2/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.