CSC 4700 Software Engineering SPRING 2004

SYLLABUS


Meetings
Section 1:
Section 2:
Tues/Thurs
Tues/Thurs

11:30am-12:45pm
1:00pm-2:15pm

Mendel G87
Mendel G87
Instructor Dr. Thomas Way
160A Mendel Science Center

Email:   thomas.way@villanova.edu
IM:       DrTomWay
Phone:  (610) 519-5033
Office hours Tue 5-6pm, Wed 12pm, Thur 10:30-11:30am, and before/after class or by appointment
TA
Programming TAs
Office: Mendel 292
Hours: posted online
Info: From main CS dept web page, follow link to "Student support, Technical support, Programming assistants"
Textbook Software Engineering, Ian Somerville,
Addison-Wesley, Sixth Edition, 2001.
Prerequisite
CSC 1700 Analysis of Algorithms
Web site
http://www.csc.villanova.edu/~tway and follow the link for CSC 4700
Course
description

Management and production of software systems; the software life cycle; software design techniques and methodologies; participation in a team software development project. Course is Writing Intensive.  Student will gain experience in team-based software design and learn some tools & techniques for software development.
Lesson plan
The course follows the textbook outline, although some topics will be covered more in depth and some less (or not at all).  The heart of the course is the design and development of a real software product, carried through from initial design, through prototyping, development and testing, to actual finished product which will be made available online to the rest of the world, through Open Source and the GNU General Public License, as an educational and research tool..
What to expect
This is a different approach to this course, as our goal is twofold:  1) to thoroughly learn the subject of Software Engineering, and 2) to develop and deploy an actual software product.  Software engineering is an inexact science, so expect some surprises, twists and turns along the way during the semester.  Being a contributing member of your team and of our company (i.e., the class) will be crucial to our success.  In the end, we will have learned first hand about the software engineering process, while applying the theory we study in class, to develop a legitimate software product that will be available to the entire world. Note: because software engineering is a collaborative science, attendance is an important part of the course (and your grade).
Grading policy
  50  Rough Design & Project Plan
  50  Requirements specification #1
  50  Requirements specification #2
  50  Prototype #1
  50  Prototype #2
100  Team deliverable (contribution to your team's part of the product)
100  Finished product (team-based grade, scaled based on individual contribution)
150  Design & development tasks (10-15 points each)
100  Midterm exam
150  Final exam
  50  Team participation (attendance, class discussions, contributions to class)
900  Total points (may change slightly during semester)
Final grades
Earning the following percentage of points in the class will guarantee that you earn at least the associated grade.
A
A-
92
90
B+
B
B-
88
84
80
C+
C
C-
78
74
70
D+
D
D-
68
64
60
Makeup
Policy

No missed tests without prior excuse. Each case will be handled separately based on its own merits. Makeup tests might be more difficult than regularly scheduled tests. Each student is responsible for what is covered and assigned in any classes which they miss.
Late Assignment Policy
No assignments will be accepted late without the direct consent of the instructor prior to the due date of the assignment. Penalty points will be determined for each case based on why the assignment is late and how late it is.
Academic Integrity
Although this course will contain a lot of collaborative work, many assignments will be individual, so it is up to the student to maintain the highest standards of acadmic integrity as outlined in the Villanova Univerity policy on Academic Integrity.  Please refamiliarize yourself with the policy.

Last updated: 1/06/04