Week 5 in Review

Tasks Accomplished

This week we successfully completed our first draft of our Software Requirements Specification document. Additionally, we conducted an interview of our stakeholder and reviewed our Vision and Scope and SRS documents with them to ensure we were on the right track. Mike and Wayne conducted the majority of the interview -Jeremy joined in for the second half of it. In the SRS, Wayne worked on sections 3 and 6, Mike worked on sections 1 and 4, Damas worked on section 5, Jeremy worked on section 2, and Drew helped on sub-section 1.1. Mike and Wayne reviewed the document and worked on the Use Cases and Stereotype class models. Mike and Damas worked on the sequence diagram, and Mike wrote the blog.

Week 6 Tasks

Modify the SRS draft based on feedback and finalize it for the deliverable.

Challenges

Our main challenge was completing the SRS draft before the deadline, and team communication.

Week 4 in Reveiw

Tasks Accomplished

This week we've started to draft out SRS document. We've each taken it upon ourselves to oversee the drafting of one section of the SRS. We all contributed to the entire document while drafting it.

Week 5 Tasks

• Review the initial SRS draft
• Continue working on the SRS draft until full completion, revisiting and retouching individual sections as needed, and filling in empty sections.

Challenges

It may be a challenge completing a suitable amount of the SRS draft and reviewing it before the coming deliverable due date.

Week 3 Status Report

Tasks Accomplished

This week we held two group meetings in which we discussed our vision and scope for the project. In our first meeting, all team members participated in formulating a risk management plan draft. We also spent time creating an initial draft of our vision and scope document. Lastly, we created a template for our defect log. In our second meeting, we focused on creating a final vision and scope document. All team members worked towards completing this document. Wayne, Drew, and Jeremy finalized the requirements risk management plan, and schedule. Lastly, Mike wrote the weekly status report.

Week 4 Tasks

• Review any feedback on the Vision and Scope Document, all team members will discuss this for approximately 30 minutes
• Review SRS template, all team members should do this in no more than 20 minutes
• Begin working on initial SRS draft, all team members should participate for 2 hours

Challenges

We've identified several requirements risks which could occur gathering requirements for the product. It will be a challenge to adhere tightly to our risk management plan and perform the proper mitigations to avoid these risks.

Week 2 Status Report

Tasks Accomplished

We solidified a project sponsor which took Mike, Wayne, and Damas an hour to accomplish. With this, we also have a project idea. The project is a website which manages Air Force ROTC Detachment 538. The website should be able to manage all of the cadets (users) in the wing, as well as schedule Leadership Laboratories and Physical Training. It should also keep track of cadets' attendance and common reference resources (such as  the code of conduct, the honor code, etc.). The website will be written using a combination of PHP and JavaScript. This was decided by Damas, Wayne, and Mike in one hour.

Terminology

• Cadets - students at the Detachment (users)
• Wing - the top-level structure of the Detachment (All Cadets belong to the Wing)

Week 3 Tasks

• Vision and Scope Document, All team members will take 2 hours to complete.
• Week 3 Status Report, All team members will take 20 minutes to complete.

Challenges

We will have to learn different terminology and quite a bit of domain knowledge to understand the system and its requirements. This may not be a quick process, taking more time than we expect. The website will also be written in PHP, which can at times be a difficult language to understand.