Scribd
Upload
8 views4 pages

Presentation 01

Design patterns in software engineering are general repeatable solutions to common design problems, enhancing development speed and code readability. They are categorized into creational, behavioral, and structural patterns, each addressing different aspects of software design. Utilizing design patterns promotes reusability, maintainability, and best practices, facilitating better collaboration among developers.

Uploaded by

Asma Rehman
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views4 pages

Presentation 01

Design patterns in software engineering are general repeatable solutions to common design problems, enhancing development speed and code readability. They are categorized into creational, behavioral, and structural patterns, each addressing different aspects of software design. Utilizing design patterns promotes reusability, maintainability, and best practices, facilitating better collaboration among developers.

Uploaded by

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

Submitted by:

Group 10(adnan,asghar,awais,saqlain,rauf)
Submitted to:
Mam Asma
Topic:
Design Patterns
MNS university of agriculture Multan
Patterns
In software engineering a design pattern is a general repeatable solution to a commonly occurring
problem in software design. A design pattern isn't a finished design that can be transformed directly into
code. It is a description or template for how to solve a problem that can be used in many different
situations.

Uses of Design Patterns


Design patterns can speed up the development process by providing tested, proven development
paradigms. Effective software design requires considering issues that may not become visible until later
in the implementation. Reusing design patterns helps to prevent subtle issues that can cause major
problems and improves code readability for coders and architects familiar with the patterns.
Often, people only understand how to apply certain software design techniques to certain problems. These
techniques are difficult to apply to a broader range of problems. Design patterns provide general
solutions, documented in a format that doesn't require specifics tied to a particular problem.

Creational design patterns


These design patterns are all about class instantiation. This pattern can be further divided into class-
creation patterns and object-creational patterns. While class-creation patterns use inheritance effectively
in the instantiation process, object-creation patterns use delegation effectively to get the job done.
Example of Abstract Factory
Abstract Factory
Creates an instance of several families of classes.
Builder
Separates object construction from its representation.
Factory Method
Creates an instance of several derived classes.
Object Pool
Avoid expensive acquisition and release of resources by recycling objects that are no longer in use.
Prototype
A fully initialized instance to be copied or cloned.
Singleton
A class of which only a single instance can exist.

Behavioral design patterns


These design patterns are all about Class's objects communication. Behavioral patterns are those patterns
that are most specifically concerned with communication between objects.
Chain of responsibility
A way of passing a request between a chain of objects.
Command
Encapsulate a command request as an object.
Interpreter
A way to include language elements in a program.
Iterator
Sequentially access the elements of a collection.
Mediator
Defines simplified communication between classes.
Memento
Capture and restore an object's internal state.
Null Object
Designed to act as a default value of an object.
Observer
A way of notifying change to a number of classes.
State
Alter an object's behavior when its state changes.
Strategy
Encapsulates an algorithm inside a class.
Template method
Defer the exact steps of an algorithm to a subclass.
Visitor
Defines a new operation to a class without change.

Structural design patterns


These design patterns are all about Class and Object composition. Structural class-creation patterns use
inheritance to compose interfaces. Structural object-patterns define ways to compose objects to obtain
new functionality.
Adapter
Match interfaces of different classes.
Bridge
Separates an object’s interface from its implementation.
Composite
A tree structure of simple and composite objects.
Decorator
Add responsibilities to objects dynamically.
Facade
A single class that represents an entire subsystem.
Flyweight
A fine-grained instance used for efficient sharing.
Private Class Data
Restricts accessor/mutator access.
Proxy
An object representing another object.
Design patterns are crucial in software development as they provide proven solutions to common
problems, enhancing the quality, maintainability, and scalability of software. Here’s why they are
important:

1. Promote Reusability
Design patterns offer templates that can be reused across multiple projects, reducing development time
and effort.

2. Enhance Code Readability


By following well-documented and widely recognized patterns, developers can produce code that is easier
for others to understand and maintain.
3. Improve Maintainability
Patterns create a structure in the code, making it easier to locate, debug, and extend functionality.

4. Encourage Best Practices


They embody best practices in software design, helping developers to avoid common pitfalls and
inefficiencies.

5. Facilitate Collaboration
When teams use standard design patterns, communication and collaboration become smoother as
everyone speaks a common "design language."

Conclusion
Design patterns are essential in modern backend development as they provide a structured approach to
solving common problems. The use of design patterns offers numerous advantages, including code
reusability, scalability, maintainability, reduced errors, and improved performance.

You might also like