Towards an Integrated Approach to Requirement Engineering

Requirements Engineering (RE) still constitutes the Achilles' heel of the entire software development activities. Even worse, there is a considerable gap between the state of the art in academic RE and in industrial RE. Although many academic RE approaches exhibit a high potential in practical application, they are not applied in practice. This report demonstrates that a set of approaches developed at the Technische Universitat Munchen can be integrated into one approach that covers most RE tasks. The aim of this integrated approach is to provide a comprehensive RE framework. In industrial practice, RE is influenced by a plethora of stakeholders. This makes it difficult to address the needs of every stakeholder and not loosing the big picture. The presented artefact-oriented approach provides a guideline that defines what should be specified so that the resulting set of requirements is as complete as possible. The approach is supported by adequate modeling techniques required to achieve the objectives of consistency and completeness in requirements specifications. The approach includes both general technical tasks, as proper writing of requirements documents or transition from requirements to design, and methodical issues, as structuring of requirements artefacts.

[1]  Jyrki Kontio,et al.  Software engineering risk management : a method, improvement framework, and empirical evaluation , 2001 .

[2]  Manfred Broy,et al.  SERVICE-ORIENTED SYSTEMS ENGINEERING: SPECIFICATION AND DESIGN OF SERVICES AND LAYERED ARCHITECTURES , 2005 .

[3]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[4]  B. Boehm Software risk management: principles and practices , 1991, IEEE Software.

[5]  Leonid Kof,et al.  Translation of Textual Specifications to Automata by Means of Discourse Context Modeling , 2009, REFSQ.

[6]  Marisa E. Campbell,et al.  Conference preview: HCI 2000: usability or else! , 2000, INTR.

[7]  Luisa Mich,et al.  Market research for requirements analysis using linguistic tools , 2004, Requirements Engineering.

[8]  Marco Pistore,et al.  Nusmv version 2: an opensource tool for symbolic model checking , 2002, CAV 2002.

[9]  Martín Abadi,et al.  Decomposing Specifications of Concurrent Systems , 1994, PROCOMET.

[10]  Rajeev Alur,et al.  Modular refinement of hierarchic reactive machines , 2004, TOPL.

[11]  Manfred Broy,et al.  Modulare hierarchische Modellierung als Grundlage der Software- und Systementwicklung , 2007, Informatik-Spektrum.

[12]  Albert Endres,et al.  A handbook of software and systems engineering - empirical observations, laws and theories , 2003, The Fraunhofer IESE series on software engineering.

[13]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.

[14]  James R. Curran,et al.  Multi-Tagging for Lexicalized-Grammar Parsing , 2006, ACL.

[15]  Manfred Broy,et al.  Formalizing the notion of adaptive system behavior , 2009, SAC '09.

[16]  Axel van Lamsweerde,et al.  Requirements Engineering: From System Goals to UML Models to Software Specifications , 2009 .

[17]  Egon Börger,et al.  The Stream Boiler Case Study: Competition of Formal Program Specification and Development Methods , 1995, Formal Methods for Industrial Applications.

[18]  Michael D. Harrison,et al.  The role of formal methods in human-computer interaction , 1990 .

[19]  Judea Pearl,et al.  Probabilistic reasoning in intelligent systems - networks of plausible inference , 1991, Morgan Kaufmann series in representation and reasoning.

[20]  Sebastian Winter,et al.  Modellbasierte Analyse von Nutzerschnittstellen , 2009 .

[21]  Edmund M. Clarke,et al.  Design and Synthesis of Synchronization Skeletons Using Branching Time Temporal Logic , 2008, 25 Years of Model Checking.

[22]  Bernhard Schätz,et al.  Model-Based Development of Embedded Systems , 2002, OOIS Workshops.

[23]  Manfred Broy,et al.  Service-Oriented Systems Engineering: Modeling Services and Layered Architectures , 2003, FORTE.

