ACM Home Page
Please provide us with feedback. Feedback
Factors influencing requirements traceability practice
Full text PdfPdf (368 KB)
Source
Communications of the ACM archive
Volume 41 ,  Issue 12  (December 1998) table of contents
Pages: 37 - 44  
Year of Publication: 1998
ISSN:0001-0782
Author
Balasubramaniam Ramesh  Georgia State Univ., Atlanta, GA
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 29,   Downloads (12 Months): 188,   Citation Count: 9
Additional Information:

references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/290133.290147
What is a DOI?

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Eisenhardt, K.M. Building theories from case study research. Acad. Manage. Rev. 14, 4 (Oct. 1989), 532-550.
 
2
 
3
Morgan, D.L. Focus Groups as Qualitative Research. Sage Publications, Newbury Park, Calif., 1988.
 
4
Nejmeh, B.A., Dickey, T.E. and Wartik, S.P. Traceability technology at the software productivity consortium. G.X. In Riter, (Ed). Information Processing '89. Elsevier Science Publishers, New York, (1989).
 
5
Orlikowski, W. CASE Tools as organizational change: Investigating incremental and radical changes in systems development. MIS Q. (Sept. 1993), 309-340.
 
6
 
7
Palmer, J.D. Traceability. Software Requirements Engineering. R.H. Thayer. and M. Dorfman (Eds). IEEE Computer Society Press, New York, 1997.
 
8
 
9
 
10
 
11
Ramesh, B. and Jarke, M. Towards Reference Modek for Requirements Traceability. Technical Report, Georgia State University, 1998.
 
12

CITED BY  9

Collaborative Colleagues:
Balasubramaniam Ramesh: colleagues