Document Actions
AP233-DIS Ontology
This is a Protege version 4.0 OWL file. Its the very beginnings of a reference data collection for AP233. It is unreviewed work in progress by Harry Frisch. I'm using AP239 DEXlib reference data work as a creation guide. I'm using AP233 documentation layout constructs to aid in making the product reviewable in logically connected chunks. I'm using readilly available systems engineering standards for semanics. In priority order: ISO 15288, INCOSE Systems Engineering Handbook v3.1 5-Sep-2007, Navy SE-Guide-for-SoS, NASA-2007 SE HandbookRev1. The struggle is to maintain a consistent level of abstraction across the whole. Suggestion would be appreciated.
Size 94.5 kB - File type text/xml
Click here to get the file
File contents
<?xml version="1.0"?>
<!DOCTYPE rdf:RDF [
<!ENTITY owl "http://www.w3.org/2002/07/owl#" >
<!ENTITY dc "http://purl.org/dc/elements/1.1/" >
<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#" >
<!ENTITY owl2xml "http://www.w3.org/2006/12/owl2-xml#" >
<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
<!ENTITY Ontology1230124791610 "http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#" >
<!ENTITY Safety "http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Safety/" >
<!ENTITY EXPRESS "http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:" >
<!ENTITY _ "http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Modeling,_Simulation,_&" >
]>
<rdf:RDF xmlns="http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#"
xml:base="http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl"
xmlns:owl2xml="http://www.w3.org/2006/12/owl2-xml#"
xmlns:Safety="&Ontology1230124791610;Safety/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
xmlns:_="&Ontology1230124791610;Modeling,_Simulation,_&"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:EXPRESS="&Ontology1230124791610;EXPRESS:"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:Ontology1230124791610="http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:owl="http://www.w3.org/2002/07/owl#">
<owl:Ontology rdf:about=""/>
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Annotation properties
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<owl:AnnotationProperty rdf:about="&dc;description"/>
<owl:AnnotationProperty rdf:about="&dc;coverage"/>
<owl:AnnotationProperty rdf:about="&dc;creator"/>
<owl:AnnotationProperty rdf:about="&dc;contributor"/>
<!--
///////////////////////////////////////////////////////////////////////////////////////
//
// Classes
//
///////////////////////////////////////////////////////////////////////////////////////
-->
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl# -->
<owl:Class rdf:about="#">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Acquisition_Process -->
<owl:Class rdf:about="#Acquisition_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Acquisition_and_supply -->
<owl:Class rdf:about="#Acquisition_and_supply">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Activity_concepts -->
<owl:Class rdf:about="#Activity_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
<rdfs:isDefinedBy
>AP233 systems engineering ISO/TS 10303-433:2009(E)
"</rdfs:isDefinedBy>
<rdfs:comment
>Concepts related to Activity within the context of its natural language meaning. See Annex F of ISO 10303-433: AP233_systems_engineering</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Agreement -->
<owl:Class rdf:about="#Agreement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:comment
>the mutual acknowledgement of terms and conditions under which a working relationship is conducted</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Architectural_Design -->
<owl:Class rdf:about="#Architectural_Design">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Architectural_Design_Process -->
<owl:Class rdf:about="#Architectural_Design_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Baseline -->
<owl:Class rdf:about="#Baseline">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:comment
>The gate-controlled step-by-step elaboration of business, budget, functional, performance, and physical characteristics, mutually agreed to by buyer and seller, and under formal change control. Baselines can be modified between formal decision gates by mutual consent through the change control process.</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Calculated_property_value -->
<owl:Class rdf:about="#Calculated_property_value">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:comment
>A Calculated property value is a property value of a whole calculated or estimated from the values of the parts that assemble to make the whole.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Concept_of_Operations -->
<owl:Class rdf:about="#Concept_of_Operations">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:comment
>Concept of Operations (ConOps) (sometimes Operations Concept)
The ConOps describes how the system will be operated during the life-cycle phases to meet stakeholder expectations. It describes the system characteristics from an operational perspective and helps facilitate an understanding of the system goals. It stimulates the development of the requirements and architecture related to the user elements of the system. It serves as the basis for subsequent definition documents and provides the foundation for the long-range operational planning activities.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Concept_stage -->
<owl:Class rdf:about="#Concept_stage">
<rdfs:subClassOf rdf:resource="#Life_cycle_stage"/>
<owl:disjointWith rdf:resource="#Development_stage"/>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
<rdfs:comment
>The Concept Stage begins with initial recognition of a need or a concept for a new system-of-interest or for the modification to an existing system-of-interest. This is an initial exploration, fact finding, and planning period, when economic, technical, strategic, and market bases are assessed through acquirer/market survey, feasibility analysis and trade-off studies. Acquirer/user feedback to the concept is obtained.
The Concept Stage is executed to assess new business opportunities and to develop preliminary system requirements and a feasible design solution.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Configuration_Management -->
<owl:Class rdf:about="#Configuration_Management">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Configuration_Management_Process -->
<owl:Class rdf:about="#Configuration_Management_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Cost-Benefit_Analysis -->
<owl:Class rdf:about="#Cost-Benefit_Analysis">
<rdfs:subClassOf rdf:resource="#EXPRESS:Analysis_version"/>
<rdfs:comment
>A methodology to determine the advantage of one alternative over another in terms of equivalent cost or benefits. It relies on totaling positive factors and subtracting negative factors to determine a net result.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Cost-Effectiveness_Analysis -->
<owl:Class rdf:about="#Cost-Effectiveness_Analysis">
<rdfs:subClassOf rdf:resource="#EXPRESS:Analysis_version"/>
<rdfs:comment
>A systematic quantitative method for comparing the costs of alternative means of achieving the same equivalent benefit for a specific objective.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Decision-Making_Process -->
<owl:Class rdf:about="#Decision-Making_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Decision_Matrix -->
<owl:Class rdf:about="#Decision_Matrix">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:comment
>A methodology for evaluating alternatives in which valuation criteria typically are displayed in rows on the left side of the matrix, and alternatives are the column headings of the matrix. Criteria “weights” are typically assigned to each criterion.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Decision_Support_Package -->
<owl:Class rdf:about="#Decision_Support_Package">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>Documentation submitted in conjunction with formal reviews and change requests.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Decision_management -->
<owl:Class rdf:about="#Decision_management">
<rdfs:subClassOf rdf:resource="#Enabling_systems_engineering"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Derived_Requirment -->
<owl:Class rdf:about="#Derived_Requirment">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:comment
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:comment>
<rdfs:comment
>Detailed characteristics of the system-of interest that typically are identified during elicitation of stakeholder requirements, requirements analysis, trade studies or validation</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Design_Constraint -->
<owl:Class rdf:about="#Design_Constraint">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>The boundary conditions, externally or internally imposed, for the system-of-interest within which the organization must remain when executing the processes during the concept and development stage</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Design_for_Acquisition_Logistics -->
<owl:Class rdf:about="#Design_for_Acquisition_Logistics">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Development_stage -->
<owl:Class rdf:about="#Development_stage">
<rdfs:subClassOf rdf:resource="#Life_cycle_stage"/>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
<rdfs:comment
>The Development Stage begins with sufficiently detailed technical refinement of the system requirements and the design solution and transforms these into one or more feasible products that enable a service during the Utilization Stage. The system-of-interest may be a prototype in this stage. The hardware, software and operator interfaces are specified, analyzed, designed, fabricated, integrated, tested and evaluated, as applicable, and the requirements for production, training, and support facilities are defined. This stage also ensures that the aspects of future stages (production, utilization, support, and retirement) and their enabling systems' requirements and capabilities are considered and incorporated into the design through the involvement of all interested parties. Feedback is obtained from stakeholders and those who will produce, operate, use, support, and retire the system-of-interest. Outputs are a system-of-interest or a prototype of the final system-of-interest, refined enabling systems or the enabling systems themselves and all documentation and cost estimates of future stages.
The Development Stage is executed to develop a system-of-interest that meets acquirer requirements and can be produced, tested, evaluated, operated, supported and retired.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Disposal_Process -->
<owl:Class rdf:about="#Disposal_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Activity -->
<owl:Class rdf:about="#EXPRESS:Activity">
<rdfs:subClassOf rdf:resource="#SCHEMA_Activity_arm"/>
<rdfs:comment
>An Activity is the identification of the occurrence of an action that has taken place, is taking place, or is expected to take place in the future. The procedure executed during that Activity is identified with the Activity_method that is referred to by the chosen_method attribute.
EXAMPLE Change, distilling, design, a process to drill a hole, and a task such as training someone, are examples of activities.
NOTE 1 Status information identifying the level of completion of each activity may be provided within an instance of Activity_status.
NOTE 2 The items that are affected by an Activity, for example as input or output, may be identified within an instance of Applied_activity_assignment.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Activity ISO/TS 10303-1047:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Activity_property -->
<owl:Class rdf:about="#EXPRESS:Activity_property">
<rdfs:subClassOf rdf:resource="#SCHEMA_Process_property_assignment_arm"/>
<rdfs:isDefinedBy
>Application module: Process property assignment ISO/TS 10303-1040:2008(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Activity_property is a property of an Activity or of an Activity_method.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Analysis_version -->
<owl:Class rdf:about="#EXPRESS:Analysis_version">
<rdfs:subClassOf rdf:resource="#_SCHEMA_Analysis_identification_arm"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Applied_activity_assignment -->
<owl:Class rdf:about="#EXPRESS:Applied_activity_assignment">
<rdfs:subClassOf rdf:resource="#SCHEMA_Activity_arm"/>
<rdfs:comment
>An Applied_activity_assignment is an association of an Activity with product or activity data. It characterizes the role of the concepts represented with these data with respect to the activity.
NOTE This entity should not be used to represent the association of an activity with the organizations that are responsible for its execution or its management. That kind of information can be represented with instances of Organization_or_person_in_organization_assignment .</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Activity ISO/TS 10303-1047:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Context_dependent_unit -->
<owl:Class rdf:about="#EXPRESS:Context_dependent_unit">
<rdfs:subClassOf rdf:resource="#SCHEMA_Value_with_unit_arm"/>
<rdfs:comment
>A Context_dependent_unit is a type of Unit that is not related to the system of units defined in this part of ISO 10303.
EXAMPLE The number of parts in an assembly is a physical quantity that may be measured in a unit called 'parts'. Such a unit cannot be related to an SI unit.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Value with unit ISO/TS 10303-1054:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Conversion_based_unit -->
<owl:Class rdf:about="#EXPRESS:Conversion_based_unit">
<rdfs:subClassOf rdf:resource="#SCHEMA_Value_with_unit_arm"/>
<rdfs:comment
>A Conversion_based_unit is a type of Unit that that is based on another and related by a conversion factor.
NOTE A Conversion_based_unit is often used to convert a unit in one system of units to a similar unit in another system.
EXAMPLE An Imperial inch is 25.4 millimetres</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Value with unit ISO/TS 10303-1054:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Document_definition -->
<owl:Class rdf:about="#EXPRESS:Document_definition">
<rdfs:subClassOf rdf:resource="#_SCHEMA_Document_definition_arm"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Organization_or_person_in_organization_assignment -->
<owl:Class rdf:about="#EXPRESS:Organization_or_person_in_organization_assignment">
<rdfs:subClassOf rdf:resource="#SCHEMA_Person_organization_assignment_arm"/>
<rdfs:isDefinedBy
>Application module: Person organization assignment ISO/TS 10303-1013:2004(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Organization_or_person_in_organization_assignment is an association of an organization or a person in an organization with activity or product data.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Product_view_definition -->
<owl:Class rdf:about="#EXPRESS:Product_view_definition">
<rdfs:subClassOf rdf:resource="#SCHEMA_Product_view_definition_arm"/>
<rdfs:comment
>A Product_view_definition is a characterization of a Product_version, relevant in one or more application domains and for one or more life cycle stages.
A Product_view_definition is a collector of the properties that characterize the Product_version in the initial_context and additional_contexts.
EXAMPLE 1 The design of the SS Titanic and the as-built description of the SS Titanic can be represented as two instances of Product_view_definition.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Product view definition ISO/TS 10303-1019:2006(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Property_value_representation -->
<owl:Class rdf:about="#EXPRESS:Property_value_representation">
<rdfs:subClassOf rdf:resource="#SCHEMA_Measure_representation_arm"/>
<rdfs:comment
>A Property_value_representation is a type of Representation that represents one or more quantity values.
NOTE The present version of this application module does not enable to represent whether the values have been imposed or were derived or measured. It is expected that a future version will add this capability.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Measure representation ISO/TS 10303-1118:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Required_resource_by_resource_item -->
<owl:Class rdf:about="#EXPRESS:Required_resource_by_resource_item">
<rdfs:subClassOf rdf:resource="#SCHEMA_Required_resource_arm"/>
<rdfs:comment
>A Required_resource_by_resource_item is a type of Required_resource that is a statement of a required resource that can be identified within the application context.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Required resource ISO/TS 10303-1267:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Requirement_version -->
<owl:Class rdf:about="#EXPRESS:Requirement_version">
<rdfs:subClassOf rdf:resource="#SCHEMA_Requirement_identification_and_version_arm"/>
<rdfs:isDefinedBy
>Application module: Requirement identification and version ISO/TS 10303-1140:2008(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>A Requirement_version is a type of Product_version that identifies a particular version of a requirement.
NOTE This entity is used to record different versions of a requirement. In this case, the word "version" implies "revision" - that is a particular release of a requirement.
NOTE A requirment is a statement that identifies a system, product or process’ characteristic or constraint, which is unambiguous, clear, unique, consistent, stand-alone (not grouped), and verifiable, and is deemed necessary for stakeholder acceptability.
EXAMPLE A given requirement might have versions 1.0, 1.1, 1.2 and 2.0.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Resource_property -->
<owl:Class rdf:about="#EXPRESS:Resource_property">
<rdfs:subClassOf rdf:resource="#SCHEMA_Resource_property_assignment_arm"/>
<rdfs:isDefinedBy
>Application module: Resource property assignment ISO/TS 10303-1273:2004(E</rdfs:isDefinedBy>
<rdfs:comment
>A Resource_property is a property of a resource related object.
NOTE The resource related object is specified in another module</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:State_definition -->
<owl:Class rdf:about="#EXPRESS:State_definition">
<rdfs:subClassOf rdf:resource="#SCHEMA_Foundation_state_definition_arm"/>
<rdfs:isDefinedBy
>Application module: Foundation state definition ISO/TS 10303-1469:2009(E)</rdfs:isDefinedBy>
<rdfs:isDefinedBy
>A State_definition is a mode of being. In formal systems, a State_definition is the definition of a situation during which some (usually implicit) invariant condition holds.</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Task_method_version_assignment -->
<owl:Class rdf:about="#EXPRESS:Task_method_version_assignment">
<rdfs:subClassOf rdf:resource="#SCHEMA_Task_specification_arm"/>
<rdfs:comment
>A Task_method_version_assignment is a type of Applied_activity_method_assignment. It is an association of a Task_method_version with product or activity data.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Task specification ISO/TS 10303-1262:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:Value_with_unit -->
<owl:Class rdf:about="#EXPRESS:Value_with_unit">
<rdfs:subClassOf rdf:resource="#SCHEMA_Value_with_unit_arm"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:View_definition_context -->
<owl:Class rdf:about="#EXPRESS:View_definition_context">
<rdfs:subClassOf rdf:resource="#SCHEMA_Product_view_definition_arm"/>
<dc:description
>A View_definition_context is the grouping of an application domain and a life cycle stage. It identifies a universe of discourse suitable for the description of products.
NOTE Requirements and vocabularies vary among the industrial activity fields. This entity intends to identify such a domain.</dc:description>
<rdfs:isDefinedBy
>Application module: Product view definition ISO/TS 10303-1019:2006(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:View_definition_usage -->
<owl:Class rdf:about="#EXPRESS:View_definition_usage">
<rdfs:subClassOf rdf:resource="#SCHEMA_Product_view_definition_relationship_arm"/>
<rdfs:isDefinedBy
>Application module: Product view definition relationship ISO/TS 10303-1041:2004(E)</rdfs:isDefinedBy>
<rdfs:comment
>A View_definition_usage is a type of View_definition_relationship that specifies a directed association between two instances of Product_view_definition.
This association represents a relationship stating that, in the definition contexts of the related instances of Product_view_definition, it is considered that the related product is used in the context of the relating product.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#EXPRESS:_Activity_method -->
<owl:Class rdf:about="#EXPRESS:_Activity_method">
<rdfs:subClassOf rdf:resource="#SCHEMA_Activity_method_arm"/>
<rdfs:isDefinedBy
>Application module: Activity method ISO/TS 10303-1049:2004(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Activity_method is a way to carry out an Activity.
NOTE 1 There may be more than one method for producing a required result
NOTE 2 This definition may be used to characterize a way to resolve a request for action. The concept of action request is dealt with in module Work request.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Electromagnetic_Compatibility -->
<owl:Class rdf:about="#Electromagnetic_Compatibility">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Enabling_Product -->
<owl:Class rdf:about="#Enabling_Product">
<rdfs:subClassOf rdf:resource="#EXPRESS:Required_resource_by_resource_item"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>The life-cycle support products and services (e.g., production, test, deployment, training, maintenance, and disposal) that facilitate the progression and use of the operational end product through its life cycle. Since the end product and its enabling products are interdependent, they are viewed as a system. Project responsibility thus extends to responsibility for acquiring services from the relevant enabling products in each life-cycle phase. When a suitable enabling product does not already exist, the project that is responsible for the end product may also be responsible for creating and using the enabling product.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Enabling_system -->
<owl:Class rdf:about="#Enabling_system">
<rdfs:subClassOf rdf:resource="#EXPRESS:Product_view_definition"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>a system that complements a system-of-interest during its life cycle
stages but does not necessarily contribute directly to its function
during operation</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Enabling_systems_engineering -->
<owl:Class rdf:about="#Enabling_systems_engineering">
<rdfs:subClassOf rdf:resource="#Systems_engineering_process_activity"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Enterprise_Environment_Management_Process -->
<owl:Class rdf:about="#Enterprise_Environment_Management_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Enterprise_and_Agreement_process -->
<owl:Class rdf:about="#Enterprise_and_Agreement_process">
<rdfs:subClassOf rdf:resource="#Systems_engineering_process"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>Enterprise processes are the purview of the organization and are used to direct, enable, control, and support the system life cycle. The focus is on the capabilities of an organization relevant to the realization of a system; they are not intended to address general business management objectives, although sometimes the two overlap.
Within the enterprise, organizational units cooperate to develop, implement, deploy, operate, maintain and dispose of the system-of-interest. Enabling systems may also need to be modified to meet the needs of new systems; developed or acquired if they do not exist.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Environment -->
<owl:Class rdf:about="#Environment">
<rdfs:subClassOf rdf:resource="#EXPRESS:State_definition"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>The surroundings (natural or man-made) in which the system-of-interest is utilized and supported; or in which the system is being developed, produced or retired.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Environmental_Impacts -->
<owl:Class rdf:about="#Environmental_Impacts">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#FinalState -->
<owl:Class rdf:about="#FinalState">
<rdfs:subClassOf rdf:resource="#EXPRESS:State_definition"/>
<rdfs:comment
>A special kind of state signifying that the enclosing region is completed. If the enclosing region is directly contained in a state machine and all other regions in the state machine also are completed, then it means that the entire state machine is completed.</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#FunctionalRequirement -->
<owl:Class rdf:about="#FunctionalRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Functional requirement states what the system shall be done by the system to which it is allocated.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#How_concepts -->
<owl:Class rdf:about="#How_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Human_Factors -->
<owl:Class rdf:about="#Human_Factors">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Implementation_Process -->
<owl:Class rdf:about="#Implementation_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#ImposedDesignRequiremen -->
<owl:Class rdf:about="#ImposedDesignRequiremen">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:comment
>An Imposed design requirement states particular elements that shall be used in the design of the system or part.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Information_Management_Process -->
<owl:Class rdf:about="#Information_Management_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Integration_Process -->
<owl:Class rdf:about="#Integration_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#InterfaceRequirement -->
<owl:Class rdf:about="#InterfaceRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Interface requirement states the characteristics of the interface to which it is assigned.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Investment_Management -->
<owl:Class rdf:about="#Investment_Management">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Investment_Management_Process -->
<owl:Class rdf:about="#Investment_Management_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Least-Cost_Analysis -->
<owl:Class rdf:about="#Least-Cost_Analysis">
<rdfs:subClassOf rdf:resource="#EXPRESS:Analysis_version"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>A methodology that identifies the least-cost project option for meeting the technical requirements.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Life_cycle_cost -->
<owl:Class rdf:about="#Life_cycle_cost">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1
NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>The total cost to the organization of acquisition and ownership of a system over its entire life. It includes all costs associated with the system and its use in the concept, development, production, utilization, support and retirement stages.
The total cost of ownership over the project’s or system’s life cycle from Formulation through Implementation. The total of the direct, indirect, recurring, nonrecurring, and other related expenses incurred, or estimated to be incurred, in the design, development, verification, production, deployment, operation, maintenance, support, and disposal of a project.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Life_cycle_stage -->
<owl:Class rdf:about="#Life_cycle_stage">
<rdfs:subClassOf rdf:resource="#EXPRESS:View_definition_context"/>
<rdfs:comment
>The life cycle processes and activities are selected, tailored as appropriate and employed in a stage to fulfil the purpose and outcomes of that stage. Different organizations may undertake different stages in the life cycle. However, each stage is conducted by the organization responsible for that stage with due consideration of the available information on life cycle plans and decisions made in preceding stages. Similarly, the organization responsible for that stage records the decisions made and records the assumptions regarding subsequent stages in the life cycle
Stages may be used to construct frameworks within which system life cycle processes are used to model life cycles. The scale and rigour of process application in the listed stages and the duration of these stages will be determined by the varying technical and business needs of the projects defining and using the life cycle.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Maintenance_Process -->
<owl:Class rdf:about="#Maintenance_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Margin -->
<owl:Class rdf:about="#Margin">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:comment
>The allowances carried in budget, projected schedules, and technical performance parameters (e.g., weight, power, or memory) to account for uncertainties and risks. Margin allocations are baselined in the Formulation process, based on assessments of risks, and are typically consumed as the program/ project proceeds through the life cycle.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Mass_Properties -->
<owl:Class rdf:about="#Mass_Properties">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#MeasureOfEffectiveness -->
<owl:Class rdf:about="#MeasureOfEffectiveness">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)
INCOSE Systems Engineering Handbook v. 3.1
NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>A Measure of effectiveness states an optimization condition that a system shall meet. One of the two subclasses shall be used to signify the optimization direction.
A metric used to quantify the performance of a system, product or process in terms that describe a measure to what degree the real objective is achieved.
A measure by which a stakeholder’s expectations will be judged in assessing satisfaction with products or systems produced and delivered in accordance with the associated technical effort. The MOE is deemed to be critical to not only the acceptability of the product by the stakeholder but also critical to operational/mission usage. An MOE is typically qualitative in nature or not able to be used directly as a design-to requirement.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#MeasureOfEffectivenessMaximize -->
<owl:Class rdf:about="#MeasureOfEffectivenessMaximize">
<rdfs:subClassOf rdf:resource="#MeasureOfEffectiveness"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>A Measure of effectiveness stating that the condition shall be maximized.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#MeasureOfEffectivenessMinimize -->
<owl:Class rdf:about="#MeasureOfEffectivenessMinimize">
<rdfs:subClassOf rdf:resource="#MeasureOfEffectiveness"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>A Measure of effectiveness states that the condition shall be minimized</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Measure_of_Performance -->
<owl:Class rdf:about="#Measure_of_Performance">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>A quantitative measure that, when met by the design solution, will help ensure that an MOE for a product or system will be satisfied. These MOPs are given special attention during design to ensure that the MOEs to which they are associated are met. There are generally two or more measures of performance for each MOE.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Measured_property_value -->
<owl:Class rdf:about="#Measured_property_value">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>A Measured property value is a property value established by measurement of an actual part.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Modeling,_Simulation,_&_Prototype -->
<owl:Class rdf:about="#Modeling,_Simulation,_&_Prototype">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Operation_Process -->
<owl:Class rdf:about="#Operation_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Performance -->
<owl:Class rdf:about="#Performance">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:comment
>A quantitative measure characterizing a physical or functional attribute relating to the execution of a process, function, activity or task; Performance attributes include quantity (how many or how much), quality (how well), timeliness (how responsive, how frequent), and readiness (when, under which circumstances).</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#PerformanceRequirement -->
<owl:Class rdf:about="#PerformanceRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Performance requirement states a time duration or a time probability for the completion of a functional requirement or a function as a modelling element.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#PhysicalPropertyRequirement -->
<owl:Class rdf:about="#PhysicalPropertyRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Physical property requirement states a physical property that shall be exhibited by the system or system assembly to which it is assigned.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Process_control -->
<owl:Class rdf:about="#Process_control">
<rdfs:subClassOf rdf:resource="#EXPRESS:Applied_activity_assignment"/>
<rdfs:comment
>A Process_control is an Applied_activity_assignment class whose members control a Systems_engineering_process. It consists of directives and constraints.</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Process_enabler -->
<owl:Class rdf:about="#Process_enabler">
<rdfs:subClassOf rdf:resource="#EXPRESS:Applied_activity_assignment"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>A Process_enabler is an Applied_activity_assignment class whose members enable a Systems_engineering_process. It consists of Resources (infrastructure, including workforce) Tools and technologies.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Process_input -->
<owl:Class rdf:about="#Process_input">
<rdfs:subClassOf rdf:resource="#EXPRESS:Applied_activity_assignment"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>A Process_input is an Applied_activity_assignment class whose members are inputs to a Systems_engineering_process. It consists of data and material.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Process_output -->
<owl:Class rdf:about="#Process_output">
<rdfs:subClassOf rdf:resource="#EXPRESS:Applied_activity_assignment"/>
<rdfs:comment
>A Process_output is an Applied_activity_assignment class whose members are outputs from a Systems_engineering_process. It consists of processed data and products and services.</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Production_stage -->
<owl:Class rdf:about="#Production_stage">
<rdfs:subClassOf rdf:resource="#Life_cycle_stage"/>
<rdfs:comment
>The Production Stage begins with the approval to produce the system-of-interest. The system-of-interest may be individually produced, assembled, integrated, and tested, as appropriate, or may be mass-produced. Planning for this stage begins in the preceding Stage. Production may continue throughout the remainder of the system life
cycle. During this stage, the product may undergo enhancements or redesigns, the enabling systems may need to be reconfigured and production staff re-trained in order to continue evolving a cost effective service from the stakeholder viewpoint.
The Production Stage is executed to produce or manufacture the product, to test the product and to produce related supporting and enabling systems as needed.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Project_Assessment_Process -->
<owl:Class rdf:about="#Project_Assessment_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Project_Control_Process -->
<owl:Class rdf:about="#Project_Control_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Project_Planning -->
<owl:Class rdf:about="#Project_Planning">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Project_Planning_Process -->
<owl:Class rdf:about="#Project_Planning_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Project_concepts -->
<owl:Class rdf:about="#Project_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Project_process -->
<owl:Class rdf:about="#Project_process">
<rdfs:subClassOf rdf:resource="#Systems_engineering_process"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>Within the system life cycle, the creation or upgrade of products and services is managed by the conduct of projects.
The processes described in this section are applied according to the risk and complexity of the project. These processes fall in two categories; project specific processes include project planning, project assessment, and project control; life cycle processes, which apply both inside and outside the project context, include decisionmaking, risk management, configuration management, and information management.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Proof_of_concept -->
<owl:Class rdf:about="#Proof_of_concept">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:comment
>A naïve realization of an idea or technology to demonstrate its feasibility</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate -->
<owl:Class rdf:about="#Pseudostate">
<rdfs:subClassOf rdf:resource="#EXPRESS:State_definition"/>
<rdfs:comment
>A pseudostate is an abstraction that encompasses different types of transient vertices in the state machine graph.
Pseudostates are typically used to connect multiple transitions into more complex state transitions paths. For example, by combining a transition entering a fork pseudostate with a set of transitions exiting the fork pseudostate, we get a compound transition that leads to a set of orthogonal target states.</rdfs:comment>
<rdfs:isDefinedBy
>http://www.omg.org/docs/formal/07-11-01
15.3.8 Pseudostate (from BehaviorStateMachines)
OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-choice -->
<owl:Class rdf:about="#Pseudostate-choice">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:comment
>choice vertices which, when reached, result in the dynamic evaluation of the guards of the triggers of its outgoing transitions. This realizes a dynamic conditional branch. It allows splitting of transitions into multiple outgoing paths such that the decision on which path to take may be a function of the results of prior actions performed in the same run-to-completion step. If more than one of the guards evaluates to true, an arbitrary one is selected. If none of the guards evaluates to true, then the model is considered ill-formed. (To avoid this, it is recommended to define one outgoing transition with the predefined “else” guard for every choice vertex.) Choicevertices should be distinguished from static branch points that are based on junction points (described above).</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-deepHistory -->
<owl:Class rdf:about="#Pseudostate-deepHistory">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
<rdfs:comment
>deepHistory represents the most recent active configuration of the composite state that directly contains this pseudostate (e.g., the state configuration that was active when the composite state was last exited). A composite state can have at most one deep history vertex. At most one transition may originate from the history connector to the default deep history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a deep history are performed.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-entryPoint -->
<owl:Class rdf:about="#Pseudostate-entryPoint">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
<rdfs:comment
>An entry point pseudostate is an entry point of a state machine or composite state. In each region of the state machine or composite state it has a single transition to a vertex within the same region.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-exitPoint -->
<owl:Class rdf:about="#Pseudostate-exitPoint">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
<rdfs:comment
>An exit point pseudostate is an exit point of a state machine or composite state. Entering an exit point within any region of the composite state or state machine referenced by a submachine state implies the exit of this composite state or submachine state and the triggering of the transition that has this exit point as source in the state machine enclosing the submachine or composite state.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-fork -->
<owl:Class rdf:about="#Pseudostate-fork">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:comment
>fork vertices serve to split an incoming transition into two or more transitions terminating on orthogonal target vertices (i.e., vertices in different regions of a composite state). The segments outgoing from a fork vertex must not have guards or triggers.</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-initial -->
<owl:Class rdf:about="#Pseudostate-initial">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:isDefinedBy></rdfs:isDefinedBy>
<rdfs:comment
>An initial pseudostate represents a default vertex that is the source for a single transition to the default state of a composite state. There can be at most one initial vertex in a region. The outgoing transition from the initial vertex may have a behavior, but not a trigger or guard.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-join -->
<owl:Class rdf:about="#Pseudostate-join">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:isDefinedBy></rdfs:isDefinedBy>
<rdfs:comment
>join vertices serve to merge several transitions emanating from source vertices in different orthogonal regions. The transitions entering a join vertex cannot have guards or triggers.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-junction -->
<owl:Class rdf:about="#Pseudostate-junction">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:comment
>junction vertices are semantic-free vertices that are used to chain together multiple transitions. They are used to construct compound transition paths between states. For example, a junction can be used to converge multiple incoming transitions into a single outgoing transition representing a shared transition path (this is known as a merge). Conversely, they can be used to split an incoming transition into multiple outgoing transition segments with different guard conditions. This realizes a static conditional branch. (In the latter case, outgoing transitions whose guard conditions evaluate to false are disabled. A predefined guard denoted “else” may be defined for at most one outgoing transition. This transition is enabled if all the guards labeling the other transitions are false.) Static conditional branches are distinct from dynamic conditional branches that are realized by choice vertices (described below)</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-shallowHistory -->
<owl:Class rdf:about="#Pseudostate-shallowHistory">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:comment
>shallowHistory represents the most recent active substate of its containing state (but not the substates of that substate). A composite state can have at most one shallow history vertex. A transition coming into the shallow history vertex is equivalent to a transition coming into the most recent active substate of a state. At most one transition may originate from the history connector to the default shallow history state. This transition is taken in case the composite state had never been active before. Entry actions of states entered on the path to the state represented by a shallow history are performed.</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Pseudostate-terminate -->
<owl:Class rdf:about="#Pseudostate-terminate">
<rdfs:subClassOf rdf:resource="#Pseudostate"/>
<rdfs:comment
>Entering a terminate pseudostate implies that the execution of this state machine by means of its context object is terminated. The state machine does not exit any states nor does it perform any exit actions other than those associated with the transition leading to the terminate pseudostate. Entering a terminate pseudostate is equivalent to invoking a DestroyObjectAction.</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Quality_Management -->
<owl:Class rdf:about="#Quality_Management">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Quality_Management_Process -->
<owl:Class rdf:about="#Quality_Management_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#ReferenceRequirement -->
<owl:Class rdf:about="#ReferenceRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:comment
>An Reference requirement states a reference to a source of additional requirements that shall be met by the system or part.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Region -->
<owl:Class rdf:about="#Region">
<rdfs:subClassOf rdf:resource="#EXPRESS:State_definition"/>
<rdfs:comment
>A region is an orthogonal part of either a composite state or a state machine. It contains states and transitions.</rdfs:comment>
<rdfs:isDefinedBy
>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Representation_concepts -->
<owl:Class rdf:about="#Representation_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
<rdfs:comment
>Concepts related to PRepresentation within the context of its natural language meaning. See Annex F of ISO 10303-433: AP233_systems_engineering</rdfs:comment>
<rdfs:isDefinedBy
>AP233 systems engineering ISO/TS 10303-433:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Required_budgeted_property_value -->
<owl:Class rdf:about="#Required_budgeted_property_value">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:comment
>A Required budgeted property value is a property value allocated to a part by a requirement, or budgeted to that part by analysis.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Requirement_management -->
<owl:Class rdf:about="#Requirement_management">
<rdfs:subClassOf rdf:resource="#Enabling_systems_engineering"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Requirements_Analysis_Process -->
<owl:Class rdf:about="#Requirements_Analysis_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
<rdfs:comment
>The purpose of the Requirements Analysis Process is to review, assess, prioritize, and balance all stakeholder and derived requirements (including constraints); and to transform those requirements into a functional and technical view of a system description capable of meeting the stakeholders’ needs.</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Resource_Management -->
<owl:Class rdf:about="#Resource_Management">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Resource_Management_Process -->
<owl:Class rdf:about="#Resource_Management_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Resource_concepts -->
<owl:Class rdf:about="#Resource_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Retirement_stage -->
<owl:Class rdf:about="#Retirement_stage">
<rdfs:subClassOf rdf:resource="#Life_cycle_stage"/>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
<rdfs:comment
>The Retirement Stage provides for the removal of a system-of-interest and related operational and support services. Planning for the Retirement Stage begins in the preceding stages. This stage begins when a system-ofinterest
is taken out of service.
The Retirement Stage is executed to provide for the removal of a system-of-interest and related operational and support services, and to operate and support the retirement system itself.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Risk_and_Opportunity_Management_Process -->
<owl:Class rdf:about="#Risk_and_Opportunity_Management_Process">
<rdfs:subClassOf rdf:resource="#Project_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Risk_and_opportunity_management -->
<owl:Class rdf:about="#Risk_and_opportunity_management">
<rdfs:subClassOf rdf:resource="#Enabling_systems_engineering"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Activity_arm -->
<owl:Class rdf:about="#SCHEMA_Activity_arm">
<rdfs:subClassOf rdf:resource="#Activity_concepts"/>
<rdfs:comment
>This part of ISO 10303 specifies an application module for the representation of the data that identify activities and of association of an activity with product or activity data</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Activity ISO/TS 10303-1047:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Activity_method_arm -->
<owl:Class rdf:about="#SCHEMA_Activity_method_arm">
<rdfs:subClassOf rdf:resource="#Activity_concepts"/>
<rdfs:comment
>This part of ISO 10303 specifies an application module for the representation of a method by which an activity may be performed.
NOTE The Activity_method module provides a foundation for more detailed and specific specifications of how particular activities are to be performed.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Activity method ISO/TS 10303-1049:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Foundation_state_definition_arm -->
<owl:Class rdf:about="#SCHEMA_Foundation_state_definition_arm">
<rdfs:subClassOf rdf:resource="#Activity_concepts"/>
<rdfs:isDefinedBy
>Application module: Foundation state definition ISO/TS 10303-1469:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>This part of ISO 10303 specifies an application module for the representation of states and transitions between states.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Measure_representation_arm -->
<owl:Class rdf:about="#SCHEMA_Measure_representation_arm">
<rdfs:subClassOf rdf:resource="#Representation_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Person_organization_assignment_arm -->
<owl:Class rdf:about="#SCHEMA_Person_organization_assignment_arm">
<rdfs:subClassOf rdf:resource="#Who_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Process_property_assignment_arm -->
<owl:Class rdf:about="#SCHEMA_Process_property_assignment_arm">
<rdfs:subClassOf rdf:resource="#Representation_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Product_view_definition_arm -->
<owl:Class rdf:about="#SCHEMA_Product_view_definition_arm">
<rdfs:subClassOf rdf:resource="#What_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Product_view_definition_relationship_arm -->
<owl:Class rdf:about="#SCHEMA_Product_view_definition_relationship_arm">
<rdfs:subClassOf rdf:resource="#What_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Required_resource_arm -->
<owl:Class rdf:about="#SCHEMA_Required_resource_arm">
<rdfs:subClassOf rdf:resource="#Resource_concepts"/>
<rdfs:comment
>This part of ISO 10303 specifies an application module for the representation of resources required to achieve a specified objective.</rdfs:comment>
<rdfs:isDefinedBy
>Application module: Required resource ISO/TS 10303-1267:2004(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Requirement_identification_and_version_arm -->
<owl:Class rdf:about="#SCHEMA_Requirement_identification_and_version_arm">
<rdfs:subClassOf rdf:resource="#Project_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Resource_property_assignment_arm -->
<owl:Class rdf:about="#SCHEMA_Resource_property_assignment_arm">
<rdfs:subClassOf rdf:resource="#Representation_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Task_specification_arm -->
<owl:Class rdf:about="#SCHEMA_Task_specification_arm">
<rdfs:subClassOf rdf:resource="#Activity_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#SCHEMA_Value_with_unit_arm -->
<owl:Class rdf:about="#SCHEMA_Value_with_unit_arm">
<rdfs:subClassOf rdf:resource="#Representation_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Safety/Health_Hazards -->
<owl:Class rdf:about="#Safety/Health_Hazards">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Specialty_engineering_activities -->
<owl:Class rdf:about="#Specialty_engineering_activities">
<rdfs:subClassOf rdf:resource="#Systems_engineering_process_activity"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Stakeholder_Requirements_Definition_Process -->
<owl:Class rdf:about="#Stakeholder_Requirements_Definition_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>The purpose of the Stakeholder Requirements Definition Process is to elicit, negotiate, document, and maintain stakeholders’ requirements for the system-of-interest within a defined environment.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Supply_Process -->
<owl:Class rdf:about="#Supply_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Support_stage -->
<owl:Class rdf:about="#Support_stage">
<rdfs:subClassOf rdf:resource="#Life_cycle_stage"/>
<rdfs:comment
>The Support Stage begins with the provision of maintenance, logistics and other support for the system-of-interest's operation and use. Planning for this stage begins in the preceding stages. The Support Stage is completed with the retirement of the system-of-interest and termination of support services.
The Support Stage is executed to provide logistics, maintenance, and support services that enable continued system-of-interest operation and a sustainable service.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Sustainment_Engineering -->
<owl:Class rdf:about="#Sustainment_Engineering">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#System_Life_Cycle_Processes_Management_Process -->
<owl:Class rdf:about="#System_Life_Cycle_Processes_Management_Process">
<rdfs:subClassOf rdf:resource="#Enterprise_and_Agreement_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#System_element -->
<owl:Class rdf:about="#System_element">
<rdfs:subClassOf rdf:resource="#EXPRESS:Product_view_definition"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>a member of a set of elements that constitutes a system</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#System_of_interest -->
<owl:Class rdf:about="#System_of_interest">
<rdfs:subClassOf rdf:resource="#EXPRESS:Product_view_definition"/>
<rdfs:comment
>the system whose life cycle is under consideration</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#System_of_systems -->
<owl:Class rdf:about="#System_of_systems">
<rdfs:subClassOf rdf:resource="#EXPRESS:Product_view_definition"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>System of systems applies to a system-of-interest whose system elements are themselves systems; typically these entail large scale inter-disciplinary problems with multiple, heterogeneous, distributed systems.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Systems_engineering_process -->
<owl:Class rdf:about="#Systems_engineering_process">
<rdfs:subClassOf rdf:resource="#EXPRESS:View_definition_context"/>
<rdfs:isDefinedBy
>Cloned from PLCS DexLib Class Application_domain</rdfs:isDefinedBy>
<rdfs:comment
>A Systems_engineering_process is a View_definition_context that classifies the associated data as having been defined within the context of that Systems_engineering_process</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Systems_engineering_process_activity -->
<owl:Class rdf:about="#Systems_engineering_process_activity">
<rdfs:subClassOf rdf:resource="#EXPRESS:Activity"/>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:seeAlso
>Table 1.1 - for INCOSE list of Systems engineering process activity</rdfs:seeAlso>
<rdfs:comment
>set of interrelated or interacting activities which transforms inputs into outputs</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Systems_engineering_support -->
<owl:Class rdf:about="#Systems_engineering_support">
<rdfs:subClassOf rdf:resource="#Systems_engineering_process_activity"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Target_budget_property_value -->
<owl:Class rdf:about="#Target_budget_property_value">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>A Target budget property value is a temporary property value used by a designer as the design work proceeds and different design alternatives are considered.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Technical_Data_Package -->
<owl:Class rdf:about="#Technical_Data_Package">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>An output of the Design Solution Definition Process, it evolves from phase to phase, starting with conceptual sketches or models and ending with complete drawings, parts list, and other details needed for product implementation or product integration.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Technical_Measures -->
<owl:Class rdf:about="#Technical_Measures">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:comment
>An established set of measures based on the expectations and requirements that will be tracked and assessed to determine overall system or product effectiveness and customer satisfaction. Common terms for these measures are MOEs, MOPs, and TPMs.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Technical_Performance_Measures -->
<owl:Class rdf:about="#Technical_Performance_Measures">
<rdfs:subClassOf rdf:resource="#EXPRESS:Value_with_unit"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>The set of critical or key performance parameters that are monitored by comparing the current actual achievement of the parameters with that anticipated at the current time and on future dates. Used to confirm progress and identify deficiencies that might jeopardize meeting a system requirement. Assessed parameter values that fall outside an expected range around the anticipated values indicate a need for evaluation and corrective action. Technical performance measures are typically selected from the defined set of MOPs.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Technical_process -->
<owl:Class rdf:about="#Technical_process">
<rdfs:subClassOf rdf:resource="#Systems_engineering_process"/>
<rdfs:comment
>The ISO/IEC 15288 technical processes are invoked throughout the life cycle stages of a system. Technical processes are used to establish requirements for the system as the basis for the efforts to create an effective product or service; to sustain the system through its useful life; and to support retirement of the system.
A Technical_process is a Systems_engineering_process that classifies the associated data as having been defined within the context of that Technical_process.</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1 also cloned from PLCS DexLib Class Discipline_domain</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Trade_Study_Report -->
<owl:Class rdf:about="#Trade_Study_Report">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:comment
>A report written to document a trade study. It should include: he system under analysis; system goals, objectives (or requirements, as appropriate to the level of resolution), and constraints; measures and measurement methods (models) used; all data sources used; the alternatives chosen for analysis; computational results, including uncertainty ranges and sensitivity analyses performed; the selection rule used; and the recommended alternative.</rdfs:comment>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Training_Need_Analysis -->
<owl:Class rdf:about="#Training_Need_Analysis">
<rdfs:subClassOf rdf:resource="#Specialty_engineering_activities"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Transition_Process -->
<owl:Class rdf:about="#Transition_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Utilization_stage -->
<owl:Class rdf:about="#Utilization_stage">
<rdfs:subClassOf rdf:resource="#Life_cycle_stage"/>
<rdfs:comment
>The Utilization Stage begins after installation and transition to use of the system. The Utilization Stage is executed to operate the product at the intended operational sites to deliver the required services with continued operational and cost effectiveness. This stage ends when the system-of-interest is taken out of service.
The Utilization Stage is executed to operate the product, to deliver services within intended environments and to ensure continued operational effectiveness.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Validated_Requirements -->
<owl:Class rdf:about="#Validated_Requirements">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<dc:contributor
>A set of requirements that are well formed (clear and unambiguous), complete (agree with customer and stakeholder needs and expectations), consistent (conflict free), and individually verifiable and traceable to a higher level requirement or goal.</dc:contributor>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Validation -->
<owl:Class rdf:about="#Validation">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#ValidationRequirement -->
<owl:Class rdf:about="#ValidationRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Verification requirement states how a system requirement, design or instance shall be shown by the development organization to meet stakeholder needs.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Validation_Process -->
<owl:Class rdf:about="#Validation_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Verification -->
<owl:Class rdf:about="#Verification">
<rdfs:subClassOf rdf:resource="#Systems_engineering_support"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#VerificationRequirement -->
<owl:Class rdf:about="#VerificationRequirement">
<rdfs:subClassOf rdf:resource="#EXPRESS:Requirement_version"/>
<rdfs:isDefinedBy
>Application module: Decision support ISO/TS 10303-1486:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>An Verification requirement states how a system design or instance shall be shown by the development organization using test, analysis, inspection , demonstration, simulation, similarity, sampling, or other method to meet a requirement allocated to the system.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Verification_Process -->
<owl:Class rdf:about="#Verification_Process">
<rdfs:subClassOf rdf:resource="#Technical_process"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Waiver -->
<owl:Class rdf:about="#Waiver">
<rdfs:subClassOf rdf:resource="#EXPRESS:Document_definition"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>A documented agreement intentionally releasing a program or project from meeting a requirement. (Some Centers use deviations prior to Implementation and waivers during Implementation).</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#What_concepts -->
<owl:Class rdf:about="#What_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
<rdfs:comment
>Concepts related to What within the context of its natural language meaning. See Annex F of ISO 10303-433: AP233_systems_engineering</rdfs:comment>
<rdfs:isDefinedBy
>AP233 systems engineering ISO/TS 10303-433:2009(E)</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Who_concepts -->
<owl:Class rdf:about="#Who_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
<rdfs:isDefinedBy
>AP233 systems engineering ISO/TS 10303-433:2009(E)</rdfs:isDefinedBy>
<rdfs:comment
>Concepts related to Who within the context of its natural language meaning. See Annex F of ISO 10303-433: AP233_systems_engineering</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#Why_concepts -->
<owl:Class rdf:about="#Why_concepts">
<rdfs:subClassOf rdf:resource="&owl;Thing"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#_SCHEMA_Analysis_identification_arm -->
<owl:Class rdf:about="#_SCHEMA_Analysis_identification_arm">
<rdfs:subClassOf rdf:resource="#How_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#_SCHEMA_Document_definition_arm -->
<owl:Class rdf:about="#_SCHEMA_Document_definition_arm">
<rdfs:subClassOf rdf:resource="#Why_concepts"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#acquirer -->
<owl:Class rdf:about="#acquirer">
<rdfs:subClassOf rdf:resource="#EXPRESS:Organization_or_person_in_organization_assignment"/>
<rdfs:comment
>the stakeholder that acquires or procures a product or service from a supplier
NOTE Other terms commonly used for an acquirer are buyer, customer, purchaser. The acquirer may at the same time be the owner, user or operating organization.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#buyer -->
<owl:Class rdf:about="#buyer">
<rdfs:subClassOf rdf:resource="#acquirer"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#customer -->
<owl:Class rdf:about="#customer">
<rdfs:subClassOf rdf:resource="#acquirer"/>
<rdfs:isDefinedBy
>NASA Systems Engineering Handbook</rdfs:isDefinedBy>
<rdfs:comment
>The organization or individual that has requested a product and will receive the product to be delivered. The customer may be an end user of the product, the acquiring agent for the end user, or the requestor of the work products from a technical effort. Each product within the system hierarchy has a customer.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#enabling_system -->
<owl:Class rdf:about="#enabling_system">
<rdfs:subClassOf rdf:resource="#EXPRESS:View_definition_usage"/>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)</rdfs:isDefinedBy>
<rdfs:comment
>a system that complements a system-of-interest during its life cycle stages but does not necessarily contribute directly to its function during operation
NOTE 1 For example, when a system-of-interest enters the production stage, an enabling production system is required.
NOTE 2 Each enabling system has a life cycle of its own. This International Standard is applicable to each enabling system
when, in its own right, it is treated as a system-of-interest.</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#enterprise -->
<owl:Class rdf:about="#enterprise">
<rdfs:subClassOf rdf:resource="#EXPRESS:Organization_or_person_in_organization_assignment"/>
<rdfs:comment
>that part of an organization with responsibility to acquire and to supply products and/or services according to agreements
NOTE An organization may be involved in several enterprises and an enterprise may involve one or more organizations.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#facility -->
<owl:Class rdf:about="#facility">
<rdfs:subClassOf rdf:resource="#EXPRESS:Required_resource_by_resource_item"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>the physical means or equipment for facilitating the performance of an action, e.g. buildings, instruments, tools</rdfs:comment>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#life_cycle_model -->
<owl:Class rdf:about="#life_cycle_model">
<rdfs:subClassOf rdf:resource="#EXPRESS:Analysis_version"/>
<rdfs:comment
>a framework of processes and activities concerned with the life cycle, which also acts as a common reference for communication and understanding</rdfs:comment>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#operator -->
<owl:Class rdf:about="#operator">
<rdfs:subClassOf rdf:resource="#EXPRESS:Organization_or_person_in_organization_assignment"/>
<rdfs:comment
>an individual who, or an organization that, contributes to the functionality of a system and draws on knowledge, skills and procedures to contribute the function
NOTE 1 The role of operator and the role of user may be vested, simultaneously or sequentially, in the same individual or
organization.
NOTE 2 An individual operator combined with knowledge, skills and procedures may be considered as an element of the
system.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#purchaser -->
<owl:Class rdf:about="#purchaser">
<rdfs:subClassOf rdf:resource="#acquirer"/>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#stakeholder -->
<owl:Class rdf:about="#stakeholder">
<rdfs:subClassOf rdf:resource="#EXPRESS:Organization_or_person_in_organization_assignment"/>
<rdfs:comment
>a party having a right, share or claim in a system or in its possession of characteristics that meet that party’s needs and expectations</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#supplier -->
<owl:Class rdf:about="#supplier">
<rdfs:subClassOf rdf:resource="#EXPRESS:Organization_or_person_in_organization_assignment"/>
<rdfs:comment
>an organization or an individual that enters into an agreement with the acquirer for the supply of a product or service.</rdfs:comment>
<rdfs:isDefinedBy
>ISO/IEC 15288:2002(E)
INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
</owl:Class>
<!-- http://www.semanticweb.org/ontologies/2008/11/Ontology1230124791610.owl#user -->
<owl:Class rdf:about="#user">
<rdfs:subClassOf rdf:resource="#EXPRESS:Organization_or_person_in_organization_assignment"/>
<rdfs:isDefinedBy
>INCOSE Systems Engineering Handbook v. 3.1</rdfs:isDefinedBy>
<rdfs:comment
>individual who or group that benefits from a system during
its utilization</rdfs:comment>
</owl:Class>
<!-- http://www.w3.org/2002/07/owl#Thing -->
<owl:Class rdf:about="&owl;Thing">
<dc:description
>This is pre working draft 1 work, It has not been reviewed by anyone.
The focus is just as much on content as on being reviewable on logical chunks
Use layout constructs within AP233 ISO documentation for logical chunking.
Use layout constructs within AP239 DEXlib reference data as a guide.
Semantics and definitions of AP233 reference data based upon:
1 - ISO-15288 standard
2 - INCOSE Systems Engineering Handbook v3.1 5-Sep-2007
3 - Ap233 Concept model Draft 12
4 - Navy SE-Guide-for-SoS
5 - NASA-2007 SE HandbookRev1
Attempts to remove redundancy and synonyms have been made; the above list order aligns with prioritization.</dc:description>
<dc:coverage>AP233-DIS</dc:coverage>
<dc:creator
>Harold P. Frisch</dc:creator>
</owl:Class>
</rdf:RDF>
<!-- Generated by the OWL API (version 2.2.1.962) http://owlapi.sourceforge.net -->