Software Architecture Colloquium

8/14/2019 Software Architecture Colloquium

1/13

1

Software Architecture WorkshopSummary

A. Barletta

ASL

Sony Corporate Laboratories Europe

SCLE Colloquium - March 2003 - Software Architect Workshop Summary V 1.02

Summary

l Architecture (what you do)

l Architecting (how you do the process)

l Architects (who they are)

l Conclusions


2/13

2

Architecture


What is an Architecture ? (I)

Gigantic

New

Visionary

Immortal

Multi tier

Expensive

Technology


3/13

3


What is an Architecture ? (II)

l Definitions:

There are 3 reasons why Software Architecture is important

a) communication among stakeholders,

b) early design decisions, and

c) transferable abstraction of the system

Architecture is the structure of the system, comprised of

a) components or building blocks,

b) externally visible properties of those components and therelationships among them

l Definitions:

There are 3 reasons why Software Architecture is important

a) communication among stakeholders,

b) early design decisions, and

c) transferable abstraction of the system

Architecture is the structure of the system, comprised of

a) components or building blocks,

b) externally visible properties of those components and therelationships among them


When do we need an Architecture ?(I)

l Large/Complex System

Number of people (communication)

Time Frame Size of the artifacts

l Multiple Interactive Applications

Different technical/engineering areas


4/13

4


When do we need an Architecture ?(II)

l Product Family

Ex: Sony Home Devices -> Symphony !

l Technology Architecture

Java 2EE, .Net, CORBA,etc

l Domain Standard/Reference Models Harmonization of a large domain

UML, ISO-OSI, etc


Software Architecture Domain

l Technology Engineering: Java, C++, digital signal processing

Is it good ?

l Environment or Context team, company structure, resources, etc

Is it right ?

l Political Finance, Engagement

Is it successful ?

Tensions & Conflict


5/13

5


Big Stones First !!

lPut in the Jar the BIG stones first

lArchitectural Principles

lArchitectural Styles

l Important Properties


Divide et Impera

lReduce complexity

lConstraint infinite choices

l Focus on priorities

Intellectually manageable

Socially manageable


6/13

6

Architecting


Architecting

l It is the step-by-step process to build a properArchitecture starting

l from the contextual forcesl problems to solvel environment

l skills

l to the final solutionl Architectural principles, styles, attributes, etc

l Architect document (components, interfaces, protocols, etc)

The process is a framework to be used properly.


7/13

7


Software Architecture Model (I)

l Meta-Architecture

l Architecture

Conceptual Architecture

identification of components and allocation of responsibilities

Logical Architecture

design of component interactions, connection mechanisms, protocols

Execution Architecture

physical allocation of resources and process

l Architecture Guidelines and Policies


Software Architecture Model (II)


8/13

8


Software Architecting

Init/Commit

Deployment

Architectural

Requirements System

Structuring

Architecture

Validation

Architects


9/13

9


Architect(s) Role

l Domains of competency

l What you know ?

l What you do ?

l What you are ?

l How many do you need ?


Domains of CompetencyFramework

Technology

BusinessStrategy

OrganizationalPolitics

ConsultingLeadership

What youARE

What youDO

What youKNOW


10/13

10


Domains of Competency

l Leadership

Technical, Intellectual

l Consulting

Willing to provide support

l Organizational Politics

Who is in control of What

l Business Strategy

Visionary but with the feet on the ground

l Technology


What you know ?

l Understanding what technical issues are thekey to success

l Modeling techniques & development methodsl Organizations business strategy and rationale

l Understand where are the Key players in theorganization


11/13

11


What you do ?

l Communicate, Communicate and Communicate

l Modeling, tradeoff analysis, prototype,experiment, system viewpoint

l Prepare architectural documents andpresentations

l Translate business strategy into technicalvision and strategy

l Motivate and make decisions


What you are ?

l Investigative, Creative and Practical

l Visionary

l Ambitious and driven, patient and notl Good mentor, teacher

l Committed, dedicate, passionate


12/13

12


Conclusions

l Architecture Structure of the solution: good, right and successful

Divide et Impera, reduce complexity

l Architecting Architecture Model and Process

l Architects What you DO, you KNOW, you ARE

Communication


References

l http://www.bredemeyer.com/papers.htm


13/13

13

Thank you very much for yourpatience J

Any Question ?

Software Architecture Colloquium

Documents

Transcript of Software Architecture Colloquium