Figure 68 : IoT architecture generation (expansion of Figure 67 )
This figure gives a detailed view of the actions taking place within each activity and what parts of this document contribute to these
activities and actions. The rectangular dark-red boxes represent sections in this document while <
Architecting
activity
Architecting
action
Pertinent ARM
module
Type of activity Guidance/information provided in ARM module
Create IoT
Context View
Domain-model
analysis
IoT Domain-Model
(Section 3.3)
Create an IoT Domain Model of the
envisaged IoT system. Use
information provided in the context
view for an identification of system
boundaries and system scope.
The IoT Domain Model including a thorough discussion of all
its entities.
Reference Manual
pertaining to the IoT
Domain Model
(Section 5.4.1)
In-depth information on the entities in the IoT Domain Model
together with examples of how to model these entities and
entire systems.
Requirement
process
Threat analysis Threat analysis
(Section 5.2.9)
Perform a threat analysis for the
envisaged system.
List of system aspects to be taken into account during the
threat analysis and what importance they carry.
Design choices
(Section 5.2.10)
Link identified security risks to
design choices for mitigation of
said risks.
Lists of design choices for mitigating security threats to IoT
systems.
Requirements
engineering
How to use Unified
Requirements
(UNIs) (Section
5.2.8)
Generation of system
requirements.
Insight of how the high-level UNIs can support the generation
of system requirements.