ProcessCO: Core Ontology for Process Modeling

• ProcessCO is a semantically rich core ontology that defines processes, work entities, and resources through formal axioms and detailed classifications.
• It structures key concepts within the FCD-OntoArch architecture, aligning foundational proxies with domain-specific constructs for comprehensive process analysis.
• The ontology employs formal axioms and quality metrics to ensure precise process decomposition, resource allocation, and rigorous reuse in diverse application scenarios.

ProcessCO is a domain-independent core ontology for representing processes, work entities, resources, roles, and their relationships, situated within the FCD-OntoArch multilayer ontological architecture for the sciences. It provides a formalized, semantically rich vocabulary and axiom set for modeling work processes—such as those found in project management, engineering, scientific workflows, or information systems—offering precise definitions, structural constraints, and systematic links to foundational ontologies. ProcessCO’s design emphasizes interoperability, reuse, quality assurance, and alignment with international standards, supporting both rigorous ontological analysis and process-centric applications (Becker et al., 2021, Olsina et al., 2021).

1. Position in FCD-OntoArch and Foundational Alignment

ProcessCO is located at the Core Ontological Level (CO) of the five-layer FCD-OntoArch (Foundational, Core, Domain, Instance Ontological Architecture for Sciences). The full layer stack comprises:

• Foundational Ontology (FO): ThingFO, providing the universal primitives (e.g., Thing, Assertion on Particulars, Allotment-related Assertion).
• Core Ontologies (CO): ProcessCO, SituationCO, GoalCO, ProjectCO, etc.—domain-independent, often reusing and refining FO via stereotypes.
• Domain Ontologies (DO): Application-field-specific, such as TestTDO or MEvaITDO.
• Low-Domain Ontologies (LDO): Specialized sub-domain or property-level extensions (e.g., MetricsLDO).
• Instance Ontology (IO): Concrete instantiations.

ProcessCO refines foundational terms using explicit stereotypes (e.g., «TFO::Thing» for WorkEntity), ensuring ontological interoperability and semantic traceability. Relationships and classes in ProcessCO are mapped to their FO analogues (e.g., consumes refines interactsWithOther), and peer ontologies (e.g., SituationCO) enrich semantic content by sharing or specializing instance-level constructs (Becker et al., 2021).

2. Principal Terms, Classifications, and Definitions

ProcessCO defines a structured set of core concepts with fine-grained stereotypes and textual definitions. Key categories include:

• WorkEntity (Thing): Generic entity for process modeling; includes WorkProcess (coarse-grained), Activity (composed of tasks/sub-activities), and Task (atomic, fine-grained).
• WorkResource (ResourceEntity): Assignable means (Agent, Method, Tool, Strategy, Time, Money).
• Agent (WorkResource subtype): Performer of tasks, explicitly partitioned as Human Agent (goal-conceiver) and Automated Agent (e.g., software bots).
• Allocation («TFO::Allotment-related Assertion»): Assignment of a WorkResource to a WorkEntity; modeled formally via AllocationModel (Artifact).
• Role («TFO::Behavior-related Assertion»): Capability/competence required of an Agent for a WorkEntity; associated via isPlayedBy.
• Condition («TFO::Constraint-related Assertion»): Pre- or post-constraints tied to a process or activity (e.g., runtime or scheduling conditions).
• ProcessPerspective: Assertion modeling specific views—functional, behavioral, informational, organizational, methodological—on a WorkEntity.
• ProductEntity (Thing): Output or consumable; subclassified (WorkProduct, NaturalProduct, Outcome, Service, Artifact).

These categories are linked by explicit relationships, e.g., produces (WorkEntity→WorkProduct), consumes, involves (WorkEntity→Role), performs (Agent→Task), setsPrecondition, isAssignedTo (Allocation→WorkEntity), and isApplicable (Method→Task). Each term or property is accompanied by an unambiguous, canonical definition (Becker et al., 2021).

3. Relationships, Properties, and Verification Matrix

ProcessCO specifies both data properties (attributes) and object properties (relationships), supporting rich process modeling.

• Data Properties include name, description, specification, version, procedure, rules, value, objective, status, startDate/endDate, and level. These annotate individuals or classes for semantic clarity.
• Object Properties form the relational backbone:

| Relationship | Domain → Range | FO Refinement | |---------------------|-------------------------------|--------------------------------------------------| | consumes | WorkEntity → ProductEntity | interactsWithOther | | produces | WorkEntity → WorkProduct | interactsWithOther | | involves | WorkEntity → Role | interactsWithOther | | isPlayedBy | Role → Agent | dealsWithParticulars | | performs | Agent → Task | interactsWithOther | | setsPrecondition | WorkEntity → Condition | defines (Assertion) |

