Architectural Design - Ian Sommerville 2006 Software...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 1 Architectural Design Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 2 Objectives To introduce architectural design and to discuss its importance To explain the architectural design decisions that have to be made To introduce three complementary architectural styles covering organisation, decomposition and control To discuss reference architectures are used to communicate and compare architectures Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 3 Topics covered Architectural design decisions System organisation Decomposition styles Control styles Reference architectures Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 4 Software architecture The design process for identifying the sub- systems making up a system and the framework for sub-system control and communication is architectural design . The output of this design process is a description of the software architecture. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 5 Architectural design An early stage of the system design process. Represents the link between specification and design processes. Often carried out in parallel with some specification activities. It involves identifying major system components and their communications. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 6 Advantages of explicit architecture Stakeholder communication Architecture may be used as a focus of discussion by system stakeholders. System analysis Means that analysis of whether the system can meet its non-functional requirements is possible. Large-scale reuse The architecture may be reusable across a range of systems. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 7 Architecture and system characteristics Performance Localise critical operations and minimise communications. Use large rather than fine-grain components. Security Use a layered architecture with critical assets in the inner layers. Safety Localise safety-critical features in a small number of sub- systems. Availability Include redundant components and mechanisms for fault tolerance. Maintainability Use fine-grain, replaceable components. Ian Sommerville 2006 Software Engineering, 8th edition. Chapter 11 Slide 8 Architectural conflicts Using large-grain components improves performance but reduces maintainability. Introducing redundant data improves availability but makes security more difficult....
View Full Document

Page1 / 52

Architectural Design - Ian Sommerville 2006 Software...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online