Team Number: 12
Program Size (SLOC) Actual
# of COTS 0
Total New SLOC 0
Effort (Hours) Planned Actual
Project Mgmt. 65 70
Requirements 8 9
COTS Assessment 4 4
Design 7 7
Life Cycle Planning 8 8
Configuration Mgmt. 0 0
Feasibility Analysis 4 5
Code 0 0
COTS Tailoring 0 0
COTS Glue Code development 0 0
Test 0 0
Deployment 0 0
Cumulative No. Of tasks Man-hours
Actual Planned Actual
Date Wk. Completed On Sched Late Date Wk. This Wk. Cumulative This Wk. Cumulative
09/26/2007 1 5 5 5 0 09/26/2007 1 52 52 52.5 52.5
10/03/2007 2 8 8 8 0 10/03/2007 2 96 148 103 155.5
10/10/2007 3 10/10/2007 3
10/17/2007 4 10/17/2007 4
10/24/2007 5 10/24/2007 5
10/31/2007 6 10/31/2007 6
11/07/2007 7 11/07/2007 7
11/14/2007 8 11/14/2007 8
11/21/2007 9 11/21/2007 9
11/28/2007 10 11/28/2007 10
12/05/2007 11 12/05/2007 11
12/12/2007 12 12/12/2007 12
Based on submitted effort reports…
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) Reviewed the OCD.
c) Met with the client and discussed the requirements and sample prototype
3) Had team meeting to present a prototype based on the requirements and ideas of the client.
d) Worked on understanding the SSRD document.
e) Rated the risks in dart.
f) setup WikiWinWin
e) prepaared the MS project Plan
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. COTS "drupal" Assessment
3. Attach any client meeting notes. If you have not had a client meeting in the past week, say "No client meetings were scheduled".
a) Client meeting noted have been uploaded on the team website
Top Project Risks as of xx/yy/zzzz
This Week Risk Description Risk Mitigation Action Items Weeks Active
Team members drop the class may result not Every team member should follow the project closely so
1 0 1
meeting deadline. another team member can substitute the drop out member.
The COTS product may not be able to add new
features that the client wants easily if they are Pick a COTS which is flexible and allows customized module
2 0 1
not provided by the COTS in the future. This will integration.
result longer development time.
# of Defects Injected Removed
Life Cycle Planning
COTS Glue Code development
Problem Reports as of mm/dd/yyyy:
* See QMP or Below for Definitions
Type New Opened New Closed Old Closed Current
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).
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)
List of third-party components being considered for use in the system as of mm/dd/yyyy
Component Component use in the
Function of the component in the system Related components
Black White Modify
Box Box Code
Provides the application web-server for the system Java SDK 1.4.1 x
Tomcat database driver
9.0, Solaris 2.1,
Redhat Linux driver to interact
9.0, Solaris 2.1, with apache
MySQL Provices persistent data storage for the system Windows 2003 tomcat
Components that were filtered in the previous week
Rationale for filtering the component Notes and References
The underlying platform required is Microsoft Server, the Refer to Microsoft website
MSSQL client does not have the resources to maintain a MS (http://www.microsoft.com/mssql/requirements), Constraint PC-
server 01 (OCD Section 4.2), Client meeting minutes xx-xx-xxxx.
Project Indicators as of xx/yy/zzzz
Cumulative Project Effort
Cumulative no. of tasks