Loading content
Device Capabilities describes the collection of hardware and software features of an endpoint (sensors, actuators, performance characteristics and APIs) and how they are systematically described and exposed. The concept supports interoperability, adaptability and context-aware functionality across platforms. It is technology-agnostic and architecture-focused…
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Device Capabilities describes which hardware and software abilities a device has and how they can be made usable by other systems.
The concept arose from a practical problem in mobile, IoT, and edge architectures: endpoints differ widely in sensors, actuators, performance limits, security functions, and available APIs, yet they still need to be addressed in a consistent way. The W3C Web of Things formalized this with Thing Description as a machine-readable description of metadata and interfaces; for resource-constrained devices, it can also be hosted externally.
Think of device capabilities as a capability contract in three steps: first inventory what the hardware and software can do, then publish that as a description, and finally let applications consume it according to context, permission, and resource constraints. Properties expose state, actions start work, and events report changes. That lets one application behave sensibly across very different devices.
Devices can observe data or influence physical and digital states.
Battery, compute, memory, connectivity, and latency constrain what a device can realistically do.
Capabilities are exposed through clearly named interfaces and invocation patterns.
Systems can evaluate capability information automatically instead of relying only on human reading.
The W3C model describes metadata, properties, actions, events, and security information for Things.
Device Capabilities is useful for device integration, platform abstraction, edge and IoT design, feature detection, and controlled feature exposure. It matters most when devices are unevenly equipped or when functions must be negotiated at runtime. Limits: a capability description is only as good as its maintenance; too much exposure increases complexity, upkeep, and potential attack surface.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.