(B) Requirements Documentation and Traceability for SWTbahn

This thesis shall conduct a change impact analysis on SWTbahn to establish clear links between its evolving formal requirements, software components and other artefacts. In particular, this thesis shall

(a) explore requirements management and impact analysis tools, and select an appropriate method to realize an impact analysis for SWTbahn;
(b) reorganize the existing SWTbahn documentation and artefacts in preparation for an impact analysis. It may be necessary to propose improvements to the existing documentation, requirements, or artefacts to ensure a successful impact analysis; and
(c) evaluate the chosen impact analysis method on linking SWTbahn’s requirements to existing artefacts, and reflect on the appropriateness of the chosen method.

The ideal student for this thesis topic will have a keen interest in requirements engineering and safety-critical systems. Missing knowledge in some areas or technologies can be acquired during the thesis.

1. Firesmith, D., 2004. Engineering safety requirements, safety constraints, and safety-critical requirements. Journal of Object technology, 3(3), pp.27-42.
2. Goknil, A., Kurtev, I., Van Den Berg, K. and Spijkerman, W., 2014. Change impact analysis for requirements: A metamodeling approach. Information and Software Technology, 56(8), pp.950-972.
3. Martins, L.E.G. and Gorschek, T., 2016. Requirements engineering for safety-critical systems: A systematic literature review. Information and software technology, 75, pp.71-89.
4. Rempel, P., Mäder, P., Kuschke, T. and Cleland-Huang, J., 2014, May. Mind the gap: assessing the conformance of software traceability to relevant guidelines. In Proceedings of the 36th International Conference on Software Engineering (pp. 943-954).
5. Sutcliffe, A., 1998. Scenario-based requirements analysis. Requirements engineering, 3, pp.48-65.