softwear

1. What Is Software Architecture
• Software application architecture is
the process of defining a
structured solution that meets
all of the technical and
operational requirements, while
optimizing common quality
attributes such as performance,
security, and manageability.
• It involves a series of decisions
based on a wide range of factors,
and each of these decisions can
have considerable impact on the
quality, performance,
maintainability, and overall success
of the application.

2. Why Is Architecture Important?
• Like any other complex structure, software must be built
on a solid foundation. Failing to consider key scenarios,
failing to design for common problems, or failing to
appreciate the long term consequences of key decisions
can put your application at risk.
• Modern tools and platforms help to simplify the task of
building applications, but they do not replace the need
to design your application carefully, based on your
specific scenarios and requirements.
• The risks exposed by poor architecture include software
that is unstable, is unable to support existing or future
business requirements, or is difficult to deploy or
manage in a production environment.

3. The Goals of Architecture
• Application architecture seeks to build a bridge between
business requirements and technical requirements by
understanding use cases, and then finding ways to
implement those use cases in the software.
• The goal of architecture is to identify the requirements
that affect the structure of the application.
• Keep in mind that the architecture should:
– Expose the structure of the system but hide the implementation
details.
– Realize all of the use cases and scenarios.
– Try to address the requirements of various stakeholders.
– Handle both functional and quality requirements.

4. System Architecture
Types
Type of
architecture
Examples of elements Examples of relationships
Conceptul Components Connectors
Module Sub system, modules Exports, imports
Code Files, directories, libraries Includes, contains
Execution Tasks, threads, object interactions Uses, calls

5. software architecture by
referring to UML diagrams
– Structural Diagrams: These diagrams are used to define static architecture.
They comprise static constructs such as classes, objects, and components, and
the relationships between these elements. There are six structural diagrams:
Package Diagrams, Class Diagrams, Object Diagrams, Composite Structure
Diagrams, Component Diagrams and Deployment Diagrams.
– Behavioral Diagrams: These diagrams are used to represent dynamic
architecture. They comprise behavioral constructs such as activities, states,
timelines and the messages that run between different objects. These diagrams
are used to represent the interactions among various model elements and
instantaneous states over a time period. There are seven behavioral diagrams:
Use Case Diagrams, Activity Diagrams, State Machine Diagrams,
Communication Diagrams, Sequence Diagrams, Timing Diagrams and
Interaction Overview Diagrams.
_Composition of Structural and Behavioral elements into larger subsystems:
Such compositions are guided by desired abilities (non-functional
requirements) like usability, resilience, performance, re-use, comprehensibility,
economic and technology constraints and trade-offs etc. Also, there are cross-
cutting concerns (like security and transaction management) that apply across
all the f