CS616 Software Eng. II - Spring 2004

CRN 22000, Thur 6:00-9:35pm, Grad Center 428

Instructor: Dr. Charles Tappert    Email: ctappert@pace.edu    Website
Office hours by appointment: Thurs Grad Center 416A before/after class, or Goldstein 325 PLV
Other Info: Computer support for classroom x4060    Webopedia   Conferences of Interest
Graduate Assistant: Prashant Karmarkar    Email: prashant@karmarkar.org

Textbooks (two from last semester, one new):    Bookstores
Software Engineering, Roger Pressman, 5th Ed., McGraw (2001), ISBN 0073655783
The Object Primer, Scott Ambler, Cambridge (2001), ISBN 0521785197
UML Distilled, 3rd Edition, Fowler, Addison-Wesley (2004), ISBN 0321193687

Additional recommended but not required texts:
The CRC Card Book, Bellin and Simone, Addison-Wesley (1997) ISBN 0201895358
The Elements of Java Style, Vermeulen, Cambridge U. Press (2000) ISBN 0521777682

Course Description:
This is the second semester of a two-semester course on software engineering. The goals of the course are to understand what a Computer Information System (CIS) is, the importance of a systematic approach in CIS design, and how to develop a real-world CIS. Last semester we focused on the traditional systems development methodologies and this semester we will focus on the object-oriented ones. This semester you will also reengineer and add functionality to your first semester system and work more closely with your instructor and client.

This course uses an extensive course website to present the course information: course requirements and grading system, projects, current grades, syllabus, student and team information, and links to related websites, to papers in PDF, and to related conferences/exhibits.

Graded Events and Grade Scale

Ten quizzes (each with 20 minute limit) to be taken via Blackboard. The quizzes are designed not only to check that you read the assignments but, more importantly, to increase your capability to quickly process and comprehend IT material.

A midterm exam on all course material up to the midterm, or a midterm project review and prototype demos.

A team project to design, build, and test a real-world computing system for a real client. Checkpoints:

A team paper for publication on your real-world computing system. Checkpoints:

A 30-40 minute team topic presentation that allows us to benefit from our variety of experience, expertise, and interest in various areas of computing. The topics are software developers' issues and are often related to the team projects.

Incompletes: in order to be fair to those students who complete the course in a timely manner, my policy is to reduce the grade of those students taking an incomplete by a letter grade for each semester, or portion thereof, that the incomplete is in effect.

Graded Events: 1000 points total
Event Points and Percent
Quizzes (10 * 20 points) 200 points = 20%
Team Topic Presentation 100 points = 10%
Team Project 500 points = 50%
(Prototype 150, System at Delivery 150, Final 200)
Team Project Paper
for Publication
200 points = 20%
(Draft 100, Final 100)

Grade Scale: 1000 points = 100%
Grade Assigned Score Definition
A  93-100% 930 or more points Dominates the Material
A-  90-93% 900-929 points Masters the Material
B+  87-90% 870-899 points Good Understanding
with Flashes of Stellar Work
B  83-87% 830-869 points Good Understanding
B-  80-83% 800-829 points Aptitude for the Subject
Incomplete/Failure
Less than 80%
Below 800 points Weak for Graduate Work