N342 Server-side Programming for the Web

Modified:

LF-105 or LF-111

Lab Consulting Schedule

Raymond Wisman:

William Apple:

May

S	M	T	W	R	F	S
10	11	12	13	14 WA 5-8P	15	16 RW 10A-2P
17	18 RW 5:30-8:30P	19 WA 2-8P	20 WA 12-5P RW 4:30-5:30P	21 WA 3-5:30P RW 5:30-8P	22	23 RW 10A-2P
24	25 Memorial Day	26 RW 2-8P	27 WA 12-5P RW 4:30-5:30P	28 WA 3-8P	29 WA 10-4	30 WA 8A-12P
31

June

S	M	T	W	R	F	S
	1 RW 5:30-8:30P	2 WA 2-8P	3 WA 12-5P RW 4:30-5:30P	4 WA 3-8P	5	6 WA 10A-2P
7	8 WA 12:30-5:30P RW 5:30-8:30P	9 WA 3-8P	10 WA 12-5P RW 4:30-5:30P	11 WA 3-8P	12	13 RW 10A-2P
13	15 WA 12:30-5:30P RW 5:30-8:30P	16 WA 3-8P	17 WA 12-5P RW 4:30-5:30P	18 WA 3-8P	19	20 WA 10A-2P
21	22 WA 12:30-5:30P RW 5:30-8:30P	23 WA 2-8P	24 WA 12-5P RW 4:30-5:30P

**Class Schedule**
	Reading	Home Work	Test
13 May	Client/Server (Browsers/Web Servers) Server Programming Overview HTML WWW Chapters 4 and 5 Client side programming Enrichment JavaScript WWW Chapters 7-12, 16 Content management - mambo Chapters 1, 2 of Guide to Web Publishing Basic Networking Protocols (TCP/IP, HTTP). Chapters 1 and 2.
20	Setting up a Server - Windows and IIS. Chapter 21. Server Side Programming - ASP using JScript, VBScript. ActiveX. Chapter 25. ASP/ADO Databases Start Project.	1
27	XML and XSL Introduction - WWW Chapter 20 ASP/ADO/XML/XSL Enrichment Chapter 5 of Guide to Web Publishing	2
3 June	Visitor Data - Hidden variables/Cookies. Chapter 25.7 and 27.9. User Session handling. RESTful services.	3
10	Microsoft .NET Code-Behind Dynamic Graphics. Java Applets. Project Finish Discussion	4
13		Last Credit for 1
14		Last Credit for 2
15		Last Credit for 3
17	Error Handling Security. Project finish, critique and wrap up. Protocols, Web Services and .NET	5
21		Last Credit for 4
24	Project Due 5:30pm	Project Finish
16 - 23	OnCourse test, can be taken over one hour period between 21:00 June 16 through 20:00 June 23. DO NOT use Internet Explorer. Use Safari or FireFox browser.		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 7:30-9: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 2007 (IUS Bookstore check out) or Download Free
Resources:	Recommended books, guides, tutorials, software available on Web
Course Goals:	See N342 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 24.
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