Tuesday, March 27, 2007

Final Project Phase 3

Our presentation for phase 3 actually covers some areas from the previous phases, particularly on the part of Requirements Specifications.
Need Analysis finalization

We developed 9 personas, and we managed to derive the following needs to be fulfilled by our target user.
  • A simple, easy to use interface to get all info
  • Accessibility of the information
  • Manipulability (freedom to construct any kind of knowledge with the Data)
  • Usability (Functional)
Content
For the content of our product, we further investigated a list of feature requirements, based on the interviews and survey:
What the School Provides
Student's Requirements
Module Name and Description
Categorization into Course Requirements
Each Semester's Schedule & Exam Time
Time Table Builder, Scheduler, Bidding Management
Graduation Requirements
Graduation Requirement Tracking, Modules taken Listing
Structure of Assessments
Grade Simulator, Current CAP or Accumulative point
Announcements
Messaging tools (Email, Forums)


Card Sorting and Information Architecture

Experience Strategy

Design Element
What The personas Say
Possible Design Strategy
Visual (Sensorial Design)
icon sleek, clean, aesthetically pleasing
Functional, simplicity
Visual (Sensorial Design)
Intuitive interface, minimal instructions
icons with simple action words
[ie Track/Check, Forecast]
Information Architecture
no information overload; no cram functions
Use words, links and graphics only when necessary, avoid clutter
Interaction Design
Personalization
icons to create their own individual space;
customised user space
Interaction Design
Fluidity
employ a drag and drop interface.