Requirements Traceability for Detecting Defects in Agile Software Development

The process of developing applications with agile methods especially extreme programming (XP) is very popular these days. The short iteration process makes software development faster. However, this method has weaknesses on the documentation side that makes it difficult to see the defect related to the requirements level, coupled with changes that can occur quickly and continuously. In this study, the author will look at the extent of software quality management at each stage of this method and build traceability using the Requirement Traceability Matrix (RTM). After the matrix is formed, each document contained in it can be taken as information that affects the occurrence of bugs during the development and defect at the end of the product when released. In the requirements document, it can be seen how many times there have been changes or additions. At each stage of the test the number of tests performed at each stage can be seen, and the time it takes for the application to pass each test. All of these variables will be seen as correlated to the number of bugs and defects. Seen the number of tests and the number of additional requirements has a strong correlation to the number of bugs appearing throughout the development process and defects at the end of the product release. It can be concluded that tracing the relationship between requirements, testing, and implementation at the code level is very important to identify the quality of the software.