The Software Lifecycle Ontology

IRI:
http://aligned.cs.ox.ac.uk/ontologies/slo
Date:
30-06-2015
Current version:
1.0.000
Authors:
Monika Solanki (monika.solanki
Imported Ontologies:
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. Object Properties
  4. Data Properties
  5. Namespace Declarations

Introduction

The Software Lifecycle Ontology (SLO) is the top level ontology for describing a process in the lifecycle of a Software. The ontology conforms to the ISO/IEC 12207 standard for Systems and software engineering — Software life cycle processes. The terminology used in the ontology conforms to ISO/IEC TR 24774:2010(E). All subprocesses will require to import this module. The figure below illustrates the conceptual entities in SLO. The core concept is a SoftwareLifecyleProcess which can be decomposed into sub-processes, tasks and activities. The <a href="http://aligned.cs.ox.ac.uk/ontologies/sip" target="_blank">SIP ontology</a> builds on this basic framework to describe standard software engineering processes e.g. requirements analysis and architectural design.

Classes

Activityc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#Activity

Activities describe a set of actions that might be undertaken to execute the process. Activities are constructs for grouping together related tasks. The activities provide a means to look at related tasks within the process to improve understanding and communication of the process.
has super-classes
action
activity
is in domain of
has taskop

Information Itemc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#InformationItem

Information items are process products that are of particular interest to life cycle management. Information items are separately identifiable bodies of information that are produced and stored for human use during a system or software life cycle. In other words they are the outputs from and inputs to system and software life cycle processes and are transformed by these processes.
has super-classes
information entity
is in range of
has information itemop

Process Outcomec back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#ProcessOutcome

Observable result of the successful achievement of the process purpose

Software Lifecycle Processc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#SoftwareLifecycleProcess

The generic software lifecycle process. It is a specialisation of the Process entity from the DUL ontology. ISO:12207: set of interrelated or interacting activities which transforms inputs into outputs
has super-classes
process
is in domain of
has activityop, has information itemop

Taskc back to ToC or Class ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#Task

Tasks are written to define specific requirements, or provide recommendations on the execution of a conforming process. A task is expressed in the form of a requirement, recommendation, or permissible action, intended to support the achievement of the outcomes of a process.
has super-classes
action

Object Properties

has activityop back to ToC or Object Property ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#hasActivity

A relationship between the Software Lifecycle Process and the activities it incorporates.
has super-properties
has component
has domain
Software Lifecycle Processc
has range
activity

has information itemop back to ToC or Object Property ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#hasInformationItem

A relationship between the Software Lifecycle Process and the information item defined for it.
has super-properties
has component
has domain
Software Lifecycle Processc
has range
Information Itemc

has outcomeop back to ToC or Object Property ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#hasOutcome

A relationship between the process and its outcome.

has taskop back to ToC or Object Property ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#hasTask

A relationship between the task and the activity it is associated with.
has super-properties
associated with
has component
has domain
Activityc
has range
task

Data Properties

has Purposedp back to ToC or Data Property ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#hasPurpose

The purpose of the process is stated as a high level, overall goal for performing the process. In cases where processes might be thought to overlap, the purpose should be used to characterize the scope or bounds of the process. Whenever possible, the purpose should be succinctly captured in a single sentence.

has Titledp back to ToC or Data Property ToC

IRI: http://aligned.cs.ox.ac.uk/ontologies/slo#hasTitle

The title of a process description is a short noun phrase that presents a descriptive heading for the process. The title identifies the principle concern of the process and distinguishes the process from other processes in the model.

Namespace Declarations back to ToC

default namespace
http://aligned.cs.ox.ac.uk/ontologies/slo#
dc
http://purl.org/dc/elements/1.1/
dul
http://www.ontologydesignpatterns.org/ont/dul/
dul-owl
http://www.ontologydesignpatterns.org/ont/dul/DUL.owl#
images
http://aligned.cs.ox.ac.uk/images/
ontologies
http://aligned.cs.ox.ac.uk/ontologies/
owl
http://www.w3.org/2002/07/owl#
prov
http://www.w3.org/ns/prov#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
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.