CPT 450 Enterprise Application Development

For the most recent updates to this syllabus see http://www.tech.purdue.edu/cpt/cpt450

This page was last updated on August 20, 2007

This course explores advanced application development techniques in a large enterprise-wide setting. Topics include component development and reuse, distributed object technologies, multi-tier applications, data marshalling, transaction processing, concurrency problems and resolutions, load balancing and tuning, and application installation and deployment issues.

Organization and Schedule Lecture 3 hours, PSO 1 hour, Credit 3 hours

Semester Meeting Type Days Time Location Instructor

Fall 2007 Lecture 1-1 Tue & Thur 4:30 pm - 5:45 pm KNOY B035 Whittinghill

PSO 1-1 Wed 3:30 pm - 4:20 pm KNOY 242 Whittinghill

PSO 2-1 Wed 4:30 pm - 5:20 pm KNOY 242 Whittinghill

Midterm Exam TBA

Final Exam TBA

help sessions scheduled as needed

last day to add 8-24-2006

last day to drop 8-31-2006 Last day to cancel a course assignment without it appearing on record

last day to drop 9-17-2006 Last day to cancel a course assignment without a grade, for course additions, change of level or change of pass/not-pass option

last day to drop 10-24-2006 Last day a course assignment may be cancelled (with passing or failing grade)

Prerequisites

CIT 272 and CIT 295 (was CIT 350). SQL and Object-Oriented Programming Experience.

Information Technology Used In This Course

Java 1.6 SE
J2EE 5
HTML
NetBeans and/or Eclipse
MySql
SQL

Course Instructors

Instructor Office Phone Email

Professor David Whittinghill KNOY 242 765-532-5742 davewhit@purdue.edu

Coordinator Office Phone Email

Professor Kyle Lutes KNOY 235 49-45125 kdlutes@purdue.edu

Required Textbooks, Lab Manuals, and Supplies

No textbooks are required for this course. However, daily reading assignments from various sources (books, web, white papers, periodicals, reference manuals, etc.) will be announced and posted on the course web site.

How Final Grades will be Determined (subject to change with notice)

Assessment Mechanism
Total Points

Quizzes 40

Programming Exercises 500

Midterm Exam 100

Final Exam 200

Total 550

Grading Scale

A 90% and above

B 80% - 89.9%

C 70% - 79.9%

D 60% - 69.9%

F below 60%

Incompletes

An incomplete will only be granted for serious, extenuating circumstances. Written proof of the particulars will be required. Any makeup work must be completed within a period of time not to exceed the time of the absence, beginning immediately after the absence, as discussed with the course instructor. Extended absences must be documented through the Dean of Students Office and will be validated by the instructor. Do not expect to receive an incomplete to cover up failure in this course. Incompletes will not be given for non-mastery of programming assignments or poor attendance without prior instructor approval.

Course Policies

Contacting Course Instructors

1. Students should not contact instructors just before, during, or just after class to discuss personal affairs. Matters of this type should be scheduled via email and discussed during office hours.

2. Students are strongly urged to use email to contact the course instructors.

3. The sender of all email correspondence must be clearly identifiable or it may not be answered. For example, it is recommended you include CPT 450 in the subject line and your full name in the message body. Additionally, email should be written in a professional, courteous, non-offensive manner. Email that contains unprofessional, discourteous, or otherwise offensive language will likely not be answered.

4. Teaching Assistants only have authority to help with assignments and related questions. Personal matters should be directed to the course instructors.

Attendance, Preparation, and Courtesy Expectations and Policies

1. Students are expected to be present, be prepared, and display a positive, professional attitude throughout the semester in every class meeting. All students are also expected to share in classroom meetings by asking relevant questions and offering suggestions and answers to questions. Disruptive, argumentative, and other unprofessional behavior will result in the student being dismissed from the class.

2. If you must miss a class for a valid reason, contact the instructor in advance about the possibility of rescheduling any missed work. You should also have the names of two or three other students in the class that you can contact to get class notes, announcements or assignments if you must miss class.

3. In the event of an extended absence (usually three days or longer), you should contact the Dean of Students Office to report the absence and receive advice on how to proceed. Upon your return to campus, you must promptly contact your instructor to determine if, and how, missed work will be made up.

