ALGUMAS FERRAMENTAS PARA IDEF0 - UNINOVA · Web viewUML Unified Modeling Language Booch, Rumbaugh,...

ENTERPRISE MODELING

Enterprise modeling => a pre-requisite for Enterprise Integration

Enterprise modeling must provide a set of common languages to describe various aspects of the enterprise at different abstraction levels (e.g. business level, engineering level or operational level) and from different angles (e.g. function view, information view, organization or economic views).

Essential features of an enterprise to be modeled include:

- Enterprise functionality and behavior in terms of business processes, activities, functional operations and triggering events;

- Decision-making processes, decision flows and decision centers;- Products, their logistics and their life cycle;- Physical components or resources, e.g. machines, tools, storage devices, or

transportation means, their logistics, capabilities, capacities and layout;- Applications (i.e. software packages) in terms of their basic functional

capabilities;- Operational data and information and their flows in the form of orders,

documents, data items, data files or complex databases;- Enterprise knowledge and know-how, i.e. domain specific knowledge, rules

of thumb, decision-making rules, internal management policies, international regulations, etc.;

- Human individuals, especially their qualification, skills, roles and availability;- Organizational structure, i.e. organization units, decision levels, decision

centers and their relationships; - Responsibility and authority distribution over each of the previous elements;- Exceptional events and exception handling policies; - Temporal aspects because an enterprise is a dynamic system.

Vernadat, 1997

L.M. Camarinha-Matos

Modern enterprise systems must be engineered, implemented and integrated in a systematic way very similar to approaches developed

for software engineering.This emerging discipline is termed Enterprise Engineering.

ALGUMAS FERRAMENTAS DE MODELAÇÃO

Modelação funcional – IDEF 0

Modelação de informação – EXPRESS, NIAM, UML <ver disciplina de Modelação de Dados em Engenharia>

Modelação de processos- Redes de Petri <ver disciplina de Sistemas de Tempo Real>

- Modelção de Processos de Negócio – várias ferramentas- Standards – PIF, PSL


FUNCTIONAL MODEL

IDEF0 /SADTSADT – Structured Analysis and Design Technique [SofTech, >70’s]ICAM –Integrated Computer Aided Manufacturing [US Air Force, >80’s]IDEF – ICAM DEFinition methodology

Basic Principle: Top-Down Decomposition

Everything that can be said about something shall be expressed in 6 or less “parts”

Graphical Language:

=>ICOM


ACTIVITY

IDEF0 – Hierarchy of diagrams


IDEF3

IDEF3 - Process Description Capture Method - captures precedence and causality relations between situations and events.

IDEF3 captures the behavioral aspects of an existing or proposed system.

Two IDEF3 description modes:

- Process flow - captures knowledge of "how things work" in an organization, e.g., the description of what happens to a part as it flows through a sequence of manufacturing processes.

Example IDEF3 Process Description Diagram

- Object state transition network - summarizes the allowable transitions an object may undergo throughout a particular process.


Example IDEF3 Object State Transition Network Diagram


ALGUMAS FERRAMENTAS PARA IDEF0

Ventana => www2.ventana.com

Activity Modeler

IDEF Primer => www2.ventana.com/html/idef0_prime.html

IDEFine => www.idefine.com

Design/IDEF0

Knowledge Based Systems Inc. => www.kbsi.com

IDEF based tools: AI0 WIN, SmartER

IDEF Methods => www.idef.com [overview] www.idef.com/toc.htm [completo]

Bibliografia sobre IDEF: www.uta.edu/ie/idef.htm


http://www.idef.com/toc.htm

http://www.idef.com/

http://www.kbsi.com/

http://www.idefine.com/

IDEFØ rules include the following:

Control of the details communicated at each level (three to six function boxes at each level of a decomposition).

Bounded Context (no omissions or additional out-of-scope detail).

Diagram Interface Connectivity (Node numbers, Box numbers, C-numbers, and Detail Reference Expression).

Data Structure Connectivity (ICOM codes and the use of parentheses).

Unique Labels and Titles (no duplicated names).

Syntax Rules for Graphics (boxes and arrows).

Data Arrow Branch Constraint (labels for constraining the data flow on branches).

Input versus Control Separation (a rule for determining the role of data).

Data Arrow Label Requirements (minimum labeling rules).

Minimum Control of Function (all functions require at least one control).

Purpose and Viewpoint (all models have a purpose and viewpoint statement).


