05 Fakultät Informatik, Elektrotechnik und Informationstechnik

Permanent URI for this collectionhttps://elib.uni-stuttgart.de/handle/11682/6

Browse

Publication Type: search.filters.UBSTyp.KonferenzbeitragAuthor: search.filters.author.Kalinowski, Marcos

Search Results

Now showing 1 - 3 of 3
  • Thumbnail Image
    ItemOpen Access
    Towards building knowledge on causes of critical requirements engineering problems
    (2015) Kalinowski, Marcos; Spínola, Rodrigo Oliveira; Conte, Tayana; Prikladnicki, Rafael; Méndez Fernández, Daniel; Wagner, Stefan
    [Context] Many software projects fail due to problems in requirements engineering (RE). [Objective] The goal of this paper is to gather information on relevant RE problems and to represent knowledge on their most common causes. [Method] We replicated a global family of RE surveys in the Brazil and used the data to identify critical RE problems and to build probabilistic cause-effect diagrams to represent knowledge on their common causes. [Results] The survey was answered by 74 different organizations, including small, medium and very large sized companies, conducting both, plan-driven and agile development. The most critical RE problems, according to those organizations, are related to communication and to incomplete or underspecified requirements. We provide the full probabilistic cause-effect diagrams with knowledge on common causes of the most critical identified RE problems online. [Conclusion] We believe that the knowledge presented in the diagrams can be helpful to support organizations in conducting causal analysis sessions by providing an initial understanding on what usually causes critical RE problems.
  • Thumbnail Image
    ItemOpen Access
    Towards guidelines for preventing critical requirements engineering problems
    (2016) Mafra, Priscilla; Kalinowski, Marcos; Méndez Ferández, Daniel; Felderer, Michael; Wagner, Stefan
    [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.
  • Thumbnail Image
    ItemOpen Access
    Preventing incomplete/hidden requirements: reflections on survey data from Austria and Brazil
    (2015) Kalinowski, Marcos; Felderer, Michael; Conte, Tayana; Spinola, Rodrigo; Prikladnicki, Rafael; Winkler, Dietmar; Méndez Fernández, Daniel; Wagner, Stefan
    [Context] Many software projects fail due to problems in requirements engineering (RE). [Goal] The goal of this paper is analyzing a specific and relevant RE problem in detail: incomplete/hidden requirements. [Method] 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. [Results] 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. [Conclusions] 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.