| Team Pandora | ||
| Date | Progress | Comments |
| 2005/04/07 | Proposals: No adjustments have been made to the proposals
since the last team lead meeting. SOW: Completed CONOPS: Obtained customer sign-off 03/18. SRS: Obtained customer sign-off 03/18. Architectural documents: We've had a lot of work done on the Architecture Description Document (ADD), which was used in preparation for last week's ATAM with Tony and Mel. We are currently heavy into the low-level design and hope to have a completed low-level design (public interfaces and classes) in Rational Rose completed by the end of the month. Process definition: We've written a draft of a Subcontract Management Plan for our intern. We've also each completed a requirements post-mortem questionnaire that will be used as a basis for a prose version of a requirements post-mortem. SPMP: Still need to pull all the docs together and write some prose that could help us describe the project to a newcomer who needed to get up to speed ASAP. |
Major status:
|
| 2005/03/24 | Proposals: We reviewed the proposals, and they are fine for
now, but we need to start some of the reflection pieces. Also, the only
thing that we siad we'd do that we're not is Pert charts. I'm working
with Mel on some ideas as to how I can make that happen. SOW: Completed CONOPS: We added some more scenarios for the customer, and she has signed off on it. SRS: We received sign-off from the customer last Friday. Architectural documents: All high-level views complete. We are currently working on the Architecture Description Document (ADD) in preparation for an ATAM with Tony next week. The low-level design work has been distributed to the team and has begun. Process definition: We've done a lot on the V&V plan, QA plan, and Metrics plan. We've also started time collection and task breakdown analysis as a team. SPMP: Need to pull all the docs together and write some prose that could help us describe the project to a newcomer who needed to get up to speed ASAP. |
Major status:
|
| 2005/03/04 | Mid of Semester Presentation. | See slides. |
| 2005/02/16 | Proposals: We are conducting a proposal review this week and
will plan on updating them the following week as needed. CONOPS: Second draft accepted and being reviewed by customer. Initial reaction was positive. We are shooting for sign-off next week. SRS: Minor adjustments added, but the document is essentially complete. We expect customer sing-off next week. Architectural documents: High-level module view and deployment view complete. Concurrency view is in progress. We are currently discussing the timeframe for an ATAM. Process definition: Requirements postmortem is underway - we have a questionnaire that we will complete upon sign-off of the SRS. We are also reviewing roles within the team to better document what our responsibilities really are. SPMP: This coming week begins the start of the V&V doc and the Metrics Collection doc. |
In general, we're doing 3 things: 1. Finishing up the high-level arhictecture and discussing ATAM 2. Reviewing old documents and roles for completeness 3. Finishing up process documents as part of the SPMP |
| 2005/02/03 |
Proposal: Done. SOW: Done. CONOPS: Initial draft was not what the customer was looking for. We are currently reworking the draft based on her comments. Plan for next draft next week. SRS: Final draft in customer's hands, but she will not sign-off on the SRS until she has a CONOPS she is happy with. Architectural documents: Working the high-level architecture diagrams now. We plan on having draft versions of the module, concurrency, and deployment views next week. Process definition: No additional process definition efforts at this time, but we will soon be working on our requirements postmortem which will act as a "Lessons learned" document for future endeavors. SPMP: Will be finalized later this semester as we get closer to the coding phase. |
Our schedule currently hasing us focusing on two things: First, we are completing the requirements phase with the completion of the CONOPS and the SRS. Second, we are working to our high-level architectural design. The plan is to have the high-level design complete by the 17th of this month with our first ATAM to follow the week of the 21st. |
| Team Phoenix | ||
| Date | Progress | Comments |
| 2005/04/07 | Proposal: Done SOW: Done CONOPS: N/A SRS: Waiting for getting approvals from clients. Architectural documents: Wrote draft documents and now reviewing. Process definition: N/A |
So far, the team has achieved five of 11 milestones. M0:Project plan (1/21) M1. Approved SRS v2.0 (2/18) M2. Agreed scope with clients (2/28) M9. MOSP completed (3/4) M3. Finished notional architecture (2/28) |
| 2005/03/24 | Proposals:
We had reflection team meeting and updated Proposals before
MOSP SOW: Done. Got the signatures from clients last semester SRS: The team is now reviewing the SRS. It will be finalized this week. Technical writer will start to review the SRS document. Architectural document: We created draft of software architecture and reviewed with clients several times. We will work on documenting software architecture. Process definition: The detail process is already defined. The process manager tries to verify it and will audit the process periodically. SPMP: Haven't updated yet* |
* The original SPMP is too long and voluminous, so the team will try to make new SPMP simple and brief. |
| 2005/03/04 | Mid of Semester Presentation. | See slides. |
| 2005/02/17 | Proposals: Finished to update proposals and handed them to
mentors SOW: DONE SRS: Feature list to clarify the requirements and to discuss the scope that what we should do. SRS will be refined and updated during this weekend. The estimation and scope of requirements will be started from this week. Architectural document: We're behind schedule. We should have started to draw notional architecture from last week. It will start from this week. Process definition: NONE SPMP: NONE |
Proposals: All reflections during the project will be written into
the WIKI server. Next updated proposals will be delivered in April. SRS: As a means to draw requirement, we are using paper prototyping techinique |
| 2005/02/03 | Proposals: Finished to update the 1st version of proposals * SOW: Done. Got the signatures from clients last semester SRS: The team started to review the draft of SRS and refined the quality attributes. Technical writer started to review the SRS document. Architectural document: Not started. Process definition: The detail process are already defined. The process manager tries to verify it and will audit the process periodically. SPMP: Haven't updated yet ** |
* The team will update three times during this semester. ** The team will start updating the SPMP document from Feb 21st. |
| Team Salsa! | ||
| Date | Progress | Comments |
| 2005/03/24 | Proposal: No formal changes to proposals but we have
started reflecting on our adherence to them.
We need to do some updating of the Design and Implementation
proposals soon as those activities are either ongoing or coming
up soon. SOW: Signed CONOPS: n/a SRS: I'd estimate at ¾ done. I'm meeting with Gabe (our requirements engineer) after this meeting to do some planning and assessment on the SRS so I'll know better then. Architectural documents: We are making progress on this and it is the main focus of our work right now. We are concentrating on the C&C views although we should put together a deployment view soon. We have a fairly large set of experiments/research that we are working on to solve some questions that we have uncovered during our architectural reviews. Process definition: Again, we are only defining processes on an “as needed” basis. Lately we have been working on better processes for team status reporting and reflections. SPMP: N/A |
We are behind on our plan but it is the mentor's opinion that this is due to our overly ambitious plan and not any real fault of our implementing it |
| 2005/03/04 | Mid of Semester Presentation. | See slides. |
| 2005/02/03 | Proposals: Still two approved, three need work, no progress SOW: Done and signed! SRS: Progressing probably 60% done. We are in the process of picking an (HW) Architectural Definition Language which is the centerpiece of our SRS. Architectural document: We have a very early notion architecture but no analysis yet. Process definition: No progress but it is on my short list. |
|
| Team Sapphire | ||
| Date | Progress | Comments |
| 2005/04/07 |
Proposal: All proposals are in a stable state. No
changes for this cycle. SOW: Stable. May need to be reviewed for summer due to possible new type of work. Will be discussing this with customer on Friday. CONOPS: N/A SRS: Supplied by customer. Will be used for implementation in ER4 release due April 22nd. Architectural documents: Need to be reviewed and documented properly. Process definition: Currently defining QA and code integration processes for team and other global teams to use SPMP: Using planning proposal. |
|
| 2005/03/24 | Proposal: Stable. Will be revised in next 4 weeks. SOW: Complete and signed. CONOPS: N/A SRS: Supplied by customer and revised by team. Architectural documents: Done and now undergoing revision as more information is acquired Process definition: We are currently researching to define our Quality Assurance and Code Integration processes. SPMP: N/A |
Team is currently in planning cycle 7. We just completed cycle 6 where we made our first major code delivery to the customer. We encouontered many unexpected problems while doing the integration and are now reflecting on what went wrong and what we need to improve for the next time. |
| 2005/03/04 | Mid of Semester Presentation. | See slides. |
| 2005/02/17 | Proposals: All proposals have been reviewed and updated as
necessary. Will be reviewed again during current planning cycle. SOW: currently at version 2.0 to reflect change in team members. It will be updated again to reflect a change in work that has come from customer SRS: currently on our wiki but not in a normal formalized format. Our domain model is one of our main deliverables where we create an SRS of sorts to define what it needs to accommodate. The SRS for our implementation is provided by the customer and reviewed by us before it is formally used for implementation. Architectural document: This is in the form of our domain model, C&C, Module, and allocation views we have for our implementation. Process definition: We have adapted and customized RUP to work for us. We are using RUP to help us define our tasks and know what artifacts we should be producing. Our short cycles make for a very interesting use of RUP and we are currently keeping this in mind when we do our reflections. SPMP: does not exist formally yet. I am using the planning proposal to help define this. |
|
| 2005/02/03 | Proposals: Design (v2.0 draft), Implementation (v2.0 draft),
Operation (v2.0 draft), Problem Definition (v2.0 draft), Planning (v2.0
draft) SOW: (v2.0 draft) SRS: n/a Architectural document: Under revision Process definition: Complete. Next revision in process SPMP: n/a |
We are currently in the final stage of our ER2 release for Feb 15th. This release will not be as complete as we wished due to a slow start to the semester. There were several reasons but I will detail them later. |
| Team SOCS | ||
| Date | Progress | Comments |
| No progress review was done | ||