Software traceability; Artifact alignment; Software evolution; Documentation update
Hotomski Sofija, Glinz Martin (2019), GuideGen: An approach for keeping requirements and acceptance tests aligned via automatically generated guidance, in Information and Software Technology
, 110, 17-38.
Hotomski Sofija, Glinz Martin (2018), A Qualitative Study on using GuideGen to Keep Requirements and Acceptance Tests Aligned, in 2018 IEEE 26th International Requirements Engineering Conference (RE)
, Banff, ABIEEE Computer Society, Los Alamitos, CA..
Hotomski Sofija, Glinz Martin (2018), GuideGen – A Tool for Keeping Requirements and Acceptance Tests Aligned, in the 40th International Conference
, Gothenburg, SwedenACM, New York NY.
Hotomski Sofija, Ben Charrada Eya, Glinz Martin (2018), Keeping Evolving Requirements and Acceptance Tests Aligned with Automatically Generated Guidance, in Requirements Engineering: Foundation for Software Quality (REFSQ 2018)
, Utrecht, The NetherlandsSpringer International Publishing, Cham.
Hotomski Sofija, Charrada Eya Ben, Glinz Martin (2017), Aligning Requirements and Acceptance Tests via Automatically Generated Guidance, in 2017 IEEE 25th International Requirements Engineering Conference Workshops (REW)
, Lisbon, PortugalIEEE Computer Society, Los Alamitos, CA..
Sofija Hotomski, Eya Ben Charrada, Martin Glinz (2016), An Exploratory Study on Handling Requirements and Acceptance Test Documentation in Industry, in 24th IEEE International Requirements Engineering Conference
The knowledge about a software system is scattered through several artifacts, which together constitute the system's documentation. Key artifacts containing such knowledge include the requirements specification, software architecture and design, source code, tests, and user manual. Preserving the knowledge contained in all these artifacts is crucial for ensuring a high quality software system that can be easily maintained and extended. For example, if a requirements specification has become obsolete, the ability to trace system features to the rationale why these features have been implemented is lost. Similarly, when the architecture document becomes obsolete, the knowledge about design decisions and why they have been taken is lost. This is becoming even more crucial nowadays, as systems are continuously evolved and tailored to individual customers' needs.If software artifacts are not maintained and updated when a system evolves, they progressively become outdated and useless. Nevertheless, due to time and cost constrains, developers often neglect updating the entire documentation and apply the changes to the source code only. This negatively affects a system's maintainability and increases the cost of adapting a system to changes in its environment and to new or changed needs of its users.The goal of this project is to investigate new methods to address the problem of outdated software documentation. We will explore new techniques that merge information from different artifacts to generate precise traceability links between the software artifacts. We will also develop an approach that automates parts of the change propagation task between software artifacts. The approach will be based on an analysis of the relations that exist between different types of software artifacts at the evolution stage.The outcome of this research will extend the scientific knowledge in the fields of software traceability, software documentation and software evolution. It will also improve current software development practice by reducing the effort needed for keeping software documentation up-to-date, thus encouraging maintainers to perform documentation updates regularly.