The Software Implementation Process ontology

IRI:
http://aligned.cs.ox.ac.uk/ontologies/sip#
Date:
05-07-2015
Current version:
1.0.000
Authors:
Monika Solanki
Imported Ontologies:
http://aligned.cs.ox.ac.uk/ontologies/slo (visualise it with LODE)
http://purl.obolibrary.org/obo/swo.owl (visualise it with LODE)
http://www.ontologydesignpatterns.org/ont/dul/DUL.owl (visualise it with LODE)
http://www.w3.org/ns/prov-o# (visualise it with LODE)
Other visualisation:
Ontology source
This vocabulary is licensed under a Creative Commons Attribution License - http://creativecommons.org/licenses/by/3.0

Table of Content

  1. Introduction
  2. Classes
  3. Namespace Declarations

Introduction

The purpose of the Software Implementation Process ontology is to provide a set of conceptual entities to represent a specified system element implemented as a software product or service. This ontology imports the Software Lifecycle Ontology (SLO) available at http://aligned.cs.ox.ac.uk/ontologies/slo#. It also utilises concepts defined in the SEON ontologies available at http://www.se-on.org/ and the Software ontology (SWO) available at http://purl.obolibrary.org/obo/swo.owl. Agents using this ontology are strongly recommended to exploit the various terms and relationships defined within SWO and SEON for asserting the requirements of their implementation processes. The basic concepts of the SIP ontology are illustrated in the figure below. It shows the definition of basic software engineering processes and activities such as requirements analysis, design, implementation,

Classes

Software architectural designc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareArchitecturalDesign

has super-classes
activity

Software Architectural Design Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareArchitecturalDesignProcess

The purpose of Software Requirements Analysis Process is to establish the requirements of the software elements of the system.
has super-classes
Software Implementation Processc and (has activity some Software architectural designc)

Software constructionc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareConstruction

has super-classes
activity

Software Construction Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareConstructionProcess

The purpose of the Software Construction Process is to produce executable software units that properly reflect the software design.
has super-classes
Software Implementation Processc and (has activity some Software constructionc)

Software detailed designc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareDetailedDesign

has super-classes
activity

Software Detailed Design Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareDetailedDesignProcess

The purpose of the Software Detailed Design Process is to provide a design for the software that implements and can be verified against the requirements and the software architecture and is sufficiently detailed to permit coding and testing
has super-classes
Software Implementation Processc and (has activity some Software detailed designc)

Software Implementation Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareImplementationProcess

This process transforms specified behaviour, interfaces and implementation constraints into actions that create a system element impl emented as a software product or service, otherwise known as a "software item." This process results in a software item that satisfies architectural design requirements through verification and stakeholder requirements through validation.
has super-classes
software lifecycle process and (has activity some Software Implementation Processc)
has sub-classes
Software Qualification Testing Processc

Software implementation strategyc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareImplementationStrategy

has super-classes
activity

Software integrationc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareIntegration

has super-classes
activity

Software Integration Process c back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareIntegrationProcess

The purpose of the Software Integration Process is to combine the software units and software components, producing integrated software items, consistent with the software design, that demonstrate that the functional and non-functional software requirements are satisfied on an equivalent or complete operational platform.
has super-classes
Software Implementation Processc and (has activity some Software integrationc)

Software Qualification Testing Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareQualificationTestingProcess

has super-classes
Software Implementation Processc
The purpose of the Software Qualification Testing Process is to confirm that the integrated software product meets its defined requirements.

Software requirements analysisc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareRequirementsAnalysis

has super-classes
activity

Software Requirements Analysis Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/sip#SoftwareRequirementsAnalysisProcess

The purpose of Software Requirements Analysis Process is to establish the requirements of the software elements of the system.
has super-classes
Software Implementation Processc and (has activity some Software requirements analysisc)

Namespace Declarations back to ToC

default namespace
http://aligned.cs.ox.ac.uk/ontologies/sip#
dc
http://purl.org/dc/elements/1.1/
dul
http://www.ontologydesignpatterns.org/ont/dul/
images
http://aligned.cs.ox.ac.uk/images/
obo
http://purl.obolibrary.org/obo/
ontologies
http://aligned.cs.ox.ac.uk/ontologies/
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
slo
http://aligned.cs.ox.ac.uk/ontologies/slo#
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni.