Architecting
activity
Architecting
action
Pertinent ARM
module
Type of activity Guidance/information provided in ARM module
Choose tactics
Perspectives
(Section 4.3)
Mapping of requirements onto
qualities (a.k.a. perspectives) and
identification of suitable tactics for
how to address said qualities.
These tactics can be understood as
architectural ―lines of attack.‖
Minimum set of perspectives and associated tactics.
Make design
choices
Design choices
(Section 5.2.10)
By means of the tactics identified in
the previous step, identify design
choices for addressing the
underlying qualitative requirements.
Comprehensive taxonomy of tactics and associated design
choices.
View mapping of
requirements
Non-functional
views (Section
4.2.3and Section
4.2.4)
Perform first mapping of non-
functional view requirements (and,
where expedient, of qualitative
requirements) onto the information
view and the deployment and
operational views.
Overview of IoT-specific aspects of these views and how to
model them.
Functional view
(Section 3.5 and
Section 4.2.2)
Perform first mapping of functional
requirements (and, where
expedient, of qualitative
requirements) to FCs. Identify
interfaces needed.
Description of FGs and FCs.
Derive other
views
Derive functional
view
Appendix C Define basic functions, interfaces,
and interactions for functional view.
The Appendix C provides exhaustive text on the FCs, related
technical-use-case diagrams, descriptions of basic FC
functions and high-level interfaces, as well as elementary
interactions of FC and their basic functions (sequence charts).
Interactions (Section Define system-wide interactions of The Interactions Section provides examples of how such