chapter5

for the Small Enterprise

section II
Analysis
Systems Analysis and Design

object-oriented methodology
object models
use case modeling
unified modeling language
the data dictionary
the cornucopia case
portfolio project
 Chapter Objectives

When you complete this chapter you will be able to:

• Differentiate between object-oriented and
traditional methodologies
• Identify objects and construct an elementary
object model
• Identify the elements in a use case model
• Identify the elements in four of the most common
UML models
• Define, construct, and maintain data dictionaries

Systems Analysis and Design

Chapter 5 2
for the Small Enterprise
 Object-Oriented Methodology

• Object-oriented systems analysis and design

(OOSAD) evolved to accommodate the
increasing popularity of object-oriented
programming languages

• If you plan to implement your design with

object-oriented development tools, you should
seriously consider using OOSAD

• As the name implies, OOSAD revolves around

objects

Systems Analysis and Design

Chapter 5 3
for the Small Enterprise
 Object-Oriented Methodology

• Information system objects derive their

definition from our understanding of real-
world objects

• Just as real-world objects are organized into

classifications, enterprise objects are
members of a class

• While a specific object is distinguished by its

particulars, it inherits its general makeup
from its class

Systems Analysis and Design

Chapter 5 4
for the Small Enterprise
 Object-Oriented Methodology

• By definition, a class embodies two important

information processing concepts:
– Data attributes
– Behaviors

• After enterprise objects are created from their

class blueprint, their data attributes are
assigned values and their behaviors are
tailored to fit their specific circumstance

• Objects interact with one another through a

messaging system

Systems Analysis and Design

Chapter 5 5
for the Small Enterprise
 Object-Oriented Methodology

• The object-oriented methodology involves

familiar phases: analysis, design, and
implementation
– Analysis: Identify the classes from which
enterprise objects are created and the
interactions between these classes

– Design: Refine class definitions and

interactions based on the requirements of the
new information system

– Implementation: Create a working information

system using object-oriented languages and
tools

Systems Analysis and Design

Chapter 5 6
for the Small Enterprise
 Object Models

• In the OOSAD methodology, the object

model serves the same purpose as do the
DFD and ERD in the traditional SDLC
methodology

• The object model is focused on data and

software, showing classes and class
interactions

Systems Analysis and Design

Chapter 5 7
for the Small Enterprise
 Figure 5-1: The Object Model and the Six CIS Components

Object

People Class
Procedures
Data Attributes
Hardware
Software Methods
Networks

Systems Analysis and Design

Chapter 5 8
for the Small Enterprise
 Object Models

Object Identification:

• Use case modeling is the preferred technique

for identifying enterprise objects

• Another way to identify classes is to use the

DFD and ERD models as a springboard, where
each of the DFD’s data stores and ERD’s
entities are potential classes

Systems Analysis and Design

Chapter 5 9
for the Small Enterprise
 TECHNOTE 5-1

Anatomy of an Object

•Class: a two-part abstraction (attributes and methods) of

a real-world person, place, thing, or activity
•Instance: a specific object created from the class
blueprint
•Encapsulation: describes the enveloping, membrane-like
environment in which an object exists
•Messages: means by which objects communicate with
each other
•Polymorphism: allows a method to behave differently
when encapsulated in different classes
•Inheritance: imprints class definitions on new
generations of the class
•Class relationships: describes the way classes interact
with one another
Systems Analysis and Design
Chapter 5 10
for the Small Enterprise
 Object Model Symbols

Reference Figure 5-2: Silhouette Sea Charter’s Object Model

Systems Analysis and Design

Chapter 5 11
for the Small Enterprise
 Figure 5-2:Silhouette Sea Charter’s Object Model

This aggregate relationship allows

for one or more customers to
signup for the same charter

This specialization relationship

indicates that there are two
subsets of the Boat class

Systems Analysis and Design

Chapter 5 12
for the Small Enterprise
 Comparing Silhouette’s Object Model and Data Model

Object Model

Data Model

Systems Analysis and Design

Chapter 5 13
for the Small Enterprise
 Use Case Modeling

• Use case modeling provides a systematic way

to identify objects

• A use case is a detailed description of what

happens when someone or something
interacts with the information system

• The nouns used to title the use case scenarios

provide a basis for object identification

• The interactions between use cases provide

