(Imported from OWL file.) |
|||
| Line 1: | Line 1: | ||
{{Content_OP_Proposal_toolbar}} | {{Content_OP_Proposal_toolbar}} | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
| − | {{Graphical representation | + | {{Graphical representation}} |
| − | + | ||
| − | }} | + | |
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| − | | | + | |SubmittedBy=EfstratiosKontopoulos, PanagiotisMitzias, MarinaRiga |
| − | + | |Name=Policy | |
| − | + | ||
|Intent=The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents. | |Intent=The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents. | ||
| − | | | + | |Domain=General |
| − | + | |CompetencyQuestion=<p><i>What are the main entities associated with a policy?</i> A policy is usually associated with super/sub-policies, processes, agents and other entities.</p> | |
| − | + | <p><i>What are the main attributes of a policy?</i> They are version, language, policy type, requirement level, implementation status and automation status.</p> | |
| − | + | <p><i>Where is a policy described?</i> Statements are detailed text (formal or non- formal) definitions of the policy contents.</p> | |
| − | + | |ContentODPDescription=The pattern’s main entity is a policy. Appropriate object properties connect the policy with significant attributes and other entities. | |
| − | + | |ReusableOWLBuildingBlock=http://mklab.iti.gr/pericles/Policy_ODP.owl | |
|Consequences=The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous. | |Consequences=The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous. | ||
| − | | | + | |Scenario=<ul><li>The policy has two subpolicies.</li><li>The policy is implemented by a certain process.</li><li>The policy is validated by a certain process.</li><li>The policy is assigned to John Smith.</li><li>The policy is fully automated.</li></ul> |
| − | + | ||
| − | + | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 90: | Line 85: | ||
|HasElement=Version | |HasElement=Version | ||
}} | }} | ||
| − | |||
{{Additional information header}} | {{Additional information header}} | ||
{{Scenarios about me}} | {{Scenarios about me}} | ||
| − | {{Reviews about me}}{{Modeling issues about me}}{{My references}} | + | {{Reviews about me}} |
| + | {{Modeling issues about me}} | ||
| + | {{My references}} | ||
|
Last modified date is: 2016-11-17 |
Diagram (this article has no graphical representation)
| Name: | Policy |
|---|---|
| Submitted by: | EfstratiosKontopoulos, PanagiotisMitzias, MarinaRiga |
| Also Known As: | |
| Intent: | The pattern intends to model policies, their characteristics and their associated entities, such as processes and agents. |
| Domains: | |
| Competency Questions: |
What are the main attributes of a policy? They are version
Where is a policy described? Statements are detailed text (formal or non- formal) definitions of the policy contents. |
| Solution description: | The pattern’s main entity is a policy. Appropriate object properties connect the policy with significant attributes and other entities. |
| Reusable OWL Building Block: | 1 (342) |
| Consequences: | The Policy ODP is expected to facilitate the representation of the policy notion, which can be exploited in various domains. A well-established, comprehensible pattern will prove to be advantageous. |
| Scenarios: |
|
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The Policy Content OP locally defines the following ontology elements:
assignedTo (owl:ObjectProperty) Associates a policy to the agent that is responsible for the application of the policy (person or role).
assignedTo page hasAutomationStatus (owl:ObjectProperty) Associates a policy with an automation level.
hasAutomationStatus page hasImplementationStatus (owl:ObjectProperty) Associates a policy with an implementation level.
hasImplementationStatus page hasLanguage (owl:ObjectProperty) Associates a policy with the language used for the policy definition.
hasLanguage page hasRequirementLevel (owl:ObjectProperty) Associates a policy with an requirement level.
hasRequirementLevel page hasStatement (owl:ObjectProperty) Associates a policy with a statement, which is a detailed definition of the policy contents.
hasStatement page hasSubPolicy (owl:ObjectProperty) Associates a policy to another policy that is contained in the initial.
hasSubPolicy page hasValidationProcess (owl:ObjectProperty) Associates a policy with a process that is used to validate the policy.
hasValidationProcess page implementedBy (owl:ObjectProperty) Associates a policy with a process that is used to implement the policy.
implementedBy page targetsEntity (owl:ObjectProperty) Associates a policy with an entity that is subject to the policy.
targetsEntity page targetsUsers (owl:ObjectProperty) Associates a policy to the user community the policy has been designed for.
targetsUsers page
AutomationStatus (owl:Class) The level of automation of a policy. Specifies if a policy implementation requires human intervention. E.g. manual, automated with human intervention, automated with human validation, fully automated, etc.
AutomationStatus page ImplementationStatus (owl:Class) The level of implementation of a policy. E.g. implemented, partially implemented, unimplemented, not-implementable, etc.
ImplementationStatus page Language (owl:Class) The language used for the policy definition. E.g. natural language, ReAL, SPIN, etc.
Language page Policy (owl:Class) A deliberate system of principles to guide decisions and achieve rational outcomes. A policy is a statement of intent, and is implemented as a procedure or protocol.
Policy page PolicyType (owl:Class) The type of policy. Not all policies are equal; mandatory ones must be implemented to satisfy law or other requirements, others are aspirational, and most are met with the best possible effort. E.g. mandatory, legal requirement, aspirational, business driven, etc.
PolicyType page Process (owl:Class) A sequence of interdependent and linked procedures which, at every stage, consume one or more resources (time, energy, machines, money) to convert inputs (data, material, parts, etc.) into outputs.
Process page RequirementLevel (owl:Class) The level of a policy's compliance. E.g. must, must not, should, shoud not, may, etc.
RequirementLevel pageNo scenario is added to this Content OP.
This revision (revision ID 13067) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
