Softwaretechnik-Trends 38(1) - 2018

Autor*innen mit den meisten Dokumenten  

Auflistung nach:

Neueste Veröffentlichungen

1 - 10 von 32
  • Zeitschriftenartikel
    Lessons Learned from Analyzing Requirements Traceability using a Graph Database
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Goman, Maksim; Rath, Michael; Mäder, Patrick
    Established traceability among development artifacts allows to apply structured analysis in order to answer questions posed by stakeholders. Typically, the artifacts and their links are stored in relational databases. However, answering trace related questions involves finding paths and patterns in the artifact graph - a difficult task to perform using generic query languages. Mapping the artifact and link data onto graph databases and utilizing specialized query languages may overcome this limitation. In this paper, this mapping from a relational traceability dataset to a graph database is demonstrated. Afterwards, the advantages and disadvantages of the approach are investigated by calculating three trace metrics, heavily relying on graph patterns, using a graph query language. Overall, utilizing a graph database proved to simplify traceability analysis.
  • Zeitschriftenartikel
    Gleitender Übergang vom manuellen zum automatisierten Test eingebetteter Software
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Bürsner, Simone; Hess, Anne; Queins, Stefan; Schmid, Klaus; Seyff, Norbert
  • Zeitschriftenartikel
    Traceability enabled by Metamodel Integration
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Meier, Johannes; Winter, Andreas
    Traceability supports software development by connecting separated software artifacts explicitly with each other using traceability links. While intra traceability within single artifacts is solvable by a single metamodel, for inter traceability between different separated artifacts their metamodels have to be related to each other. Therefore, this paper presents an approach to realize inter traceability by integrating the metamodels of the artifacts into one metamodel together with their traceability information. The approach is demonstrated in a small software project using requirements, class diagrams, and source code.
  • Zeitschriftenartikel
    Preprocessing Texts in Issue Tracking Systems to improve IR Techniques for Trace Creation
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Todorova Tomova, Mihaela; Mäder, Patrick
    Multiple studies showed the usefulness of requirements traceability in developing software and systems. Still, a major challenge is to establish the required trace links among development artifacts. Often, information retrieval (IR) techniques combined with text similarity measures are used for this task. Applying these ideas to requirements texts found in issue tracking systems (ITS) of open source systems is difficult, because often these texts are structured and not only contain natural language. Thus, preprocessing of the textual information is required to extract the different kinds of text. In this paper, the authors study the structure of issue descriptions found in open source systems and identify several categories of text found therein, such as source code and stack traces. These text categories allow a more precise application of similarity analysis in order to create traces by comparing textual information of the same kind, i. e. source code with source code and natural language with natural language.
  • Zeitschriftenartikel
    Challenges in Using Interaction Data for Trace Link Creation
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Hübner, Paul; Paech, Barbara
    For direct usage of trace links during a development project the precision of information retrieval (IR) based trace link creation is not sufficient [1]. Too many false links generated by IR hinder developers to directly use the resulting links and require further assessment by an expert. Thus, we develop an interaction based trace link creation approach (IL) aiming to create trace links with perfect precision. In IL we utilize the interactions of developers recorded in the IDE while working on a requirement. We already performed an evaluation of our IL approach with open source data [2]. For that we could show that IL creates trace links with perfect precision and has a better recall than IR. However, in a follow up evaluation in which we applied our approach in a student project it turned out that the precision of created trace links was not perfect. Now we are investigating the reasons for this not perfect precision, in particular we try to find techniques to detect wrong links. In this short paper we motivate and introduce our IL approach, compare the two different projects in which we applied IL, discuss reasons why links created by IL can be wrong and outline the challenges how to countervail the creation of wrong links.
  • Zeitschriftenartikel
    Erhebung von Trace Links fur die koordinierte, plattformubergreifende Co-Evolution portierter Software
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Stehle, Tilmann; Riebisch, Matthias
  • Zeitschriftenartikel
    Softwaretechnik-Trends Band 38, Heft 1
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) GI-FB Softwaretechnik
  • Zeitschriftenartikel
    Aufruf zur Einreichung von Beiträgen zum Workshop Konstruktion von SafeWare
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) FG ADA
  • Zeitschriftenartikel
    State of the Art of Traceability in Open-Source Projects
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Rath, Michael; Goman, Maksim; Mäder, Patrick
    Software and systems traceability is widely accepted as an essential element for supporting many software development tasks. Todays version control systems provide inbuilt features that allow developers to tag each commit with one or more issue IDs, thereby providing the building blocks from which project-wide traceability can be established between feature requests, bug fixes, commits, source code, and tests. We analyzed seven large open source projects to investigate to what extent developers explicitly established traces between issues and commits. Therefore, we categorized resolved issues and commits and studied the traces between the resulting artifact clusters. Among other metrics, our research shows, that 70% of all resolved issues are linked to commits. However, in the opposite direction, only 48% of the commits are linked to issues. Thus, open-source developers actively establish traceability. Nevertheless, automated traceability techniques might increase the amount of interlinking.
  • Zeitschriftenartikel
    Early Model-Driven Timing Validation of Embedded Software Systems Developed Using Matlab/Simulink
    (Softwaretechnik-Trends Band 38, Heft 1, 2018) Iyenghar, Padma; Pulvermueller, Elke
    This paper presents a model-driven workflow for specification of timing constraints in Matlab/Simulink (ML/SL), their extraction and synthesis of a timing analysis model and its subsequent validation in a specialized timing validation tool (e.g. SymTA/S). We present a light-weight interfacing tool framework, adhering to the proposed workflow, and evaluate it in a real-life automotive engine model example. A main benefit of this work is the feedback at early d design stage, about the performance characteristics (e.g. load, schedulability) of the system.