N342 Server-side Programming for the Web

   Modified: 

LF-105 / UC-100

Lab Consulting Schedule

Raymond Wisman
Chris Synder

May

S M  LF-105 T  LF-105 W  LF-105 R  LF-105 F S  UC-100
      11 12
CS 9A-3P
RW 6-7P		 13
 		 14
RW 12-4P
15 16
RW 12-3P
CS 3-5:30P		 17
CS 11A-12:30P
CS 1-6:30P		 18
RW 12-3P
CS 3-5:30P		 19
CS 9A-3P		 20 21
CS 12-4P
22 23
CS 3-5:30P
RW 6-9P		 24
CS 11A-12:30P
CS 1-6:30P
RW 6:30-9P		 25
RW 12-3P
CS 3-5:30P		 26
CS 9A-3P		 27 28
RW 12-4P
29 30 31
CS 11A-12:30P
CS 1-6:30P
RW 6:30-9P		        

June

S M  LF-105 T  LF-105 W  LF-105 R  LF-105 F S  UC-100
      1
RW 12-3P
CS 3-5:30P		 2
CS 9A-3P
 		 3 4
CS 12-4P
5 6
CS 3-5:30P
RW 6-9P		 7
CS 11A-12:30P
CS 1-6:30P
RW 6:30-9P		 8
RW 12-3P
CS 3-5:30P		 9
CS 9A-3P
 		 10
 		 12
RW 12-4P
12 13
CS 3-5:30P
RW 6-9P		 14
CS 11A-12:30P
CS 1-6:30P
RW 6:30-9P		 15
RW 12-3P
CS 3-5:30P		 16
CS 9A-3P		 17 18
CS 12-4P
19 20
CS 3-5:30P
RW 6-9P		 21
CS 11A-12:30P
CS 1-6:30P
RW 6:30-9P		 22
RW 12-3P
CS 3-5:30P
RW 6:30-9P		 23
CS 9A-3P		    
Class Schedule
  Reading Home
Work		 Test
11 May Mapping W:
Client/Server (Browsers/Web Servers)
Server Programming Overview
HTML
Client side programming
Enrichment
    Content management - mambo
    Chapters 1, 2 of Guide to Web Publishing
    Basic Networking Protocols (TCP/IP, HTTP). 		   
18 Server Side Programming - ASP using JScript, VBScript. ActiveX.
ASP/ADO Databases
Start Project.		 1  
25 XML and XSL Introduction
ASP/ADO/XML/XSL
Enrichment
     Chapter 5 of Guide to Web Publishing 		 2  
1 June Visitor Data - Hidden variables/Cookies.
User Session handling.
RESTful services.		 3  
8 Editing DOM trees
Microsoft .NET Code-Behind
Dynamic Graphics.
Java Applets.
Project Finish Discussion		 4  
15 Error Handling
Security.
Project finish, critique and wrap up.
Protocols, Web Services and .NET  		5  
22 Project Due 9:00pm Project
Finish		  
16 - 23 OnCourse test, can be taken over a two hour period between 21:00 June 15 through 20:00 June 23.   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 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:

  1. clearly cite any contributing source; a text, another student, the Internet, etc.
  2. 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