Systems Analysis and Design

TOPIC TITLE: OBJECT-ORIENTED ANALYSIS AND DESIGN

USING UML (PART 1)

SPECIFIC OBJECTIVES:

At the end of the topic session, the students should be able to:

1. describe the concepts about the object-oriented approach,

2. identify the phases of the object-oriented development life cycle,
3. recall the concepts used in object-oriented,
4. describe the concepts of the unified modeling language (UML),
and
5. identify the components in the UML.

MATERIALS/EQUIPMENT:

o OHP
o File/s (11 Object-Oriented Analysis and Design Using UML (Part
1))
 11 Instructor’s Guide
 11 Presentation
 11 Handout
o Software requirements
 MS PowerPoint

TOPIC PREPARATION:

o Prepare the slide handout (4 pages) needed for the topic

presentation and have it photocopied.
o Prepare the computer unit for slides presentation.
o Prepare additional examples on the sub-topics to be presented.

PRESENTATION OVERVIEW:

A. Bell-ringer 5 min
B. Instructional Input
Object-Oriented Development Life Cycle 10 min
a. Discuss the phases of OODLC using the figure
b. Discuss the reasons for using object-oriented design
Object-Oriented Concepts 10 min
a. Discuss objects, classes, and inheritance
The Unified Modeling Language 20 min
a. Explain unified modeling language
b. Discuss the table of the overall view of UML and its
components
c. Discuss the elements of things
d. Discuss the two ways of relationship
e. Discuss the types of UML diagrams
f. Discuss the six commonly used UML diagrams
C. Generalization 15 min
D. Application 60 min
Total duration 180 min

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 1 of 9
 Systems Analysis and Design

TOPIC PRESENTATION:

A. Bell-ringer

1. Start the session by telling your students that this discussion will be
the first part of Object-Oriented Analysis and Design using UML.

2. Ask at least three of your students of their idea about Object-Oriented

Development Life Cycle. Write down on the board the keywords of
their answer and relate it to your discussion later on.

3. Have a brief introduction of the topic to be discussed.

B. Instructional Input

Object-Oriented Development Life Cycle

Slide 1 1. Start the discussion by presenting the topic coverage to your students
using Slide 1 of 11 Presentation.
Systems Analysis and Design

Object-Oriented
Analysis and Design
using UML (Part 1)

 Object -Orien ted Developm en t

Life Cycle
 Object -Orien ted Con cepts
 Th e Un ified Modelin g Lan guage

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 1 of 16

Slide 2 2. Show Slide 2 and discuss the phases of OODLC using the figure in
the slide.
Systems Analysis and Design

Object-Oriented The OODLC is an update of the older SDLC. Figure 11.1

Development Life Cycle
depicts the phases of the OODLC.

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 2 of 16

Figure 11.1 Phases of the OODLC

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 2 of 9
 Systems Analysis and Design

The object-oriented development life cycle shown in the

figure is composed of progressively and developing object
representation through three phases: (1) analysis, (2) design,
and (3) implementation. In the initial stages of development,
the model built is abstract, which focused on the external
qualities of the application system. As the model evolves, it
becomes progressively detailed, changing the focus on how
the system will be built and how it should function. Analysis
and design should be the emphasis of modeling that focuses
on front-end conceptual issues rather than back-end
implementation issues.

In the analysis phase, the users’ requirements are modeled.

The focus should be on analyzing and modeling the real
world of domain interest and not the internal characteristics of
the software system during analysis activities. You need to
devote sufficient time to understand clearly the requirements
of the problem. The analysis model should obtain those
requirements completely and accurately.

Slide 3 3. Show Slide 3 and discuss the reasons for using object-oriented
design.
Systems Analysis and Design

Object-Oriented In the design phase, the analysis models are elaborated to

Development Life Cycle
produce implementation specifications. According to
 According to Jacobson et al, there are
Jacobson et al, there are three reasons for using object-
three reasons for using object-oriented
design.
oriented design. These are:
 The analysis model is informal enough to be
implemented directly in a programming
language. 1. The analysis model is informal enough to be
 The actual system should be adapted to the
environment in which the system will implemented directly in a programming language.
actually be implemented.
 The analysis results can be validated using Converting this into source code requires refining the
object-oriented design.
objects by making decisions on what operations an
object will provide; what the inter object
communication should look like; what messages are
to be passed; and so on.

