Jon
Carelli
COP
4331 - Fall 2014 - Online Health Monitoring System
Project Name: Online Health Monitoring System
Team Web site: link
Web Pages for Other Team Members:
Contents
of this Document
Individual Weekly Time and Activity Log:
Weekly
statements of individual progress and status:
|
Week |
Notes |
Hours |
Percentage |
|
2 |
Set up team
webpage, and my own individual webpage. |
1-3 hours |
No estimated
completion |
|
3 |
Began working on
SRS document for deliverable 1 |
1.5 hours |
33% for a total
of 33% |
|
4 |
Software
Requirements Specification |
3
hours |
57%
for a total of 90% |
|
5 |
Software
Requirements Specification |
1.5 hours |
10% for a total
of 100% |
|
6 |
Helped
work on high level layout for Deliverable II |
1
hour |
50%
for a total of 50% |
|
7 |
Research on JS /
HTML5 messaging system |
4 hours |
30% for a total
of 30% |
|
8 |
Worked
on detailed design for Chat manager module |
4
hours |
65
% for a total of 95% |
|
9 |
Worked on slides
for presentation #1 |
2 hours |
100% for a total
of 100% |
|
10 |
Worked
on code for Chat Manager |
4
hours |
75%
for a total of 75% |
|
11 |
Linked up with
James for Database Integration, found out the module must be redone with PHP
and AJAX support. |
5 hours |
10% for a total
of 10% |
|
12 |
Researched
PHP and AJAX |
5
hours |
20%
for a total of 30% |
|
13 |
James assisted
me greatly in the backend of the chat module. The chat module is functionally
complete. |
8 hours |
65% for a total
of 95% |
|
|
|
|
|
Defect
log:
|
Week |
Log |
|
2 |
It’s becoming apparent that these document’s should be completed in order, and not individually The SRS document requires references to both the Concept of Operations and the Project Plan documents. |
|
3 |
We
will need to look into a good database option. I’m thinking MySQL or MongoDB |
|
4 |
None |
|
5 |
None |
|
6 |
None |
|
7 |
None |
|
8 |
None |
|
9 |
Missed
the team meeting about the presentation / Deliverable III due to illness.
Will have to get caught up during the week. |
|
10 |
None |
|
11 |
Its come to my attention that I will need to redo the
chat module to support PHP and AJAX. |
|
12 |
None |
|
13 |
James
helped me a lot this week with the coding of the Chat module. Its functionally completed after some bug squashing. |
|
|
|
Notes / Lessons learned, etc.
|
Week |
Anticipated progress next week: |
Hours |
Percentage |
|
2 |
Begin working on
SRS document |
1.5-3 hours |
33% for a total of
33% |
|
3 |
Continue working on SRS document |
3 hours |
57% for a total of 90% |
|
4 |
The completion of
SRS grammar check for first deliverable. |
1-3 hours |
90% to 100% |
|
5 |
Begin working on Deliverable II / Go over
notes |
1-3 hours |
No anticipation |
|
6 |
Continue working
on Deliverable II |
1-3 hours |
No anticipation |
|
7 |
Continue doing research on messaging
system, begin detailed design for the Chat Manager module. |
1-8 hours |
30% to 80% |
|
8 |
Clean up the
detailed design and begin working on presentation slides |
1-4 hours |
95% to 100% |
|
9 |
Begin coding Chat Manager module |
1-8 hours |
75% for a total of 75% |
|
10 |
Link up with James
to integrate database functionality into the Chat Manager. |
1-8 hours |
25% for a total of
100% |
|
11 |
Begin re-coding Chat Module |
1-8 hours |
20% for a total of 30% |
|
12 |
Code chat module |
1-8 hours |
65% for a total of
95% |
|
13 |
Complete chat module |
1-3 hours |
5% for a total of 100% |
|
|
|
|
|
Template created by G. Walton (GWalton@mail.ucf.edu) on August 15, 2000
This page last modified by Jon Carelli (jcarelli@knights.ucf.edu) on 10/1/2014