This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
An Object-Oriented Tool for Tracing Requirements
March 1996 (vol. 13 no. 2)
pp. 52-64
Tracing requirements helps verify system features against the requirements specification, identify error sources, and — most importantly — manage change. We describe a tool called TOOR (Traceability of Object-Oriented Requirements), based on Joseph Goguen's broad view of requirements, which suggests that not only technical but also social factors play a significant role in software development. Of course, the requirements themselves are not necessarily object-oriented. Our tool's name is derived more from its use for object-oriented development and its object-oriented implementation, which allows the definition of classes and subclasses of objects and relationships among objects. Requirements traceability is our primary topic, but the scope of the tool reflects our view that requirements issues are pervasive and occur throughout the life cycle. Therefore, requirements traceability should be available at all times, and traceability of any desired artifacts should be supported.
Citation:
Francisco A.C. Pinheiro, Joseph A. Goguen, "An Object-Oriented Tool for Tracing Requirements," IEEE Software, vol. 13, no. 2, pp. 52-64, March 1996, doi:10.1109/52.506462
Usage of this product signifies your acceptance of the Terms of Use.