Project Name: Online Health Monitoring System

Team Web site: link

Web Pages for Other Team Members:

• Jon Carelli - email - page
• Chris McCue - email - page
• Chris Chffin - email - page
• Ethan Pitts - email - page
• David Gundler - email - page
• James Luke - email - page

Contents of this Document

Individual Weekly Time and Activity Log:

Week 14:

Overall status this week:

• Navigation fully integrated.

Progress this week:

• Code page layout/navigation - 4 hours (10% for total of 100%)
• User manual writing/compilation - 4 hours (100% for total of 100%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• No notes for this week.

Week 13:

Overall status this week:

• Working on getting the navigation running with the server.

Progress this week:

• Code page layout/navigation - 3 hours (10% for total of 90%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• No notes for this week.

Week 12:

Overall status this week:

• Worked on the navigation functionality.

Progress this week:

• Code page layout/navigation - 1 hours (0% for total of 80%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• Need to start interacting with the database.

Week 11:

Overall status this week:

• Worked on the navigation functionality.

Progress this week:

• Code page layout/navigation - 1 hours (5% for total of 80%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• We decided on separate style sheet and JavaScript imports with each module.

Week 10:

Overall status this week:

• Worked on the navigation functionality.

Progress this week:

• Code page layout/navigation - 2 hours (10% for total of 75%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• I was able to get the main functionality working, but I have to decide with the team how we are going to handle style sheet imports.

Week 9:

Overall status this week:

• Worked on the navigation functionality.

Progress this week:

• Code page layout/navigation - 3 hours (40% for total of 65%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• No notes.

Week 8:

Overall status this week:

• Worked on the detailed design.

Progress this week:

• Code page layout/navigation - 0 hours (0% for total of 25%)
• Detailed design for navigation module - 5 hours (100% for total of 100%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• No notes this week.

Week 7:

Overall status this week:

• Completed some of the main layout work.

Progress this week:

• Code page layout/navigation - 4 hours (20% for total of 25%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• The page will have to be run locally on a simple HTTP server in order for the AJAX calls to be made.

Week 6:

Overall status this week:

• I have a good direction for finishing the main page layout and navigation.

Progress this week:

• Code page layout/navigation - 1 hour (5% for total of 5%)

Issues this week:

• No issues so far.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• No notes

Week 5:

Overall status this week:

• Progress is according to schedule.

Progress this week:

• Edited Concept of Operations - 1 hour (100% for total of 100%)

Issues this week:

• I had to change the original concept of operations in order to make it follow the format described more accurately.

Defect log

• No defects are currently known.

Notes, lessons learned, etc.

• No notes

<Note: These are the logs from which you will determine your status on the project and calculate project metrics (for the proj mgmt reports that must be produced at least every 2 weeks ) and from which you will build your individual lessons learned paper and your project legacy document (at the end of the semester). At a minimum, you should add to each section weekly.>