Why Is Architecture

Important

Building Quality Software

Lack of Architectural Concerns
Why Is Architecture Important?
Building Quality Software

Why is application architecture important when

building quality software solutions?

2
ISO/IEC 9126:1991

ISO/IEC 9126:1991

3
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

4
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

5
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

6
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

7
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

8
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

9
ISO/IEC 9126:1991

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991

10
ISO/IEC 25010:2011

Usability Functionality Efficiency Maintanability

Portability Reliability

ISO/IEC 9126:1991 and ISO/IEC 25010:2011

11
ISO/IEC 25010:2011

Usability Functionality Efficiency Maintanability

Portability Reliability Security

ISO/IEC 9126:1991 and ISO/IEC 25010:2011

12
ISO/IEC 25010:2011

Usability Functionality Efficiency Maintanability

Portability Reliability Security Compatibility

ISO/IEC 9126:1991 and ISO/IEC 25010:2011

13
ISO/IEC 25010:2011

Usability Functionality Efficiency Maintanability

Portability Reliability Security Compatibility

ISO/IEC 9126:1991 and ISO/IEC 25010:2011

14
Lack of Architectural Concerns

15
Lack of Architectural Concerns
Poor service abstraction

Business concepts not correctly isolated and abstracted.

Business rules spread over different systems, and little to no code reuse

16
Lack of Architectural Concerns
Poor service abstraction

Business concepts not correctly isolated and abstracted.

Business rules spread over different systems, and little to no code reuse

Unmanageable dependencies

Systems not isolated from each other.

Updating or replacing a system has a cascade effect on other systems.

17
Lack of Architectural Concerns
Poor service abstraction

Business concepts not correctly isolated and abstracted.

Business rules spread over different systems, and little to no code reuse

Unmanageable dependencies

Systems not isolated from each other.

Updating or replacing a system has a cascade effect on other systems.

Inflexible and slow-moving legacy systems

Adapting legacy systems to business changes may be difficult.

Changes in complex and inflexible systems can take a long time.

18
Spaghetti Architecture

19
Spaghetti Architecture

20
Spaghetti Architecture

21
Why Is Architecture Important?

22
Why Is Architecture Important?

Drives Consensus

23
Why Is Architecture Important?

Drives Consensus Manages Complexity

24
Why Is Architecture Important?

Drives Consensus Manages Complexity Reduces Risk

25
Why Is Architecture Important?

Drives Consensus Manages Complexity Reduces Risk

Supports Planning

26
Why Is Architecture Important?

Drives Consensus Manages Complexity Reduces Risk

Supports Planning Facilitates Change

27
Why Is Architecture Important?

Drives Consensus Manages Complexity Reduces Risk

Supports Planning Facilitates Change Reduces Costs

28