(Imported from OWL file.) |
|||
| Line 2: | Line 2: | ||
{{Graphical representation header}} | {{Graphical representation header}} | ||
{{Graphical representation | {{Graphical representation | ||
| − | |ImageName= | + | |ImageName=ComputerSystemODP Diagram.png |
}} | }} | ||
{{Content OP Proposal Template | {{Content OP Proposal Template | ||
| + | |SubmittedBy=PanagiotisMitzias, EfstratiosKontopoulos, MarinaRiga | ||
| + | |Name=Computer System | ||
| + | |Intent=The pattern intends to model computer systems based on a hardware/software approach. This pattern has been developed by [http://mklab.iti.gr/ MKLab] at CERTH/ITI and Tate [http://www.tate.org.uk] for the [http://www.pericles-project.eu/ PERICLES] FP7 project. | ||
| + | |Domain=General | ||
|CompetencyQuestion=What is currently installed in a computer? A computer uses specific pieces of hardware and software. | |CompetencyQuestion=What is currently installed in a computer? A computer uses specific pieces of hardware and software. | ||
What software or hardware is required so that some other software or hardware can operate properly? This relationship is represented with properties requiresSoftware and requiresHardware. | What software or hardware is required so that some other software or hardware can operate properly? This relationship is represented with properties requiresSoftware and requiresHardware. | ||
What software or hardware is compatible with other software or hardware? This is expressed via the isCompatibleWith relationship. | What software or hardware is compatible with other software or hardware? This is expressed via the isCompatibleWith relationship. | ||
| + | |ContentODPDescription=The pattern represents a computer system, along with the involved software and hardware components. It also includes significant properties between these main entities. | ||
| + | |ReusableOWLBuildingBlock=http://mklab.iti.gr/pericles/ComputerSystem_ODP.owl | ||
|Consequences=The design pattern is expected to facilitate the creation of computer system domain ontologies that can be exploited in numerous fields. A well-established, comprehensible pattern will prove to be advantageous. | |Consequences=The design pattern is expected to facilitate the creation of computer system domain ontologies that can be exploited in numerous fields. A well-established, comprehensible pattern will prove to be advantageous. | ||
| − | |Scenario= | + | |Scenario=<ul><li>The computer uses Ubuntu 16.04.</li><li>The graphics card requires driver A.</li><li>The software is compatible with Windows 10.</li><li>The processor is compatible with motherboard B.</li></ul> |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
| Line 56: | Line 54: | ||
|HasElement=Software | |HasElement=Software | ||
}} | }} | ||
| − | |||
{{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: 2017-01-16 |
Diagram
| Name: | Computer System |
|---|---|
| Submitted by: | PanagiotisMitzias, EfstratiosKontopoulos, MarinaRiga |
| Also Known As: | |
| Intent: | The pattern intends to model computer systems based on a hardware/software approach. This pattern has been developed by MKLab at CERTH/ITI and Tate [1] for the PERICLES FP7 project. |
| Domains: | |
| Competency Questions: |
What software or hardware is required so that some other software or hardware can operate properly? This relationship is represented with properties requiresSoftware and requiresHardware. What software or hardware is compatible with other software or hardware? This is expressed via the isCompatibleWith relationship. |
| Solution description: | The pattern represents a computer system, along with the involved software and hardware components. It also includes significant properties between these main entities. |
| Reusable OWL Building Block: | 1 (353) |
| Consequences: | The design pattern is expected to facilitate the creation of computer system domain ontologies that can be exploited in numerous fields. 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 Computer System Content OP locally defines the following ontology elements:
isCompatibleWith (owl:ObjectProperty) Represents the relationship of compatibility between two components.
isCompatibleWith page requiresHardware (owl:ObjectProperty) Indicates that an entity requires a certain piece of hardware to operate.
requiresHardware page requiresSoftware (owl:ObjectProperty) Indicates that an entity requires a certain piece of software to operate.
requiresSoftware page usesHardware (owl:ObjectProperty) Indicates the usage of a specific piece of hardware.
usesHardware page usesOperatingSystem (owl:ObjectProperty) Indicates the usage of a certain Operating System.
usesOperatingSystem page usesSoftware (owl:ObjectProperty) Indicates the usage of a specific piece of software.
usesSoftware page
Computer (owl:Class) This entity represents computers of any type, size, cost and application.
Computer page Driver (owl:Class) A computer program that operates or controls a particular type of device that is attached to a computer.
Driver page Hardware (owl:Class) A physical component or a collection of physical components used by (or within or aside) a computer.
Hardware page OperatingSystem (owl:Class) A system software that manages computer hardware and software resources and provides common services for computer programs.
OperatingSystem page Software (owl:Class) Part of a computer system that consists of encoded information or computer instructions.
Software pageNo scenario is added to this Content OP.
This revision (revision ID 13113) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
