Spring Semester 2005, 3 semester hour credits
Avery 111, TR, 9:30am-10:45am
| Instructor: |
Stephen E. Reichenbach,
Professor Avery 260; 472-5007; reich@cse.unl.edu Office Hours: 11:00am-12:00noon MTWRF (or by appointment) | |
|---|---|---|
| Assistant: |
Jiazheng Shi,
Graduate Teaching Assistant Avery 122C; 472-4257; jshi@cse.unl.edu Office Hours: MTWRF 1:30pm-2:30pm (or by appointment) | |
| Textbook: |
Required:
Programming the World Wide Web, 2nd edition Robert W. Sebesta (Addison Wesely, 2003) | |
|
Optional:
XML in a Nutshell, 3rd edition Elliotte Rusty Harold, W. Scott Means (O'Reilly & Associates, 2004) | ||
This course is a survey of paradigms and languages used for Internet programming, including client-side and server-side programming, object-based and event-based programming, and multi-tier applications with XHTML, HTTP, CSS, DHTML, JavaScript, XML, DOM, CGI, Perl, PHP, distributed SQL services, Java applets, servlets, JavaServer Pages, and Web services. The course is made difficult to plan and execute by the rapid changes in the technologies of Internet programming. Students must have advanced knowledge of programming in a high-level language such as Java and broad knowledge and experience with data structures and algorithms. Knowledge and experience with an object-oriented programming language (e.g., Java), SQL database systems, software engineering, computer organization, distributed systems, and computer networks is helpful.
The planned components of the course are the textbook readings, lecture
attendance, quizzes, programs, and written reports.
The planned schedule of lecture topics and text references are listed
in the following table (subject to change).
| WEEK | DATE | LECTURE | TEXT |
|---|---|---|---|
| 1 | Jan 11, Jan 13 | Introductions, WWW | 1 |
| 2 | Jan 18, Jan 20 | HTML and XHTML | 2 |
| 3 | Jan 25, Jan 27 | HTML, XHTML, CSS | 3 |
| 4 | Feb 1, Feb 3 | XML, etc. | 8 |
| 5 | Feb 8, Feb 10 | XML, etc. | 8 |
| 6 | Feb 15, Feb 17 | JavaScript | 4 |
| 7 | Feb 22, Feb 24 | JavaScript and DOM | 5 |
| 8 | Mar 1, Mar 3 | JavaScript and Dynamic Documents | 6 |
| 9 | Mar 8, Mar 10 | Java Applets | 7 |
| 10 | Mar 22, Mar 24 | Perl | 9 |
| 11 | Mar 29, Mar 31 | CGI, Perl | 10 |
| 12 | Apr 5, Apr 7 | PHP | 12 |
| 13 | Apr 12, Apr 14 | Databases, PHP | 13 |
| 14 | Apr 19, Apr 21 | Servlets and JavaServer Pages | 11 |
| 15 | Apr 26, Apr 28 | SOAP and Web Services | |
| 16 | May 3 | Final exam (10:00am-12:00noon), final project due |
There will be several short quizzes covering the assigned reading and lectures. Not all quizzes will be announced in advance. There will be several programming assignments which will provide substantial hands-on experience with practical implementations. The final grade will be based on both quizzes and final exam (50%) and homework (50%).
The CSE Department has adopted an academic integrity policy that requires reporting of all incidents of academic dishonesty to the CSE Department office. You are responsible to read the policy and adhere to it. While it can be permissable to discuss problems in general terms with others, you must do all class work independently. Representing the work of anyone else as your own, in whole or in part, is plagiarism. Sharing your work with others in the class is equally serious. Make sure that all your files are protected. You will be accountable if someone copies your work and hands it in. Students whom the instructors determine are guilty of academic dishonesty will receive an F in the course and will be referred to the CSE Department office with a recommendation for expulsion.
We welcome any comments or suggestions you wish to make at any time during the semester - we plan to be flexible in conducting this class and your input will help us conduct the course. We have posted office hours when we will make every effort to be in our offices, but we sometimes have other commitments so if it is important to see us try to make an appointment. One of us is here most daytime hours and can usually take time to talk, so feel free to drop by most any time. On programming questions, it is best to see the GTA first. Also, email is one of the best mechanisms for contacting us.