SlideShare a Scribd company logo
Dr. Himanshu Hora
SRMS College of Engg. & Tech., Bareilly
INDIA
• Software is the root cause of most of
today’s system problems.
• The quality and longevity of a software
system is determined by its
architecture.
Typically software architecture includes ad hoc box and line
drawing(s) of the system that is intended to solve the
problems articulated by the specification.
• Boxes define the elements or “parts” of the system.
• Lines define the interactions or the between parts.
A software architecture is a “first cut” at
solving the problem and designing the
system.
“The software architecture of a program or
computing system is the structure or structures
of the system, which comprise software
elements, the externally visible properties of
those elements, and therelationships among
them.”
Bass L.; Clements P.;
Kazman R. Software
Architecture in Practice
Defines the properties of components
• Properties of components are assumptions that one
component can make about another:
- provided services, required services, performance
characteristics, fault handling, resource usage
Just having an architecture is different from
having an
architecture that is known to everyone.
Represents earliest design decisions
First design artifact addressing
Key to systematic reuse
• hardest to change
• most critical to get right
• communication vehicle
among
stakeholders
• performance
• reliability
• modifiability
• security
• transferable, reusable abstraction
The right architecture paves the way for system success.
The wrong architecture usually spells some form of
disaster.
Functional requirements define
• what the system must do
• how components will interact, cooperate, and
synchronize correctly
• what it means to “function” properly
Functionality is largely orthogonal to the structure.
• how modifiable is a system that is functioning
properly?
Essential quality attributes are often overlooked or
omitted from functional specifications and system
descriptions.
Importance of software architecture
 What precisely do these quality attributes such as
modifiability, security, performance and reliability
mean?
 Can a system be analyzed to determine these
desired qualities?
 How soon can such an analysis occur?
 How do you know if software architecture for a
system is suitable without having to build the system
first?
 How do you document an architecture?
 Can you recover an architecture from an existing
system?
Dr. Himanshu Hora
SRMS College of Engg. & Tech., Bareilly
INDIA

More Related Content

PPT
Pm02 system design
PPT
Software Quality Metrics
PPTX
SQA - chapter 13 (Software Quality Infrastructure)
PPT
Software architecture design ppt
KEY
Software complexity
PDF
Software Architecture and Design Introduction
PPTX
UML and Software Modeling Tools.pptx
PPTX
Presentation on component based software engineering(cbse)
Pm02 system design
Software Quality Metrics
SQA - chapter 13 (Software Quality Infrastructure)
Software architecture design ppt
Software complexity
Software Architecture and Design Introduction
UML and Software Modeling Tools.pptx
Presentation on component based software engineering(cbse)

What's hot (20)

PPTX
Software Configuration Management (SCM)
PPTX
formal verification
PPTX
component based development model
PPT
Object Oriented Analysis and Design
PPT
08 state diagram and activity diagram
PDF
SE_Lec 05_System Modelling and Context Model
PPTX
Importance of software architecture 1
PPT
17. Recovery System in DBMS
PPTX
Quality Attributes In Software Architecture & Design Patterns
PPT
Orthogonal array testing
PDF
[Question Paper] Linux Administration (75:25 Pattern) [November / 2014]
PPTX
Software Engineering Process Models
PPTX
UML Class Diagram G-3-122139
PPTX
Hipo diagram
PDF
Software Engineering Past Papers (Short Questions)
PPTX
Implementation issues software engineering
PPTX
Database connectivity in asp.net
PDF
Software engineering lecture notes
PPT
Introduction to System Calls
PPT
Chapter 01
Software Configuration Management (SCM)
formal verification
component based development model
Object Oriented Analysis and Design
08 state diagram and activity diagram
SE_Lec 05_System Modelling and Context Model
Importance of software architecture 1
17. Recovery System in DBMS
Quality Attributes In Software Architecture & Design Patterns
Orthogonal array testing
[Question Paper] Linux Administration (75:25 Pattern) [November / 2014]
Software Engineering Process Models
UML Class Diagram G-3-122139
Hipo diagram
Software Engineering Past Papers (Short Questions)
Implementation issues software engineering
Database connectivity in asp.net
Software engineering lecture notes
Introduction to System Calls
Chapter 01
Ad

