home—lects—exams—hws
D2L—breeze (snow day)
project
Project
requirements
For this course,
teams of four students
will design a web application.
Some examples of the sorts of things that can be done are:
-
A reservation system:
Enter room-requests,
have them approved,
show all reservations for a given room,
show all reservations for a given client,
udpate a room's details.
Include a calendar view.
-
A specific variant of the above:
A scheduling tool for RU students to make (advising) appointments w/ a faculty member.
For example, spend an hour trying out a site like checkappointments.com
and doodle.com
(setting up your schedule and having a friend arrange an “appointment” with you),
and see if you can make a site which is better for the specific task of RU student advising.
-
mp3 shop:
Browse inventory,
search for albums/artists/songs,
release files upon payment,
update inventory.
-
sports-team database:
Look up information about players and about teams;
administrators can to update such info;
users can have a list of favorites teams or players
and log in to see summaries.
Allow users to either make changes to data,
or suggest changes to be reviewed by an administrator.
-
Live project (External client):
Let coaches enter range-of-movement measurements of their athletes, and store in a database.
Any injuries during the season will be entered (and stored) later.
Then, this info can be mined for correlations that can help predict and prevent future injuries.
See full information
-
Live project (external client): a nursing Ph.D. student
Develop a small web site to give providers
a central, easy source for
diagnosing and treating vaginitis
(one or two pages for each of the four types, plus one landing/diagnosis page).
-
Live project (external client): a local Church
Improve and update the webiste for
a local church
- If you know of a local organization, charity, or business
that would like a web project,
and are interested in helping them,
see me right away.
-
A page for a (campus) club, that you seek out.
Perhaps one with events that people can sign up for;
or perhaps one with a bio sketch for each member;
…
- A web-site to maintain a friendly betting pool:
On superbowl sunday, friends come over and watch the game together,
and might have a small betting pool
based on
an elegant parimutuel system.
A web-site would track the tickets issued,
and when the game finishes it would show how to distribute the pot.
See ibarland@ for details.
You encouraged to suggest your own projects, perhaps inspired by the suggestions above.
However, your project must include the following features1:
-
Your pages are reachable via
https://php.radford.edu/projn, where n
is your team-number (in {1,…,5}).
I will likely require access via git as well (presumably bitbucket.org
or github.com).
-
User authentification,
either as a client or a manager/administrator.
-
A back-end database to store information.
-
Pages for clients to
enter new records,
and view all their own records (possibly modifying/updating parts of them);
-
Pages for administrators to modify any records (with safeguards),
view appropriate
groups of records (e.g. all reservations for next week),
with a page for administrators to enter/modify any record,
a way for a client to enter/modify parts of their own record,
and
ways for administrators to view summary of many records.
-
Data validation performed (as appropriate)
on the client-side, server-side, and database back-end.
-
As appropriate, a unified appearance for all the pages.
-
You may use tools like dreamweaver,
as well as libraries like Node.js or PEAR packages you install.
Be sure to cite code you get from elsewhere
(e.g. a bunch of php/javascript for showing a clock/calendar),
and during your presentations be up-front about what libraries
and code you made use of.
(Discussing the difficulties of integrating others' code certainly
can be a worthy topic, as well.)
If you feel unsure whether you're borrowing too much,
just talk with me.
Note that the individual homeworks are where the course
ensures you know various specifics of coding;
the project is intentionally there to help you expand
your vision of what your sites can (or, should) do.
Checkpoints include:
- (due
Feb.13 23:59; email to me (one per team))
Choose teams and projects.
Choose one team member as liaison, that I'll channel all communication through.
The liaison should send me the names of the team-members, and a 3-sentence description of their project.
- (due
Feb.23)
Submit a proposal (10%):
-
Team name,
-
members (with the liaison )
-
a list of pages that site will contain, along with:
- A crude, hand-drawn mock-up of each page
(each page has a short name;
each links/forms to other pages are that target name, circled).
You do not have to use crayons.
- A crude, hand-drawn mockup of any standard header/footer/sidebar
that will be on all other pages.
-
What input fields each page has (if any),
annotated with what data/validation will allow a successful submit;
(perhaps even the exact id/name attributes
for each input field).
-
Example sentences of the page-specific content.
-
A database schema/ERD:
what tables,
what columns they have,
and one-to-two sample rows for each table.
Show primary and foreign keys.
(This can be hand-drawn, but neatly (using ruler etc).
Or you can use a tool such as Visio,
which might save time during updates and presenting later.)
You aren't locked in by this proposal;
it is intended to make sure you have thought through what you
need to do, and that the entire group understands
exactly what functions will be implemented.
(Details to follow:)
You will also have to have a git account working (presumably on bitbucket.org or github.com).
Have a README file for the project, which includes
the team name and their members (as well as usual README info:
a quick overview of the project,
what sub-directories include what major components of your project).
Everybody should be pushing their changes to this repo regularly;
I'll glance at the project's log.
Add ibarland@radford.edu as a team-member to the git project!
-
(due Mar.
1718)
Prototype (10%), with a class demonstration (10%):
-
A stub for each page,
with input fields and links
(validation not fully required).
-
An instantiated database , even if just done in Excel tables or written on paper, with the indicated tables,
and at least four rows of sample (concocted) data in each
(exercising the range of cardinalities in the ERD),
and
at least two sample SQL queries that might
be eventually generated by the web form
(but not necessarily connected to the web forms).
-
For the presentation:
this is fairly informal — you don't need to dress up,
nor have powerpoint slides (though you certainly may, if you like).
But you do need each person to partake in the presentation,
make eye contact with everybody in the room (not just the professor),
and not have any misspellings on your web page or database samples.
-
The pages and database design you present are locked in at this point.
-
(due Apr.01) Progress report (5%):
A short written summary of progress and problems-encountered (less than one page),
including which team-members have been contributing to which component(s).
- (due Apr.29 and May.01)
Final project (40%), with a class demonstration (15%):
Full data validation and database connectivity.
In your demo, include a few moments to talk about
technical and managerial difficulties you encountered (expected or not).
- (due May.01 (Fri) 23:59)
Peer evaluation (10%):
Evaluate both other groups' presentations,
and your teammates.
project-team-feedback—itec325 project feedback
Due dates are at the start of class, unless indicated otherwise.
Archiving your project
The project-accounts will be cleared, a few weeks into the summer!
If you want to keep a copy of your work…
-
Grab all the code files.
(If you've been using github or bitbucket, this is already done!)
-
Grab the database!
In myphpadmin, there is an “export” button which will
create a .sql script which, when run, re-adds all the tables and populates them.
-
Make a screencast?
If you want to link to the project in your resume/portfolio,
but don't want to keep the project hosted and live and updated-security,
a screencast isn't as good as a live site, but is better than nothing.
If you archive your project, you might want to share your files with your teammates.
1If you
have an external client,
their requirements trump my list.
However, if you learn that there are features below that aren't included at all,
contact me before the proposal deadline, and we'll work something out.
↩
home—lects—exams—hws
D2L—breeze (snow day)
radford.edu