slide 1 unified modeling language, version 2.0 object-oriented sad
TRANSCRIPT
Slide 1
Unified Modeling Language, Version 2.0
Object-Oriented SAD
Slide 2
Objectives
Understand the basic characteristics of object-oriented systems.
Be familiar with the Unified Modeling Language (UML), Version 2.0.
Slide 3
Basic Characteristics of Object Oriented Systems
Classes and ObjectsMethods and MessagesEncapsulation and Information HidingInheritancePolymorphism and Dynamic Binding
Slide 4
Classes and Objects
Class – Template to define specific instances or objectsObject – Instantiation of a classAttributes – Describes the objectBehaviors – specify what object can do
Slide 5
Classes and Objects
Slide 6
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
Slide 7
Messages and Methods
Slide 8
Encapsulation and Information Hiding
Encapsulation combination of data and process into an entity
Information HidingOnly the information required to use a software module is published to the user
Reusability KeyUse an object by calling methods
Slide 9
Inheritance
Superclasses or general classes are at the top of a hierarchy of classesSubclasses or specific classes are at the bottomSubclasses inherit attributes and methods from classes higher in the hierarchy
Slide 10
Class Hierarchy
Slide 11
Inheritance
Slide 12
Polymorphism and Dynamic Binding
PolymorphismA message can be interpreted differently by different classes of objects
Dynamic BindingSometimes called late bindingDelays typing or choosing a method for an object until run-time
Static BindingType of object determined at compile time
Slide 13
Polymorphish & Encapsulation
Slide 14
The Unified Modeling Language
UML provides Common vocabulary of OO termsCommon notation of diagramming techniques
UML can be used to model any OO project
Slide 15
The Unified Modeling Language, Version 2.0
Structure DiagramsBehavior DiagramsExtension MechanismsDevelopers
Grady BoochIvar JacobsonJames Rumbaugh
Slide 16
Structure Diagram
Structure Diagrams – represent data and static relationshipsThey include
ClassObjectPackageDeploymentComponentComposite structure diagrams
Slide 17
Behavioral Diagram
Behavioral Diagrams – model dynamic behavior and dynamic relationships among objects in the systemUsed to model functional requirementsThey include
ActivityInteraction (Sequence, Communication, Interaction Overview, Timing)State Machines (Behavior, Protocol)Use-Case
Slide 18
UML 2.0 Diagram Summary
Slide 19
Structure Diagrams
Classrelationship between classes
ObjectRelationships between objects
PackageGroup UML elements together to form higher level constructs
Slide 20
Structure Diagrams Cont.
DeploymentShows the physical architecture and software components of system
ComponentPhysical relationships among software components
Composite StructureIllustrates internal structure of a class
Slide 21
Activity DiagramsActivity
Illustrates business workflows
SequenceTime-based ordering Behavior of objects activities in a use case
CommunicationCommunication among a set of collaborating objects of an activity
Interaction Overview TimingOverview of flow of control of a process
Slide 22
State Machines
Behavioral State MachineExamines behavior of one class
Protocol State MachineShows dependencies of different interfaces of a class
Use-CaseCaptures business requirementsIllustrates interaction between system and environment
Slide 23
Use Case Diagrams
Captures Business requirementsIllustrates interaction between a system and its environment
Includes end userAny external system that interacts with its information system
Documents and clarifies requirements of system being modeled
Slide 24
Benefits of the Object Approach
Slide 25
Basic Characteristics of Object Oriented Systems
Identifying business valueAnalyze feasibilityDevelop workplanStaff the projectControl and direct projectRequirements determinationFunctional modelingStructural modelingBehavioral modelingMoving on to design
Slide 26
UML Summary
Class and method designData management layer designHuman computer interaction layer designPhysical architecture layer designConstructionInstallationOperations and support
Slide 27
Summary
Basic characteristics of an object oriented systemUnified modeling systemObject oriented Systems Analysis and Design