| 1. |
- Alahdab, Mohannad, et al.
(författare)
-
Empirical Analysis of Hidden Technical Debt Patterns in Machine Learning Software
- 2019
-
Ingår i: Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics). - Cham : Springer International Publishing. - 1611-3349 .- 0302-9743. ; 11915 LNCS, s. 195-202
-
Konferensbidrag (refereegranskat)abstract
- Context/Background Machine Learning (ML) software has special ability for increasing technical debt due to ML-specific issues besides having all the problems of regular code. The term “Hidden Technical Debt” (HTD) was coined by Sculley et al. to address maintainability issues in ML software as an analogy to technical debt in traditional software. Goal The aim of this paper is to empirically analyse how HTD patterns emerge during the early development phase of ML software, namely the prototyping phase. Method Therefore, we conducted a case study with subject systems as ML models planned to be integrated into the software system owned by Västtrafik, the public transportation agency in the west area of Sweden. Results During our case study, we could detect HTD patterns, which have the potential to emerge in ML prototypes, except for “Legacy Features”, “Correlated features”, and “Plain Old Data Type Smell”. Conclusion Preliminary results indicate that emergence of significant amount of HTD patterns can occur during prototyping phase. However, generalizability of our results require analyses of further ML systems from various domains.
|
|
| 2. |
- Kasauli, Rashida, 1984, et al.
(författare)
-
Safety-Critical Systems and Agile Development: A Mapping Study
- 2018
-
Ingår i: Proceedings - 44th Euromicro Conference on Software Engineering and Advanced Applications, SEAA 2018. ; , s. 470-477
-
Konferensbidrag (refereegranskat)abstract
- In the last decades, agile methods had a huge impact on how software is developed. In many cases, this has led to significant benefits, such as quality and speed of software deliv- eries to customers. However, safety-critical systems have widely been dismissed from benefiting from agile methods. Products that include safety critical aspects are therefore faced with a situation in which the development of safety-critical parts can significantly limit the potential speed-up through agile methods, for the full product, but also in the non-safety critical parts. For such products, the ability to develop safety-critical software in an agile way will generate a competitive advantage. In order to enable future research in this important area, we present in this paper a mapping of the current state of praxis based on a mixed method approach. Starting from a workshop with experts from six large Swedish product development companies we develop a lens for our analysis. We then present a systematic mapping study on safety-critical systems and agile development through this lens in order to map potential benefits, challenges, and solution candidates for guiding future research.
|
|
| 3. |
- Mahmood, Wardah, 1992, et al.
(författare)
-
Virtual Platform: Effective and Seamless Variability Management for Software Systems
- 2024
-
Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. ; In Press
-
Tidskriftsartikel (refereegranskat)abstract
- Customization is a general trend in software engineering, demanding systems that support variable stakeholder requirements. Two opposing strategies are commonly used to create variants: software clone & own and software configuration with an integrated platform. Organizations often start with the former, which is cheap and agile, but does not scale. The latter scales by establishing an integrated platform that shares software assets between variants, but requires high up-front investments or risky migration processes. So, could we have a method that allows an easy transition or even combine the benefits of both strategies? We propose a method and tool that supports a truly incremental development of variant-rich systems, exploiting a spectrum between the opposing strategies. We design, formalize, and prototype a variability-management framework: the virtual platform. Virtual platform bridges clone & own and platform-oriented development. Relying on programming-language independent conceptual structures representing software assets, it offers operators for engineering and evolving a system, comprising: traditional, asset-oriented operators and novel, feature-oriented operators for incrementally adopting concepts of an integrated platform. The operators record meta-data that is exploited by other operators to support the transition. Among others, they eliminate expensive feature-location effort or the need to trace clones. A cost-and-benefit analysis of using the virtual platform to simulate the development of a real-world variant-rich system shows that it leads to benefits in terms of saved effort and time for clone detection and feature location. Furthermore, we present a user study indicating that the virtual platform effectively supports exploratory and hands-on tasks, outperforming manual development concerning correctness. We also observed that participants were significantly faster when performing typical variability management tasks using the virtual platform. Furthermore, participants perceived manual development to be significantly more difficult than using the virtual platform, preferring virtual platform for all our tasks. We supplement our findings with recommendations on when to use virtual platform and on incorporating the virtual platform in practice.
|
|
| 4. |
- Perera, Charith, et al.
(författare)
-
Guest Editorial Special Section on Engineering Industrial Big Data Analytics Platforms for Internet of Things
- 2018
-
Ingår i: IEEE Transactions on Industrial Informatics. - : Institute of Electrical and Electronics Engineers (IEEE). - 1551-3203 .- 1941-0050. ; 14:2, s. 744-747
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)abstract
- Over the last few years, a large number of Internet of Things (IoT) solutions have come to the IoT marketplace. Typically, each of these IoT solutions are designed to perform a single or minimal number of tasks (primary usage). We believe a significant amount of knowledge and insights are hidden in these data silos that can be used to improve our lives; such data include our behaviors, habits, preferences, life patterns, and resource consumption. To discover such knowledge, we need to acquire and analyze this data together in a large scale. To discover useful information and deriving conclusions toward supporting efficient and effective decision making, industrial IoT platform needs to support variety of different data analytics processes such as inspecting, cleaning, transforming, and modeling data, especially in big data context. IoT middleware platforms have been developed in both academic and industrial settings in order to facilitate IoT data management tasks including data analytics. However, engineering these general-purpose industrial-grade big data analytics platforms need to address many challenges. We have accepted six manuscripts out of 24 submissions for this special section (25% acceptance rate) after the strict peerreview processes. Each manuscript has been blindly reviewed by at least three external reviewers before the decisions were made. The papers are briefly summarized.
|
|
| 5. |
- Steghöfer, Jan-Philipp, 1983, et al.
(författare)
-
Involving External Stakeholders in Project Courses
- 2018
-
Ingår i: ACM Transactions on Computing Education. - : Association for Computing Machinery (ACM). - 1946-6226. ; 18:2
-
Tidskriftsartikel (refereegranskat)abstract
- Problem: The involvement of external stakeholders in capstone projects and project courses is desirable dueto its potential positive effects on the students. Capstone projects particularly profit from the inclusion ofan industrial partner to make the project relevant and help students acquire professional skills. In addition,an increasing push towards education that is aligned with industry and incorporates industrial partners canbe observed. However, the involvement of external stakeholders in teaching moments can create friction andcould, in the worst case, lead to frustration of all involved parties.Contribution: We developed a model that allows analysing the involvement of external stakeholders inuniversity courses both in a retrospective fashion, to gain insights from past course instances, and in aconstructive fashion, to plan the involvement of external stakeholders.Key Concepts: The conceptual model and the accompanying guideline guide the teachers in their analysisof stakeholder involvement. The model is comprised of several activities (define, execute, and evaluate thecollaboration). The guideline provides questions that the teachers should answer for each of these activities.In the constructive use, the model allows teachers to define an action plan based on an analysis of potentialstakeholders and the pedagogical objectives. In the retrospective use, the model allows teachers to identifyissues that appeared during the project and their underlying causes. Drawing from ideas of the reflectivepractitioner, the model contains an emphasis on reflection and interpretation of the observations made bythe teacher and other groups involved in the courses.Key Lessons: Applying the model retrospectively to a total of eight courses shows that it is possible toreveal hitherto implicit risks and assumptions and to gain a better insight into the interaction betweenexternal stakeholders and students. Our empirical data reveals seven recurring risk themes that categorisethe different risks appearing in the analysed courses. These themes can also be used to categorise mitigationstrategies to address these risks pro-actively. Additionally, aspects not related to external stakeholders, e.g.,about the interaction of the project with other courses in the study program, have been revealed. Theconstructive use of the model for one course has proved helpful in identifying action alternatives and finallydeciding to not include external stakeholders in the project due to the perceived cost-benefit-ratio.Implications to practice: Our evaluation shows that the model is viable and a useful tool that allowsteachers to reason about and plan the involvement of external stakeholders in a variety of course settings,and in particular in capstone projects.
|
|
| 6. |
- Tuma, Katja, 1991, et al.
(författare)
-
Threat analysis of software systems: A systematic literature review
- 2018
-
Ingår i: Journal of Systems and Software. - : Elsevier BV. - 0164-1212. ; 144, s. 275-294
-
Tidskriftsartikel (refereegranskat)abstract
- Architectural threat analysis has become an important cornerstone for organizations concerned with developing secure software. Due to the large number of existing techniques it is becoming more challenging for practitioners to select an appropriate threat analysis technique. Therefore, we conducted a systematic literature review (SLR) of the existing techniques for threat analysis. In our study we compare 26 methodologies for what concerns their applicability, characteristics of the required input for analysis, characteristics of analysis procedure, characteristics of analysis outcomes and ease of adoption. We also provide insight into the obstacles for adopting the existing approaches and discuss the current state of their adoption in software engineering trends (e.g. Agile, DevOps, etc.). As a summary of our findings we have observed that: the analysis procedure is not precisely defined, there is a lack of quality assurance of analysis outcomes and tool support and validation are limited.
|
|
