Team Number: 11
Week: 11
Program Size (SLOC) Actual
Base
Added 0
Deleted 0
Modified 0
Reused 0
From COTS 0
Total New SLOC 0
Progress Description:
Describe the progress on the project during the past week, both in qualitative and quantitative.
A. List your top priority works that must be accomplished in this week
1 Configure Moodle on the hosting services and designing the system as per the requirements of the clients
2 Meeting the client and discussing the currently designed system
3 Finish the documentation for submission of Draft DC package
4
We have explored moodle completely and are trying configure the system and deploying the final system on the hosting
services for final system delivery.
C. List your accomplishments from the previous week
1 Designed and implemented all the requirements as agreed in the win conditions for the final system
2 Met the client and finalized the hosting services.
3
4
#
D. Report your planned and actual man-hours for each category of your work in the previous week
Effort (Hours) Planned Actual
Project Management 7 10
Requirements 10 10
COTS Assessment 4 7
Design 0 0
Life Cycle Planning 10 12
Configuration Management 0 0
Feasibility Analysis 0 0
Code 0 0
COTS Tailoring 0 0
COTS Glue Code development 0 0
Test 0 0
Deployment 6 10
Top Project Risks as of 11/26/2008
Rank
This Last Risk Description
Week Week
We don’t have any risks for the system currently. All the
1 past risks have been mitigated
2
3
4
5
6
7
8
ct Risks as of 11/26/2008
No. of
Risk Mitigation Action Items Weeks
Active
NA
List of third-party components being considered for use in the system as of 11/26/2
Component Function of the component in the
Related components
Name system
Dependency
Existing website for small
CollectiveX Provide collaboration for groups.
businesses
Explored Moodle and connfiguring it
on the hosting services to provide full
set of requirements as set in the
moodle.com Winwin report None
Components that were filtered in the previous week
Component
Rationale for filtering the component
Name
NA We have not discarded any components this week.
sidered for use in the system as of 11/26/2008
Component use in the
Related components
system
Black White Modify
Interaction Box Box Code
Has to be set up for the client.
NA
iltered in the previous week
Notes and References
Defects, Problems, and Issues
Describe the defects, problems, and issues in the project during the past week
Avoidable Defects: a shortcoming, fault, imperfection or problem that could be prevented such as human error
Unavoidable Defects: a shortcoming, fault, imperfection or problem that the team has no control over such as a change in the requirem
Concern: A matter that might cause some trouble, worry or an unsettled matter is ready for a decision
A. List any avoidable defect occurred in the previous week
Avoidable Defects
1 There are no defects to mention here for the system
2
3
4
5
B. List any unavoidable defect occurred in the previous week
Unavoidable defect
1 There are no defects to mention here for the system
2
3
4
5
C. List any concern occurred in the previous week
Concerns
1 The small business system needs a functionality of communities which is currently
available but the user need to switch between groups sites on the system hosted
on collectiveX.
2
3
4
5
uld be prevented such as human error
he team has no control over such as a change in the requirement
matter is ready for a decision
Proposed Solution
Proposed Solution
Proposed Solution
It has been placed as an Evolutionary requirement as of now and the new
version of CollectiveX will be checked for that funcationality when it becomes
available.
Defect Counts
Type New Opened New Closed Old Closed
Issues 0 0 0
Defects 0 0 0
Problem Reports 0 0 0
"Problem reports" and issues generated since last report
"Old" are those in "current" in the previous report
Issues Issues are problems that the "Author" can not fix solely in the artifact or at that specific tim
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).
Current
0
0
0
n the artifact or at that specific time
voidable Defect) or by situations
ect - e.g. change in the
he number of problems reported
that information. In that case,
e reviewers. Concers can be an
indicate false defects).