Object-Oriented Analysis and Design using UML

(Part 1)
* Property of STI
Page 3 of 16
2. The actual system should be adapted to the
environment in which the system will actually be
implemented. To achieve that, the analysis model is
converted into a design model, with different factors
considered, such as performance requirements; real-
time requirements and concurrency; target hardware
and systems software; the DBMS and programming
language to be implemented; and so on.

3. The analysis results can be validated using object-

oriented design. At this stage, the results from the
analysis is verified if it is appropriate for building the
system and if necessary changes are made to the
analysis model.

Followed by the design phase is the implementation phase,

wherein the design is implemented using a programming
language and/or a database management system.
Converting the design into program code is relatively in a
straightforward process.

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 3 of 9
 Systems Analysis and Design

Object-Oriented Concepts

1. Before showing the next slide, ask your students what they remember
about objects, classes, and inheritance from their previous subjects.
Write down the keywords of their answer on the board and relate their
answers to the discussion.

Slide 4 2. Show Slides 4 to 5 and discuss objects, classes, and inheritance.

Systems Analysis and Design
Below are the general descriptions of the key object-oriented
Object-Oriented Concepts concepts of objects, classes, and inheritance.

Objects
 Objects
 can be a person, place, or thing that is


relevant to the system to be analyzed
can also be a GUI display or text area on
An object can be a person, place, or thing that is relevant to

the display
examples include customers, items, orders
the system to be analyzed. Examples of objects include
customers, items, orders, etc. An object can also be a GUI
display or text area on the display.

Classes

A class is a blueprint for an object. The blueprint specifies

the attributes (also known as instance variables) and
methods of the class. Attributes are things an object of that
Object-Oriented Analysis and Design using UML * Property of STI
(Part 1) Page 4 of 16
class knows while methods are things an object of that class
does. An object is instantiated (created) from the description
Slide 5 provided by its class. Thus, objects are often called
instances. Each object has its own values for the attributes
of its class. For example, two objects of the Person class
Systems Analysis and Design

Object-Oriented Concepts can have different values for the name attribute. Each object
shares the implementation of a class’ methods. When a
 Classes class is defined, a developer provides an implementation for
 blueprint for an object – attributes and
methods of the class each of its methods. Classes can define static attributes and
 can define static attributes and methods
methods. A static attribute is shared among all instances of a
 Inheritance
 implies that classes can inherit attribute and class (each object has the same value for the static attribute).
behavior from other classes
A static method does not have to be accessed via an object,
but it is invoked directly on a class.

Inheritance

Inheritance is an object-oriented concept, which implies that

classes can inherit attribute and behavior from other classes.
Object-Oriented Analysis and Design using UML
(Part 1)
* Property of STI
Page 5 of 16
Classes can have children—that is, one class can be created
out of another class. This is achieved by deriving a new
class, called a subclass, from the existing one. The new class
will then have the combined features of both classes. For
example, consider a Car class that defines everything
common to all cars. A Convertible subclass may then be
defined from the Car class. A Convertible then inherits
properties from the Car class. That is, a Convertible is a
Car that has and can do everything a plain Car does. This,
however, has added mechanisms for and an added ability to
lower its top. Note that a Convertible is not an object. It
is a class that inherits from the Car class.

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 4 of 9
 Systems Analysis and Design

The Unified Modeling Language

Slide 6 1. Show Slides 6 to 16 and explain what unified modeling language is.
Also, discuss the table of the overall view of UML and its
Systems Analysis and Design
components, the elements of things, the two ways of relationship,
The Unified Modeling
types of UML diagrams, and the six commonly used UML diagrams.
Language

 the standard visual modeling language

The Unified Modeling Language (UML) is the standard visual
 Businesses modeling language used for modeling businesses, software
 Software applications
 System architectures applications, and system architectures. Though it is a
standard of the Object Management Group (OMG), the UML
is not just for modeling object-oriented software applications
but also provides an effective means of communication
between the development team and the business team on a
project. The UML is a graphical language designed to be
very flexible and customizable, which enables designers to
create many different types of models, including models for
understanding business processes, workflow, sequences of
Object-Oriented Analysis and Design using UML
(Part 1)
* Property of STI
Page 6 of 16
queries, applications, databases, architectures, etc.

