Requiring CS1 students to write requirements specifications: a rationale, implementation suggestions, and a case study

ABSTRACT

This paper offers arguments supporting the concept of requiring written requirements specifications for all programming assignments in the first Computer Science course. The term “requirements specifications” is used here to refer to a description of the functional interaction of a single computer program with its environment and the non-functional constraints placed on that interaction. The principle thrust of the arguments is that students are best served if they are introduced to program design only as an activity which naturally follows requirements specification. This concept must be reinforced in all classroom examples and by practical student exercises. By requiring the students to create requirements specifications, the instructor encourages them to view the software development effort, from the beginning, as the analysis and solution of a problem rather than as the generation of a computer program. They are similarly encouraged to realize that the valuable end product of the effort is not just a program, but a thorough description of the problem and solution. Guidelines for incorporating the concept into existing CS1 courses are given. They are reinforced by a description of how this has been done in a specific course.

REFERENCES

• AY83: William E. Ayen , Sam Grier, A new environment for teaching introductory computer science, ACM SIGCSE Bulletin, v.15 n.1, p.258-264, February 1983
• BE81: Ali Behforooz , Onkar P. Sharma, A one-year introductory course for computer science undergraduate program, ACM SIGCSE Bulletin, v.13 n.1, p.46-49, February 1981
• BE84: Ali Behforooz, A foundation course in computer science, ACM SIGCSE Bulletin, v.16 n.1, p.159-163, February 1984
• DA87: Dale, N. and Weems, C. Pascal. D. C. Heath and Company, 1987.
• EN83: Eileen B. Entin, Teaching human-computer interaction in introductory courses, Proceedings of the fourteenth SIGCSE technical symposium on Computer science education, p.51-56, February 17-18, 1983, Orlando, Florida, United States
• FO82: Gary Ford, A software engineering approach to first year computer science courses, Proceedings of the thirteenth SIGCSE technical symposium on Computer science education, p.8-12, February 11-12, 1982, Indianapolis, Indiana, United States
• FR79: Freeman, P. "A Perspective on Requirements Analysis and Specification," in Structured Software Development, Infotech International, Maidenhead England, 1979.
• GR85: Neill Graham, Introduction to computer science (3rd ed.), West Publishing Co., St. Paul, MN, 1985
• GA82: Philippe Gabrini, Integration of design and programming methodology into beginning computer science courses, ACM SIGCSE Bulletin, v.14 n.1, p.85-87, February 1982
• HE86: Peter B. Henderson, Anatomy of an introductory computer science course, ACM SIGCSE Bulletin, v.18 n.1, p.257-264, February 1986
• HY79: Daniel C. Hyde , Ben D. Gay , Donald Utter, Jr., The integration of a Problem Solving Process in the first course, Proceedings of the tenth SIGCSE technical symposium on Computer science education, p.54-59, January 1979
• KO84: Elliot B. Koffman , Philip L. Miller , Caroline E. Wardle, Recommended curriculum for CS1, 1984, Communications of the ACM, v.27 n.10, p.998-1001, Oct 1984 [doi>10.1145/358274.358279]
• LE75: Ledgard, H. F. Programming Proverbs, Hayden, Rochelle Park, N.J. 1975.
• MU79: G. P. Mullery, CORE - a method for controlled requirement specification, Proceedings of the 4th international conference on Software engineering, p.126-135, September 17-19, 1979, Munich, Germany
• RA78: Ramamoorthy, C. V. and So, H. H. "Software Requirements and Specifications: Status and Perspectives," Tutorial:Software Method,_, Ramamoorthy, C. V. and Yeh, R. T., eds., IEEE Computer Society, 1978.
• RI81: David D. Riley, Teaching problem solving in an introductory computer science class, ACM SIGCSE Bulletin, v.13 n.1, p.244-251, February 1981
• RO85: Roman, G. C. "A Taxonomy of Current Issues in Requirements Engineering," Computer.. IEEE Computer Society, April, 1985.
• RS77: Ross, D. T. Structured Analysis for Requirements Definition," ..IEEt~ Trans. Sfw. Eng., January, it977.
• SC78: G. Michael Schneider, The introductory programming course in computer science: ten principles, ACM SIGCSE Bulletin, v.10 n.1, February 1978
• TA85: Wing C. Tam, A multilevel approach to undergraduate software engineering education, ACM SIGCSE Bulletin, v.17 n.1, p.332-334, Mar. 1985
• YE82: Yeh, R. T. "Requirements Analysis---A Management Perspective," Proc~ COMPSAC '82, Nov. 198:2.

INDEX TERMS

Primary Classification:
  K. Computing Milieux
  K.3 COMPUTERS AND EDUCATION
      K.3.2 Computer and Information Science Education
          Subjects: Computer science education

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
        D.2.10 Design**
            Subjects: Methodologies**

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software development

General Terms:
Design, Human Factors, Management