0707.321 Principles of Software Engineering

Instructor: Stewart M. Clamen

Office:

Computer Science Department, Robinson Hall, 3rd Floor

Phone:

(856) 256-4500 x3884

URLs:

http://elvis.rowan.edu/~clamen/
http://elvis.rowan.edu/~clamen/classes/SE/

Office Hours:

Mon	14:00-15:00; 18:00-18:30
Wed	14:00-15:00; 18:00-18:30
Fri	11:00-12:00

Other times by appointment

Section Times

Section 1:	M		18:30-21:00		Rob 201A
Section 2:	MWF		10:00-10:50		Rob 101A

Important Dates

Tuesday, January 22

First day of classes

Monday, January 28

Last day to add/drop

Monday, March 11

Last day to withdraw from class with signature of instructor

Monday, March 18 - Friday, March 22

Spring Break

Friday, March 29

Good Friday (no classes)

Tuesday, May 7 - Monday, May 13

Finals Week

Catalog Description

0707.321  3 s.h.
Principles of Software Engineering
(Prerequisite: 0704.222 or 0909.242, 1506.202, 1702.360)

This course is an introduction to the discipline of Software Engineering. Students will explore the major phases of the Software Lifecycle, including analysis, specification, design, implementation and testing. Techniques for creating documentation and using software development tools will be presented. Students will gain experience in these areas by working in teams on mini-projects.

Prerequisites

Students will be assumed to be able to write programs in C++ using classes. Actual programming will not start for a few weeks, so there is time to catch up, if necessary. If this is a problem, come see me.

Grading

Homework & Quizzes	20%
Group Projects	30%	(three or four)
Midterm exams	30%	(best two of three)
Final	20%
Class Participation	tbd

Ground Rules

1. There will be two midterm exams in class, and one included along with the final. The worst of your midterm grades will be dropped.
2. If a student cannot make a scheduled exam, they must notify me beforehand.
3. Make-up exams will likely be more difficult.
4. Attendance in class in strongly encouraged. While I will try to make as much available on the Web as possible, you are responsible for everything said in class. Students are responsible for tracking when exams are scheduled and when assignments are due.
5. Students are responsible for material presented in class and/or assigned as required readings. Optional readings might also be suggested from time to time.
6. Students will be assumed to be checking their students.rowan.edu email at least every other weekday. Homework assignments are likely to be announced — and emergency announcements made — via email. This is of particular importance for students in the night-time section. If checking your students.rowan.edu emailbox is inconvenient for you, configure it to forward to a convenient emailbox.
7. Students who have been attending class regularly and have been making a serious effort are welcome to see me for additional help during office hours.
8. While it is alright to seek help on assignments from others, copying or plagiarizing assignments (or being an accomplice to it) will not tolerated. This rule applies at the student level for homework assignments, and at the team level for group projects. If you do not understand the difference between plagiarism and permissable help, please ask me for elaboration.
9. Homework assignments will be due one week after they have been assigned. Completed homeworks submitted late will be penalized 5% each weekday, and will not be accepted after one week.
10. Group projects will be due 1-2 weeks after they have been assigned. Projects submitted late will be penalized 5% the first day, and 2% each additional weekday, up to two weeks. Group assignments can only be submitted more than one day late by prior (at least one day before due date) arrangement.
11. Students may withdraw from the class after March 11 only in cases of extreme emergency (e.g., prolonged illness) or other circumstances beyond their control.

Group Assignments

Group project work represents a considerable portion of the curriculum, and students who do not submit their projects should not expect to pass this course. If absolutely necessary, students will be permitted to work on a project alone ("team of one"), but work in teams is strongly encouraged. Team will make a single submission, and receive a common grade. For this reason, it is highly recommended that everyone in the team look over the work before it is submitted. Teams will be assigned and will be shuffled during the semester.

Text Books

Sommerville, Ian. Software Engineering. 6th edition

Required.

Brooks, Frederick P., Jr. The Mythical Man-Month. 20th Anniversary Edition

Optional. The must-read book about software systems development in the real world. (OK, IBM.)

What to Expect

Some specifics:

• Homework assignments and projects based on each of the major phases of the Software Lifecycle (requirements analysis, specification, design, implementation, testing) and each of the deliverable components of software (code, user documentation, API documentation, etc.)
• The possibility of a group presentation in class
• Two in-class (50min) exams, plus one of similar length included with the final (during finals week)
• Some surprises (Software Engineering is like that!)