How software engineering tools organize programmer behavior during the task of data encapsulation

Empirical Software Engineering

Volumn 2, Issue 3, 1997, Pages 221-267

  Bowdidge, Robert W ^a   Griswold, William G ^b  

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

^b UNIVERSITY OF CALIFORNIA   (United States)

Author keywords

Data encapsulation; Empirical study; Restructuring; Software tools

Indexed keywords

COMPUTER PROGRAMMING; COMPUTER SOFTWARE; DATA HANDLING; SOFTWARE PROTOTYPING;

DATA ENCAPSULATION; RESTRUCTURING;

SOFTWARE ENGINEERING;

EID: 0031341346     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1023/A:1009716016693     Document Type: Article

References (42)

1. Belady, L. A., and Lehman, M. M. 1985. Programming system dynamics or the metadynamics of systems in maintenance and growth. Research Report RC3546, IBM, 1971.
2. Reprinted in M. M. Lehman, L. A. Belady, (eds.), Program Evolution: Processes of Software Change, Ch. 5, APIC Studies in Data Processing No. 27. London, Academic Press.
3. Blomberg, J., Giacomi, J., Mosher, A., and Swenton-Wall, P. 1993. Ethnographic field methods and their relation to design. In D. Schuler and A. Namioka, (eds.), Participatory Design: Principles and Practices, chapter 7, 123-155. Lawrence Erlbaum Associates, Hillsdale, New Jersey.
4. Boehm, B. W. 1975. The high cost of software. In E. Horowitz, (ed.), Practical Strategies for Developing Large Software Systems, 3-15. Addison-Wesley, Reading, MA.
5. Bowdidge, R. W., and Griswold, W. G. 1994. Automated support for encapsulating abstract data types. In ACM SIGSOFT '94 Symposium on the Foundations of Software Engineering, 97-110.
6. Bowdidge, R. W. 1995. Supporting the restructuring of data abstractions through manipulation of a program visualization. PhD dissertation, University of California, San Diego, Department of Computer Science & Engineering. Technical Report CS95-457.
7. Brooks, F. P. 1987. No silver bullet: Accidents and essence of software engineering. IEEE Computer 20(4): 10-19.
8. Chi, M. T. H. 1997. Quantifying qualitative analyses of verbal data: a practical guide. To appear in Journal of Learning Sciences.
9. Collofello, J. S., and Bortman, S. 1986. An analysis of the technical information necessary to perform effective software maintenance. In 5th Annual International Phoenix Conference on Computers and Communications, 420-423.
10. Cousin, L., and Collofello, J. S. 1992. A task-based approach to improving the software maintenance process. In Conference on Software Maintenance, 118-126.
11. Curtis, B., Krasner, H., and Iscoe, N. 1988. A field study of the software design process for large systems. Communications of the ACM 31(11): 1268-1287.
12. Dumas, J., and Parsons, P. 1995. Discovering the ways programmers think about new programming environments. Communications of the ACM 38(6): 45-56.
13. Ericsson, K. A., and Simon, H. A. 1993. Protocol Analysis: Verbal Reports as Data, revised edition. MIT Press: Cambridge, MA.
14. Flor, N. V., and Hutchins, E. L. 1991. Analyzing distributed cognition in software teams: A case study of team programming during perfective software maintenance. In J. Koenemann-Belliveau, T. G. Moher, and S. P. Robertson, (eds.), Empirical Studies of Programmers: Fourth Workshop, 36-64. Ablex, Norwood, NJ.
15. Gray, W. D., and Anderson, J. R. 1987. Change episodes in coding: When and how do programmers change their code? In G. M. Olson, S. Sheppard, and E. Soloway, (eds.), Empirical Studies of Programmers: Second Workshop, 185-197. Ablex, Norwood, NJ.
16. Griswold, W. G., and Notkin, D. 1992. Computer-aided vs. manual program restructuring. ACM SIGSOFT Software Engineering Notes 17(1): 33-41.
17. Griswold, W. G., and Notkin, D. 1993. Automated assistance for program restructuring. ACM Transactions on Software Engineering and Methodology 2(3): 228-269.
18. Griswold, W. G. 1991. Program restructuring as an aid to software maintenance. PhD dissertation, University of Washington, Dept. of Computer Science & Engineering, Technical Report No. 91-08-04.
19. Griswold, W. G., Chen, M. I., Bowdidge, R. W., and Morgenthaler, J. D. 1996. Tool support for planning the restructuring of data abstractions in large systems. ACM SIGSOFT '96 Symposium on the Foundations of Software Engineering.
20. Guindon, R. 1990a. Designing the design process: Exploiting opportunistic thoughts. Human-Computer Interaction 5(2): 305-344.
21. Guindon, R. 1990b. Knowledge exploited by experts during software system design. International Journal of Man-Machine Studies 33(3): 279-304.
22. Guindon, R., Krasner, H., and Curtis, B. 1986. Breakdowns and processes during the early activities of software design by professionals. In Empirical Studies of Programmers: First Workshop 65-81.
23. Houde, S., and Sellman, R. 1994. In search of design principles for programming environments. Conference on Human Factors in Computing Systems (CHI '94), 424-430.
24. Johnson, R. E., and Opdyke, W. F. 1993. Refactoring and Aggregation. In Object Technologies for Advanced Software, volume 742 of Lecture Notes in Computer Science, 264-278. First JSSST International Symposium.
25. Lange, B. M., and Moher, T. G. 1989. Some strategies of reuse in an object-oriented programming environment. In Conference on Human Factors of Computing Systems (CHI '89), 69-73.
26. Letovsky, S., and Soloway, E. 1985. Strategies for documenting delocalized plans. In Conference on Software Maintenance, 144-151.
27. Letovsky, S. 1986. Cognitive processes in program comprehension. In First Workshop on Empirical Studies of Programmers, 58-79.
28. Lientz, B., and Swanson, E. 1980. Software Maintenance Management: A Study of the Maintenance of Computer Application Software in 487 Data Processing Organizations. Addison-Wesley: Reading, MA.
29. Miyake, N. 1986. Constructive interaction and the iterative process of understanding. Cognitive Science 10(2): 151-177.
30. Norman, D. A. 1986. Cognitive engineering. In D. A. Norman and S. W. Draper, (eds.), User Centered System Design. Lawrence Erlbaum Associates, Hillsdale, NJ.
31. Norman, D. A. 1989. The Design of Everyday Things. Doubleday: New York.
32. Opdyke, W. F., and Johnson, R. E. 1990. Refactoring: An aid in designing application frameworks and evolving object-oriented systems. In Proceedings of the 1990 Symposium on Object-Oriented Programming Emphasizing Practical Applications, 274-282.
33. Opdyke, W. F. 1992. Refactoring: A program restructuring aid in designing object-oriented applications frameworks. PhD dissertation, University of Illinois at Urbana-Champaign, Dept. of Computer Science, Technical Report No. 1759.
34. Parnas, D. L. 1972. On the criteria to be used in decomposing systems into modules. Communications of the ACM 15(12): 1053-1058.
35. Rosson, M. B., and Carroll, J. M. 1993. Active programming strategies in reuse, ECOOP '93, 7th European Conference on Object-Oriented Programming, 4-20.
36. Sanderson, P. M., and Fisher, C. 1994. Exploratory sequential data analysis - foundations. Human-Computer Interaction 9(3): 251-317.
37. Schneiderman, B., and Carroll, J. M. 1988. Ecological studies of professional programmers. Communications of the ACM 31(11): 1256-1258.
38. Schon, D. A. 1982. The Reflective Practitioner: How Professionals Think in Action. Basic Books: New York.
39. Strauss, A. L. 1987. Qualitative Analysis for Social Scientists. Cambridge University Press: Cambridge.
40. Sutcliffe, A. G., and Maiden, N. A. M. 1992. Analysing the novice analyst: cognitive models in software engineering. International Journal of Man-Machine Studies 36(5): 719-740.
41. Weick, K. E. 1968. Systematic observational methods. In G. Lindzey and E. Aronson, (eds.), The Handbook of Social Psychology, 357-451. Reading, MA: Addison-Wesley.
42. Wildman, D. 1995. Getting the most from paired-user testing. ACM Interactions 2(3): 21-27.