Auflistung nach Schlagwort "traceability"
1 - 4 von 4
Treffer pro Seite
Sortieroptionen
- KonferenzbeitragAutomated Process-Centric Quality Constraints Checking for Quality Assurance in Safety-critical Systems(Software Engineering 2022, 2022) Mayr-Dorn, Christoph; Vierhauser, Michael; Bichler, Stefan; Keplinger, Felix; Cleland-Huang, Jane; Egyed, Alexander; Mehofer, ThomasThis abstract summarizes the work published as an ICSE 2021 research track paper ''Supporting Quality Assurance with Automated Process-Centric Quality Constraints Checking'' available at https://doi.org/10.1109/ICSE43902.2021.00118 . We propose an approach that, on the one hand, assists in checking compliance with traceability requirements but, on the other hand, allows engineers to temporarily deviate from the prescribed software engineering process. Through the observation of developer activities in the form of changes to engineering artifacts in tools such as Jira or Jama, we build up a representation of the ongoing process progress. This tracking in the background does not force the software developer to work only on activities as defined in a process description. At the same time, it enables us to provide timely feedback to the developer on whether tasks fulfill all QA criteria. This approach lifts the burden off QA engineers in manually checking QA constraints, often a time-consuming, tedious, and error-prone task where feedback reaches developers usually very late. We evaluate our approach by applying it to two different case studies; one open source community system and a safety-critical system in the air-traffic control domain. Results from the analysis show that trace links are often corrected or completed after the fact and thus timely and automated constraint checking support has significant potential on reducing rework.
- KonferenzbeitragExperiences on Traceability and Consistency Checking across Engineering Tools in an Automation Solution Company(Software Engineering und Software Management 2018, 2018) Demuth, Andreas; Kretschmer, Roland; Tröls, Michael; Kanakis, Georgios; Maes, Davy; Egyed, AlexanderThe engineering of systems is unimaginable without software tools. Engineers use them to capture and analyze engineering problems; specify, implement, test, and maintain engineering solutions, and manage engineering processes. Yet, there is a gap between the capabilities of independently working engineers and the needs of a collaborative engineering team. The existing tool landscape emphasizes the former. Most engineering tools are single-user applications – often of excellent quality but limited in that they support the works of individual engineers and not that of a group of engineers. And herein lies one of the most fundamental problems of software and systems engineering. Engineers know well the engineering knowledge they capture but they often lack awareness of the many implications their work has on other engineers and/or other engineering domains. This is a problem because in today’s engineering projects, companies continuously have to adapt their systems to changing customer or market requirements. This requires a flexible, iterative development process in which different parts of the system under construction are built and updated concurrently. However, concurrent engineering is quite problematic in domains where different engineering domains and different engineering tools come together. In this paper, we discuss experiences with Van Hoecke Automation, a leading company in the areas of production automation and product processing, in maintaining the consistency between electrical models and the corresponding software controller when both are subject to continuous change. The paper discusses how we let engineers describe the relationships between electrical model and software code in form of links and consistency rules; and how through continuous consistency checking our approach then notified those engineers of the erroneous impact of changes in either electrical model or code.
- KonferenzbeitragIntegrating BPMN- and UML-based Security Engineering via Model Transformation(Software Engineering und Software Management 2018, 2018) Ramadan, Qusai; Salnitri, Mattia; Strüber, Daniel; Jürjens, Jan; Giorgini, PaoloWe present our paper from the proceedings of 2017 edition of the MODELS conference. Tracing and integrating security requirements throughout the development process is a key challenge in security engineering. In socio-technical systems, security requirements for the organizational and technical aspects of a system are currently dealt with separately, giving rise to substantial misconceptions and errors. In this paper, we present a model-based security engineering framework for supporting the system design on the organizational and technical level. The key idea is to allow the involved experts to specify security requirements in the languages they are familiar with: business analysts use BPMN for procedural system descriptions; system developers use UML to design and implement the system architecture. Security requirements are captured via the language extensions SecBPMN2 and UMLsec. We provide a model transformation to bridge the conceptual gap between SecBPMN2 and UMLsec. Using UMLsec policies, various security properties of the resulting architecture can be verified. In a case study featuring an air traffic management system, we show how our framework can be practically applied.
- ZeitschriftenartikelUnderstanding the Re-Engineering of Variant-Rich Systems: An Empirical Work on Economics, Knowledge, Traceability, and Practices(Softwaretechnik-Trends Band 42, Heft 2, 2022) Krüger, JacobMost modern software systems exist in different variants to address a variety of requirements, such as customer requests, regulations, or hardware restrictions. In this dissertation, we empirically study four closely related properties in the context of variant-rich systems, namely economics, knowledge, traceability, and practices. First, we contribute a rich dataset on the economics of (re-)engineering variant-rich systems, from which we derive the core insight that moving towards platform engineering (e.g., via more systematic clone management) is economically promising. Second, we contribute an understanding of developers memory and how to support their knowledge needs, leading to the core insight that expensive reco very activities can be mitigated by enforcing suitable documentation techniques (e.g., feature traceability). Third, we contribute insights on how different feature traces impact developers program comprehension, based on which our core insight is that feature traceabi lity should ideally be independent of configurability. Finally, we contribute a process model and recommendations on how to (re-)engineer variant-rich systems, with our core insight being that carefully planning and periodically assessing a variant-rich system helps to exploit its full potential (e.g., in terms of cost savings).