A DSL for importing models in a requirements management system

Requirements are artefacts often described with text and models. It is important to manage traceability between requirements and other software artefacts, including designs and test cases, also often captured with specialized models. Some Requirements Management Systems (RMS) support traceability relationships, between (textual) requirements artefacts in the RMS and model artefacts created outside the RMS, through complex standards or proprietary solutions. This paper proposes a new Domain-Specific Language (DSL) for describing the concepts of a modeling language intended to be traced using an RMS, with tool support handling the import and re-import of models and of their traceability links. The Model Import DSL (MI-DSL) is supported by an Xtext-based editor and the automatic generation of an import library targeting a leading RMS, namely IBM Rational DOORS. The language and the tools are demonstrated for model import and evolution scenarios with two different modeling languages. This work contributes a simple yet reliable mechanism to define and support traceability between requirements and models from different tools.

[1]  Bo Jiang.  Combining graphical scenarios with a requirements management system , 2005 .

[2]  Patrick Mäder,et al.  Software traceability: trends and future directions , 2014, FOSE.

[3]  Jane Cleland-Huang,et al.  A visual language for modeling and executing traceability queries , 2012, Software & Systems Modeling.

[4]  Tiberiu Seceleanu,et al.  Embedded Systems Design Flows: Integrating Requirements Authoring and Design Tools , 2013, 2013 39th Euromicro Conference on Software Engineering and Advanced Applications.

[5]  Andreas Graf,et al.  Requirements, Traceability and DSLs in Eclipse with the Requirements Interchange Format (ReqIF) , 2011, CSDM.

[6]  Daniel Amyot,et al.  Goal and scenario modeling, analysis, and transformation with jUCMNav , 2009, 2009 31st International Conference on Software Engineering - Companion Volume.

[7]  Daniel Amyot,et al.  Towards Integrated Tool Support for the User Requirements Notation , 2006, SAM.

[8]  Richard F. Paige,et al.  Engineering a DSL for Software Traceability , 2009, SLE.

[9]  Bo Jiang,et al.  Traceability and Evaluation in Scenario Analysis by Use Case Maps , 2003, Scenarios: Models, Transformations and Tools.

[10]  Daniel Amyot,et al.  Towards a Framework for Tracking Legal Compliance in Healthcare , 2007, CAiSE.

[11]  Daniel Amyot,et al.  User Requirements Notation: The First Ten Years, The Next Ten Years (Invited Paper) , 2011, J. Softw..

[12]  Maged Elaasar,et al.  Integrating Modeling Tools in the Development Lifecycle with OSLC: A Case Study , 2013, MoDELS.

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

[14]  Vijay K. Vaishnavi,et al.  Design Science Research Methods and Patterns: Innovating Information and Communication Technology , 2007 .

[15]  Carl K. Chang,et al.  Event-Based Traceability for Managing Evolutionary Change , 2003, IEEE Trans. Software Eng..

[16]  Patrick Mäder,et al.  Towards automated traceability maintenance , 2012, J. Syst. Softw..

[17]  Jane Cleland-Huang,et al.  A tactic-centric approach for automating traceability of quality concerns , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[18]  Anisur Rahman.  A Domain-Specific Language for Traceability in Modeling , 2013 .

[19]  Daniel Amyot,et al.  Integrating an Eclipse-Based Scenario Modeling Environment with a Requirements Management System , 2006, 2006 Canadian Conference on Electrical and Computer Engineering.