COSC 301 - Software Engineering
Fall 2010
St. Mary's College of MarylandCourse Syllabus
SH 168
240-895-2197 (SMCM Office)
301-373-3698 (Home)
301-866-4263 (J.F. Taylor Office)
Course Web Site / faculty.smcm.edu/rttracy
Course Prerequisites / COSC 130
Required Text / Pressman, Roger S.
SOFTWARE ENGINEERING, A PRACTITIONER’S APPROACH
(7th Edition)
McGraw-Hill, 2010
ISBN: 9780073375977
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.
1 / August 31 / Introductions, discussion of syllabus, discussion of course schedule, course overview
September 2 / Chapters 1 and 2 / Project Team Name, project team member roles
2 / September 7 / Chapters 4 and 5
September 9 / Chapter 6
Discuss Software Development Plan
3 / September 14 / Chapter 7
Discuss Software Requirements Specification
September 16 / Chapter 8 / Software Development Plan document due
4 / September 21 / SRS Peer Review
September 23 / Chapter 9
Discuss Traceability Matrix / Software Requirements Specification document due
5 / September 28 / Chapter 10
Discuss Software Design Document
September 30 / Chapter 11 / Traceability Matrix due
6 / October 5 / Chapter 12
October 7 / Review for Midterm Exam
Project status review / Software Design Document due
7 / October 12 / No class – reading day
October 14 / Midterm Exam
8 / October 19 / Chapter 14 / Updated SDP due
October 21 / Chapter 15 / Updated SRSdocumentdue
9 / October 26 / Chapter 16
Discuss Software Test Plan / Updated Traceability Matrix due
October 28 / Chapter 17
10 / November 2 / No class – advising day
November 4 / Chapter 18 / Updated SDD due
11 / November 9 / Chapter 22 / Software Test Plan (STP) document due
November 11 / Chapter 24
12 / November 16 / Chapter 23
November 18 / Chapter 25 / Updated STP document due
13 / November 23 / Chapter 26
November 25 / No class
14 / November 30 / Chapter 27 / Delivery list of documentation, media, etc.
December 2 / Chapter 28
15 / December 7 / Chapter 29 / Project presentations, source code due
December 9 / Review for Final Exam
16 / December 16 / Final Exam (7:00 pm – 9:15 pm)
Grading
The final grade for this course will be based on the following criteria:
Homework/In-Class Activities / 20%Project Team Assignments / 25%
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 / A90-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.
1