FORMATIVE ASSESSMENT-02

20CS5103-OBJECT ORIENTED ANALYSIS AND DESIGN

C0-3 DEPLOYMENT DIAGRAM

C0-4 DESIGN PATTERN

C0-5 OBJECT ORIENTED MODELLING

SUBMITTED BY...
ARAVINTH M.D
811722104013
Deployment Diagram in
Object-Oriented
Analysis and Design

Deployment diagrams are essential for visualizing the physical architecture of a

software system, showing how software components are distributed across hardware
nodes.
Introduction to Deployment
Diagrams Diagrams
Deployment diagrams are a type of UML diagram used in software engineering to represent the
physical
deployment of software components and their relationships to hardware nodes.

Visual Representation Communication Pathways

They provide a clear and concise overview Deployment diagrams illustrate the
of overview of how a system is physically connections and dependencies between
implemented, showing the layout of between software components and
hardware and software components. hardware hardware nodes, including
communication communication paths and
network configurations.

System Architecture
They help developers understand the overall structure of a system, enabling them to make
informed decisions about resource allocation, performance optimization, and system
scalability.
Elements of a Deployment Diagram

Deployment diagrams consist of several key elements that help to represent the physical
architecture of a software system.

1 Nodes 2 Components
These represent physical hardware Components represent software
components, such as servers, entities, such as applications, libraries,
workstations, or network devices. or databases.

3 Artifacts 4 Connections
Artifacts are physical representations of Connections show the relationships
representations of software relationships between nodes and
components, such as executable files, components, including communication
files, libraries, or configuration files. communication paths, dependencies,
dependencies, and network
configurations.
Benefits of Using Deployment
Diagrams
Deployment diagrams offer several advantages for software development teams.

Improved Communication Enhanced Understanding Reduced Errors

They facilitate better communication among They provide a clear visual representation of By visualizing the deployment, they help
among stakeholders, including developers, representation of the system architecture, prevent errors and inconsistencies during
developers, architects, and project managers. architecture, leading to a deeper the implementation phase.
managers. understanding of its physical
implementation. implementation.
Identifying Hardware and
Software Nodes
The first step in creating a deployment diagram is to identify the hardware and software nodes
that
will be involved in the system.

Hardware
Servers, workstations, network devices, and other physical components that host
software components.

Software
Applications, libraries, databases, and other software entities that are deployed
on
hardware nodes.

Dependencies
Identify the relationships between hardware and software components,
including
communication paths and dependencies.
Mapping Software
Components to Hardware
Nodes
Once you have identified the nodes, you need to map software components to
specific hardware nodes.

Node Software Component

Server A Web Application

Server B Database

Workstation C Client Application

Representing Communication Paths
and Dependencies
Deployment diagrams also represent communication paths and dependencies between software components and
hardware nodes.

Network Communication
Show how software components on different nodes communicate over the network.

Data Flow
Represent the direction of data flow between components, including data transfer protocols.

Dependencies
Highlight dependencies between components, such as shared resources or communication protocols.
Best Practices and Practical
Considerations
There are several best practices and practical considerations to keep in mind when creating deployment
diagrams.

Clarity 1
Make sure the diagram is clear, concise, and easy to
understand.

2 Accuracy
The diagram should accurately reflect the physical deployment of
the system.
Scalability 3
Consider the scalability of the system and how the diagram can be
updated
be updated as the system evolves.
Conclusion and Key Takeaways
Deployment diagrams are a valuable tool for visualizing the physical architecture of software
systems.

Visual Representation Effective Communication

They provide a clear and concise overview of how software components They facilitate communication between stakeholders and help to
are components are distributed across hardware nodes. ensure ensure everyone is on the same page.
Design Patterns in
Object-Oriented
Analysis and Design
Design patterns provide reusable solutions to common software
design problems. They offer a shared vocabulary and best
practices for building robust and maintainable code.
Introduction to Design Patterns
1 Conceptual Frameworks 2 Proven Solutions
Design patterns act as These patterns have
templates for solving been tested and
recurring design validated in real- world
challenges. projects.

3 Improved Communication
Design patterns foster collaboration and understanding
among developers.
Creational Patterns: Singleton, Factory, Builder
Singleton Factory Builder