Slide 7 The UML is composed of things, relationships, and diagrams.

The table below shows the overall view of UML and its
Systems Analysis and Design
components.
The Unified Modeling
Language

 standard of the Object Management Group

UML Category UML Elements Specific UML
(OMG) Details
 graphical language designed to be very
flexible and customizable Things Structural Things Classes
 composed of things, relationships, and
diagrams Interfaces
Collaborations
Use Cases
Active Classes
Components
Nodes
Behavioral Things Interactions
State Machines
Object-Oriented Analysis and Design using UML
(Part 1)
* Property of STI
Page 7 of 16 Grouping Things Packages
Annotational Things Notes
Slide 8 Relationships Structural Dependencies
Relationships Aggregations
Systems Analysis and Design

The Unified Modeling

Associations
Language Generalizations
Behavioral Communicates
UML Category UML Elements Specific UML Details
Relationships Includes
Things Structural Things Classes Active Classes
Interfaces
Collaborations
Use Cases
Components
Nodes Extends
Behavioral Things Interactions
State Machines
Generalizes
Grouping Things

Annotational Things
Packages

Notes
Diagrams Structural Diagrams Class Diagrams
Relationships Structural
Relationships
Dependencies
Aggregations
Associations
Generalizations
Component
Behavioral
Relationships
Communicates
Includes
Extends
Generalizes
Diagrams
Diagrams Structural Diagrams Class Diagrams
Deployment
Component Diagrams

Behavioral
Deployment Diagrams

Use Case Statechart

Diagrams
Diagrams Diagrams
Sequence
Diagrams
Diagrams
Activity Diagrams Behavioral Use Case Diagrams
Collaboration
Diagrams
Diagrams Sequence
Object-Oriented Analysis and Design using UML * Property of STI
Diagrams
(Part 1) Page 8 of 16
Collaboration
Diagrams
Statechart
Diagrams

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 5 of 9
 Systems Analysis and Design

Slide 9 Activity Diagrams

Table 11.1 UML and its components
Systems Analysis and Design

The Unified Modeling The first component of UML is called things, which can also
Language be referred to as object. As shown in the table, there are
several elements of things and these are:
 Elements of Things:
 Structural things
• include classes, interfaces, use cases, and
many other elements that provide a means to  Structural things – most common of all elements;
create models
• allow the user to describe relationships also called classifiers that are mostly static parts of a
model; include classes, interfaces, use cases, and
many other elements that provide a means to create
models; allow the user to describe relationships

 Behavioral things – describe how things work;

dynamic parts of UML models; examples include
interactions and state machines

 Group things – used to define boundaries;

Object-Oriented Analysis and Design using UML * Property of STI
(Part 1) Page 9 of 16

organizational parts of UML models; an example is a

Slide 10 package

 Annotational things – used to add notes to the

Systems Analysis and Design

The Unified Modeling

Language diagrams; explanatory parts of UML models

 Behavioral things
• describe how things work
• include interactions and state machines
 Group things
• used to define boundaries
• example is a package
 Annotational things
• used to add notes to the diagrams

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 10 of 16
The second component of UML is called relationships, which
acts as glue that holds the things together. Relationships can
be useful in two ways:

Slide 11  Structural relationships – used to tie the things

together in the structural diagrams; include
Systems Analysis and Design
dependencies, aggregations, associations, and
The Unified Modeling
Language
generalizations; an example is inheritance

 Relationships can be useful in two ways:

 Behavioral relationships – used in the behavioral
diagrams; can be classified into four types, namely:
 Structural relationships
• used to tie the things together in the
structural diagrams
o Communicates
• include dependencies, aggregations,
associations, and generalizations
o Includes
• an example is inheritance
o Extends
o Generalizes

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 11 of 16

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 6 of 9
 Systems Analysis and Design

Slide 12

Systems Analysis and Design

The Unified Modeling

Language

 Behavioral relationships
• used in the behavioral diagrams
• can be classified into four types:
– Communicates
– Includes
– Extends
– Generalizes

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 12 of 16

The last component of UML is called diagrams, which have

two major types:

Slide 13  Structural diagrams – used , for instance, in

describing the relationships between classes; include
Systems Analysis and Design
class diagrams, object diagrams, component
The Unified Modeling
diagrams, and deployment diagrams
Language

 Two types of UML diagrams:

 Behavioral diagrams – used to describe the
