SWE 642

There is one required text for the course:

• Java for the Web with Servlets, JSP, and EJB, Budi Kurniawan, 2002, New Riders Press. Amazon New Riders

We will read from Kurniawan, various sources on the web, and transparencies that will be made available on the web site. The schedule for the readings is given on the schedule web page.

There are two recommended books for HTML and Java. Many students will already have good references for HTML and Java, so these are only recommended if you need them. Please note that I did not order these books through the bookstore, but the Java book is used in SWE 619 and INFS 590.

• HTML 4 for the World Wide Web, 4th ed., Castro, Peachpit Press. Amazon
• Java 2: The Complete Reference, current edition, Naughton and Schildt, Osborne/McGraw Hill. Amazon

Other web software reference books are listed on the assignment and resources page.

SWE 642 teaches some of the topics related to the exciting new software development models that are used to support web and e-commerce applications. We will be studying the software design and development side of web applications, rather than the policy, business, or networking sides. An introductory level knowledge of HTML and Java is required. SWE 619 is a required prerequisite and SWE 632 is a good background courses. The class will be very practical (how to build things) and require extensive small programming assignments.

The course content will focus on client-side and server-side software design and devlopment. We will learn technologies such as HTML, JavaScripts , J2EE platform and XML.

A number of homework assignments will be given. I will discuss each in class and make the assignment available on the class web site. You will submit your solutions by placing them on your web sites. You will send an email to myself, and CC the TA. The email will contain a URL to access your assignment, and a zip file containing all of your code. I reserve the right to deduct points if the link and/or zip file is not included with the homework.
Be sure that you are on the class mailing list, as refinements and hints for the assignments will be sent through email. Assignments will be checked immediately after the due date; if you finish an assignment late, you must inform us by email when it is ready for us to grade it. Changing an assignment after the due date without prior permission will be treated as a late submission. Late submissions carry an automatic 10 percent deduction in grade for each week that it is late. No homeworks will be accepted after the start of the last lecture on Week 14 (04/29/2008).

Assingments will be graded on style and formatting as well as correctness. A more detailed description on the homework grading will be included with the homework requirements when assigned.

Since the assignments are web-based, it is your responsibility to have the homework assignements hosted. George Mason offers an application server to SWE 642 students as a convenience. However, if you would like to host your homework elsewhere, that is permitted, as long as the TA and myself can access the assignment, and the server space where the assignment is hosted. Below are some links for Java based hosting companies. Feel free to use them (or any other you can find), but remember, your homework is your responsibility. I highly reccomend downloading and installing the Tomcat Applcation Server on your own computer, so that you can still complete your assignments, even if your application server, or Internet connection, is down.

• http://jsp-servlet.net/
• http://www.servlets.net/
• http://www.lunarpages.com/

Missed quizzes and tests cannot be made up. Late assignments will be deducted 10 percent per class meeting. Assignments that are handed in later than 2 weeks will receive a zero. No homeworks will be accepted after the start of the last lecture on Week 14 (04/29/2008).

As with all GMU courses, SWE 642 is governed by the GMU Honor Code. In this course, all assignments, exams, and project submissions carry with them an implicit statement that it is the sole work of the author, unless joint work is explicitly authorized. Help may be obtained from the instructor or other students to understand the description of the problem and any technology, but the solution, particularly the design portion, must be the student's own work. If joint work is authorized, all contributing students must be listed on the submission. Any deviation from this is considered an Honor Code violation, and as a minimum, will result in failure of the submission and as a maximum, failure of the class. Honor code violation may include, but are not limited to the following examples:

• Copying answers from other students during exams.
• Submitting homework that is not your own work.
• Copying and pasting someone else's code into your own files (even with slight modifications)

The examples I show in class can be used to grow on, not to copy. I understand that in the real world, software reuse is considered the norm, and can drastically improve a projects schedule. However, in this class, software reuse will be considered an Honor Code violation, unless permission is granted before the project is submitted. When in doubt, ask me? It is better to find out what I would consider a violation before the assignment is submitted. This is not the real world, and one of the requirements to passing this class is that you, the student, can handle the material on your own.

For more information about the GMU Honor Code, Please visit the GMU Honor Code page.

• There will be several computer programming assignments (total 30%)
• There will be 7 quizzes throughout the semester. They will be given during the first 20 minutes of class time. You are allowed to miss two quizzes (the two lowest quiz grades will be dropped). The 5 quizzes with the highest scores will be used to calculate the final grade (5 * 6% = 30%)
• There will be a closed-book, in-class, comprehensive final (40%)