The document discusses software architecture and design. It defines software architecture as dealing with how software processes cooperate, serving as a blueprint and managing complexity through component communication. Software design is defined as dealing with the internal design of single processes and providing a design plan for system elements and their relationships. The document then discusses the goals of software architecture design, including bridging business and technical requirements, identifying architecture-impacting requirements, considering the effect of design decisions, and enabling flexibility.

2. SOFTWARE DESIGN
& ARCHITECTURE
PRESENTATION
ON

3. PresentedTo:
Mr Arslan Iftikhar
Presented By :
Haider Ali

4. Software Architecture typically refers to
the bigger structures of a software
system, and it deals with how multiple
software processes cooperate to carry
out their tasks.
Software Architecture

5. Architecture serves as a blueprint for a
system. It provides an abstraction to
manage the system complexity and
establish a communication and
coordination mechanism among
components.

7. Software Design refers to
the smaller structures and
it deals with the internal
design of a single software
process.
Software Design

8. Software design provides a
design plan that describes the
elements of a system, how they
fit, and work together to fulfill
the requirement of the system.

9. WHAT IS SOFTWARE
ARCHITECTURE DESIGN?
Software architecture design is a
representation of system which aids in
the understanding of how the system
will behave.
It is a structured framework used to
conceptualize software elements,
relationships and properties.

10. It serves as the blueprint for both
the system and project.
Software architecture is used for
defining and structuring of a
solution which connects technical
and operational requirements.

11. GOALS OF SOFTWARE ARCHITECTURE
DESIGN
Software Architecture Design has
following goals:
The main important goal of software
architecture design is to build the bridge
between business and technical
requirements.
To identify the requirements which
affect the basic structure of the
application.

12. Consider the overall effect of design
decisions.
Design should be flexible to handle the
changes in user scenarios and
requirements.
To find the different ways to implement
the use cases in the software.

14. WHY WE USE?
 It help in planning something
It help in real world complex
system by divide and conquer
In this we distribute work
between which allows us to work
parallel