Viewers also liked (18)

PPT
Design pattern & categories
PPTX
Architecture Review
PPTX
Cost Benefit Analysis Method
PPTX
Building systems from off the shelf components
PPTX
Documenting software architecture
PPTX
Software Product Line
PPTX
Reliability and its principals
PPTX
Structural and functional testing
PPT
CBAM
PPTX
Architecture Review
PPTX
Software reliability tools and common software errors
PPTX
Abc
PPTX
Business analysis in data warehousing
PPTX
Saam
PPT
Structural patterns
PPTX
Architecture business cycle
PDF
Software archiecture lecture07
PPT
ATAM
Design pattern & categories
Architecture Review
Cost Benefit Analysis Method
Building systems from off the shelf components
Documenting software architecture
Software Product Line
Reliability and its principals
Structural and functional testing
CBAM
Architecture Review
Software reliability tools and common software errors
Abc
Business analysis in data warehousing
Saam
Structural patterns
Architecture business cycle
Software archiecture lecture07
ATAM
Ad

Similar to Importance of software architecture (20)

PDF
Software architecture
 
DOC
PDF
Software archiecture lecture03
PDF
O.Savchenko FWDays workshop Software Architecture
PPT
Importance of Software architecture
DOCX
Software architecture Unit 1 notes
PPTX
Software requirement specification Unit 3.pptx
PDF
XP-Manchester 2013 Software Architecture for Agile Developers Intro
PPTX
Software Architecture and Design CS.pptx
PPTX
Software Architecture: Why and What?
PPTX
Sda 1
PDF
V5 i3201613
PPTX
software engineering Architecture and design Unit 3.pptx
PPT
Unit 2
PDF
software architecture
PPTX
chapter-6-Software_Engineering_P1_MohamedElhawy_19135002.pptx
PPTX
Designer engineering on the Data Science student
PPTX
Architecture Design
PDF
Design concepts in concepts of engineering design
PPT
DESIGN CONCEPTS
Software architecture
 
Software archiecture lecture03
O.Savchenko FWDays workshop Software Architecture
Importance of Software architecture
Software architecture Unit 1 notes
Software requirement specification Unit 3.pptx
XP-Manchester 2013 Software Architecture for Agile Developers Intro
Software Architecture and Design CS.pptx
Software Architecture: Why and What?
Sda 1
V5 i3201613
software engineering Architecture and design Unit 3.pptx
Unit 2
software architecture
chapter-6-Software_Engineering_P1_MohamedElhawy_19135002.pptx
Designer engineering on the Data Science student
Architecture Design
Design concepts in concepts of engineering design
DESIGN CONCEPTS

More from Himanshu (20)

PPTX
Software product line
PPT
Shared information systems
PPTX
Saam
PPTX
Design Pattern
PPTX
Creational pattern
PPTX
White box black box & gray box testing
PPTX
Pareto analysis
PPTX
Load runner & win runner
PPTX
Crud and jad
PPTX
Junit and cactus
PPTX
Risk based testing and random testing
PPTX
Testing a data warehouses
PPTX
Software testing tools and its taxonomy
PPTX
Software reliability engineering process
PPTX
Software reliability growth model
PPTX
Regression and performance testing
PPTX
Eleven step of software testing process
PPTX
Off the-shelf components (cots)
PPTX
Building a software testing environment
PPTX
Reconstructing Software Architecture
Software product line
Shared information systems
Saam
Design Pattern
Creational pattern
White box black box & gray box testing
Pareto analysis
Load runner & win runner
Crud and jad
Junit and cactus
Risk based testing and random testing
Testing a data warehouses
Software testing tools and its taxonomy
Software reliability engineering process
Software reliability growth model
Regression and performance testing
Eleven step of software testing process
Off the-shelf components (cots)
Building a software testing environment
Reconstructing Software Architecture

