Attribute (AKA Slot): software_components
An asset can host software artifacts that might want to be tracked. This can be used simply to keep track of the firmware version or to keep a full-blown Software Bill of Material (SBOM). Please notice that this attribute is not meant to model relationships between the different software assets available in a device. Static relationships implicit to the SoftwareAssets themselves (like "firmware image A contains package X" or "package X depends on package Y") might be modeled on the Software Assets, if desired. Although it probably goes beyond the purpose of asset modeling. Deployment dependent relationships (like "firmware image needs to be installed before installing app") might be modeled as external AssetLinks, if desired. Once again it probably goes beyond the purpose of asset modeling.
URI: base:software_components
Applicable Classes
| Name | Description |
|---|---|
| SoftwareAsset | Any kind of software element that needs to be considered |
| Dcd | Device Class Driver (DCD) running and registered |
| Gateway | Gateway as a software asset can be mapped using the class |
| SoftwareArtifact | Software asset representing software on rest |
| Asset | An asset is the representation of a functional object with a technical functi... |
| AssetLink | Asset Link (AL) running and registered |
| Device | A device is a special type of asset that can be managed with some asset manag... |
| RunningSoftware | Software asset representing running software |
Properties
- Range: SoftwareAsset
- Multivalued: True
Identifier and Mapping Information
LinkML Source
name: software_components
description: 'An asset can host software artifacts that might want to be tracked.
This can be used simply to keep track of the firmware version or to keep a full-blown
Software Bill of Material (SBOM).
Please notice that this attribute is not meant to model relationships between the
different software assets available in a device. Static relationships implicit to
the SoftwareAssets themselves (like "firmware image A contains package X" or "package
X depends on package Y") might be modeled on the Software Assets, if desired. Although
it probably goes beyond the purpose of asset modeling. Deployment dependent relationships
(like "firmware image needs to be installed before installing app") might be modeled
as external AssetLinks, if desired. Once again it probably goes beyond the purpose
of asset modeling.'
from_schema: https://common-device-management.code.siemens.io/documentation/asset-modeling/base-schema/v0.10.0/iah-base.jsonld
rank: 1000
alias: software_components
domain_of:
- Asset
range: SoftwareAsset
multivalued: true
inlined: true
inlined_as_list: true