Unit 5 Flashcards

1
Q

Business Process

A

Consists of a set of tasks or activities, known as process steps
Has a trigger
A trigger is something initiates a process
Has temporal relationship or sequence between tasks
Has a start and an end
Has participants that perform the process steps

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Review Process Triggers Graphic

A

DO IT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Types of Triggers

A

External Event
an event that occurs outside the system, usually initiated by an external agent or actor

Temporal Event
an event that occurs as a result of reaching a point in time

State/Internal Event
an event that occurs when something happens inside the system that triggers some process
reorder point is reached for inventory item

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Documenting Business Processes

A

Can be described using textual narratives –not very useful because they do not typically follow a standard structure
Business Process Modeling Notation (BPMN
)Focus is on individual processes and process steps
Business level –not designed from IT systems’ perspective

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Documenting Business Processes (Continued)

A

Unified Modeling Language (UML) notations
Use Case Diagram
Use Case Descriptions
Activity Diagram
Context Diagram –not part of UML but very useful
**(Bullet)Designed from IT Systems’ perspective, though they can be used to model non-IT based processes also

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Process Modeling using BPMN

A

Business Process Modeling Notation
graphical notation that depicts the steps in a business process
depicts the end to end flow of a business process
Shows the sequence and coordination of steps Shows messages that flow between different process participants

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Key Aspects of BPMN

A
Key Aspects
Event
•Start, End and Intermediate Event
Activity/Task
Gateway
•Forks and Joins
•Parallel branches
•Exclusive or Inclusive branches
Sequence
•Normal
•Exception
Pool
•Participants
Message
Trigger
•Message trigger
•Time trigger
Looping
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

BPMN Symbols

A

Refer to the BPMN notes for symbols

Symbols for the key BPMS aspects mentioned in the previous slide are sufficient for most situations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Review A Process Diagram Using BPMN Graphic

A

Do it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Review A Choreography Diagram Using BPMN Graphic

A

Do it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Review Choreography along with Pools Graphic

A

Do it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Context Diagram

A

Context diagram represents the interaction of outside entities with a system as a whole.
Context diagram is composed of three elements
A system or subsystem.
Entities outside the system that interact with it.
Interactions between outside entities and the system.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Review Context Diagram Graphic

A

Do it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Context Diagram

A

A context diagram defines the boundary of the system being modeled

The processes done by the actors that are outside the boundary are not of interest to us –we are not interested in examining those outside processes but only those that are inside the system

The interactions between the external actors and the system are important because these interactions often provide the necessary data to carry out the internal processes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Review One Supermartket, Two Systems Graphic

A

Do it

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Use Case Modeling

A

Top-down Modeling
Context diagram is exploded to use case diagram
A process in a use case diagram can be exploded further into another use case diagram
A use case diagram shows the internals of a system/process using use cases

17
Q

Use Case

A

Use cases model the behavior of a system
A use case is a contract that formalizes the interaction between actors and the system
A use case details the interaction of an actor with a system to accomplish a goal of value to the actor

18
Q

What Use Case Modeling Is Not

A

Use Case modeling is limited to a system’s external behavior
Use cases generally focus on the system from outside.
Use cases are not effective in capturing the non-functional requirements.
Use cases are not inherently object-oriented.

19
Q

Use Case Diagrams

A

Use case diagram—a UML model used to graphically show uses cases and their relationships to actors
Recall UML is Unified Modeling Language, the standard for diagrams and terminology for developing information systems
Actor is the UML name for a end user

20
Q

Review Use Case Diagrams Symbols Graphic

A

Do it

21
Q

Review Use Case Diagrams Draw for a single actor, such as customer Graphic

A

Do it

22
Q

Review Use Case Diagrams Graphic

A

Do it

23
Q

Use Case Diagrams—The <> relationship

A

A relationship between use cases where one use case is stereotypically included within the other use case—like a called subroutine. Arrow points to subroutine

24
Q

Review Use Case Diagram to show Extends Relationship Graphic

A

Do it

25
Q

Difference between Include and Extend Relationships

A

Include is an example of a mandatory relationshipIf Use Case A includes Use Case B (A B), then whenever use case (process) A is done, use case B (process) B is always done

Extend is an example of a optional relationshipIf Use Case A extends Use Case B (AB), then when Use Case B is done sometimes ( not always) Use case A is also done

Note the difference in the usage of A and B in the above definitions.

26
Q

Elements of a Use Case Description

A

Basic information
Name, number and brief description
Trigger –event that causes the use case to being
•External trigger –some from outside the system
•Temporal triggers –time-based occurrences

Normal Flow of Events
Steps performed and the data inputs and outputs
Exception Flows
It is a good idea to underline data referred to in the use case descriptions

27
Q

Review Use Case Graphic (Slide 27)

A

Do it

28
Q

Activity Diagram

A

Activity diagram depicts the flow from activity to activity. It presents a visual, dynamic view of the system and its components.
It is similar to the process diagram in BPMN

29
Q

Review Activity Diagram Graphic

A

Do it