| 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. |
- Hebig, Regina, 1984, et al.
(författare)
-
How do students experience and judge software comprehension techniques?
- 2020
-
Ingår i: IEEE International Conference on Program Comprehension. - New York, NY, USA : ACM. ; , s. 425-435
-
Konferensbidrag (refereegranskat)abstract
- Today, there is a wide range of techniques to support softwarecomprehension. However, we do not fully understand yet whattechniques really help novices, to comprehend a software system.In this paper, we present a master level project course on softwareevolution, which has a large focus on software comprehension. Wecollected data about student's experience with diverse comprehension techniques during focus group discussions over the course oftwo years. Our results indicate that systematic code reading canbe supported by additional techniques to guiding reading efforts.Most techniques are considered valuable for gaining an overviewand some techniques are judged to be helpful only in later stagesof software comprehension efforts.
|
|
| 3. |
- Holtmann, Jörg, 1979, et al.
(författare)
-
Using boundary objects and methodological island (BOMI) modeling in large-scale agile systems development
- 2024
-
Ingår i: Software and Systems Modeling. - 1619-1374 .- 1619-1366. ; In Press
-
Tidskriftsartikel (refereegranskat)abstract
- Large-scale systems development commonly faces the challenge of managing relevant knowledge between different organizational groups, particularly in increasingly agile contexts. Here, there is a conflict between coordination and group autonomy, and it is challenging to determine what necessary coordination information must be shared by what teams or groups, and what can be left to local team management. We introduce a way to manage this complexity using a modeling framework based on two core concepts: methodological islands (i.e., groups using different development methods than the surrounding organization) and boundary objects (i.e., artifacts that create a common understanding across team borders). However, we found that companies often lack a systematic way of assessing coordination issues and the use of boundary objects between methodological islands. As part of an iterative design science study, we have addressed this gap by producing a modeling framework (BOMI: Boundary Objects and Methodological Islands) to better capture and analyze coordination and knowledge management in practice. This framework includes a metamodel, as well as a list of bad smells over this metamodel that can be leveraged to detect inter-team coordination issues. The framework also includes a methodology to suggest concrete modeling steps and broader guidelines to help apply the approach successfully in practice. We have developed Eclipse-based tool support for the BOMI method, allowing for both graphical and textual model creation, and including an implementation of views over BOMI instance models in order to manage model complexity. We have evaluated these artifacts iteratively together with five large-scale companies developing complex systems. In this work, we describe the BOMI framework and its iterative evaluation in several real cases, reporting on lessons learned and identifying future work. We have produced a matured and stable modeling framework which facilitates understanding and reflection over complex organizational configurations, communication, governance, and coordination of knowledge artifacts in large-scale agile system development.
|
|
| 4. |
- Kasauli, Rashida, 1984, et al.
(författare)
-
Charting Coordination Needs in Large-Scale Agile Organisations with Boundary Objects and Methodological Islands
- 2020
-
Ingår i: Proceedings - 2020 IEEE/ACM International Conference on Software and System Processes, ICSSP 2020. - New York, NY, USA : ACM. ; , s. 51-60
-
Konferensbidrag (refereegranskat)abstract
- Large-scale system development companies are increasingly adopting agile methods. While this adoption may improve lead-times, such companies need to balance two trade-offs: (i) the need to have a uniform, consistent development method on system level with the need for specialised methods for teams in different disciplines (e.g., hardware, software, mechanics, sales, support); (ii) the need for comprehensive documentation on system level with the need to have lightweight documentation enabling iterative and agile work. With specialised methods for teams, isolated teams work within larger ecosystems of plan-driven culture, i.e., teams become agile “islands”. At the boundaries, these teams share knowledge which needs to be managed well for a correct system to be developed. While it is useful to support diverse and specialised methods, it is important to understand which islands are repeatedly encountered, the reasons or factors triggering their existence, and how best to handle coordination between them. Based on a multiple case study, this work presents a catalogue of islands and the boundary objects between them. We believe this work will be beneficial to practitioners aiming to understand their ecosystems and researchers addressing communication and coordination challenges in large-scale development.
|
|
| 5. |
- Maro, Salome, 1987
(författare)
-
Addressing Traceability Challenges in the Development of Embedded Systems
- 2017
-
Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Context: Currently, development e orts in embedded systems development lead to a large number of interconnected artifacts. Traceability enables understanding and managing these artifacts as they evolve. However, establishing traceability is not a trivial task, it requires the development organization to plan how traceability will t into its processes and provide tools to support traceability establishment. In practice, guidelines for how traceability should be established are lacking. Therefore, companies struggle with establishing traceability and making the most of traceability once it is established. Objective: The overall objective of this research is to improve traceability processes and tools for embedded systems development. In this thesis, we started with rst understanding the domain and practical traceability challenges and also investigated how traceability tools can be improved. Method: Since establishing traceability is a practical problem, our research is conducted in close collaboration with industry partners. We conducted qualitative empirical studies to understand which traceability challenges exist in reality and designed solutions for some of these challenges. Concretely, we used action research, case study and design science methods for the di erent studies. Results: Our studies show that establishing traceability in practice still has several challenges, the most prominent ones being: the manual work of establishing traceability is high; the engineers responsible for creating the links perceive it as an overhead; lack of tools to enable using traceability; lack of methods and tools to measure its quality; no universal standards for traceability to be shared and exchanged and it is di cult to measure the return on investment of establishing traceability. To reduce the amount of manual work needed to maintain traceability links, we designed guidelines that can be followed by tool developers. We also show the feasibility of a con gurable and extendable traceability management tool through a prototype implementation. Contributions: As part of this thesis, we have elicited persistent traceability challenges in development of embedded systems development. This list of challenges can also be used by other researchers who are interested in the topic of traceability for embedded systems development. As a rst initiative towards solving these challenges, we propose important factors and guidelines for traceability tool developers and organizations that need to acquire traceability tools. Lastly, we have demonstrated the feasibility of these factors and guidelines through a prototype implementation. This implementation is open source and available for industry to use in their development and for other researchers to use for studies and extend the tool.
|
|
| 6. |
- Maro, Salome, 1987
(författare)
-
Addressing Traceability Challenges in the Development of Embedded Systems
- 2017
-
Licentiatavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Context: Currently, development efforts in embedded systems lead to a large number of interconnected artifacts. Traceability enables understanding and managing these artifacts. However, establishing traceability is not a trivial task, it requires the development organization to plan how traceability will fit into its processes and provide tools to support traceability establishment. In practice, guidelines for establishing traceability are lacking. Therefore, companies struggle with establishing traceability and making the most of traceability.Objective: The overall objective of this research is to improve traceability processes and tools for embedded systems development. In this thesis, we started with first understanding the domain and practical traceability challenges and also investigated how traceability tools can be improved.Method:Since establishing traceability is a practical problem, our research is conducted in close collaboration with industry partners. We conducted empirical studies to understand which traceability challenges exist and designed solutions for some of these challenges. Concretely, we used action research, case study and design science methods for the different studies.Results:Our studies show that establishing traceability in practice has several challenges, the most prominent ones being: the manual work of establishing traceability is high; the engineers responsible for creating the links perceive it as an overhead; lack of tools to enable using traceability; lack of methods and tools to measure its quality; no universal standards for traceability to be exchanged and it is difficult to measure the return on investment of establishing traceability. To reduce the amount of manual work needed to maintain traceability links, we designed guidelines for traceability tool developers. We also show the feasibility of a configurable and extendable traceability management tool. Contributions: As part of this thesis, we have elicited persistent traceability challenges in development of embedded systems development. This list of challenges can also be used by other researchers who are interested in the topic of traceability for embedded systems development. As a first initiative towards solving these challenges, we propose important factors and guidelines for traceability tool developers and organizations that need to acquire traceability tools. Lastly, we have demonstrated the feasibility of these factors and guidelines through a prototype implementation. This implementation is open source and available for industry to use in their development and for other researchers to use for studies and extend the tool.
|
|
| 7. |
- Maro, Salome, 1987, et al.
(författare)
-
Capra: A Configurable and Extendable Traceability Management Tool
- 2016
-
Ingår i: Proceedings - 2016 IEEE 24th International Requirements Engineering Conference, RE 2016. - 9781509041213 ; , s. 407-408
-
Konferensbidrag (refereegranskat)abstract
- Traceability is a known problem both in academia and industry. One of the main challenges is that there is no one solution that will solve traceability problems for everyone in industry. Traceability needs are dependent on the context of the organization and can differ from project to project in the same organization. To cater for this problem we have developed Capra, an open source, flexible, configurable and extendable traceability management tool. Capra can be tailored according to specific traceability needs of individual projects and organizations. © 2016 IEEE.
|
|
| 8. |
- Maro, Salome, 1987, et al.
(författare)
-
Capra: A Configurable and Extendable Traceability Management Tool
- 2016
-
Ingår i: International Requirements Engineering Conference. - : IEEE. - 2332-6441.
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- Traceability is a known problem both in academia and industry. One of the main challenges is that there is no one solution that will solve traceability problems for everyone in industry. Traceability needs are dependent on the context of the organization and can differ from project to project in the same organization. To cater for this problem we have developed Capra, an open source, flexible, configurable and extendable traceability management tool. Capra can be tailored according to specific traceability needs of individual projects and organizations.
|
|
| 9. |
- Maro, Salome, 1987, et al.
(författare)
-
Challenges of Establishing Traceability in the Automotive Domain
- 2017
-
Ingår i: Software Quality. Complexity and Challenges of Software Engineering in Emerging Technologies. - : Springer International Publishing. - 1865-1348. - 9783319494210
-
Konferensbidrag (refereegranskat)abstract
- Traceability, i.e., relationships between artifacts in software development, is prescribed by quality standards such as ISO 26262 and therefore mandatory for automotive companies that develop safety-critical systems. However, establishing traceability is a challenge for many automotive companies. The objective of this study is to identify traceability challenges and solutions in this domain and compare these challenges and solutions with the ones in literature. To achieve this, we conducted a case study with a large automotive supplier to discover their traceability challenges and a tertiary literature review on existing traceability literature surveys to identify reported challenges and their solutions. We found 13 challenges from the literature study, of which ten were also found at the company. Three challenges are solved at the company with solutions that correlate with those proposed in literature, three are partially solved while four are still unsolved even though there are solutions in literature.
|
|
| 10. |
- Maro, Salome Honest, 1987, et al.
(författare)
-
Vetting automatically generated trace links: What information is useful to human analysts?
- 2018
-
Ingår i: Proceedings - 2018 IEEE 26th International Requirements Engineering Conference, RE 2018. ; , s. 52-63
-
Konferensbidrag (refereegranskat)abstract
- Automated traceability has been investigated for over a decade with promising results. However, a human analyst is needed to vet the generated trace links to ensure their quality. The process of vetting trace links is not trivial and while previous studies have analyzed the performance of the human analyst, they have not focused on the analyst's information needs. The aim of this study is to investigate what context information the human analyst needs. We used design science research, in which we conducted interviews with ten practitioners in the traceability area to understand the information needed by human analysts. We then compared the information collected from the interviews with existing literature. We created a prototype tool that presents this information to the human analyst. To further understand the role of context information, we conducted a controlled experiment with 33 participants. Our interviews reveal that human analysts need information from three different sources: 1) from the artifacts connected by the link, 2) from the traceability information model, and 3) from the tracing algorithm. The experiment results show that the content of the connected artifacts is more useful to the analyst than the contextual information of the artifacts.
|
|
| 11. |
- Maro, Salome, 1987
(författare)
-
Improving Software Traceability in the Development of Automotive Embedded Systems: A Research Abstract
- 2016
-
Ingår i: Joint Proceedings of the REFSQ 2016 Co-Located Events.
-
Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
- Development of embedded software in the automotive domain is a complex task involving the combination of multi-discipline and safety critical requirements. In such an environment, traceability to and from related software development artifacts is demanded by safety standards. It is also needed to facilitate activities such as impact analysis and software maintenance. Despite a lot of research done on software traceability, challenges still exist for complex domains such as the automotive domain due to development being done with multiple companies (suppliers) and integrated at the Original Equipment Manufactures (OEMs) side. This paper describes a PhD research study that is aimed at developing a traceability process, a set of relevant traceability link semantics and a tool. Expected results are that deployment of the process and tool will improve traceability both in terms of link correctness and completeness and that the semantics will support development activities such as impact analysis.
|
|
| 12. |
- Maro, Salome, 1987
(författare)
-
Improving software traceability tools and processes
- 2020
-
Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
- Context: Development of large and complex software leads to a large number of interconnected artifacts such as requirements, design models, code and implementation. Traceability enables understanding and managing these artifacts as they evolve. However, establishing traceability is not trivial. It requires the development organization to design effective traceability strategies and provide tools to support the traceability activities. Establishing traceability in practice faces many challenges such as the amount of effort needed to establish traceability, unclear traceability processes and difficulty in measuring the benefits of traceability. Objective: The overall objective of this research is to improve traceability processes and tools in software development. In this thesis we started with exploring the state of the art as well as the state of practice of traceability in order to identify persisting challenges and existing solutions. We then propose and implement solutions for four of the identified challenges: manual work of establishing traceability, lack of configurable tools, diverse artifacts and tools, and unclear traceability processes. Method: To identify existing traceability challenges and solutions, we conducted a systematic tertiary literature review, a multi-vocal literature review, and a case study to understand how these challenges and solutions manifest in practice. To design solutions we took an empirical approach where we used case studies and design science for the different studies. Results: Our results show that there are still many traceability challenges which are not solved by current solutions in literature due to practical constraints and limitations that exist especially in safety critical domains. To address the challenge of manual work needed to maintain trace links we propose a set of important factors and guidelines for traceability maintenance aimed at traceability tool developers and companies acquiring traceability tools. The feasibility of these factors and guidelines are demonstrated through a prototype implementation. The prototype implementation also shows how to design traceability solutions that are both configurable and support tracing to and from diverse artifacts and tools. To address the challenge of manual work in creating traceability links we have investigated how to improve the trace link vetting process as part of a way to transfer automated techniques of creating trace links to industry. We provide insights and lessons learned on how to improve the trace link vetting process. Lastly the thesis proposes a traceability introduction methodology (TracIMo), which consists of concrete steps that companies can take to design, deploy and evaluate traceability strategies.
|
|
| 13. |
- Maro, Salome, 1987, et al.
(författare)
-
Managing Traceability Information Models: Not Such a Simple Task After All?
- 2021
-
Ingår i: IEEE Software. - 0740-7459 .- 1937-4194. ; 38:5
-
Tidskriftsartikel (refereegranskat)abstract
- Practitioners are poorly supported by the scientific literature when managing traceability information models (TIMs), which capture the structure and semantics of trace links. In practice, companies manage their TIMs in very different ways, even in cases where companies share many similarities. We present our findings from an in-depth focus group about TIM management with three different systems engineering companies. We find that the concrete needs of the companies as well as challenges such as scale and workflow integration are not considered by existing scientific work. We thus issue a call-to-arms for the requirements engineering and software and systems traceability communities, the two main communities for traceability research, to refocus their work on these practical problems. IEEE
|
|
| 14. |
- Maro, Salome, 1987, et al.
(författare)
-
On integrating graphical and textual editors for a UML profile based domain specific language: an industrial experience
- 2015
-
Ingår i: Proceedings of the 2015 ACM SIGPLAN International Conference on Software Language Engineering. - : Association for Computing Machinery (ACM). - 9781450336864
-
Konferensbidrag (refereegranskat)abstract
- Domain Specific Languages (DSLs) are an established means of reducing the gap between problem and solution domains. DSLs increase productivity and improve quality as they can be tailored to exactly fit the needs of the problem to be solved. A DSL can have multiple notations including textual and graphical notations. In some cases, one of these notations for a DSL is enough but there are many cases where a single notation does not suffice and there is a demand to support multiple notations for the same DSL. UML profile is one of several approaches used to define a DSL, however most UML tools only come with graphical editors. In this paper, we present our approach and industrial experience on integrating textual and graphical editors for a UML profile-based DSL. This work was conducted as part of an explorative study at Ericsson. The main aim of the study was to investigate how to introduce a textual editor to an already existing UML profile-based DSL in an Eclipse environment. We report on the challenges of integrating textual and graphical editors for UML profile-based DSLs in practice, our chosen approach, specific constraints and requirements of the study.
|
|
| 15. |
- Maro, Salome, 1987, et al.
(författare)
-
Software traceability in the automotive domain: Challenges and solutions
- 2018
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 141, s. 85-110
-
Tidskriftsartikel (refereegranskat)abstract
- In the automotive domain, the development of all safety-critical systems has to comply with safety standards such as ISO 26262. These standards require established traceability, the ability to relate artifacts created during development of a system, to ensure resulting systems are well-tested and therefore safe. This paper contrasts general traceability challenges and solutions with those specific to the automotive domain, and investigates how they manifest in practice. We combine three data sources: a tertiary literature review to identify general challenges and solutions; a case study with an automotive supplier as validation for how the challenges and solutions are experienced in practice; and a multi-vocal literature review to identify challenges and solutions specific to the automotive domain. We found 22 challenges and 16 unique solutions in the reviews. 17 challenges were identified in the case study; six remain unsolved. We discuss challenges and solutions from the perspectives of academia, tool vendors, consultants and users, and identify differences between scientific and "grey" literature. We discuss why challenges remain unsolved and propose solutions. Our findings indicate that there is a significant overlap between general traceability challenges and those in the automotive domain but that they are experienced differently. (C) 2018 Elsevier Inc. All rights reserved.
|
|
| 16. |
- Maro, Salome, 1987, et al.
(författare)
-
Traceability Maintenance: Factors and Guidelines
- 2016
-
Ingår i: Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering (ASE 2016). - New York, NY, USA : ACM. - 1527-1366. - 9781450338455 ; , s. 414-425
-
Konferensbidrag (refereegranskat)abstract
- Traceability is an important concern for numerous software engineering activities. Establishing traceability links %that capture useful connections between software artefactsis a challenging and cost-intensive task, which is uneconomical without suitable strategies for maintaining high link quality. Current approaches to Traceability Management (TM), however, often make important assumptions and choices without ensuring that the consequences and implications for traceability maintenance are feasible and desirable in practice. In this paper, therefore, we identify a set of core factors that influence how the quality of traceability links can be maintained. For each factor, we discuss relevant challenges and provide guidelines on how best to ensure viable traceability maintenance in a practical TM approach. Our results are based on and supported by data collected from interviews conducted with: (i) 9 of our industrial and academic project partners to elicit project specific requirements, and (ii) 24 software development stakeholders from 15 industrial cases to provide a broader overview of the current state of the practice on traceability maintenance.To evaluate the feasibility of our guidelines, we investigate a set of existing TM solutions used in industry with respect to our guidelines.
|
|
| 17. |
- Maro, Salome, 1987, et al.
(författare)
-
TracIMo: a traceability introduction methodology and its evaluation in an Agile development team
- 2022
-
Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 27, s. 53-81
-
Tidskriftsartikel (refereegranskat)abstract
- Software traceability, the ability to relate software development artifacts such as requirements, design models and code to each other, is an important aspect in software development. It yields a number of benefits such as facilitating impact analysis and tracking software changes. However, for companies to reap these benefits, a proper traceability strategy-a plan for how traceability should be managed-needs to be defined and implemented. Existing literature lacks concrete guidelines for practitioners to systematically define such a strategy. In this study, we address this gap by defining a Traceability Introduction Methodology (TracIMo), which is a methodology for systematically designing, implementing and evaluating software traceability in practice. We used design science research to design TracIMo and evaluated it in a case study with an agile development team of a company in the finance domain. Our results show that TracIMo is feasible as it allows incremental definition and evaluation of a traceability strategy that is aligned with the company's traceability goals and the existing development process. We also report practical challenges encountered when designing a traceability strategy such as defining the right level of granularity and the need for defining intermediate development artifacts.
|
|
| 18. |
- Mukelabai, Mukelabai, 1985, et al.
(författare)
-
Tackling Combinatorial Explosion: A Study of Industrial Needs and Practices for Analyzing Highly Configurable Systems
- 2018
-
Ingår i: Automated Software Engineering. - New York, NY, USA : ACM. - 1573-7535 .- 0928-8910. ; , s. 155-166
-
Konferensbidrag (refereegranskat)abstract
- Highly configurable systems are complex pieces of software. To tackle this complexity, hundreds of dedicated analysis techniques have been conceived, many of which able to analyze system properties for all possible system configurations, as opposed to traditional, single-system analyses. Unfortunately, it is largely unknown whether these techniques are adopted in practice, whether they address actual needs, or what strategies practitioners actually apply to analyze highly configurable systems. We present a study of analysis practices and needs in industry. It relied on a survey with 27 practitioners engineering highly configurable systems and follow-up interviews with 15 of them, covering 18 different companies from eight countries. We confirm that typical properties considered in the literature (e.g., reliability) are relevant, that consistency between variability models and artifacts is critical, but that the majority of analyses for specifications of configuration options (a.k.a., variability model analysis) is not perceived as needed. We identified rather pragmatic analysis strategies, including practices to avoid the need for analysis. For instance, testing with experience-based sampling is the most commonly applied strategy, while systematic sampling is rarely applicable. We discuss analyses that are missing and synthesize our insights into suggestions for future research.
|
|
| 19. |
- Steghöfer, Jan-Philipp, 1983, et al.
(författare)
-
The MobSTr Dataset - An Exemplar for Traceability and Model-based Safety Assessment
- 2021
-
Ingår i: Proceedings of the IEEE International Conference on Requirements Engineering. - 2332-6441 .- 1090-705X. ; RE 2021, s. 444-445
-
Konferensbidrag (refereegranskat)abstract
- The MobSTr dataset contains a number of artifacts for an autonomous driver assistance system, ranging from textual requirements to models for system design and models relevant to safety assurance. The artifacts provided are connected with traceability links created and managed with Eclipse Capra, an open source traceability management tool. The dataset builds upon a custom traceability information model that provides type safety and semantics for the trace links.MobSTr is intended for researchers that work on software and systems traceability as well as on model-based safety assurance. It is already being used in a number of studies, including research on trace link consistency, change impact analysis, and automated analysis of safety and timing requirements.
|
|
| 20. |
- Trei, Maria, et al.
(författare)
-
An ISO 26262 compliant design flow and tool for automotive multicore systems
- 2016
-
Ingår i: Proceedings of the 17th International Conference on Product-Focused Software Process Improvement (PROFES). - Cham : Springer International Publishing.
-
Konferensbidrag (refereegranskat)abstract
- The complex interactions between suppliers and OEMs as well as between suppliers in the automotive industry make it necessary to clearly define processes and models for the exchange of information between different companies. Especially when several suppliers are jointly working on the same product, reducing friction and adhering to common standards are a necessity. In addition, standards like AUTOSAR and ISO 26262 put additional requirements on the processes and tools. In this paper, we report on our efforts to standardise the design flow and the modelling environment for automotive suppliers. In particular, we analyse the existing design flows at the suppliers, as well as the current state of an advanced automotive modelling tool, the Amalthea platform. Furthermore, we analyse compliance of both the design flows and the platform with the ISO 26262 standard, identifying which aspects of the standard are already covered and which are currently missing. From this, we derive recommendations and a roadmap to achieve full coverage of the standard with the aim of providing a single integrated platform with an accompanying design methodology.
|
|
| 21. |
- Wohlrab, Rebekka, 1991, et al.
(författare)
-
Collaborative traceability management: a multiple case study from the perspectives of organization, process, and culture
- 2020
-
Ingår i: Requirements Engineering. - : Springer Science and Business Media LLC. - 0947-3602 .- 1432-010X. ; 25:1, s. 21-45
-
Tidskriftsartikel (refereegranskat)abstract
- Traceability is crucial for many activities in software and systems engineering including monitoring the development progress, and proving compliance with standards. In practice, the use and maintenance of trace links are challenging as artifacts undergo constant change, and development takes place in distributed scenarios with multiple collaborating stakeholders. Although traceability management in general has been addressed in previous studies, there is a need for empirical insights into the collaborative aspects of traceability management and how it is situated in existing development contexts. The study reported in this paper aims to close this gap by investigating the relation of collaboration and traceability management, based on an understanding of characteristics of the development effort. In our multiple exploratory case study, we conducted semi-structured interviews with 24 individuals from 15 industrial projects. We explored which challenges arise, how traceability management can support collaboration, how collaboration relates to traceability management approaches, and what characteristics of the development effort influence traceability management and collaboration. We found that practitioners struggle with the following challenges: (1) collaboration across team and tool boundaries, (2) conveying the benefits of traceability, and (3) traceability maintenance. If these challenges are addressed, we found that traceability can facilitate communication and knowledge management in distributed contexts. Moreover, there exist multiple approaches to traceability management with diverse collaboration approaches, i.e., requirements-centered, developer-driven, and mixed approaches. While traceability can be leveraged in software development with both agile and plan-driven paradigms, a certain level of rigor is needed to realize its benefits and overcome challenges. To support practitioners, we provide principles of collaborative traceability management. The main contribution of this paper is empirical evidence of how culture, processes, and organization impact traceability management and collaboration, and principles to support practitioners with collaborative traceability management. We show that collaboration and traceability management have the potential to be mutually beneficial—when investing in one, also the other one is positively affected.
|
|
| 22. |
- Wohlrab, Rebekka, 1991, et al.
(författare)
-
Collaborative Traceability Management: Challenges and Opportunities
- 2016
-
Ingår i: Proceedings of 24th IEEE International Requirements Engineering Conference (RE' 16). - : IEEE. - 2332-6441. - 9781509041213
-
Konferensbidrag (refereegranskat)abstract
- Traceability and the management of tracing links are important for various reasons, including to manage knowledge about a complex software system, to monitor the progress of its development, and to prove that it is developed in accordance to regulations. However, maintaining tracing links and using them in a beneficial way proves to be challenging in practice. In this paper, we investigate traceability and its management as a collaboration problem. Based on 15 industrial cases and 24 semi-structured interviews we identify a) challenges in collaborative traceability management and b) how traceability management can be used to enable collaboration. Our findings show that main challenges are boundaries between organizations and tools, a lack of common goals and responsibilities, and the difficulty of collaboratively maintaining trace links. On the other hand, traceability can be an important facilitator for documentation and knowledge management.
|
|
| 23. |
- Wohlrab, Rebekka, 1991, et al.
(författare)
-
Modeling and Analysis of Boundary Objects and Methodological Islands in Large-Scale Systems Development
- 2020
-
Ingår i: Lecture Notes in Computer Science. - Cham : Springer International Publishing. - 0302-9743 .- 1611-3349. - 9783030625214 ; 12400, s. 575-589
-
Konferensbidrag (refereegranskat)abstract
- Large-scale systems development commonly faces the challenge of managing relevant knowledge between different organizational groups, particularly in increasingly agile contexts. In previous studies, we found the importance of analyzing methodological islands (i.e., groups using different development methods than the surrounding organization) and boundary objects between them. In this paper, we propose a metamodel to better capture and analyze coordination and knowledge management in practice. Such a metamodel can allow practitioners to describe current practices, analyze issues, and design better-suited coordination mechanisms. We evaluated the conceptual model together with four large-scale companies developing complex systems. In particular, we derived an initial list of bad smells that can be leveraged to detect issues and devise suitable improvement strategies for inter-team coordination in large-scale development. We present the model, smells, and our evaluation results.
|
|