Add/Drop Expectations and Policies

1. According to CIT educational policy, this course may not be added to any student's academic schedule after the third week of a Fall or Spring semester (or equivalent for a Summer semester) except under very extenuating circumstances to be approved by the Department Head.

2. According to CIT educational policy, no independent study course can be substituted for this course.

3. You may drop this course without a failing grade so long as you do so before the published University deadline for dropping the course. After the initial withdrawal period, you will need your instructor's signature.

Quiz and Exam Policies

1. Make-up quizzes and examinations will only be given under extenuating and unavoidable circumstances. The burden of proof of said circumstances is on the student. All CIT faculty members have e-mail and voice mail, so messages can be left for them at any time.

Homework Policies and Quality Expectations

1. Assignments will generally be posted one week prior to their due date unless otherwise noted by your instructor.

2. Assignments must be turned in using the eSub electronic submission system as posted on the course web site.

3. Assignments can be turned in early, but late homework assignments will not be accepted.

4. All assignments must be prepared in a professional manner. Always check your assignments for correct spelling and grammar. Unprofessional work may not be graded. Points may be subtracted for submitting poorly or improperly organized work, or for not following instructions.

5. To protect your privacy, graded materials will never be passed around the classroom or placed outside of an instructor's office door.

6. Scores and grades will be posted on the course web page.

7. The course instructors reserve the right to lower the grading scale expectations but will never raise the minimum grade requirements.

8. Deadline extensions and extra credit assignments will not be given.

9 Unless otherwise noted, all programming homework assignments that contain compile/syntax errors will automatically receive a score of zero.

Re-Grading Policies

1. Students wishing to appeal any score must return their work to their course instructor via email with a written statement explaining the appeal no later than one week after the original scores were posted.

2. Any work submitted for re-grade (other than misreported material) may be totally re-graded. Do not assume the instructor will only re-grade those portions that the student wishes to be re-graded.

3. According to University regulations, only final course grades can be "appealed." There is a formal College of Technology and University timetable and process for grade appeals. It must be followed exactly! Questions about grade appeals should be directed to the Department of Computer & Information Technology Department Head or the Chair of the College of Technology Grade Appeals Committee.

Academic Dishonesty ("Cheating") Policies

1. The maximum penalty for cheating on any assignment, quiz, or examination in the course is an "F" grade for the course.

2 Is it worth the risk to receive an F in a class after a considerable investment of time/effort or worse yet to be suspended from school for one or more semesters at any time during your academic career? Don't Cheat!

3. You are expected to do your own original work and to acknowledge correctly the work of others. Copies of the original authors' work(s) must be submitted with your assignment. One student doing/taking another's work (in whole or part) or collaborating with other(s) and submitting that work (in whole or part) as his/her individual effort (perhaps with cosmetic changes) constitutes cheating. Using unauthorized crib sheets or copying answers from another source when completing in-class assignments, quizzes, and exams constitutes cheating. Gaining unauthorized access to exams, quizzes, or instructor's keys or any student's answers is cheating.

4 Your instructor recognizes the learning value in exchanging ideas with others and learning from the mistakes and solutions of others; however, this type of unauthorized sharing can result in suspiciously similar work that is not an individual effort. All work that you submit must truly represent your individual effort. You should be aware that it is next to impossible for someone to forget a unique, creative approach once it has been seen/shared/heard. Most of the work in this class requires multiple levels of creativity, so it is not difficult to detect work submitted under suspicious circumstances. The best way to avoid being caught in the middle of a suspicious situation is to not discuss/show/share your work (in whole or part) with/to others.

5 Throughout the semester, your instructor will work through related problems and make assignment solutions available. You are encouraged to use these solutions to improve your understanding of course concepts and to facilitate your completion of course assignments. However, you are not permitted to exchange/give/take/use any other person's work without prior, written permission from your instructor. Failure to abide by this policy is considered cheating. If you experience difficulty in completing course assignments, you are encouraged to seek the assistance of your instructors during scheduled class meetings and scheduled office hours (or to schedule an appointment). Additional assistance will also be made available as needed and can be arranged.

