0% found this document useful (0 votes)
117 views17 pages

Biteranta - John Vincent - 2nd Year Bsit 1

The document discusses several types of UML diagrams used for object-oriented programming: activity diagrams model system flows; use case diagrams show system functionality and actors; interaction overview diagrams represent interaction diagrams with nodes; state machine diagrams visualize object states; sequence diagrams show object interactions over time; class diagrams conceptualize system classes; object diagrams focus on object attributes and relationships; and component diagrams model physical system components.

Uploaded by

api-619829083
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
117 views17 pages

Biteranta - John Vincent - 2nd Year Bsit 1

The document discusses several types of UML diagrams used for object-oriented programming: activity diagrams model system flows; use case diagrams show system functionality and actors; interaction overview diagrams represent interaction diagrams with nodes; state machine diagrams visualize object states; sequence diagrams show object interactions over time; class diagrams conceptualize system classes; object diagrams focus on object attributes and relationships; and component diagrams model physical system components.

Uploaded by

api-619829083
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

Object Oriented Programming

Types of Diagrams
Activity Diagram

 Activity diagram is another important behavioral diagram in UML


diagram to describe dynamic aspects of the system. Activity
diagram is essentially an advanced version of flow chart that
modeling the flow from one activity to another activity. 
What is Activity Diagram? (visual-paradigm.com)
Case Diagram

 An use case diagram can be explained as a behavioral or dynamic


diagram that models a system’s functionality by the use of use cases
and actors. The use cases are the set of services, functions which the
system needs to execute the functionality of the system. A “system” in
this context is something that is being operated or developed, for
instance, a website. 
Free Editable Use Case Diagram Examples | EdrawMax Online
Interaction Overview Diagram

 An interaction overview diagram is a form of activity diagram in which the


nodes represent interaction diagrams. Interaction diagrams can include
sequence, communication, interaction overview and timing diagrams. Most of
the notation for interaction overview diagrams is the same for activity diagrams.
For example, initial, final, decision, merge, fork and join nodes are all the same.
However, interaction overview diagrams introduce two new elements:
interaction occurrences and interaction elements. 
Interaction Overview Diagram - UML 2 Tutorial | Sparx Systems
State Machine UML diagram

 A state machine is any device that stores the status of an object at a given time
and can change status or cause other actions based on the input it receives. States
refer to the different combinations of information that an object can hold, not
how the object behaves. In order to understand the different states of an object,
you might want to visualize all of the possible states and show how an object gets
to each state, and you can do so with a UML state diagram. 
The state machine of the Simplicity Device: UML state diagram  | Download Scientifi
c Diagram (researchgate.net)
Sequence UML Diagram

 UML Sequence Diagram can be created using Concept Draw DIAGRAM diagramming
software contains rich examples and template. Concept Draw is perfect for software
designers and software developers who need to draw UML Sequence Diagrams.

 The UML sequence diagram is used primarily to show the interactions between objects in
the sequential order that those interactions occur. Much like the class diagram, developers
typically think sequence diagram were meant exclusively for them. One of the primary uses
of sequence diagrams is in the transition from requirements expressed as use cases to the
next and more formal level of refinement. UML Sequence Diagrams to Print | 101 Diagrams
Class Diagram

 oppose you have to design a system. Before implementating a bunch of classes,


you’ll want to have a conceptual understanding of the system — that is, what
classes do I need? What functionality and information will these classes have?
How do they interact with one another? Who can see these classes? And so on.

 That’s where class diagrams come in. Class diagrams are a neat way of
visualizing the classes in your system before you actually start coding them up.
They’re a static representation of your system structure.
UML Class Diagrams Tutorial, Step by Step | by Salma | Medium
Object Diagram

 An object diagram focuses on the attributes of a set of objects and


how those objects relate to each other. For instance, in this object
diagram below, all three bank accounts tie back to the bank itself. The
class titles show the type of accounts (savings, checking, and credit
card) that a given customer could have with this particular bank. The
class attributes are different for each account type. 
Object Diagram Tutorial | Lucidchart
Component Diagram
 component diagrams are used in modeling the physical aspects of
object-oriented systems that are used for visualizing, specifying, and
documenting component-based systems and also for constructing
executable systems through forward and reverse engineering.
Component diagrams are essentially class diagrams that focus on a
system's components that often used to model the static implementation
view of a system.What is Component Diagram? (visual-paradigm.com)

You might also like