This paper makes an attempt to outline Software Engineering course with particular attention on the administration of the project. Section II describes the type of students taking the course, and a general description of the topics covered in the course. In section III the project itself is discussed with attention focused on the need for a project, what is expected of the students and the administration of the project. Section IV describes how parts of the course have been automated to relieve some of the problems of administration. Finally, the last section of the paper summarizes the impact of this course on the students and their employers.

In the last decade, the field of Computer Science has undergone a revolution.It has started ihe move from a mvsterious art form to a detailed science. The vehicle for this progress has been the rising popularity of the field of Software Engineering. This innovative area of computer science has brought about a number of changes in the way we think of, and work with, the development of software. Due to this renovation, a field that started with little or no design techniques and unstructured, unreliable software has progressed to a point where a plethora of techniques exist to improve the quality of a program design as well as that of the resultant software. The popularity of structured design and coding techniques prove that there is widespread belief that the overall product produced using these ideas is somehow better, and statistics seem to indicate that this belief is true. Until recently, however, there existed no technique for quantitatively showing one program better than its functional equivalent. In the past few years, the use of software quality metrics seems to indicate that such a comnarison is not only possible, but is also valid.The advent of Software Engineering has demanded that most universities offer a Software Engineering course which entails a "Real-World" group project. Students participating in the class design a system using a program design language (PDL). Other students then write code from the design and finally the design team integrates the modules into a working system. For a complete description of the class see [HENS831 and [TOMJ87].

No abstract

No abstract