Problem-solution mapping in object-oriented design

Authors:
M. B. Rosson;E. Gold
Affiliations:
IBM T.J.Watson Research Center, P.O.Box 704, Yorktown Heights, NY;IBM T.J.Watson Research Center, P.O.Box 704, Yorktown Heights, NY
Venue:
OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Year:
1989

Citing 5
Cited 7

Smalltalk-80: the language and its implementation

Smalltalk-80: the language and its implementation
The Role of Domain Expenence in Software Design

IEEE Transactions on Software Engineering - Special issue on artificial intelligence and software engineering
Object-oriented development

IEEE Transactions on Software Engineering
Knowledge representations as the basis for requirements specifications

Readings in artificial intelligence and software engineering
Smalltalk and exploratory programming

ACM SIGPLAN Notices

When objects collide experiences with reusing multiple class hierarchies

OOPSLA/ECOOP '90 Proceedings of the European conference on object-oriented programming on Object-oriented programming systems, languages, and applications
Internal representation and rule development in object-oriented design

ACM Transactions on Computer-Human Interaction (TOCHI)
Identifying the difficulties of object-oriented development

Journal of Systems and Software
Scenario-based design

The human-computer interaction handbook
Exploring the difficulties of learning object-oriented techniques

Journal of Management Information Systems - Special section: Strategic and competitive information systems
The cognitive consequences of object-oriented design

Human-Computer Interaction
Cognitive activities and levels of abstraction in procedural and object-oriented design

Human-Computer Interaction

Quantified Score

Hi-index	0.00

Visualization

Abstract

Six expert Smalltalk programmers and three expert procedural programmers were observed as they worked on a gourmet shopping design problem; they were asked to think aloud about what was going through their minds as they worked. These verbal protocols were recorded and examined for ways in which the programmers' understanding of the problem domain affected the design process; most of our examples are from the three Smalltalk programmers who focussed most on the mapping from problem to solution. We characterize the problem entities that did appear as solution objects, the active nature of the mapping process, and ways in which the resultant objects went beyond their problem analogs.