Internet of Things Architecture

UNI.701, UNI.712, UNI.720

Applicability Important for all systems to some extent; more

important for longer- lived and more widely used

systems. IoT systems are expected, as an emerging

technology, to be highly affected by evolution and

interoperability issues.

Activities Characterize the evolution needs

Assess the current ease of evolution

Consider the evolution trade-offs

Rework the architecture

Tactics Contain change

Create extensible interfaces

Apply design techniques that facilitate change

Apply metamodel-based architectural styles

Build variation points into the software

Use standard extension points

Achieve reliable change

Preserve development environments

Table 5 : Evolution and Interoperability (adopted from [Rozanski 2005]), extended

with IoT specific aspects

4.3.2 Performance and scalability

This perspective addresses two quality properties that are closely related:
Performance and Scalability. Both are, compared to traditional information
systems, even harder to cope with in a highly distributed scenario as we have it
in IoT.

Desired Quality The ability of the system to predictably execute within

its mandated performance profile and to handle

increased processing volumes in the future if required

IoT-A Requirements UNI.008, UNI.026, UNI.027, UNI.028, UNI.066,

UNI.089, UNI.101, UNI.102, UNI.234, UNI.511,

UNI.512, UNI.615, UNI.706, UNI.708, UNI.711,

UNI.716, UNI.717

Applicability Any system with complex, unclear, or ambitious

performance requirements; systems whose architecture

includes elements whose performance is unknown; and

systems where future expansion is likely to be

significant. IoT systems are very likely to have unclear

performance characteristics, due to their heterogeneity

and high connectivity of devices.

Activities Capture the performance requirements

Create the performance models