Metropolitan State University
ICS 225 Web Design and Development
Project: 2
Concept: Events, Forms & Navigation
Due: October 9
Points: 50
points
Preliminary Project Plan is Due Next
Week
1. Goals:
§
Combine the use of XHTML, CSS and JavaScript
§
Provide consistent navigation on all pages
§
Validate fields using JavaScript
§
Write your own functions
§
Use arrays
§
Be creative and produce a visually attractive, usable
set of pages
2. Overview:
Design and
build a web site of at least 5 pages (not including the previously created
index page) on a topic of interest to you.
(Note: A picture does not count
as a web page.) You may adapt the work
you did on project #1 if you wish and continue to build on that theme for this
project. Be sure to COPY your existing
pages and work on the copies if you wish to start on project #2 now. Do not change the original pages for project
#1 before it is graded or it will be counted as late.
Bear in
mind that you may wish to use your work in this class as part of a portfolio
that you can show to a prospective employer.
Make your web site look as professional as possible.
Your work
must be your own original and individual work.
That is, you cannot exactly copy an example from a book to meet the
requirements.
3. Requirements: Demonstrate the use of at least these
features.
·
Navigation
-
Use
the same navigation scheme across all pages
-
Make
your navigation as attractive and consistent as possible.
·
Use
all three of these event handlers
-
onclick
-
onmouseover
-
onmouseout
- Collect data using a form
-
Include
at least one example of making a form field appear or disappear based on the
value of another field
- Implement and use the following
forms validation techniques using functions you have written
-
Check
for a valid email address
-
Check
for blank entries in required fields
-
Check
for numbers only
-
Check
for a valid phone number
-
Create
and use at least one array
-
Use
a separate style sheet file which contains at least 4 style rules in addition
to those you created for the last project (or at different from those you
created for the last project)
-
Use
functions where appropriate. Use
functions at least once.
-
Comment
your code appropriately. Include the
name of the file, the author, the creation date and a short description of the
purpose of the page in each file.
-
In
the footer (or some other unobtrusive part) of each web page, include a brief
description of the project requirement(s) that page meets. Come up with a standard convention for doing
this that is not distracting to the user of your web site.
-
Your
pages must be attractive and professional looking. Try for a consistent look and feel across
pages.
4. Turn in:
- Put
this project in a separate directory on the class server.
- Add a
link from your home page to this project.
- Print
and hand in a project report which includes the following sections:
a.
A title page with your name, the name and number of
the class (ICS 225), the date and the URL of your project. Indicate which browser you normally use for
testing
b.
A 2-paragraph summary of the nature and purpose of
the system (see McCracken, p. 5, needs analysis)
c.
A user analysis characterizing your typical user (see
McCracken, p. 6)
d.
A task analysis (see McCracken, p. 6)
-
List the user goals or tasks or activities
e.
A project plan with – a preliminary version with
milestones and estimated times is due next week
-
Milestones with dates (due next week)
-
Estimated time to complete each milestone (due next
week)
-
Actual time to complete each milestone
-
Actual completion date
f.
Rough sketches of the web pages and the links between
them (flow of control)
There will be a 2% penalty if you do not hand in a printed
copy of your report.
Late Penalty:
10% per day late
Extra Credit:
Use a regular expression for field validation