Requirements Traceability Ontology to Support Requirements Management

Requirements management (RM) is an important phase in software requirements engineering that addresses changes in the requirements over time. Any effective ontology of requirements management needs to support the capturing of all the artefacts at every stage of the development life cycle along with a flexible granularity that fits the chosen development framework and project characteristics. One of the artefact types captured in the ontology should be the requirement to support the impact analysis in the requirements change management. We report on the Requirements Traceability Ontology (RTOnto) which is designed to support a flexible trace granularity by separating the ontology into three layers. The second and third layers of the ontology can be adapted to a specific development framework. Artefacts in the ontology are classified into eight sub-classes to enable capturing artefacts at every development life cycle.

[1]  Ivan A. Garcia,et al.  A serious game for teaching the fundamentals of ISO/IEC/IEEE 29148 systems and software engineering - Lifecycle processes - Requirements engineering at undergraduate level , 2020, Comput. Stand. Interfaces.

[2]  Juan Garbajosa,et al.  A study to support agile methods more effectively through traceability , 2011, Innovations in Systems and Software Engineering.

[3]  Steffen Lehnert.  Multiperspective Change Impact Analysis to Support Software Maintenance and Reengineering , 2015 .

[4]  Giuliano Antoniol,et al.  Traceability Fundamentals , 2012, Software and Systems Traceability.

[5]  Patricio Letelier.  A Framework for Requirements Traceability in UML-based Projects , 2002 .

[6]  Alexander Egyed,et al.  focus Requirements Conflicts and Cooperation: How Quality Attributes and Automated , 2004 .

[7]  Thanwadee Sunetnanta,et al.  Ontology-based multiperspective requirements traceability framework , 2010, Knowledge and Information Systems.

[8]  Katja Siegemund.  Contributions To Ontology-Driven Requirements Engineering , 2013 .

[9]  Thomas R. Gruber,et al.  A translation approach to portable ontology specifications , 1993 .

[10]  Vassilka Kirova,et al.  Effective requirements traceability: Models, tools, and practices , 2008, Bell Labs Technical Journal.

[11]  Alexander Egyed,et al.  Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help , 2004, IEEE Software.

[12]  S. Ghaisas,et al.  Knowledge-Assisted Ontology-Based Requirements Evolution , 2013, Managing Requirements Knowledge.

[13]  Bashar Nuseibeh,et al.  Characterizing Architecturally Significant Requirements , 2013, IEEE Software.

[14]  Kent Beck,et al.  Extreme Programming Explained: Embrace Change (2nd Edition) , 2004 .

[15]  V. Haarslev,et al.  An Ontology-based Approach for Traceability Recovery , 2006 .

[16]  Joselice Ferreira Lima,et al.  Building an Ontological Model for Software Requirements Engineering , 2011, CENTERIS.

[17]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[18]  Rosângela Dellosso Penteado,et al.  ObasCId(-Tool): an ontologically based approach for concern identification and classification and its computational support , 2017, Journal of the Brazilian Computer Society.

[19]  Peng Liang,et al.  Traceability in the Co-evolution of Architectural Requirements and Design , 2011, Relating Software Requirements and Architectures.

[20]  Ken Ptack,et al.  ISO/IEC JTC1 SC7 WG24 – ISO/IEC 29110 – Systems and Software Engineering – Life Cycle Profiles for Very Small Entities (VSEs) , 2014 .

[21]  Philippe Kruchten,et al.  The Rational Unified Process Made Easy - A Practitioner's Guide to the RUP , 2003, Addison Wesley object technology series.

[22]  S. Rohini,et al.  TOWARDS REFERENCE MODELS FOR REQUIREMENTS TRACEABILITY , 2019 .

[23]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[24]  Didar Zowghi,et al.  Constructing a Catalogue of Conflicts among Non-functional Requirements , 2010, ENASE.

[25]  Peter F. Patel-Schneider,et al.  OWL 2 Web Ontology Language Primer (Second Edition) , 2012 .

[26]  Kent L. Beck,et al.  Extreme programming explained - embrace change, Second Edition , 2005, The XP series.

[27]  Jeff Sutherland,et al.  The Scrum Guide , 2012 .