| Project Overview | Collaboration | Milestones
| Deliverable A | Deliverable B|
Deliverable C | Deliverable D | Deliverable E | Deliverable F | Deliverable G | Evaluation
Criteria |
Project Overview
This project provides students the experience in the methodology and the
collaborative process for Web site engineering. Your team will
function as a Web consulting group which has been contracted to
develop a business case and Web solutions for a client. The end product is a full
document and the implementation of the proposed web site.
The project should include the following components:
- Develop a business case for consumer-oriented Internet commerce.
It can be a dot.com case or a click-and-brick case.
- Analyze client requirements--strategies, customers/users, content, process, functions, and image.
- Provide an information architecture of the web site.
- Design site layout, content presentation, user interface, and
transaction processing.
- Implement your proposed site. The completeness of
your site will depend on the complexity of your proposal, and the team's
experience and size.
- Each web site must include transaction processing that
access databases, such as
order placement and payment processing. For non profit sites, this
may mean membership registration and other database driven functions.
- Prepare a technical feasibility report.
- Prepare a pro forma budget for implementation.
- Propose evaluation criteria to measure the success of the web site.
Milestones
and Deliverables
For each team project deliverable, list each team member's
contribution. It is expected that some team
members will devote more time and effort to certain but not all
deliverables. However, the contribution of each member (15% of the
course grade) should
balance out over the entire project. In another words, a team member
needs to take on a "fair"
amount of responsibility throughout the project, as judged by other team
members, in order to earn a satisfactory grade for contribution.
Each deliverable should provide information about the contribution of each
team member. Each member should have some programming responsibility for
the final project. Each team should create a project Web site in the assigned
project account and publish each deliverable timely to the directory of
"project_deliverables". For example, the URL
for team green19's deliverable C should be: "http://ectweb2.cs.depaul.edu/green19/deliverables/deliverableC."
Send the URL for each deliverable via email to the
instructor. Please note that ASP accounts are on the ECTWEB
server and ASP.NET 2.0 accounts are on ECTWEB2 server. Modify the above URL
accordingly.
DL Teams: Each DL team should schedule at
least two consultation meetings with the instructor about project progress,
one meeting for Deliverable C (between weeks 4 and 6) and one meeting for
Deliverable D or prototype (between weeks 5 and 7).
Deliverable A: Team
Organization Statement
- Form a project team of four to six members.
- Each team should have members performing roles of project lead, analyst, designer,
technical support, media/graphic design, programmer, and scribe.
Each team member is required to participate in the development of the
prototype web site and project presentation. Each member should
perform multiple roles
- The Team organization statement should include a
statement of mutual agreement regarding communication methods,
commitment to timely completion of tasks, and right to release members
who do not contribute to the project.
- Email the instructor an 1- or 2-page memo describing the names, skills, experience and
responsibilities of each member in the team and post the
deliverable online.
- Due: Week #2
Deliverable B: Business Case
Statement
- Post a 1-2 page statement about the client's business case.
- Present the proposed site's value proposition, business models (sources of
revenues),
market competitions, intended customers, and the rationale for using the
Internet solutions. If the project involves several phases,
discuss each phase and focus analysis on the immediate phase. For
multi-channel strategies, discuss how online and off-line channels work
in your case.
- Due : Week #3
Deliverable C: Requirements
Analysis and Specification Document
- Prepare an analysis of goals and message, content, structure and interpretation,
sensorial design, and market testing.
- This document should include a draft of (a) information
architecture for the site, and (b) the detailed flow chart for transaction processing
(catalog, order creation, order capture, payment authorization, order
fulfillment)-- a flow chart showing
the detailed process steps.
- Due: Week #4
Deliverable D: Detailed
Design
- Perform content and interface design
- Create content
- Integrate look and feel--sketches of layouts, graphics and template.
- Accommodate advertising
- Revise information architecture chart.
- Perform low fidelity (paper) prototyping. (optional)
- Post a document of revised information architecture chart, draft
page layouts/templates, page description, ERD and data tables, and sources of
content.
- Due: Week #5
Deliverable E: Technical and
Budget Feasibility Report
- Determine technical solutions and requirements for hosting web site and maintenance.
Explain rationale for your choice of ISP service.
- Prepare a pro forma budget for project implementation, including technology, planning,
programming, production, promotion and maintenance. Show one-time and
continuing
- Propose at least five criteria for measuring the web usage and
business success of this web site.
Explain the rational for selecting these criteria.
- Due: Week #8
Deliverable F: Project
Web Site and Presentation
- Implement the proposed web site.
- Perform response time and usability testing.
- Publish the results and project documentation.
- List team members' names and tools used in creating the prototype.
- Present the project prototype in class. Each team member should have a speaking part.
- DL teams are also required to make in-class presentation by at
least one team member. If there is schedule conflict, the team should
arrange a different date for presentation with the instructor.
- Indicate the tools and technology used in
developing this project.
- Provide details about the environment for site
testing (i.e., browser type and version, and display setting).
- Due: Week #11
Deliverable G: Project
Documentation
- Make necessary revision of all deliverables.
- Revise Deliverable A or provide a revised task responsibilities at
the end of the documentation.
- Post final project documentation on the ectweb2 course server.
- Provide a complete set of project documentation in a 3-ring binder.
- Include presentation materials and a copy of your web site in the
final document.
- Provide the complete URLs for the project site
and deliverable site, and password.
- Provide a list of responsibility of each member
for the deliverables and the final project.
- List the programming responsibility of each
member of the final project.
- Keep a copy of the project files and deliverables for your own record.
- Due: Week #11
Evaluation Criteria
This Team Project will count toward 40% of your course grade, 15% for individual contribution, and
25% for group work. Individual scores
will be based on the detailed list of responsibilities and contribution of
each team member, as well as the results of peer evaluation. Group
work will be graded upon the completion of the project. During the term, the instructor will provide written or verbal feedback
about each deliverable. Each team should arrange to meet with the
instructor in class or during office hours regularly. Late
submission of each deliverable will result in deduction of points. The
final project and documentation will be evaluated according to the following criteria (total = 100
points; 25%, see instructor's grading sheet).
- Team effectiveness -- leadership, clarity of roles and responsibilities, cohesiveness,
involvement and collaboration efforts (Deliverable A, minutes, a
detailed list of each member's responsibility and contribution, and peer evaluation) 10 points
- Clarity of project scope and objectives (B) 10 points
- Completeness of analysis (C) 15 points
- Consistency and creativity in design ( D )
15 points
- Sound technical and budget solutions (E) 5 points
- Complexity of solution and successful demo of prototype web site (F) 25
points
- Effective Presentation (Deliverable F) 10 points
- Completeness and quality of documentation (online project site, and
Deliverable G) 10 points
|