SlideShare a Scribd company logo
Object Oriented Design and Analysis
Building Blocks of UML
Object Oriented Design and Analysis
OOAD with UML
Building a
house
Design and
layout
Blueprint
Actual
construction
Building software
OOAD
UML
Coding
Object Oriented Design and Analysis
A conceptual model of the UML
To understand the UML, you need to form a conceptual
model of the language, and this requires learning
three major elements:
 The UML’s basic building blocks.
 The rules that dictate how these building blocks put
together.
 Some mechanisms that apply throughout the UML.
Object Oriented Design and Analysis
Building Blocks of UML
• Things – abstractions that are first class citizen
in a model
• Relationships - tie things together
• Diagrams - group interesting collections of
things
Object Oriented Design and Analysis
Things in the UML
There are four kinds of things in the UML:
 Structural things
 Behavioral things
 Grouping things
 Annotational things
Object Oriented Design and Analysis
Structural Things
• Static part of a model, representing elements
that are either conceptual or physical
– Classes
– Interfaces
– Collaborations
– Use cases
– Active classes
– Components
– Nodes
Object Oriented Design and Analysis
• class
– a class is a description of a set of objects that share the same attributes,
operations, relationships, and semantics
– A class implements one or more interfaces.
• interface
– a collection of operations that specify a service of a class or component
– describes the externally visible behavior of that element
– defines a set of operation specifications but never a set of operation
implementations
– attached to class or component that realizes the interface
• Collaboration
– defines an interaction and is a society of roles and other elements that work
together to provide some cooperative behavior
– Collaborations have structural, as well as behavioral dimensions
– A given class may participate in several collaborations
– therefore represent the implementation of patterns that make up a system
Object Oriented Design and Analysis
Figure 1: Classes
Figure 2: Interfaces
Class Name
Attributes
Operations
Figure 3: Collaborations
Object Oriented Design and Analysis
• use case - a description of set of sequence of actions that a system
performs that yields an observable result of value to a particular
actor. A use case is used to structure the behavioral things in a
model. A use case is realized by a collaboration.
• active class - a class whose objects own one or more processes or
threads and therefore can initiate control activity. An active class is
just like a class except that its objects represent elements whose
behavior is concurrent with other elements.
• component - a physical and replaceable part of a system that
conforms to and provides the realization of a set of interfaces.
Represents the physical packaging of otherwise logical elements,
such as classes, interfaces, and collaborations.
• node - a physical element that exists at run time and represents a
computational resource, having at least some memory and, often,
processing capability. A set of components may reside on a node
and may also migrate from node to node.
Object Oriented Design and Analysis
Figure 3: Use Cases
Figure 4: Active Classes
Figure 5: Components Figure 6: Nodes
Object Oriented Design and Analysis
Behavioral Things
• Behavioral things are the dynamic parts of UML
models.
• These are the verbs of a model, representing
behavior over time and space.
• Two primary kinds of behavioral things.
– Interaction (exchange of set of messages among a set of
objects)(includes message, links, action sequence)
– State Machine (specifies the sequences of states an object or an
interaction goes through during its lifetime in response to
events, together with its responses to those events.)(includes
states, transitions, events, activities)
* Shown in the figure 7 and 8
Object Oriented Design and Analysis
Grouping Things
• Grouping things are the organizational parts
of UML models. These are the boxes into
which a model can be decomposed.
• There is one primary kind of grouping.
– Packages(mechanism for organizing elements
into groups) (a package is purely conceptual
meaning that it exists only at development time)
* Shown in the figure 9
Object Oriented Design and Analysis
Annotational Things
• Annotational things are the explanatory parts
of UML models. These are the comments you
may apply to describe, illuminate, and remark
about any element in a model.
• There is one primary kind of annotational
things.
– Note (a symbol for rendering constraints and comments
attached to an element or a collection of elements)
* Shown in the figure 10
Object Oriented Design and Analysis
Figure 7: Messages
Figure 8: States
Figure 9: Packages
Figure 10: Notes
Object Oriented Design and Analysis
Relationships in the UML
Object Oriented Design and Analysis
Relationships in the UML
• There are four kinds of relationships in the UML:
1. Dependency (a semantic relationship between two things in
which a change to one thing may affect the semantics of the other
thing)
2. Association (a structural relationship that describes a set of links, a
link being a connection among objects)
3. Generalization (a specialization / generalization relationship in
which objects of the specialized element (the child) are substitutable
for objects of the generalized element (the parent))
4. Realization (a semantic relationship between classifiers, wherein
one classifier specifies a contract that another classifier guarantees to
carry out) (between interfaces and the classes or components and
between use cases and the collaborations)
Object Oriented Design and Analysis
Relationships in the UML
1. Dependencies: rendered as a
dashed line, possibly directed, and
occasionally including a label
2. Associations: rendered as a solid line,
possibly directed, occasionally including a label,
and often containing other adornments, such as
multiplicity and role names
3. Generalizations: rendered as a
solid line with a hollow arrowhead pointing to
the parent
4. Realization: rendered as a cross
between a generalization and a dependency
relationship
Object Oriented Design and Analysis
Object Oriented Design and Analysis
Object Oriented Design and Analysis
Diagrams in the UML
• graphical presentation of a set of elements,
rendered as a connected graph of vertices
(things) and arcs (relationships).
• a projection into a system
• The same element may appear in all diagrams,
only a few diagrams (the most common case), or
in no diagrams at all (a very rare case)
Object Oriented Design and Analysis
Diagrams in the UML
1. Class diagram
2. Object diagram
3. Use case diagram
4. Sequence diagram
5. Collaboration diagram
6. Statechart diagram
7. Activity diagram
8. Component diagram
9. Deployment diagram
Interaction
diagrams
Object Oriented Design and Analysis
1. Class Diagram
• A class diagram shows a set of classes, interfaces,
and collaborations and their relationships.
• most common diagram found in modeling object-
oriented systems.
• address the static design view of a system.
• Class diagrams that include active classes address the
static process view of a system.
Object Oriented Design and Analysis
Object Oriented Design and Analysis
2. Object Diagram
• An object diagram shows a set of objects and
their relationships.
• Object diagrams represent static snapshots of
instances of the things found in class diagrams.
• address the static design view or static process
view of a system as do class diagrams, but from
the perspective of real or prototypical cases.
Object Oriented Design and Analysis
Object Oriented Design and Analysis
3. Use Case Diagram
• A use case diagram shows a set of use cases
and actors (a special kind of class) and their
relationships.
• address the static use case view of a system.
• especially important in organizing and
modeling the behaviors of a system.
Object Oriented Design and Analysis
Interaction Diagrams
• Both sequence diagrams and collaboration
diagrams are kinds of interaction diagrams.
• Arc shows an interaction, consisting of a set of
objects and their relationships, including the
messages that may be dispatched among
them.
• Interaction diagrams address the dynamic
view of a system
Object Oriented Design and Analysis
Object Oriented Design and Analysis
4. Sequence Diagram
• A sequence diagram is an interaction diagram
that emphasizes the time-ordering of messages.
Object Oriented Design and Analysis
5. Collaboration Diagram
• collaboration diagram is an interaction diagram
that emphasizes the structural organization of
the objects that send and receive messages.
• Note: Sequence diagrams and collaboration
diagrams are isomorphic, meaning that you can
take one and transform it into the other.
Object Oriented Design and Analysis
6. Statechart Diagram
• A statechart diagram shows a state machine,
consisting of states, transitions, events and
activities.
• Statechart diagrams address the dynamic view of a
system.
• especially important in modeling the behavior of an
interface, class, or collaboration and emphasize the
event-ordered behavior of an object, which is
especially useful in modeling reactive systems.
Object Oriented Design and Analysis
Object Oriented Design and Analysis
7. Activity Diagram
• An activity diagram is a special kind of a
statechart diagram that shows the flow from
activity to activity within a system.
• Activity diagrams address the dynamic view of
a system.
• They are especially important in modeling the
function of a system and emphasize the flow
of control among objects
Object Oriented Design and Analysis
Object Oriented Design and Analysis
8. Component Diagram
• A component diagram shows the organizations and
dependencies among a set of components.
• Component diagrams address the static
implementation view of a system.
• They are related to class diagrams in that a
component typically maps to one or more classes,
interfaces, or collaborations.
Object Oriented Design and Analysis
Object Oriented Design and Analysis
9. Deployment Diagram
• A deployment diagram shows the configuration of
run-time processing nodes and the components that
live on them.
• Deployment diagrams address the static deployment
view of an architecture.
• They are related to component diagrams in that a
node typically encloses one or more components.
Object Oriented Design and Analysis

