AbstractCreditsTable of ContentsIntroductionPresentation of DesignTransition DiagramScreen ShotsHelp ScreenTimeline / Calendar ViewDaily SummaryTask ViewNew Task DialogHelp / WalkthroughAdding a New TaskPrinting the Task ListCompleting the Task ListViewing HistoryDevelopment ProcessPost-test QuestionairePre-test QuestionaireUsability Tests and Analysis of ResultsIntroductionSubject ReportsSubject 1Subject 2Subject 3Subject 4Subject 5Summary of Usability Test ResultsEvaluation of Problems and SuggestionsUsability Test ConclusionsDevelopment ProcessPhase 3: ImplementationPhase 2: Layout DesignPhase 1: PreplanningLow-Fidelity PrototypePrototype Main ScreenPrototype Task ScreenPrototype New Task ScreenPrototype Information ScreenPrototype Daily SummaryConclusionFuture Work PossibilitiesFinal Status of ProjectAcknowledgementsReferenceskidSTART Interface Design Report December 7, 2004 Stephen Dicocco [email protected] David Handy [email protected] Dyami Jenkins [email protected] Lauren Smith [email protected] Parents attempting to follow the DIR/Floortime treatment plan for autistic spectrum disorders (ASD) have a huge amount of information to keep track of. DIR/Floortime is a new treatment plan for children with ASD that emphasizes an individualized, relationship based approach to treatment. A large number of daily tasks are prescribed for the child by the 3-7 clinicians working together to help the child. The kidSTART software attempts to help the parents keep track of all of the information related to the treatment of their child, and coordinate the many people involved in their child’s treatment. It is also designed to evaluate the effectiveness of different aspects of the program by maintaining a detailed history of the treatment process.Credits Stephen DiCocco • Windows testing for Java / SWT • Java Programming, embedding browser • User Needs Document: 1/3 user tasks • References Document: ¼ citations • First Design Document: Visual Studio models for the calendar view and navigation panel, task-centered walk-through section • Task List / Questionnaire Revision before Usability Test • Usability Testing • Usability Test Report Document • Final Report: development process section, future work possibilities section of conclusion David Handy • Java / SWT programming in Linux, CVS server setup • Help documentation inside the program • User Needs Document: introduction, system requirements sections, final formatting, proofreading and submission • References Document: ¼ citations, final formatting, proofreading and submission • First Design Document: Visual Studio models for the task view, new task, and daily summary interfaces, final formatting, proofreading and submission • Final Report: final status section of conclusion, transition diagram, proofreading Dyami Jenkins • Flash Programming: Timeline / Calendar visualization • User Needs Document: 1/3; user tasks • References Document: ¼ citations • First Design Document: web-based interface models for calendar, task list • Task List / Questionnaires Document: first version and submission • Final Report: web page design and formatting, introduction, presentation of design Lauren Smith • Flash Programming: Timeline / Calendar • User Needs Document: 1/3; user tasks • References Document: ¼ citations • First Design Document: Strengths / Weaknesses section • Final Report: introduction, presentation of designTable of Contents 1. Introduction.................................................................................................................5 2. Presentation of Design ................................................................................................ 7 2.1. Transition Diagram ............................................................................................. 7 2.2. Screen Shots........................................................................................................ 8 2.2.1. New Task Dialog ........................................................................................ 8 2.2.2. Task View ................................................................................................... 9 2.2.3. Daily Summary ......................................................................................... 10 2.2.4. Timeline / Calendar View......................................................................... 11 2.2.5. Help Screen............................................................................................... 12 2.3. Help / Walkthrough........................................................................................... 12 2.3.1. Adding a New Task .................................................................................. 12 2.3.2. Printing the Task List................................................................................ 13 2.3.3. Completing the Task List.......................................................................... 13 2.3.4. Viewing the History.................................................................................. 13 3. Development Process................................................................................................ 13 3.1. Low-Fidelity Prototype..................................................................................... 13 3.1.1. Prototype Main Screen.............................................................................. 14 3.1.2. Prototype Task Screen .............................................................................. 15 3.1.3. Prototype New Task Screen...................................................................... 16 3.1.4. Prototype Information page ...................................................................... 17 3.1.5. Prototype Daily Summary......................................................................... 18 3.2. Development Process........................................................................................ 18 3.2.1. Phase 1: Preplanning................................................................................. 18 3.2.2. Phase 2: Layout Design ............................................................................ 20 3.2.3. Phase 3: Implementation........................................................................... 20 3.3. Usability Tests and Analysis of