The document appears to be slides from a presentation on software architecture given by Amit Midha. The presentation covers topics such as defining software architecture, using models to represent systems, managing architecture through the software development lifecycle, and applying architecture techniques through case studies on banking and ATM systems. It emphasizes that architecture involves making decisions to address the needs of multiple stakeholders and separating areas of concern while maintaining consistent data formats within components.

1. Amit Midha
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Introduction to
Software Architecture
Slide 1
B.E ( Computer Science )
MBA ( FINANCE)
USING
VISUALIZE YOUR SYSTEM
Architecting using UML

2. WE ALL KNOW THAT ...
Architecture and design are the same thing but not vice versa
Architecture and infrastructure are the same thing but not vice versa
<my favorite technology> is the architecture
A good architecture is the work of a single architect
Architecture is flat, one blueprint is enough
Architecture is just structure?
System architecture precedes software architecture?
Architecture cannot be measured and validated?
Architecture is a Science?
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Architecture is an Art
Slide 2

3. WHY TO ARCHITECT?
How the users of the system will be
interacting with the system?
How will the application be
deployed into production and
managed?
What are the various non-functional
requirements for the application,
such as security, performance,
concurrency, internationalization,
and configuration?
How can the application be
designed to be flexible and
maintainable over time?
What are the architectural trends
that might impact your application
now or after it has been deployed?
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 3
Separate the areas of concern
Be explicit about how layers communicate
with each other
Abstraction should be used to implement
loose coupling between layers
Keep the data format consistent within a
layer or component

4. Models are the language of
designer, in many disciplines
Models are representations of
the system to-be-built or as-built
Models are vehicle for
communications with various
stakeholders
Visual models, blueprints
Models allow reasoning about
some characteristic of the real
system
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
MODELS
Scale
Slide 4

5. MANY STAKEHOLDERS, MANY VIEWS
Architecture is many things to many different interested parties
end-user
customer
project manager
system engineer
developer
architect
maintainer
other developers
Multidimensional reality
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Multiple stakeholders
Slide 5
multiple views, multiple blueprints

6. ARCHITECTURE IS MAKING DECISIONS
The life of a software architect is a long (and
sometimes painful) succession of suboptimal
decisions made partly in the dark.
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 6

7. Introduction to UML with Architecture and
Design Techniques
Saturday, October 18, 2014
Defining Software
Architecture
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 7
Use of Design Patterns and
Architectural Styles
Real Life Hands on Exercises
E2E Case Study
Modeling Architecture

8. Course Coverage
Workshop Objectives
Introduction and Use of Software Architecture
Defining Software Architecture
Software Architecture and Use of Design Artifacts
Software Architecture Models
Do’s and Don’ts of Architecture Modeling with a Detailed Case Study
Day 1 Theme: Introduction to Software Architecture
Layers of Software Architecture
Modeling Architecture using UML
Categorization and Capturing of Requirements using Spar EA
Introduction to Use Case Scenarios and their association with Requirements using Sparx EA
Relating Layers of Architecture to UML Diagrams
Hands on Exercise for Modeling
Case Study: Banking
Day 2 Theme: Managing Software Architecture
Understanding relating of Architecture to SDLC
Managing Change Requirements and impact on Software Architecture
Understanding Reporting and Version Control of Architecture
Case Study: ATM Management
Assessment Test -40 Questions
Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 8

9. Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 9

10. Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 10
A
COMPREHENSIVE
COURSE

11. Saturday, October 18, 2014
Don’t
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 11
Thanks
FFFFoooorrrr YYYYoooouuuurrrr AAAAtttttttteeeennnnttttiiiioooonnnn
Forget to put

12. Saturday, October 18, 2014
Tuck up your sleeves and plunge into Business
© Amit Midha
Slide 12
Thank You
Amit Midha
A Freelance EA Consultant
amit_prk@yahoo.com