Advertisement

Computer productivity initiative

  • Kurt J. Maly
  • Dennis E. Ray
  • J. Christian Wild
  • Irwin B. Levinstein
  • Stephan Olariu
  • C. Michael Overstreet
  • Nageswara S. V. Rao
  • Tijen Ireland
  • George Kantsios
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 750)

Abstract

Over the last three decades computer science has evolved into a mature and experimentally oriented discipline with a well defined curriculum. Only recently have we come to realize that as a discipline computer science must reach beyond its own subject area to applications in other disciplines in order to stay relevant. Most computer science curricula teach principles and programming skills in isolation from an application perspective, provide limited laboratory experience, and introduce inadequate integration with non-CS components. The Computer Productivity Initiative, described in this paper, proposes to alleviate these problems by integrating a multi-year project into the curriculum. The project involves courses normally taken in three different years of the curriculum. It includes hardware and software issues and also addresses engineering, business, and other non-CS issues. The initiative uses prototyping and simulations in the development of specifications for an integrated television communication and display computer system. The students apply principles of productivity and make extensive use of leading-edge technologies both in the process of the project development and the product being developed. They hone essential career-oriented skills in the areas of management, formal presentations, and group problem solving. This paper is a report of work in progress. It emphasizes the implementation issues we are facing and the integration of evaluation into our curriculum development. It describes our preparation for the dissemination of a model curriculum when we are able to demonstrate that the approach is adaptable to CS departments across the country.

Keywords

Software Engineering Advisory Board Model Curriculum Senior Level Computer Science Student 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    A report on undergraduate curricula for software engineeing. British Computer Society and Institution of Electrical Engineers, 1989.Google Scholar
  2. 2.
    ACM/IEEE-CS Joint Curriculum Task Force, 1991. Computing Curricula 1991.Google Scholar
  3. 3.
    The Case for Change. Commonwealth of Virginia, Commision on The University of The 21st Century, Richmond, Virginia, 1992.Google Scholar
  4. 4.
    Discipline review of computer studies and information sciences education, 1992.Google Scholar
  5. 5.
    Computer science curriculum. Department of Computer Science, University of Virginia, Charlettsville, Virginia, 1993.Google Scholar
  6. 6.
    P. A. Bailes and E. J. Salzman. A proposal for a bachelor's degree program in software engineering. In N. E. Gibbs, editor, Software Engineering Education; SEI Conference 1989. Springer-Verlag, New York, 1989.Google Scholar
  7. 7.
    B. Bruegge. Teaching an industry-oriented software engineering course. In C. A. Sledge, editor, Software Engineering Education; SEI Conference 1992. Springer-Verlag, New York, 1992. 65–87.Google Scholar
  8. 8.
    E. Epp. An experimental computer science laboratory. SIGCSE Bulletin, 23(1). 1991.Google Scholar
  9. 9.
    J. Foley et al. Report of the NSF Computer Science Education Workshop. SIGCSE Bulletin, 20(3), 1988.Google Scholar
  10. 10.
    P. Denning et al. Computing as a discipline. Communications of the ACM, 1, 1989.Google Scholar
  11. 11.
    R. E. Prather et al. A lecture/laboratory approach to the first course in computing. SIGCSE Bulletin, 10(1), 1978.Google Scholar
  12. 12.
    N. E. Gibbs. Software engineering and computer science: the impending split? Education and Computing, 7:111–117, 1991.Google Scholar
  13. 13.
    M. Kantioudi, J. S. Collofello, K. W. Collier, and S. Medeiros. Teaching an industry-oriented software engineering course. In C. A. Sledge, editor, Software Engineering Education; SEI Conference 1992. Springer-Verlag, New York, 1992. 323–338.Google Scholar
  14. 14.
    W. M. Lively and M. Lease. Undergraduate software engineering laboratory at Texas A & M university. In C. A. Sledge, editor, Software Engineering Education; SEI Conference 1992. Springer-Verlag, New York, 1992. 315–323.Google Scholar
  15. 15.
    A. J. Offutt and R. H. Untch. Integrating research, reuse, and integration into software engineering courses. In C. A. Sledge, editor, Software Engineering Education; SEI Conference 1992. Springer-Verlag, New York, 1992. 88–98.Google Scholar
  16. 16.
    L. J. Olson. A lab approach for introductory programming. In Proceedings of the 14th SIGCSE Symposium on Computer Education, Orlando, Florida, 1983.Google Scholar
  17. 17.
    D. L. Parnas. On the criteria to be used in decomposing systems into modules. Communications of the ACM, 15(2), 1972.Google Scholar
  18. 18.
    D. L. Parnas. Education for computing professionals. IEEE Computer, 23(1):17–22, 1990.Google Scholar
  19. 19.
    J. P. Penny and P. J. Ashton. Laboratory-style teaching of computer science. SIGCSE Bulletin, 22, 1990.Google Scholar
  20. 20.
    D. E. Ray. Course syllabus: CS250-Problem Solving and Programming. Department of Computer Science, Old Dominion University, Norfolk, Virginia, 1988.Google Scholar
  21. 21.
    J. Roberge and C. Suriano. Embedding laboratories in the computer science curriculum. SIGCSE Bulletin, 23(1), 1991.Google Scholar
  22. 22.
    M. Shaw. We can improve the way we teach CS students. Computing Research News, 4(1):2–3, 1992. letter to the editor.Google Scholar
  23. 23.
    J. Turner. private communication. Clemson University, 1993.Google Scholar
  24. 24.
    C. Wild, K. Maly, and L. Liu. Decision-based software development. Software Maintenanace: Research and Practice, 3:17–43, 1991.Google Scholar
  25. 25.
    W. A. Wulf. SE programs won't solve our problems. Computing Research News, 3(5):2, 1991. letter to the editor.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1993

Authors and Affiliations

  • Kurt J. Maly
    • 1
  • Dennis E. Ray
    • 1
  • J. Christian Wild
    • 1
  • Irwin B. Levinstein
    • 1
  • Stephan Olariu
    • 1
  • C. Michael Overstreet
    • 1
  • Nageswara S. V. Rao
    • 2
  • Tijen Ireland
    • 1
  • George Kantsios
    • 1
  1. 1.Department of Computer ScienceOld Dominion UniversityNorfolk
  2. 2.Intelligent Systems Section, Center for Engineering Systems Advanced ResearchOak Ridge National LaboratoryOak Ridge

Personalised recommendations