Enterprise Information Processing Domain-specific Meta-Model
type: Ontology
date: 05-02-2016
version info: 1.11.000
creator: Bojan Bozic (bozicb@scss.tcd.ie)
description: The purpose of the Enterprise Information Processing Domain-specific Meta-Model is to provide a set of concrete entities, agents, activities, and roles to represent the data engineering process. It is based on the general Data Lifecycle Ontology. The initial information gathered to build the domain-specific enterprise information processing metamodel is based on the JURION use case. The JURION use case includes both processes for data and software development and therefore uses the data lifecycle ontology and the software lifecycle ontology. The ontology models mandatory data requirements for specific processes and checks if they are fulfilled. The location of error occurence within the process is registered and the type of error or incosistency asserted. Furthermore, we capture how many errors occured, in which dataset they were detected, what was responsible for it, who fixed it, when was it fix, and how long does fixing take. Captured information about the dataset include publishing, versioning, and properties. Functionalities are associated to specific datasets and changing of data is tracked. Other areas of interest are links and how they behave especially when linking eternal data sources as well as mapping ontologies and information of processes about external data changes. This ontology imports the W3C PROV ontology available at http://www.w3c.org/TR/prov-o/. It is derived from the Data Lifecycle Ontology available at http://aligned-project.eu/ontologies/dlo.
comment: This ontology provides a description of the data lifecycle for enterprise information processing. It models both the data and the software lifecycle on the example of the JURION platform. Furthermore, it supports different kinds of entities, users, and versioning.
publisher: Wolters Kluwer
imports: dlo

hasBuildMetadata
type: DatatypeProperty
domain: Version
range: string
comment: Build meta-data as string is a place for potential future growth of the model, depending on use cases.

Transformation
type: Class
subclass of: DataLifecycleProcess
subclass of: SoftwareLifecycleProcess
comment: Transformation is a data and software lifecycle process which is the base class for several subprocesses for changing data or software artefacts.

Schema Authoring
type: Class
subclass of: Authoring
comment: Creation of a schema as a data lifecycle process.

Data Authoring
type: Class
subclass of: Authoring
comment: Generation of data as a data lifecycle process.

Content Architect
type: Class
subclass of: DataEngineer
comment: Person responsible for the content of a software system.

Customer
type: Class
subclass of: User
comment: Person who is involved in requirement engineering and usage of the software or data product.

Legal Domain Expert
type: Class
subclass of: DomainExpert
comment: Person who is an expert for legal issues in a certain domain.

Legal Editor
type: Class
subclass of: DataProcessPerson
comment: Person who edits legal documents for a software or data system.

Product Owner
type: Class
subclass of: DataProcessPerson
comment: Person who owns and uses the end product.

Schema Expert
type: Class
subclass of: DataEngineer
comment: Person who is an expert in development of schemas for a data system.

Software Analyst
type: Class
subclass of: DataProcessPerson
comment: Person responsible for analysing software systems and requirements engineering.

Software Developer
type: Class
subclass of: DataProcessPerson
comment: Person responsible for development of software systems.

Software Manager
type: Class
subclass of: DataProcessPerson
comment: Person responsible for management of software engineering projects.

Software Tester
type: Class
subclass of: DataProcessPerson
comment: Person responsible for testing software systems before releases.

CMS Expert
type: Class
subclass of: DataProcessPerson
comment: Person who is an expert in development and management of content management systems.

Internal Data
type: Class
subclass of: ProcessOutcome
comment: Unspecified internal system data.

Controlled Vocabulary
type: Class
subclass of: ProcessOutcome
comment: A controlled vocabulary process outcome.

Issue Ticket
type: Class
subclass of: ProcessOutcome
comment: A bug report in a software system.

Requirements Document
type: Class
subclass of: ProcessOutcome
comment: A requirements document as output of requirements engineering.

Schema Change
type: Class
subclass of: ProcessOutcome
comment: A document describing the change of schema for a sofware or data system.

Server Infrastructure
type: Class
subclass of: ProcessOutcome
comment: The server infrastructure on which a software or data system is deployed.

Data Source
type: Class
subclass of: ProcessOutcome
comment: The data source for a specific kind of data.

Source File
type: Class
subclass of: ProcessOutcome
comment: A source file containing source code in a specific programming language.

Source Code
type: Class
subclass of: ProcessOutcome
comment: An unspecified amount (collection) of source code in a specific programming language.

Test Case
type: Class
subclass of: ProcessOutcome
comment: A test case which tests one specific aspect of a software system.

Testing Suite
type: Class
subclass of: ProcessOutcome
comment: A collection of test cases for a software system.

Test File
type: Class
subclass of: ProcessOutcome
comment: A file containing test suites and/or test cases for a software system.

Version
type: Class
comment: Versioning model according to Semantic Versioning (http://semver.org/).
subclass of: Restriction
  on property: hasMinor
  some values from: nonNegativeInteger
subclass of: Restriction
  on property: hasPatch
  some values from: nonNegativeInteger
subclass of: Restriction
  on property: hasMajor
  some values from: nonNegativeInteger