| Ryan Hollister Alphonce Tumuna |  |
Purpose The purpose of this webpage is to outline and document our progress through D term 2007 in CS3041. This webpage will provide the visitor with up to date information regarding our HCI project. In addition to the progress the visitor will be able to view past iterations of the design. During the course our project will undergo continuous refinements. Project We would like to build a system that allows people to perform most of the tasks a hospital offers only ours will be virtual and accessible anywhere there is internet access. We would like to implement basic tasks such as scheduling, calling 911, and updating of personal information. Other aspects of the system are more ambitious. We would also like to see video conferencing with doctors, virtual surgeries, and ability to perform various tests from the comfort of the patient’s home.
Assignments
Portfolio Assignment 1 (64/100) : A. what are the functionalities you will add to your component? B. Mention your refinement list? C. List according to importance i) Functionalities, and ii) Refinements, for your Component.
Portfolio Assignment 2 (80/100) : The focus for this submission should be requirements gathering- including user, domain, task, and environment analysis. Please refer to textbook chapters 2, 3, 4, 5,and 6 for a clearer understanding.
Portfolio Assignment 3 (84/100) : The focus for this submission should be conceptual design and interaction design process. You are expected to do concept diagram and enhance your requirements specs. You can come up with a style guide. You can make use of mock-ups or prototypes as well.
Portfolio Assignment 4 (85/100) : This submission includes the first working prototype of our system. The guts of the system are mostly there but the final configuration of the interface still needs to be tweeked. "Perform Tests" portion of the system is still lacking.
Portfolio Assignment 5 (67/100) : This prototype now contains all the "guts" of the system. The interface still needs tweeking but "Perform Tests" is now complete. Audible cues have been added to various portions of the system.
Portfolio Assignment 6 (90/100) : In this assignment we have brought our prototype one step closer to meeting all the requirements in our document. We have also given numerous evaluations to people and asked for thier responses back. Below in the reference section you will find the survey with various helpful answers that we recieved.
Portfolio Assignment 7 (FINAL) : This is the final prototype that we will develope. It presents all the features that we wished to incorporate into the product. It also contains a screen by screen critique of our system. This is of course not a finished product but only our final prototype.
Notes
Notes 1 (Ryan): Characteristics that need to be investigated for the user, task, and domain of the application. Also outlines the Requirements Specification.
Notes 2 (Ryan): Four steps to a cognative walkthrough. Notes from meeting with other groups. Enviromental issues and a user's mental model outline.
Notes 3 (Ryan): Mental model (cont.). Design principles and Gestalt's Principles.
Notes 4 (Ryan): Personal experience principles and notes from group meeting about Requirements Specification.
Notes 5 (Alphonce): Requirements gathering
Notes 6 (Alphonce): User characteristics.
Notes 7 (Ryan): Prototyping and Conceptual design notes.
Notes 8 (Ryan): Principle and rules. Notes from group meeting regarding prototype evaluation.
Notes 9 (Alphonce): Interaction design example of a cell phone user interface.
Notes 10 (Ryan): Interface design styles. Mainly notes about form fillin and direct manipulation.
Notes 11 (Ryan): Continuation of interface design sytle notes that include natural language interface. Overview of interactive devices followed by notes taken during the inclass group meeting.
Notes 12 (Ryan): Text, Images, Sound and Layout Notes.
Notes 13 (Ryan): Midterm Exam review topics.
Notes 14 (Ryan): Web Page Design, Embedded Systems and Group critique of WPI.edu.
Notes 15 (Ryan): Evaluation and Inclass activity.
Notes 16 (Ryan): What tasks are best handled by humans and which best by computers? In class group activity.
Interface Iterations
Iteration 1 (03/26/2007): This first sample interface shows the main page. On the main page the user will be able to call 911 and login to account. At this point nothing else will be accessible since all their information will be protected.
Iteration 2 (03/27/2007): This iteration is a mock up of the personal information entry page. This page will allow people to update and change their information.
Iteration 3 (04/01/2007): Changes made to information entry page based on recommendations recieved in class from Carey Edlund and Matt Duval.
Iteration 4 (04/08/2007): This is the first working prototype. It is a Visual Basic for Applications program. Download the document and press the button. Make sure that macros are enabled.
Iteration 5 (04/13/2007): This is a slight modification of the prototype. It now contains all functions originall desired. The actual interface needs tweeking. Some audible cues were added as well.
Iteration 6 (04/16/2007): This iteration is slightly different in that it has command buttons on the left of the screen. This allows for bigger and bolder fonts to be used for easier navigation. Also the "Call 911" button has been moved off the login page and onto the top so that it is present on every screen.
Iteration 7 (04/21/2007): This is our prototype further along in developement. We are much closer now to meeting all the design requirements layed out in the original assignment. We have decided to remove Virtual Surguries from our requirements list. We are still choosing between the two navigation styles and still collecting feedback for both.
References
Concept Diagram : This is the flow of the processes that our program will perform.
Color Chooser: This website is quite useful when choosing colors that work well together.
Style Guide: This is a link to a style guide which we will attempt to follow.
Design Guidelines: There are design guidelines as they are outlined in the book. We also discuss how each guideline is met with out program.
User Evaluation: We asked 5 people to sit down with the application and to answer this survey after, the better responses from all the surveys are entered into the document.
Design Requirements: These are the latest design requirements. (Updated 4/21/2007)