CS 4800 Software Engineering Fall 2001 Time: MWF 1:25 PM to 2:23 PM Room: P-159 Instructor: Edward L. Lamie Office: P 284 Email: [email protected]: 667-3183 Class web site: http://www.cs.csustan.edu/~lamie/cs4800/main.htmOffice hours: Mon & Wed 11:15 AM to 12:15 PM, Tue 9:30 AM to 12:30 PM Textbook: Classical and Object-Oriented Software Engineering, 5th Edition, by Stephen Schach, McGraw-Hill Publishing Company, 2001, ISBN 0-07-239559-1 Text web site: http://www.mhhe.com/engcs/compsci/schach5/Prerequisites: CS 3050 File Processing and CS 3100 Data Structures Course Description We will emphasize large software product development in this course. We will study and utilize techniques that have been found to be useful in the management of such projects. For most of the semester, you will be working in teams on a project chosen by your team and with the agreement of your instructor. Class time will be used at the beginning of the semester for lecture and organization of the project, but will soon become a time for team meetings and progress reports with the instructor. We will use C++ as our primary software engineering tool to aid in the analysis, design, and implementation of the software project. Grading the Project Most of your final grade (i.e., 80%) will be based on the work you do on your project. Your work will be judged on the basis of successful utilization of methodologies, correctness of code and documentation, and correctness and readability of the documentation. The grade will be computed as follows. 10% Individual Written/Oral Assignments You will be assigned end-of-chapter problems from the textbook. Your task is to prepare brief, written (typed, double-spaced) solutions to these problems and to orally present your solutions to the class. Make certain that you include the date, the textbook page number, the problem number, and a restatement of the problem itself in your written solution. Consult the class web site for a sample. Page 1 of 330% Weekly Progress Reports Each team will submit a written project proposal and implementation schedule at the beginning of the semester. During the course of the semester, written progress reports will be presented to the instructor. Each report must be submitted on Wednesday for the preceding week. Each team member is expected to attend and to participate in the scheduled joint team meetings (see page 3), and discuss the team progress. Intermediate documents such as high-level and detailed designs and preliminary versions of the user documentation should be submitted during the semester, as part of the weekly progress reports. These items will collectively account for 30% of your final grade. There are eight (8) reports due; the first is due on October 17, the last is due on December 5. These reports may be submitted by email or in writing. 15% Final Project Presentation Each team member will equally contribute to a public demonstration of the team project during the last week of classes. Everyone in the class is expected to attend and to participate. The quality of this presentation will account for 15% of your final grade. 15% Final Written Documentation The user and system manuals describing the operation of your software will be graded and used to determine 15% of your final grade. 20% Final Code and Internal Documentation The program structure, code, and internal documentation will form 20% of your final grade. 10% Individual Self and Team Member Assessment Each team member will assess his/her own effort AND the efforts of his/her team members. The results will be averaged with the assessment of the instructor to form 10% of your final grade. Note that the "homework" assignments and this assessment are the only factors of the grading formula that will vary by individuals on each team. Thus, members of successful teams will tend to receive good grades, while the converse will hold for unsuccessful teams. This corresponds to the reward system, for better or worse, in the "real world." N.B.: To pass this course, each team must turn in a project, user documentation, and deliver a public presentation. Failure to complete any of these components will result in an automatic failing grade for each of the team members. The only exception to this rule is when a team member effectively stops contributing to the team. However, the instructor must be notified of such a problem at an early date. Page 2 of 3Attendance: Attendance in class and at team meetings does not automatically enter the grading formula. However, habitual absence will almost certainly affect several of the components listed above, including the Individual Self and Team Member Assessment category and the overall success of your project. Tentative Schedule September 10 – October 15 Individual Written/Oral Assignments September 14 and 28 No formal class on these days; prepare for project discussion and assignments September 19 Discussion of project scope, final team assignments October 10 Feasibility Report due; this must include Name of team leader, names and responsibilities of team members Goals Functions to be implemented Functions NOT to be implemented Hooks for later expansion Schedule--List major milestones with dates Design completion User documentation drafts Completion of partial systems Coding completion Testing completion Documentation completion October 17 - December 5 Each team is expected to meet during the regularly scheduled class times. Progress reports will be presented at joint team meetings in the classroom each Wednesday. December 10 Project demonstrations today. December 17 Documented projects due in instructor's office. Page 3 of