interaction between people (called actors in UML)
 Structural diagrams
• used , for instance, in describing the and the thing referred to as a use case, or how the
relationships between classes
• include class diagrams, object diagrams,
component diagrams, and deployment
actors use the system; include use case diagrams,
diagrams
sequence diagrams, collaboration diagrams,
statechart diagrams, and activity diagrams

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 13 of 16

Slide 14

Systems Analysis and Design

The Unified Modeling

Language

 Behavioral diagrams
• used to describe the interaction between
people (called actors in UML) and the thing
referred to as a use case, or how the actors
use the system
• include use case diagrams, sequence
diagrams, collaboration diagrams, statechart
diagrams, and activity diagrams

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 14 of 16

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 7 of 9
 Systems Analysis and Design

There are six commonly used UML diagrams and these are
as follows:

Slide 15 1. A use case diagram describes how the system is

used. Systems analysts start with a use case
Systems Analysis and Design
diagram.
The Unified Modeling
Language
2. A use case scenario (though technically it is not a
 Six commonly used UML diagrams:
diagram) is a verbal articulation of exceptions to the
 A use case diagram describes how the
system is used. Systems analysts start with
main behavior described by the primary use case.
a use case diagram.
 A use case scenario (though technically it is
not a diagram) is a verbal articulation of 3. An activity diagram illustrates the overall flow of
exceptions to the main behavior described
by the primary use case. activities. Each use case may create one activity
 An activity diagram that illustrates the
overall flow of activities. diagram. It shows the structure of a process or other
computations as the flow control and data from step
to step within the computation.

4. Sequence diagrams show the sequence of activities

and class relationships. Each use case may create
Object-Oriented Analysis and Design using UML
(Part 1)
* Property of STI
Page 15 of 16
one or more sequence diagrams. An option to a
sequence diagram is a collaboration diagram, which
contains the same information in a different format. It
Slide 16
also emphasizes the time-ordering messages.
Systems Analysis and Design

The Unified Modeling 5. Class diagrams show the classes and relationships.
Language Sequence diagrams are used to determine classes.
An offshoot of a class diagram is a gen/spec diagram
 Sequence diagrams that show the
(stands for generalization/specification).
sequence of activities and class
relationships. An option to a sequence
diagram is a collaboration diagram, which
contains the same information in a different
6. Statechart diagrams show a state machine consisting

format.
Class diagrams that show the classes and
of states and transitions. Each class may create a

relationships.
Statechart diagrams that show the state
statechart diagram, which is useful for determining
transitions.
class methods.

Object-Oriented Analysis and Design using UML * Property of STI

(Part 1) Page 16 of 16

C. Generalization

1. Have a recap and summary of the topic discussed by having a short

quiz.

D. Application

1. Ask the students to perform the exercise below. Give the students an
hour to finish the exercise. Move around the class to check their
activities. Tell them that they can consult you with their concerns
regarding the activities.

2. Give the students time to research and discuss with their group about
their proposed system.

3. Each group should be able to complete their documentation with the

following information:

 Resource Requirements

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 8 of 9
 Systems Analysis and Design

o Hardware Requirements

o Software Requirements

o Human Resource Requirements

 Implementation Plan

o Site Preparation

o Personnel Training

o System Conversion

o Data Conversion

o Implementation Schedule

4. The font face of the document should be Arial, font size of 10 and
paper size should be A4.

5. Ask each group to submit the documentation of their proposed

system on the next session.

REFERENCES:

Valacich, J., George, J. & Hoffer, J. (2012). Essentials of systems:

analysis and design (5th Edition). Upper Saddle River, New Jersey:
Pearson.

Shelly, G. & Harry J. (2012). Systems analysis and design (9th Edition).
Boston: Course Technology Cengage Learning.

Whitten, J. & Bentley, L. (2007). Systems analysis and design methods

(7th Edition). Boston : McGraw-Hill/Irwin.

Yeates, D. & Wakefield, T. (2004). Systems analysis and design (2nd

Edition). Harlow, UK : Financial Times Prentice Hall.

Hoffer, J., George, J.& Valacich, J. (2008). Modern systems analysis and
design (5th Edition.). Upper Saddle River, N.J.: Prentice Hall.

Object-Oriented Analysis and Design Using UML (Part 1) *Property of STI

Page 9 of 9