| 1. |
|
|
| 2. |
- Horkoff, Jennifer, 1980, et al.
(författare)
-
A Method for Modeling Data Anomalies in Practice
- 2021
-
Ingår i: Proceedings - 2021 47th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2021.
-
Konferensbidrag (refereegranskat)abstract
- As technology has allowed us to collect large amounts of industrial data, it has become critical to analyze and understand the data collected, in particular to find data anomalies. Anomaly analysis allows a company to detect, analyze and understand anomalous or unusual data patterns. This is an important activity to understand, for example, deviations in service which may indicate potential problems, or differing customer behavior which may reveal new business opportunities. Much previous work has focused on anomaly detection, in particular using machine learning. Such approaches allow clustering of data patterns by common attributes, and, although useful, clusters often do not correspond to the root causes of anomalies, meaning that more manual analysis is needed. In this paper we report on a design science study with two different teams, in a partner company which focuses on modeling and understanding the attributes and root causes of data anomalies. After iteration, for each team, we have created general and anomaly-specific UML class diagrams and goal models to capture anomaly details. We use our experiences to create an example taxonomy, classifying anomalies by their root causes, and to create a general method for modeling and understanding data anomalies. This work paves the way for a better understanding of anomalies and their root causes, leading towards creating a training set which may be used for machine learning approaches.
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
|
|
| 6. |
- Kasauli, Rashida, 1984, et al.
(författare)
-
Requirements engineering challenges and practices in large-scale agile system development
- 2021
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 172
-
Tidskriftsartikel (refereegranskat)abstract
- Context: Agile methods have become mainstream even in large-scale systems engineering companies that need to accommodate different development cycles of hardware and software. For such companies, requirements engineering is an essential activity that involves upfront and detailed analysis which can be at odds with agile development methods. Objective: This paper presents a multiple case study with seven large-scale systems companies, reporting their challenges, together with best practices from industry. We also analyze literature about two popular large-scale agile frameworks, SAFe (R) and LeSS, to derive potential solutions for the challenges. Methods: Our results are based on 20 qualitative interviews, five focus groups, and eight cross company workshops which we used to both collect and validate our results. Results: We found 24 challenges which we grouped in six themes, then mapped to solutions from SAFe (R), LeSS, and our companies, when available. Conclusion: In this way, we contribute a comprehensive overview of RE challenges in relation to largescale agile system development, evaluate the degree to which they have been addressed, and outline research gaps. We expect these results to be useful for practitioners who are responsible for designing processes, methods, or tools for large scale agile development as well as guidance for researchers.
|
|
| 7. |
- 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
|
|
