New Wine in Old Bottles?: Oftware Rchitecture

SOFTWARE ARCHITECTURE
New wine in old bottles?

(i.e., software architecture global design?,
architect designer)
OVERVIEW
| Tema 1. What is it, why bother?

Role of the software architect
www.wileyeurope.com/college/van vliet
2008 John Wiley & Sons Ltd.
| Tema 2. Architecture Design
| Tema 3. Viewpoints and view models
| Tema 4. Architectural styles
| Tema 5. Architecture asssessment
2
PRE-ARCHITECTURE LIFE CYCLE
stakeholders
requirements quality
(few)
agreement
development
3
CHARACTERISTICS
| Iteration mainly on functional requirements
| Few stakeholders involved
| No balancing of functional and quality

requirements
4
ADDING ARCHITECTURE, THE EASY WAY
stakeholders
(few)
agreement
architecture
detailed design development
implementation
5
ARCHITECTURE IN THE LIFE CYCLE
stakeholders
(many)
architecture
agreement
development
6
CHARACTERISTICS
| Iteration on both functional and quality
requirements
| Many stakeholders involved
| Balancing of functional and quality

requirements
7
WHY IS ARCHITECTURE IMPORTANT?
| Architecture is the vehicle for stakeholder
communication
Architecture manifests the earliest set of design
|
decisions
y Constraints on implementation
y Dictates organizational structure
y Inhibits or enable quality attributes
| Architecture is a transferable abstraction of a

system
y Product lines share a common architecture
y Allows for template-based development
y Basis for training
8
WHERE DID IT START?
| 1992: Perry & Wolf

| 1987: J.A. Zachman; 1989: M. Shaw
| 1978/79: David parnas, program families
| 1972 (1969): Edsger Dijkstra, program families
| 1969: I.P. Sharp @ NATO Software Engineering
conference:
I think we have something in addition to software
engineering [..] This is the subject of software
architecture. Architecture is different from
engineering.
9
SOFTWARE ARCHITECTURE, DEFINITION (1)
The architecture of a software system defines
that system in terms of computational
components and interactions among those
components.
(from Shaw and Garlan, Software Architecture,

Perspectives on an Emerging Discipline,
Prentice-Hall, 1996.)
10
statement

procedure

module

(design) pattern

architecture
11
The software architecture of a system is the

structure or structures of the system, which
comprise software elements, the externally visible
properties of those elements, and the relationships
among them.
(from Bass, Clements, and Kazman, Software

Architecture in Practice, SEI Series in Software
Engineering. Addison-Wesley, 2003.)
12
| Important issues raised in this definition:
y multiple system structures;
y externally visible (observable) properties of
components.
| The definition does not include:

y the process;
y rules and guidelines;
y architectural styles.
13
ARCHITECTURAL STRUCTURES
| module structure
| conceptual, or logical structure
| process, or coordination structure
| physical structure
| uses structure
| calls structure
| data flow
| control flow
| class structure
14
Architecture is the fundamental organization of
a system embodied in its components, their
relationships to each other and to the
environment and the principles guiding its
design and evolution
(from IEEE Standard on the Recommended

Practice for Architectural Descriptions, 2000.)
15
| Architecture is conceptual.
| Architecture is about fundamental things.
| Architecture exists in some context.
16
OTHER POINTS OF VIEW
| Architecture is high-level design
| Architecture is overall structure of the system
| Architecture is the structure, including the

principles and guidelines governing their design
and evolution over time
| Architecture is components and connectors
17
SOFTWARE ARCHITECTURE & QUALITY
| The notion of quality is central in software
architecting: a software architecture is devised to
gain insight in the qualities of a system at the
earliest possible stage.
| Some qualities are observable via execution:

performance, security, availability, functionality,
usability
| And some are not observable via execution:

modifiability, portability, reusability, integrability,
testability
18
THE ROLE OF THE ARCHITECT
requirements solutions
client,
architect developers
users
assess creates assess
visualises prescribes
appearance, architectural construction,

behaviour design co-operation
19
ROLE OF THE SOFTWARE ARCHITECT
| Key technical consultant
| Make decisions
| Coach of development team
| Coordinate design
| Implement key parts
| Advocate software architecture

www.wileyeurope.com/college/van vliet 20

New Wine in Old Bottles?: Oftware Rchitecture

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

New Wine in Old Bottles?: Oftware Rchitecture

Încărcat de

Drepturi de autor:

Formate disponibile

SOFTWARE ARCHITECTURE

New wine in old bottles?

| Tema 1. What is it, why bother?

| No balancing of functional and quality

detailed design development

| Balancing of functional and quality

| Architecture is a transferable abstraction of a

| 1992: Perry & Wolf

The architecture of a software system defines

(from Shaw and Garlan, Software Architecture,

The software architecture of a system is the

(from Bass, Clements, and Kazman, Software

| Important issues raised in this definition:

| The definition does not include:

Architecture is the fundamental organization of

(from IEEE Standard on the Recommended

| Architecture exists in some context.

| Architecture is the structure, including the

| Architecture is components and connectors

| Some qualities are observable via execution:

| And some are not observable via execution:

assess creates assess

appearance, architectural construction,

2008 John Wiley & Sons Ltd.

S-ar putea să vă placă și