ISO/IEC 29182-3 — Sensor Networks: SNRA — Part 3: Reference Architecture Views

Five architectural viewpoints for describing sensor network systems

Architectural Viewpoints in SNRA

ISO/IEC 29182-3 defines a set of architectural viewpoints for describing sensor network architectures, following the IEEE 1471 / ISO/IEC 42010 framework for architecture description. These viewpoints address the concerns of different stakeholders by providing multiple, coordinated perspectives on the same underlying system. The standard defines five primary viewpoints: the Functional View, the Communication View, the Information View, the Physical View, and the Operational View.

When documenting a sensor network architecture, always produce at least the Functional and Communication views before proceeding to detailed design. These two views together cover the majority of stakeholder concerns and serve as the foundation for the remaining viewpoints.

Each viewpoint is defined by a set of model kinds, conventions for constructing architecture views, and correspondence rules that ensure consistency across views. For example, a functional element identified in the Functional View must have a corresponding realisation in the Physical View, and the data flows in the Information View must be supported by the communication paths in the Communication View.

The Five Viewpoints in Detail

The Functional View organises the system into functional entities and their interactions, focusing on what the system does rather than how it is implemented. Key entities include sensing functions, processing functions, communication functions, and management functions. The Communication View describes the network topology, protocol stacks, and data link technologies, addressing how information flows between functional entities.

Viewpoint Primary Concern Key Models Stakeholder
Functional View System capabilities and functional decomposition Function tree, data flow diagram, service map System architect, application developer
Communication View Network topology and protocols Network graph, protocol stack, QoS mapping Network engineer, protocol designer
Information View Data semantics and information flow Information model, metadata schema, data dictionary Data architect, application developer
Physical View Hardware deployment and physical constraints Deployment diagram, power budget, coverage map Hardware engineer, field installer
Operational View Management, maintenance, and lifecycle Management hierarchy, alarm flow, upgrade procedure Network operator, system administrator
A common architectural mistake is creating views in isolation. The views must be cross-referenced: a change in the Physical View (e.g., replacing a wired backbone with a wireless mesh) ripples through the Communication View (new protocol requirements) and the Operational View (new management processes).

Applying the Viewpoints: A Structural Health Monitoring Example

Consider a bridge structural health monitoring system. The Functional View identifies sensing functions (vibration, strain, temperature), processing functions (FFT, peak detection, alarm generation), and communication functions (data aggregation, gateway relaying). The Communication View selects a hierarchical topology with local clusters using IEEE 802.15.4 and backhaul via cellular LTE-M.

The strength of the SNRA viewpoint approach is traceability. Each requirement from Part 1 can be traced to elements in the Functional View, then to communication paths in the Communication View, and finally to physical devices in the Physical View. This end-to-end traceability is invaluable for safety-critical applications.

The Information View defines the data model: each observation includes a timestamp, sensor identifier, measurement value, quality indicator, and spatial coordinates. The Physical View specifies that sensor nodes are attached to bridge girders at 10-metre intervals and must withstand -20 to +60 °C environmental conditions. The Operational View covers remote configuration, over-the-air firmware updates, and automated alarm escalation procedures.

Without the Operational View, many sensor network deployments suffer from “deploy-and-forget” syndrome — the network functions initially but degrades over time due to battery depletion, firmware bugs, or environmental changes. Part 3 mandates operational planning as a first-class architectural concern.

Frequently Asked Questions

Q: Do I need to use all five viewpoints for every project?
A: No. The standard recommends selecting the viewpoints that address the concerns of the relevant stakeholders. A simple indoor environmental monitoring system might only need Functional, Communication, and Physical views, while a mission-critical industrial system would benefit from all five.
Q: How does the Communication View relate to the OSI model?
A: The Communication View is compatible with the OSI model but extends it with sensor-network-specific concerns such as duty-cycled MAC protocols, energy-aware routing, and in-network processing at intermediate nodes.
Q: Can new viewpoints be added?
A: Yes. The framework is extensible. If a stakeholder group has concerns not covered by the five predefined viewpoints (e.g., a Security View for threat modelling), a new viewpoint can be defined following the same conventions.

Leave a Reply

Your email address will not be published. Required fields are marked *