Volume 5
Volume 5, Number 19 |
June 5, 2007 |
|
Robert F. Roggio
|
Abstract: Computing programs typically have a capstone course or sequence wherein students customarily marshal their academic skills and specify, design and develop a modern, often web-based, application. The process guiding this development may be a light-weight methodology or a heavy-weight methodology – or somewhere in between; the development may be implemented using a traditional, procedural approach or an object-oriented approach. But in any event, stakeholder needs must ultimately be mapped into a requirements specification that supports follow-on design and implementation. This paper provides the motivation, mechanism, and empirical data showing how the infusion of requirements traceability into a capstone sequence is low in cost, high in value, and easy to implement.
Keywords: capstone software development; requirements traceability
Download this issue: ISEDJ.5(19).Roggio.pdf (Adobe PDF, 11 pages, 512 K bytes)
Preview the contents: Roggio.j.txt (ASCII txt, 24 K bytes)
Recommended Citation: Roggio (2007). Inserting Requirements Traceability into the Capstone Sequence. Information Systems Education Journal, 5 (19). http://isedj.org/5/19/. ISSN: 1545-679X. (A preliminary version appears in The Proceedings of ISECON 2006: §2152. ISSN: 1542-7382.)