More Related Content

PPTX
Environmental movement in india
PPTX
Mining Data Streams
PPTX
Overview of UML Diagrams
PPTX
Database connectivity in python
PPTX
Hashing
PPTX
Python Programming Full Course || Beginner to Intermediate || Bangla (বাংলা) ...
PPTX
Basic Structural Modeling
PPT
Use Case Diagram
Environmental movement in india
Mining Data Streams
Overview of UML Diagrams
Database connectivity in python
Hashing
Python Programming Full Course || Beginner to Intermediate || Bangla (বাংলা) ...
Basic Structural Modeling
Use Case Diagram

What's hot (20)

PPTX
Object oriented modeling and design
PPT
UML Diagrams
PPT
State Diagrams
PPTX
Cohesion and coupling
PPT
Coupling and cohesion
PPT
PPTX
Software development life cycle (SDLC)
PPTX
PPT
PDF
Collaboration diagram- UML diagram
PPTX
Structural modeling and analysis
PPT
Uml diagrams
PPTX
Object oriented methodologies
PPTX
1. introduction to uml
DOCX
Evolving role of Software,Legacy software,CASE tools,Process Models,CMMI
PPTX
System testing
PPTX
Software Development Life Cycle
PPT
Software Architecture
PPTX
Data Designs (Software Engg.)
PPTX
Software Design Concepts
Object oriented modeling and design
UML Diagrams
State Diagrams
Cohesion and coupling
Coupling and cohesion
Software development life cycle (SDLC)
Collaboration diagram- UML diagram
Structural modeling and analysis
Uml diagrams
Object oriented methodologies
1. introduction to uml
Evolving role of Software,Legacy software,CASE tools,Process Models,CMMI
System testing
Software Development Life Cycle
Software Architecture
Data Designs (Software Engg.)
Software Design Concepts
Ad

