Use Cases and Traceability

Full paper in Proceedings of the 16th Annual NACCQ, Palmerston North, New Zealand, July, 2003 (eds) Mann, S. and Williamson, A. www.naccq.ac.nz

Use Cases and Traceability: a Marriage for Improved Software Quality
Robert F. Roggio
Professor of Computer and Information Sciences University of North Florida Jacksonville, Florida, USA broggio@unf.edu

ABSTRACT
This paper asserts the close relationship between Use Cases and functional requirements traceability throughout the software development process. Use-case driven application development can provide a natural vehicle that assures the traceability of functional requirements. When functional requirements are both traceable and visible throughout essential development activities to all stakeholders, the likelihood that required functionality will be accommodated in the delivered system is improved. This paper uses the template of the Use Case to introduce a mechanism called traceability identifiers (scenario identifiers) that are used to actually name and track these scenarios through analysis, design, construction, and ultimately to validation. Identifiers are used in a traceability matrix that provides a visible trace of functionality to various stakeholders. Using this matrix requires only a slightly modified development process. This paper asserts that these suggested mechanisms will boost the potential for improved requirements traceability as found in use cases into a set of real development activities undertaken to improve the quality of the delivered system.

1. THE USE CASE / TRACEABILITY LANDSCAPE
Perhaps one of the most serious problems in software development nowadays is the disconnect between analysis and design. While the discipline of computer science considers analysis and design two domains of knowledge, software engineers find it difficult to separate these two activities, as good design often requires additional analysis, while some additional analysis may be required to improve the... [continues]

Read full essay