BUSINESS PROCESS AND

FUNCTIONAL MODELING
SESSION 9

SUBJECT MATTER EXPERT

D6580 – Muhammad Amien
Ibrhaim, S.Kom., M.Sc.
SUB TOPICS

• Introduction
• Business Process Identification using Use Case Diagram
• Business process Modeling using Activity Diagram
• Business Process Documentation: use case Description
• Verifying and validating and functional Model
• Applying the concepts
• Data Flow Diagram
ACKNOWLEDGEMENT

These slides have been adapted from:

Alan Dennis, Barbara Haley Wixom, David Tegarden

(2015). Systems Analysis and Design_ An Object-
Oriented Approach with UML, 5th ed.
ISBN: 978-1-118-80467-4

Chapter 4
LEARNING OUTCOMES

At the end of this lecture, students are able to:

LO3: To analyze the requirement of a system

INTRODUCTION

• All object-oriented systems development approaches are use-case driven,

architecture-centric, and iterative and incremental.

• A use case is a formal way of representing the way a business system

interacts with its environment.

• A use case is a high-level overview of the business processes in a business

information system.

• From an architecture-centric perspective, use-case modeling supports the

creation of an external or functional view of a business process in that it
shows how the users view the process rather than the internal mechanisms
by which the process and supporting systems operate
INTRODUCTION

• All object-oriented systems development approaches are developed

in an incremental and iterative manner.

• Activity diagrams are typically used to augment our understanding of

the business processes and our use-case model.

• An activity diagram can be used for any type of process-modeling

activity

• Activity diagrams and use cases are logical model.

• Models that describe the business domain’s activities without

suggesting how they are conducted.
INTRODUCTION

• First we describe business process identification using use cases and

use-case diagrams.

• Second, we describe business process modeling with activity diagrams.

• Third, we describe use-case descriptions, their elements, and a set of

guidelines for creating them.

• Fourth, we describe the process of verification and validation of the

business process and functional models.
BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

Elements of Use-Case Diagrams

BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

Elements of Use-Case Diagrams

BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

Example: Use Case Diagram for Appointment System

BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

• Association Use cases are connected to actors through association

relationships.

• The association typically represents two-way communication between the use

case and the actor. If the communication is only one way, then a solid
arrowhead can be used to designate the direction of the flow of information.

• It is possible to represent the multiplicity of the association.

BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

• Association Use cases are connected to actors through association

relationships.

• The association typically represents two-way communication between

the use case and the actor. If the communication is only one way, then
a solid arrowhead can be used to designate the direction of the flow of
information.

• It is possible to represent the multiplicity of the association.

BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

• Use Case with Specialized Actor

BUSINESS PROCESS IDENTIFICATION WITH USE CASES AND USE-CASE DIAGRAMS

Include and Extent Relationship

MINI CASE: USE CASE DIAGRAM

Campus Housing Example

• The campus housing service helps students find apartments.
Apartment owners complete information forms about the available
rental units (e.g., location, number of bedrooms, monthly rent), which
are then entered into a database. Students can search this database
via the Web to find apartments that meet their needs (e.g., a two-
bedroom apartment for $400 or less per month within a half mile of
campus) and contact the apartment owners directly to see the
apartment and possibly rent it. Apartment owners call the service to
delete their listing when they have rented their apartment(s).
MINI CASE: USE CASE DIAGRAM

Campus Housing Example

IDENTIFYING USE CASE
CREATING USE CASE DIAGRAM
ELEMENTS OF ACTIVITY DIAGRAM
ELEMENTS OF ACTIVITY DIAGRAM
ELEMENTS OF ACTIVITY DIAGRAM
GUIDELINE FOR CREATING ACTIVITY DIAGRAM

Because an activity diagram can be used to model any kind of process,

you should set the context or scope of the activity being modeled.

