Team Number: Week: Program Size (SLOC) Base Added Deleted Modified Reused # of COTS Total New SLOC Effort (Hours) Project Mgmt. Requirements COTS Assessment Design Life <a href="/keyword/cycle-planning-configuration/" >cycle planning configuration</a> Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code <a href="/keyword/development-test-deployment/" >development test deployment</a> Planned Actual 20 1 Actual 7 14 2 0 0 0 0 0 0 0 0 0 6 16 2 0 0 0 0 0 0 0 0 0 Date Wk. 1 2 3 4 5 6 7 8 9 10 11 12 13 Planned 5 7 Cumulative No. Of tasks Actual Completed On Sched 6 6 6 5 Late 0 1 Date Wk. 1 2 3 4 5 6 7 8 9 10 11 12 13 Man-hours Planned Actual This Wk. Cumulative This Wk. Cumulative 85 85 85 170 91.8 88.5 91.8 180.3 09/11/2006 09/18/2006 09/25/2006 10/02/2006 10/09/2006 10/16/2006 10/23/2006 10/30/2006 11/06/2006 11/13/2006 11/20/2006 11/27/2006 12/04/2006 09/11/2006 09/18/2006 09/25/2006 10/02/2006 10/09/2006 10/16/2006 10/23/2006 10/30/2006 11/06/2006 11/13/2006 11/20/2006 11/27/2006 12/04/2006 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.Easy Win Win Negotiations Session 1. b.Evaluation of the Win Conditions. c.Worked On Prototype of the system. d.Further Vision Clearance Regarding the clients perspective. e.Requirement refinement(GUI). 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.Studied various NLP systems,their requirements and capabilities. b. c. d. 3. Attach any client meeting notes. If you have not had a client meeting in the past week, say &quot;No client meetings were scheduled&quot;. Weekxx_PR_S02b_Txx.xls a.Discussed the various win conditions with the client that were generated by the easy win win negotiation session 1. b.Discussed about the interface requirements of the system with the client. c. d. Weekxx_PR_S02b_Txx.xls Top Project Risks as of 09/19/2006 This Week Last Week 3 3 Risk Description Developing the wrong interface <a href="/keyword/risk-mitigation-action/" >risk mitigation action</a> Items Showing the prototype of the Interface to Client before developing the project Not Mitigated Holding more informative Requirement meetings with the client. Studying the working of Win Win Negotiation tool Weeks Active 2 5 4 Overrunning the schedule 2 4 2 Requirement mismatch 2 2 1 COTS integration 2 1 __ Misinterpretation of brainstorm condition Providing extensive glossary and elaborating the condition. 1 Weekxx_PR_S02b_Txx.xls # of Defects Project Mgmt. Requirements COTS Assessment Design Life <a href="/keyword/cycle-planning-configuration/" >cycle planning configuration</a> Mgmt. Feasibility Analysis Code COTS Tailoring COTS Glue Code <a href="/keyword/development-test-deployment/" >development test deployment</a> Total Injected 3 2 Removed 2 1 5 3 List of third-party components being considered for use in the system as of 09/27/2006 Component Name Component use in the system Black Box x x x White Box Modify Code Function of the component in the system Related components Dependency Interaction Requirement Tool Keyword Analyzer Easy Win Win Tool Requirement Tool NLP Easy Win Win Provide Negotiation result in XML format. Tool Natural Language Processor Extracting attributes from artifacts Keyword Analyzer Defect Analysis Components that were filtered in the previous week Component Name Rationale for filtering the component Notes and References Problem Reports as of mm/dd/yyyy: 09/27/2006 : * See QMP or Below for Definitions Type Issues Defects Problem Reports Definitions Issues Defects Problem Reports New Opened New Closed Old Closed Current Issues are problems that the &quot;Author&quot; can not fix solely in the artifact or at that specific time Defects in the artifact caused either by a human error (Avoidable Defect) or by situations that the &quot;Author&quot; has no control over ( Unavoidable Defect - e.g. change in the requirement). 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 Rev...