COSC 301 - Software Engineering
Spring 2004
St. Mary's College of Maryland

Instructor Bob Tracy
301-373-3698 (Home), 240-725-7021 (Office)
rttracy@smcm.edu
Course Web Site www.smcm.edu/users/rttracy
Course Prerequisites COSC 130
Required Text Presman, Roger S.
SOFTWARE ENGINEERING, A BEGINNER'S GUIDE (5th Edition)
McGraw-Hill, 2001
ISBN: 0070507902



Course Description
An introduction to the discipline of software engineering. A broad view of the software lifecycle is taken, and emphasis is placed on developing “good” software as opposed to developing software quickly. The principles of software engineering are introduced and their impact on language design and the software development process is examined. The course includes participation in a group project. Each project team is assigned a role in the software engineering process as applied to a large, existing software a artifact. Course requirements include writing assignments and oral presentations.


Course Objectives
This course familiarizes students with the concept of software engineering. Students will learn about the methods and participants of the software engineering process, both theoretical and practical. Students will learn how to develop “good” software as opposed to developing software quickly.


Course Schedule/Important Dates
This course outline is a tentative plan of class activities and lecture content. It may be modified due to unforeseen circumstances. The order in which lectures and activities appear on the schedule will be followed.

Week Date Topic/Assignment Project
1 January 20 Introductions, discussion of syllabus, discussion of course schedule, course overview  
January 22 Chapters 1 - 3  
2 January 27 Class Cancelled  
January 29 Class Cancelled  
3 February 3 Chapter 10 Project Team Name, project team member roles, Keirsey Temperament Rating
February 5 Discussion of Software Development Plan
SDP Link (see below)
 
4 February 10 Chapter 12 Software Development Plan
February 12 Chapters 20-21  
5 February 17 Chapters 19, 24 Updated SDP, Software Requirements Document
February 19 Chapters 13-15 Traceability Matrix
6 February 24 Chapters 16, 22  
February 26 Review for Midterm Exam
Project status review
 
7 March 2 Midterm Exam  
March 4 Chapter 6  
8 March 9 Chapter 9 Software Design Document
March 11 Chapters 4-5  
9 March 16 No Class  
March 18 No Class  
10 March 23 Chapter 8 CM Plan and estimates, updated SDP, updated SDD
March 25 Chapters 17-18  
11 March 30 No Class  
April 1 Chapter 23 QA Plan
12 April 6 Chapter 7  
April 8 Chapter 30 ATP document, updated traceability
13 April 13 Chapter 15  
April 15 Chapter 28  
14 April 20 Chapter 29 Delivery list of documentation, media, etc.
April 22 Chapter 32  
15 April 27 Project presentations  
April 29 Review for Final Exam  
16 May 7 (Fri) Final Exam (7:00-9:15 PM)  
SPD Link: http://www.yoopeedoo.org/upedu/process/artifact/tmpl_cs/webtmpl/PM/upedu_sdp.htm


Grading
The final grade for this course will be based on the following criteria:

Homework/In-Class Activities   15%
Project Team Assignments 30%
Midterm Exam 25%
Final Exam 30%

All tests and assignments will have a possible score of 100 points, and the above percentages will be multiplied by each score and summed to determine the overall course grade. The following grading scale will be used to determine letter grades:

93-100  A
90-92 A-
87-89 B+
83-86 B
80-82 B-
77-79 C+
 
73-76   C
70-72 C-
67-69 D+
63-66 D
60-62 D-
0-59 F

Test and exams will be based upon the course text book, lecture materials, and handouts. Prior to each test or exam, class time will be allocated for question/answer sessions. Make-up tests will be administered only with prior approval by the instructor. All tests, exams, and assignments will be discussed and announced in class as well as the requirements and due dates. Unless prior arrangements have been made with the instructor, assignments will not be accepted after the due dates.


Academic Honesty
Each student is expected to perform his or her own academic work. Plagiarism and other forms of academic dishonesty are considered an extremely serious offense. Each student is personally responsible for understanding the various forms of academic dishonesty as they are explained in the Student Code section of the College's Student Handbook. Ignorance of any requirement for academic honesty will not constitute an excuse from disciplinary proceedings.


Absences
Students are expected to attend class and be on time. Students are responsible for all material covered during each class session. The majority of students will find that class attendance is imperative in order to complete the course work satisfactorily.

Absence from any class session will likely be detrimental to a student's progress and grade due to the technical nature of the course. In legitimate emergency situations, the student should contact the instructor so that the opportunity to make up work that was missed can be granted. Otherwise, the absence will be considered unexcused.