ITM352 Logo
ITM352



HOME
Overview
Schedule
Assignments
Policies
Contact
 

Assignment 4: Final Project

Description:

For this assignment, you will choose your own teams of 2-5 people. Your team will work together to build an entirely unique, new e-service website. It should not resemble any other websites designed by other teams from this or previous ITM352 classes and should not be previous homework sloppily pieced together. You are encouraged to find a real client for your project--perhaps a friend, relative, or neighbor who needs some website development done for their business, hobby, or charitable organization. All topics, whether they involve a real client or not, must be approved by the Professor.

First, discuss the concept of your e-service website, whether it be a music store, a clothing store, an acupuncture service, a site to support a church group, or something else, with your team members. Then sketch a design of the look-and-feel, pages, features, and navigation of the website. The requirements are intentionally "vague" for this assignment:

1) Your site must be original (it can NOT be something from a previous 352 assignment or class)

2) It should be "realistic" in that one could easily see how this site might actually be used in the real world.

3) It should be something you are proud to have built. It is a reflection of what you have learned in this class. This should include non-programming aspects such as design considerations, development concepts (e.g. prototyping and testing).

4) Your site must include some administration functions (e.g. to add/delete/modify inventory, add/delete users, reset user passwords, accept/reject customer contributions, etc.).

You are not limited to features from assignments 1-3. You are STRONGLY ENCOURAGED to add other features. For example, log-in and customized pages for members, special pages for blogs, discussion forums, customer feedback, customer-contributions, wikis, etc. Create whatever makes sense for your site.

You will present your e-service website to the class, so make sure you test everything and that everything functions properly well in advance of your presentation date. So treat your classmates as if they are your potential clients. Attendance during presentations is mandatory. Participation points will be deducted for missing class during presentations.

Deliverables:

Deliverable Due Date
Project Proposal: register team (member's names) and project at: 

     http://itm-vm.shidler.hawaii.edu/itm352/register/asst4_signup.php

You will be notified within 24 hours if there are problems with your proposal.  Also, you must sign up for a presentation slot by this date:  first-come, first served!

4/18
Software Design/User Interface Prototype Due (presented in class)
4/23
Project Presentation
Here are team presentation guidelines
4/30 or 5/2
Final Project Due (including a final project report as described below)
Your final report, web-site URL, code, and web-site credentials (regular login, admin login) should be emailed to Prof. Kazman by this date.
5/10 @ 11:59pm

Your project proposal should be a relatively short (2-3 pages + title page) document describing your client (real or imaginary), their requirements, and your proposed solution. The document should also describe your team (including a team name), the role and duties of each team member, and your major milestones (both internal and external, with dates) and final deliverables.

The user interface prototype should show all the screens that the user will encounter, and allow a user to navigate among them. This could be a pure HTML prototype: it is not necessary to have any working functionality at this point. You will present this in class.

The project presentation should explain all of the above in a professional manner, demo your project progress, and outline what needs to be done before your final project delivery to your "customer".

The project report (typically 10-15 pages, but write as much as you need) should explain:

  1. The project goals and objectives--what were you trying to do?
  2. What was accomplished in the project as compared to what was planned (with respect to the project proposal)?
  3. Describe any notable shortcomings, bugs, problems, or additional (incomplete) features.
  4. What was your biggest project risk and how was it managed?
  5. An assessment of the overall quality of the system.  Specifically, how did you do testing?
  6. What is needed before this system can be placed into operation?  For example: documentation, training, more data, more testing, transition to a cloud infrastructure, etc.

Remember to include, in your project report, the URL of your web-site and any credentials needed for regular and admin login.

Please treat this project as though you are a professional consulting organization. Give your team a name (e.g. PHP Gurus Inc.) and write the documents as though you were delivering a business presentation to a paying customer. Come on your presentation date well-dressed, prepared to impress, and ready to give a slick presentation.

Grading:

The points for the project are broken down as follows:

  • Project Proposal: 10%
  • Software Design/User Interface Prototype and Presentation: 10%
  • Software Quality (usability, correctness, completeness, ingenuity) and Final Report: 60%
  • Final Project Presentation: 20%

All team members will be required to fill out a peer evaluation form. Your grade will be adjusted, if necessary, to reflect your evaluations.


Assignment 4 Peer Evaluation

Instructions: Each team member must submit their own evaluation. Evaluations will be confidential and should be emailed directly to the Professor--kazman@hawaii.edu--within 24 hours of final project submission.

Name:_____________________________

When providing answers to the following items, be as specific as possible. Avoid vague answers like "I learned a lot" and "My partner did all the work." However, be as concise as possible.

  1. Assign an estimated percentage on the amount each team member contributed to the assignment (including yourself).
  2. Briefly explain your rationale for the above percentage breakdown. Be sure to include an overview of what specifically you and your partners contributed (e.g. "I worked on the security and my partner 1 worked on personalization").  The percentages of all group members, including you, must add up to 100.
  3. Describe what you are most proud of with your project.
  4. Describe what you are least happy about with your project.