N341 Introduction to Client-side Web Programming

Modified:

LF-105 / UC-100

Lab Consulting Schedule

Raymond Wisman

June

S	M LF-105	T LF-105	W LF-105	R LF-105	F	S UC-100

July

S	M LF-105	T LF-105	W LF-105	R LF-105	F	S UC-100

August

S	M LF-105	T LF-105	W LF-105	R LF-105	F	S UC-100

**Class Schedule**
	Reading	Home Work	Test
27 June	Mapping W: Client/Server (Browsers/Web Servers) HTML WWW Chapters 4 and 5 Overview of Client side programming Client side programming Enrichment JavaScript WWW Chapters 7-12, 16 Content management - mambo Chapters 1, 2 of Guide to Web Publishing
4 July No Class but read notes and attend weekly lab	Read Chapter 7 and 8 handouts on Paper Prototyping The Web Design Process - WD 1 Designing for Users - WD 2. Task Analysis - WD 3 Content Organization - WD 4 Card Sorting Prototyping - WD 7 Paper Prototyping Demo Video, see OnCourse Resources User Testing with a Paper Prototype - WD 8	1
11	Start Project. XML and XSL Introduction - WWW Chapter 20 XSL Include and Server Side Includes for Standardized Navigation Debugging HTML/XML/XSL Syntax Errors Exercise 3 Results Enrichment Reading Chapter 4 of Guide to Web Publishing	2
18	Debugging HTML/XML/XSL Syntax Errors ADO/XSL/XML - Building modular user interfaces XSL Templates for Modular Systems Enrichment Reading Chapter 5 of Guide to Web Publishing	3
25	User Input Validation Cascading Style Sheets WWW Chapter 6 Client-side XML Page Types and Layouts Navigation Theory & Practice & Linking - WD 6 Site Maps, Indexes, Help & Other Navigational Aides Text - WD 10 Colors, Images and Backgrounds - WD 9 Project Finish Discussion	4
1 Aug	Search Dynamic Graphics - Java Applets AJAX - Asynchronous Javascript And XML Project finish, critique and wrap up. Web Technologies and Their Effect on Web-Design Site Delivery and Management	5
7	Project Due 9:00pm	Project Finish
1-7	OnCourse test, can be taken over a two hour period between 21:00 August 1 through 20:00 August 7.		Test

Course Details

Instructor:

Name:	Raymond F. Wisman
Office:	LF-122	By appointment outside of Lab Schedule
Phone:	941-2465
Email:
Web:	www.ius.edu/rwisman

Class:

Meetings:	LF-105 W 5:30-7:00 pm
Prerequisites:	C201 or other programming introduction.
No Text Required Recommended References	Internet and World Wide Web: How to Program 4e by Deitel and Deitel. ISBN-10 0-13-175242-1. User-Centered Website Development by McCracken and Wolfe ISBN 0-13-041161-2 Usability for the Web by Brinck, Gergle and Wood ISBN 1-55860-658-0 Web Design by Powell. ISBN 0-07-212297-8
Software:	FrontPage 2003 and Office or Download Free
Resources:	Recommended books, guides, tutorials, software available on Web
Course Goals:	See N341 Course Goals

Student:

Grade Scale:	A+ 97% - 100% A 93% - 96% A- 90% - 92% B+ 87% - 89% B 83% - 86% B- 80% - 82% C+ 77% - 79% C 73% - 76% C- 70% - 72% D+ 67% - 69% D 63% - 66% D- 60% - 62% F 0% - 59% Note that grades below a C are not accepted in the School of Natural Sciences.
Course Evaluation:	5 Homework Assignments 50% 1 Test 30% 1 Project 20%
Homework:	Due at the start of class on dates listed in syllabus. No late homework accepted.
Test:	Online test completed outside class.
Project:	A comprehensive project to implement a significant Web client/server application. No work can be accepted after 5:30pm, June 23.
Academic Ethics:	All work is subject to the Indiana University Code of Student Ethics. Learning requires a partnership between the instructor, authors, researchers and students; therefore students are encouraged to use any and all resources available to solve homework problems and complete programming assignments. However, students must: clearly cite any contributing source; a text, another student, the Internet, etc. create their own solutions For example, students may work in groups to solve homework problems provided each student creates their own (not copies) solutions and clearly lists all group members or other sources such as authors of texts or on the Internet. Likewise, software that performs assigned functionality may not be directly used but the source code may be consulted provided it is subsequently cited. Changing the spelling of algorithm identifiers does not constitute creating an original solution. It is absolutely essential to note that failure to cite any contributing source will be considered cheating regardless of the reason for the omission. Likewise, verbatim duplication of any source, whether from another student, a text, etc. will always be considered plagiarism. Violation of any aspect of this policy will result in a failing grade for the course.

FAQ