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.

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.

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.

Status Report for Week 5

During this week's meeting on Thursday, September 24th, the team used the WAAD and requirements list created from last week to decide the five most significant tasks users will perform within the QuickVitals application.

With each of the five tasks decided, the team them proceeded to discuss what the sub-tasks the user needs to accomplish and in what order to accomplish the major task. Once all the tasks and sub-tasks had been discussed, the team came up with plans, or alternate workflows for the various devised tasks.

During the next week couple weeks the team will transition from modeling the user interaction for QuickVitals to creating initial concepts for the actual design of the application's UI. The next coming week could cause some scheduling problems for our members due to the career fair happening next Wednesday, September 30th. These possible scheduling problems could potentially hamper productivity in relation to QuickVitals.

Status Report for Week 4

During the meeting on 9/17/15, each team member went through interview notes and synthesized work activity notes from the interviews performed by the team. As a team member finished what they thought was a good collection of work activity notes, they posted their post it notes on the board.

From all of these notes, we determined which notes there were duplicates of other notes and removed them from the discussion. As we went through the remaining notes, we started creating a WAAD, sorting out which activity notes belong and which ones don't. Once the WAAD was created, we went note by note through the WAAD and came up with design requirements.

We also found some usability requirements using MULES. Taking the design and usability requirements, we filled out the requirements template. This process took us 4 hours to complete as a team.

Over the next 2 weeks, we will be creating design models and a conceptual and intermediate design. Exams and midterms approaching quickly so team members may have other priorities in the mix as well, but that shouldn't affect our weekly meeting time. Interview day for the career fair is on Thursday, Sept. 31, however, so if any team members get any interviews scheduled that day from the career fair, they may be missing from the team meeting that week.

Status report for Week 3

During the meeting on 9/10/15, we worked for 2 hours completing the system concept statement and creating a set of interview questions.

Individually between meetings, we interviewed a total of 4 medical professionals and 1 patient for the contextual inquiry and uploaded our notes to Google Drive.

During the meeting on 9/13/15, we worked for 2 hours on the Interactive Design Requirements document. We worked on consolidating the collected interview notes. The organized notes were analyzed by the team and summarized into bullet points and sentences found in the interview/observation notes of the design requirements. Work roles were completed based on the analysis of the interview answers. The work flow diagram was also completed based on the system concept statement follow up with some interview’s comments.

Next week we will work on creating a Work Activity Affinity Diagram, and use this to establish requirements. After that will be design modeling. We do not foresee any issues in the next two weeks.

Status Report for Week 2

During the meeting on 9/3/15 each team member brainstormed an idea and had a two hour discussion to determine the best three to put up for candidacy, listed from most favored to least favored. Surprisingly, the third idea was decided to be the project to work on. This idea is intended to display vitals of patients in a hospital so nurses or anyone monitoring the patient can easily access and see the statuses.

Currently the team is putting in effort to find four users who are familiar with the medical field, most ideally nurses as that is the target user of this project. Everyone will take part in attempting to find users. 

Once we have recruited four users, we plan to interview those them about their user story. Using these stories, we will organize the notes and form work activity notes. On the side, we plan to discuss and determine the libraries and frameworks the team will use in the prototype.

One potential issue is that we may not be able to find any users to assist in our project. It may be a challenge to travel to hospitals and speak with members who are willing to assist us. This is especially true for those who do not have cars. In that case, team members may need to group together to seek out users.