IT6403 Windows Application Development -- Final Project Requirements

Richard Halstead-Nussloch, Ph.D.

Due Dates: (list)

• Team set-up and organization:
• Decide on Problem Domain, Objectives, and Learning Requirements:
• Proposal:
• Presentation and Demo:
• Report:

Objectives

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

• Articulate and selectively implement windows application design and development strategies focusing on interactive systems.
• Analyze the target population of a proposed system and design effectively for those users.
• Design and evaluate a prototype graphical user interface (GUI) for an interactive system.
• Incorporate an object-oriented design strategy into your windows application development projects.

Fundamental Requirements

• A decision about the team you would like to be on. Normally teams will have between 3 and 5 individuals on them. If you would like to be on a team with 1 or 2 or more than 5, it is possible with justification. Include your justification in the project proposal.
• The choice of a problem domain with a significant degree of complexity for windows application development
• Unless otherwise arranged, it should utilize Bill Venners' Design Techniques see http://www.javaworld.com/javaworld/jw-02-1998/jw-02-techniques_p.html
• A completed analysis for the problem domain to ensure the design centers on the interactivity between the application and its user
• A completed user interface (UI) design appropriate to the analysis that utilizes appropriate design features
• An application prototype of the UI
• Successfully complete one iteration of development and test
• Requires blending the work of each individual on the team

High Level Schedule

Week 1 - Choices

Choose:

• Team (3, 4, or 5)
• Roles on the team
• Development methodology
• Project--Windows Client for VB application or ....

Week 2 & 3 - Requirements and Problem Domain Analysis

Identify requirements for your project and begin analysis

Week 4 - Design, Prototype Code, and Test

Complete the design, code prototype, and begin testing

Week 5 - Implement--Code, Test

Complete the coding and testing.

Week 6 - Integrate and Test your Code

Put it all together and test it out.

Week 7 & 8 - Refine, Fix, and Present

Refine your code after the integration test. Present your project to the class.

Week 9 - - Finalize, Package, and Hand-in

Hand in the report and diskette(s).

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, object descriptions, class descriptions, usability lab reports, 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 analysis to make it fit with Venner's approach, a working prototype for a significant segment of the UI and application, has implemented windowing interactivity, and has done some testing.

For an A

The team completes what is described above and implements a reasoned, and disciplined design. The design should encompass requirements, good principles of design, have a good user interface, incorporate design for good windowing interactivity, have good ease of use and learning, and be well tested. The project personnel should work together well as a team, and teach each other tips and techniques.