Functional Modeling

Chapter 5 Dennis, Wixom and Tegarden

PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition
Copyright 2009 John Wiley & Sons, Inc. All rights reserved.

Objectives
Understand the rules and style guidelines for activity diagrams. Understand the rules and style guidelines for use cases and use-case diagrams. Understand the process used to create use cases and use-case diagrams Be able to create functional models using activity diagrams, use cases, and use-case diagrams.
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 2

BUSINESS PROCESS MODELING WITH ACTIVITY DIAGRAMS

Business Process Modeling

Business process models describe the sequences of activities that collectively support a business process A very powerful tool for communicating the analysts current understanding of the requirements with the user Activity diagrams are used to model the behaviour of a business process
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 4

Activity Diagram Syntax

Action or Activity Control Flow
Object Flow
Represents action or set of actions Shows sequence of execution Shows flow of an object between actions The beginning of a set of actions Stops all flows in an activity

Initial Node Final Node

Decision Node, Merge Node

17 March, 2011

Represents a conditional branch or join

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 5

Sample Activity Diagram

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

Guidelines for Activity Diagrams

Set the scope of the activity being modeled (activity, process, workflow) Identify the activities, control flows, and object flows that occur between the activities Identify any decisions that are part of the process being modeled Identify potential parallelism in the process or workflow Draw the activity diagram
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 7

Activity Diagram Swimlanes

Subdivides the Activity diagram by responsibility Business activity may be conducted by several people/objects Each objects responsibilities for the activity are shown in a separate swimlane Adds clarifying detail to complex activities and workflows May be horizontal or vertical
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 8

Swimlane example
Customer Sales Warehouse Request product Process order Pick materials Continue work Ship order

Receive order Pay bill

Bill Customer

Close order

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

Alternative conventions
Several syntaxes in common use for Activity diagrams BPMN Business Process Modelling Notation EPC Event-Driven Process Chain Eriksson-Penker Business Modelling Profile All conceptually similar, but not the same Be prepared to see them all in professional practice
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 10

USE-CASE DESCRIPTIONS

Use Cases
A use case illustrates the activities that are performed by the actors (users) of a system. They describe the basic functions of the system
What the actor (user) can do How the system responds

Use cases are building blocks for continued design activities. Documented as Use Case Descriptions
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 12

Types of Use Cases

Amount of information Overview Detail Detailed description of issues essential to understanding required functionality Detailed description of a specific set of steps performed on the real system once implemented

Essential Real

Purpose

High-level overview of issues essential to understanding required functionality High-level overview of a specific set of steps performed on the real system once implemented

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

13

Use Case Elements: Overview

Name ID Number Type Primary Actor Brief Description Importance Level Stakeholder(s) Trigger(s) Trigger type (ext/int)

Relationships
Association Include Extend Generalisation

Normal flow of events Subflows Exception/Alternate flows (see Fig 5-5 p169)
14

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

Use Case Elements: Relationships

Association Extend
represents the extension of the functionality of the use case to incorporate optional behaviour documents the communication between the use case and the actors that use the use case

Include
shows the mandatory inclusion of another use case

Generalisation
allows use cases to support inheritance
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 15

Use Case Elements: Flows

Normal Flows
include only those steps that are executed in the normal use case

Sub-Flows
the normal flow of events decomposed to keep that flow of events as simple as possible

Alternate or Exceptional Flows

flows that do happen but are not considered to be the norm
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 16

Use Case Description Writing Guidelines

Write in the form of subject-verb-direct object Make sure it is clear who is the initiator of the step Write from an independent observers perspective Write at a consistent level of abstraction Ensure the use case has a sensible set of steps Apply the KISS principle liberally (but dont insult the readers intelligence) Write repeating instructions after the set of steps to be repeated
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 17

USE-CASE DIAGRAMS
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 18

Use Case Diagram Syntax

Actor
person or system that derives benefit from, and is external to, the subject

Use Case
Represents a major piece of system functionality

Association Relationship Include Relationship Extend Relationship Generalisation Relationship

17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

<<includes>> <<extends>>

19

Sample Use Case

Fig 5-10 pg 177

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

20

CREATING USE-CASE DESCRIPTIONS AND USE-CASE DIAGRAMS

17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 21

Identify the Major Use Cases

Review the activity diagram Find the subjects (process, activity) boundaries Identify the primary actors and their goals Identify and write the overviews of the major use cases for the above Carefully review the current use cases. Revise as needed
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 22

Extend the Major Use Cases

Choose one of the use cases to expand Start filling in the details of the chosen use case Write the normal flow of events of the use case If the normal flow of events is too complex or long, decompose into sub flows List the possible alternate or exceptional flows For each alternate or exceptional flow, list how the actor and/or system should react
17 March, 2011 ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material. 23

Confirm the Major Use Cases

Carefully review the current set of use cases with the users. Revise as needed Start again, to confirm that the users got it right, or have changed their requirements

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

24

Create the Use Case Diagram

Draw the subject boundary Place the use cases on the diagram Place the actors on the diagram Draw the associations

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

25

REFINING PROJECT SIZE AND EFFORT ESTIMATION USING USE-CASE POINTS

Research task: Read and understand this topic, explained on pp182-187

Next lecture
Structural modelling Objects Classes

17 March, 2011

ICT117 Systems Analysis & Design, Semester 1, 2011. Includes John Wiley & Sons material.

27