Lecuture 8 Architectural Design

Lecuture 8 Architectural Design - ArchitecturalDesign...

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

View Full Document Right Arrow Icon
CUHK, Spring 2007 Architectural Design Architectural Design Teresa Teresa  Xia Cai  Xia Cai
Background image of page 1

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 5A - 2 Outline Outline Architectural design decisions System organisation Decomposition styles Control styles
Background image of page 2
CUHK, Spring 2007 Software Engineering / 5A - 3 Architectural design Architectural design Represents the  link  between specification and  design processes. It involves identifying major system components  and their communications. It is useful for: Stakeholder communication System analysis Large-scale reuse
Background image of page 3

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 5A - 4 Architecture attributes Architecture attributes Performance Localise operations to minimise sub-system communication Security Use a layered architecture with critical assets in inner layers Safety Isolate safety-critical components Availability Include redundant components in the architecture Maintainability Use fine-grain, self-contained components
Background image of page 4
CUHK, Spring 2007 Software Engineering / 5A - 5 1. System organisation 1. System organisation Reflects the basic strategy that is used to  structure  a system. Three organisational styles are widely used: A shared  data  repository style; A shared  services  and servers style; An abstract machine or  layered  style.
Background image of page 5

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 5A - 6 A. Repository model A. Repository model Sub-systems must exchange  information to work together  effectively All shared data is held in a central database  that can be accessed by all sub-systems    ( repository model ) Each sub-system maintains its own database.  Data is interchanged with other sub-systems  by passing messages to them
Background image of page 6
CUHK, Spring 2007 Software Engineering / 5A - 7 CASE toolset architecture CASE toolset architecture
Background image of page 7

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

View Full DocumentRight Arrow Icon
CUHK, Spring 2007 Software Engineering / 5A - 8 Repository model Repository model Advantages Efficient way to share large amounts of data; Sub-systems need not be concerned with how data is produced Centralised management e.g. backup, security, etc. Sharing model is published as the repository schema. Disadvantages Sub-systems must agree on a repository data model. Inevitably  a compromise; Data evolution is difficult and expensive; No scope for specific management policies; Difficult to distribute efficiently.
Background image of page 8
CUHK, Spring 2007 Software Engineering / 5A - 9 B. Client-server model B. Client-server model Distributed system  model which shows how data  and processing is distributed across a range of 
Background image of page 9

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

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

Page1 / 30

Lecuture 8 Architectural Design - ArchitecturalDesign...

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

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