• Norman E. Gibbs
  • Richard E. Fairley


Univer DODCI 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    Aho, A.V., Kernighan, B.W. and Weinberger, P.J. Awk - A Pattern Scanning and Processing Language: Programmer’s Manual. Computing Science Technological Report 118, AT&T Bell Laboratories, June 1985. 36 pp.Google Scholar
  2. [2]
    Ardis, M., Bouhana, J., Fairley, R., Gerhart, S., Martin, N. and McKeeman, W., Core Course Documentation, Master’s Degree Program in Software Engineering. Technical Report TR-85–17, Wang Institute of Graduate Studies, 1985.Google Scholar
  3. [3]
    Baker, F.T. Chief Programmer Team. IBM Systems Journal, IBM, 1972.Google Scholar
  4. [4]
    Balkovich, E., Lerman, S. and Parmelee, R.P. “Computing in Higher Education: The Athena Experience.” ACM/IEEE-CS Joint Special Issue, Volume 18, Number 11, November 1985.Google Scholar
  5. [5]
    Balzer, R. “The Role of Logic and Al in the Software Enterprise.” IEEE Software Engineering, pp. 394,1985.Google Scholar
  6. [6]
    Barbacci, M., Habermann, A.N. and Shaw M. “The Software Engineering Institute: Bridging Practice and Potential.” IEEE Software, Volume 2, Number 6, November 1985.Google Scholar
  7. [7]
    Basili, Turner. “Iterative Enhancement.” IEEE Transactions on Software Engineering, Volume 1, Number 4, pp. 390–396, December 1975.Google Scholar
  8. [8]
    Beizer, B. Software System Test and Quality Assurance. Van Nostrand Reinhold Co., 1984.Google Scholar
  9. [9]
    Ben-David, A., Ben-Porath, M., Loeb, J. and Rich, M. “An Industrial Software Engineering Retraining Course: Development Considerations and Lessons Learned.” IEEE Transactions on Software Engineering, Volume SE-10, Number 1, pp. 748–755, November 1984.CrossRefGoogle Scholar
  10. [10]
    Bentley, J.L. Programming Pearls. Addison-Wesley, 1986.Google Scholar
  11. [11]
    Boehm, B. Software Engineering. Technical Report TRW- SS-76–08, TRW Systems, October 1976.Google Scholar
  12. [12]
    Boehm, B. Software Engineering Economics. Prentice-Hall. Inc., 1981.MATHGoogle Scholar
  13. [13]
    Boehm, B. “Software Technology in the 1990’s: Using an Evolutionary Paradigm.” IEEE Computer, Volume 16, Number 11, pp. 30–37, November 1983.Google Scholar
  14. [14]
    Boehm, B. “Prototyping vs. Specifying: A Multi-project Experiment.” Proceedings of the 7th International Conference on Software Engineering, pp. 473–484. IEEE, March 1984.Google Scholar
  15. [15]
    Boehm, B.W. Notes on Requirement Analysis and Design. Data Processing Management Association Seminar.Google Scholar
  16. [16]
    Booch, Grady. Software Engineering with Ada. Benjamin/Cummings Pub. Co., 1983.MATHGoogle Scholar
  17. [17]
    Bristol Polytech. System Analysis Course. Bristol Polytech School Catalog.Google Scholar
  18. [18]
    Brooks, F.The Mythical Man-Month. Addison-Wesley, 1975.Google Scholar
  19. [19]
    Brooks, R. E. “Using a Behavioral Theory of Program Comprehension in Software Engineering.” Proceedings of the 3rd International Conference on Software Engieering, pp. 196–201. IEEE Computer Society, May 1978.Google Scholar
  20. [20]
    Brooks, R.E. “Studying Programmer Behavior Experimentally: the Problems of Proper Methodology.” Communications of the ACM, Volume 23, pp. 207–213, April 1980.CrossRefGoogle Scholar
  21. [21]
    Busenberg, S.N. and Tarn, W.C. “An Academic Program Providing Realistic Training in Software Engineering.” Communications of the ACM, Volume 22, Number 6, June 1979. Harvey Mudd College.Google Scholar
  22. [22]
    Cain, J.T., Langdon, G.G., Varanasi, M.R. Model Program in Computer Science and Engineering. Technical Report 4, IEEE Computer Society, April 1983.Google Scholar
  23. [23]
    Cameron, J.R. JSP & JSD: The Jackson Approach to Software Development. 1983.Google Scholar
  24. [24]
    Denning P.J. “A Discipline in Crisis.” Communications of the ACM, Volume 24, Number 6, pp. 370–374, June 1981.CrossRefGoogle Scholar
  25. [25]
    DeRemer, Frand and Krön, Hans H. “Programming-in-the-Large versus Programming-in-the-Smail.” IEEE Transactions on Software Engineering, Volume 2, Number 2, pp. 80–86, June 1976.CrossRefGoogle Scholar
  26. SE of Computer. The DoD STARS Program. Vol. 16, #11.Google Scholar
  27. [27]
    Doherty, Robert E. The Development of Professional Education. Carnegie Press, Carnegie-Mellon University, 1950.Google Scholar
  28. [28]
    Fairley, R. “Toward Model Curricula in Software Engineering.” SIGCSE Bulletin, Volume 10, Number 3, pp. 77–79, August 1978.CrossRefGoogle Scholar
  29. [29]
    Fairley, Richard. Software Engineering Concepts. McGraw-Hill, Inc., 1985.Google Scholar
  30. [30]
    Fairley, R.E. The Role of Academe in Software Engineering Education. Technical Report TR-85–19, Wang Institute of Graduate Studies, October 1985.Google Scholar
  31. [31]
    Feldman, S.I. “Make - A Program for Maintaining Computer Programs.” Software - Practice & Experience, Volume 9, Number 3, March 1975.Google Scholar
  32. [32]
    [31]Feldman, J.A. and Sutherlin, W.R. “Rejuvenating Experimental Computer Science.” Communications of the ACM, Volume 22, Number 9, pp. 497–502, September 1979.CrossRefGoogle Scholar
  33. [33]
    Finniston, Montague Sir. Engineering, Our Future.Report of the Committee of Enquiry into the Engineering Profession Command Paper 7794, HMSO, 1980.Google Scholar
  34. [34]
    [33]Fjeldstad, R.K. and Hamlen, W.T. Application Program Main- tenance Study: Report to our Respondents. Technical Report, Proceedings of Guide 48,1979.Google Scholar
  35. [35]
    Freedman, D.P. and Weinberg, G.M. Handbook of Walkthrough, Inspections, and Technical Reviews.Little-Brown, 1982.Google Scholar
  36. [36]
    Freeman, Peter and Newell, Allen. “A Model for Functional Reasoning in Design.” Proceedings of the 2nd International Joint Conference on Artificial Intelligence, pp. 621 -633. 1971.Google Scholar
  37. [37]
    Freeman, Peter. “Training Software Designers: Lessons from a Development Project.” Proceedings of the International Conference on National Planning for Informatics, pp. 232–243. North Holland, 1975.Google Scholar
  38. [38]
    Freeman, Peter. “Realism, Style, and Design: Packing It Into a Constrained Course.” Proceedings of the ACM Symposium on Computer Science Education, pp. 150–157. SIGCSE Bulletin 8,1, ACM, 1976.CrossRefGoogle Scholar
  39. [39]
    Freeman, Peter. “The Central Role of Design in Software Engineering.” Freeman, Peter and Wasserman, Anthony I. (editors), Interface Workshop on Software Engineering Education, pp. 116–119. Springer-Verlag, Irvine, CA. July 1976.Google Scholar
  40. [40]
    Freeman, Peter, Wasserman, A.I. and Fairley, Richardb E. “Essential Elements of Software Engineering Education.” Proceedings of the 2nd International Conference on Software Engineering, pp. 116–122. 1976.Google Scholar
  41. [41]
    Freeman, Peter and Wasserman, A.I. “A Proposed Curriculum for Software Engineering Education.” Proceedings of the 3rd International Conference on Software Engineering, pp. 52–62. 1978.Google Scholar
  42. [42]
    Freeman, Peter. “The Central Role of Design in Software Engineering.” Software Engineering: Research Directions. Academic Press, 1980, pages 121–132.Google Scholar
  43. [43]
    Freeman, H. and Lewis, P. (editors). The Central Role of Design in Software Engineering: Implications for Research. Academic Press, 1980.Google Scholar
  44. [44]
    Freeman, Peter. “Fundamentals of Design.” Software Design Techniques. IEEE Press, 1983, pages 2–22.Google Scholar
  45. [45]
    Gardner, Howard. The Mind’s New Science: A History of the Cognitive Revolution. Basic Books, 1985.Google Scholar
  46. [46]
    Garlan, D.B. and Miller, P.L. “GNOME: An Introductory Programming Environment Based on a Family of Structure Editors.” Proceedings ACM, SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Enviroments. ACM, April 1984.Google Scholar
  47. [47]
    Gill, T.A. A Workable Approach to Software Engineering Documentation. Technical Report TR-85–22, Wang Institute of Graduate Studies, December 1985.Google Scholar
  48. [48]
    Goldberg, A. and Robsen, A. SMALLTALK-80: The Language and its Implementation. Addison-Wesley, 1983.MATHGoogle Scholar
  49. [49]
    Guttag, J. “Abstract Data Types and the Development of Data Structures.” CACM, Volume 20, Number 6, pp. 369–404,1977.Google Scholar
  50. [50]
    Hester, S.D., Parnas, D.L. and Utter, D.F. “Using Documentation as a Software Design Medium.” Bell System Technical Journal, Volume 60, Number 8, pp. 1941–1977, October 1981.Google Scholar
  51. [51]
    Hoffman, A. “Survey of Software Engineering Courses.” SIGCSE Bulletin, Volume 10, Number 3, pp. 80–83, August 1978.CrossRefGoogle Scholar
  52. [52]
    Hopper, G.M., Admiral, USNR. “David and Goliath.” DODCI Selected Computer Articles, 1983.Google Scholar
  53. [53]
    Horning, J.J. and Wortman, D.B. “Software Hut: A Computer Program Engineering Project in the Form of a Game.” IEEE Transactions on Software Engineering, Volume SE-3, Number 4, pp. 325–330, July 1977.Google Scholar
  54. [54]
    Subcommittee on Software Engineering. Draft Report on MSE-80: A Graduate Program In Software Engineering. Technical Report, IEEE Computer Society Education Committee, May 1980.Google Scholar
  55. [55]
    Jackson, M. System Development. Prentice-Hall, 1983.MATHGoogle Scholar
  56. [56]
    Jensen, R., Tonies, C. and Fletcher, W. “A Proposed 4-Year Software Engineering Curriculum.” SIGCSE Bulletin, Volume 10, Number 3, pp. 84–92, August 1978.CrossRefGoogle Scholar
  57. [57]
    Jensen, R. and Tonies, C. Software Engineering. Prentice-Hall, Inc., 1979.Google Scholar
  58. [58]
    Kant, E. “A Semester Course in Software Engineering.” ACM SIGSOFT Software Engineering Notes, Volume 6, Number 4, August 1981.Google Scholar
  59. [59]
    Kernighan, B.W. and Plauger, P.J. Software Tools in Pascal. Addison-Wesley, 1981.Google Scholar
  60. [60]
    Knuth, D.E. “The Art of Computer Programming.” Fundamental Algorithms, Volume 1. Addison-Wesley, 1973, pages 1–24. 2nd Edition.Google Scholar
  61. [61]
    Koffman, E.B., Stemple, D. and Wardle, C.E. “Recommended Curriculum for CS2,1984: A Report of the ACM Curriculum Task Force for CS2.” Communications of the ACM, Volume 28, Number 8, August 1985.Google Scholar
  62. [62]
    Leblang, D.B. and Chase, R.P., Jr. “Computer-Aided Software Engineering in a Distributed Workstation Environment.” Proceedings ACM, SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments. ACM, 1984.Google Scholar
  63. [63]
    Lee, K.Y. “Status of Graduate Software Engineering Education.” Proceedings of the 1981 Annual Conference. ACM, Los Angeles, California. 1981.Google Scholar
  64. [64]
    Lee, K.Y. and Frankel, E.C. “Real-Life Software Projects as Software Engineering Laboratory Exercises.”, Volume 8, Number 3, July 1983. Seattle University.Google Scholar
  65. [65]
    Linderman, J.P. “Theory and Practice in the Construction of a Working Sort Routine.” AT&T Laboratories Technical Journal, Volume 63, Number 8, pp. 1827–1843,1984. part 2.Google Scholar
  66. [66]
    Liskov, B. and Zilles, S.N. “Specification Techniques for Data Abstractions.“, Volume SE-1, Number 1, March 1975.Google Scholar
  67. [67]
    Martin, N., Ligget, D. and Kirby, J. The Wang Institute Software Environment. Technical Report TR-85–05, Wang Institute of Graduate Studies, 1985.Google Scholar
  68. [68]
    McGill, J. “The Software Engineering Shortage: A Third Choice.” IEEE Transactions on Software Engineering, Volume SE-10, Number 1, pp. 42–49, January 1984.CrossRefGoogle Scholar
  69. [69]
    Mcllroy, M.D. “Development of a Spelling List.” IEEE Transactions on Communications, Volume COM-30, Number 1, pp. 91–99, January 1982.CrossRefGoogle Scholar
  70. [70]
    Myers, W. “An Assessment of the Competitiveness of the United States Software Industry.” IEEE Computer, Volume 18, Number 3, pp. 81–92, March 1985.Google Scholar
  71. [70]
    NATO Science Committee. Software Engineering. Conference Report. Garmisch, Germany, October 7–11,1968 (January, 1969).Google Scholar
  72. [72]
    Neisser, Ulric. “Chapter 11, A Cognitive Approach to Memory and Thought.” Cognitive Psychology. Meredith Publishing, Co., 1967, pages 279–305.Google Scholar
  73. [73]
    Notkin, D.S. “The Gandalf Project.” The Jornal of Systems & Software, Volume 5, Number 2, May 1985.Google Scholar
  74. [74]
    Osterweil, L.J. “Software Environment Research Directions for the Next Five Years.” IEEE Computer, Volume 14, Number 4, pp. 35–43,1981.Google Scholar
  75. [75]
    Parnas, D.L. “On the Criteria to be Used in Decomposing Systems into Modules.” Communications of the ACM, Volume 15, Number 12, pp. 1053–1058, December 1972.CrossRefGoogle Scholar
  76. [76]
    Parnas, D.L. “Some Software Engineering Principles, from A Technique for Software Module Specification with Examples.” CACM, Volume 15, Number 5, May 1972.Google Scholar
  77. [77]
    Parnas, D.L. and Clements, P.C. “A Rational Design Process: How and Why to Fake it.” Proc. Int. Joint Conf. on Theory and Practice of Software Development, pp. 80–100. Springer-Verlag, March 1985.Google Scholar
  78. [78]
    Paul, F.W., Feucht, D.L., Jr., Teare, B.R., Neuman, D.P. and Tuma, D. “Analysis, Synthesis, and Evaluation - Adventures in Professional Engineering Problem Solving.” Proceedings Fifth Annual Frontiers in Education Conference, pp. 244–251, October 1975. IEEE and Amer. Soc. for Engr. Ed.Google Scholar
  79. [79]
    Perlman, G. Shar, A Program In C. Distributed on net.sources, January, 1985, Citing Gosling version of October 18,1982.Google Scholar
  80. [80]
    Peters, Lawrence. Software Design: Methods and Techniques. Yourdon Press, 1981.MATHGoogle Scholar
  81. [81]
    Pressman, Roger. Software Engineering: A Practitioners Guide. McGraw-Hill, Inc., 1982.Google Scholar
  82. [82]
    Redwine, S.T. and Riddle, W.E. “Software Technology Maturation.” Proceedings 8th International Conference on Software Engineering, pp. 189–200. ACM, London, England. August 1985.Google Scholar
  83. [83]
    Riddle, W.E. and Williams, L.G. Software Environments Workshop Report. Technical Report TR-85–001, Rocky Mountain Institute of Software Engineering, December 1985.Google Scholar
  84. [84]
    Rochkind, M.J. “The Source Code Control System.” IEEE Transactions on Software Engineering, Volume SE-1, Number 4, December 1975.Google Scholar
  85. [85]
    Shaw, M. (editor). The Carnegie-Mellon Curriculum for Undergraduate Computer Science. Springer-Verlag, 1985.Google Scholar
  86. [86]
    Shaw, M. Beyond Programming-in-the-Large: The Next Challenges for Software Engineering. Technical Report SEI-86- TM-6, Software Engineering Institute, Carnegie-Mellon University, May 1986.Google Scholar
  87. [87]
    Sheil, B.A. “The Psychological Study of Programming.” AMC Computing Surveys, Volume 13, Number 1, pp. 101–120, March 1981.CrossRefGoogle Scholar
  88. [88]
    Simon, H.A. Science of the Artificial. MIT Press, 1969.Google Scholar
  89. [89]
    Simon, Herbert A. The Sciences of the Artificial. MIT Press, 1981.Google Scholar
  90. [90]
    Sommerville, I. Software Engineering. Addison-Wesley Pub. Co., 1985.MATHGoogle Scholar
  91. [91]
    Spicer, J.C. A Spiral Appproach to Software Engineering Project Management Education. Technical Report, Wang Institute of Graduate Studies, December 1983.Google Scholar
  92. [92]
    Stucki, L.G. and Peters, L. “A Software Engineering Graudate Curriculum.”Proceedings of the 1978 Annual ACM Conference, pp. 63–67. ACM, 1978.Google Scholar
  93. [93]
    Teitelbaum, R. and Reps T. “The Cornell Program Synthesizer: A Syntax-Directed Programming Environment.” CACM, Volume 24, Number 9, September 1981.Google Scholar
  94. [94]
    Teitelman, W. and Masinter, L. “The Interlisp Programming Environment.” Computer; Volume 14, Number 4, April 1981.Google Scholar
  95. [95]
    Thayer, R.H. and Tozza, J.C. Report on an Investigation to Determine a Set of Evaluation Criteria for Selecting Project Management Productivity Tools. Technical Report, National Bureau of Standards, February 1985. Prepared by Software Management Consultants.Google Scholar
  96. [96]
    Tichy, W.F. “Design, Implementation and Evaluation of a Revision Control System.” Proc. 6th International Conference on Software Engineering, pp. 58–67. IEEE Computer Society, September 1982.Google Scholar
  97. [97]
    Tichy, W. “RCS - A System for Version Control.” Software - Practice & Experience, Volume 15,1985.Google Scholar
  98. [98]
    Traub, J.F. “Quo Vademus: Computer Science in a Decade.” Communications of the ACM, Volume 24, Number 6, pp. 351–369, June 1981.CrossRefGoogle Scholar
  99. [99]
    U.S. Department of Defense. Reference Manual for the Ada Programming Language, MIL 1815a. 1983.Google Scholar
  100. [100]
    Wasserman, A.I. and Freeman, Peter. Software Engineering Education: Needs and Objectives. Springer-Verlag, 1976.Google Scholar
  101. [101]
    Wasserman, A.I. and Freeman, Peter. “Software Engineering Education: Status and Prospects.” Proceedings of the IEEE, Volume 66, Number 8, pp. 886–892, August 1978.CrossRefGoogle Scholar
  102. [102]
    Wegner, P. “Ada Education and Technology Transfer.”Ada Letters, Volume 2, Number 2,1982.Woffinden, Duard. lecture notes for EENG 593 Software Engineering, 1985. Air Force Institute of Technology, WPAFB, OH.Google Scholar
  103. [103]
    Woffinden, Duard. lecture notes for EENG 593 Software Engineering, 1985. Air Force Institute of Technology, WPAFB, OH.Google Scholar
  104. [104]
    Wolf, A.L., Clarke, L.A. and Wiieden, J.C. “Ada-Based Support for Programming-in-the-Large.” IEEE Software, Volume 2, Number 2, pp. 58–77, March 1985.CrossRefGoogle Scholar
  105. [105]
    Woodfield, S.N., Collofello, J.S. and Collofello, P.M. “Some Insights and Experiences in Teaching Team Project C.S.” Communications of the ACM, 1983.Google Scholar
  106. [106]
    Woodward, M.R. and Mander, K.C. “On Software Engineering Education: Experiences with the Software Hut Game.” IEEE Transactions on Software Engineering, Volume SE-25, Number 1, February 1982.Google Scholar
  107. [107]Worth, L. Personnel conversation with Professor Laurie Worth, University of Texas at Austin. December.Google Scholar
  108. [108]
    Zave, P. “Let’s Put More Emphasis on Prescriptive Methods.” Software Engineering Notes. ACM, 1986.Google Scholar
  109. [109]
    Zelkowitz, M.V., Yeh, R., Hamlet, G., Gannon, J.D. and Basili, V.R. The Software Industry: A State of the Art Survey. Technical Report, Department of Computer Science, University of Maryland, 1981.Google Scholar
  110. [110]
    Zelkowitz, M., Yeh, R., Hamlet, R., Gannon, J. and Vasili, V. “Software Engineering Practices in the United States and Japan.” IEEE Computer, June 1984.Google Scholar

Copyright information

© Springer-Verlag New York Inc. 1987

Authors and Affiliations

  • Norman E. Gibbs
    • 1
  • Richard E. Fairley
    • 2
  1. 1.Software Engineering InstituteCarnegie-Mellon UniversityPittsburghUSA
  2. 2.Wang Institute of Graduate StudiesTyngsboroUSA

Personalised recommendations