Viewers also liked (20)

PPT
Object Oriented Analysis and Design
PPT
OOAD UNIT I UML DIAGRAMS
PPT
Uml class Diagram
PPT
UML- Unified Modeling Language
PPTX
Lecture#02, building blocks of uml ASE
PPT
M03 1 Structuraldiagrams
PPT
Ooad
PPTX
Ooad unit – 1 introduction
PPT
Uml - An Overview
PPT
Uml class-diagram
PPTX
Structured Vs, Object Oriented Analysis and Design
PPTX
Understanding unified modelling language
PPT
PPT
Image processing techniques 1
PDF
Planning-Based Approach for Automating Sequence Diagram Generation
PPT
08 class and sequence diagrams
DOCX
Uml Common Mechanism
DOC
Object Oriented Analysis And Design
Object Oriented Analysis and Design
OOAD UNIT I UML DIAGRAMS
Uml class Diagram
UML- Unified Modeling Language
Lecture#02, building blocks of uml ASE
M03 1 Structuraldiagrams
Ooad
Ooad unit – 1 introduction
Uml - An Overview
Uml class-diagram
Structured Vs, Object Oriented Analysis and Design
Understanding unified modelling language
Image processing techniques 1
Planning-Based Approach for Automating Sequence Diagram Generation
08 class and sequence diagrams
Uml Common Mechanism
Object Oriented Analysis And Design
Ad

