Documenting Software Requirements Specification Using R2UC Ontology
Elviawaty Muisa Zamzami, Eko Kuswardono Budiardjo · Zenodo (CERN European Organization for Nuclear Research) · 2012
It is quite common to represent Software Requirements Specification in text document, graphical model, formal model, prototype, or any combination of them. Meanwhile, Ontologies have been applied in software engineering, including requirements ontology. This paper describes an ontology approach on documenting SRS. It is convey ontology coined as Requirements Representation with Use Case (R2UC) Ontology. The oontology refers to elements of requirements specification in Requirements Management with Use Case (RMUC). The R2UC ontology can be used to describe software requirements that is captured in software engineering process or forward engineering process. The R2UC ontology represents the software requirements as the interpretation of software features. The software features as in solution domain fulfill stakeholder's needs or stake holder request as captured in problem domain. The R2UC ontology is modeled on three levels. The final level describes how software requirements will be specified. Requirements representation in R2UC ontology refers to Rational Unified Process (RUP) format. The R2UC ontology is implemented in OWL-DL language, developed using Protégé as graphical tools, OWLViz as visualization tool, and Pellet as reasoner.