IT6753 Advanced Web Concepts and Applications -- Final Project Requirements

Richard Halstead-Nussloch, Ph.D.
January 2005

Due Dates: (list)

• Team set-up and organization:
• Proposal:
• Presentation and Demo:
• Report:

Objectives

Upon successful completion of the final project, each student will be able to:

• Define and discuss major business, architecture and technical issues faced by web-service developers.
• Articulate and selectively implement appropriate business-case and design strategies and principles for a web service.
• Analyze the target population of a proposed web service and design effectively for those users.
• Design a prototype web service.
• Evaluate the web service.
• As appropriate, incorporate enterprise architecture into web services.

Fundamental Requirements

• The choice of a web-service development problem domain with a significant degree of information and/or technical complexity complexity. (For this term, we will work within the domain of web newsletters.)
• A completed information analysis for the problem domain and audience analysis for the user group to ensure the design centers on the information the user needs
• A completed analysis of the enterprise architecture to ensure the web service fits within the current enterprise approach
• An application prototype of the web service
• Successfully complete one iteration of development and test
• Requires blending the work of each individual on the team

High Level Schedule

Step 1 - Choices

Choose:

• Team
• Roles on the team
• Development methodology
• Project--Web Service for a Web-Based Newsletter

Step 2 - Requirements and Information Analysis

Identify requirements for your project and complete a) information analysis, b) audience analysis, c) business case, and d) enterprise-architecture analysis.

Step 3 - Design, Code, and Test

Complete the design, code prototype web service, and begin testing

Step 4 - Code, Test, Present, and Report

Complete the coding and testing. Present your project to the class.

Step 5 - Finalize, Package, and Hand-in

Hand in the report and code and accompanying materials via WebCT on the the final exam day.

Suggestion for Project Reporting

In addition to the project report, which should be short (10 pages or less), we suggest a project log or notebook be submitted. In the log, your team can document activity and partial products (e.g., designs, layouts, analysis reports, business case etc.) that will be useful in evaluating the project according to the following criteria:

For a C

The team makes a good-faith effort at completing one iteration of the project.

For a B

The team completes what is described above and has an effective business case and analysis set. Team completes a working prototype for a significant segment of the web service.

For an A

The team completes what is described above and implements a reasoned, and disciplined design for the requirements and associated analyses. The design should encompass and be consistent with the business case, the requirements, the analyses, good principles of design, have a good information architecture and user interface (if applicable). The web service should be well tested (for audience approval, usability, coding, etc.). The project personnel should work together well as a team, and teach each other tips and techniques.