Similar to UML diagrams and symbols (20)

PPTX
objects and design in unified modelling language
PPTX
UNIT-3 Design Using UML (1).pptx
PPTX
UNIT-3 Design Using UML_Design_of_UML.pptx
PDF
UML-Advanced Software Engineering
DOC
Ooad lab manual
PPTX
Introduction to unified language modeling.pptx
PPTX
Unified Modelling Languageeeeeeeeeeeeeee
PDF
OBJECT ORIENTED CONCEPTS,UML DIAGRAMS,DFD
PPTX
Unified Modeling Language
PDF
PPTX
PPTX
Capturing System Behaviour
PPT
Oomd unit1
PPTX
R1x g02 enterprise architecture i
PPTX
UML Diagrams.pptxUML DiagramsUML DiagramsUML Diagrams
PPTX
Chapter 6 Object Modeling .pptxInformation Technology Project Management
PPTX
20CS011.pptx
PPT
fdocuments.in_unit-2-ooad.ppt
PPT
oomd-unit-i-cgpa.ppt
PPTX
unit-1 &2 important questions to be noted
objects and design in unified modelling language
UNIT-3 Design Using UML (1).pptx
UNIT-3 Design Using UML_Design_of_UML.pptx
UML-Advanced Software Engineering
Ooad lab manual
Introduction to unified language modeling.pptx
Unified Modelling Languageeeeeeeeeeeeeee
OBJECT ORIENTED CONCEPTS,UML DIAGRAMS,DFD
Unified Modeling Language
Capturing System Behaviour
Oomd unit1
R1x g02 enterprise architecture i
UML Diagrams.pptxUML DiagramsUML DiagramsUML Diagrams
Chapter 6 Object Modeling .pptxInformation Technology Project Management
20CS011.pptx
fdocuments.in_unit-2-ooad.ppt
oomd-unit-i-cgpa.ppt
unit-1 &2 important questions to be noted

More from Kumar (20)

PPT
Graphics devices
PPT
Fill area algorithms
PDF
region-filling
PDF
Bresenham derivation
PPT
Bresenham circles and polygons derication
PPTX
Introductionto xslt
PPTX
Extracting data from xml
PPTX
Xml basics
PPTX
XML Schema
PPTX
Publishing xml
PPTX
DTD
PPTX
Applying xml
PPTX
Introduction to XML
PDF
How to deploy a j2ee application
PDF
JNDI, JMS, JPA, XML
PDF
EJB Fundmentals
PDF
JSP and struts programming
PDF
java servlet and servlet programming
PDF
Introduction to JDBC and JDBC Drivers
PDF
Introduction to J2EE
Graphics devices
Fill area algorithms
region-filling
Bresenham derivation
Bresenham circles and polygons derication
Introductionto xslt
Extracting data from xml
Xml basics
XML Schema
Publishing xml
DTD
Applying xml
Introduction to XML
How to deploy a j2ee application
JNDI, JMS, JPA, XML
EJB Fundmentals
JSP and struts programming
java servlet and servlet programming
Introduction to JDBC and JDBC Drivers
Introduction to J2EE

Recently uploaded (20)

