A Framework for Multi-layered Requirements Documentation and Analysis

The complexity of current software-intensive systems must be tackled during all phases of the system life cycle. Requirements Engineering is considered both by practitioners and researchers a crucial phase of software development. This article tackles requirements complexity by proposing a framework to document and analyze requirements at different levels of detail, inspired by the layered style of software architecture. Therefore, separation of concerns, an important concept used for software design, is applied in the context of requirements documentation and analysis. The framework has been applied in practice to design software-intensive systems in many domains. Specifically for this article, the proposal is to apply the framework to document and to analyze requirements for road traffic management systems.

[1]  Edsger W. Dijkstra,et al.  Selected Writings on Computing: A personal Perspective , 1982, Texts and Monographs in Computer Science.

[2]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[3]  Kent L. Beck,et al.  Extreme programming explained - embrace change , 1990 .

[4]  Mary Shaw,et al.  An Introduction to Software Architecture , 1993, Advances in Software Engineering and Knowledge Engineering.

[5]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[6]  Gerald W. Both,et al.  Object-oriented analysis and design with applications , 1994 .

[7]  Anthony J. H. Simons,et al.  Use cases considered harmful , 1999, Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275).

[8]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[9]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[10]  Martin Glinz,et al.  Problems and deficiencies of UML as a requirements specification language , 2000, Tenth International Workshop on Software Specification and Design. IWSSD-10 2000.

[11]  Mabo Ito,et al.  1.6.2 Formalizing a Structured Natural Language Requirements Specification Notation , 2002 .

[12]  Alain Abran,et al.  Fundamental principles of software engineering - a journey , 2002, J. Syst. Softw..

[13]  T.C. Lethbridge,et al.  Guide to the Software Engineering Body of Knowledge (SWEBOK) and the Software Engineering Education Knowledge (SEEK) - a preliminary mapping , 2001, 10th International Workshop on Software Technology and Engineering Practice.

[14]  Bashar Nuseibeh,et al.  Relating software requirements and architectures using problem frames , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[15]  Daniel M. Berry,et al.  The Inevitable Pain of Software Development: Why There Is No Silver Bullet , 2002, RISSEF.

[16]  Seija Komi-Sirviö,et al.  Great Challenges and Opportunities of Distributed Software Development - An Industrial Survey , 2003, International Conference on Software Engineering and Knowledge Engineering.

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

[18]  Daniela E. Damian,et al.  An Industrial Case Study of Immediate Benefits of Requirements Engineering Process Improvement at the Australian Center for Unisys Software , 2004, Empirical Software Engineering.

[19]  Jocelyn Armarego,et al.  Requirements Engineering: a close look at industry needs and a model curricula , 2005, Australas. J. Inf. Syst..

[20]  Erik Kamsties,et al.  Understanding Ambiguity in Requirements Engineering , 2005 .

[21]  Jos L. M. Vrancken,et al.  Model-Driven User Requirements Specification using SysML , 2008, J. Softw..

[22]  Grady Booch,et al.  Object-oriented analysis and design with applications, third edition , 2007, SOEN.

[23]  Jos L. M. Vrancken,et al.  A real-life test bed for multi-agent monitoring of road network performance , 2009, 2008 First International Conference on Infrastructure Systems and Services: Building Networks for a Brighter Future (INFRA).

[24]  Z. Lukszo,et al.  Intelligent Infrastructures , 2009 .

[25]  Remco C. de Boer,et al.  On the similarity between requirements and architecture , 2009, J. Syst. Softw..

[26]  Jos L. M. Vrancken,et al.  Architecture-based development of road traffic management systems , 2010, 2010 International Conference on Networking, Sensing and Control (ICNSC).

[27]  Nazim H. Madhavji,et al.  An exploratory study of architectural effects on requirements decisions , 2010, Journal of Systems and Software.

[28]  Alexander Verbraeck,et al.  User requirements modeling and analysis of software-intensive systems , 2011, J. Syst. Softw..