6 Giving another student access to your computer account, or negligently permitting another student to access your computer account constitutes cheating on your part if that other student copies any files that become implicated in a cheating case. Protect your account as if your academic career depends on it!

7. Cheating, or helping another student to cheat, are considered equal cases of academic dishonesty and will be dealt with as noted below.

8 All cases of academic dishonesty are forwarded to the Office of the Dean of Students for record-keeping purposes and consideration of other, appropriate disciplinary action.

Course Outline (subject to change)

Unit

Topic

1 Object-Oriented Programming Review

2 Introduction to the Java Platform

3 Database Connectivity and SQL

4 Software Architectures Overview

5

Multi-User Issues and Solutions

6
Component-Based Development

7

n-Tier Application Development using Web Services

8

The Impedance Mismatch Between Relational Systems and Object-Oriented Programming

Optional Units

9
Application Deployment and Distribution

10
Application Security

11 Application Transaction Processing

Semester	Meeting Type	Days	Time	Location	Instructor
Fall 2007	Lecture 1-1	Tue & Thur	4:30 pm - 5:45 pm	KNOY B035	Whittinghill
	PSO 1-1	Wed	3:30 pm - 4:20 pm	KNOY 242	Whittinghill
	PSO 2-1	Wed	4:30 pm - 5:20 pm	KNOY 242	Whittinghill

	Midterm Exam	TBA
	Final Exam	TBA
	help sessions	scheduled as needed
	last day to add	8-24-2006
	last day to drop	8-31-2006	Last day to cancel a course assignment without it appearing on record
	last day to drop	9-17-2006	Last day to cancel a course assignment without a grade, for course additions, change of level or change of pass/not-pass option
	last day to drop	10-24-2006	Last day a course assignment may be cancelled (with passing or failing grade)

Instructor	Office	Phone	Email
Professor David Whittinghill	KNOY 242	765-532-5742	davewhit@purdue.edu

Coordinator	Office	Phone	Email
Professor Kyle Lutes	KNOY 235	49-45125	kdlutes@purdue.edu

Assessment Mechanism	Total Points
Quizzes	40
Programming Exercises	500
Midterm Exam	100
Final Exam	200
Total	550

A	90% and above
B	80% - 89.9%
C	70% - 79.9%
D	60% - 69.9%
F	below 60%

1.	Students should not contact instructors just before, during, or just after class to discuss personal affairs. Matters of this type should be scheduled via email and discussed during office hours.
2.	Students are strongly urged to use email to contact the course instructors.
3.	The sender of all email correspondence must be clearly identifiable or it may not be answered. For example, it is recommended you include CPT 450 in the subject line and your full name in the message body. Additionally, email should be written in a professional, courteous, non-offensive manner. Email that contains unprofessional, discourteous, or otherwise offensive language will likely not be answered.
4.	Teaching Assistants only have authority to help with assignments and related questions. Personal matters should be directed to the course instructors.

1.	Students are expected to be present, be prepared, and display a positive, professional attitude throughout the semester in every class meeting. All students are also expected to share in classroom meetings by asking relevant questions and offering suggestions and answers to questions. Disruptive, argumentative, and other unprofessional behavior will result in the student being dismissed from the class.
2.	If you must miss a class for a valid reason, contact the instructor in advance about the possibility of rescheduling any missed work. You should also have the names of two or three other students in the class that you can contact to get class notes, announcements or assignments if you must miss class.
3.	In the event of an extended absence (usually three days or longer), you should contact the Dean of Students Office to report the absence and receive advice on how to proceed. Upon your return to campus, you must promptly contact your instructor to determine if, and how, missed work will be made up.

1.	According to CIT educational policy, this course may not be added to any student's academic schedule after the third week of a Fall or Spring semester (or equivalent for a Summer semester) except under very extenuating circumstances to be approved by the Department Head.
2.	According to CIT educational policy, no independent study course can be substituted for this course.
3.	You may drop this course without a failing grade so long as you do so before the published University deadline for dropping the course. After the initial withdrawal period, you will need your instructor's signature.

