RE 2015 – Author Index |
Contents -
Abstracts -
Authors
|
Basirati, Mohammad R. |
RE '15-IND: "Understanding Changes in Use ..."
Understanding Changes in Use Cases: A Case Study
Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, and Alexander Widera (TU München, Germany; Munich Re, Germany) Requirements change and so (should) do requirements artifacts, such as use cases. However, we have little knowledge about which changes requirements engineers actually perform on use cases. We do not know what is changing, at which locations use cases change and need a deeper understanding of which changes are problematic in terms of difficult or risky. To explore these challenges from an industrial point of view, we conducted a mixed methods case study in which we analyze 15 month of changes in use cases in an industrial software project. The study provided interesting observations for both practitioners and researchers involved: First, the most frequently changing use cases had an issue in their structuring. Second, alternative flows (i.e., variations or extensions of the main flow) were especially prone to changes. Third, changes in content (semantic changes) and in presentation of the content (syntactic changes) happen similarly frequently. Last, a qualitative and quantitative analysis aiming at a deeper understanding of problematic changes identified taxonomy changes, as well as locally or temporally dispersed changes as particularly difficult and risky. In this paper, we contribute a first empirical inquiry for understanding the maintainability of use cases: The presented study provides empirical evidence that there are particular maintenance risks and suggests to continuously analyze local and temporal dispersion. @InProceedings{RE15p352, author = {Mohammad R. Basirati and Henning Femmer and Sebastian Eder and Martin Fritzsche and Alexander Widera}, title = {Understanding Changes in Use Cases: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {352--361}, doi = {}, year = {2015}, } |
|
Callele, David |
RE '15-IND: "Experience Requirements in ..."
Experience Requirements in Video Games: Definition and Testability
David Callele, Philip Dueck, Krzysztof Wnuk, and Peitsa Hynninen (Experience First Design, Canada; Blekinge Institute of Technology, Sweden; Aalto University, Finland) A properly formed requirement is testable, a necessity for ensuring that design goals are met. While challenging in productivity applications, entertainment applications such as games compound the problem due to their subjective nature. We report here on our efforts to create testable experience requirements, the associated scope challenges and challenges with test design and result interpretation. We further report on issues experienced when performing focus group testing and provide practitioner guidance. @InProceedings{RE15p324, author = {David Callele and Philip Dueck and Krzysztof Wnuk and Peitsa Hynninen}, title = {Experience Requirements in Video Games: Definition and Testability}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {324--333}, doi = {}, year = {2015}, } |
|
Dueck, Philip |
RE '15-IND: "Experience Requirements in ..."
Experience Requirements in Video Games: Definition and Testability
David Callele, Philip Dueck, Krzysztof Wnuk, and Peitsa Hynninen (Experience First Design, Canada; Blekinge Institute of Technology, Sweden; Aalto University, Finland) A properly formed requirement is testable, a necessity for ensuring that design goals are met. While challenging in productivity applications, entertainment applications such as games compound the problem due to their subjective nature. We report here on our efforts to create testable experience requirements, the associated scope challenges and challenges with test design and result interpretation. We further report on issues experienced when performing focus group testing and provide practitioner guidance. @InProceedings{RE15p324, author = {David Callele and Philip Dueck and Krzysztof Wnuk and Peitsa Hynninen}, title = {Experience Requirements in Video Games: Definition and Testability}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {324--333}, doi = {}, year = {2015}, } |
|
Eder, Sebastian |
RE '15-IND: "Understanding Changes in Use ..."
Understanding Changes in Use Cases: A Case Study
Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, and Alexander Widera (TU München, Germany; Munich Re, Germany) Requirements change and so (should) do requirements artifacts, such as use cases. However, we have little knowledge about which changes requirements engineers actually perform on use cases. We do not know what is changing, at which locations use cases change and need a deeper understanding of which changes are problematic in terms of difficult or risky. To explore these challenges from an industrial point of view, we conducted a mixed methods case study in which we analyze 15 month of changes in use cases in an industrial software project. The study provided interesting observations for both practitioners and researchers involved: First, the most frequently changing use cases had an issue in their structuring. Second, alternative flows (i.e., variations or extensions of the main flow) were especially prone to changes. Third, changes in content (semantic changes) and in presentation of the content (syntactic changes) happen similarly frequently. Last, a qualitative and quantitative analysis aiming at a deeper understanding of problematic changes identified taxonomy changes, as well as locally or temporally dispersed changes as particularly difficult and risky. In this paper, we contribute a first empirical inquiry for understanding the maintainability of use cases: The presented study provides empirical evidence that there are particular maintenance risks and suggests to continuously analyze local and temporal dispersion. @InProceedings{RE15p352, author = {Mohammad R. Basirati and Henning Femmer and Sebastian Eder and Martin Fritzsche and Alexander Widera}, title = {Understanding Changes in Use Cases: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {352--361}, doi = {}, year = {2015}, } |
|
Eliasson, Ulf |
RE '15-IND: "The Need of Complementing ..."
The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
Ulf Eliasson, Rogardt Heldal, Eric Knauss, and Patrizio Pelliccione (Volvo, Sweden; Chalmers University of Technology, Sweden; University of Gothenburg, Sweden) The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs. @InProceedings{RE15p372, author = {Ulf Eliasson and Rogardt Heldal and Eric Knauss and Patrizio Pelliccione}, title = {The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {372--381}, doi = {}, year = {2015}, } |
|
Femmer, Henning |
RE '15-IND: "Understanding Changes in Use ..."
Understanding Changes in Use Cases: A Case Study
Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, and Alexander Widera (TU München, Germany; Munich Re, Germany) Requirements change and so (should) do requirements artifacts, such as use cases. However, we have little knowledge about which changes requirements engineers actually perform on use cases. We do not know what is changing, at which locations use cases change and need a deeper understanding of which changes are problematic in terms of difficult or risky. To explore these challenges from an industrial point of view, we conducted a mixed methods case study in which we analyze 15 month of changes in use cases in an industrial software project. The study provided interesting observations for both practitioners and researchers involved: First, the most frequently changing use cases had an issue in their structuring. Second, alternative flows (i.e., variations or extensions of the main flow) were especially prone to changes. Third, changes in content (semantic changes) and in presentation of the content (syntactic changes) happen similarly frequently. Last, a qualitative and quantitative analysis aiming at a deeper understanding of problematic changes identified taxonomy changes, as well as locally or temporally dispersed changes as particularly difficult and risky. In this paper, we contribute a first empirical inquiry for understanding the maintainability of use cases: The presented study provides empirical evidence that there are particular maintenance risks and suggests to continuously analyze local and temporal dispersion. @InProceedings{RE15p352, author = {Mohammad R. Basirati and Henning Femmer and Sebastian Eder and Martin Fritzsche and Alexander Widera}, title = {Understanding Changes in Use Cases: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {352--361}, doi = {}, year = {2015}, } RE '15-IND: "Systematic Elicitation of ..." Systematic Elicitation of Mode Models for Multifunctional Systems Andreas Vogelsang, Henning Femmer, and Christian Winkler (TU München, Germany; MAN Truck & Bus, Germany) Many requirements engineering approaches structure and specify requirements based on the notion of modes or system states. The set of all modes is usually considered as the mode model of a system or problem domain. However, it is neither clear how such a mode model can be elicited systematically, nor whether it is realistic to elicit a mode model for a productive system with regard to size and comprehensibility. In this paper, we introduce three elicitation approaches for mode models. We applied the three approaches in an industrial automotive context and assessed the resulting mode models with respect to size, complexity, and differences to each other. Our results show that all elicitation approaches were capable of eliciting modes, which were structured in mode models with 20 to 42 modes. From these results, we conclude that it is possible to elicit manageable mode models for an entire system in a productive context. In our case, the practitioners decided to integrate our model in their feature specification and analysis process. @InProceedings{RE15p305, author = {Andreas Vogelsang and Henning Femmer and Christian Winkler}, title = {Systematic Elicitation of Mode Models for Multifunctional Systems}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {305--314}, doi = {}, year = {2015}, } |
|
Fritzsche, Martin |
RE '15-IND: "Understanding Changes in Use ..."
Understanding Changes in Use Cases: A Case Study
Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, and Alexander Widera (TU München, Germany; Munich Re, Germany) Requirements change and so (should) do requirements artifacts, such as use cases. However, we have little knowledge about which changes requirements engineers actually perform on use cases. We do not know what is changing, at which locations use cases change and need a deeper understanding of which changes are problematic in terms of difficult or risky. To explore these challenges from an industrial point of view, we conducted a mixed methods case study in which we analyze 15 month of changes in use cases in an industrial software project. The study provided interesting observations for both practitioners and researchers involved: First, the most frequently changing use cases had an issue in their structuring. Second, alternative flows (i.e., variations or extensions of the main flow) were especially prone to changes. Third, changes in content (semantic changes) and in presentation of the content (syntactic changes) happen similarly frequently. Last, a qualitative and quantitative analysis aiming at a deeper understanding of problematic changes identified taxonomy changes, as well as locally or temporally dispersed changes as particularly difficult and risky. In this paper, we contribute a first empirical inquiry for understanding the maintainability of use cases: The presented study provides empirical evidence that there are particular maintenance risks and suggests to continuously analyze local and temporal dispersion. @InProceedings{RE15p352, author = {Mohammad R. Basirati and Henning Femmer and Sebastian Eder and Martin Fritzsche and Alexander Widera}, title = {Understanding Changes in Use Cases: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {352--361}, doi = {}, year = {2015}, } |
|
Heldal, Rogardt |
RE '15-IND: "The Need of Complementing ..."
The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
Ulf Eliasson, Rogardt Heldal, Eric Knauss, and Patrizio Pelliccione (Volvo, Sweden; Chalmers University of Technology, Sweden; University of Gothenburg, Sweden) The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs. @InProceedings{RE15p372, author = {Ulf Eliasson and Rogardt Heldal and Eric Knauss and Patrizio Pelliccione}, title = {The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {372--381}, doi = {}, year = {2015}, } |
|
Holmegaard, Maria |
RE '15-IND: "Requirements Problems in the ..."
Requirements Problems in the Development of a New User Interface for Healthcare Equipment
Maria Holmegaard, Jens Bæk Jørgensen, Michael Sørensen Loft, and Martin Stig Stissing (Mjølner Informatics, Denmark) In August 2013, our company started work for an industrial customer. First, we developed a prototype and conducted field studies in small-scale projects. This was successful and the basis for a larger project about development of a new user interface for healthcare equipment. A main aim for us was to use this project as starting point for establishing a strategic, long-term relationship with this customer. However, we were not successful. In November 2014, our customer chose to take over the development themselves. We were too expensive, used too many hours and were not able to provide useful estimates, they said. In this paper, we describe the project and analyze causes to our customer’s decision. We also look at possible alternatives to the actions we took in the project and discuss whether we could have done better. A root cause to our customer’s dissatisfaction is related to requirements and handling of requirements. @InProceedings{RE15p315, author = {Maria Holmegaard and Jens Bæk Jørgensen and Michael Sørensen Loft and Martin Stig Stissing}, title = {Requirements Problems in the Development of a New User Interface for Healthcare Equipment}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {315--323}, doi = {}, year = {2015}, } |
|
Houdek, Frank |
RE '15-IND: "The Myth of Bad Passive Voice ..."
The Myth of Bad Passive Voice and Weak Words: An Empirical Investigation in the Automotive Industry
Jennifer Krisch and Frank Houdek (Daimler, Germany) In requirements engineering literature dealing with natural language specifications, we usually find writing rules like avoid passive voice or do not use weak words. Adhering to such rules should result in understandable and unambiguous requirements. Passive voice, especially when used without an explicit actor, is considered to result in incomplete requirements. The usage of weak words is considered to result in imprecise requirements that are hardly testable. But is the inversion of the claim correct, i.e. does the violation of the writing rules result in problematic specifications? At least in our environment (the passenger car development of Mercedes-Benz) we observe that authors often use passive voice, and there are many requirements containing weak words. To answer this question, we conducted an empirical investigation whose results we report in this paper. The results of this investigation are quite surprising: The use of passive voice, even when the actor is missing, is almost never problematic, as the missing information (the actor) can in most cases easily derived from the context (i.e. surrounding requirements or the general project context). The usage of weak words may be considered problematic in approximately 12% of all occurrences. For an automatic analysis on weak words linguistic patterns can be defined to detect these problematic occurrences. @InProceedings{RE15p344, author = {Jennifer Krisch and Frank Houdek}, title = {The Myth of Bad Passive Voice and Weak Words: An Empirical Investigation in the Automotive Industry}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {344--351}, doi = {}, year = {2015}, } |
|
Hynninen, Peitsa |
RE '15-IND: "Experience Requirements in ..."
Experience Requirements in Video Games: Definition and Testability
David Callele, Philip Dueck, Krzysztof Wnuk, and Peitsa Hynninen (Experience First Design, Canada; Blekinge Institute of Technology, Sweden; Aalto University, Finland) A properly formed requirement is testable, a necessity for ensuring that design goals are met. While challenging in productivity applications, entertainment applications such as games compound the problem due to their subjective nature. We report here on our efforts to create testable experience requirements, the associated scope challenges and challenges with test design and result interpretation. We further report on issues experienced when performing focus group testing and provide practitioner guidance. @InProceedings{RE15p324, author = {David Callele and Philip Dueck and Krzysztof Wnuk and Peitsa Hynninen}, title = {Experience Requirements in Video Games: Definition and Testability}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {324--333}, doi = {}, year = {2015}, } |
|
Jørgensen, Jens Bæk |
RE '15-IND: "Requirements Problems in the ..."
Requirements Problems in the Development of a New User Interface for Healthcare Equipment
Maria Holmegaard, Jens Bæk Jørgensen, Michael Sørensen Loft, and Martin Stig Stissing (Mjølner Informatics, Denmark) In August 2013, our company started work for an industrial customer. First, we developed a prototype and conducted field studies in small-scale projects. This was successful and the basis for a larger project about development of a new user interface for healthcare equipment. A main aim for us was to use this project as starting point for establishing a strategic, long-term relationship with this customer. However, we were not successful. In November 2014, our customer chose to take over the development themselves. We were too expensive, used too many hours and were not able to provide useful estimates, they said. In this paper, we describe the project and analyze causes to our customer’s decision. We also look at possible alternatives to the actions we took in the project and discuss whether we could have done better. A root cause to our customer’s dissatisfaction is related to requirements and handling of requirements. @InProceedings{RE15p315, author = {Maria Holmegaard and Jens Bæk Jørgensen and Michael Sørensen Loft and Martin Stig Stissing}, title = {Requirements Problems in the Development of a New User Interface for Healthcare Equipment}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {315--323}, doi = {}, year = {2015}, } |
|
Käpyaho, Marja |
RE '15-IND: "Agile Requirements Engineering ..."
Agile Requirements Engineering with Prototyping: A Case Study
Marja Käpyaho and Marjo Kauppinen (Futurice, Finland; Aalto University, Finland) The rise of agile software development methods has led to the abandonment of many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and the growing use of agile methods in large projects is forcing companies to look for more formal practices for RE. This paper describes experiences gained from a case study of a large agile project. The goal of this case study was to explore how prototyping can solve the challenges of agile RE. Our findings indicate that while prototyping can help with some challenges of agile RE such as lack of documentation, motivation for RE work and poor quality communication, it also needs complementary practices to reach its full potential. These practices include reviewing the big picture regularly, keeping track of quality requirements, and using ATDD (Acceptance Test Driven Development). Key words: prototyping, agile requirements engineering @InProceedings{RE15p334, author = {Marja Käpyaho and Marjo Kauppinen}, title = {Agile Requirements Engineering with Prototyping: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {334--343}, doi = {}, year = {2015}, } |
|
Kauppinen, Marjo |
RE '15-IND: "Agile Requirements Engineering ..."
Agile Requirements Engineering with Prototyping: A Case Study
Marja Käpyaho and Marjo Kauppinen (Futurice, Finland; Aalto University, Finland) The rise of agile software development methods has led to the abandonment of many traditional practices especially in requirements engineering (RE). Agile RE is still a relatively new research area and the growing use of agile methods in large projects is forcing companies to look for more formal practices for RE. This paper describes experiences gained from a case study of a large agile project. The goal of this case study was to explore how prototyping can solve the challenges of agile RE. Our findings indicate that while prototyping can help with some challenges of agile RE such as lack of documentation, motivation for RE work and poor quality communication, it also needs complementary practices to reach its full potential. These practices include reviewing the big picture regularly, keeping track of quality requirements, and using ATDD (Acceptance Test Driven Development). Key words: prototyping, agile requirements engineering @InProceedings{RE15p334, author = {Marja Käpyaho and Marjo Kauppinen}, title = {Agile Requirements Engineering with Prototyping: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {334--343}, doi = {}, year = {2015}, } |
|
Knauss, Eric |
RE '15-IND: "The Need of Complementing ..."
The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
Ulf Eliasson, Rogardt Heldal, Eric Knauss, and Patrizio Pelliccione (Volvo, Sweden; Chalmers University of Technology, Sweden; University of Gothenburg, Sweden) The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs. @InProceedings{RE15p372, author = {Ulf Eliasson and Rogardt Heldal and Eric Knauss and Patrizio Pelliccione}, title = {The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {372--381}, doi = {}, year = {2015}, } |
|
Krisch, Jennifer |
RE '15-IND: "The Myth of Bad Passive Voice ..."
The Myth of Bad Passive Voice and Weak Words: An Empirical Investigation in the Automotive Industry
Jennifer Krisch and Frank Houdek (Daimler, Germany) In requirements engineering literature dealing with natural language specifications, we usually find writing rules like avoid passive voice or do not use weak words. Adhering to such rules should result in understandable and unambiguous requirements. Passive voice, especially when used without an explicit actor, is considered to result in incomplete requirements. The usage of weak words is considered to result in imprecise requirements that are hardly testable. But is the inversion of the claim correct, i.e. does the violation of the writing rules result in problematic specifications? At least in our environment (the passenger car development of Mercedes-Benz) we observe that authors often use passive voice, and there are many requirements containing weak words. To answer this question, we conducted an empirical investigation whose results we report in this paper. The results of this investigation are quite surprising: The use of passive voice, even when the actor is missing, is almost never problematic, as the missing information (the actor) can in most cases easily derived from the context (i.e. surrounding requirements or the general project context). The usage of weak words may be considered problematic in approximately 12% of all occurrences. For an automatic analysis on weak words linguistic patterns can be defined to detect these problematic occurrences. @InProceedings{RE15p344, author = {Jennifer Krisch and Frank Houdek}, title = {The Myth of Bad Passive Voice and Weak Words: An Empirical Investigation in the Automotive Industry}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {344--351}, doi = {}, year = {2015}, } |
|
Loft, Michael Sørensen |
RE '15-IND: "Requirements Problems in the ..."
Requirements Problems in the Development of a New User Interface for Healthcare Equipment
Maria Holmegaard, Jens Bæk Jørgensen, Michael Sørensen Loft, and Martin Stig Stissing (Mjølner Informatics, Denmark) In August 2013, our company started work for an industrial customer. First, we developed a prototype and conducted field studies in small-scale projects. This was successful and the basis for a larger project about development of a new user interface for healthcare equipment. A main aim for us was to use this project as starting point for establishing a strategic, long-term relationship with this customer. However, we were not successful. In November 2014, our customer chose to take over the development themselves. We were too expensive, used too many hours and were not able to provide useful estimates, they said. In this paper, we describe the project and analyze causes to our customer’s decision. We also look at possible alternatives to the actions we took in the project and discuss whether we could have done better. A root cause to our customer’s dissatisfaction is related to requirements and handling of requirements. @InProceedings{RE15p315, author = {Maria Holmegaard and Jens Bæk Jørgensen and Michael Sørensen Loft and Martin Stig Stissing}, title = {Requirements Problems in the Development of a New User Interface for Healthcare Equipment}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {315--323}, doi = {}, year = {2015}, } |
|
Morciniec, Tobias |
RE '15-IND: "Using the Requirements Specification ..."
Using the Requirements Specification to Infer the Implicit Test Status of Requirements
Tobias Morciniec and Andreas Podelski (Daimler, Germany; University of Freiburg, Germany) We investigate a method to infer the implicit test status of requirements and thus increase the number of requirements for which the test status is known. The general idea is to improve the data set for measuring the maturity of the system in the current release. The inference is based on the structuring mechanisms (hierarchy, types) which are typically used to document the (natural language) requirements specification. We present a case study in the context of the development process for Mercedes-Benz passenger cars at Daimler AG. The results of the case study indicate the usefulness of the structuring mechanisms in the requirements specification as the basis for the inference. In particular, the number of requirements for which the status is known could be increased by almost a third. @InProceedings{RE15p362, author = {Tobias Morciniec and Andreas Podelski}, title = {Using the Requirements Specification to Infer the Implicit Test Status of Requirements}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {362--371}, doi = {}, year = {2015}, } |
|
Panis, Michael C. |
RE '15-IND: "Reuse of Architecturally Derived ..."
Reuse of Architecturally Derived Standards Requirements
Michael C. Panis (Teradyne, USA) Requirements reuse promises to reduce product development cost and improve product quality. Applying a standard set of requirements to multiple products configured into the same system can ensure all the products take advantage of the system’s architectural features and do not adversely interact with each other. While existing literature provides guidance for developing requirements suitable for reuse, little has been written on the practical realities an organization faces in attempting to reuse requirements. This paper addresses that gap by describing a commercial engineering company’s deployment of a requirements reuse process, the problems encountered, the results obtained, and the plans for future improvement of the process. @InProceedings{RE15p296, author = {Michael C. Panis}, title = {Reuse of Architecturally Derived Standards Requirements}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {296--304}, doi = {}, year = {2015}, } |
|
Pelliccione, Patrizio |
RE '15-IND: "The Need of Complementing ..."
The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group
Ulf Eliasson, Rogardt Heldal, Eric Knauss, and Patrizio Pelliccione (Volvo, Sweden; Chalmers University of Technology, Sweden; University of Gothenburg, Sweden) The automotive industry is currently going through an enormous change, transitioning from being pure hardware and mechanical companies to becoming more software focused. Currently, software development is embedded into a V-Model process that defines how software requirements are extracted from system requirements. In recent years, OEMs have come to recognize the importance and opportunities offered by software, which include better management and shorter time-to-market of distinguishing features. Strategies to better utilize software include in-house software development and new ways to collaborate with suppliers. However, in their effort to take advantage of these opportunities, engineers struggle with the formal process imposed on software development. In this paper, we investigate the impact of this struggle on the flow of requirements, including challenges and practices. We found that new ways of working with requirements had emerged that are partly not supported, partly hindered by the old tooling and processes for requirements engineering. Requirements flow both vertical and horizontal in the organization and across the supply-chain. Support for the new way of working should allow us to refine requirements iteratively throughout their life-cycle, handle the discussion of rationales, and to manage assumptions. We found strategies of achieving this to differ not only between OEMs, but also between different divisions inside the OEMs. @InProceedings{RE15p372, author = {Ulf Eliasson and Rogardt Heldal and Eric Knauss and Patrizio Pelliccione}, title = {The Need of Complementing Plan-Driven Requirements Engineering with Emerging Communication: Experiences from Volvo Car Group}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {372--381}, doi = {}, year = {2015}, } |
|
Podelski, Andreas |
RE '15-IND: "Using the Requirements Specification ..."
Using the Requirements Specification to Infer the Implicit Test Status of Requirements
Tobias Morciniec and Andreas Podelski (Daimler, Germany; University of Freiburg, Germany) We investigate a method to infer the implicit test status of requirements and thus increase the number of requirements for which the test status is known. The general idea is to improve the data set for measuring the maturity of the system in the current release. The inference is based on the structuring mechanisms (hierarchy, types) which are typically used to document the (natural language) requirements specification. We present a case study in the context of the development process for Mercedes-Benz passenger cars at Daimler AG. The results of the case study indicate the usefulness of the structuring mechanisms in the requirements specification as the basis for the inference. In particular, the number of requirements for which the status is known could be increased by almost a third. @InProceedings{RE15p362, author = {Tobias Morciniec and Andreas Podelski}, title = {Using the Requirements Specification to Infer the Implicit Test Status of Requirements}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {362--371}, doi = {}, year = {2015}, } |
|
Stissing, Martin Stig |
RE '15-IND: "Requirements Problems in the ..."
Requirements Problems in the Development of a New User Interface for Healthcare Equipment
Maria Holmegaard, Jens Bæk Jørgensen, Michael Sørensen Loft, and Martin Stig Stissing (Mjølner Informatics, Denmark) In August 2013, our company started work for an industrial customer. First, we developed a prototype and conducted field studies in small-scale projects. This was successful and the basis for a larger project about development of a new user interface for healthcare equipment. A main aim for us was to use this project as starting point for establishing a strategic, long-term relationship with this customer. However, we were not successful. In November 2014, our customer chose to take over the development themselves. We were too expensive, used too many hours and were not able to provide useful estimates, they said. In this paper, we describe the project and analyze causes to our customer’s decision. We also look at possible alternatives to the actions we took in the project and discuss whether we could have done better. A root cause to our customer’s dissatisfaction is related to requirements and handling of requirements. @InProceedings{RE15p315, author = {Maria Holmegaard and Jens Bæk Jørgensen and Michael Sørensen Loft and Martin Stig Stissing}, title = {Requirements Problems in the Development of a New User Interface for Healthcare Equipment}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {315--323}, doi = {}, year = {2015}, } |
|
Vogelsang, Andreas |
RE '15-IND: "Systematic Elicitation of ..."
Systematic Elicitation of Mode Models for Multifunctional Systems
Andreas Vogelsang, Henning Femmer, and Christian Winkler (TU München, Germany; MAN Truck & Bus, Germany) Many requirements engineering approaches structure and specify requirements based on the notion of modes or system states. The set of all modes is usually considered as the mode model of a system or problem domain. However, it is neither clear how such a mode model can be elicited systematically, nor whether it is realistic to elicit a mode model for a productive system with regard to size and comprehensibility. In this paper, we introduce three elicitation approaches for mode models. We applied the three approaches in an industrial automotive context and assessed the resulting mode models with respect to size, complexity, and differences to each other. Our results show that all elicitation approaches were capable of eliciting modes, which were structured in mode models with 20 to 42 modes. From these results, we conclude that it is possible to elicit manageable mode models for an entire system in a productive context. In our case, the practitioners decided to integrate our model in their feature specification and analysis process. @InProceedings{RE15p305, author = {Andreas Vogelsang and Henning Femmer and Christian Winkler}, title = {Systematic Elicitation of Mode Models for Multifunctional Systems}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {305--314}, doi = {}, year = {2015}, } |
|
Widera, Alexander |
RE '15-IND: "Understanding Changes in Use ..."
Understanding Changes in Use Cases: A Case Study
Mohammad R. Basirati, Henning Femmer, Sebastian Eder, Martin Fritzsche, and Alexander Widera (TU München, Germany; Munich Re, Germany) Requirements change and so (should) do requirements artifacts, such as use cases. However, we have little knowledge about which changes requirements engineers actually perform on use cases. We do not know what is changing, at which locations use cases change and need a deeper understanding of which changes are problematic in terms of difficult or risky. To explore these challenges from an industrial point of view, we conducted a mixed methods case study in which we analyze 15 month of changes in use cases in an industrial software project. The study provided interesting observations for both practitioners and researchers involved: First, the most frequently changing use cases had an issue in their structuring. Second, alternative flows (i.e., variations or extensions of the main flow) were especially prone to changes. Third, changes in content (semantic changes) and in presentation of the content (syntactic changes) happen similarly frequently. Last, a qualitative and quantitative analysis aiming at a deeper understanding of problematic changes identified taxonomy changes, as well as locally or temporally dispersed changes as particularly difficult and risky. In this paper, we contribute a first empirical inquiry for understanding the maintainability of use cases: The presented study provides empirical evidence that there are particular maintenance risks and suggests to continuously analyze local and temporal dispersion. @InProceedings{RE15p352, author = {Mohammad R. Basirati and Henning Femmer and Sebastian Eder and Martin Fritzsche and Alexander Widera}, title = {Understanding Changes in Use Cases: A Case Study}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {352--361}, doi = {}, year = {2015}, } |
|
Winkler, Christian |
RE '15-IND: "Systematic Elicitation of ..."
Systematic Elicitation of Mode Models for Multifunctional Systems
Andreas Vogelsang, Henning Femmer, and Christian Winkler (TU München, Germany; MAN Truck & Bus, Germany) Many requirements engineering approaches structure and specify requirements based on the notion of modes or system states. The set of all modes is usually considered as the mode model of a system or problem domain. However, it is neither clear how such a mode model can be elicited systematically, nor whether it is realistic to elicit a mode model for a productive system with regard to size and comprehensibility. In this paper, we introduce three elicitation approaches for mode models. We applied the three approaches in an industrial automotive context and assessed the resulting mode models with respect to size, complexity, and differences to each other. Our results show that all elicitation approaches were capable of eliciting modes, which were structured in mode models with 20 to 42 modes. From these results, we conclude that it is possible to elicit manageable mode models for an entire system in a productive context. In our case, the practitioners decided to integrate our model in their feature specification and analysis process. @InProceedings{RE15p305, author = {Andreas Vogelsang and Henning Femmer and Christian Winkler}, title = {Systematic Elicitation of Mode Models for Multifunctional Systems}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {305--314}, doi = {}, year = {2015}, } |
|
Wnuk, Krzysztof |
RE '15-IND: "Experience Requirements in ..."
Experience Requirements in Video Games: Definition and Testability
David Callele, Philip Dueck, Krzysztof Wnuk, and Peitsa Hynninen (Experience First Design, Canada; Blekinge Institute of Technology, Sweden; Aalto University, Finland) A properly formed requirement is testable, a necessity for ensuring that design goals are met. While challenging in productivity applications, entertainment applications such as games compound the problem due to their subjective nature. We report here on our efforts to create testable experience requirements, the associated scope challenges and challenges with test design and result interpretation. We further report on issues experienced when performing focus group testing and provide practitioner guidance. @InProceedings{RE15p324, author = {David Callele and Philip Dueck and Krzysztof Wnuk and Peitsa Hynninen}, title = {Experience Requirements in Video Games: Definition and Testability}, booktitle = {Proc.\ RE}, publisher = {IEEE}, pages = {324--333}, doi = {}, year = {2015}, } |
26 authors
proc time: 0.27