Course Information Schedule Assignments

SWE 642: Software Engineering for the World Wide Web
Course Syllabus
Fall 2007

Professor: Andy Gravatt
Email: agravatt@induscorp.com
Class Hours: Thur 7:20-10:00, Bldg: Robinson Hall, Rm: B220
Prerequisite: SWE 619 and SWE Foundation material or (CS 540 and 571)
Office Hours: None scheduled. Please e-mail me if you have any questions.
TA: Hanjo Jeong
TA Office Hours: 5:30 - 6:30 p.m., Building: ST2, Room: 458

TEXTS:
There is one required text for the course:
There are two recommended texts 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.
Other web software reference books are listed on the assignment and resources page.

OBJECTIVE:
Detailed study of the engineering methods and technologies for building highly interactive web sites for e-commerce and other web-based applications. Engineering principles for building web sites that exhibit high reliability, usability, security, availability, scalability and maintainability are presented. Methods such as client-server programming, component-based software development, middleware, and reusable components are covered. After the course, students should be prepared to create software for large-scale web sites.

CONTENT:
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 course. 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.

READING:
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.

MAKEUPS AND LATE SUBMISSIONS:
Unless arrangements are worked out in advance, the Final Exam cannot be made up. Each homework will receive a 10 percent deduction per class meeting when submitted late. No homeworks will be accepted that are more than two-weeks late or after the start of the last lecture on Week 14 (12/6/2007).

HOMEWORKS:
A number of homework assignments will be given. I will discuss each in class and make the assignment available on the class web site. All assignments will be tested on Internet Explorer and must work on this web browser. Each homework (except Homework 1) will be submitted by e-mail to the GTA (TBD) and the professor (agravatt@induscorp.com). The e-mail should include all of the files necessary to run the application and a link to our class server where the application can be tested. If you finish an assignment late, you must inform us by email when it is ready for us to grade.. Changing an assignment after the due date without prior permission will be treated as a late submission. Each homework will receive a 10 percent deduction per class meeting when submitted late. No homeworks will be accepted that are more than two-weeks late or after the start of the last lecture on Week 14 (12/6/2007).

Programs will be graded on style and formatting as well as correctness.

You are not permitted to share project code with another student. You are not permitted to run the homework assignments of other students in the class. Both of these infractions will be considered a breach of the GMU Honor Code and will not be tolerated.

HONOR CODE STATEMENT:
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.

GRADING POLICIES:
  • There will be several computer programming assignments (total 30%)
  • Each class (except the first one) will have a quiz in the first 15 minutes of classtime. You are allowed to miss up to three quizzes (the lowest three quiz grades will be dropped). The 10 quizzes with the highest scores will be used to calculate the final grade (10 * 3.0% = 30%)
  • There will be a closed-book, in-class, comprehensive final (40%)
Top