| ITEC 325 |
| 2014spring |
| ibarland |
|
|
|
home—lects—hws
D2L—breeze (snow day)
ITEC325 is an introduction to intermediate Web processing technologies, focusing on PHP, forms and data validation, and XSLT. Topics include:
These hours are subject to change; see the class web page for the most up-to-date times.
| Dr. Ian Barland |
|
Davis 230 |
You are also encouraged to post questions on the D2L discussion board. If you email me instead, please include “ITEC325”; I will answer on the discussion board if it's a question several people might have.
|
Larry Ullman
PHP Visual Quickstart Guide (The 4e and 3e versions are more to be compatible w/ PHP6, but 2e is acceptable as well.) ISBN 978-0-321-44249-9, publ. Peach Pit Press |
Optional |
|
Kevin Howard Goldberg
XML Visual Quickstart Guide ISBN 978-0-321-55967-8, publ. Peach Pit Press. |
Optional |
The above two texts are both available electronically from
McConnell Library,
via their Safari Electronic Books.
(They require authenticating with your RU password.
They may not always be available: only a limited number
of licenses have been purchased by the commonwealth.)
Between the library's e-book, the posted lecture slides, and web searches
you should have all the materials you need.
However, many students (and, your prof) still find a physical copy of the book
better for both studying and referencing.
Class Courtesy
Please refrain from texting during lecture,
and use a computer only for taking notes and looking up material related to lecture
(e.g. looking up allowable attributes for a
Evaluation:
| Assignments | 40% |
| Project | 20% |
| Exams (2) & Quizzes (weekly-ish) | 40% |
Programming assignments will be graded not only for the extent to which the program produces the required results, but also for programming style. In particular, the programs should be well designed and self-documented with meaningful and informative comments and identifier names. A program which does not run might summarily get a 0. PLEASE compile and/or run your programs or documents immediately before submitting. Never make a change to the code or html file(s) and turn it in without compiling and running first. It is very easy to make last minute mistakes that introduce syntax errors, so checking before submitting can save you an unnecessary grade of 0.
A special word of caution about the deadlines for programming assignments: The assignments for this class will generally require more time for completion than you might assume at first glance. Because certain error messages can be sparse or non-existent, significant time can be spent tracking down problems like file-permissions or files in the wrong directory (totally unrelated to the complexity of the program itself). Since the penalty for being late is severe, you should begin working on each assignment as soon as it is distributed. Allow time for unexpected problems and difficulties such as minor computer downtime. Keep back-up copies of your work -- computer crashes are not an acceptable excuse for late assignments!
There will frequent summary-quizzes and occasional pop quizzes in class; fair game for these quizzes include applying concepts from recent lecture topics or reading, as well as any previous homework problems. (Note: “recent” lectures includes lecture material given earlier in the same class!)
Final Exam: May.05 (Mon) 14:45, as per the final exam schedule.
Although there are no attendence points per se, short in-class quizzes are factored into your grade.
Late Policy: Late homeworks will be accepted up to 48hrs late with a penalty of 15% of points-possible. (Homeworks between 0 and 3hrs late might be accepted for only a 5% penalty, at discretion of the teacher.) If turning in hardcopy late, you must include the due-date and the time you turn it in. Do not submit late homeworks intermingled with currently-due homeworks.
If you know in advance you won't be able to turn in homework on time (e.g. participating in university sports) you must get permission in advance to turn the homework in late. For significant illness or family crisis without advance notice (but with later documentation), contact the professor as soon as possible to arrange to catch up on the work. You cannot make up missed quizzes; however your one lowest quiz score will be dropped.
Honor Policy: As with all your RU classes, the university honor code governs all work done for the course. (For some specifics, see page 7, items 1-9.) Copying from internet sources (including Wikipedia) is plagiarism. Allow other students to copy your work (either knowingly, or due to not taking proper measures to secure your work — e.g. printing to a lab printer but not picking up the hardcopy promptly, or making your files readable to others on a filesystem that others have access to.
You are encouraged to discuss and interpret the homeworks and general approaches to solutions with your fellow students. However, You must be the direct author of all your submitted work. (For example, sharing (sending or receiving) a hw solution with others is a clear honor code violation.) If you had worked through a homework problem while talking with a friend, you must re-write it on your own, without referring to your draft version. If you got significant advice which you'd like to credit somebody for, cite them in your work.
Other University Resources: Radford has many resources to help you in different ways, including the student counseling services (x5226), and the Learning Assistance Resource Center (“LARC”, x7704, www.radford.edu/~larc, ). If you need any special accomodations for a class, and have registered with the Disability Resource Office (x6350, Tyler Hall Suite 64), please contact the professor at the start of the semester.
1 Still, safety comes first in inclement weather; if attending-virtually isn't possible due to safety concerns, contact me to avoid attendence issues, though you will still need to review any material discussed. ↩
home—lects—hws
D2L—breeze (snow day)
| ©2013, Ian Barland, Radford University Last modified 2014.Jan.22 (Wed) |
Please mail any suggestions (incl. typos, broken links) to ibarland  radford.edu |
 |