Status Report for Week 15

Status Report for Week 15

Accomplishments

We completed the analysis of the user testing, and generated a consolidated list of usability issues and potential solutions. We created tasks to solve each of the major usability issues and divided them amongst the ourselves. We also created a slideshow that captures the evolution of the prototype and design process the team used.

Goals

Sometime during week 16 we will deliver our presentation and demonstrate our final prototype.

Status report for week 14

This week, we didn't have our weekly team meeting due to the Thanksgiving holiday, but we have assigned tasks to team members in order to improve the prototype based on the feedback from our testers. Several important changes have been noted and the results were partially analyzed and interpreted.

This upcoming week we'll finish our analysis and interpretation of the tester's data. The final changes will be made to the protoype. We would also be working our our presentation.

Status Report for Week 13

This week, we concluded our user testing by having another 6 potential users come in and test our prototype. The testing was complete by Thursday so we were able to start analyzing the data at the end of our weekly meeting and finish it up on Saturday. We found our last qualitative question "What would you change about this application if anything?" to give us the best feedback as it was an open ended question.

This upcoming week, we won't have our weekly team meeting due to the Thanksgiving holiday, but we will assign tasks to improve the prototype to each member to work on over the break. When we get back from the break, we will finalize our changes to the prototype and create our presentation.

Status Report for Week 12

This week was focused primarily on executing the test plan we had drafted in week 11. We ensured that all of our metrics were the ones we wanted. Once that was done we created a survey using Google forms to gather all of our Likert scale metrics. Our other metrics were gathered via direct observations. During our meeting last week, we were able to perform user testing on two users, with the members trying to perform testing on other users after the meeting.

Status Report for Week 11

As of 11/08/15, the team finished the test plan and programmed prototype. At least 3-5 people have been recruited for the beta testing. During our meeting for Thursday the test plan was worked on and elaborated. Different scales and values, expected results, and optimal results were added to the test plan.


Each questions that would be asked for the interview was evaluated to match the scaling of our question's measurement. After this was done we worked on the programmed prototype of our web application. Basic "template" was finished before our meeting on Thursday. On Sunday the more complicated features such as graphs, search, and css interface was implemented.


In the coming weeks the team will recruit more members for beta testing and further refine the web application before it is released for testing.

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.

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.

In the coming weeks, the team will attempt to recruit four more users for testing and refinement. Concurrently, the team will begin to divy up the programmable prototype workload and look into what technologies would be required to complete the assigned prototypes. After a scheduled short discussion on the decided technologies and sync up before fully going into development. This meetup can help other teammates with suggestions in case they are at a standstill.