Introduction to ObjectOriented Analysis and Design - PowerPoint PPT Presentation

About This Presentation
Title:

Introduction to ObjectOriented Analysis and Design

Description:

4. Explain the basic characteristics of object-oriented systems. 5. Explain the Unified Process. 6. Explain encapsulation, polymorphism, and inheritance. 3. Key ... – PowerPoint PPT presentation

Number of Views:82
Avg rating:3.0/5.0
Slides: 26
Provided by: FredNie
Category:

less

Transcript and Presenter's Notes

Title: Introduction to ObjectOriented Analysis and Design


1
Introduction to Object-Oriented Analysis and
Design
  • Chapter 2

1
2
Learning Objectives
  • 4. Explain the basic characteristics of
    object-oriented systems
  • 5. Explain the Unified Process
  • 6. Explain encapsulation, polymorphism, and
    inheritance

2
3
Key Definitions
  • Object-oriented techniques view a system as a
    collection of self-contained objects which
    include both data and processes.
  • The Unified Modeling Language (UML)
  • the object modeling standard
  • adds a variety of techniques to the field of
    system development.

3
4
THE OBJECT APPROACH AND UML
4
5
Object Concepts/Characteristics
  • An object is a person, place, event, or thing
    about which we want to capture information.
  • Each object has properties (or attributes).
  • The state of an object is defined by the value of
    its properties and relations with other objects
    at a point in time.
  • Objects have behaviors -- things that they can do
    -- which are described by methods (or
    operations).
  • Objects do not use primary or foreign keys,
    instead each instance is assigned a unique
    identifier (UID) when it is created.

5
6
An Object and Object Instances
6
7
Class
  • A class is a general template we use to define
    and create specific instances or objects.

7
8
Classes and Objects
8
9
Class Hierarchy
9
10
Messages
  • Messages are information sent to objects to
    trigger methods

10
11
Encapsulation
  • The message is sent without considering how it
    will be implemented
  • The object can be treated as a black-box

11
12
Inheritance
  • Classes are arranged in a hierarchy
  • Superclasses or general classes are at the top
  • Subclasses or specific classes are at the bottom
  • Subclasses inherit attributes and methods from
    the superclasses above them
  • Classes with instances are concrete classes
  • Abstract classes only produce templates for more
    specific classes

12
13
Inheritance
13
14
Polymorphism
  • The same message can be interpreted differently
    by different classes of objects

14
15
Polymorphism
15
16
Unified Modeling Language - UML
16
17
Unified Modeling Language - UML
  • Defines a set of 14 object diagramming techniques
    (we will learn only 4)
  • 2 major groupings structure and behavior
  • Diagrams are tightly integrated syntactically and
    conceptually to represent an integrated whole
  • Application of UML can vary among organizations

17
18
Structure Diagrams
  • Class Diagrams
  • Object Diagrams
  • Package Diagrams
  • Deployment Diagrams
  • Component Diagrams
  • Composite Structure Diagrams

18
19
Behavior Diagrams
  • Activity Diagrams
  • Sequence Diagrams
  • Communication Diagrams
  • Interaction Overview Diagrams
  • Timing Diagrams
  • Behavior State Machines
  • Protocol State Machines
  • Use Case Diagrams

19
20
Object Oriented Analysis and Design and the
Unified Process
20
21
Object Oriented Analysis and Design
  • Use Case Driven
  • Use cases are the primary modeling tool
  • Architecture Centric
  • The software architecture drives the
    specifications, construction, and documenation
  • Iterative and Incremental
  • Continuous refinement

21
22
Unified Process (similar to the four steps of
SDLC)
  • Phases
  • Inception
  • Similar to Planning phase
  • Elaboration
  • Similar to Analysis and Ddesign phase
  • Construction
  • Combines end of Ddesign phase with beginning of
    Implementation
  • Transition
  • Testing and deployment of the Implementation
    phase

22
23
Workflows (Engineering)
  • Business modeling
  • Requirements
  • Analysis
  • Design
  • Implementation
  • Test
  • Deployment

23
24
Workflows (Supporting)
  • Configuration and change management
  • Project management
  • Environment

24
25
Adaptation of the Phased Development Method
25
Write a Comment
User Comments (0)
About PowerShow.com