Page 286 -

CHAPTER 10

Object-Oriented Systems

Analysis and Design Using

UML *

Learning Objectives
Once you have mastered the material in this chapter you will be able to:
1. Understand what object-oriented systems analysis and design is and appreciate its
usefulness.
2. Comprehend the concepts of Unified Modeling Language (UML), the standard approach for
modeling a system in the object-oriented world.
3. Apply the steps used in UML to break down the system into a use case model and then a
class model.
4. Diagram systems with the UML toolset so they can be described and properly designed.

5. Document and communicate the newly modeled object-oriented system to users and other
analysts.

j

Object-oriented analysis and design can offer an approach that facili-
tates logical, rapid, and thorough methods for creating new systems that
are responsive to a changing business landscape. Object-oriented tech-
niques work well in situations in which complicated information systems
are undergoing continuous maintenance, adaptation, and redesign.
In this chapter, we introduce Unified Modeling Language (UML),
the industry standard for modeling object-oriented systems. The UML
toolset includes diagrams that allow you to visualize the construction of an object-oriented
system. Each design iteration takes a successively more detailed look at the design of the
system, until the things and relationships in the system are clearly and precisely defined in
UML documents. UML is a powerful tool that can greatly improve the quality of your systems
analysis and design, and thereby help create higher-quality information systems.
When the object-oriented approach was first introduced, advocates cited reusability of
the objects as the main benefit of the approach. It makes intuitive sense that the recycling
of program parts should reduce the costs of development in computer-based systems. It has
proven to be very effective in the development of GUIs and databases. Although reusability is
the main goal, maintaining systems is also very important, and because the object-oriented
approach creates objects that contain both data and program code, a change in one object
has a minimal impact on other objects.

253
* By Julie E. Kendall, Kenneth E. Kendall, and Allen Schmidt.