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 PRACTITIONER’S APPROACH (6th Edition) McGraw-Hill, 2005 ISBN: 0072853182

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	August 30	Introductions, discussion of syllabus, discussion of course schedule, course overview
	September 1	Chapters 1 and 2
2	September 6	Chapters 3 and 4
	September 8	Chapter 5	Project Team Name, project team member roles
3	September 13	Chapter 6
	September 15	Discussion of Software Development Plan SDP Link (see below)
4	September 20	Chapter 7	Software Development Plan
	September 22	Chapter 8
5	September 27	Chapter 9	Updated SDP, Software Requirements Document
	September 29	Chapter 10	Traceability Matrix
6	October 4	Chapter 11	Updated Software Requirements Document
	October 6	Review for Midterm Exam Project status review
7	October 11	No class
	October 13	Midterm Exam
8	October 18	Chapter 12
	October 20	Chapter 13	Software Design Document
9	October 25	Chapter 14
	October 27	Chapter 15
10	November 1	No class
	November 3	Chapter 16	CM Plan and estimates, updated SDD
11	November 8	Chapter 17
	November 10	Chapter 18	QA Plan
12	November 15	Chapter 19	Updated CM Plan
	November 17	Chapter 20	ATP document, updated Traceability Matrix
13	November 22	Chapter 23	Updated QA Plan
	November 24	No class
14	November 29	Chapter 25	Delivery list of documentation, media, etc., Updated ATP document
	December 1	Chapter 27
15	December 6	Chapter 30	Project presentations, source code due
	December 8	Review for Final Exam
16	December 14	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.