CS616 Software Engineering II - Spring 2002

CRN 22454, Thur 6:00-9:35pm, Grad Center, Room 204

Instructor: Dr. Charles Tappert Email: ctappert@pace.edu http://www.csis.pace.edu/~ctappert/
Office hours by appointment: Thurs Room 416A before/after class or Goldstein Room 325 PLV
Computer support for classroom x4060 Webopedia

Textbooks: Bookstores
Software Engineering, 5th Edition, Pressman, McGraw-Hill (2001), ISBN 0073655783
The Object Primer, Scott Ambler, Cambridge (2001), ISBN 0521785197
UML Distilled, 2nd Edition, Fowler, Addison-Wesley (2000), ISBN 020165783x

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. This semester we will focus on the object-oriented methodologies for systems development and on reengineering the systems developed the first semester.

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.

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

Team Project Prototype System
Team Project System at Delivery
Team Project Final System

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

Draft of Team Paper
Final Team Paper

A 20-30 minute team topic presentation:

Possible Topics (software developers' issues)
- PHP, Cold Fusion, or ASP (Active Server Pages)
- Java Server
- Java Beans and/or Enterprise JavaBeans
- Java 2 Micro Edition (J2ME)
- Wireless Application Protocol (WAP)
- Bluetooth
- Asynchronous Transfer Mode
- CORBA
- UML
- XML and/or other varieties of XML such as VoiceXML
- Microsoft's DCOM/COM+ (COM=Common Object Model)
- Internet Protocol 6 (IPv6)
- eXtreme Programming (XP)
- Microsoft's Active Server
- Microsoft's .NET
- SOAP
- an IDE that you know real well (e.g. Rational Rose)
PowerPoint slides emailed to instructor for posting on the course website
Presentations are scattered throughout the semester

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%
Midterm Exam	200 points = 20%
Team Project	350 points = 35% (Prototype 100, System at Delivery 100, Final 150)
Team Paper for Publication	150 points = 15% (Draft 50, Final 100)
Team Topic Presentation	100 points = 10%

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