Once you have determined the scope, you should give the diagram an
appropriate title.
■ You must identify the activities, control flows, and object fl ows that
occur between
the activities.
■ You should identify any decisions that are part of the process being
modeled.
■ You should attempt to identify any prospects for parallelism in the
process.
■ You should draw the activity diagram.
CREATING ACTIVITY DIAGRAM
MINI CASE: ACTIVITY DIAGRAM

Campus Housing Example

• Based on the earlier description, there are two separate activities
(subprocesses): one to add a rental unit and one to delete a rental
unit. To add a rental unit, the apartment owner must provide the
campus housing service with the location of the apartment, the
number of bedrooms in the apartment, and the monthly rent of the
apartment. To delete an apartment, the apartment owners must tell
the campus housing service that the specific apartment has been
rented and is no longer available.
MINI CASE: ACTIVITY DIAGRAM

Campus Housing Example

BUSINESS PROCESS DOCUMENTATION WITH USE CASES AND USE-CASE DESCRIPTIONS

Types of Use Cases

• Overview Use Case
– Created very early in the process of understanding the system requirements, and
they document only basic information about the use case, such as its name; ID
number; primary actor; type; a brief description; and the relationships among the
actors, actors and use cases, and use cases
• Detail use case
– Contains all the information needed for the use case.
• Essential Use Case
– Describes only the minimum essential issues necessary to understand the
required functionality
• Real use case
– Describes a specific set of steps
BUSINESS PROCESS DOCUMENTATION WITH USE CASES AND USE-CASE DESCRIPTIONS

Elements of a Use Case Description

• Use Case Name
• Actors
• Overview Information
• Stakeholders
• Trigger
• Relationships
• Normal Flow of Events
• Sub Flow
• Alternative/Exceptions
GUIDELINES FOR CREATING USE-CASE DESCRIPTIONS

• Write each individual step in the form subject–verb–direct object and,

optionally, preposition–indirect object
• Make clear who or what is the initiator of the action and who or what is the
receiver of the action in each step
• Write the step from the perspective of an independent observer
• Write each step at the same level of abstraction
• Ensure that the use case contains a sensible set of actions. Each use case
should represent a transaction
1. Th e primary actor initiates the execution of the use case by sending a
request (and possibly data) to the system.
2. Th e system ensures that the request (and data) is valid.
3. Th e system processes the request (and data) and possibly changes its
own internal state.
4. Th e system sends the primary actor the result of the processing
VERIFYING AND VALIDATING

• Walkthrough
–A walkthrough is essentially a peer review of a product
–A walkthrough uncovers errors or faults in the evolving specification
–A walkthrough does not correct errors

• Functional Model Verification and Validation

–With three different representations for the functional model: activity
diagrams, use-case descriptions, and use-case diagrams. In this section,
we describe a set of rules to ensure that these three representations are
consistent among themselves
DATA FLOW DIAGRAM

• Graphical representation of flow of data

• DFD includes a mechanism to model the data flow

• Supports decomposition

• Characteristics:
– (1) supporting the analysis and requirement stage of system design
– (2) a diagramming technique with annotation;
– (3) describing a network of activities/processes of the target system
– (4) allowing for behaviors of parallel and asynchronous (5) stepwise refinement
through hierarchical decomposition of processes.
DATA FLOW DIAGRAM

Symbols External Entity

Data Flow Data Store

DFS TYPES

• Context Diagram
– Highest abstraction Level. Contains the scope of an organizational system that
shows the system boundaries, external entities that interact with the system and
the major information flows
• Level 0
– represents a system’s major processes, data flows and data stores at a high level
of detail
• Level 1
– The breakdown of Level 0 into more degtail, contains basic processes and
sources of information.
• Level 2
– The breakdown of Level 1
• Level 3, 4 etc.
EXAMPLE

Context Diagram
EXAMPLE

Level 1
EXAMPLE

Decomposition Framework
REFERENCES

Alan Dennis, Barbara Haley Wixom, David Tegarden

(2015). Systems Analysis and Design_ An Object-
Oriented Approach with UML, 5th ed.
ISBN: 978-1-118-80467-4