Software Product & System
Operator-governed logical software systems business applications and effective-dated organizational usage
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 6 layers · 0 findings · 0 questions
product The offered software artifact
identity
products, producers, categories
release
versions, channels, publication
architecture What the software is made of
systemComposition
components and their assembly
dependencyAndSbom
declared dependencies and bill of materials
operation Where and how it runs
deploymentAndEnvironment
deployed systems, environments, instances
lifecycleAndSupport
support status, advisories, end of life
Note: Legacy card: layers named, findings and questions never written.
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- standalone-mm
- Navigation path
- NAV.INF.SFT.SYS
- Domain
- INF.SFT.SYS
- Industry
- Cross-industry
- Tags
- softwaresystembusinessapplicationinf.sft.sys
- Also called
- N4
What it is Derived, awaiting review
This meta-model describes software in full context: products offered by producers, their releases and components, declared dependencies, and the deployed systems and environments where releases actually run.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Operator-governed logical software systems business applications and effective-dated organizational usage
Distinguishing features Derived, awaiting review
- It is its own model because software has a double life, as a published artifact with versions and licenses and as an operated system with environments and advisories, and the two must be described together to answer questions about provenance, exposure and lifecycle.
What robots and AI may and may not do Missing, in the backlog
Not described yet. This gap is in the card backlog.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
The neutral owner archetype is the producing organization for products and releases, and the operator for deployed systems; each owns its slice of the record.
Links to other meta-models Filled
imports
- aismm - ALIGN: whole-model binding; every bundle of this model aligns to the corresponding AISMM area so a full AISMM product model can stand behind any record here.
- spdx - ALIGN: bill of materials structure and license expressions.
references
- world.organization - producing organizations and system operators.
- world.intellectualProperty - licenses and other rights over software subject matter.
- world.dataset - datasets produced or consumed by deployed systems.
- world.identifierNaming - package and product identifier schemes.
requires
- vr.wm-knw-003
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Derived, awaiting review
- releasePublished: a new version became available on a channel.
- releaseWithdrawn: a published version was pulled from distribution.
- systemDeployed: a release went live in an environment.
- systemDecommissioned: a deployed system was retired.
- advisoryIssued: a defect or exposure notice was published.
- endOfLifeAnnounced: the producer declared the end of support for a product or release line.
Legacy events listed as state transitions.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- softwareLicenseContract: the usage license attached to releases.
- supportAndMaintenanceContract: producer or operator obligations for a product or system.
- sbomDisclosureContract: terms of sharing the dependency bill of materials with consumers.
- productCataloguePage: public product and release information; omits deployment and operator detail.
- sbomExport: the component and dependency graph of a release; omits product marketing and operations.
- operationsInventory: systems, environments and running versions for the operator; omits producer-side release internals.
Context of use required Filled
- Access is always granted by the respective owner through the catalogue's S1/S2 ownership and access models, with disclosure of SBOMs and inventories audited via S4.
Sources Missing, in the backlog
Not described yet. This gap is in the card backlog.
Open questions
- Superseded by a researched world model? Map this legacy card to its successor or retire it.
Machine files
Provenance
legacy MMAS card (world-models v0.2) · legacy
Built from: models/world-n4-software-product-and-system/spec.yaml, models/docs/knowledge-information/N4-software-product-and-system.md