| 1. |
- Zimelewicz, Eduardo, et al.
(författare)
-
ML-Enabled Systems Model Deployment and Monitoring : Status Quo and Problems
- 2024
-
Ingår i: Software Quality as a Foundation for Security. - : Springer Science+Business Media B.V.. - 9783031562808 ; , s. 112-131
-
Konferensbidrag (refereegranskat)abstract
- Systems that incorporate Machine Learning (ML) models, often referred to as ML-enabled systems, have become commonplace. However, empirical evidence on how ML-enabled systems are engineered in practice is still limited; this is especially true for activities surrounding ML model dissemination. [Goal] We investigate contemporary industrial practices and problems related to ML model dissemination, focusing on the model deployment and the monitoring ML life cycle phases. [Method] We conducted an international survey to gather practitioner insights on how ML-enabled systems are engineered. We gathered a total of 188 complete responses from 25 countries. We analyze the status quo and problems reported for the model deployment and monitoring phases. We analyzed contemporary practices using bootstrapping with confidence intervals and conducted qualitative analyses on the reported problems applying open and axial coding procedures. [Results] Practitioners perceive the model deployment and monitoring phases as relevant and difficult. With respect to model deployment, models are typically deployed as separate services, with limited adoption of MLOps principles. Reported problems include difficulties in designing the architecture of the infrastructure for production deployment and legacy application integration. Concerning model monitoring, many models in production are not monitored. The main monitored aspects are inputs, outputs, and decisions. Reported problems involve the absence of monitoring practices, the need to create custom monitoring tools, and the selection of suitable metrics. [Conclusion] Our results help provide a better understanding of the adopted practices and problems in practice and support guiding ML deployment and monitoring research in a problem-driven manner. © The Author(s), under exclusive license to Springer Nature Switzerland AG 2024.
|
|
| 2. |
- Biffl, Stefan, et al.
(författare)
-
An Industry 4.0 Asset-Based Coordination Artifact for Production Systems Engineering
- 2021
-
Ingår i: Proceedings - 2021 IEEE 23rd Conference on Business Informatics, CBI 2021 - Main Papers, Volume 2. - : IEEE. - 9781665420693 ; , s. 92-101
-
Konferensbidrag (refereegranskat)abstract
- In Cyber-Physical Production System (CPPS) engineering, domain experts design assets like products, production processes, and resources. However, the representation of dependencies between assets in heterogeneous engineering artifacts, like system plans, models, and tool data, is insufficient to coordinate engineering activities, like changes to shared asset properties, as it increases the risk of unplanned rework and project delay. While Industry 4.0 (I4.0) assets, defined in RAMI 4.0, allow representing multi-disciplinary views on assets, it remains open how to leverage this capability to coordinate changes in CPPS engineering. In this paper, we introduce the Product- Process-Resource Asset Network (PAN) coordination artifact, a knowledge graph based on I4.0 assets. We argue that the PAN coordination artifact fosters an explicit representation of change dependencies and engineering knowledge, improving capabilities for coordinating changes efficiently. In a feasibility study, we investigate the coordination capabilities of a PAN that represents change dependencies on a typical robot work cell in automotive manufacturing. Results show that the PAN provides effective capabilities for identifying risky assets for re-validation after changes.
|
|
| 3. |
|
|
| 4. |
- Borg, Markus, et al.
(författare)
-
The AIQ Meta-Testbed : Pragmatically Bridging Academic AI Testing and Industrial Q Needs
- 2021
-
Ingår i: Lecture Notes in Business Information Processing. - Cham : Springer Science and Business Media Deutschland GmbH. - 1865-1348 .- 1865-1356. - 9783030658533 ; 404, s. 66-77
-
Tidskriftsartikel (refereegranskat)abstract
- AI solutions seem to appear in any and all application domains. As AI becomes more pervasive, the importance of quality assurance increases. Unfortunately, there is no consensus on what artificial intelligence means and interpretations range from simple statistical analysis to sentient humanoid robots. On top of that, quality is a notoriously hard concept to pinpoint. What does this mean for AI quality? In this paper, we share our working definition and a pragmatic approach to address the corresponding quality assurance with a focus on testing. Finally, we present our ongoing work on establishing the AIQ Meta-Testbed.
|
|
| 5. |
- Bures, Tomas, et al.
(författare)
-
Software Engineering for Smart Cyber-Physical Systems - Towards a Research Agenda : Report on the First International Workshop on Software Engineering for Smart CPS
- 2015
-
Ingår i: Software Engineering Notes. - : ACM Press. - 0163-5948 .- 1943-5843. ; 40:6, s. 28-32
-
Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)abstract
- Cyber-Physical Systems (CPS) are large interconnected softwareintensivesystems that influence, by sensing and actuating, thephysical world. Examples are traffic management and power grids.One of the trends we observe is the need to endow such systemswith the “smart” capabilities, typically in the form of selfawarenessand self-adaptation, along with the traditional qualitiesof safety and dependability. These requirements combined withspecifics of the domain of smart CPS – such as large scale, the roleof end-users, uncertainty, and open-endedness – render traditionalsoftware engineering (SE) techniques not directly applicable; makingsystematic SE of smart CPS a challenging task. This paperreports on the results of the First International Workshop on SoftwareEngineering of Smart Cyber-Physical Systems (SEsCPS2015), where participants discussed characteristics, challenges andopportunities of SE for smart CPS, with the aim to outline anagenda for future research in this important area.
|
|
| 6. |
- DeAngelis, Nicola, et al.
(författare)
-
2020 WSES guidelines for the detection and management of bile duct injury during cholecystectomy
- 2021
-
Ingår i: World Journal of Emergency Surgery. - : BMC. - 1749-7922. ; 16:1
-
Forskningsöversikt (refereegranskat)abstract
- Bile duct injury (BDI) is a dangerous complication of cholecystectomy, with significant postoperative sequelae for the patient in terms of morbidity, mortality, and long-term quality of life. BDIs have an estimated incidence of 0.4-1.5%, but considering the number of cholecystectomies performed worldwide, mostly by laparoscopy, surgeons must be prepared to manage this surgical challenge. Most BDIs are recognized either during the procedure or in the immediate postoperative period. However, some BDIs may be discovered later during the postoperative period, and this may translate to delayed or inappropriate treatments. Providing a specific diagnosis and a precise description of the BDI will expedite the decision-making process and increase the chance of treatment success. Subsequently, the choice and timing of the appropriate reconstructive strategy have a critical role in long-term prognosis. Currently, a wide spectrum of multidisciplinary interventions with different degrees of invasiveness is indicated for BDI management. These World Society of Emergency Surgery (WSES) guidelines have been produced following an exhaustive review of the current literature and an international expert panel discussion with the aim of providing evidence-based recommendations to facilitate and standardize the detection and management of BDIs during cholecystectomy. In particular, the 2020 WSES guidelines cover the following key aspects: (1) strategies to minimize the risk of BDI during cholecystectomy; (2) BDI rates in general surgery units and review of surgical practice; (3) how to classify, stage, and report BDI once detected; (4) how to manage an intraoperatively detected BDI; (5) indications for antibiotic treatment; (6) indications for clinical, biochemical, and imaging investigations for suspected BDI; and (7) how to manage a postoperatively detected BDI.
|
|
| 7. |
- Kuhrmann, Marco, et al.
(författare)
-
What Makes Agile Software Development Agile
- 2022
-
Ingår i: IEEE Transactions on Software Engineering. - 0098-5589 .- 1939-3520. ; 48:9, s. 3523-3539
-
Tidskriftsartikel (refereegranskat)abstract
- Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile In this article, we investigate the question: what makes a software development method agile We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.
|
|
| 8. |
- Lindholm, Christin, et al.
(författare)
-
A Case Study on Software Risk Analysis in Medical Device Development
- 2012
-
Ingår i: Software Quality. Process Automation in Software Development/Lecture Notes in Business Information Processing. - Berlin, Heidelberg : Springer Berlin Heidelberg. - 1865-1348. - 9783642272127 ; 94, s. 143-158
-
Konferensbidrag (refereegranskat)abstract
- Software failures in medical devices can lead to catastrophic situations. Therefore is it crucial to handle software related risks when developing medical devices. This paper presents the experiences gained from an ongoing case study with a medical device development organisation. This part of the study focuses on the two first steps of the risk management process, i.e. risk identification and risk analysis. The research is conducted as action research, with the aim of analysing and giving input to the organisation’s introduction of a software risk management process. The risk identification activities focus on user risks based on scenarios describing the expected use of the medical device in its target environment. Challenging problems have been found in the risk management process with respect to definition of the system boundary and system context, the use of scenarios as input to the risk identification and estimation of detectability used during risk assessment.
|
|
| 9. |
- Musil, Angelika, et al.
(författare)
-
Continuous adaptation management in collective intelligence systems
- 2019
-
Ingår i: Software Architecture. - Cham : Springer. - 9783030299828 - 9783030299835 ; , s. 109-125
-
Konferensbidrag (refereegranskat)abstract
- Collective Intelligence Systems (CIS), such as wikis and social networks, enable enhanced knowledge creation and sharing at organization and society levels. From our experience in R&D projects with industry partners and in-house CIS development, we learned that these platforms go through a complex evolution process. A particularly challenging aspect in this respect represents uncertainties that can appear at any time in the life-cycle of such systems. A prominent way to deal with uncertainties is adaptation, i.e., the ability to adjust or reconfigure the system in order to mitigate the impact of the uncertainties. However, there is currently a lack of consolidated design knowledge of CIS-specific adaptation and methods for managing it. To support software architects, we contribute an architecture viewpoint for continuous adaptation management in CIS, aligned with ISO/IEC/IEEE 42010. We evaluated the viewpoint in a case study with a group of eight experienced engineers. The results show that the viewpoint is well-structured, useful and applicable, and that its model kinds cover well the scope to handle different CIS-specific adaptation problems.
|
|
| 10. |
- Musil, Juergen, et al.
(författare)
-
An Architecture Framework for Collective Intelligence Systems
- 2015
-
Ingår i: Proceedings. - : IEEE. - 9781479919222 ; , s. 21-30
-
Konferensbidrag (refereegranskat)abstract
- Collective intelligence systems (CIS), such as wikis, social networks and content sharing platforms, have dramatically improved knowledge creation and sharing at society level. There is a trend to exploit the stigmergic mechanisms of CIS also at organization/corporate level. However, despite the wide adoption of CIS, there is a lack of consolidated systematic knowledge of the architectural principles and practices that underlie CIS. Software architects lack guidance to design CIS for the application context of individual organizations. To address these challenges, we contribute with an architecture framework for CIS, aligned with ISO/IEC/IEEE 42010. The CIS-AF framework provides guidance for architects to describe key CIS elements and systematically model a CIS that is well-suited for an organization's context and goals. The framework is grounded in an in-depth analysis of existing CIS, workshops and interviews with key stakeholders, and experiences from developing a prototypical CIS. We evaluated the architecture framework in two cases in industry setting where CIS have been designed and implemented using the framework. Results show that the framework effectively supports stakeholders with providing a shared vocabulary of CIS concepts, guiding them to systematically apply the stigmergic principles of CIS, and supporting them with kick starting CIS in their organizations.
|
|
