Documents
We've got that covered.
 |
Home | Project Overview | People | Process | Planning | Prototypes | Documentation | Task Tracker |
|
Weekly Reports |
|
12-19-03 |
Summary
- We have had on average about two meetings per week they all have been productive. But we decided in one of our latest meetings that all of us (with the exception of Bill) need to start putting more effort into the project. We should each be putting in approximately 15 hrs/week and we’re currently under that estimate. Our goal is to increase our total project effort, evenly distribute our tasks and ensure everyone is putting in the same amount of effort.
- We have developed baseline planning (both long-term and short-term) and process documents (general practices and specific cycle steps). They have been sent to Chad (client) and to Professor Hilburn for review. We have reviewed these documents as a team.
- We feel that the J2EE environment setup will take a lot of effort so we will be beginning this effort over break. Brian is currently heading up this task.
- We have decided to setup Issue Tracker which will keep track of our current tasks and keep the team (and other interested parties) up to date about the status of these tasks. Our Issue Tracker (developed by Doug) will also be responsible for bug tracking.
- Besides our website, we have decided to not use the SE machines for project and instead, use external machines (mostly Bill’s and Brian’s computers). We feel we have more control over these machines and they are accessible to everyone.
- Our short term plan has an initial list of items to be done. Every item has someone responsible for the task and dates have been assigned where applicable. This will ensure task efficiency once we return from break.
- Our initial approach of the first cycle will concentrate on the plug-ins for extensibility. We feel these will be crucial to a successful project and are going to begin attacking this topic early on.
- Elicitation meeting with AFRL planned (although not confirmed) for Jan 7th. Between now and then are team will be developing elicitation questions for that meeting.
Upcoming activities
- Research of J2EE
|
1-9-04 |
Summary
- We have begun using Issue Tracker as a means of tracking the status of our weekly tasks. It can be found at: http://walltowall.homedns.org/issuetracker/toDoList.php
- Our initial Java development environment using Ant and Jetty has been setup, but we may be changing to Apache/Tomcat. We are awaiting information from Chad for a decision of which environment we will use.
- We discussed an initial possible architecture for this system and developed several elicitation questions based on this discussion.
- Our team held an elicitation meeting with Chad and Jeremy from AFRL. Greg, Bill and Brian attended the meeting while Doug and Travis will provide an “outsiders” point of view on the requirements. Now that some initial requirements have been elicited a draft requirements document is being produced.
- After reviewing the proposed contents of our “Vision and Scope” document we have decided to, instead, integrate portions of this document into our Kickoff document and our Requirements document. We decided against a separate document because we didn’t want to maintain the same information in several documents.
Upcoming activities
- Review of AFRL-commented documents and replying to any outstanding issues found in those documents.
- Our latest documents will soon be available and maintained on our team website found at: http://www.se.rit.edu/~w2wsw
- Research of plug-in techniques to be used in Java
- Initial requirements documentation
|
1-16-04 |
Summary
- Project planning was discussed between Professor Hilburn and the team. We made several changes based on his suggestions:
- Project Planning worksheet was devised to plan out the major deliverables and tasks for all 3 cycles (with the last 2 cycles having very rough estimates)
- Major cycle 1 tasks were taken from this worksheet and entered into the Task Tracker (renamed from Issue Tracker) as “major tasks”
- Task Tracker now has separate views for major and minor tasks. The major task view will serve as our reference for planning.
- Dynamic code loading (to be used for plug-ins) has been researched by Bill and appears to be technically feasible.
- Based on Chad’s comments to our Kickoff document, and additional information we found to be important, we have created a Vision and Scope document which will act as our finalized Kickoff document.
- We have decided to use Apache as the Web server for our project. This was decided because AFRL’s environment is currently using Apache and there were no additional risks discovered from using Apache.
- Product Architecture has been discussed further and we are continuing to make progress on this.
Upcoming activities
- Initial Requirement documentation will be completed and inspected in the upcoming week