Team Number: 22
Week: 12
Program Size (SLOC) Actual
Base 5000
Added 3000
Deleted
Modified
Reused
# of COTS 5
Total New SLOC 8000
Effort (Hours) Planned Actual
Project Mgmt. 6 16
Requirements 25 28
COTS Assessment 5 12
Design 40 35
Life Cycle Planning 15 12
Configuration Mgmt.
Feasibility Analysis 10 17
Code
COTS Tailoring
COTS Glue Code development
Test
Deployment
Cumulative No. Of tasks Man-hours
Actual Planned Actual
Planned
Date Wk. Completed On Sched Late Date Wk. This Wk. Cumulative This Wk. Cumulative
09/13/2004 1 2 2 2 0 09/13/2004 1 3 3 2.5 2.5
09/20/2004 2 1 1 1 0 09/20/2004 2 60 63 58 60.5
09/27/2004 3 4 2 1 1 09/27/2004 3 90 153 104.5 165
10/04/2004 4 4 2 2 10/04/2004 4 90 243 100 265
10/11/2004 5 3 1 3 0 10/11/2004 5 105 348 120 385
10/18/2004 6 4 2 2 10/18/2004 6 110 458 121 506
10/25/2004 7 3 1 3 0 10/25/2004 7 110 568 108 614
11/01/2004 8 1 1 1 0 11/01/2004 8 94 662 114 728
11/08/2004 9 2 2 2 0 11/08/2004 9 100 762 102 830
11/15/2004 10 1 1 1 0 11/15/2004 10 100 862 107 937
11/22/2004 11 3 1 3 0 11/22/2004 11 110 972 110 1040
11/29/2004 12 1 1 1 0 11/29/2004 12 100 1072 126 1166
12/06/2004 13 1 1 1 0 12/06/2004 13 100 1172 120 1286
Based on submitted effort reports…
Progress Description:
Describe the progress on the project during the past week, both in qualitative and quantitative.
1. List any significant accomplishments since the last status report (including the completion/revision of project deliverables).
a.SSAD updated.
b. SSRD updated.
c. FRD and LCP updated
d. OCD updated.
e. LCA presentation
f.
2. If you are using COTS Process Framework, list the process areas that you worked in the past week (For example, P3, P4, etc.).
a.
b.
c.
d.
3. Attach any client meeting notes. If you have not had a client meeting in the past week, say "No client meetings were scheduled".
Weekxx_PR_S02b_Txx.xls
a.No meeting scheduled
b.
c.
d.
Weekxx_PR_S02b_Txx.xls
Top Project Risks as of 12/6/2005
Last
This Week Risk Description Risk Mitigation Action Items Weeks Active
Week
Technologies like NLP and Summarization have
Tryng to access this technologies by scrutinizing the
1 1 been in the incipient stage and that’s why it’s a 9
technical papers and evaulating tools available.
risk .
Requirements in the flux,from client point of
Increase client interaction,and try fix requirements atleast on
2 2 some of requirement can only be fixed when we 6
primary basis.
have enough research on tools we are going to
use
3 3 Tight Schedule Implement low priority requirements if time permits. 9
Weekxx_PR_S02b_Txx.xls
# of Defects Injected Removed
Project Mgmt. 0
Requirements
COTS Assessment
Design
Life Cycle Planning
Configuration Mgmt.
Feasibility Analysis
Code
COTS Tailoring
COTS Glue Code development
Test
Deployment
Total 0 0
Problem Reports as of mm/dd/yyyy: 12/6/2005
* See QMP or Below for Definitions
Type New Opened New Closed Old Closed Current
Issues 0 1
Defects 0 1
Problem Reports 0 2
Definitions
Issues Issues are problems that the "Author" can not fix solely in the artifact or at that specific time
Defects Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the "Author"
has no control over ( Unavoidable Defect - e.g. change in the requirement).
Problem Reports In case the team is using a Defect Tracking tool, that is the number of problems reported in the tool. You
can also use the Review Forms to collect that information. In that case, this will be the total number of
Concerns provided by the reviewers. Concers can be an issue, a defect or neither (consider that reviewers
might indicate false defects).
Problem Description:
List any problems team is experiencing. This includes things that have caused delays, rework or any other roadblocks to anticipated progress.
No. Problem Description Proposed Solutions Is it COTS Related? (Y/N)
1 lack of client interaction hinders Increased client intreaction via N
the project directions toward other communication. Ex. Email.
goal.
2 Prototyping of project needed Can be sloved by interaction N
to assume many artificial with client.
requirements , which is yet not
3 clear
Weekxx_PR_S02b_Txx.xls
4
5
…
Weekxx_PR_S02b_Txx.xls
progress.
Weekxx_PR_S02b_Txx.xls
List of third-party components being considered for use in the system as of 12/6/2005
Component Component use in the
Function of the component in the system Related components
Name system
Black White Modify
Dependency Interaction
Box Box Code
Apache Java-MySQL
Provides the application for the IM server. Java SDK 1.4.1 x
Tomcat database driver
Redhat Linux
9.0, Solaris 2.1,
Windows 2003
Redhat Linux
Apache 9.0, Solaris 2.1, x
webserver Provides webserver application to the system. Windows 2003
Java-MySQL
Redhat Linux driver to interact
x
9.0, Solaris 2.1, with apache
MySQL Provices persistent data storage for the system Windows 2003 tomcat
Java SDK
JAVA IM 1.4.1,APACHE x
SERVER Provides Instant Notification to user on their cellphone. TOMCAT Mysql
MYSQL,
APACHE Mysql,TOMCAT,J x
PHPBB Provide basic infrastucture for discussion forum. Webserver AVA IM SERVER
Components that were filtered in the previous week
Component
Rationale for filtering the component Notes and References
Name
Project Indicators as of xx/yy/zzzz
Cumulative Project Effort
1400
1200
Man-hours
1000 Planned
800
600 Actual
400
200
0
Week
Project Progress
Cumulative no. of tasks
5 Late
4
3 On Sched
2 Completed
1 Planned
0
Week no.
Weekxx_PR_S02b_Txx.xls