INTRODUCTION TO SOFTWARE ARCHITECTURE-TRAINING WORKSHOP

Saturday, October 18, 2014 © Amit Midha

Tuck up your sleeves and plunge into Business

Slide 1 © Amit Midha

B.E ( Computer Science )

MBA ( FINANCE)

Amit Midha

Introduction to

Software Architecture

USING

VISUALIZE YOUR SYSTEM

Architecting using UML



Slide 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?

Architecture is an Art



Slide 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?

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



Slide 4

MODELS

� 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

� Scale

� Models allow reasoning about

some characteristic of the real

system



Slide 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

� Multiple stakeholders

multiple views, multiple blueprints



Slide 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.



Slide 7

Introduction to UML with Architecture and

Design Techniques

Use of Design Patterns and

Architectural Styles

Real Life Hands on Exercises

Defining Software

Architecture

E2E Case Study Modeling Architecture



Slide 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



Slide 9



Slide 10

A

COMPREHENSIVE

COURSE



Slide 11

Thanks

For Your AttentionFor Your AttentionFor Your AttentionFor Your Attention

Forget to put

Don’t



Slide 12

Thank You Amit Midha A Freelance EA Consultant [email protected]

INTRODUCTION TO SOFTWARE ARCHITECTURE-TRAINING WORKSHOP

News & Politics

Transcript of INTRODUCTION TO SOFTWARE ARCHITECTURE-TRAINING WORKSHOP