CS Graduate Human Factors--Final Project Requirements
Richard Halstead-Nussloch, Ph.D.
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 cognitive, perceptual, and ergonomic
issues faced within the computer industry., e.g., usability, ease
of learning, ease of use, user comfort, interaction styles, etc.
- State major limits on human capabilities pertinent to computing
and the major implications of these limits for computer and software
design.
- Articulate and selectively implement design strategies and
principles for the user interface, focusing on interactive systems.
- Incorporate human factors and ergonomics into computer software
development projects.
- Analyze the target population of a proposed system and design
effectively for those users.
- Design a prototype graphical user interface (GUI) for an interactive
system.
- Evaluate the graphical user interface (GUI) using the Usability
Lab.
- Incorporate human factors and ergonomics into computer software
development projects.
Fundamental Requirements
- The choice of a problem domain with a significant degree of
human factors complexity
- A completed user analysis for the problem domain
- A completed user interface (UI) design appropriate to the
user analysis that utilizes user-centered 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 2 & 3 - Choices
Choose:
- Team (3, 4, or 5)
- Roles on the team
- Development methodology
- Project--Windows Client for VB application, Web, or ....
Week 4 & 5 - Requirements and User Analysis
Identify requirements for your project and begin a user analysis
Week 6 & 7 - Design, Code, and Test
Complete the design, code prototype, and begin testing
Week 8 & 9 - Code, Test, Present, and Report
Complete the coding and testing. Present your project to the
class.
Week 10 - Finalize, Package, and Hand-in
Hand in the report and diskette(s) before taking
the final exam.
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, 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
user analysis, a working prototype for a significant segment of
the UI and application, and has done some usability testing.
For an A
The team completes what is described above and implements a reasoned,
and disciplined user-centered design. The design should encompass
user requirements, good principles of design, have a good user
interface, incorporate design for ease of use and learning, and
be well tested for usability and coding. The project personnel
should work together well as a team, and teach each other tips
and techniques.