1.	Assignments will generally be posted one week prior to their due date unless otherwise noted by your instructor.
2.	Assignments must be turned in using the eSub electronic submission system as posted on the course web site.
3.	Assignments can be turned in early, *but late homework assignments will not be accepted*.
4.	All assignments must be prepared in a professional manner. Always check your assignments for correct spelling and grammar. Unprofessional work may not be graded. Points may be subtracted for submitting poorly or improperly organized work, or for not following instructions.
5.	To protect your privacy, graded materials will never be passed around the classroom or placed outside of an instructor's office door.
6.	Scores and grades will be posted on the course web page.
7.	The course instructors reserve the right to lower the grading scale expectations but will never raise the minimum grade requirements.
8.	Deadline extensions and extra credit assignments will not be given.
9	*Unless otherwise noted, all programming homework assignments that contain compile/syntax errors will automatically receive a score of zero.*

1.	Students wishing to appeal any score must return their work to their course instructor via email with a written statement explaining the appeal no later than one week after the original scores were posted.
2.	Any work submitted for re-grade (other than misreported material) may be totally re-graded. Do not assume the instructor will only re-grade those portions that the student wishes to be re-graded.
3.	According to University regulations, only final course grades can be "appealed." There is a formal College of Technology and University timetable and process for grade appeals. It must be followed exactly! Questions about grade appeals should be directed to the Department of Computer & Information Technology Department Head or the Chair of the College of Technology Grade Appeals Committee.

1.	The maximum penalty for cheating on any assignment, quiz, or examination in the course is an "F" grade for the course.
2	Is it worth the risk to receive an F in a class after a considerable investment of time/effort or worse yet to be suspended from school for one or more semesters at any time during your academic career? Don't Cheat!
3.	You are expected to do your own original work and to acknowledge correctly the work of others. Copies of the original authors' work(s) must be submitted with your assignment. One student doing/taking another's work (in whole or part) or collaborating with other(s) and submitting that work (in whole or part) as his/her individual effort (perhaps with cosmetic changes) constitutes cheating. Using unauthorized crib sheets or copying answers from another source when completing in-class assignments, quizzes, and exams constitutes cheating. Gaining unauthorized access to exams, quizzes, or instructor's keys or any student's answers is cheating.
4	Your instructor recognizes the learning value in exchanging ideas with others and learning from the mistakes and solutions of others; however, this type of unauthorized sharing can result in suspiciously similar work that is not an individual effort. All work that you submit must truly represent your individual effort. You should be aware that it is next to impossible for someone to forget a unique, creative approach once it has been seen/shared/heard. Most of the work in this class requires multiple levels of creativity, so it is not difficult to detect work submitted under suspicious circumstances. The best way to avoid being caught in the middle of a suspicious situation is to not discuss/show/share your work (in whole or part) with/to others.
5	Throughout the semester, your instructor will work through related problems and make assignment solutions available. You are encouraged to use these solutions to improve your understanding of course concepts and to facilitate your completion of course assignments. However, you are not permitted to exchange/give/take/use any other person's work without prior, written permission from your instructor. Failure to abide by this policy is considered cheating. If you experience difficulty in completing course assignments, you are encouraged to seek the assistance of your instructors during scheduled class meetings and scheduled office hours (or to schedule an appointment). Additional assistance will also be made available as needed and can be arranged.
6	Giving another student access to your computer account, or negligently permitting another student to access your computer account constitutes cheating on your part if that other student copies any files that become implicated in a cheating case. Protect your account as if your academic career depends on it!
7.	Cheating, or helping another student to cheat, are considered equal cases of academic dishonesty and will be dealt with as noted below.
8	All cases of academic dishonesty are forwarded to the Office of the Dean of Students for record-keeping purposes and consideration of other, appropriate disciplinary action.

Unit	Topic
1	Object-Oriented Programming Review
2	Introduction to the Java Platform
3	Database Connectivity and SQL
4	Software Architectures Overview
5	Multi-User Issues and Solutions
6	Component-Based Development
7	n-Tier Application Development using Web Services
8	The Impedance Mismatch Between Relational Systems and Object-Oriented Programming
Optional Units
9	Application Deployment and Distribution
10	Application Security
11	Application Transaction Processing