Holistic Requirements for Interdisciplinary Development Processes

In modern systems, complexity rises stronger than the strength of discipline specific development methods. This leads to a gap in adequate engineering. Developers for e.g. mechatronic systems especially struggle with software intensive systems. Systems engineering offers certain methods to handle this complexity. Nevertheless, potential is still not fully used concerning requirements. Naturally, those determine the goals of the system to be developed and provide synergy effects within development processes. A closer look shows a lack of comprehension of requirements in the context of interdisciplinary system development and some clear challenges. Especially traditional engineering and software engineering can benefit from a common understanding of requirements. Therefore, an analysis of challenges is provided within this work. To tackle these, a systematic process is shown to integrate different levels into an interdisciplinary development process. This contribution discusses differences and synergy potentials from traditional and software engineering for technical requirements in an abstract and generic context. One possible solution is provided by the briefly described approach of the N3 matrix.

[1]  Jeffrey C. Carver,et al.  A systematic literature review to identify and classify software requirement errors , 2009, Inf. Softw. Technol..

[2]  Gerhard Pahl,et al.  Konstruktionslehre : Handbuch für Studium und Praxis , 1977 .

[3]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[4]  Christoph Jung Anforderungsklärung in interdisziplinärer Entwicklungsumgebung , 2006 .

[5]  Olivia Penas,et al.  SAMOS for Spatial Architecture based on Multi-physics and Organisation of Systems in conceptual design , 2015, 2015 IEEE International Symposium on Systems Engineering (ISSE).

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

[7]  James Robertson,et al.  Mastering the Requirements Process: Getting Requirements Right , 2012 .

[8]  Daniel M. Berry,et al.  The impact of domain knowledge on the effectiveness of requirements idea generation during requirements elicitation , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).

[9]  Herbert A. Simon,et al.  The Structure of Ill Structured Problems , 1973, Artif. Intell..

[10]  Ansgar Trächtler,et al.  Consistency analysis for requirements, functions, and system elements: Requirements for the entire development process , 2016, 2016 Annual IEEE Systems Conference (SysCon).

[11]  Marc Frappier,et al.  19 - A Comparison of the Specification Methods , 2010 .

[12]  Nelly Bencomo,et al.  Requirements-Aware Systems: A Research Agenda for RE for Self-adaptive Systems , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[13]  Rogério de Lemos,et al.  08031 -- Software Engineering for Self-Adaptive Systems: A Research Road Map , 2008, Software Engineering for Self-Adaptive Systems.

[14]  D.R. Lindstrom,et al.  Five ways to destroy a development project (software development) , 1993, IEEE Software.

[15]  Matthias Rauterberg,et al.  Partizipative Modellbildung zur Optimierung der Softwareentwicklung , 1992, IS/KI.

[16]  Eugenio Brusa,et al.  Integration of heterogeneous functional-vs-physical simulation within the industrial system design activity , 2015, 2015 IEEE International Symposium on Systems Engineering (ISSE).

[17]  P. Zave,et al.  Specifying software requirements , 1980, Proceedings of the IEEE.

[18]  Haralambos Mouratidis,et al.  Software Engineering for Secure Systems: Industrial and Research Perspectives , 2010 .

[19]  Tetsuo Tomiyama,et al.  Towards automation of control software: A review of challenges in mechatronic design , 2010 .