Auflistung nach Autor:in "Winkler, Dietmar"
1 - 2 von 2
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragChristian Doppler Laboratory on Security and Quality Improvement in the Production Systems Life Cycle(Software Engineering 2020, 2020) Winkler, Dietmar; Biffl, StefanThe size and complexity of software components in production systems engineering, such as manufacturing plants or automation systems, requires effective and efficient approaches for security and quality improvement. In industrial practice, engineers from different disciplines, such as electrical, mechanical, and software disciplines typically follow a plan-driven and sequential engineering process approach with parallel engineering activities within a heterogeneous set of methods and tools. Therefore, major challenges concern (a) insufficient data exchange capabilities between disciplines, (b) a lack of consistency evaluation capabilities across disciplines, tools, and engineering phases, (c) insufficient knowledge representation and exchange between disciplines and project stakeholders and (d) limited security considerations. The goal of the Christian Doppler Laboratory on Security and Quality Improvement in the Production Systems Life Cycle (CDL-SQI) is to address these challenges in cooperation with industry partners in the production systems domain. We build on requirements and use case explorations at industry partners and on best-practices from Business Informatics to develop concepts and prototype solutions for the target domain and evaluate these concepts and prototypes in close collaboration with industry partners We derive requirements, use cases, and test data from industry and provide concepts and prototypes to the industry partner and to related scientific communities.
- ConferencePaperStatus Quo in Requirements Engineering: A Theory and a Global Family of Surveys(Software Engineering 2021, 2021) Wagner, Stefan; Fernández, Daniel Méndez; Felderer, Michael; Vetrò, Antonio; Kalinowski, Marcos; Wieringa, Roel; Pfahl, Dietmar; Conte, Tayana; Christiansson, Marie-Therese; Greer, Desmond; Lassenius, Casper; Mänistö,Tomi; Nayebi, Maleknaz; Oivo, Markku; Penzenstadler, Birgit; Prikladnicki, Rafael; Ruhe, Guenther; Schekelmann, André; Sen, Sagar; Spínola, Rodrigo; Tuzcu, Ahmed; de la Vara, Jose Luis; Winkler, DietmarThis paper reports on the second run of the Naming the Pain in Requirements Engineering (NaPiRE) initiative that has the goal to characterise requirements engineering practice and problems and was published in the ACM Transactions on Software Engineering and Methodology in 2019. Requirements Engineering (RE) has established itself as a software engineering discipline over the past decades. While researchers have been investigating the RE discipline with a plethora of empirical studies, attempts to systematically derive an empirical theory in context of the RE discipline have just recently been started. However, such a theory is needed if we are to define and motivate guidance in performing high quality RE research and practice. We aim at providing an empirical and externally valid foundation for a theory of RE practice, which helps software engineers establish effective and efficient RE processes in a problem-driven manner. We designed a survey instrument and an engineer-focused theory that was first piloted in Germany and, after making substantial modifications, has now been replicated in 10 countries world-wide. We have a theory in the form of a set of propositions inferred from our experiences and available studies, as well as the results from our pilot study in Germany. We evaluate the propositions with bootstrapped confidence intervals and derive potential explanations for the propositions. In this article, we report on the design of the family of surveys, its underlying theory, and the full results obtained from the replication studies conducted in 10 countries with participants from 228 organisations. Our results represent a substantial step forward towards developing an empirical theory of RE practice. The results reveal, for example, that there are no strong differences between organisations in different countries and regions, that interviews, facilitated meetings and prototyping are the most used elicitation techniques, that requirements are often documented textually, that traces between requirements and code or design documents are common, that requirements specifications themselves are rarely changed and that requirements engineering (process) improvement endeavours are mostly internally driven. Our study establishes a theory that can be used as starting point for many further studies for more detailed investigations. Practitioners can use the results as theory-supported guidance on selecting suitable RE methods and techniques.