This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Traceability Process for Large OO Projects
September 1996 (vol. 29 no. 9)
pp. 63-68

Object-oriented software development has become popular, but scaling it up for large projects has been a problem. With large OO projects, late integration problems are a particular concern. They can cause schedule slippage and other difficulties. I developed a process called Traceability for OO Quality Engineering, or TOOQE, to minimize such problems. TOOQE emphasizes traceability and the integration of development and testing to achieve quality and maintainability. TOOQE features an iterative design process that lets developers correct mistakes and learn more about the problem they are trying to solve as they go along. Each iteration includes requirements capture, analysis, design, coding, and testing. In other words, each is a mini-life cycle. TOOQE's approach is also incremental. This lets each iteration build on its predecessor and eliminates the need to retest functionality at each iteration. Integration does not occur late in the process in TOOQE but instead occurs at each iteration. Moreover, integration entails immediate testing of the integrated artifacts, thus providing early and continuous feedback. For object-oriented analysis and design, you use three views of the system. The expression of each view requires at least one model, so OOA and OOD lead to the production of several models.

Citation:
Jean-Pierre Corriveau, "Traceability Process for Large OO Projects," Computer, vol. 29, no. 9, pp. 63-68, Sept. 1996, doi:10.1109/2.536785
Usage of this product signifies your acceptance of the Terms of Use.