Sunday, October 25, 2015
Status Report for Week 9
As of 10/25/15, the team completed heuristic evaluations during class time, with the help of two participants from another team. These evaluations revealed several potential issues, especially around "Flexibility and Ease of Use" and "Consistency and Standards". During the meeting on Thursday, the team discussed the issues and came up with several possible solutions. The team also created a basic framework for their prototype, using the Rails web framework.
In the coming weeks, the team will further refine the design (taking the results of the heuristic evaluation into consideration) and will continue building the prototype.
Sunday, October 18, 2015
Status Report for Week 8
As of 10/18/15, the team created the detailed designs of the app. The process involved considering the critiques from the user walkthroughs. We redesigned the wireframes incorporating the users' evaluation. Once the redesigns were done, the detailed wireframes were conceptualized and documented. Much of the feedback contained concerns with ease of use ans convenience of the user interface.
Friday, October 9, 2015
Status Report for Week 7
On October 6th the team started to work on building the first versions of the wireframe based on the sketches and storyboards made from previous meetings. Many considerations and minor changes were made as we walk through each tasks while building the wire frame. This resulted in the wireframe looking slightly different from the sketch. The GitHub repository was also set up to provide a skeleton in prototyping the interface.
Our next meeting was October 8th. The wireframe was modified based on constructive feedback from October 7th.'s activities. The HTA was also added/modified. Many of these changes/modifications weren't considered prior to making the wireframe. A preliminary programmed prototype of the interface was constructed.
The team will continue to work on the web interface in the upcoming weeks. The wireframes would be modified again based on the feedback from October 9th's activities. One of our concerns is that there would be no more peer evaluations for our wireframes.
Our next meeting was October 8th. The wireframe was modified based on constructive feedback from October 7th.'s activities. The HTA was also added/modified. Many of these changes/modifications weren't considered prior to making the wireframe. A preliminary programmed prototype of the interface was constructed.
The team will continue to work on the web interface in the upcoming weeks. The wireframes would be modified again based on the feedback from October 9th's activities. One of our concerns is that there would be no more peer evaluations for our wireframes.
Sunday, October 4, 2015
Status Report for Week 6
On October 1st, the met for two hours to begin work on the interactive design of Quick Vitals. The team created a sample user persona, and conceptualized the user interface through sketches and storyboards.
The team was not able to complete all the design-related tasks during the October 1st meeting, and will be meeting again on October 6th to complete the mental models and metaphors, and wireframes.
In the coming week, the team will refine the design and perform a cognitive walkthrough which will provide feedback for a more detailed design. The detailed design will be translated into a wireframe prototype. One potential risk related to this activity is creating a design that is too difficult to implement for the final prototype.
The team was not able to complete all the design-related tasks during the October 1st meeting, and will be meeting again on October 6th to complete the mental models and metaphors, and wireframes.
In the coming week, the team will refine the design and perform a cognitive walkthrough which will provide feedback for a more detailed design. The detailed design will be translated into a wireframe prototype. One potential risk related to this activity is creating a design that is too difficult to implement for the final prototype.
Subscribe to:
Posts (Atom)