Object-Oriented Analysis and Design in Software Project Teams

Human-Computer Interaction

Volumn 10, Issue 2-3, 1995, Pages 249-292

  Herbsleb, James D ^a   Klein, Helen ^a   Olson, Gary M ^b   Brunner, Hans ^c   Olson, Judith S ^b   Harding, Joe ^d  

^a University of Michigan ^*

^b UNIVERSITY OF MICHIGAN   (United States)

^c U S WEST Inc   (United States)

^d NONE   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COGNITIVE SYSTEMS; COMPUTER SOFTWARE; HUMAN COMPUTER INTERACTION; KNOWLEDGE ACQUISITION; OBJECT ORIENTED PROGRAMMING; PROJECT MANAGEMENT;

OBJECT ORIENTED ANALYSIS; OBJECT ORIENTED DESIGN; SOFTWARE PROJECT TEAMS;

SOFTWARE ENGINEERING;

EID: 0029237832     PISSN: 07370024     EISSN: 15327051     Source Type: Journal    
DOI: 10.1080/07370024.1995.9667219     Document Type: Article

References (51)

1. Anderson, J. R. (1983). The architecture of cognition. Cambridge, MA: Harvard University Press.
2. Booch, G. (1991). Object oriented design with applications. Redwood City, CA: Benja-min/Cummings.
3. Brooks, F. P. (1975). The mythical man-month: Essays on software engineering. Reading, MA: Addison-Wesley.
4. Brooks, F. P. (1987). No silver bullet. IEEE Computer, 20, 10–19.
5. Bruegge, B., Blythe, J., Jackson, J., & Shufelt, J. (1992). Object-oriented system modeling with O MT. Proceedings of OOPSLA ‘92, 359–376. Vancouver: ACM.
6. Champeaux, D. D., Anderson, A., & Feldhousen, E. (1992). Case study of object-oriented software development. Proceedings of OOPSLA ‘92, 377–391. Vancouver: ACM.
7. Chi, M. T. H., Feltovich, P. J., & Glaser, R. (1981). Categorization and representation of physics problems by experts and novices. Cognitive Science, 5, 121–152.
8. Coad, P. (1992). Object-oriented patterns. Communications of the ACM, 35, 152–159.
9. Coad, P., & Yourdon, E. (1991). Object-oriented analysis (2nd ed.). Englewood Cliffs, NJ: Prentice-Hall.
10. Constantine, L. L. (1993). Work organization: Paradigms for project management and organization. Communications of the ACM, 36, 35–43.
11. Curtis, B., Krasner, H., & Iscoe, N. (1988). A field study of the software design process for large systems. Communications of the ACM, 31, 1268–1287.
12. Curtis, B., & Walz, D. (1990). The psychology of programming in the large: Team and organizational behavior. In J.-M. Hoc, T. R. G. Green, R. Samurçay, & D. J. Gilmore (Eds.), Psychology of programming (pp. 253–270). London: Academic.
13. Fenton, N. (1993). How effective are software engineering methods? Journal of Systems and Software, 22, 141–146.
14. Fienberg, S. E. (1980). The analysis of cross-classified categorical data (2d ed.). Cambridge, MA: MIT Press.
15. Galbraith, J. (1973). Designing complex organizations. Reading, MA: Addison-Wesley.
16. Gentner, D. (1981). Some interesting differences between verbs and nouns. Cognition and Brain Theory, 4, 161–178.
17. Gentner, D., & France, I. M. (1988). The verb mutability effect: Studies of the combinatorial semantics of nouns and verbs. In S. I. Small, G. W. Cottrell, & M. K. Tanenhaus (Eds.), Lexical ambiguity resolution: Perspectives from psycholinguistics, neuropsychology and artificial intelligence (pp. 343–382). San Mateo, CA: Morgan Kaufman.
18. Gottman, J. M., & Roy, A. K. (1990). Sequential analysis: A guide for behavioral researchers. New York: Cambridge University Press.
19. Henderson-Sellers, B., & Edwards, J. M. (1990). The object-oriented systems life cycle. Communications of the ACM, 33, 142–159.
20. Herbsleb, J. D., & Kuwana, E. (1993). Preserving knowledge in software engineering: What designers need to know. Proceedings of lNTERCHI ‘93, 7–14. New York: ACM.
21. Hutchins, E. (1990). The technology of team navigation. In J. Galegher, R. E. Kraut, & C. Egido (Eds.), Intellectual teamwork (pp. 191–220). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
22. Hutchins, E. (in press). How a cockpit remembers its speed. Cognitive Science.
23. Jacobson, I., Christerson, M.,Johnsson, P., & Overgaard, G. (1992). Object-oriented software engineering: A use case driven approach. Reading, MA: Addison-Wesley.
24. Jeffries, R., Turner, A. A., Poison, P. G., & Atwood, M. (1981). The processes involved in designing software. In J. R. Anderson (Ed.), Cognitive skills and their acquisition (pp. 255–283). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
25. Johnson, R. E., & Russo, V. F. (1991). Reusing object-oriented designs (Technical Report UIUCDCS 91–1696). Champaign: University of Illinois.
26. Karat, J., & Bennett, J. L. (1991). Working within the design process: Supporting effective and efficient design. In J. M. Carroll (Ed.), Designing interaction: Psychology at the human-computer interface (pp. 269–285). New York: Cambridge University Press.
27. Krasner, H., Curtis, B., & Iscoe, N. (1987). Communication breakdowns and boundary spanning activities on large programming projects. In G. M. Olson, S. Sheppard, & E. Soloway (Eds.), Empirical studies of programmers: Second workshop (pp. 47–64). Norwood, NJ: Ablex.
28. Kraut, R. E., & Streeter, L. A. (in press). Coordination in large scale software development. Communications of the ACM.
29. Krueger, C. W. (1992). Software reuse. ACM Computing Surveys, 24, 131–183.
30. Kuwana, E., & Herbsleb, J. D. (1993). Representing knowledge in requirements engineering: An empirical study of what software engineers need to know. Proceedings of the IEEE International Symposium on Requirements Engineering, 273–276. San Diego: IEEE Computer Society Press.
31. Lubars, M., Potts, C., & Richter, C. (1993). A review of the state of the practice in requirements modeling. Proceedings of the IEEE International Symposium on Requirements Engineering, 2–14. San Diego: IEEE Computer Society Press.
32. Malhotra, A., Thomas, J. C., Carroll, J. M., & Miler, L. A. (1980). Cognitive processes in design. International Journal of Man-Machine Studies, 12, 119–140.
33. Martin, J., & Odell, J. J. (1992). Object-oriented analysis and design. Englewood Cliffs, NJ: Prentice-Hall.
34. McGrath J. E. (1984). Groups: Interaction and performance. Englewood Cliffs, NJ: Prentice-Hall.
35. McKeithen, K. B., ReitmanJ. S., Rueter, H. H., & Hirtle, S. C. (1981). Knowledge organization and skill differences in computer programmers. Cognitive Psychology, 13, 307–325.
36. Meyer, B. (1992). The new culture of software development: Reflections on the practice of object-oriented design. In D. Mandrioli & B. Meyer (Eds.), Advances in object-oriented software engineering (pp. 51–64) Englewood Cliffs, NJ: Prentice-Hall.
37. Miller, G. A. (1991). The science of words. New York: Scientific American Library.
38. Nakajo, T., & Kume, H. (1991). A case history analysis of software error cause-effect relationships. IEEE Transactions on Software Engineering, 17, 830–837.
39. Nascimento, C., & Dollimore, J. (1993). A model for cooperative object-oriented programming. Software Engineeringjournal, 8, 41–48.
40. Nierstrasz, O., Gibbs, S., & Tsichritzis, D. (1992). Component-oriented software development. Communications of the ACM, 35, 160–165.
41. Olson, G. M., Herbsleb, J. D., & Rueter, H. H. (1994). Characterizing the sequential structure of interactive behaviors through statistical and grammatical techniques. Human-Computer Interaction, 9, 427–472.
42. Olson, G. M., Olson, J. S., Carter, M. R., & Storrøsten, M. (1992). Small group design meetings: An analysis of collaboration. Human-Computer Interaction, 7, 347–374.
43. Olson, G. M., Olson, J. S., Storrøsten, M., Carter, M., Herbsleb, J., & Rueter, H. (in press). The structure of activity during design meetings. In T. P. Moran & J. M. Carroll (Eds.), Design rationale. Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
44. Olson, J. S., Olson, G. M., Storrøsten, M., & Carter, M. (1993). Groupwork close up: A comparison of the group design process with and without a simple group editor. ACM Transactions on Information Systems, 11, 321–348.
45. Potts, C. (1993). Panel: “I never knew my requirements were object-oriented until I talked to my analyst”. Proceedings of the IEEE International Symposium on Requirements Engineering, 226. San Diego: IEEE Computer Society Press.
46. Rosch, E. (1978). Principles of categorization. In E. Rosch & B. Lloyd (Eds.), Cognition and categorization (pp. 28–49). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
47. Rosch, E., Mervis, C. B., Gray, W., Johnson, D., & Boyes-Braem, P. (1975). Basic objects in natural categories. Cognitive Psychology, 8, 133–156.
48. Rosson, M. B., & Alpert, S. R. (1990). The cognitive consequences of object-oriented design. Human-Computer Interaction, 5, 345–379.
49. Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., & Lorensen, W. (1991). Object-oriented modeling and design. Englewood Cliffs, NJ: Prentice-Hall.
50. Walz, D. B., Elam, J. J., & Curtis, B. (1993). Inside a software design team: Knowledge acquisition, sharing, and integration. Communications of the ACM, 36, 62–77.
51. Wirfs-Brock, R., Wilkerson, B., & Wiener, L. (1990). Designing object-oriented software. Englewood Cliffs, NJ: Prentice-Hall.