Friday, September 19, 2014

Week 4 Updates

This Week:

These past two weeks, our team has made a lot of progress on the project. Besides having our weekly team meeting as necessary, our team has completed a Software Requirements Specification, done Hierarchical Task Analysis, created prototypes, and started programming the application.

The Software Requirements Specification (SRS) contains a variety of project-relation information, including but not limited to an analysis of the domain problem and stakeholders, features, task analysis, and functional/nonfunctional requirements. The team divided the document for work, and completing the sections took a total of around 4 or 5 hours per person. 
In addition, a hierarchical task analysis (HTA) for system features was completed to be included in the SRS. These took around a half hour per person. 

As a final portion of the SRS, our team created a prototype during one of our weekly meetings. The wireframe shows the primary view, displayed when a user navigates to the site. You can see the prototype below contains a left panel for the user to select subjects and difficulty, a large upper-middle panel to display the current flash card problem, and a place to answer then submit the answer for validation. If we were afforded a chance to expand upon this concept in the future, we could consider a new design model that would allow users to modify difficulty for each selected subject. As of right now, however, that functionality would be out of scope and could be added as an extra feature later as time permits.
Finally, Zach has made the time to start up writing the application, and has made very significant progress on it.

Overall:
Task: SRS
People involved: All team members
Hours: 4-5 hrs per team member


Task: HTAs
People involved: All team members
Hours: 0.5 hr per team member

Task: Prototype
People involved: All team members
Hours: 1 hr per team member (working together during meeting)

Task: Start of Code Base
People involved: Zach
Hours: 4

Next Week:

In the coming week, we will be starting work on the Design Document and Conceptual Prototype for the project. We estimate very roughly that the design document will take 3 hours per team member, and the conceptual prototype will take 2 hours per member. We expect all members will be involved working on the two deliverables.

Challenges, Risks, and Issues:

Challenges: 

Our team had the challenge early in the project to coordinate a weekly team meeting time. Although we had to resort to meeting virtually on weekends and talking in person during/after classes, our team has adjusted very well to the unusual meeting schedule. Team members have been effective in efficiently completing deliverables.

Risks: 

There is a risk that as the semester progresses, team members may be unable to attend meetings or may fall behind on deliverables. To mitigate this, we have been attempting to start deliverables as soon as possible to allow for maximum time for completion.

Issues: 

[no significant issues encountered thus far]

No comments:

Post a Comment