the basis for defining the relationship between
the objects underlying class

Systems Analysis and Design

Chapter 5 14
for the Small Enterprise
 Unified Modeling Language

• The Unified Modeling Language (UML) has

emerged as the generally accepted modeling
standard for object-oriented methodologies
and techniques

• Four of the numerous UML diagrams serve the

same function as the traditional DFD, ERD, and
walk-through models:
– Use case diagram
– Class diagram
– Interaction diagrams
– Statechart diagrams

Systems Analysis and Design

Chapter 5 15
for the Small Enterprise
 Figure 5-3: Nine UML Modeling Diagrams

Class Diagram
Object Diagram
Use Case Diagram
Interactive (Sequence) Diagram
Interactive Collaborative Diagram
Statechart Diagram
Activity Diagram
Component Diagram
Deployment Diagram
Systems Analysis and Design
Chapter 5 16
for the Small Enterprise
 Figure 5-4: Silhouette’s UML Use Case Diagram

Systems Analysis and Design

Chapter 5 17
for the Small Enterprise
 Figure 5-5: Silhouette’s UML Class Diagram

Systems Analysis and Design

Chapter 5 18
for the Small Enterprise
 Figure 5-6: Silhouette’s UML Interactive sequence Diagram

Systems Analysis and Design

Chapter 5 19
for the Small Enterprise
 Figure 5-7: Silhouette’s UML Statechart Diagram

Systems Analysis and Design

Chapter 5 20
for the Small Enterprise
 ThinkingCritically
Inflatable Labor Charges

What action would you recommend

if you discovered that your most
talented analyst had consistently
inflated the labor hours charged to a
project?

Systems Analysis and Design

Chapter 5 21
for the Small Enterprise
 The Data Dictionary

A data dictionary is an ordered catalog of data

elements and their definitive characteristics

Form Symbols

multiple entries {}
permitted

optional entry []

key field underline

data structure =
composition

attribute +
separator

Systems Analysis and Design

Chapter 5 22
for the Small Enterprise
 Figure 5-8: Illustrated Data Dictionary Form and Symbols

Element Name: customer

Type: data store

Description: customer master file

Contents: customer = custid+

name+
address+
phone

Usage Cross-Reference: DFD, USD,

ERD, system flowchart

Storage reference: customer.dbf

Systems Analysis and Design

Chapter 5 23
for the Small Enterprise
 The Cornucopia Case
THE CORNUCOPIA CASE

The analysts do not intend to use an object-

oriented programming language to
implement the new system. Even the
objectlike features of 4Gl software do not
require object identification or use case
modeling.

Cornucopia’s object model is derived from

the ERD.

Systems Analysis and Design

Chapter 5 24
for the Small Enterprise
 Figure 5-9: Cornucopia
Existing System Object Model

Systems Analysis and Design

Chapter 5 25
for the Small Enterprise
 Figure 5-10: Cornucopia Object Definition
with Visible Analyst

Enlarge
Systems Analysis and Design
Chapter 5 26
for the Small Enterprise
PortfolioprojectPortfolio Project

Team Assignment 5: Object Modeling

•Review the existing system ERD,

giving consideration to the potential for
each entity to be defined as a class
•Prepare the UML diagram for the
existing system

Systems Analysis and Design

Chapter 5 27
for the Small Enterprise
 Chapter Summary (1/3)

• The object model is an alternative to the

traditional SAD methodology

• It is important to understand the object model,

even if the analyst does not intend to use
object-oriented development tools

• Objects are created from a class blueprint

Systems Analysis and Design

Chapter 5 28
for the Small Enterprise
 Chapter Summary (2/3)

• Objects are characterized by their attributes

and behaviors

• Objects communicate with one another

through messaging

Systems Analysis and Design

Chapter 5 29
for the Small Enterprise
 Chapter Summary (3/3)

• The Unified Modeling Language (UML)

provides a collection of modeling tools for
OOSAD
– Use case diagram
– Class diagram
– Interaction diagrams
– Statechart diagram

• The data dictionary provides a systematic

procedure to keep track of the names,
definitions, associates, and existing or
proposed uses of data
Systems Analysis and Design
Chapter 5 30
for the Small Enterprise
 Figure 5-10 Enlargement

Return
Systems Analysis and Design
Chapter 5 31
For the Small Enterprise