Home arrow Practices arrow Page 8 - Introducing UML: Object-Oriented Analysis and Design

Summary - Practices

The purpose of UML, or Unified Modeling Language, is communication; to be specific, it is to provide a comprehensive notation for communicating the requirements, architecture, implementation, deployment, and states of a system. This article will offer an overview of Object Oriented Analysis and Design, focusing in on the three most important concepts it encompasses: objects, analysis, and design. It is excerpted from the book UML Applied: A .Net Perspective, by Martin Shoemaker (Apress, 2004; ISBN: 1590590872).

  1. Introducing UML: Object-Oriented Analysis and Design
  2. Analysis
  3. UML
  4. UML Diagrams
  5. Component Diagrams
  6. Package Diagrams
  7. It’s All About Communication
  8. Summary
By: Apress Publishing
Rating: starstarstarstarstar / 169
July 21, 2005

print this article



I began this chapter with a quick overview of some of the main concepts underpinning Object-Oriented development and seeing how these apply to the process of Analysis and Design. Next, I discussed how modeling can help you not only design a better system, but also develop a better understanding of that system and how it should work.

In the second half of this chapter, we dipped our toes in the waters of UML— taking a quick look at some of the different types of diagram—but it’ll be time to jump right in during the next chapter.

Exercise Solutions

Solutions to Exercise 101

  1. The system creates a kennel assignment, a mapping of a pet to a specific pen.

  2. The system closes the kennel assignment.

  3. Checking a pet in or checking a pet out.

  4. Logging a medical problem.

Solutions to Exercise 102

  1. Enter the pet’s name. Find available kennel space. Assign the kennel to the pet.

  2. Enter the pet’s personal data. Create a new record for the pet.

Solutions to Exercise 103

   1.  ICareGiving.

    2.  Reservation Center through the IReservations interface. 
        Accounting Center through the IAccounting interface.

    3.  Intercom, telephone, email, and postal.

Solutions to Exercise 104

   1.  Care Giver Center, Vet Record Page, ICareGiving interface,  
        and ICommunications interface.

   2.  Care Giver and Veterinarian.

    3.  ICareGiving.

   4.  Via a telephone contact.

Solutions to Exercise 105

  1. Pet Record, Reservation Record, and Kennel Space.

  2. Create and Close.

  3. Name, Species, Breed, Owner, and Schedule.

  4. Kennel Number, Building, Size, and Status.

Solutions to Exercise 106

  1. Specifications Completed.

  2. Construction Completed (from Defined), Pet Checked Out (from In Use), and Pet Relocated (also from In Use).

  3. Deconstructed.

   4. Via a Pet Checked Out event or a Pet Relocated event,
       followed by a Dismantled event. This prevents the system from
       having a pet with no defined pen. (Can’t have the dogs running

Solutions to Exercise 107

  1. Accounting center and reception center.

  2. Via the modem.

  3. Via the Internet.

  4. According to this diagram, the only path possible is through the KMS server. Although the diagram doesn’t explicitly state this, the likely approach is that the care giver station updates information in the central database, and the reception center reads this updated data.

Solutions to Exercise 108

  1. Care Giver Classes, Accounting Classes, Reservation Classes, and KMS Central Classes.

  2. KMS Interfaces and KMS Database Classes.

    1. Grady Booch, Object-Oriented Analysis and Design with
, Second Edition (Addison-Wesley, 1994). This is the
       classic work on OOAD, and a must-read.

    2. Steve McConnell, Code Complete: A Practical Handbook of 
       Software Construction
(Microsoft Press, 1993), pp. 81–93, 116–
       130, 150. McConnell provides far more information
on code 
       design than I can cover here.

   3. See http://www.cuttysark.org.uk/ for pictures and the history
       of this vessel.   

   4. Steve McConnell, Software Project Survival Guide (Microsoft
       Press, 1997), p. 29

   5. Kent Beck, Extreme Programming Explained: Embrace Change 
      (Addison Wesley, 1999),
pp. 21–25

   6. In December 2002, Rational became a division of IBM Corporation.

   7. Martin Fowler and Kendall Scott, UML Distilled, Second Edition
      (Addison-Wesley, 1999), pp. 13–38

   8. Murray R. Cantor, Object-Oriented Project Management with UML
      (John Wiley & Sons, 1998), pp. 98–103

   9. Putnam P. Texel and Charles B. Williams, Use Cases Combined
      with Booch/OMT/UML: Process and Products
(Prentice Hall,
      1997), pp. 3–9ff.

 10. Ivar Jacoboson, Grady Booch, and James Rumbaugh, The Unified
      Software Development Process
(Addison-Wesley, 1999)

 11. Scott W. Ambler, Agile Modeling: Effective Practices for eXtreme
      Programming and the
Unified Process
(John Wiley & Sons, 2002)

 12. Klutz Press Editors, Draw the Marvel Comics Super Heroes (Klutz
      Press, 1995), pp. 20–32

13. Scott Adams, The Dilbert Principle (HarperBusiness, 1997), p. 324

>>> More Practices Articles          >>> More By Apress Publishing

blog comments powered by Disqus
escort Bursa Bursa escort Antalya eskort


- Calculating Development Project Costs
- More Techniques for Finding Things
- Finding Things
- Finishing the System`s Outlines
- The System in So Many Words
- Basic Data Types and Calculations
- What`s the Address? Pointers
- Design with ArgoUML
- Pragmatic Guidelines: Diagrams That Work
- Five-Step UML: OOAD for Short Attention Span...
- Five-Step UML: OOAD for Short Attention Span...
- Introducing UML: Object-Oriented Analysis an...
- Class and Object Diagrams
- Class Relationships
- Classes

Developer Shed Affiliates


Dev Shed Tutorial Topics: