NFR+ framework method to support bi-directional traceability of non-functional requirements

Accurate and correctly defined requirements are of importance to ensure the production of feasible products. For requirements engineering, it is not enough that functional requirements are accurately defined and considered in software development but vital non-functional requirements require special attention because they often are cross-cutting concerns and difficult to interpret during design. Not only requirements have to be carefully considered but they also have to be implemented and the implementation must be validated against the original requirements. This is facilitated if a bi-directional traceability link between requirements and implementation is maintained. NFR+ Framework supported by a tool enables to do that in the context of Domain-Specific Modeling (DSM). In this publication, we propose a method for applying such a framework supported by a tool to enable maintaining a bi-directional traceability link between in the development process phases with careful attention on maintaining traceability over different typical tool boundaries existing in the context of DSM.

[1]  C. Ebert.  Putting requirement management into praxis: dealing with nonfunctional requirements , 1998, Inf. Softw. Technol..

[2]  Eila Niemelä,et al.  The impact of maintainability on component-based software systems , 2003, 2003 Proceedings 29th Euromicro Conference.

[3]  Daniel Gross,et al.  From Non-Functional Requirements to Design through Patterns , 2001, Requirements Engineering.

[4]  Juha-Pekka Tolvanen,et al.  Domain-Specific Modeling: Enabling Full Code Generation , 2008 .

[5]  M. Mari,et al.  The impact of maintainability on component-based software systems , 2003, 2003 Proceedings 29th Euromicro Conference.

[6]  Dorothy R. Graham,et al.  Requirements and Testing: Seven Missing-Link Myths , 2002, IEEE Softw..

[7]  Janne Merilinna,et al.  Extending the NFR Framework with Measurable NonFunctional Requirements , 2009, NFPinDSML@MoDELS.

[8]  John Mylopoulos,et al.  Non-Functional Requirements in Software Engineering , 2000, International Series in Software Engineering.

[9]  Clémentine Nebut,et al.  Model-Driven Engineering for Requirements Analysis , 2007, 11th IEEE International Enterprise Distributed Object Computing Conference (EDOC 2007).

[10]  Lawrence Chung,et al.  NFR-Assistant: tool support for achieving quality , 1999, Proceedings 1999 IEEE Symposium on Application-Specific Systems and Software Engineering and Technology. ASSET'99 (Cat. No.PR00122).

[11]  Julio Cesar Sampaio do Prado Leite,et al.  Nonfunctional requirements: from elicitation to conceptual models , 2004, IEEE Transactions on Software Engineering.

[12]  Paul Clements,et al.  ATAM: Method for Architecture Evaluation , 2000 .

[13]  Janne Merilinna.  A Tooling Environment for Quality-Driven Domain-Specific Modelling , 2009 .

[14]  Tomi Räty,et al.  Bridging the Gap between the Quality Requirements and Implementation , 2009, 2009 Fourth International Conference on Software Engineering Advances.

[15]  Janne Merilinna,et al.  Verification and validation in the context of domain-specific modelling , 2010, DSM '10.

[16]  Aniruddha S. Gokhale,et al.  Domain-Specific Modeling , 2008, Handbook of Dynamic System Modeling.

[17]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[18]  Janne Merilinna,et al.  Tooling for the full traceability of non-functional requirements within model-driven development , 2010, ECMFA-TW '10.

[19]  Ferhat Khendek,et al.  Fault coverage in testing real-time systems , 1999, Proceedings Sixth International Conference on Real-Time Computing Systems and Applications. RTCSA'99 (Cat. No.PR00306).