1. Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis and Design with the Unified Modeling Language, Version 2.0 Alan Dennis, Barbara Wixom, and David Tegarden © 2005 John Wiley & Sons, Inc.

2. Slide 2 Copyright © 2005 John Wiley & Sons, Inc. All rights reserved. Reproduction or translation of this work beyond that permitted in Section 117 of the 1976 United States Copyright Act without the express written permission of the copyright owner is unlawful. Request for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. The purchaser may make back-up copies for his/her own use only and not for redistribution or resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.

3. Slide 3 Unified Modeling Language, Version 2.0 Chapter 2

4. Slide 4 Objectives Understand the basic characteristics of object- oriented systems. Be familiar with the basic concepts of the Unified Modeling Language (UML), Version 2.0. Be familiar with the process.

5. Slide 5 Basic Characteristics of Object Oriented Systems Classes and Objects Methods and Messages Encapsulation and Information Hiding Inheritance Polymorphism and Dynamic Binding

6. Slide 6 Classes and Objects Class – Template to define specific instances or objects Object – Instantiation of a class Attributes – Describes the object Behaviors – specify what object can do

7. Slide 7 Classes and Objects

8. Slide 8 Methods and Messages Methods implement an object’s behavior Analogous to a function or procedure Messages are sent to trigger methods Procedure call from one object to the next

9. Slide 9 Messages and Methods

10. Slide 10 Encapsulation and Information Hiding Encapsulation combination of data and process into an entity Information Hiding Only the information required to use a software module is published to the user Reusability Key Use an object by calling methods

11. Slide 11 Inheritance Superclasses or general classes are at the top of a hierarchy of classes Subclasses or specific classes are at the bottom Subclasses inherit attributes and methods from classes higher in the hierarchy

12. Slide 12 Class Hierarchy

13. Slide 13 Inheritance

14. Slide 14 Polymorphism and Dynamic Binding Polymorphism A message can be interpreted differently by different classes of objects Dynamic Binding Sometimes called late binding Delays typing or choosing a method for an object until run-time Static Binding Type of object determined at compile time

15. Slide 15 Polymorphish & Encapsulation

16. Slide 16 The Unified Modeling Language, Version 2.0 In this class we will use UML to describe three viewpoints of the current system and the new system. You will model these viewpoints with Use Cases and Use Case Diagrams Structure Diagrams Behavior Diagrams

17. Slide 17 Use Cases Use Case Descriptions and Use Case Diagrams are used to describe an external, functional viewpoint of the system. They model the business processes of the current and the new system. The principal question to ask is what information do users of the system give to the system and what information do they receive from it.

18. Slide 18 Use Case Diagrams Capture Business requirements Illustrate interaction between a system and its environment Includes end user Any external system that interacts with its information system The purpose of the Use Cases is to documents and clarify requirements of the system being modeled Think of Use Cases as the contract between you and the client organization

19. Slide 19 Structural Modeling Structure Diagrams are used to describe an internal, structural viewpoint of the system Structural Diagrams describe the all the classes, data and methods of the system that will store, process and deliver the information described by the use cases

20. Slide 20 Behavioral Modeling Behavioral Diagrams are used to describe the internal behavior of the system. The questions to ask is what are the steps required to produce information to the users and how do the objects have to interact in order to deliver it.

21. Slide 21 Object Oriented Systems Analysis and Design is Use-case driven Architecture Centric An Iterative and Incremental Process

22. Slide 22 Distribution of Effort Over Planning, Analysis, Design and Implementation Phases

23. Slide 23 Supporting Workflows

24. Slide 24 Benefits of the Object Approach

25. Slide 25 MOOSAD Approach