Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil

Many software projects fail due to problems in requirements engineering (RE). The goal of this paper is analyzing a specific and relevant RE problem in detail: incomplete/hidden requirements. We replicated a global family of RE surveys with representatives of software organizations in Austria and Brazil. We used the data to (a) characterize the criticality of the selected RE problem, and to (b) analyze the reported main causes and mitigation actions. Based on the analysis, we discuss how to prevent the problem. The survey includes 14 different organizations in Austria and 74 in Brazil, including small, medium and large sized companies, conducting both, plan-driven and agile development processes. Respondents from both countries cited the incomplete/hidden requirements problem as one of the most critical RE problems. We identified and graphically represented the main causes and documented solution options to address these causes. Further, we compiled a list of reported mitigation actions. From a practical point of view, this paper provides further insights into common causes of incomplete/hidden requirements and on how to prevent this problem.Comment: in Proceedings of the Software Quality Days, 201

Towards Guidelines for Preventing Critical Requirements Engineering Problems

Context] Problems in Requirements Engineering (RE) can lead to serious consequences during the software development lifecycle. [Goal] The goal of this paper is to propose empirically-based guidelines that can be used by different types of organisations according to their size (small, medium or large) and process model (agile or plan-driven) to help them in preventing such problems. [Method] We analysed data from a survey on RE problems answered by 228 organisations in 10 different countries. [Results] We identified the most critical RE problems, their causes and mitigation actions, organizing this information by clusters of size and process model. Finally, we analysed the causes and mitigation actions of the critical problems of each cluster to get further insights into how to prevent them. [Conclusions] Based on our results, we suggest preliminary guidelines for preventing critical RE problems in response to context characteristics of the companies.Comment: Proceedings of the 42th Euromicro Conference on Software Engineering and Advanced Applications, 201

System Evolution Barriers and How to Overcome Them!

Creating complex systems from scratch is time consuming and costly, therefore a strategy often chosen by companies is to evolve existing systems. Yet evolving a system is also complicated. Complex systems are usually the result of multidisciplinary teams, therefore it is essential to understand barriers those teams face when evolving a system.\ud From the research carried at Philips Healthcare MRI, we have identified that main evolution barriers employees face are; managing system complexity,communication across disciplines and departments, finding the necessary system information, lack of system overview, and ineffective knowledge sharing. Those barriers were identified as the root cause of many development problems and bad decisions.\ud To overcome those barriers, and therefore enhance the evolution process, effective reuse of knowledge is essential. This knowledge must be presented in a fashion that can be understood by a broad set of stakeholders. In this paper system evolution barriers and a method to effectively deal with them, based on the creation of A3 Architecture Overviews, is presented