Instructor: Phil Waclawski
email: waclawski@mail.mc.maricopa.edu
http://www.felitaur.com/ (Instructors home page)
http://www.felitaur.com/webscripting/ Course Home Page
Section: 8041 Tues-Thursday 5:20-7:00pm BA1W
Lab Hours: See Schedule
Office: BPO 53, (480) 461-7468
Materials
You need to buy at least one 3.5" HD Floppy disk (or a USB flash
disk/thumb drive). Two or more green
scantrons from the bookstore should be purchased before the exams. A
notebook with pockets or a 3 ring binder would also be a good idea.
Rough Schedule (expect some modifications) | ||
---|---|---|
Week of: | Topic | Reading/etc |
January 17 | Introduction, Set up of Accounts, Review of Pre-Reqs. Programming Concepts, Intro to Perl? | Skim Chapter 1, read chapter 2 Assignment 1 Assignment 2: Practice form You can pick up Putty on my Internet page down near the bottom under "Web page resources". |
January 24 | Perl Basics, Control Structures | Read Chapter 3, Exercises 2.7,2.8,2.9 and 3.10 |
January 31 | Arrays and Hashes | Read Chapter 4 Exercise 4.8 |
February 7 | Control Structures II | Read Chapter 5 |
February 14 | Subroutines and functions, No Class Thursday, Take to Lab Assignment | Read Chapter 6 Exercise 6.8, add a bgcolor option for the body tag |
February 21 | Intro to CGI and CGI.pm | Read Chapter 7
Exercise 7.8 |
NOTE: All assignments from 7.8 onwards must be built as CGI programs, and should be linked into your index.html homepage | ||
February 28 | Regular Expressions and security | Read Chapter 8 exercises 8.5 and 8.6 combined |
March 7 | String Manipulation | Read Chapter 9 exercise 9.8 |
March 14 | SPRING BREAK WEEK | |
March 21 | File and Directory Processing and Manipulations | Read Chapters 10, 11 Exercises ??? |
March 28 | References and Objects | Chapter 13,14 |
April 4 | Session Tracking and Cookies | Chapter 16 Exercise 16.6 |
April 11 | SQL and PerlDBI | Read Chapter 15 | April 18 | SQL and Perl DBI continued | Exercise: 15.7 web page interface to DB you create |
April 25 | Web Services, SOAP::Lite, XML | Skim chapter 22 |
May 2 | Catch up week | Final Projects Due |
Finals | May 10, Tues 5:20-7:00pm BA1W |
Open Lab Requirements
As stated in the schedule, you
are required to spend at least 1 additional hour in the open lab. There
will be outside of class assignments and you will need to find time to do
so. Expect to spend several hours a week on this course outside of class. I will
be available during my lab hours for help, and possibly other times by
arrangement. You can see my attached schedule.
Grading
I grade on a straight scale based on
percentage of total points. If you attend the classes, do the work,
spend time every week in the open lab, you should do well in this
course.
90% A
80% B
70% C
60% D
Below 60% is an F
INCOMPLETE GRADES ARE NOT GIVEN IN THIS CLASS!!
Exams
There will be several short
"quizzes", possibly one or two main exams,
worth
50 pts each, and a final worth 100pts.
Projects and Assignments
Note: Assignments will be refined
nearly every semester. Do not "go ahead" or you will find out that
you have to redo an assignment. There will be several small to medium
programming projects. Often you will be sending me the
results as email attachments (or just the web links to the page involved
with a copy of the source attached). You will also have one or two
main projects. Approximately
300pts of your grade will be based in the small projects.
Final Project:
You will be doing a final project for this course, which will be nearly
150pts. In order to get a grade, you must complete this assignment.
Attendance
I am continuing to build this class as
we go. If you do not make attendance in class (and open lab) a priority,
you will not do well in this course. I can't stress this enough. You knew
when this class met when you signed up for it, so you have no excuse short
of illness, death in the family etc. Please do everything you can to
attend all classes.
Withdrawing from Class
As of this semester, if you just
"disappear" without informing me, you will be withdrawn with a "W". I
will only assign an "F" for the class if you have attended the
majority of the class, and you request that grade. It is YOUR
responsibility
to make sure you are properly withdrawn, or ask for a grade, if that is
your wish.
Requesting your final Grade Early
In accordance with FERPA (Federal
education records privacy act) I can only give out grades to the student
who earned them. So, if you want to request your grade by email (because
you just will die if you have to wait for it to arrive by snail mail ;),
it MUST be done via the campus email system
(username@mail.mc.maricopa.edu).
Requests from any other email will be ignored.
Plagiarism and Cheating
Check the college catalog for official
school policies. Again, I don't
expect this to be a problem, but if it does become a problem, I'll push
for the most severe punishment the administration allows. Remember, using
more than 4 words in a row without quoting (and including a source) is
plagiarism.
Cell Phones, Pagers
These have become a horrendous problem
of late. ALL cell phones should be turned off during class time. You will
get at most one warning. After that, I may consider either taking points
away, or if it continues, withdrawing you from the class. You can live for
a couple of hours without your phones (Just 4-5 years ago, hardly anyone
had these blasted things, and yet civilization didn't collapse, so you can
live without it for an hour or two). There may be periodic breaks for you
to go outside and call if you need to do so. Pagers should be put on
vibrate, but only if they are quiet when they buzz. Note, anyone actually
ANSWERING the phone in class will be asked to leave immediately, and not to
come back that day, or possibly ever.
Disciplinary Standards
Students who violated the disciplinary
standards of MCC (page 26 of the 2000-2001 college catalog) will be
removed from class, and if appropriate, withdrawn. Misconduct for which
students are subject to disciplinary action falls into the general areas
of:
General Standards Governing Use of Maricopa County Community
College District Computer Resources Handbook:
Maricopa's computing resources
specifically prohibits: "Transmitting, storing or receiving data, or
otherwise using computer resources in a manner that would constitute a
violation of state or federal law, including (but not limited to)
obscenity, defamation, threats, harassment and theft.
Violations of ANY provisions of the Standards, which are detailed in the Handbook, could result in immediate termination of a user's access to Maricopa's computing resources, as well as appropriate disciplinary or legal action.
Sexual Harassment Policy for Employees and Students
The policy of the Maricopa Community
Colleges is provide an educational, employment, and business environment
free of unwelcome sexual advances, requests for sexual favors, and other
verbal and/or physical conduct or communications constituting sexual
harassment as defined and otherwise prohibited by local, state and federal
law.
Sexual harassment by and between employees, students, employees and students, and campus visitors and students or employees is prohibited by this policy.
Violations of this policy may result in disciplinary action up to and including termination of employees, sanctions up to and including suspension or expulsion for students, and appropriate sanctions against campus visitors.
This policy is subject to constitutionally protected speech rights and principles of academic freedom. Questions about this policy may be directed to the Maricopa Community Colleges Equal Employment Opportunity/Affirmative Action (EEO/AA) Office.
Special Accommodations
MCC complies with the ADA. Anyone who
needs special accommodations should
let the instructor and disability services know immediately to insure you
have full and adequate opportunities to succeed in this course
.
Murphy's Law of Computers
Things go wrong and will. :) I have
put in a great number of hours in the past several months working on this
course. I will continue to put a great number of hours into the course
(outside my scheduled hours). I want this to be a fun course, and a very
useful one. However, I can't guarantee that everything will work, or that
we will be able to do everything. I will do my utmost to test out material
and assignments thoroughly before they are passed out, but we are still
installing things on our UNIX server (such as MySQL etc.) and stuff
happens.
Because of that,
things will be altered, edited, added and deleted from the above schedule.
Changes
will be put on the web pages as time permits, but they will be announced
in class. Therefore, attendance is crucial.