SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Biffl Stefan) srt2:(2020-2024)"

Sökning: WFRF:(Biffl Stefan) > (2020-2024)

  • Resultat 1-10 av 11
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
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.
  • Biffl, Stefan, et al. (författare)
  • Architecting for a Sustainable Digital Society
  • 2023
  • Ingår i: Journal of Systems and Software. - : Elsevier. - 0164-1212 .- 1873-1228. ; 200
  • Tidskriftsartikel (övrigt vetenskapligt/konstnärligt)
  •  
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.
  • 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.
  •  
6.
  • 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.
  •  
7.
  • Musil, Juergen, et al. (författare)
  • Society-Level Software Governance : A Challenging Scenario
  • 2020
  • Ingår i: Proceedings - 2020 IEEE/ACM 42nd International Conference on Software Engineering Workshops, ICSEW 2020. - New York, NY, USA : ACM Publications. - 9781450379632 ; , s. 307-308
  • Konferensbidrag (refereegranskat)abstract
    • The technology-driven transformation process continues to spawn novel, growth-oriented digital application domains and platforms. The user base of these society-level software systems consists of a larger proportion of the community and that involve a large set of stakeholder groups. In case of an incident there is a public demand from a variety of stakeholders for multilateral intervention in order to correct the behavior of the software system. For software engineering as a technical discipline that has been fostered and matured in corporate and organizational context, this is a major challenge because it has to deal with a multitude of multidisciplinary stakeholders and their concerns. In order to stimulate further discussions, we discuss software governance on societal level and identify future research challenges of this increasingly relevant topic. © 2020 ACM.
  •  
8.
  • Weyns, Danny, et al. (författare)
  • Preliminary Results of a Survey on the Use of Self-Adaptation in Industry
  • 2022
  • Ingår i: Proceedings - 17th Symposium on Software Engineering for Adaptive and Self-Managing Systems, SEAMS 2022. - New York, NY, USA : IEEE. - 9781450393058 ; , s. 70-76
  • Konferensbidrag (refereegranskat)abstract
    • Self-Adaptation equips a software system with a feedback loop that automates tasks that otherwise need to be performed by operators. Such feedback loops have found their way to a variety of practical applications, one typical example is an elastic cloud. Yet, the state of the practice in self-Adaptation is currently not clear. To get insights into the use of self-Adaptation in practice, we are running a largescale survey with industry. This paper reports preliminary results based on survey data that we obtained from 113 practitioners spread over 16 countries, 62 of them work with concrete self-Adaptive systems. We highlight the main insights obtained so far: motivations for self-Adaptation, concrete use cases, and difficulties encountered when applying self-Adaptation in practice. We conclude the paper with outlining our plans for the remainder of the study. © 2022 ACM.
  •  
9.
  • Weyns, Danny, et al. (författare)
  • Self-Adaptation in Industry : A Survey
  • 2023
  • Ingår i: ACM Transactions on Autonomous and Adaptive Systems. - : ACM Publications. - 1556-4665 .- 1556-4703. ; 18:2
  • Tidskriftsartikel (refereegranskat)abstract
    • Computing systems form the backbone of many areas in our society, from manufacturing to traffic control, healthcare, and financial systems. When software plays a vital role in the design, construction, and operation, these systems are referred to as software-intensive systems. Self-adaptation equips a software-intensive system with a feedback loop that either automates tasks that otherwise need to be performed by human operators or deals with uncertain conditions. Such feedback loops have found their way to a variety of practical applications; typical examples are an elastic cloud to adapt computing resources and automated server management to respond quickly to business needs. To gain insight into the motivations for applying self-adaptation in practice, the problems solved using self-adaptation and how these problems are solved, and the difficulties and risks that industry faces in adopting self-adaptation, we performed a large-scale survey. We received 184 valid responses from practitioners spread over 21 countries. Based on the analysis of the survey data, we provide an empirically grounded overview the of state of the practice in the application of self-adaptation. From that, we derive insights for researchers to check their current research with industrial needs, and for practitioners to compare their current practice in applying self-adaptation. These insights also provide opportunities for applying self-adaptation in practice and pave the way for future industry-research collaborations.
  •  
10.
  • Bravo, L, et al. (författare)
  • 2021
  • swepub:Mat__t
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-10 av 11

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy