| 1. |
- Maro, Salome, 1987, et al.
(författare)
-
Impact of Gamification on Trace Link Vetting: A Controlled Experiment
- 2019
-
Ingår i: International Working Conference on Requirements Engineering: Foundation for Software Quality REFSQ 2019. - Cham : Springer. - 9783030155377
-
Konferensbidrag (refereegranskat)abstract
- [Context] Automatically generated trace links must be vetted by human analysts before use. The task of vetting trace links is considered boring due to its repetitive nature and tools that are not engaging to the analyst. Therefore, a lack of developer engagement can hamper the successful implementation of a traceability strategy in an organisation. [Objective] In this study, we examine whether two gamification features, levels and badges, have a positive effect on human analysts’ engagement and ultimately on the quality of vetted trace links. [Method] We have conducted a controlled experiment with 24 participants that vetted trace link candidates and recorded their speed, correctness, enjoyment, and perceived usability of the tool. [Results] The results indicate that there was no significant difference between the speed, correctness, and perceived usability of the control and the experiment group. However, gamification features significantly increased the users’ perceived enjoyment. Levels and badges were perceived positively by the majority of the participants while some pitfalls and improvements were pointed out. [Conclusion] Our study indicates the need for further research as the results raise several questions, in particular, w.r.t. what analyst behaviour gamification incentivises, and the impact of gamification on long-term enjoyment.
|
|
| 2. |
- Bordeleau, Francis, et al.
(författare)
-
Challenges and Research Directions for Successfully Applying MBE Tools in Practice
- 2017
-
Ingår i: CEUR Workshop Proceedings. - 1613-0073. ; 2019
-
Konferensbidrag (refereegranskat)abstract
- Model Based Engineering aims to improve efficiency and effectiveness of software engineering. Success in industrial practice of MBE does not only depend on the modeling languages and constructive or analytical approaches, like code generation or model checking. It is also heavily influenced by the quality and, particularly, usability of the used tools. In this position paper, we discuss challenges experienced in applying MBE in practice both from academic as well as industrial viewpoints. Based on the research challenges, we discuss future research directions to improve the chances for the success of MBE in industrial practice.
|
|
| 3. |
- de Oliveira Neto, Francisco Gomes, et al.
(författare)
-
Challenges of Aligning Requirements Engineering and System Testing in Large-Scale Agile: A Multiple Case Study
- 2017
-
Ingår i: 2017 IEEE 25th International Requirements Engineering Conference Workshops (REW), 4-8 Sept. 2017, Lisbon, Portugal. - : IEEE. - 9781538634882
-
Konferensbidrag (refereegranskat)abstract
- Abstract: As agile methods become more pervasive, agile practices are applied to more large-scale systems with a scope that goes beyond pure software. The expansion of agile in these contexts provides benefits, but creates new challenges. Widespread use of agile has changed the way we must think about practices both in Requirements Engineering (RE) and in System Testing (ST). Our experience shows that many challenges in the application of large-scale agile development relate to either RE or ST, and in particular to the alignment between these areas. In this paper we present large-scale agile-related challenges from a multiple case study which relate to REST alignment. We map our challenges to an existing framework for REST alignment, and make an initial attempt to suggest agile RE practices from the literature which may alleviate these challenges. Our results show that the interviewed companies need to first adopt more agile RE practices to enhance REST alignment and then leverage agile testing. Future work will look more towards evaluating these best practices.
|
|
| 4. |
- Fagerström, Martin, 1979, et al.
(författare)
-
Verdict Machinery: On the need to automatically make sense of test results
- 2016
-
Ingår i: International Symposium on Software Testing and Analysis (ISSTA '16). - New York, NY, USA : ACM. - 9781450343909 ; , s. 225-234
-
Konferensbidrag (refereegranskat)abstract
- Along with technological developments and increasing competition there is a major incentive for companies to produce and market high quality products before their competitors. In order to conquer a bigger portion of the market share, companies have to ensure the quality of the product in a shorter time frame. To accomplish this task companies try to automate their test processes as much as possible. It is critical to investigate and understand the problems that occur during different stages of test automation processes. In this paper we report on a case study on automatic analysis of non-functional test results.We discuss challenges in the face of continuous integration and deployment and provide improvement suggestions based on interviews at a large company in Sweden. The key contributions of this work are filling the knowledge gap in research about performance regression test analysis automation and providing warning signs and a road map for the industry.
|
|
| 5. |
- Jolak, Rodi, 1985, et al.
(författare)
-
Position paper: Knowledge sharing and distances in collaborative modeling
- 2019
-
Ingår i: Proceedings - 2019 ACM/IEEE 22nd International Conference on Model Driven Engineering Languages and Systems Companion, MODELS-C 2019. ; , s. 415-416
-
Konferensbidrag (refereegranskat)abstract
- To develop systems effectively, a shared system understanding is required. Collaborative modeling is one way to capture this shared understanding. Increasingly, in large systems engineering projects different distances lead to social barriers between stakeholders. These barriers affect the quantity and quality of knowledge that is shared between stakeholders, thus reducing the quality of the resulting product. While it has been proposed to limit modeling activities to co-located teams, this might not always be possible or feasible. We argue that, despite the technological advances in collaborative modeling, effective collaboration can only be achieved if we understand how to account for social barriers. We propose to study, in depth, how these barriers affect modeling, and how their effects can be reduced. By understanding the effects of social barriers and accounting for them, we can maximize the benefits of collaborative modeling. © 2019 IEEE
|
|
| 6. |
- Karg, Stefan, et al.
(författare)
-
Model-Driven Software Engineering in the open ETCS Project: Project Experiences and Lessons Learned
- 2016
-
Ingår i: Proceedings of 19th International Conference on Model-Driven Engineering Languages and Systems. - New York, NY, USA : ACM. ; , s. 238-248
-
Konferensbidrag (refereegranskat)abstract
- Model-driven software engineering in industrial practice has been the focus of different empirical studies and experience reports. Particularly, positive effects of model-driven software engineering have been reported in the domain of embedded and safety-critical systems. We report in this paper on the experiences of the openETCS European research project whose goal was to formalize the System Requirements Specification and to develop an open source reference implementation of the European Train Control System including open source modeling tools. Furthermore, we will discuss lessons learned, e.g., about using open source modeling toolchains in safety-critical contexts and about using the SCADE Suite for the development of the safety-critical parts.
|
|
| 7. |
|
|
| 8. |
- Kasauli, Rashida, 1984, et al.
(författare)
-
Requirements Engineering Challenges in Large-Scale Agile System Development
- 2017
-
Ingår i: International Requirements Engineering Conference. - : IEEE. - 9781538631911 ; , s. 352-361
-
Konferensbidrag (refereegranskat)abstract
- Agile methods have proven their value to accelerate delivery of high quality software products and services to customers. End-users have become used to regular updates that fix bugs and provide new features and for software products, short time-to-market has become an important business driver. In order to remain competitive, more and more companies imple- ment agile methods and their practices also for software-intense, large products, such as cars, telecommunication infrastructure, and embedded systems. Development of such system usually relies on plan-driven, stage-gate processes and is subject to safety and regulative concerns. Consequently, requirements engineering involves upfront and detailed analysis, which can be at odds with agile (software) development. In this paper, we present results from a multiple case study with two car manufacturers, a telecommunications company, and a technology company that are on the journey to introduce organization wide continuous integration and continuous delivery to customers. Based on 20 qualitative interviews, 5 focus groups, and 2 cross-company workshops, we discuss possible scopes of agile methods within system development, the consequences this has on the role of requirements, and the challenges that arise from the interplay of requirements engineering and agile methods in large-scale system development. These relate in particular to communicating and managing knowledge about a) customer value and b) the system under development. We argue that better alignment of a holistic requirements model with agile development practices promises rich gains in development speed, flexibility, and overall quality of software and systems.
|
|
| 9. |
- Knauss, Eric, 1977, et al.
(författare)
-
Quality Requirements in Agile as a Knowledge Management Problem: More than Just-in-Time
- 2017
-
Ingår i: 2nd International Workshop on Just-In-Time Requirements Engineering: Dealing with Non-Functional Requirements in Agile Software Development (JITRE@RE17). - : IEEE. - 9781538634882
-
Konferensbidrag (refereegranskat)abstract
- Just-in-time (JIT) approaches have been suggested for managing non-functional requirements in agile projects. However, many non-functional requirements cannot be raised and met on the spot. In this position paper, we argue that effective JIT engineering of quality requirements depends on a solid foundation of long-term knowledge about all relevant quality requirements. We present two examples from projects related to safety and security and show that not all aspects of these quality requirements can be invented and changed just in time. Further, managing for example operationalization of quality requirements just in time depends on sufficient understanding of (i) customer value and (ii) the system under construction that must be shared by the engineering team. If a Learning Software Organization (LSO) intends to increase agility and speed up system development, it needs a holistic concept for managing this knowledge. We propose that a knowledge-management framework can facilitate JIT-RE by structuring, representing, and allowing updates of long-term knowledge about quality requirements. Such a knowledge-management framework should allow to map user value to system requirements and have important properties to allow JIT RE and sustainable evolution.
|
|
| 10. |
- Knauss, Eric, 1977, et al.
(författare)
-
T-Reqs: Tool Support for Managing Requirements in Large-Scale Agile System Development
- 2018
-
Ingår i: Proceedings of 26th IEEE International Requirements Engineering Conference (RE'18).
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- Requirements engineering is crucial to support agile development of large systems with long lifetimes. Agile cross-functional teams must be aware of requirements at system level and able to efficiently propose updates to those requirements. We discuss requirements for tooling to manage requirements in large-scale agile system development and propose a working solution. We investigate challenges of large-scale agile system development, derive requirements towards a tool to support a subset of these challenges, and discuss how these are addressed in T-Reqs, a text-based requirements management solution based on the git version control system. In our industrial context, T-Reqs offered the best trade-off with respect to the requirements we establish and was most likely to be accepted by a broad base of agile teams. It supports proven solutions for many challenges, for example updating system requirements based on using gerrit to review changes proposed by agile teams. T-Reqs is currently in industrial use and while our experience is specific to one industrial case, it may be valuable in different contexts as well. Regardless, we hope our experience helps to trigger a dialogue on how the changing landscape of requirements engineering in relation to agile system and software development affects needs for tooling support.
|
|
