You should read at least two papers each in your group, and make sure you cover all sources. You are free to look at additional material.

Ball, T., & Rajamani, S. K. (2000). The SLAM toolkit. In Proceedings of CAV’2001 (13th Conference on Computer Aided Verification) (Vol. 2102, pp. 260-264)
Kamburjan, E., & Hähnle, R. (2016, November). Uniform modeling of railway operations. In International Workshop on Formal Techniques for Safety-Critical Systems (pp. 55-71). Springer, Cham.
Parnas, D. L., Asmis, G. J. K., & Madey, J. (1991). Assessment of safety-critical software in nuclear power plants. Nuclear safety, 32(2), 189-198.
Lutz, R. R., & Mikulski, I. C. (2003, May). Requirements discovery during the testing of safety-critical software. In 25th International Conference on Software Engineering, 2003. Proceedings. (pp. 578-583). IEEE.
Hähnle, R., & Huisman, M. (2019). Deductive software verification: from pen-and-paper proofs to industrial tools. In Computing and Software Science (pp. 345-373). Springer, Cham.

Prepare a presentation on the key points of each paper, and also think about the "big picture":

How have test and verification tools and methods evolved in the last 30 years?
What were the limitations of these approaches in the past, and what are they now?
What is the role of requirements in verification and validation?