Transcript
1/19
9강. IDEF (1)
2/19
학습 목표
• 비즈니스 모델링 도구 소개
• IDEF의 의미
• IDEF0 작성법 파악
3/16
비즈니스 모델링 도구
1) Phenomenon + combination of process (activity), function, event, state
2) Overview of process modeling techniques + function-based * Flow Charts * Data Flow Diagram (DFD, IDEF0) + state-based * Finite State Automata (FSA) * Markov Chains * state transition diagram (UML state diagram) + event-based * event graph + state/event-based * Petri net * PERT/CPM
4/16
1) State * snapshot of the process/system * 특정 시점에서의 시스템의 특성을 표현하는 변수들의 집합 * ex) 은행 - # of busy tellers - # of customers in the bank 2) event * state changes are caused by events. * ex) 은행 - customer leaves - customer enters
State & Event(1)
5/19
IDEF 소개(1)
• 정의
- IDEF: Family of Integrated DEFinition methods
(ICAM Definition)
- ICAM: US Air Force Program for Integrated
Computer Aided Manufacturing.
6/19
• IDEF 방법
(1) IDEF0: function modeling * a method designed to model the decisions, actions, and activities of an organization or system. * mainly concerned with what activities the organization performs. * hierarchical structure * a non-temporal fashion * simple (2) IDEF1: information modeling * information analysis method, not database design method (IDEF1x) * a method for organizations to analyze and clearly state their information resource management needs and requirements. (3) IDEF3 * how a particular system or organization works * process description capture method * two modes - process flow description: “how things work” - object state transition network: “allowable transition an object may undergo”
IDEF 소개(2)
7/19
• IDEF 요약
IDEF0 (Functional modeling)
IDEF1(Data Modeling)
IDEF3 (Process Modeling)
(what)
(how & when)
(what data)
IDEF 소개(3)
8/19
IDEF0 작성법(1)
• IDEF0
- used to produce a “functional model”
- functional model is a structured
representation of the functions, activities
or processes within the subject area.
- a kind of data flow diagrams (DFD, SADT..)
9/19
Perform Inspection
1
: : function name=verb(phrase), box number is shown.
: : convey data or objects related to functions to be performed.
Function object
ICOM (Input,Control,Output,Mechanism) object
Function name
1
Input Output
Mechanism
Control
• 구성 요소
① Input - arrows entering the left side of box. - Inputs are transformed or consumed by the function to produce outputs. ② Output - arrows leaving a box on the right side - outputs are the data or objects produced by the function. ③ Control - arrows entering the box on the top - controls specify the conditions required for the function to produce correct outputs. ④ Mechanism - arrows connected to the bottom side of the box - mechanisms identify some of the means(resource) that support the execution of the function.
IDEF 0 작성법(2)
10/19
Perform Detailed design
1
Preliminary Design data
Recommended Detailed design
Design engineer
Design requirements
A-0 Detailed Design
IDEF 0 작성법(3)
11/19
• Box와 화살표의 사용
IDEF 0 작성법(4)
12/19
• Box와 화살표의 사용
IDEF 0 작성법(5)
13/19
• 경계 화살표와 내부 화살표
IDEF 0 작성법(6)
14/19
• 경계 화살표와 내부 화살표
* If a box on a diagram is detailed by a child diagram,
each arrow connected to
the parent box shall appear
on the child diagram.
* All boundary arrows on
a child diagram shall
correspond to the arrows
that connect to its parent
box.
IDEF 0 작성법(7)
15/19
• 기능 분할
- No more than six sub-functions on each successive function
IDEF 0 작성법(8)
16/19
• Top-Level Context Diagram (A-0 Diagram)
IDEF 0 작성법 (9)
17/19
• A0 다이어그램 (Level1)
IDEF 0 모델 예(1)
18/19
• A2 다이어그램 (Level 2)
IDEF 0 모델 예(2)
19/19
IDEF 0 모델 예(3)
• A21 다이어그램 (Level 3)
1/17
학습 목표
• IDEF1의 의미와 작성법 파악
• IDEF3의 의미와 작성법 파악
2/17
• IDEF1 구성 요소 - 실체
- 속성
- 관계
IDEF1 개요
3/17
• IDEF1 모델 예 (1)
department
Employee
(_DEPT#)
employs/ works for
(_EMP#) (_SSN) Salary DEPT#
Entity class box
Relation class
Relation class label
Entity class label
Non-key attribute classes
Key attributes classes denoted by underlining
cardinality
IDEF1 예(1)
4/17
• IDEF1 모델 예 (2)
IDEF1 예(2)
(_ )
5/17
• 개요
- Captures precedence and causality relations between situations and events.
- IDEF3 may contain zero or more Process Schematics and zero or more Object Schematics
IDEF 3 개요(1)
6/17
• Process Schematics - process-centered view - a focus on processes and their temporal, causal, and logical relations within a scenario. - scenario: can be thought of as a recurring situation, a set of situations that describe a typical class of problems addressed by an organization or system. - decomposition
IDEF 3 개요(2)
7/17
• Object Schematics - object-centered view - focus on objects and their state change behavior in a single scenario or across multiple scenarios. - object: any physical or conceptual thing that is recognized and referred to by participant in the domain.
IDEF 3 개요(3)
8/17
• Process Schematic symbols
UOB Label
Node Ref# IDEF Ref#
- UOB (Unit of Behavior) – type of happening (단위 활동)
- simple precedence link (선후행 연결 관계)
- Junctions (합류점) &
X
O
- (asynchronous) AND - (synchronous) AND - (asynchronous) OR - (synchronous) OR
- XOR
IDEF 3 (1)
&
O
9/17
• Object Schematic symbols
- Object (객체) symbol Object:state label
- Links (연결 관계)
- Junctions (합류점) &
O
X
- AND
- OR
- XOR
IDEF 3 (2)
10/17
• 참조 대상 정보 - 참조 대상유형 (Referent type): UOB, Scenario, object schematic
- 이름 (Label):
- 식별자 (Locator): number
Referent type/ Label
locator
call and continue referent
Referent type/ Label
locator
call and wait referent
IDEF 3 (3)
11/17
• 합류점 (junction) 유형
(parallel :AND) (alternative)
(split) (join)
(OR) (XOR)
IDEF 3 (4)
12/17
• Asynchronous & synchronous AND
IDEF 3 (5)
13/17
• Asynchronous OR - J1 indicates that, following an instance of A, one or more of the UOBs B, C,
and D will be realized. This will initiate one to three “threads” in the activation. Because J2 is an asynchronous OR junction, only one of the threads needs to complete before an instance of F initiates.
A B C D E F
IDEF 3 (6)
14/17
• Synchronous OR
- Because the junction is synchronous, when more than one UOB is instantiated, the instances occur simultaneously.
(B is instantiated) (B is not instantiated)
IDEF 3 (7)
top related