2024
C.T.N. Strong
It is often imperative that the software system be able to make emergency changes while also dynamically updating the requirements document to avoid any possible inconsistencies. A model that could be used to ensure that requirement documentation aligns with system implementation is with a traceability matrix. A traceability matrix is an ‘at-a-glance’ way of seeing the dependencies between requirements (Sommerville, 2015). Being that the traceability matrix uses a spreadsheet to keep track of documentation, this allows for easy screeching for the correct part of the documentation that needs to be modified. This modular process allows for only the needed parts of the documentation to be updated. Changes can then be made without any effects to other parts of the document (Sommerville, 2015). Therefore, not only can modifications be made independently from the whole, but also the document can be changed as well without affecting the whole document. This model is effective for use before changes to the requirements have been approved. It is effective because it allows for a way for changes to be made and documented simultaneously. The traceability matrix can be seen as an intermediate to the final approved requirement documentation. In conclusion, this module is very effective when making “on the fly” changes to both the system and its requirements documentation. Once all requirements have been approved, documentation can then be detailed and copied into a finalized document.
References
Sommerville, I (2015). Software Engineering (10th ed.). Pearson. ISBN- 9780133943030