language en
License:
http://insertlicenseURIhere.example.org
Visualization:
Visualize with WebVowl
Provenance of this page
Ontology Specification Draft

[Ontology Name]: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Cross-reference for [Ontology Name] classes, object properties and data properties back to ToC

This section provides details for each class and property defined by [Ontology Name].

Classes

Architecture Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ArchitectureProcess

A process within the architecture governance or lifecycle framework. An architecture process transforms inputs (information items, models, forces) into outputs (decisions, deliverables, models) through a structured set of activities and tasks. Processes can represent governance workflows (e.g., architecture review boards), lifecycle phases (e.g., architecture elaboration), or operational procedures (e.g., change impact assessment).
Example
ex:ArchReviewProcess a ap:ArchitectureProcess ;
    skos:prefLabel "Architecture Review Board Process"@en ;
    ap:hasActivity ex:ReviewPreparation, ex:ReviewExecution, ex:ReviewFollowUp ;
    rdfs:seeAlso <https://meta.linked.archi/iso42020#ArchitectureGovernance> .
has super-classes
element c
is in domain of
has activity op, has sub-process op, input op, output op, related process op, triggered by op
is in range of
activity of process op, consumed by op, has sub-process op, milestone of process op, produced by op, related process op, responsible for op

Information Itemc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#InformationItem

A separately identifiable body of information that is produced, stored, and delivered for human use. Information items are the currency of process communication — they flow between processes as inputs and outputs.
Example
ex:ArchProposal a ap:InformationItem ;
    skos:prefLabel "Architecture Proposal Document"@en ;
    skos:definition "The solution architect proposal including context, options, and rationale."@en ;
    ap:consumedBy ex:ArchReviewProcess .
has super-classes
Process Deliverable c
is in range of
input op, output op

Process Activityc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessActivity

A cohesive set of tasks within an architecture process that contributes to achieving the process purpose. Activities decompose a process into manageable units of work. An activity groups related tasks and may have its own inputs and outputs. Activities are ordered within a process and may have dependencies on other activities.
Example
ex:StakeholderAnalysis a ap:ProcessActivity ;
    skos:prefLabel "Stakeholder Analysis"@en ;
    ap:activityOfProcess ex:ArchConceptualization ;
    ap:hasTask ex:IdentifyStakeholders, ex:PrioritizeConcerns .
has super-classes
element c
is in domain of
activity of process op, has task op
is in range of
has activity op, task of activity op

Process Deliverablec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessDeliverable

A required output of a process that must be formally delivered to a stakeholder. Deliverables are the tangible work products that result from process execution — documents, models, assessments, or other artifacts.
Example
ex:ArchDefinitionDoc a ap:ProcessDeliverable ;
    skos:prefLabel "Architecture Definition Document"@en ;
    ap:producedBy ex:ArchElaborationProcess .
has super-classes
element c
has sub-classes
Information Item c
is in domain of
produced by op
is in range of
output op

Process Milestonec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessMilestone

A significant point or event in a process that marks the completion of a set of activities or the achievement of a key objective. Milestones are used for governance checkpoints, phase gates, and progress tracking.
Example
ex:ArchReviewGate a ap:ProcessMilestone ;
    skos:prefLabel "Architecture Review Gate"@en ;
    ap:milestoneOfProcess ex:ArchGovernanceProcess .
has super-classes
element c
is in domain of
milestone of process op

Process Rolec back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessRole

A role that a stakeholder plays within an architecture process. Process roles define responsibilities and authorities for process execution — who performs, reviews, approves, or is informed about process activities.
Example
ex:ChiefArchitect a ap:ProcessRole ;
    skos:prefLabel "Chief Architect"@en ;
    ap:responsibleFor ex:ArchGovernanceProcess .
has super-classes
stakeholder c
is in range of
approved by op, performed by op

Process Taskc back to ToC or Class ToC

IRI: https://meta.linked.archi/arch-processes#ProcessTask

A specific action or work item within a process activity. Tasks are the finest-grained units of work in the process decomposition. A task is a requirement, recommendation, or permissible action intended to contribute to the achievement of one or more outcomes of a process.
Example
ex:IdentifyStakeholders a ap:ProcessTask ;
    skos:prefLabel "Identify stakeholders and their concerns"@en ;
    ap:taskOfActivity ex:StakeholderAnalysis ;
    ap:performedBy ex:SolutionArchitect .
has super-classes
element c
is in domain of
task of activity op
is in range of
has task op

Object Properties

activity of processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#activityOfProcess

Links a ProcessActivity to the ArchitectureProcess it belongs to.
has domain
Process Activity c
has range
Architecture Process c
is inverse of
has activity op

approved byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#approvedBy

Links a ProcessDeliverable or ProcessMilestone to the role that approves it.
has range
Process Role c

consumed byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#consumedBy

Links an element to the ArchitectureProcess that consumes it as input.
has range
Architecture Process c

followsop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#follows

Links a process element to another that must precede it. Used for sequencing activities, tasks, or milestones within a process.
is inverse of
precedes op

has activityop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasActivity

Links an ArchitectureProcess to a ProcessActivity that is part of it. Activities decompose a process into manageable units of work.
has domain
Architecture Process c
has range
Process Activity c
is inverse of
activity of process op

has sub-processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasSubProcess

Links an ArchitectureProcess to a child ArchitectureProcess, enabling hierarchical process decomposition.
has domain
Architecture Process c
has range
Architecture Process c

has taskop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#hasTask

Links a ProcessActivity to a ProcessTask that is part of it.
has domain
Process Activity c
has range
Process Task c
is inverse of
task of activity op

inputop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#input

An information item, model, or artifact consumed by a process. Inputs can include architecture models, metamodels, forces (requirements, constraints), information items, or any other element that feeds into the process.
has domain
Architecture Process c
range includes
force
Information Item c
metamodel
model

milestone of processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#milestoneOfProcess

Links a ProcessMilestone to the ArchitectureProcess it belongs to.
has domain
Process Milestone c
has range
Architecture Process c

outputop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#output

An information item, model, or artifact produced by a process. Outputs can include architecture models, decisions, deliverables, information items, or any other element that results from process execution.
has domain
Architecture Process c
range includes
decision
Information Item c
Process Deliverable c
metamodel
model

performed byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#performedBy

Links a ProcessActivity or ProcessTask to the role that performs it.
has range
Process Role c

precedesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#precedes

Links a process element to another that must follow it. Used for sequencing activities, tasks, or milestones within a process.
is inverse of
follows op

produced byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#producedBy

Links a ProcessDeliverable to the ArchitectureProcess that produces it.
has domain
Process Deliverable c
has range
Architecture Process c

related processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#relatedProcess

Links an ArchitectureProcess to another related process.
has domain
Architecture Process c
has range
Architecture Process c

responsible forop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#responsibleFor

Links a ProcessRole (or Stakeholder) to the ArchitectureProcess they are responsible for executing or governing.
has domain
stakeholder c
has range
Architecture Process c

task of activityop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#taskOfActivity

Links a ProcessTask to the ProcessActivity it belongs to.
has domain
Process Task c
has range
Process Activity c
is inverse of
has task op

triggered byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/arch-processes#triggeredBy

Links a process to the event or condition that triggers its execution. The trigger can be a milestone, a decision, an external event, or a change in the architecture.
has domain
Architecture Process c

Legend back to ToC

c: Classes
op: Object Properties

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.