PDF
737-MAX_SRG.pdf student reference guides
PDF
Unit I ESSENTIAL OF DIGITAL MARKETING.pdf
PDF
R24 SURVEYING LAB MANUAL for civil enggi
PDF
22EC502-MICROCONTROLLER AND INTERFACING-8051 MICROCONTROLLER.pdf
PPT
Occupational Health and Safety Management System
PPTX
AUTOMOTIVE ENGINE MANAGEMENT (MECHATRONICS).pptx
PPTX
Nature of X-rays, X- Ray Equipment, Fluoroscopy
PPTX
Module 8- Technological and Communication Skills.pptx
PDF
Categorization of Factors Affecting Classification Algorithms Selection
PDF
Artificial Superintelligence (ASI) Alliance Vision Paper.pdf
PPTX
introduction to high performance computing
PDF
Design Guidelines and solutions for Plastics parts
PDF
SMART SIGNAL TIMING FOR URBAN INTERSECTIONS USING REAL-TIME VEHICLE DETECTI...
PDF
BIO-INSPIRED HORMONAL MODULATION AND ADAPTIVE ORCHESTRATION IN S-AI-GPT
PPTX
Safety Seminar civil to be ensured for safe working.
PDF
III.4.1.2_The_Space_Environment.p pdffdf
PPTX
communication and presentation skills 01
PDF
PREDICTION OF DIABETES FROM ELECTRONIC HEALTH RECORDS
PDF
BIO-INSPIRED ARCHITECTURE FOR PARSIMONIOUS CONVERSATIONAL INTELLIGENCE : THE ...
PDF
Exploratory_Data_Analysis_Fundamentals.pdf
737-MAX_SRG.pdf student reference guides
Unit I ESSENTIAL OF DIGITAL MARKETING.pdf
R24 SURVEYING LAB MANUAL for civil enggi
22EC502-MICROCONTROLLER AND INTERFACING-8051 MICROCONTROLLER.pdf
Occupational Health and Safety Management System
AUTOMOTIVE ENGINE MANAGEMENT (MECHATRONICS).pptx
Nature of X-rays, X- Ray Equipment, Fluoroscopy
Module 8- Technological and Communication Skills.pptx
Categorization of Factors Affecting Classification Algorithms Selection
Artificial Superintelligence (ASI) Alliance Vision Paper.pdf
introduction to high performance computing
Design Guidelines and solutions for Plastics parts
SMART SIGNAL TIMING FOR URBAN INTERSECTIONS USING REAL-TIME VEHICLE DETECTI...
BIO-INSPIRED HORMONAL MODULATION AND ADAPTIVE ORCHESTRATION IN S-AI-GPT
Safety Seminar civil to be ensured for safe working.
III.4.1.2_The_Space_Environment.p pdffdf
communication and presentation skills 01
PREDICTION OF DIABETES FROM ELECTRONIC HEALTH RECORDS
BIO-INSPIRED ARCHITECTURE FOR PARSIMONIOUS CONVERSATIONAL INTELLIGENCE : THE ...
Exploratory_Data_Analysis_Fundamentals.pdf