[24]  Maria Spichkova,et al.  A Top-Down Methodology for the Development of Automotive Software , 2009 .

[25]  Bernhard Schätz,et al.  A Refined Top-Down Methodology for the Development of Automotive Software Systems - The KeylessEntry-System Case Study - , 2011 .

[26]  Bashar Nuseibeh,et al.  Weaving the Software Development Process Between Requirements and Architectures , 2001 .

[27]  Shareeful Islam,et al.  Goal and Risk Factors in Offshore Outsourced Software Development from Vendor's Viewpoint , 2009, 2009 Fourth IEEE International Conference on Global Software Engineering.

[28]  Leonid Kof,et al.  Scenarios: Identifying Missing Objects and Actions by Means of Computational Linguistics , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).

[29]  Mike Mannion,et al.  SMART requirements , 1995, SOEN.

[30]  Andreas Fleischmann Modellbasierte Formalisierung von Anforderungen für eingebettete Systeme im Automotive-Bereich , 2008 .

[31]  Wassiou Olarewaju Sitou,et al.  Requirements-Engineering kontextsensitiver Anwendungen , 2009 .

[32]  Stefan Wagner,et al.  A literature survey of the quality economics of defect-detection techniques , 2006, ISESE '06.

[33]  Robert Winter,et al.  Method construction - a core approach to organizational engineering , 2005, SAC '05.

[34]  Eckhard D. Falkenberg,et al.  Concepts for Modelling Information , 1976, IFIP Working Conference on Modelling in Data Base Management Systems.

[35]  Terry Halpin,et al.  Information modeling and relational databases: from conceptual analysis to logical design , 2001 .

[36]  Thomas A. Henzinger Masaccio: A Formal Model for Embedded Components , 2000, IFIP TCS.

[37]  Herbert Hanselmann,et al.  Challenges in automotive software engineering , 2008, ICSE Companion '08.

[38]  Mark Green,et al.  Report on Dialogue Specification Tools , 1984, Comput. Graph. Forum.

[39]  James D. Herbsleb,et al.  Splitting the organization and integrating the code: Conway's law revisited , 1999, Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002).

[40]  Bernhard Schätz,et al.  Combining Aspects of Reactive Systems , 2003, Ershov Memorial Conference.

[41]  Leonid Kof Treatment of Passive Voice and Conjunctions in Use Case Documents , 2007, NLDB.

[42]  Leonid Kof Text analysis for requirements engineering , 2005 .

[43]  Sebastian Benz Combining test case generation for component and integration testing , 2007, A-MOST '07.

[44]  Kalle Lyytinen,et al.  Components of Software Development Risk: How to Address Them? A Project Manager Survey , 2000, IEEE Trans. Software Eng..

[45]  Bernhard Schäz Building Components from Functions , 2006, Electron. Notes Theor. Comput. Sci..

[46]  Leonid Kof Requirements Analysis: Concept Extraction and Translation of Textual Specifications to Executable Models , 2009, NLDB.

[47]  Wassiou Sitou,et al.  Towards Requirements Engineering for Context Adaptive Systems , 2007, 31st Annual International Computer Software and Applications Conference (COMPSAC 2007).

[48]  Robin Jeffries,et al.  User interface evaluation in the real world: a comparison of four techniques , 1991, CHI.

[49]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[50]  Shareeful Islam,et al.  Software development risk management model: a goal driven approach , 2009, ESEC/FSE Doctoral Symposium '09.

[51]  Leonid Kof From Textual Scenarios to Message Sequence Charts: Inclusion of Condition Generation and Actor Extraction , 2008, 2008 16th IEEE International Requirements Engineering Conference.

[52]  Sabine Rittmann,et al.  A methodology for modeling usage behavior of multi-functional systems , 2008 .

[53]  Sjaak Brinkkemper,et al.  Method engineering: engineering of information systems development methods and tools , 1996, Inf. Softw. Technol..