Architectural description Flashcards
What does a a concrete architectural description consists of?
a set of views corresponding to a chosen set of viewpoints
In the 3+1 approach contains what?
A Module viewpoint concerned with how functionality of the system maps
to static development units,
———————————-
a Component & Connector viewpoint concerned with the runtime mapping
of functionality to components of the architecture, and
———————————–
an Allocation viewpoint concerned with how software entities are mapped
to environmental entities
———————————
collecting architecturally significant requirements in the architecture documentation
What is a module viewpoint?
is concerned with how the functionality is mapped
to the units of implementation. It visualizes the static view of the systems
architecture by showing the elements that comprise the system and their relationships.
What is a component and connector viewpoint?
software systems are perceived as consisting of components which are blackbox units of functionality and connectors which are first-class representations of communication paths between components
——————————-
Components embody functional behavior while control and communication
aspects are defined by the connectors.
Paraphrasing this, you can say that components define what parts of the system is responsible for doing while connectors
define how components exchange control and data.
What is an allocation viewpoint?
is concerned with how the software elements of the
system – in particular the C&C viewpoint elements and relations – are mapped
to platform elements in the environment of the system. We are interested in
what the software elements require (e.g., processing power, memory availability,
network bandwidth) and what the hardware elements provide.
Two types of descriptions of architecturally significant requirements, what are they?
Scenario-based requirement.
The architecturally significant scenarios (or use cases) contain a subset of the
overall scenarios providing the functional requirements for the system
—————————————-
quality attribute-based requirement.
What is the goal of describing architectural requirements?
is to enable the construction of a set of “test cases” against which different architectural designs may be
compared and/or evaluated.
What is architectural description languages (ADL)
Languages for describing software architectures:
- Box-and-line drawings
- Formal descriptions
- Multiple view-based descriptions
- (3+1) Unified Modelling Language (subset) in the context of multiple-view description
What is the elements of an architectural description?
Architectural view (N)
- What is the software architecture?
–3+1
–design decisions
—————————————–
Architectural significant requirements (+1)
- Why is the software architecture they way it is
–Scenario based requirements
–Quality attribute based requirements
What is the 3 questions in the 3+1
How is the functionality of the system mapped to runtime components and their
interaction?
(Component & connector viewpoint/structure)
——————————
How is the functionality of the system to be mapped into implementation?
(Module viewpoint/structure)
——————————–
How are software elements mapped onto environmental structures?
(Allocation viewpoint/structure)
What are the requirements of a quality attribute workshop?
Stakeholder roles
————————
Following a specified process
What is the steps in the quality attribute workshop?
- Identification of Architectural Drivers
= most critical software architecture quality requirements. Will be a given in this workshop
——————————— - ## Scenario Brainstorming. Find quality attribute scenarios in a brainstorming process
- ## Scenario Prioritization. Vote on scenarios
- Scenario Refinement. Refine most important scenarios to be on the quality
attribute scenario format of [Bass et al, 2003]
What is a view?
“A view represents a partial aspect of a software architecture
that shows specific properties of a software system.”
[Buschmann et al., 1996]
What is the 4+1 model?
Design View
* vocabulary of problem and its solution
* primarily supports functional requirements
Process view
* threads and processes / concurrency & synchronization
* addresses performance, scalability and throughput
Implementation view
* components & files used to assemble and release the physical system
* addresses configuration management
Deployment view
* encompasses the nodes / hardware topology
* addresses distribution, delivery, installation of part that make up the physical system.
