Chapter 6 – Architectural Design

Chapter 6 Architectural design 1

Topics covered

 Architectural design decisions

 Architectural views
 Architectural patterns
 Application architectures

Chapter 6 Architectural design 2

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.

Chapter 6 Architectural design 3

Content Management System (CMS) Website
Example

 Identifying Sub-systems: The first step is to identify

and define the major sub-systems (Components) that
make up the entire system. For instance, user
management, content editing, interface(front
rendering), and database management subsystem.
 Framework for Sub-system Control and
Communication: establish a framework for how these
sub-systems will interact with each other. For example,
the User Management sub-system might communicate
with the Content Editing sub-system to verify user
permissions. The Content Editing sub-system, in turn,
may communicate with the Database Management
sub-system to store or retrieve content.

Chapter 6 Architectural design 4

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.

Chapter 6 Architectural design 5

The architecture of a packing robot control
system
https://youtu.be/-CESiuu7CYs?si=NtWr2m-lFZPN1ST-

Chapter 6 Architectural design 6

Architectural abstraction

 Architecture in the small is concerned with the

architecture of individual programs. At this level, we are
concerned with the way that an individual program is
decomposed into components.
 Architecture in the large is concerned with the
architecture of complex enterprise systems that include
other systems, programs, and program components.
These enterprise systems are distributed over different
computers, which may be owned and managed by
different companies.

Chapter 6 Architectural design 7

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
 Product-line architectures may be developed.

Chapter 6 Architectural design 8

Architectural representations

 Simple, informal block diagrams showing entities and

relationships are the most frequently used method for
documenting software architectures.
 But these have been criticised because they lack
semantics, do not show the types of relationships
between entities nor the visible properties of entities in
the architecture.
 Depends on the use of architectural models.The
requirements for model semantics depends on how the
models are used.

Chapter 6 Architectural design 9

Box and line diagrams

 Very abstract - they do not show the nature of

component relationships nor the externally visible
properties of the sub-systems.
 However, useful for communication with stakeholders
and for project planning.

Chapter 6 Architectural design 10

Use of architectural models

 As a way of facilitating discussion about the system

design
 A high-level architectural view of a system is useful for
communication with system stakeholders and project planning
because it is not cluttered with detail. Stakeholders can relate to
it and understand an abstract view of the system. They can then
discuss the system as a whole without being confused by detail.
 As a way of documenting an architecture that has been
designed
 The aim here is to produce a complete system model that shows
the different components in a system, their interfaces and their
connections.

Chapter 6 Architectural design 11

Architectural design decisions

 Architectural design is a creative process so the process

differs depending on the type of system being
developed.
 However, a number of common decisions span all
design processes and these decisions affect the non-
functional characteristics of the system such as
performance, scalability, reliability, security,
maintainability, and usability.

Chapter 6 Architectural design 12

Architectural design decisions

Chapter 6 Architectural design 13

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.

Chapter 6 Architectural design 14

Architectural views

 What views or perspectives are useful when designing

and documenting a system’s architecture?
 What notations should be used for describing
architectural models?
 Each architectural model only shows one view or
perspective of the system.
 It might show how a system is decomposed into modules, how
the run-time processes interact or the different ways in which
system components are distributed across a network. For both
design and documentation, you usually need to present multiple
views of the software architecture.

Chapter 6 Architectural design 15

4 + 1 view model of software architecture

 A logical view, which shows the key abstractions in the

system as objects or object classes.
 A process view, which shows how, at run-time, the
system is composed of interacting processes.
 A development view, which shows how the software is
decomposed for development.
 A physical view, which shows the system hardware and
how software components are distributed across the
processors in the system.
 Related using use cases or scenarios (+1)

Chapter 6 Architectural design 16

Architectural patterns

 Patterns are a means of representing, sharing and

reusing knowledge.
 An architectural pattern is a stylized description of good
design practice, which has been tried and tested in
different environments.
 Patterns should include information about when they are
and when the are not useful.
 Patterns may be represented using tabular and graphical
descriptions.

Chapter 6 Architectural design 17

The Model-View-Controller model

Chapter 6 Architectural design 18

The Organization of the Model-View-Controller

Chapter 6 Architectural design 19

Web application architecture using the MVC
pattern ​

Chapter 6 Architectural design 20

Layered architecture​

 Used to model the interfacing of sub-systems.​

 Organises the system into a set of layers (or abstract
machines) each of which provide a set of services.​
 Supports the incremental development of sub-systems in
different layers. When a layer interface changes, only the
adjacent layer is affected.​
 However, often artificial to structure systems in this way.​

Chapter 6 Architectural design 21

The Layered architecture pattern ​

Chapter 6 Architectural design 22

A generic layered architecture ​

Chapter 6 Architectural design 23

The architecture of the Mentcare system​

16/03/25 Chapter 6 Architectural Design 24

Key points

 A software architecture is a description of how a software

system is organized. ​
 Architectural design decisions include decisions on the type
of application, the distribution of the system, the architectural
styles to be used.​
 Architectures may be documented from several different
perspectives or views such as a conceptual view, a logical
view, a process view, and a development view.​
 Architectural patterns are a means of reusing knowledge
about generic system architectures. They describe the
architecture, explain when it may be used and describe its
advantages and disadvantages.​
Chapter 6 Architectural design 25