IDEF METHODSwww.idef.com

IDEF0Function Modeling Method

IDEF1Information Modeling Method [Requirements specification]

IDEF1 X [extended]Data Modeling Method [RDB design / entity relationship]

IDEF2Simulation Model Design Method

IDEF3Process Flow and Object State Description Capture Method

IDEF4Object Oriented Design Method

IDEF5Ontology Description Capture


http://www.idef.com/

UMLUnified Modeling Language

Booch, Rumbaugh, Jacobson

1994 – Grady Booch and Jim Rumbaugh began unifying their modeling techniques at Rational Software

1996 – Consortium of 12 companies formed to oversee UML[IBM, Oracle, Digital, HP, Unisys, …]

Jan 1997 – Version 1.0 published Sept 1997 – Revised version 1.1

Classes Notes / CommentsClass_name

attributes

operations /methods

This is a note

Syntax:- Class name centered and in bold- Class name begins with uppercase- Attributes and operations begin with lowercase- Abstract classes in italic

Visibility:+ public- private# protected

{frozen} attributes whose values cannot be changed


Hierarchy / Inheritance

ObjectAn instance of a class

Parametrized Classes [Template classes]

ArrayOfObjectsT, n : int

n .. nT

ButtonList

bind (Button, 4)

Instance oftemplate class


InterfacesExternally-visible operations of a class or component without specification of their internal structures.

PackagesGroupings of model elements, usually classes.

Package


Associations

Binary association

OR association

Multiplicity

Multiplicity defines how many objects participate in a relationships– Multiplicity is the number of instances of one class related to ONE

instance of the other class– For each association and aggregation, there are two multiplicity

decisions to make: one for each end of the relationship Although associations and aggregations are bi-directional by default, it is often

desirable to restrict navigation to one direction If navigation is restricted, an arrowhead is added to indicate the direction of the

navigation


RegistrationForm

RegistrationManager

Course

Student

CourseOfferingProfessor

addStudent(Course, StudentInfo)

namenumberCredits

open()addStudent(StudentInfo)

major

location

open()addStudent(StudentInfo)

tenureStatus

ScheduleAlgorithm

10..*

0..*1

1

1..*4

3..10

0..41


Derive elements

Interaction Diagrams


State Transition Diagram


A state transition diagram shows – The life history of a given class– The events that cause a transition from one state to another– The actions that result from a state change

– State transition diagrams are created for objects with significant dynamic behavior.

Free tool: http://www.ics.uci.edu/pub/arch/uml/

Documentation: http://www.rational.com/uml/resources/documentation/formats.jtmpl


http://www.rational.com/uml/resources/documentation/formats.jtmpl

http://www.ics.uci.edu/pub/arch/uml/

BPR & WORKFLOW TOOLSEXAMPLES

IDS Scheer => www.ids_scheer.com www.meridian-marketing.com/ARIS/index.html

ARIS – Architecture of Integrated Information Systems.Modeler, Analyzer, Navigator.Organizational View, Data View, Function View, Control View

MetaSoftware => www.metasoftware.com

Workflow Analyzer.Integrates BPR & Workflows.Analysis

Workflow Modeler + Workflow Simulator.IDEF based.Activity based costing.Bottlenecks, cycle time (queue time, move time, actual processing time), cost data, resource utilization

Modus Operandi => www.intecsys.com

IsModeler.Process modeling.Cost, information usage, performance (cycle times, errors), bottlenecks, process policies.Flow model building blocks: Customers, activities, information stores, work items, flags, connectors

Grade Development Group => www.latnet.lv/MII/Grade www.corpdyn.co.uk/Global.html

Grade Modeler.BPR model.All phases of system development before programming.Object modeling, organization structure modeling, business process modeling, data modeling, structure and communication modeling, object behavior modeling, simulation & evaluation of BP


http://www.corpdyn.co.uk/Global.html

http://www.latnet.lv/MII/Grade

http://www.intecsys.com/

http://www.metasoftware.com/

http://www.meridian-marketing.com/ARIS/index.html

http://www.ids_scheer.com/

CACI => www.caciasl.com/simprocess-product.html

SIMPROCESS.Process modeling, simulation and analysis

Interfacing Technologies => www.interfacing.com

FirstSTEP.Designer, Viewer, …

Silverrun => www.silverrun.com

SILVERRUN.BP modeling, resource and cost, multi-level modeling, times, …

