No abstract

Trace links between requirements and code are beneficial for many software engineering tasks such as maintenance, program comprehension, and re-engineering. If trace links are created and used continuously during a project, they need to have high precision and recall to be useful. However, manual trace link creation is cumbersome and existing automatic trace link creation methods are typically only applied retrospectively and to structured requirements. Therefore, they focus on recall and accept manual effort to cope with low precision. Such manual effort is not acceptable continuously. Furthermore, the maintenance of existing links along with changing artefacts in a project is neglected in most automatic trace link creation approaches. Therefore, we developed and evaluated an interaction log-based trace link creation approach IL to continuously provide correct trace links during a project. IL links unstructured requirements specified in an issue tracker and source code managed in a version control system. In the latest version, I L Com , our approach uses the interactions of developers with files in an integrated development environment and issue identifiers provided in commit messages to create trace links continuously after each commit. In this paper, we present I L Com , its most recent evaluation study, and a systematic literature review (SLR) about trace link maintenance (TM). We also present a TM process for I L Com based on two approaches from our SLR. In the evaluation study, we show that precision of I L Com created links is above 90% and recall almost at 80%. In the SLR, we discuss 16 approaches. Our approach is the first trace link creation approach with very good precision and recall and integrated trace maintenance.

No abstract

Abstract. The increasing adoption of process-aware information systems (PAISs) has resulted in a large number of implemented business processes. To react on changing needs, companies need to be able to quickly adapt these process implementations. Current PAISs only provide mechanisms to evolve the schema of a process, but do not allow for support the automated creation and adaptation of user interfaces (UIs). The latter may have a complex logic and comprise conditional elements or database queries. Creating and evolving UIs manually is a tedious and error-prone task. This paper introduces a set of patterns for transforming fragments of a business process, whose activities are performed by the same user role, to UIs of the PAIS. In particular, UI logic can be expressed using the same notation as for process modeling. Furthermore, a transformation method is introduced, which applies these patterns to automatically derive UIs by establishing a bidirectional mapping between process model and UI. This mapping allows propagating UI changes to the process model and vice versa. Overall, our approach enables process designers to rapidly develop and update complex UIs in PAISs.

No abstract