The Cognitive Consequences of Object-Oriented Design

Human–Computer Interaction

Volumn 5, Issue 4, 1990, Pages 345-379

  Rosson, Mary Beth ^a   Alpert, Sherman R ^a  

^a IBM T J WATSON RESEARCH CENTER   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER PROGRAMMING LANGUAGES; COMPUTER SOFTWARE; SYSTEMS SCIENCE AND CYBERNETICS--COGNITIVE SYSTEMS;

OBJECT-ORIENTED DESIGN; PROBLEM DECOMPOSITION; PROBLEM UNDERSTANDING;

COMPUTER PROGRAMMING;

EID: 0025539354     PISSN: 07370024     EISSN: 15327051     Source Type: Journal    
DOI: 10.1207/s15327051hci0504_1     Document Type: Article

References (89)

1. Adelson, B., Soloway, E. (1984). A cognitive model of software design (Tech. Rep. No. 342). New Haven, CT: Yale University, Department of Computer Science.
2. Adelson, B., Soloway, E. (1985). The role of domain experience in software design. IEEE Transactions on Software Engineering, 11, 233-242.
3. Alavi, M. (1984). An assessment of the prototyping approach to information systems development. Communications of the ACM, 27, 556-562.
4. Barsalou, L. W. (1983). Ad hoc categories. Memory Cognition, 11, 211-227.
5. Beck, K. (1986). Position paper for “Panel: The learnability of object-oriented systems.” Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 502-503). New York: ACM.
6. Blake, E., Cook, S. (1987). On including part hierarchies in object-oriented languages, with an implementation in Smalltalk. Proceedings of the European Conference on Object-Oriented Programming (pp. 41-50). Berlin: Springer-Verlag.
7. Bobrow, D. G., Stefik, M. J. (1986). Perspectives on artificial intelligence programming. Science, 231, 951-957.
8. Borning, A. H. (1979). ThingLab: A constraint-oriented laboratory (Tech. Rep. No. SSI-79-3). Palo Alto, CA: Xerox Palo Alto Research Center.
9. Borning, A. H. (1981). The programming language aspects of ThingLab, aconstraintoriented simulation laboratory. ACM Transactions on Programming Languages and Systems, 3, 353-387.
10. Booch, G. (1983). Software engineering with Ada. Menlo Park, CA: Benjamin/ Cummings.
11. Booch, G. (1986). Object-oriented development. IEEE Transactions on Software Engineering, SE-12(2), 211-221.
12. Borgida, A., Greenspan, S., Mylopoulos, J. (1986). Knowledge representations as the basis for requirements specifications. In C. Rich R. C. Waters (Eds.), Readings in artificial intelligence and software engineering (pp. 561-570). Los Altos, CA: Kaufmann.
13. Brooks, F. P., Jr. (1987). Essence and accidents of software engineering. IEEE Computer, 20(4), 10-19.
14. Caporael, L. R. (1986). Anthropomorphism and mechanomorphism: Two faces of the human machine. Computers in Human Behavior, 2, 215-234.
15. Carroll, J. M. (1990). The Nürnberg funnel: Designing minimalist instruction for practical computer skill. Cambridge, MA: MIT Press.
16. Carroll, J. M., Campbell, R. L. (1989). Artifacts as psychological theories: The case of human-computer interaction. Behaviour and Information Technology, 8, 247-256.
17. Carroll, J. M., Mack, R. L. (1983). Actively learning to use a word processor. In W. E. Cooper (Ed.), Cognitive aspects of skilled typewriting (pp. 259-281). Berlin: Springer-Verlag.
18. Carroll, J. M., Mack, R. L. (1985). Metaphor, computing systems, and active learning. International Journal of Man-Machine Studies, 22, 39-57.
19. Carroll, J. M., Mack, R. L., Kellogg, W. A. (1988). Interface metaphors and user interface design. In M. Heiander (Ed.), Handbook of human-computer interaction (pp. 67-85). Amsterdam: New Holland.
20. Carroll, J. M., Rosson, M. B. (1987). Paradox of the active user. In J. M. Carroll (Ed.), Interfacing thought: Cognitive aspects of human-computer interaction (pp. 80-111). Cambridge, MA: MIT Press.
21. Carroll, J. M., Smith-Kerker, P. L., Ford, J. R., Mazur-Rimetz, S. A. (1987-1988). Human-Computer Interaction, 3, 123-153.
22. Carroll, J. M., Thomas, J. C. (1982). Metaphor and the cognitive representation of computing systems. IEEE Transactions on Systems, Man, and Cybernetics, SMC-12, 107-116.
23. Carroll, J. M., Thomas, J. C., Malhotra, A. (1979). Clinical-experimental analysis of design problem solving. Design Studies, 1, 84-92.
24. Cox, B.J. (1984). Message/object programming: An evolutionary change in programming technology. IEEE Software, 1, 50-61.
25. Cox, B. J. (1986). Object oriented programming: An evolutionary approach. Reading, MA: Addison-Wesley.
26. Dijkstra, E. W. (1972). Notes on structured programming. In O. J. Dahl, E. W. Dijkstra, C. A. R. Hoare (Eds.), Structured programming (pp. 1-82). New York: Academic.
27. Dunn, R. (1984). Software defect removal. New York: McGraw-Hill.
28. Foss, D. J., Smith-Kerker, P. L., Rosson, M. B. (1987). On comprehending a computer manual: Analysis of variables affecting performance. International Journal of Man-Machine Studies, 26, 277-300.
29. Freeman, P. (1987). Software perspectives: The system IS the message. Reading, MA: Addison-Wesley.
30. Gentner, D. (1983). Structure mapping: A theoretical framework for analogy. Cognitive Science, 7, 155-170.
31. Goldberg, A., Kay, A. (1977). Methods for teaching the programming language Smalltalk (Report No. SSL 77-2). Palo Alto, CA: Xerox Palo Alto Research Center.
32. Goldberg, A., Robson, D. (1983). Smalltalk-80: The language and its implementation. Reading, MA: Addison-Wesley.
33. Gould, J. D., Boies, S. J., Levy, S., Richards, J. T., Schoonard, J. (1987). The 1984 Olympic Message System — A case study in system design. Communications of the ACM, 30, 758-769.
34. Guindon, R., Curtis, B. (1988). Control of cognitive processes during software design: What tools are needed? Proceedings of the CHI ′88 Conference on Human Factors in Computing Systems, 263-268. New York: ACM.
35. Guindon, R., Curtis, B., Krasner, H. (1987). A model of cognitive processes in software design: An analysis of breakdowns in early design activities by individuals (Tech. Rep. No. STP-283-87). Austin, TX: Microelectronics and Computer Technology Corporation.
36. Halbert, D. (1986). Position paper for “Panel: The learnability of object-oriented systems.” Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 503-504). New York: ACM.
37. Halbert, D. C., O'Brien, P. D. (1987). Using types and inheritance in object-oriented programming. IEEE Software, 4, 71-79.
38. Hammond, N., Jorgensen, A., MacLean, A., Barnard, P., Long, J. (1983). Design practice and interface usability: Evidence from interviews with designers. Proceedings of the CHI ′83 Conference on Human Factors in Computing Systems, 40-44. New York: ACM.
39. Harold, F. G. (1986). Experimental evaluation of program quality using external metrics. In E. Soloway S. Iyengar (Eds.), Empirical studies of programmers (pp. 153-167). Norwood, NJ: Ablex.
40. Hutchins, E. L., Hollan, J. D., Norman, D. A. (1986). Direct manipulation interfaces. In D. A. Norman S. W. Draper (Eds.), User centered system design (pp. 87-124). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
41. Jackson, M. (1975). Principles of program design. New York: Academic.
42. Jeffries, R., Turner, A. A., Poison, P., Atwood, M. E. (1981). The processes involved in designing software. In J. R. Anderson (Ed.), Cognitive skills and their acquisition (pp. 225-283). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
43. Kant, E., Newell, A. (1984). Problem solving techniques for the design of algorithms. Information Processing and Management, 28, 97-118.
44. Laurel, B. K. (1986). Interface as mimesis. In D. A. Norman S. W. Draper (Eds.), User centered system design (pp. 67-86). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
45. Letovsky, S., Pinto, J., Lampert, R., Soloway, E. (1987). A cognitive analysis of code inspection. In G. M. Olson, S. Sheppard, E. Soloway (Eds.), Empirical studies of programmers: Second workshop (pp. 231-247). Norwood, NJ: Ablex.
46. Liberman, H. (1986). Using prototypical objects to implement shared behavior in object oriented systems. In N. Meyrowitz (Ed.), Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 214-223). New York: ACM.
47. Littman, D. C., Pinto, J., Letovsky, S., Soloway, E. (1986). Mental models and software maintenance. In E. Soloway S. Iyengar (Eds.), Empirical studies of programmers (pp. 80-98). Norwood, NJ: Ablex.
48. Loomis, M. E. S., Shah, A. V., Rumbaugh, J. E. (1987). An object modeling technique for conceptual design. Proceedings of the European Conference on Object-Oriented Programming (pp. 192-202). Berlin: Springer-Verlag.
49. Mack, R. L. (1984). Understanding text-editing: Evidence from predictions and desciptions given by computer-naive people (IBM Research Rep. No. RC 10333). Yorktown Heights, NY: IBM T.J. Watson Research Center.
50. Mason, R. E. A., Carey, T. T. (1983). Prototyping interactive information systems. Communications of the ACM, 26, 347-354.
51. Mayer, R. E. (1976). Some conditions of meaningful learning for computer programming: Advance organizers and subject control of frame order. Journal of Educational Psychology, 67, 725-734.
52. Meyer, B. (1987). Reusability: The case for object-oriented design. IEEE Software, 4, 50-64.
53. Miller, G. A. (1956). The magical number seven, plus or minus two: Some limits on our capacity for processing information. Psychological Review, 63, 81-97.
54. Moran, T. P. (1981). The command language grammar: A representation for the user interface of interactive computer systems. International Journal of Man-Machine Studies, 15, 3-50.
55. Murata, M., Kusumoto, K. (1989). Daemon: Another way of invoking methods. Journal of Object-Oriented Programming, 2, 8-12.
56. Myers, G. J. (1976). Software reliability: Principles and practices. New York: Wiley.
57. Nielsen, J., Mack, R. L., Bergendorff, K. H., Grischkowsky, N. L. (1986). Integrated software usage in the professional work environment: Evidence from questionnaires and interviews. Proceedings of the CHI ′86 Conference on Human Factors in Computing Systems, 162-167. New York: ACM.
58. Norman, D. A. (1986). Cognitive engineering. In D. A. Norman S. W. Draper (Eds.), User centered system design (pp. 31-62). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
59. Papert, S. (1980). Mindstorms. New York: Basic Books.
60. Parnas, D. L. (1972). On the criteria to be used for decomposing systems into modules. Communications of the ACM, 25, 1053-1058.
61. Pascoe, G. A. (1986). Elements of object-oriented programming. Byte, 11, 139-144.
62. Payne, S. J., Green, T. R. G. (1986). Task action grammars: A model of the mental representation of task languages. Human-Computer Interaction, 2, 93-133.
63. Pennington, N. (1987). Comprehension strategies in programming. In G. M. Olson, S. Shephard, E. Soloway (Eds.), Empirical studies of programmers: Second workshop (pp. 100-113). Norwood, NJ: Ablex.
64. Pomberger, G. (1984). Software engineering and Modula-2. Englewood Cliffs, NJ: Prentice-Hall.
65. Pugh, J. R., Lalonde, W. R., Thomas, D. A. (1987). introducing object-oriented programming into the computer science curriculum. SIGCSE Bulletin, 19, 98-102.
66. Rentsch, T. (1982). Object oriented programming. ACM Sigplan Notices, 17, 51-57.
67. Rosch, E. (1978). Principles of categorization. In E. Rosch B. B. Lloyd (Eds), Cognition and categorization (pp. 24-48). Hillsdale, NJ: Lawrence Erlbaum Associates, Inc.
68. Rosson, M. B. (1984). The role of experience in editing. In B. Shackel (Ed.), Human-computer interaction —INTERACT 84 (pp. 45-50). Amsterdam: Elsevier.
69. Rosson, M. B., Carroll, J. M. (1990). Climbing the Smalltalk mountain. SIGCHI Bulletin, 21, 76-79.
70. Rosson, M. B., Carroll, J. M., Bellamy, R. K. E. (1990). Smalltalk scaffolding: A case study of minimalist instruction. Proceedings of the CHI ′90 Conference on Human Factors in Computing Systems, 423-430. New York: ACM.
71. Rosson, M. B., Gold, E. (1989). Problem-solution mapping in object-oriented design. Proceedings of OOPSLA ′87 (pp. 7-10). New York: ACM.
72. Rosson, M. B., Maass, S., Kellogg, W. A. (1988). The designer as user: Building requirements for design tools from design practice. Communications of the ACM, 31, 1288-1298.
73. Rumbaugh, J. (1987). Relations as semantic constructs in an object-oriented language. In N. Meyrowitz (Ed.), Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 466-481). New York: ACM.
74. Sandberg, D. (1986). An alternative to subclassing. In N. Meyrowitz (Ed.), Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 424-428). New York: ACM.
75. Sharratt, B. D. (1987). Top-down interactive systems design: Some lessons learnt from using command language grammar. In B. Shackel (Ed.), Human-computer interaction-INTERACT ′87 (pp. 395-402). Amsterdam: Elsevier.
76. Sheil, B. (1981). The psychological study of programming. ACM Computing Surveys, 13(1), 101-120.
77. Shneiderman, B. (1983). Direct manipulation: A step beyond programming languages. IEEE Computer, 16, 57-69.
78. Simon, H. A. (1973). The structure of ill-structured problems. Artificial Intelligence, 4, 181-201.
79. Slusky, L. (1987). Integrating software modelling and prototyping tools. Information Software Technology, 29, 379-387.
80. Snyder, A. (1986). Encapsulation and inheritance in object-oriented programming languages. In N. Meyrowitz (Ed.), Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 38-45). New York: ACM.
81. Stefik, M., Bobrow, D. G. (1986). Object-oriented programming: Themes and variations. AI Magazine, 6, 40-62.
82. Stroustrup, B. (1986). The C+ + programming language. Reading, MA: Addison-Wesley.
83. Tesler, L. (1986). Programming experiences. Byte, 77(8), 195-206.
84. Tsichritzis, D., Fiume, E., Gibbs, S., Nierstrasz, O. (1987). KNOs: Knowledge acquisition, dissemination, and manipulation objects. ACM Transactions on Office Information Systems, 5, 96-112.
85. Ungar, D., Smith, R. B. (1987). Self: The power of simplicity. In N. Meyrowitz (Ed.), Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 227-242). New York: ACM.
86. Verrijn-Stuart, A. A., Anzenhofer, K. (1988). Information systems user-designer communication problems. Information Management, 14, 133-142.
87. Vessey, I., Weber, R. (1983). Some factors affecting program repair maintenance: An empirical study. Communications of the ACM, 26, 128-134.
88. Wegner, P. (1980). Programming with Ada. Englewood Cliffs, NJ: Prentice-Hall.
89. Wegner, P. (1987). Dimensions of object-based language design. In N. Meyrowitz (Ed.), Object-Oriented Programming Systems, Languages and Applications (OOPSLA) Conference Proceedings (pp. 168-182). New York: ACM.