PIF – Process Interchange Format

http://ccs.mit.edu/pif2.html


http://ccs.mit.edu/pif2.html

http://www.silverrun.com/

http://www.interfacing.com/

http://www.caciasl.com/simprocess-product.html

PIF – PROCESS INTERCHANGE FORMAT

http://ccs.mit.edu/pifmain.html


http://ccs.mit.edu/pifmain.html

Example:

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;; Project and Team definitions;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

(define-frame EXAMPLE-PROJECT :own-slots ((Instance-Of ACTIVITY) (Documentation "A project is the top-level activity of this activity elaboration hierarchy. The Components attribute lists the sub-activities of the project.") (Name |The Example Project Process|) (Component ARCHITECTURE-DESIGN-1 ELECTRICAL-DESIGN-2 MECHANICAL-DESIGN-3 DESIGN-REVIEW-4) ))

(define-frame DESIGN-TEAM-1 :own-slots ((Instance-Of GROUP) (Documentation "A project team is a Group. It has member actors, and can itself be viewed as an Actor.") (Name |Project Design Team|) (Member ARCHITECT-1 ELECTRICAL-ENGINEER-2 MECHANICAL-ENGINEER-3 PROJECT-MANAGER-4) ))

(define-frame TEAM-PERFORMS-PROJECT-1 :own-slots ((Instance-Of PERFORMS) (Actor DESIGN-TEAM-1) (Activity EXAMPLE-PROJECT) ))


PSL – PROCESS SPECIFICATION LANGUAGE

www.mel.nist.gov/psl/

Primary component of PSL - ontology designed to represent the primitive concepts that, according to PSL, are adequate for describing basic manufacturing, engineering, and business processes. .

Ontology - set of specialized terminology along with some specification of the meaning of terms in the lexicon.

PSL ontology - a rigorous mathematical characterization of process information as well as precise expression of the basic logical properties of

that information in the PSL language.

PSL Core:

Classes: OBJECT, ACTIVITY, ACTIVITY_OCCURRENCE and TIMEPOINT. Relations: PARTICIPATES-IN, BEFORE, and OCCURRENCE-OF. Functions: BEGINOF, and ENDOF.

Generic activities …and ordering relations


http://www.mel.nist.gov/psl/

Example:

(doc make-gt350 "Make GT350")

(and (doc make-interior "Make Interior") (forall (?a : (activation-of ?a make-interior)) (exists (?o1 : (instance-of ?o1 a002-bench)) (in ?o1 ?a))) (and (duration make-interior 5) (beginof make-interior 7)))

…(and (doc make-gt350-proc "Make GT350 Process") (subactivity make-interior-1 make-gt350-proc) (subactivity make-drive-1 make-gt350-proc) (subactivity make-trim-1 make-gt350-proc) (subactivity make-chassis-1 make-gt350-proc) (subactivity final-assembly-1 make-gt350-proc) (subactivity j2 make-gt350-proc) (subactivity j1 make-gt350-proc) (subactivity make-harness-1 make-gt350-proc) (subactivity make-wires-1 make-gt350-proc) (subactivity assemble-engine-1 make-gt350-proc) (subactivity j4 make-gt350-proc) (subactivity j3 make-gt350-proc) (subactivity machine-block-1 make-gt350-proc) (subactivity change-mould-1 make-gt350-proc) (subactivity setup-furnace-1 make-gt350-proc) (subactivity analyse-metal-1 make-gt350-proc) (subactivity melt-1 make-gt350-proc) (subactivity wait-1 make-gt350-proc) (subactivity clear-cavities-1 make-gt350-proc) (subactivity j8 make-gt350-proc) (subactivity j7 make-gt350-proc) (subactivity j6 make-gt350-proc) (subactivity j5 make-gt350-proc) (subactivity setup-racks-1 make-gt350-proc) (subactivity pour-1 make-gt350-proc) (subactivity remove-racks-1 make-gt350-proc) (subactivity batch-complete-1 make-gt350-proc) (idef-process make-gt350-proc))


ALGUMAS FERRAMENTAS PARA IDEF0 - UNINOVA · Web viewUML Unified Modeling Language Booch, Rumbaugh,...

Documents

Transcript of ALGUMAS FERRAMENTAS PARA IDEF0 - UNINOVA · Web viewUML Unified Modeling Language Booch, Rumbaugh,...