An IBIS Based Approach for the Analysis of Non-Functional Requirements

The design of complex systems is based on the needs and expectations of multiple stakeholders. Analysing such elements and transforming them into a rigorous system specification is a long and demanding task. This research is interested in supporting engineers and other stakeholders in the specification of system requirements with a focus on requirement analysis. The paper presents an approach to conduct analysis of non-functional requirements in a way that benefits both the engineers involved in the development of the current system, and those who will need to make improvements to it. The approach includes suggestions towards a tool, a representation, and a method. The tool is a software tool that specialises in capturing decision rationale known as Decision Rationale editor (DRed); the representation is adopted from the IBIS notation; the method is based on a model synthesised from literature on requirement analysis.Copyright © 2012 by Rolls-Royce plc

[1]  Dennis M. Buede,et al.  The Engineering Design of Systems: Models and Methods , 1999 .

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

[3]  Vincent Cheutet,et al.  A framework to support requirements analysis in engineering design , 2012 .

[4]  Bashar Nuseibeh,et al.  Managing inconsistencies in an evolving specification , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[5]  Lucienne Blessing,et al.  DRM, a Design Research Methodology , 2009 .

[6]  Raymond McCall,et al.  Rationale and Requirements Engineering , 2008 .

[7]  Vasant Dhar,et al.  Supporting Systems Development by Capturing Deliberations During Requirements Engineering , 1992, IEEE Trans. Software Eng..

[8]  Ljerka Beus-Dukic,et al.  Discovering Requirements: How to Specify Products and Services , 2009 .

[9]  Nick Hammond,et al.  Argumentation-based design rationale: what use at what cost? , 1994, Int. J. Hum. Comput. Stud..

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

[11]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[12]  Yoji Akao,et al.  Quality Function Deployment : Integrating Customer Requirements into Product Design , 1990 .

[13]  Steve McConnell,et al.  Rapid Development: Taming Wild Software Schedules , 1996 .

[14]  W. E. Rzepka.  A requirements engineering testbed: concept, status and first results , 1989, [1989] Proceedings of the Twenty-Second Annual Hawaii International Conference on System Sciences. Volume II: Software Track.

[15]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[16]  Kevin Otto,et al.  Product Design: Techniques in Reverse Engineering and New Product Development , 2000 .

[17]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[18]  Rob H. Bracewell,et al.  Capturing design rationale , 2009, Comput. Aided Des..