SWE 642-002 Course Syllabus

Software Engineering for the World Wide Web

SWE 642-002, Spring Semester 2004

---

 

 

Instructor:	Dr. Nick Duan
Email:	nduan@gmu.edu
URL:	http://www.ise.gmu.edu/~nduan/swe642
Office Hours:	Anytime electronically or 20 min before class starts on Thursday in classroom

 TA:                  Ru He
 Office:             Room268, ST II
 Email:              swe642_2@yahoo.com
Office Hours:     Wed 7:30pm - 10:30pm
Office Phone:     703-993-1626

 

Prerequisite:

-         SWE 619 and SWE Foundation material  (MSCS Students may substitute CS 540 and CS 571 for SWE 619)

-         Knowledge of object-oriented programming and basics of Windows and UNIX

-         Basic knowledge of Java and HTML.  Programming experience desired.

 

Objectives:

 

-         Understand the concepts of web-based n-tier architecture and the principles of web application development

-         Become skillful with various technologies for developing dynamic web-based applications, with the emphasis on Java based component technologies

-         Become familiar with the software development life cycle and design techniques of large-scale web-based applications via hands-on programming project

 

Contents:

 

-         Dynamic web pages using HTML and JavaScripts

-         Web application development with Java Servlet and Java Server Pages (Servlet and JSP APIs, session management, security, packaging and deployment)

-         Web application security (authentication, authorization, encryption, PKI, SSL and digital certificate)

-         Design techniques for creating reusable component software (MVC model, J2EE design patterns for web applications)

-         Database connectivity of web applications in a 3-tier environment using JDBC

-         Introduction of XML and Web Services (XML structure and parsing techniques, DOM, SOAP, WSDL, and UDDI)

 

Textbook:

 

Budi Kurniawan, Java for the Web with Servlets, JSP, and EJB, New Riders, 2002 (Required, available from Johnson Center bookstore)

 

Additional References:

 

-         Patzer, et al., Professional Java Server Programming, Wrox Press, J2EE edition, 2000.

-         Castro, HTML 4 for the World Wide Web, 5th ed., Peachpit Press.

-         Naughton and Schildt, Java 2: The Complete Reference, 3rd ed., Osborne/McGraw Hill

-         Java Servlet Specification, 2.4, http://java.sun.com/products/servlet

-         JavaServer Pages Specification, 2.0, http://java.sun.com/products/jsp

-         XML and Web Services Specifications at W3C, http://www.w3c.org

 

Grading Policy:

 

-         Midterm Exam              30% (open book)

-         Final Exam                               30% (open book)

-         Project Assignment                   35%

-         Presentation/Innovation             5%

 

Project Assignment:

• Objective: to obtain hands-on experience with HTML, JavaScripts, Java Servlet, and JavaServer Pages through the development of a web-based, on-line, database application, and to gain experience with real-world software development.
• Description: The application is an on-line web store application with GUI-based functions for both the customers and the store manager.  The store manager should be able to publish and update merchandize information (categories, sales items, inventory, and prices), and generate sales report.  The customer should be able to register him/herself with the store site, enter personal profile information (name, address, and credit card information), and make purchase.  The types of categories and sales items are up to each student/group to decide.  The application should consist of
  • A web-based front end, development in a combination of HTML, JavaScripts and JSPs
  • A set of Java servlets containing the application logic and connected with the backend database via JDBC.
  • A database server used to store all relevant data of the application.  A light-weight, JDBC-enabled database will be provided by the instructor. Detailed information of usage will be provided during the class.
  • A credit card validation server (provided by the instructor).  The server is located remotely and the connection to the validation server is via HTTP with SSL.
• System and Deployment Requirement: The application should be developed using JDK 1.4, and Java Servlet version 2.4, JavaServer Pages version 2.0, using Apache Tomcat version 5.0.  The Tomcat server is available on department’s UNIX server or downloadable from Apache’s web site.  The final application shall be installed and demonstrated on a designated machine provided by the instructor
• Policies: The project can be completed individually or by a group of up to three students.  If done by a group, all students of the group will receive the same final score for the project.  The deliverable consists of a design document and source code. Design document should describe the system structure, components, JavaDoc, and GUI layout. The deliverable as a single J2EE web application is to be made available to the instructor on or before the due day.
• Detailed requirements and grading scales will be provided at first class session.

Additional Information and Policies:

• All class related information, including syllabus, project information, and class notes, is accessible from the instructor's web page.
• Each student shall set up his/her computer account to receive class-related emails and help information.
• Make-up exams are permitted on a case-by-case basis according to University and Department policies. Anyone who wishes to take a make-up exam must inform the instructor at least one week in advance (either in class or via email, with name and student number).  Project due day is fixed and non-negotiable.

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.