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.