Recently uploaded (20)

PDF
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
PPTX
Programs and apps: productivity, graphics, security and other tools
PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
PDF
Approach and Philosophy of On baking technology
PDF
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
 
PDF
Per capita expenditure prediction using model stacking based on satellite ima...
PDF
NewMind AI Weekly Chronicles - August'25 Week I
PDF
Encapsulation theory and applications.pdf
PDF
Mobile App Security Testing_ A Comprehensive Guide.pdf
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
DOCX
The AUB Centre for AI in Media Proposal.docx
 
PPTX
Spectroscopy.pptx food analysis technology
PPTX
sap open course for s4hana steps from ECC to s4
PPTX
Understanding_Digital_Forensics_Presentation.pptx
PDF
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
PDF
Network Security Unit 5.pdf for BCA BBA.
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
 
PPTX
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx
Optimiser vos workloads AI/ML sur Amazon EC2 et AWS Graviton
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
Programs and apps: productivity, graphics, security and other tools
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
Reach Out and Touch Someone: Haptics and Empathic Computing
Approach and Philosophy of On baking technology
Blue Purple Modern Animated Computer Science Presentation.pdf.pdf
 
Per capita expenditure prediction using model stacking based on satellite ima...
NewMind AI Weekly Chronicles - August'25 Week I
Encapsulation theory and applications.pdf
Mobile App Security Testing_ A Comprehensive Guide.pdf
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
The AUB Centre for AI in Media Proposal.docx
 
Spectroscopy.pptx food analysis technology
sap open course for s4hana steps from ECC to s4
Understanding_Digital_Forensics_Presentation.pptx
Profit Center Accounting in SAP S/4HANA, S4F28 Col11
Network Security Unit 5.pdf for BCA BBA.
The Rise and Fall of 3GPP – Time for a Sabbatical?
 
KOM of Painting work and Equipment Insulation REV00 update 25-dec.pptx

Importance of software architecture

  • 1. Dr. Himanshu Hora SRMS College of Engg. & Tech., Bareilly INDIA
  • 2. • Software is the root cause of most of today’s system problems. • The quality and longevity of a software system is determined by its architecture.
  • 3. Typically software architecture includes ad hoc box and line drawing(s) of the system that is intended to solve the problems articulated by the specification. • Boxes define the elements or “parts” of the system. • Lines define the interactions or the between parts. A software architecture is a “first cut” at solving the problem and designing the system.
  • 4. “The software architecture of a program or computing system is the structure or structures of the system, which comprise software elements, the externally visible properties of those elements, and therelationships among them.” Bass L.; Clements P.; Kazman R. Software Architecture in Practice
  • 5. Defines the properties of components • Properties of components are assumptions that one component can make about another: - provided services, required services, performance characteristics, fault handling, resource usage
  • 6. Just having an architecture is different from having an architecture that is known to everyone.
  • 7. Represents earliest design decisions First design artifact addressing Key to systematic reuse • hardest to change • most critical to get right • communication vehicle among stakeholders • performance • reliability • modifiability • security • transferable, reusable abstraction The right architecture paves the way for system success. The wrong architecture usually spells some form of disaster.
  • 8. Functional requirements define • what the system must do • how components will interact, cooperate, and synchronize correctly • what it means to “function” properly Functionality is largely orthogonal to the structure. • how modifiable is a system that is functioning properly? Essential quality attributes are often overlooked or omitted from functional specifications and system descriptions.
  • 10.  What precisely do these quality attributes such as modifiability, security, performance and reliability mean?  Can a system be analyzed to determine these desired qualities?  How soon can such an analysis occur?  How do you know if software architecture for a system is suitable without having to build the system first?  How do you document an architecture?  Can you recover an architecture from an existing system?
  • 11. Dr. Himanshu Hora SRMS College of Engg. & Tech., Bareilly INDIA