Scribd
Upload
41 views

Object Oriented Systems Analysis and Des

The document discusses Object-Oriented Systems Analysis and Design (OOSAD). It states that OOSAD uses a RAD methodology and focuses on decomposing problems into objects that contain both data and process. It also discusses that modern OOSAD approaches should be use-case driven, architecture-centric, and iterative and incremental. The document provides details on what each of these terms mean and how they are implemented in OOSAD.

Uploaded by

eman adem
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
41 views

Object Oriented Systems Analysis and Des

The document discusses Object-Oriented Systems Analysis and Design (OOSAD). It states that OOSAD uses a RAD methodology and focuses on decomposing problems into objects that contain both data and process. It also discusses that modern OOSAD approaches should be use-case driven, architecture-centric, and iterative and incremental. The document provides details on what each of these terms mean and how they are implemented in OOSAD.

Uploaded by

eman adem
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

Object-Oriented Systems Analysis and Design

(OOSAD)

Dr. Said P. Martagón


Outline

Object-Oriented Systems Analysis and Design (OOSAD)


Object-Oriented approaches to developing information systems,
technically speaking, can use any of the traditional methodologies.
However, the object-oriented approaches are most associated with
a phased development RAD methodology.

Object-Oriented methodologies have emerged that use the


RAD-based sequence of SDLC phases but attempt to balance the
emphasis between process and data by focusing the decomposition
of problems on objects that contain both data and process.
According to the creators of the Unified Modeling Language
(UML), Grady Booch, Ivar Jacobson, and James Rumbaugh1 , any
modern object-oriented approach to developing information
systems must be
1. Use-case driven.
2. Architecture-centric.
3. Iterative and incremental.

1
Grady Booch, Ivar Jacobson, and James Rumbaugh, The Unified Modeling
Language User Guide (Reading, MA: Addison-Wesley, 1999)
Use-Case Driven

Use-case driven means that use cases are the primary modeling
tools defining the behavior of the system. A use case describes how
the user interacts with the system to perform some activity, such
as placing an order, making a reservation, or searching information.

The use cases are used to identify and to communicate the


requirements for the system to the programmers who must write
the system.

Use case are inherently simple because they focus on only one
activity at a time.
Architecture Centric

Architecture centric means that the underlying software


architecture of the evolving system specification drives the
specification, constructions, and documentation of the system.

Modern object.oriented systems analysis and design approaches


should support at least three separated but interrelated
architectural views of a system: functional, static, and dynamic.
The functional, or external, view describes the system in terms of
behavior of the system in terms of messages passed among objects
and state changes withing an object.
Iterative and Incremental

Modern object-oriented systems analysis and design approaches


emphasize iterative and incremental development that undergoes
continuous testing and refinement throughout the life of the
project. This implies that the systems analysts develop their
understanding of a user’s problems by building up the three
architectural views little by little.
The systems analyst does this by working with the user to create a
functional representation of the system under study. Next, the
analyst attempts to build a structural representation of the
evolving system. Using the structural representation of the system,
the analyst distributes the functionality of the system over the
evolving structure to create a behavioral representation of the
evolving system.
All three architectural views of the system are interlinked and
dependent on each other. As each increment and iteration is
completed, a more complete representation of the user’s real
functional requirements are uncovered.

Figure: Iterative and Incremental Development


Outline

Object-Oriented Systems Analysis and Design (OOSAD)


Benefits of Object-Oriented Systems Analysis and Design

Concepts in the Object-Oriented approach enable analysts to break


a complex system into smaller, more manageable modules, work on
the modules individually, and easily piece the modules back
together to form an information system. This modularity makes
system development easer to grasp, easer to share among members
of a project team, and easer to communicate to users.
The project team actually is creating reusable pieces that can be
plugged into other systems efforts or used as starting points for
other projects.

Many people argue that ”object-think” is a much more realistic


way to think about the real world. Users typically do not think in
terms of data or process; instead, they see their business as a
collection of logical units that contain both - so communicating in
terms of objects improves the interaction between a user and an
analyst or developer.

You might also like