Acronym | REQSPECONTO |
Visibility | Public |
Description | Software Requirements Specification Ontology (ReqSpecOnto) was a project of Knowledge System Research Labs by Usman Ahmed and Dr. Khuram Shahzad for the purpose of specifying unambiguous software requirements specification for a given software. It was made open-source with MIT's open-source license in June 2020. It consists of 100 terms including the classification of functional, and non-functional software requirements. The upper Ontology (classes, sub-classes, object properties, data properties, etc) part is the generic ontology for requirements specification of any software system while the Derived Ontology (individuals) part in this ontology can refer to a specific software under consideration. |
Status | Production |
Format | OWL |
Contact | Usman Ahmed, osmaanahmed@yahoo.com |
Categories | Computer Science, systems and electrical engineering |
Groups | IOF WG |
URI | http://www.semanticweb.org/usmanahmed/ontologies/2018/4/untitled-ontology-7 |
abstract | The specification of customers’ need as software requirements in natural language create ambiguities (in the requirements) and may fail the software project. Generally, customers are unable to define their needs due to the lack of domain understanding, technological constraints, and knowledge gap between the stakeholders and the requirements analysts. One of the most effective approaches to minimize these gaps and ambiguities for requirements specification and validation is the use of ontologies. However, the current approaches are mostly limited to the translation of ambiguous software requirements. This paper discussed, analyzed and compared the current usage of these ontologies and found that these approaches are time-consuming and create complexities in the overall development process. It presented a requirements specification ontology (ReqSpecOnto), bypassing the need for creating an ambiguous Software Requirement Specification (SRS). The upper software requirements ontology is defined in Ontology Web Language (OWL) which can be applied to different software scenarios. A case study of budget and planning system for a state physics lab was selected to specify its requirements as derived ontology from the upper ontology created. The results are validated through HermiT and Pellet reasoners to verify the defined relationships and constraints. Finally, SPARQL queries were used to obtain the necessary requirements. |
audience | Software Industry, Systems Analysts |
deprecated | false |
designed For Ontology Task | http://omv.ontoware.org/2005/05/ontology#ConfigurationTask |
example Identifier | http://www.semanticweb.org/usmanahmed/ontologies/2018/4/untitled-ontology-7#Request |
Contributors | Dr. Khuram Shahzad |
Creators | Usman Ahmed |
has Domain | https://data.industryportal.enit.fr/categories/Electrical |
has License | |
Ontology Syntax | http://www.w3.org/ns/formats/OWL_XML |
identifier | http://www.semanticweb.org/usmanahmed/ontologies/2018/4/untitled-ontology-7 |
keywords | ontology engineering, requirements specification ontology, semantic relations, software requirements,upper ontology |
known Usage | Specification of unambiguous Software Requirements |
Natural Language | |
Release date | 2020-06-27T00:00:00+00:00 |
URI Lookup Endpoint | http://193.50.189.11:8080/search?ontologies=REQSPECONTO&require_exact_match=true&q= |
use Guidelines | Create an instance of this Upper Ontology as a derived ontology for the specification of specific software under consideration. |
used Ontology Engineering Tool | http://protege.stanford.edu |
version | 1.0 |
No views of REQSPECONTO available
Classes | 96 |
Individuals | 24 |
Properties | 51 |
Maximum depth | 7 |
Maximum number of children | 10 |
Average number of children | 3 |
Classes with a single child | 3 |
Classes with more than 25 children | 0 |
Classes with no definition | 36 |
We are still collecting data for REQSPECONTO
No projects using REQSPECONTO