Collaborative conceptual design: A large software project case study

Computer Supported Cooperative Work

Volumn 5, Issue 4, 1996, Pages 415-445

  Potts, Colin ^a   Catledge, Lara ^a  

^a Georgia Institute of Technology   (United States)

Author keywords

Collaboration; Conceputal design; Software process

Indexed keywords

COMPUTER AIDED DESIGN; COMPUTER SYSTEMS PROGRAMMING; SOFTWARE PROTOTYPING;

COLLABORATIVE SUPPORT TOOLS;

COMPUTER AIDED SOFTWARE ENGINEERING;

EID: 0030365732     PISSN: 09259724     EISSN: None     Source Type: Journal    
DOI: 10.1007/BF00136713     Document Type: Article

References (28)

1. Atwood, M.E., B. Burns, D. Gairing, A. Girgensohn, A. Lee, S. Turner, S. Alteras-Webb, and B. Zimmermann (1995): Facilitating Communication in Software Development. In Proceedings DIS'95: Symposium on Designing Interactive Systems, Ann Arbor, MI, August 23-25. New York: ACM Press, pp. 65-73.
2. Berlin, L.M., R. Jeffries, V.L. O'Day, A. Paepcke, and C. Wharton (1993): Where Did You Put It? Issues in the Design and Use of a Group Memory. In Proc. InterCHI, Amsterdam, Netherlands. New York: ACM Press, pp. 23-30.
3. Boehm, B. (1983): Software Engineering Economics. Engelwood Cliffs, NJ: Prentice-Hall.
4. Brooks, F. (1986): No Silver Bullet. In Proceedings of the IFIP Tenth World Computing Congress, Dublin, Ireland. Amsterdam: Elsevier, pp. 1069-1076.
5. Conklin, J. and M. Begeman (1989): gIBIS: A Tool for all Reasons. J. Am. Soc. Inf. Sci., May, pp. 200-213.
6. Curtis, B., H. Krasner, and N. Iscoe (1988): A Field Study of the Software Design Process for Large Teams. Comm. ACM, vol. 31, no. 11, pp. 1268-1287.
7. Fagan, M. (1976): Design and Code Inspections to Reduce Errors in Program Development. IBM Systems Journal, vol. 15, no. 3, pp. 182-211.
8. Grudin, J. (1988): Why Groupware Applications Fail: Problems in Design and Evaluation. Office: Technology and People, vol. 4, no. 3, pp. 245-264.
9. Keil, M. and E. Carmel (1995): Customer-Developer Links in Software Development. Comm. ACM, vol. 38, no. 5, pp. 33-44.
10. Kraut, R.F. and L.A. Streeter (1995): Coordination in Software Development. Comm. ACM, vol. 38, no. 3, pp. 69-81.
11. Kuhn, T. (1970): The Structure of Scientific Revolutions, 2nd Ed. Chicago: Univ. Chicago Press.
12. Kunz, W. and H. Rittel (1970): Issues as Elements of Information Systems. Working Paper 131, Institute of Urban and Regional Development, University California at Berkeley.
13. Kuwana, E. and J.D. Herbsleb (1993): Representing Knowledge in Requirements Engineering: An Empirical Study of What Software Engineers Need to Know. In Proc. RE 93: IEEE Int. Symp. Requirements Eng., San Diego, CA Jan 4-6. IEEE Computer Society Press, pp. 273-276.
14. Lai, K.-Y., T.W. Malone, and K.-C. Yu (1988): Object Lens: A "Spreadsheet" for Cooperative Work. ACM Trans. Office Inf. Sys., vol. 6, no. 4, pp. 332-353.
15. Lee, J. (1991): Extending the Potts and Bruns Model for Recording Design Rationale. In Proc. 13th Int. Conf. Software Eng. IEEE Computer Society Press, pp. 114-127.
16. Lubars, M., C. Potts, and C. Richter (1993): A Review of the State of Practice in Requirements Modeling. In Proc. IEEE Symp. Requirements Eng. (RE'93), San Diego, CA, January 4-6. IEEE Computer Society Press, pp. 2-14.
17. Paulk, M., B. Curtis, M. Chrissis, and C. Weber (1995): The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley.
18. Potts, C. (1995): Using Schematic Scenarios to Understand User Needs. In Proceedings DIS'95: Symposium on Designing Interactive Systems, Ann Arbor, MI, August 23-25. New York: ACM Press, pp. 247-256.
19. Potts, C., J.D. Bolter, and A. Badre (1993): Collaborative Pre-Writing with a Video-Based Group Working Memory. Georgia Institute of Technology, GVU Technical Report, pp. 93-35.
20. Potts, C. and G. Bruns (1988): Recording the Reasons for Design Decisions. In Proc. 10th Int. Conf. Software Eng., Singapore (May). IEEE Computer Society Press, pp. 418-427.
21. Potts, C. and K. Takahashi (1993): An Active Hypertext Model for System Requirements. In Proc. 7th Int. Workshop Software Specification and Design, Redondo Beach (December). IEEE Computer Society Press, pp. 62-67.
22. Potts, C., K. Takahashi, and A. Anton (1994): Inquiry-Based Requirements Analysis, IEEE Software, vol. 11, no. 2, pp. 21-32.
23. Russell, D.M., M.J. Stefik, P. Pirolli, and S.K. Card (1993): The Cost Structure of Sensemaking. In Proc. InterCHI, Amsterdam, Netherlands. New York: ACM Press, pp. 269-276.
24. Schon, D.A. (1983): The Reflective Practitioner: How Professionals Think in Action. New York: Basic Books.
25. Sharples, M. (1993): Adding a Little Structure to Collaborative Writing. In CSCW in Practice: An Introduction and Case Studies, eds. D. Diaper and C. Sanger. London: Springer, pp. 51-67.
26. Suchman, L. (1983): Office Procedures as Practical Action: Models of Work and System Design. ACM Trans. Office Systems, vol. 1, no. 4, pp. 320-328.
27. Terveen, L.G., P.G. Selfridge, and M.D. Long (1995): Living Design Memory: Framework, Implementation, Lessons Learned. HCI, vol. 10, no. 1, pp. 1-38.
28. Walz, D., B. Curtis, and J. Elam (1993): Inside a Software Design Team: Knowledge Acquisition, Sharing and Integration. Comm. ACM, vol. 36, no. 10, pp. 62-77.