UML diagrams and symbols

  • 1. Object Oriented Design and Analysis Building Blocks of UML
  • 2. Object Oriented Design and Analysis OOAD with UML Building a house Design and layout Blueprint Actual construction Building software OOAD UML Coding
  • 3. Object Oriented Design and Analysis A conceptual model of the UML To understand the UML, you need to form a conceptual model of the language, and this requires learning three major elements:  The UML’s basic building blocks.  The rules that dictate how these building blocks put together.  Some mechanisms that apply throughout the UML.
  • 4. Object Oriented Design and Analysis Building Blocks of UML • Things – abstractions that are first class citizen in a model • Relationships - tie things together • Diagrams - group interesting collections of things
  • 5. Object Oriented Design and Analysis Things in the UML There are four kinds of things in the UML:  Structural things  Behavioral things  Grouping things  Annotational things
  • 6. Object Oriented Design and Analysis Structural Things • Static part of a model, representing elements that are either conceptual or physical – Classes – Interfaces – Collaborations – Use cases – Active classes – Components – Nodes
  • 7. Object Oriented Design and Analysis • class – a class is a description of a set of objects that share the same attributes, operations, relationships, and semantics – A class implements one or more interfaces. • interface – a collection of operations that specify a service of a class or component – describes the externally visible behavior of that element – defines a set of operation specifications but never a set of operation implementations – attached to class or component that realizes the interface • Collaboration – defines an interaction and is a society of roles and other elements that work together to provide some cooperative behavior – Collaborations have structural, as well as behavioral dimensions – A given class may participate in several collaborations – therefore represent the implementation of patterns that make up a system
  • 8. Object Oriented Design and Analysis Figure 1: Classes Figure 2: Interfaces Class Name Attributes Operations Figure 3: Collaborations
  • 9. Object Oriented Design and Analysis • use case - a description of set of sequence of actions that a system performs that yields an observable result of value to a particular actor. A use case is used to structure the behavioral things in a model. A use case is realized by a collaboration. • active class - a class whose objects own one or more processes or threads and therefore can initiate control activity. An active class is just like a class except that its objects represent elements whose behavior is concurrent with other elements. • component - a physical and replaceable part of a system that conforms to and provides the realization of a set of interfaces. Represents the physical packaging of otherwise logical elements, such as classes, interfaces, and collaborations. • node - a physical element that exists at run time and represents a computational resource, having at least some memory and, often, processing capability. A set of components may reside on a node and may also migrate from node to node.
  • 10. Object Oriented Design and Analysis Figure 3: Use Cases Figure 4: Active Classes Figure 5: Components Figure 6: Nodes
  • 11. Object Oriented Design and Analysis Behavioral Things • Behavioral things are the dynamic parts of UML models. • These are the verbs of a model, representing behavior over time and space. • Two primary kinds of behavioral things. – Interaction (exchange of set of messages among a set of objects)(includes message, links, action sequence) – State Machine (specifies the sequences of states an object or an interaction goes through during its lifetime in response to events, together with its responses to those events.)(includes states, transitions, events, activities) * Shown in the figure 7 and 8
  • 12. Object Oriented Design and Analysis Grouping Things • Grouping things are the organizational parts of UML models. These are the boxes into which a model can be decomposed. • There is one primary kind of grouping. – Packages(mechanism for organizing elements into groups) (a package is purely conceptual meaning that it exists only at development time) * Shown in the figure 9
  • 13. Object Oriented Design and Analysis Annotational Things • Annotational things are the explanatory parts of UML models. These are the comments you may apply to describe, illuminate, and remark about any element in a model. • There is one primary kind of annotational things. – Note (a symbol for rendering constraints and comments attached to an element or a collection of elements) * Shown in the figure 10
  • 14. Object Oriented Design and Analysis Figure 7: Messages Figure 8: States Figure 9: Packages Figure 10: Notes
  • 15. Object Oriented Design and Analysis Relationships in the UML
  • 16. Object Oriented Design and Analysis Relationships in the UML • There are four kinds of relationships in the UML: 1. Dependency (a semantic relationship between two things in which a change to one thing may affect the semantics of the other thing) 2. Association (a structural relationship that describes a set of links, a link being a connection among objects) 3. Generalization (a specialization / generalization relationship in which objects of the specialized element (the child) are substitutable for objects of the generalized element (the parent)) 4. Realization (a semantic relationship between classifiers, wherein one classifier specifies a contract that another classifier guarantees to carry out) (between interfaces and the classes or components and between use cases and the collaborations)
  • 17. Object Oriented Design and Analysis Relationships in the UML 1. Dependencies: rendered as a dashed line, possibly directed, and occasionally including a label 2. Associations: rendered as a solid line, possibly directed, occasionally including a label, and often containing other adornments, such as multiplicity and role names 3. Generalizations: rendered as a solid line with a hollow arrowhead pointing to the parent 4. Realization: rendered as a cross between a generalization and a dependency relationship
  • 18. Object Oriented Design and Analysis
  • 19. Object Oriented Design and Analysis
  • 20. Object Oriented Design and Analysis Diagrams in the UML • graphical presentation of a set of elements, rendered as a connected graph of vertices (things) and arcs (relationships). • a projection into a system • The same element may appear in all diagrams, only a few diagrams (the most common case), or in no diagrams at all (a very rare case)
  • 21. Object Oriented Design and Analysis Diagrams in the UML 1. Class diagram 2. Object diagram 3. Use case diagram 4. Sequence diagram 5. Collaboration diagram 6. Statechart diagram 7. Activity diagram 8. Component diagram 9. Deployment diagram Interaction diagrams
  • 22. Object Oriented Design and Analysis 1. Class Diagram • A class diagram shows a set of classes, interfaces, and collaborations and their relationships. • most common diagram found in modeling object- oriented systems. • address the static design view of a system. • Class diagrams that include active classes address the static process view of a system.
  • 23. Object Oriented Design and Analysis
  • 24. Object Oriented Design and Analysis 2. Object Diagram • An object diagram shows a set of objects and their relationships. • Object diagrams represent static snapshots of instances of the things found in class diagrams. • address the static design view or static process view of a system as do class diagrams, but from the perspective of real or prototypical cases.
  • 25. Object Oriented Design and Analysis
  • 26. Object Oriented Design and Analysis 3. Use Case Diagram • A use case diagram shows a set of use cases and actors (a special kind of class) and their relationships. • address the static use case view of a system. • especially important in organizing and modeling the behaviors of a system.
  • 27. Object Oriented Design and Analysis Interaction Diagrams • Both sequence diagrams and collaboration diagrams are kinds of interaction diagrams. • Arc shows an interaction, consisting of a set of objects and their relationships, including the messages that may be dispatched among them. • Interaction diagrams address the dynamic view of a system
  • 28. Object Oriented Design and Analysis
  • 29. Object Oriented Design and Analysis 4. Sequence Diagram • A sequence diagram is an interaction diagram that emphasizes the time-ordering of messages.
  • 30. Object Oriented Design and Analysis 5. Collaboration Diagram • collaboration diagram is an interaction diagram that emphasizes the structural organization of the objects that send and receive messages. • Note: Sequence diagrams and collaboration diagrams are isomorphic, meaning that you can take one and transform it into the other.
  • 31. Object Oriented Design and Analysis 6. Statechart Diagram • A statechart diagram shows a state machine, consisting of states, transitions, events and activities. • Statechart diagrams address the dynamic view of a system. • especially important in modeling the behavior of an interface, class, or collaboration and emphasize the event-ordered behavior of an object, which is especially useful in modeling reactive systems.
  • 32. Object Oriented Design and Analysis
  • 33. Object Oriented Design and Analysis 7. Activity Diagram • An activity diagram is a special kind of a statechart diagram that shows the flow from activity to activity within a system. • Activity diagrams address the dynamic view of a system. • They are especially important in modeling the function of a system and emphasize the flow of control among objects
  • 34. Object Oriented Design and Analysis
  • 35. Object Oriented Design and Analysis 8. Component Diagram • A component diagram shows the organizations and dependencies among a set of components. • Component diagrams address the static implementation view of a system. • They are related to class diagrams in that a component typically maps to one or more classes, interfaces, or collaborations.
  • 36. Object Oriented Design and Analysis
  • 37. Object Oriented Design and Analysis 9. Deployment Diagram • A deployment diagram shows the configuration of run-time processing nodes and the components that live on them. • Deployment diagrams address the static deployment view of an architecture. • They are related to component diagrams in that a node typically encloses one or more components.
  • 38. Object Oriented Design and Analysis

Editor's Notes

  • #5: Abstraction – selective examination of certain aspects of a problem. The goal of abstraction is to isolate those aspects that are important and suppress those aspects that are unimportant. Abstraction must always be for some purpose, because the purpose determines what is and is not important. The purpose of abstraction is to limit the universe so that we can understand.