1
Lahore Garrison University
CSC:361- Software Engineering
Semester: Fall2020
Prepared by: TOOBA MARYAM
Preamble
Software System Modeling
Context model
Process Model
Interaction Model
Structural model
Behavioral Model
3
Outline
Architectural Design
Architectural design decisions
Architectural views
Architectural patterns
Application architectures
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.
System Architecture and Design
The overall design of a system:
• Computers and networks (e.g., monolithic, distributed)
• Interfaces and protocols (e.g., http, sql)
• Databases (e.g., relational, distributed)
• Security (e.g., smart card authentication)
• Operations (e.g., backup, archiving, audit trails)
• Software environments (e.g., languages, source control tools)
UML: System and Subsystem Modeling
Subsystem model
A grouping of elements that specifies what a part of a system should do.
Component (UML definition)
"A distributable piece of implementation of a system, including software code
(source, binary, or executable) but also including business documents, etc., in a
human system."
A component can be thought of as an implementation of a subsystem.
Example: Web Browser
WebBrowser
HTMLRender Each package represents a group of
objects.
JavaScript
HTTP
System Design: Data Intensive Systems
Examples
• Electricity utility customer billing
• Telephone company call recording and billing
• Car rental reservations (e.g., Hertz)
• Stock market brokerage (e.g., Charles Schwab)
• E-commerce (e.g., Amazon.com)
Batch Processing Example: Electricity Utility Billing
First attempt:
Transaction Data input Master file Bill
Each transaction is handled as it arrives.
10
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.
11
The architecture of a packing robot control system
12
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
13
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.
14
Architectural representations
Simple, informal block diagrams showing entities and relationships are
the most frequently used method for documenting software architectures.
But these have been criticized 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.
15
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.
16
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.
17
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.
18
Architectural design decisions
Is there a generic application architecture that can be used?
How will the system be distributed?
What architectural styles are appropriate?
What approach will be used to structure the system?
How will the system be decomposed into modules?
What control strategy should be used?
How will the architectural design be evaluated?
How should the architecture be documented?
19
Architecture reuse
Systems in the same domain often have similar architectures that reflect
domain concepts.
Application product lines are built around a core architecture with variants
that satisfy particular customer requirements.
The architecture of a system may be designed around one of more
architectural patterns or ‘styles’.
These capture the essence of an architecture and can be instantiated in
different ways.
20
Architecture and system characteristics
1. Performance
Localise critical operations and minimize communications. Use large rather than fine-grain
components.
2. Security
Use a layered architecture with critical assets in the inner layers.
3. Safety
Localise safety-critical features in a small number of sub-systems.
4. Availability
Include redundant components and mechanisms for fault tolerance.
5. Maintainability
Use fine-grain, replaceable components.
21
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.
22
4 + 1 view model of software architecture
1. A logical view, which shows the key abstractions in the system as objects
or object classes.
2. A process view, which shows how, at run-time, the system is composed of
interacting processes.
3. A development view, which shows how the software is decomposed for
development.
4. 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)
23
(4+1) view cycle
Example of vending machine from http://www.programsformca.com/
24
Logical view
UML diagram: class diag., sequence diag.
Chapter 6 Architectural design
25
Development view
UML diagram:
Component diag.
Chapter 6 Architectural design
26
Physical view
UML: Deployment
diagram
Chapter 6 Architectural design
Q&A