The ProcessCO vs. ThingFO verification matrix enumerates these correspondences exhaustively, enabling semantic alignment and reuse across all FCD-OntoArch layers (Becker et al., 2021).

4. Formal Axioms and Structural Constraints

ProcessCO v1.3 is characterized by the inclusion of six formally specified axioms in first-order logic, enforcing information propagation and modularity within the work process hierarchy:

• A1/A3/A5 govern top-down propagation for consumption, production, and role-involvement from WorkProcesses to Activities.
• A2/A4/A6 extend this propagation from Activities to their subactivities or atomic Tasks.

For example, A1 asserts: $$\forall wpa, pe\;\bigl(\mathrm{WorkProcess}(wpa)\wedge\mathrm{ProductEntity}(pe)\wedge \mathrm{consumes}(wpa,pe)\;\rightarrow\;(\exists wpb\,[\mathrm{WorkProcess}(wpb)\wedge\mathrm{consumes}(wpb,pe)\wedge\mathrm{subProcessOf}(wpb,wpa)]\;\vee\;\exists a[\mathrm{Activity}(a)\wedge\mathrm{consumes}(a,pe)\wedge\mathrm{partOf}(a,wpa)])\bigr)$$ Axioms ensure that process decompositions are logically well-founded and that properties (consumption, production, role assignment) are consistent across levels of granularity (Becker et al., 2021).

5. Quality Requirements, Metrics, and Evaluation

ProcessCO’s design and improvement were tightly driven by a formal quality model structured as a non-functional requirements (NFR) tree:

• Ontological Internal Quality subdivided as
  • Structural Quality (defined terms/properties, formal axioms, relationship balance)
  • Reuse and Compliance Quality (reuse from foundational ontology, standardized glossaries).

Metrics are computed as percentages or counts, using explicit formulas such as: $$\mathit{\%DT}(e) = \frac{\#DT(e)}{\#TT(e)} \times 100$$ for “Percentage of Defined Terms”, with analogous ones for properties, axioms, and relationships. Indicator functions map raw scores to performance scales, with acceptability thresholds (e.g., >85% treated as satisfactory).

A comprehensive GOCAMECom (Goal-Oriented, Context-Aware MEasurement, Evaluation & COMparison) strategy, enriched by domain-specific metric and indicator ontologies, operationalizes this model. ProcessCO v1.3 attained the following key internal quality scores, indicating near-perfect ontological structural and reuse quality (Olsina et al., 2021):

• Defined Terms/Properties: 100%
• Formal Axioms: 100%
• Defined Non-Taxonomic Relationships: 100%
• Balanced Relationships: 86.36%
• Reuse from FO: 100%
• Use of International Glossaries: 100%
• Global Indicator (Internal Quality): 98.48% (post-axioms, up from 87.82%)

6. Recurring Use Cases and Illustrative Scenarios

ProcessCO’s formalism supports process-driven applications across multiple domains, including but not limited to:

• Resource Allocation: Assigning a Tool (e.g., JUnit) to a testing Task, encapsulated as an AllocationModel Artifict.
• Perspective Modeling: Specifying the functional view (mapping WorkProducts to inputs/outputs), organizational view (mapping Roles and Agents), and methodological view (linking Methods/Strategies) for a given WorkEntity.
• Project Scheduling: Managing Time assignments, pre-/post-conditions for Activities, and role-based performance mappings.
• Quality Assurance: Evaluating process ontologies or domain ontologies built upon ProcessCO using standardized metrics, supporting ontology comparison and improvement cycles.

These scenarios demonstrate the practical adequacy, modularity, and extensibility of the ProcessCO schema, facilitating both human-centered knowledge engineering and automated reasoning (Becker et al., 2021).

7. Comparative Evaluation and Empirical Outcomes

ProcessCO’s quality and coverage have been systematically benchmarked against related ontologies, notably the Software Process Ontology (SPO) reengineered on the UFO foundational ontology. Key empirical findings include:

• ProcessCO outperformed SPO in all evaluated quality and reuse metrics prior to the addition of formal axioms.
• Introduction of six formal axioms in v1.3 resolved the only major deficiency, yielding global internal quality >98%.
• The balanced relationships metric (PL_BNTTRA ≈ 86) is acceptable but may warrant further refinement with additional relationship types or re-tuned thresholds.

A plausible implication is that ProcessCO serves as a template for domain ontologies requiring rigorous structural and reuse quality, and that the GOCAMECom methodology is effective for iterative ontology improvement (Olsina et al., 2021).

---

References

• (Becker et al., 2021) "ProcessCO v1.3's Terms, Properties, Relationships and Axioms - A Core Ontology for Processes"
• (Olsina et al., 2021) "Designing Quality Requirements, Metrics and Indicators for Core Ontologies: Results of a Comparative Study for Process Core Ontologies"