Week 14 in Review

Tasks Accomplished

This week we worked to finish our architecture. To do this we focused most of our efforts on reworking our Module View and creating a Component-and-connector view. We also worked on our presentation and prepared to do it next week.

Week 15 Tasks

Present our architecture.

Challenges

Many projects were coming to a close this weekend and so we had to increase our efforts to coordinate our work and schedule time.

Week 13 in Review

Tasks Accomplished

This week we focused on looking at our feedback from our architecture draft and making plans as to where we would like to expand and correct

Week 14 Tasks

Eat as much as possible without passing out. Also, we will start by making all changes per our review, then create new views for our architecture and update our module view.

Challenges

We learned at the end of week 13 that we lost a team member, so from here on out we will be 1 short.

Week 12 in Review

Tasks Accomplished

This week we completed our Architecture draft. All team members reviewed our architecture and updated it according to feedback. 

Week 13 Tasks

Add additional information as outlined in our schedule and complete our final architecture diagram.

Challenges

We faced little to no challenges this week.

Week 11 in Review

Tasks Accomplished

This week we completed our Architecture draft. Wayne worked on the high level architecture. Damas worked on the quality attributes section. Mike worked on the module view and Jeremy worked on the deployment view. Mike, Wayne, Damas, and Jeremy reviewed the draft document. Mike wrote the blog post.

Week 12 Tasks

Review our architecture, update it according to feedback, and add additional information.

Challenges

Many project due dates and exams have conflicted with scheduling of project work and coordination among the team, along with lack of communication in some parts of the team.

Week 10 in Review

Tasks Accomplished

This week we focused on the creation of views for our project architecture. Damas focused on Quality attributes. Wayne and Drew focused on our high level architectural views. Mike and Jeremy focused on our module view. Mike wrote the blog.

Week 11 Tasks

Address most if not all sections of our architecture document in order to submit a draft.

Challenges

Week 11 will bright unprecedented amounts of work which we will have to learn to cope with in order to make the final stretch of the semester.

Week 9 in Review

Tasks Accomplished

This week the entire team met to finish activities done in class and further familiarize and develop a plan for the project.

Week 9 Tasks

Continue progress on architectural specification. Have a rough rough rough draft complete.

Challenges

These week many team members had a lot of work to do, so we couldn't get as much done as we would have liked.

Week 8 in Review

Tasks Accomplished

This week we decided on a new project to take into the architecture phase, ScoreStream. During this week we decided on a project, created a new project plan to use for the architecture portion, and started filling out our software architecture document. Mike, Wayne, Damas, and Jeremy participated in this.

Week 9 Tasks

This next week we will continue familiarizing ourselves with the finer details of the project, and begin the first steps to making an architecture.

Challenges

We did not face any challenges this week.

Week 7 in Review

Tasks Accomplished

This week we completed our requirements engineering process for the project. More specifically, this week we focused on writing use cases. We also met with our sponsor to verify our requirements specification one last time before our requirements presentation. All team members took part in completing use cases, descriptions, class diagrams, and sequence diagrams. Damas, Mike, Wayne, and Jeremy met with our sponsor to verify Requirements. Mike wrote the blog.

Week 8 Tasks

This next week we will decide on whether or not to continue with this project into the architecture phase, or pick up a new project with predefined software requirements. We will then begin the initial steps of the architecture phase.

Challenges

Our big challenge this week was illness among group members. However, we all survived and managed to complete the work.

Week 6 in Review

Tasks Accomplished

This week we completed additional work towards the SRS. Wayne worked on implementing feedback from the SRS Draft, adding Actor Descriptions to the Use Case document, and adding more detailed use case descriptions. Mike worked on adding use cases for the Reference Materials package. Drew and Jeremy worked on adding use cases for the website management package. Lastly, Damas worked on adding use cases for the Cadet Tracking package.

Week 7 Tasks

Finalize the SRS document and supporting Use Cases.

Challenges

Our main challenge this week was finding the time to meet, and complete work because of the extra time taken up by the career fair and interviews for various team members.

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.