I. Time Line

• Oct. 4: Start guidelines document (purpose and scope)
• Oct. 6: Complete guidelines document

Brainstorm a name for thesystem, device(s), and parts of the interfaces

• Oct. 11: Planning & research
• Oct. 18: analysis paper due (individual deadline)
• Oct. 25: Prototype in progress
• Nov. 1: Complete paper prototype
• Nov. 8: Revisions to working model
• Nov. 15: Revisions to working model
• Nov. 22: no class, research paper due (individual deadline)
• Nov. 29: no class, Thanksgiving weekend
• Dec. 6: Revisions to working model, preparation for presentation
• Dec. 13: Presentation

II. Analysis

TBDduring research

III. Labor & Tasks

• Research
• Define interaction style
• Define ergonomics limits
• What form will it take?
• Define privacy & security requirements
• Design appearance
• Prototype development
• Prevent errors (trouble shooting and casual testing)
• Create documentation template
• Documentation
• Final presentation (Power Point?)

IV. Deliverables

• Outline
• Guidelines document (purpose and scope)
• Research issues (individual papers)
• Analysis
• Paper prototype
• Presentation

V. Resources

• Computers
• Prototyping supplies
• Large format color printing
• Word (documentation template)
• Power Point (for presentation?)
• Illustrator
• Photoshop

VI. Research Issues

• Short-range networking (ie. Bluetooth)
• Biometrics (security, privacy)
• Ergonomics
• Form factors: size, shape; orientation; peripheral devices
• Does it have a touch screen?
• Does it have a keyboard?
• Would a keyboard work with it as a peripheral?
• Pause mode (interruptions, resuming use)
• How does the interface interact with non-users?
• How big is the screen?
• Can you operate it while driving?
• Limiting factors (children, individuals with disabilities)
• How many possible devices are used with this system?
• How does the functionality of the system differ between devices?
• How does the interface of the system differ between devices?
• What is the level/frequency of usage per day/week?

VII.Risks

• Absences by group members (time frames unavailable)
• Are we reinventing the wheel? (Does a similar interface already exist?)
• Does the interface “play nice” with other types of systems?
  (ie. phone, email, IM, calendar, GPS)
• What are the time limits/expectations? (ie. Ease of usability, learning; attention span of kids)
• Is the scope too broad? Too narrow?
• Does the interface involve unattainable technology?
• Social inhibition
• Is the interface cross-culture-friendly?
• Does it bring the family together or divide it?
• Research (Do we know enough?)
• Design: product reconfiguration (Is it mundane? Is it too innovative?)
• How do we best present this idea?
• Integration of ideas

VIII. Approach

TheFamily Manager Project Team is creating a collaborative application formanaging the complexities of family lives and schedules. In our design,different functions of the application will be organized into separate modules.The premise of this structure is that some parts of the application arelogically discrete entities, and that this pattern applies to functional use,some discrete features, and individualized interfaces. Naturally, the modulesare themselves part of a larger whole, and some functions, features, andinterfaces will be shared.

The modules of ourapplication will likely relate to one another as “hub-and-spokes” [of a wheel],so that one module will play a central organizing role. This modular conceptalso structures our division of labor, with one team member “owning” eachmodule, and this pattern will likely be followed through many design tasks,from requirements analysis, to prototyping, and ultimately to presentation.

ModuleBreakdown

Central Module – Ren Pope

Common functions, features, and interfaces

Use case: turn-on, install,hardware, devices

Home Module – Jill Ellis

Users,Tasks, Locations and Time Inside of the home

Use case: chores, daily tasks(dinner), time-shifting visualization

Outside Module – DavidPepper

Users,Tasks, Locations and Time Outside of the home

Use case: shopping,appointments, time-shifting visualization

Social Module – JanetLenzer

AccessPrivileges and Constraints between users

Use case: adding andsubtracting users, modeling relationships, changing privileges for users overtime

DesignMilestones

ApproachDocument: Ren Pope and David Pepper

Purposeand Scope: All

ResearchTopics: All (TBD)

Interface Design and Presentation

Central Module – RenPope
Home Module – Jill Ellis
Outside Module – David Pepper
Social Module – Janet Lenzer

Possible Design Media (across tasks):

Power Point
Conceptual diagrams to explain designwithout showing content (wireframes)
Demonstration prototypes
Visualizations and other diagrams toexplain key concepts

Presentation Templates and Graphic Design – Jill Ellis and Janet Lenzer