Ensures only one instance of a Provides an interface for Separates the construction of a
class exists. creating objects without complex object from its
specifying their concrete representation.
class.
Structural Patterns: Adapter,
Decorator, Facade
1 Adapter
Allows classes with incompatible interfaces
to work together.

2 Decorator
Dynamically adds responsibilities to an
object.

3 Facade
Provides a simplified interface to a complex
subsystem.
Behavioral Patterns: Observer,
Strategy, State
Observer
Defines a one-to-many dependency between
objects.

Strategy
Defines a family of algorithms and encapsulates
each one.

State
Allows an object to alter its behavior when its
internal state changes.
Design Patterns in Software Design
Pattern Use Case

Singleton Database connection, configuration manager

Factory Creating objects based on user input

Adapter Integrating third-party libraries

Benefits of Using Design
Patterns
Code Reusability Improved Maintainability
Patterns promote code Patterns simplify code
reuse, reducing structure, making it easier to
redundancy and understand and modify.
development time.

Enhanced Collaboration
Patterns establish a shared language, facilitating
effective communication.
Applying Design Patterns in Real-World Scenarios

E-Commerce Networking Game Development

Used in managing shopping carts, Implemented in network Used in game logic, AI, and user
user profiles, and order processing. communication protocols, socket interface design.
management, and distributed
systems.
Conclusion and Key Takeaways
Design patterns are valuable tools for software development. They
promote code quality, maintainability, and collaboration. By
understanding and applying these patterns, you can build more
effective and efficient software solutions.
Object-Oriented
Analysis and Design
Object-oriented analysis and design (OOAD) is a software
engineering approach that focuses on modeling real-world entities
as objects. It involves breaking down a problem into smaller, self-
contained units, called objects, which interact with each other to
achieve a common goal.
Fundamentals of Object-
Oriented Programming
1 Abstraction 2 Encapsulation
Abstraction is the process Encapsulation combines
of simplifying complex data and methods that
reality by focusing on operate on that data into
essential characteristics. a single unit.

3 Inheritance 4 Polymorphism
Inheritance allows for Polymorphism enables
code reuse and creating objects of different
hierarchical classes to be treated as
relationships between objects of a common
classes. type.
Classes, Objects, and Inheritance
Classes Objects Inheritance

A class is a blueprint or template Objects are instances of classes. Inheritance is a mechanism that
for creating objects. It defines the They represent real-world entities allows one class (subclass) to
attributes (data members) and with specific values for their inherit properties and methods
methods (functions) that objects of attributes. from another class (superclass).
that class will have.
Encapsulation and Information
Information Hiding
Encapsulation Information Hiding
Encapsulation bundles data Information hiding restricts
and methods that operate access to data members
on that data into a single from outside the class,
unit. promoting modularity and
maintainability.
Polymorphism and Dynamic
Binding
Polymorphism
Polymorphism allows objects of different classes
to be treated as objects of a common type.

Dynamic Binding
Dynamic binding resolves method calls at runtime,
allowing for flexible behavior based on the actual
object type.
Unified Modeling Language
(UML)
Use Case Diagram Represents interactions
between actors and the
system.

Class Diagram Defines classes,

attributes, methods, and
relationships between
them.

Sequence Diagram Illustrates interactions

between objects over time.
Object-Oriented Design Principles

Single Responsibility Principle Open/Closed Principle

Each class should have a single, Software entities should be open
well- for
defined responsibility. extension but closed for
modification.

Liskov Substitution Principle Interface Segregation Principle

Subtypes should be Clients should not be forced to
substitutable for their base depend on methods they do not
types without altering the use.
correctness of the program.
Iterative and Incremental Development
Planning 1
Define requirements and scope of the
project.

2 Design
Create a high-level design of the
system.
Implementation 3
Develop code for the
system.
4 Testing
Verify that the system meets the
requirements.
Deployment 5
Release the software to
users.
Conclusion and Best Practices
Object-oriented analysis and design provides a powerful
framework for building complex and maintainable software
systems. By following best practices and adopting a
collaborative approach, development teams can leverage the
benefits of OOAD to create effective and efficient software
solutions.
Thank you!!