Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"
(91 intermediate revisions by 2 users not shown) | |||
Line 5: | Line 5: | ||
! width="170px" | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2014T1_Chocolicious <span style="color:#ffffff">Overview</span>] || width="170px" | <span style="color:#ffffff">Project Management</span> || width="170px" | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2014T1_Chocolicious_Documentation <span style="color:#ffffff">Documentation</span>] | ! width="170px" | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2014T1_Chocolicious <span style="color:#ffffff">Overview</span>] || width="170px" | <span style="color:#ffffff">Project Management</span> || width="170px" | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki%3A_2014T1_Chocolicious_Documentation <span style="color:#ffffff">Documentation</span>] | ||
|- | |- | ||
− | | [[IS480 Team wiki: 2014T1 Chocolicious#Project Progress|<span style="color:#c49044">1. Project Progress</span>]] || <span style="color:#c49044">1. Our Team</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation# | + | | [[IS480 Team wiki: 2014T1 Chocolicious#Project Progress|<span style="color:#c49044">1. Project Progress</span>]] || <span style="color:#c49044">1. Our Team</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#Documents|<span style="color:#c49044">1. Documents</span>]] |
|- | |- | ||
| [[IS480 Team wiki: 2014T1 Chocolicious#Project Description|<span style="color:#c49044">2. Project Description</span>]] || <span style="color:#c49044">2. Time Line</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#Database|<span style="color:#c49044">2. Database</span>]] | | [[IS480 Team wiki: 2014T1 Chocolicious#Project Description|<span style="color:#c49044">2. Project Description</span>]] || <span style="color:#c49044">2. Time Line</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#Database|<span style="color:#c49044">2. Database</span>]] | ||
Line 11: | Line 11: | ||
| [[IS480 Team wiki: 2014T1 Chocolicious#Stakeholders|<span style="color:#c49044">3. Stakeholders</span>]] || <span style="color:#c49044">3. Schedule</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#Use Cases|<span style="color:#c49044">3. Use Cases</span>]] | | [[IS480 Team wiki: 2014T1 Chocolicious#Stakeholders|<span style="color:#c49044">3. Stakeholders</span>]] || <span style="color:#c49044">3. Schedule</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#Use Cases|<span style="color:#c49044">3. Use Cases</span>]] | ||
|- | |- | ||
− | | [[IS480 Team wiki: 2014T1 Chocolicious#Learning Outcomes|<span style="color:#c49044">4. Learning Outcomes</span>]] || <span style="color:#c49044">4. Risks & Constraints</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#System Diagram|<span style="color:#c49044">4. | + | | [[IS480 Team wiki: 2014T1 Chocolicious#Learning Outcomes|<span style="color:#c49044">4. Learning Outcomes</span>]] || <span style="color:#c49044">4. Risks & Constraints</span> || [[IS480 Team wiki: 2014T1 Chocolicious Documentation#System Diagram|<span style="color:#c49044">4. Diagrams</span>]] |
|- | |- | ||
− | | || <span style="color:#c49044">5. Metrics</span> || | + | | || <span style="color:#c49044">5. Metrics</span> || |
|} | |} | ||
</div> | </div> | ||
|} | |} | ||
==Our Team== | ==Our Team== | ||
+ | [[File:ChocoOurTeam.jpg|1000px]] | ||
+ | |||
==Time Line== | ==Time Line== | ||
− | [[File:ScheduleChoco.png| | + | |
+ | <!--[[File:ScheduleChoco.png|1000px]]--> | ||
+ | [[File:ChocoMVPTimeline.jpg|1100px]] | ||
+ | <br/> | ||
+ | <p> | ||
+ | The time line shows the IS480 milestones and the iterations for the whole project. Lining the schedule, are the functions that will be released with each deployment. The functions in the later iterations will be added to the functions already available from previous iterations. | ||
+ | <br/><br/> | ||
+ | <b>C.R.U.D.</b> refers to Create, Read, Update, Delete. | ||
+ | </p> | ||
+ | |||
==Schedule== | ==Schedule== | ||
+ | |||
+ | <!-- Scrollable table --> | ||
<div style="width: 100%; height:30em; overflow:auto; border: 2px solid #088"> | <div style="width: 100%; height:30em; overflow:auto; border: 2px solid #088"> | ||
{| style="width: 100%;" border="1" | {| style="width: 100%;" border="1" | ||
− | ! scope="row" colspan="3 | + | ! scope="row" colspan="3" | || scope="row" colspan="2" | Planned |
|- | |- | ||
− | ! Iter || Tasks || width="20%"|Milestone | + | ! Iter || Tasks || width="20%"|Milestone || width="10%"|Start || width="10%"|End |
|- | |- | ||
<!-- Iteration 1 --> | <!-- Iteration 1 --> | ||
Line 53: | Line 66: | ||
|<center>23 May 2014</center> | |<center>23 May 2014</center> | ||
|<center>12 Jun 2014</center> | |<center>12 Jun 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 2 --> | <!-- Iteration 2 --> | ||
Line 78: | Line 89: | ||
<li>Grant user roles</li> | <li>Grant user roles</li> | ||
<li>Create claims</li> | <li>Create claims</li> | ||
− | <li> | + | <li>Edit/ update claims </li> |
− | <li> | + | <li>Delete claims </li> |
<li>View claims</li> | <li>View claims</li> | ||
+ | <li>Save function for unsubmitted claims</li> | ||
</ul> | </ul> | ||
Line 98: | Line 110: | ||
|<center>13 Jun 2014</center> | |<center>13 Jun 2014</center> | ||
|<center>26 Jun 2014</center> | |<center>26 Jun 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 3 --> | <!-- Iteration 3 --> | ||
Line 106: | Line 116: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li>Code for | + | <li>Code for club application</li> |
− | <li>Code for viewing/editting of all accounts for SMUSA Fin sec</li> | + | <li>Code for acceptance and rejection of club application</li> |
− | <li>Code for viewing/editting of accounts for users of different | + | <li>Code for removal of club application</li> |
+ | <li>Code for editing of claims to relevant parties</li> | ||
+ | <li>Code for submission of claims to relevant parties</li> | ||
+ | <li>Code for viewing/ editting of all accounts for SMUSA Fin sec</li> | ||
+ | <li>Code for viewing/ editting of accounts for users of different</li> | ||
</ul> | </ul> | ||
Line 123: | Line 137: | ||
<li>Update database & diagrams</li> | <li>Update database & diagrams</li> | ||
</ul> | </ul> | ||
+ | |||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | <font color="red"><b>C</b>reate, <b>R</b>ead, <b>U</b>pdate, <b>D</b>elete <b>(C.R.U.D.)</b></font><br/> | ||
+ | <font color="red">Login</font><br/> | ||
+ | <font color="red">Grant user roles</font><br/><br/> | ||
+ | <font color="red">Club Application</font><br/> | ||
+ | <font color="red">Create application </font><br/> | ||
+ | <font color="red">Acceptance & Reject</font><br/> | ||
+ | <font color="red">Remove</font><br/> | ||
+ | |||
+ | | <font color="red">C.R.U.D.</font><br/> | ||
+ | <font color="red">View claims</font><br/> | ||
+ | <font color="red">Save unsubmitted claims</font><br/> | ||
+ | <font color="red">Editing of claims</font><br/> | ||
+ | <font color="red">Claims submission</font><br/> | ||
+ | |||
+ | | <font color="red">R.U. </font><br/> | ||
+ | <font color="red">View accounts</font><br/> | ||
+ | |||
+ | |||
+ | | | ||
+ | | | ||
+ | |} | ||
+ | |||
| | | | ||
|<center>27 Jun 2014</center> | |<center>27 Jun 2014</center> | ||
|<center>10 Jul 2014</center> | |<center>10 Jul 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 4 --> | <!-- Iteration 4 --> | ||
Line 139: | Line 180: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li> | + | <li>Code for approval of claims</li> |
− | <li> | + | <li>Code for rejection of claims</li> |
− | <li> | + | <li>Code for resubmission of rejected claims</li> |
− | <li> | + | <li>Code for reject claims due to error</li> |
− | <li> | + | <li>Code for change of claims status</li> |
− | <li> | + | <li>Code for propose budget (save function for individual account)</li> |
− | <li> | + | <li>Code for edit/update of budget</li> |
+ | <li>Code for removal of budget </li> | ||
+ | <li>Code for submit budget </li> | ||
+ | <li>Code to view budget </li> | ||
</ul> | </ul> | ||
Line 159: | Line 203: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
+ | <br/> | ||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | <font color="red">Approval & Rejection</font> | ||
+ | <font color="red">Resubmission </font> | ||
+ | <font color="red">Status changed</font> | ||
+ | | R.U. | ||
+ | View accounts<br/> | ||
+ | | <font color="red">C.R.U.D. </font><br/> | ||
+ | <font color="red">View budget</font><br/> | ||
+ | <font color="red">Save & Submit</font><br/> | ||
+ | |||
+ | |||
+ | | | ||
+ | |} | ||
+ | |||
| | | | ||
|<center>11 Jul 2014</center> | |<center>11 Jul 2014</center> | ||
|<center>31 Jul 2014</center> | |<center>31 Jul 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 5 --> | <!-- Iteration 5 --> | ||
Line 176: | Line 251: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | |||
− | |||
<li>Code for SMUSA CBD & SMUSA fin sec to edit submitted budget</li> | <li>Code for SMUSA CBD & SMUSA fin sec to edit submitted budget</li> | ||
+ | <li>Code for SMUSA fin sec to allocate funds (from SAC account to every clubs' expenditure account)</li> | ||
+ | <li>Code for viewing of SAC account</li> | ||
</ul> | </ul> | ||
− | + | <b> Injection and Deposits shifted to Iteration 6, to focus on functions planned for Acceptance instead in Iteration 5. </b><br/> | |
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy a Minimum Viable Product (MVP)</li> | ||
<li>Integration testing</li> | <li>Integration testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
Line 193: | Line 269: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
+ | <br/> | ||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | <!--<font color="red"> Revenue deposit </font><br/>--> | ||
+ | <font color="red"> SAC - Fund allocation </font><br/> | ||
+ | <!--<font color="red"> SAC - Injecting funds </font><br/>--> | ||
+ | <font color="red"> SAC - View accounts</font><br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | Submission<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | <font color="red">Edit submitted budget</font><br/> | ||
+ | |||
+ | |||
+ | | | ||
+ | |} | ||
+ | |||
<center> | <center> | ||
{| style="width:100%" | {| style="width:100%" | ||
Line 201: | Line 316: | ||
|<center>1 Aug 2014</center> | |<center>1 Aug 2014</center> | ||
|<center>14 Aug 2014</center> | |<center>14 Aug 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 6 --> | <!-- Iteration 6 --> | ||
Line 215: | Line 328: | ||
<b>Coding Tasks</b><br> | <b>Coding Tasks</b><br> | ||
<ul> | <ul> | ||
+ | <li>Code for deposit revenue into expenditure account (CBD fin sec & SMUSA sec)</li> | ||
+ | <li>Code for inject funds from SAC reserve</li> | ||
+ | <li>Code for SMUSA fin sec to change reserve limit</li> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li>Code for | + | <li>Code for pull back funds from SAC reserve</li> |
− | <li>Code for | + | <li>Code for viewing of reserve account</li> |
+ | <li>Code for SMUSA fin sec to approve reserve withdrawal</li> | ||
+ | <li>Code for request reserve withdrawal (CBD & Club fin sec)</li> | ||
</ul> | </ul> | ||
− | + | <b>Modifiable Pull back Formula removed (function was not required, it was initially included due to misunderstanding of requirements on our part.)</b><br/> | |
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy MVP</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
Line 231: | Line 351: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | | | + | <br/> |
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | <font color="red"> Change reserve limit </font><br/> | ||
+ | <font color="red"> View reserve accounts </font><br/> | ||
+ | <font color="red"> Request reserve withdrawal </font><br/> | ||
+ | <font color="red"> Approve reserve withdrawal </font><br/> | ||
+ | <font color="red">SAC - Injecting funds </font><br/> | ||
+ | <font color="red">SAC - Revenue deposit </font><br/> | ||
+ | <font color="red"> SAC - Pullback funds </font><br/> | ||
+ | SAC - View accounts<br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | | | ||
+ | |} | ||
+ | |||
+ | |<center>Initial Rollout<br><b>25 Aug 2014</b></center> | ||
|<center>15 Aug 2014</center> | |<center>15 Aug 2014</center> | ||
|<center>28 Aug 2014</center> | |<center>28 Aug 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 7 --> | <!-- Iteration 7 --> | ||
Line 248: | Line 407: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li> | + | <li>Code for fund transfer between CBD & Club fin sec</li> |
− | <li> | + | <li>Code for report generation for fund transactions</li> |
+ | <li>Code for report generation of transaction of pullback and allocation</li> | ||
</ul> | </ul> | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
− | |||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy MVP</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
Line 264: | Line 425: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | | | + | <br/> |
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | <font color="red">Fund transfer </font><br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/><br/> | ||
+ | <font color="red"><b>Reports</b></font><br/> | ||
+ | <font color="red">Fund transactions </font><br/> | ||
+ | <font color="red">Transaction of pullback and allocation </font><br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | | | ||
+ | |} | ||
+ | |||
+ | |<center>UAT 1<br><b>05 Sep 2014</b></center> | ||
|<center>29 Aug 2014</center> | |<center>29 Aug 2014</center> | ||
|<center>11 Sep 2014</center> | |<center>11 Sep 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 8 --> | <!-- Iteration 8 --> | ||
Line 281: | Line 488: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li> | + | <li>Code for club level report</li> |
− | <li> | + | <li>Code for CBD level report</li> |
− | <li> | + | <li>Code for SMUSA level report</li> |
− | <li> | + | <li>Code for report generation of transaction history</li> |
+ | <li>Code for analytics dashboard</li> | ||
+ | <li>Code for e-receipt generation</li> | ||
+ | <li>Code for Vendor Recommendation </li> | ||
</ul> | </ul> | ||
− | + | <b>E-Payment shifted to later after Midterm</b><br/> | |
+ | <b>Analytic Dashboard has been dropped to focus on Vendor Recommendation and E-Payment.</b><br/> | ||
+ | <b>SAP Integration has been dropped due to external reasons.<br/>The team has however decided to persist with the objective of SAP Integration by coming up with another function: Auto Approval to accomplish the same objective as this will greatly value add to the Accounting Information System. Upon discussion with our supervisor, we have been approved to go ahead. We recognise that there may be some risk involved with the task, but we are determined to resolve that together with our client. </b><br/> | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
− | |||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy MVP</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
Line 299: | Line 512: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | | | + | <br/> |
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | Fund transfer <br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/><br/> | ||
+ | |||
+ | <b>Reports</b><br/> | ||
+ | Fund transactions <br/> | ||
+ | Transaction of pullback and allocation <br/> | ||
+ | <font color="red">Club level</font><br/> | ||
+ | <font color="red">CBD level</font><br/> | ||
+ | <font color="red">SMUSA level</font><br/> | ||
+ | <font color="red">Transaction history</font><br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | |<font color="red">E-receipt</font> | ||
+ | |} | ||
+ | |||
+ | |<center>UAT 2<br><b>19 Sep 2014</b></center> | ||
|<center>12 Sep 2014</center> | |<center>12 Sep 2014</center> | ||
|<center>25 Sep 2014</center> | |<center>25 Sep 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 9 --> | <!-- Iteration 9 --> | ||
Line 319: | Line 583: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li>Code for | + | <li>Code for club level report</li> |
− | <li> | + | <li>Code for CBD level report</li> |
− | <li> | + | <li>Code for SMUSA level report</li> |
− | <li> | + | <li>Code for report generation of transaction history</li> |
+ | <li>Code for Vendor Recommendation</li> | ||
+ | <li>Code for e-Receipt Mailing</li> | ||
+ | <li>Code for vendor recommendation</li> | ||
</ul> | </ul> | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
− | |||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy MVP</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
Line 337: | Line 605: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
+ | <br/> | ||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | Fund transfer<br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/><br/> | ||
+ | |||
+ | <b>Reports</b><br/> | ||
+ | Fund transactions <br/> | ||
+ | Transaction of pullback and allocation <br/> | ||
+ | <font color="red">Club level</font><br/> | ||
+ | <font color="red">CBD level</font><br/> | ||
+ | <font color="red">SMUSA level</font><br/> | ||
+ | <font color="red">Transaction history</font><br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | |E-receipt<br/> | ||
+ | <font color="red">Vendor recommendation</font><br/> | ||
+ | |} | ||
+ | |||
<center> | <center> | ||
{| style="width:100%" | {| style="width:100%" | ||
Line 346: | Line 668: | ||
|<center>26 Sep 2014</center> | |<center>26 Sep 2014</center> | ||
|<center>10 Oct 2014</center> | |<center>10 Oct 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 10 --> | <!-- Iteration 10 --> | ||
Line 358: | Line 678: | ||
<b>Coding Tasks</b><br> | <b>Coding Tasks</b><br> | ||
+ | Our client has requested for e-Payments to be removed.<br/> | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li>Code for | + | <li>Code for Batch Reconciliation</> |
− | <li>Code for | + | <li>Code for AGM Calculator</li> |
− | <li> | + | <li>Code for Claims Tracker</li> |
</ul> | </ul> | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
− | |||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy MVP</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
Line 377: | Line 699: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
+ | <br/> | ||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | Fund transfer <br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/><br/> | ||
+ | |||
+ | <b>Reports</b><br/> | ||
+ | Fund transactions <br/> | ||
+ | Transaction of pullback and allocation <br/> | ||
+ | Club level<br/> | ||
+ | CBD level<br/> | ||
+ | SMUSA level<br/> | ||
+ | Transaction history<br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | |E-receipt<br/> | ||
+ | <font color="red">Vendor recommendation</font><br/> | ||
+ | <font color="red">Batch Reconciliation</font><br/> | ||
+ | <font color="red">Claims Tracker</font><br/> | ||
+ | <font color="red">AGM Calculator</font> | ||
+ | |} | ||
+ | |||
| | | | ||
|<center>11 Oct 2014</center> | |<center>11 Oct 2014</center> | ||
|<center>23 Oct 2014</center> | |<center>23 Oct 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 11 --> | <!-- Iteration 11 --> | ||
Line 399: | Line 776: | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
− | |||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy fully functioning system</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
Line 409: | Line 787: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | | | + | <br/> |
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | Fund transfer <br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/> | ||
+ | <br/> | ||
+ | |||
+ | <b>Reports</b><br/> | ||
+ | Fund transactions <br/> | ||
+ | Transaction of pullback and allocation <br/> | ||
+ | Club level<br/> | ||
+ | CBD level<br/> | ||
+ | SMUSA level<br/> | ||
+ | Transaction history<br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | |E-receipt<br/> | ||
+ | Vendor recommendation<br/> | ||
+ | Batch Reconciliation<br/> | ||
+ | Claims Tracker<br/> | ||
+ | AGM Calculator | ||
+ | |} | ||
+ | |||
+ | |<center>UAT<br><b>27 Oct 2014</b></center> | ||
|<center>24 Oct 2014</center> | |<center>24 Oct 2014</center> | ||
|<center>6 Nov 2014</center> | |<center>6 Nov 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 12 --> | <!-- Iteration 12 --> | ||
Line 433: | Line 867: | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
− | |||
<li>Develop test cases for revelant functions</li> | <li>Develop test cases for revelant functions</li> | ||
+ | <li>Deploy fully functioning system</li> | ||
+ | <li>Integration Testing</li> | ||
<li>Debugging</li> | <li>Debugging</li> | ||
</ul> | </ul> | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
<b>Documentation</b><br> | <b>Documentation</b><br> | ||
Line 448: | Line 879: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | | < | + | <br/> |
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | Fund transfer <br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/> | ||
+ | <br/> | ||
+ | |||
+ | <b>Reports</b><br/> | ||
+ | Fund transactions <br/> | ||
+ | Transaction of pullback and allocation <br/> | ||
+ | Club level<br/> | ||
+ | CBD level<br/> | ||
+ | SMUSA level<br/> | ||
+ | Transaction history<br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | |E-receipt<br/> | ||
+ | Vendor recommendation<br/> | ||
+ | Batch Reconciliation<br/> | ||
+ | Claims Tracker<br/> | ||
+ | AGM Calculator | ||
+ | |} | ||
+ | |||
+ | | | ||
|<center>7 Nov 2014</center> | |<center>7 Nov 2014</center> | ||
|<center>20 Nov 2014</center> | |<center>20 Nov 2014</center> | ||
− | |||
− | |||
|- | |- | ||
<!-- Iteration 13 --> | <!-- Iteration 13 --> | ||
Line 467: | Line 954: | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
+ | |||
<li>Final round of testing</li> | <li>Final round of testing</li> | ||
</ul> | </ul> | ||
Line 481: | Line 969: | ||
<li>Update wiki page & project progress</li> | <li>Update wiki page & project progress</li> | ||
</ul> | </ul> | ||
− | | <center>Final Presentation<br><b> | + | <br/> |
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | ! scope="row" colspan="7" | Deployment | ||
+ | |- | ||
+ | ! Users || Claims || Accounts || Budgeting || Additional features | ||
+ | |- valign="top" | ||
+ | | C.R.U.D.<br/> | ||
+ | Login<br/> | ||
+ | Grant user roles<br/><br/> | ||
+ | <b>Club Application</b><br/> | ||
+ | Create application <br/> | ||
+ | Acceptance & Reject<br/> | ||
+ | Remove<br/> | ||
+ | |||
+ | | C.R.U.D.<br/> | ||
+ | View claims<br/> | ||
+ | Save unsubmitted claims<br/> | ||
+ | Editing of claims<br/> | ||
+ | Claims submission<br/> | ||
+ | Approval & Rejection | ||
+ | Resubmission | ||
+ | Status changed | ||
+ | | R.U.<br/> | ||
+ | View accounts<br/> | ||
+ | Change reserve limit<br/> | ||
+ | Edit pullback formula<br/> | ||
+ | View reserve accounts<br/> | ||
+ | Request reserve withdrawal<br/> | ||
+ | Approve reserve withdrawal<br/> | ||
+ | Fund transfer <br/> | ||
+ | SAC - Fund allocation <br/> | ||
+ | SAC - Injecting funds <br/> | ||
+ | SAC - Revenue deposit <br/> | ||
+ | SAC - View accounts<br/> | ||
+ | SAC - Pullback funds<br/> | ||
+ | <br/> | ||
+ | |||
+ | <b>Reports</b><br/> | ||
+ | Fund transactions <br/> | ||
+ | Transaction of pullback and allocation <br/> | ||
+ | Club level<br/> | ||
+ | CBD level<br/> | ||
+ | SMUSA level<br/> | ||
+ | Transaction history<br/> | ||
+ | | C.R.U.D.<br/> | ||
+ | View budget<br/> | ||
+ | Save & Submit<br/> | ||
+ | Edit submitted budget<br/> | ||
+ | |||
+ | |||
+ | |E-receipt<br/> | ||
+ | Vendor recommendation<br/> | ||
+ | Batch Reconciliation<br/> | ||
+ | Claims Tracker<br/> | ||
+ | AGM Calculator | ||
+ | |} | ||
+ | |||
+ | | <center>Final Rollout<br><b>1 Dec 2014</b></center><br/><center>Final Presentation<br><b>25 Nov 2014</b><br>Poster Day<br><b>3 Dec 2014</b></center> | ||
|<center>21 Nov 2014</center> | |<center>21 Nov 2014</center> | ||
|<center>3 Dec 2014</center> | |<center>3 Dec 2014</center> | ||
− | + | |} </div> | |
− | |||
− | |||
− | </div> | ||
==Risks & Constraints== | ==Risks & Constraints== | ||
Line 507: | Line 1,050: | ||
! scope="row" colspan="6" | Project Risk | ! scope="row" colspan="6" | Project Risk | ||
|- | |- | ||
− | ! style="width: | + | !style="width:30%"|Possible Risk || Reason & Implications |
!Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
+ | |||
|- | |- | ||
− | |<b> | + | |<b>Project may not be accepted</b><br> |
− | |<b> Reason</b> | + | |<b>Implications/Reason</b> |
− | + | Project is being done for the third time | |
− | |||
− | |||
<br /> | <br /> | ||
+ | |Medium(2) | ||
+ | |High(3) | ||
+ | |6 | ||
+ | |Do our best to satisfy expectations of Course Coordinator. | ||
+ | |||
+ | |||
+ | |- | ||
+ | |<b>Incompatibility with client’s server when application is deployed</b><br> | ||
+ | |<b>Implications/Reason</b> | ||
+ | Client has their own server/domain | ||
<br /> | <br /> | ||
− | |||
− | |||
|Low (1) | |Low (1) | ||
− | | | + | |High(3) |
− | | | + | |3 |
− | |Project Manager to | + | |Project Manager to search for plausible solutions. |
− | <br /> | + | <br />Lead Developer to explore deploying on other servers in case compatibility issues cannot be resolved. |
+ | |||
+ | |||
+ | |- | ||
+ | |<b>Underestimation of scope during development and testing</b><br> | ||
+ | |<b>Implications/Reason</b> | ||
+ | Over-confidence of development ability | ||
+ | <br /> | ||
+ | |Low (1) | ||
+ | |High(3) | ||
+ | |3 | ||
+ | |Project Manager to allocate buffer time in schedule and monitor schedule metrics closely. Scheduling of tasks to be adjusted according to metrics. | ||
+ | <br />Team to seek advice from supervisor as to whether certain functionalities should be dropped. | ||
|- | |- | ||
− | |<b> | + | |<b>Insufficient users for testing</b><br> |
− | |<b> Reason</b> | + | |<b>Implications/Reason</b> |
+ | Lack of incentives for users to do testing for us | ||
<br /> | <br /> | ||
− | + | |Medium(2) | |
− | + | |Medium(2) | |
− | |Medium (2) | ||
− | |Medium (2) | ||
|4 | |4 | ||
− | | | + | |Business Analyst to discuss with sponsors to provide users with incentives. |
− | |||
− | |||
|- | |- | ||
− | |<b> | + | |<b>Inaccurate feedback given by testers</b><br> |
− | |<b>Reason</b> | + | |<b>Implications/Reason</b> |
+ | Wrong testing mind-set (i.e. purpose of test is to show that application works, not to find defects or testers’ lack of commitment to support the testing efforts) | ||
<br /> | <br /> | ||
− | + | |Medium(2) | |
− | + | |Medium(2) | |
− | |Medium (2) | + | |4 |
− | |Medium ( | + | |Team to get non-IT users for testing to ensure that feedback is more applicable to the generic public to ensure user-friendliness. |
− | | | + | <br/ >Testers to be briefed and encouraged to test the application without reservations. |
− | | | + | |} |
− | + | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | |
− | <br | + | |- |
− | + | ! scope="row" colspan="6" | Team Risk | |
+ | |- | ||
+ | ! style="width:30%"|Possible Risk || Reason & Implications | ||
+ | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
|- | |- | ||
− | |<b> | + | |<b>Team is faced with technical difficulties</b><br> |
− | |<b>Reason</b> | + | |<b>Implications/Reason</b> |
+ | Inadequate skills | ||
<br /> | <br /> | ||
− | + | |Medium(2) | |
− | + | |High(3) | |
− | |Medium (2) | ||
− | | | ||
|6 | |6 | ||
− | | | + | |Lead Developer to learn these new skills and teach team. |
− | + | <br />Systems analyst to research on other methods/technologies that could provide an easier solution. | |
|- | |- | ||
− | |<b> | + | |<b>Team member is faced with sudden illness</b><br> |
− | |<b>Reason</b> | + | |<b>Implications/Reason</b> |
+ | Virus attack | ||
<br /> | <br /> | ||
− | + | |High(3) | |
− | + | |High(3) | |
− | | | + | |9 |
− | |High (3) | + | |Project Manager to reschedule tasks or reallocate tasks to another member. |
− | | | + | <br />Project Manager to include buffer days in project schedule to accommodate such situations. |
− | |Project Manager to reschedule tasks or reallocate tasks to another member. | ||
− | <br /> | ||
|- | |- | ||
− | |<b> | + | |<b>Team member drops module at the eleventh hour</b><br> |
− | |<b>Reason</b> | + | |<b>Implications/Reason</b> |
+ | Inability to cope | ||
<br /> | <br /> | ||
− | + | |Low(1) | |
− | + | |High(3) | |
− | |Low (1) | + | |3 |
− | |High ( | + | |Project Manager to reallocate tasks. |
− | | | + | <br />Team members to devote more time to FYP. |
− | | | ||
− | <br /> | ||
|- | |- | ||
− | |<b> | + | |<b>Malfunction of software/hardware during development phase</b><br> |
− | |<b>Reason</b> | + | |<b>Implications/Reason</b> |
+ | Software crash/hardware malfunction | ||
<br /> | <br /> | ||
− | + | |Medium(2) | |
− | + | |High(3) | |
− | | | + | |6 |
− | |High ( | + | |Project Manager to reschedule tasks. |
− | | | + | <br />Team to consistently back up all data. |
− | |Project Manager to | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
|- | |- | ||
− | ! scope="row" colspan="6" | | + | ! scope="row" colspan="6" | Sponsor Risk |
|- | |- | ||
− | ! style="width: | + | ! style="width:30%"|Possible Risk || Reason & Implications |
!Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
+ | |||
|- | |- | ||
− | |<b> | + | |<b>Constantly adding/changing of requirements</b><br> |
− | |<b> Reason</b> | + | |<b>Implications/Reason</b> |
− | + | Sponsor unsure of all that they want from the very beginning | |
<br /> | <br /> | ||
− | + | |High(3) | |
− | + | |High(3) | |
− | + | |9 | |
− | | | + | |Major changes are not permitted after agreement on requirements. |
− | | | + | <br />Project Manager to look at schedule for minor changes to see if project can still be completed on time if changes are accommodated. |
− | | | + | <br />Lead Developer and Systems Analyst to accommodate changes if changes are accepted. |
− | | | + | <br />Business Analyst to reject if changes are not accepted. |
− | <br /> | ||
− | |||
|- | |- | ||
− | |<b> | + | |<b>Project is not taken up by SMUSA after completion</b><br> |
− | |<b>Reason</b> | + | |<b> Implications/Reason</b> |
+ | Users are not comfortable with the system and opt instead to revert back to their old way of doing things | ||
<br /> | <br /> | ||
− | + | |High (3) | |
− | + | |Low (1) | |
− | | | ||
− | | | ||
|3 | |3 | ||
− | | | + | |Team to organize training sessions for users. <br /> |
<br />Project Manager to assign team member to provide assistance if need be. | <br />Project Manager to assign team member to provide assistance if need be. | ||
− | |||
− | |||
− | |||
+ | |- | ||
+ | |<b>SMUSA does not know how to operate the system</b><br> | ||
+ | |<b> Implications/Reason</b> | ||
+ | SMUSA lacks technical knowledge | ||
+ | <br /> | ||
+ | |Medium(2) | ||
+ | |Low (1) | ||
+ | |2 | ||
+ | |Business Analyst to discuss with SMUSA on whether to add user manuals. <br /> | ||
+ | |- | ||
+ | |<b>Miscommunication between Business Analyst and SMUSA</b><br> | ||
+ | |<b> Implications/Reason</b> | ||
+ | Language interpretation issues | ||
+ | <br /> | ||
+ | |High(3) | ||
+ | |Low (1) | ||
+ | |3 | ||
+ | |Team to discuss with supervisor before proceeding. <br /> | ||
+ | |} | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
|- | |- | ||
− | ! scope="row" colspan="6" | | + | ! scope="row" colspan="6" | External Risk |
|- | |- | ||
− | ! style="width: | + | !style="width:30%"|Possible Risk || Reason & Implications |
!Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
+ | |||
|- | |- | ||
− | |<b> | + | |<b>Application will not be used after completion </b><br> |
− | |<b> Reason</b> | + | |<b>Implications/Reason</b> |
− | + | Users are resistant to change | |
<br /> | <br /> | ||
+ | |Medium(2) | ||
+ | |High(3) | ||
+ | |6 | ||
+ | |<b>User Champion</b><br/> | ||
+ | We have discussed with SMUSA and agreed that the current SMUSA finance secretary - Ellora, is the user champion of the system.<br/> | ||
+ | Current SMUSA Exco will educate the new exco about their processes using the system, old methods will not be transferred to the new exco. | ||
+ | Incoming batch of finance secretaries will be the UAT testers of the program. | ||
+ | <br/><br/> | ||
+ | <b>Deployment Strategy</b><br/> | ||
+ | SMUSA secretaries will use the early deployed system in parallel with their current processes. | ||
+ | We will be using UATs for new finsec to familiarize themselves with system. | ||
+ | <ul> | ||
+ | <li>Instead of deploying late, we will be deploying early (iteration 5).</li> | ||
+ | <li>We have discussed with SMUSA, they agreed for smusa finsecs to use the system in parallel. In this way, we will get early feedback from real users. </li> | ||
+ | <li>We have also arranged for training to be done during the Leader Symposium, a Leadership workshop for new student leaders of the student organizations.</li> | ||
+ | </ul> | ||
+ | |- | ||
+ | |<b>No maintenance of system after completion of project</b><br> | ||
+ | |<b>Implications/Reason</b> | ||
+ | No appointed person to maintain system. | ||
<br /> | <br /> | ||
− | + | |Medium(2) | |
− | + | |Medium(2) | |
− | | | + | |4 |
− | |Medium ( | + | |We have discussed with our client, and come to this arrangement with our client: |
− | | | + | <ul> |
− | | | + | <li>Contract for 1 team member to maintain system for 1 year</li> |
− | < | + | <li>On the job training for people to maintain the system for subsequent years</li> |
+ | </ul> | ||
|} | |} | ||
+ | ==Client Relationship== | ||
+ | Aside from the regular client meetings, The team decided to take another step in helping to value add to our client's project and plans. One of the main aim of this project is for its implementation to come to fruition as this is already the third time this project was proposed to SMU IS480. Our team hopes to help pave the way for implementation by: | ||
+ | <ol> | ||
+ | <li>Helping users cope, adapt and learn the new system to help ease the learning. Having been equipped with better knowledge through guidance, we hope the users will be more keen on using the system.</li> | ||
+ | <li>Ensuring there is maintenance for at least a year, and hence, a form of continuity in the project. In preparation for handing over, the set-up guides and technical documents would come in handy.</li> | ||
+ | </ol> | ||
+ | To ensure users have a smooth learning, the team has arranged for trainings with SMUSA as well. On 7th November, Team Chocolicious organized a training session to help new CBd Finance Secretaries familiarize with the system in preparation for budgeting. There will also be another training for all student leaders in the coming SMU Leadership Symposium. | ||
+ | |||
+ | To aid students in learning at their own pace, the team has also come up with online video tutorials embedded in the system. Since the system went live on 7th November till today, the team has been providing steady support for users in case of any doubts or help. To ensure maintenance for at least a year after FYP, SMUSA will be paying one of the team members to help maintain the system, fix bugs, make minor business rule changes and ensuring system availability. OSL and SMUSA will co-own the system after the FYP. To prepare for handover, the team has come up with Technical Documents for set up, architecture and application guide. | ||
+ | |||
+ | While the system has successfully gone live, our team hopes that in taking the steps mentioned, we can give value to the implementation of the project and to our client's plans for the future. | ||
==Metrics== | ==Metrics== | ||
+ | ===Schedule Metrics=== | ||
+ | <center> | ||
+ | <p> | ||
+ | The formula for calculating schedule metrics is as follows: <b>Estimated time / Actual Time * 100</b> | ||
+ | </p> | ||
+ | |||
+ | {|class="wikitable" width="65%" | ||
+ | ! Score (S) tiers || Actions to take | ||
+ | |- | ||
+ | | <b>S <= 50%</b> | ||
+ | | Team's progress is <b><span style="color:red">TOO SLOW</span>!!!</b><br/> | ||
+ | <ol> | ||
+ | <li>Reflect on progress and reassess schedule.</li> | ||
+ | <li>Consider dropping functions.</li> | ||
+ | </ol> | ||
+ | |- | ||
+ | | <b>50% < S <= 90%</b> | ||
+ | | Team's progress is <b>too slow</b>. Tasks are possibly under-estimated. | ||
+ | <ol> | ||
+ | <li>Consider the possibility of tasks being under-estimated.</li> | ||
+ | <li>Use buffer days if available. | ||
+ | <ul><li>If there are no buffer days available, consider dropping functions.</li></ul> | ||
+ | </li> | ||
+ | </ol> | ||
+ | |- | ||
+ | | <b>90% < S <= 110%</b> | ||
+ | | Estimations are fairly accurate. | ||
+ | |- | ||
+ | | <b>110% < S <= 150%</b> | ||
+ | | Team's progress is <b>too fast</b><br/> | ||
+ | <ol> | ||
+ | <li>Reflect on progress and reassess schedule.</li> | ||
+ | <li>Add number of days gained as buffer days.</li> | ||
+ | </ol> | ||
+ | |- | ||
+ | | <b>150% < S</b> | ||
+ | | Team's progress is <b><span style="color:blue">TOO FAST</span>!!!</b><br/> | ||
+ | <ul> | ||
+ | <li>Mitigations are the same as the previous tier.</li> | ||
+ | </ul> | ||
+ | |} | ||
+ | <br/> | ||
+ | [[File:ChocoScheduleMetric.png|600px]] | ||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:60%" | ||
+ | |- | ||
+ | ! scope="row" colspan="5" |Schedule Log | ||
+ | |- | ||
+ | !Iteration||Planned Duration||Actual Duration||Metric Score||Action | ||
+ | |- | ||
+ | | 1 || 20 || 20 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | | 2 || 13 || 14 || 0.93 || Proceed as planned | ||
+ | |- | ||
+ | | 3 || 13 || 12 || 1.08 || Proceed as planned | ||
+ | |- | ||
+ | | 4 || 21 || 22 || 0.95 || Proceed as planned | ||
+ | |- | ||
+ | | 5 || 13 || 13 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | | 6 || 13 || 15 || 0.87 || Workload was increased in Iteration 6 to prepare for UAT 1 (which was confirmed recently) in Iteration 7. However we underestimated the complexity of coding tasks which resulted in a drop in the metric score. Upon evaluation PM is to redistribute tasks in Iterations 7 and 8 so as to avoid a similar drop in metrics score without compromising UAT 2. PM is to arrange more time for similar tasks in future iterations. | ||
+ | |- | ||
+ | | 7 || 13 || 13 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | | 8 || 13 || 13 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | | 9 || 14 || 12 || 1.17 || Proceed as planned | ||
+ | |- | ||
+ | |10 || 12 || 12 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | |11 || 13 || 13 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | |12 || 13 || 13 || 1.00 || Proceed as planned | ||
+ | |- | ||
+ | |13 || 12 || 12 || 1.00 || End of FYP | ||
+ | |} | ||
+ | </center> | ||
+ | |||
+ | ===Bug Metrics=== | ||
+ | <center> | ||
+ | {|class="wikitable" width="65%" | ||
+ | ! Severity || Description | ||
+ | |- | ||
+ | | <b>Low impact (1 point)</b> | ||
+ | | Unimportant. Typo error or small user interface alignment issues. | ||
+ | |- | ||
+ | | <b>High impact (5 points)</b> | ||
+ | | The system runs. However, some non-critical functionalities are not working. | ||
+ | |- | ||
+ | | <b>Critical impact (10 points)</b> | ||
+ | | The system is down or is un-usable after a short period of time. We have to fix the bugs to continue. | ||
+ | |} | ||
+ | |||
+ | <p> | ||
+ | <b>Points Calculation:</b> Total = 1 x num (low) + 5 x num (high) + 10 x num (critical) | ||
+ | </p> | ||
+ | |||
+ | {|class="wikitable" width="65%" | ||
+ | ! Points in iteration (P) || Action | ||
+ | |- | ||
+ | | <b> P <= 5 </b> | ||
+ | | Fix during buffer time only. | ||
+ | |- | ||
+ | | <b> 5 < P < 10 </b> | ||
+ | | Use the planned debugging time. | ||
+ | |- | ||
+ | | <b> 10 <= P </b> | ||
+ | | Stop current development and resolve the bug immediately. Project Manager reschedules the project. | ||
+ | |} | ||
+ | [[File:ChocoBugMetric.png|600px]] | ||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:60%" | ||
+ | |- | ||
+ | ! scope="row" colspan="3" |Bug Log | ||
+ | |- | ||
+ | ! Iteration || Remarks || Points | ||
+ | |- | ||
+ | | 3 || When record contains multiple clubs, only some will get deleted even though all are selected to be deleted || 5 | ||
+ | |- | ||
+ | | 3 || Add and delete options work only from second try onwards || 1 | ||
+ | |- | ||
+ | | 4 || Able to set amount to negative number || 1 | ||
+ | |- | ||
+ | | 4 || Error when submitting too large an amount for claims || 1 | ||
+ | |- | ||
+ | | 4 || Error when duplicate club id || 1 | ||
+ | |- | ||
+ | | 4 || Able to add club with neither club id nor club name || 5 | ||
+ | |- | ||
+ | | 4 || Able to submit claim without entering claim amount (amount will be nil) || 1 | ||
+ | |- | ||
+ | | 4 || Error when adding non-existent clubfinsec || 1 | ||
+ | |- | ||
+ | | 5 || Clicking on "confirm email" brings user to wrong page || 5 | ||
+ | |- | ||
+ | | 5 || Entering large amounts for claims, deposits and budgets causes program to crash || 10 | ||
+ | |- | ||
+ | | 6 || not selecting category when creating new budget event causes program to crash || 10 | ||
+ | |- | ||
+ | | 6 || Remember me when logging in doesn't work || 1 | ||
+ | |- | ||
+ | | 6 || Club deposit in SMUSA President - acknowledge then cancel causes "undefined" to come out || 1 | ||
+ | |- | ||
+ | | 6 || Club claims in SMUSA President - acknowledge then cancel causes "undefined" to come out || 1 | ||
+ | |- | ||
+ | | 7 || Updating expenditure account with large values causes program to crash || 10 | ||
+ | |- | ||
+ | | 7 || Rejecting claim with long remarks causes program to crash || 10 | ||
+ | |- | ||
+ | | 7 || Club and CBD Fin secs are able to add themselves as president || 5 | ||
+ | |- | ||
+ | | 8 || Budget request sac can become negative (because they made income more than expenditure) || 5 | ||
+ | |- | ||
+ | | 8 || Able to backdate budget to long long time ago (able to budget for 1923) || 1 | ||
+ | |- | ||
+ | | 8 || When a user with no role assigned tries to edit profile, the redirection to home page will cause error500 page || 5 | ||
+ | |- | ||
+ | | 10 || Auto Reconcile did not have validation for file input, wrong file upload will crash the application || 10 | ||
+ | |- | ||
+ | | 11 || CBd Fin Sec unable to view CBd Budget Breakdown || 5 | ||
+ | |- | ||
+ | | 11 || App crashes when attempting to sign in if user attempted to sign up with a wrong email || 10 | ||
+ | |- | ||
+ | | 12 || Wrong error shown if when reserves withdrawal is same as balance || 1 | ||
+ | |- | ||
+ | | 12 || Logic error when reviewing a budget of a club without reserve account || 5 | ||
+ | |} | ||
+ | </center> |
Latest revision as of 19:00, 22 December 2014
|
Contents
Our Team
Time Line
The time line shows the IS480 milestones and the iterations for the whole project. Lining the schedule, are the functions that will be released with each deployment. The functions in the later iterations will be added to the functions already available from previous iterations.
C.R.U.D. refers to Create, Read, Update, Delete.
Schedule
Planned | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Iter | Tasks | Milestone | Start | End | ||||||||||||||||||
1 | Preparation
Project Management
Technical Requirements
|
|||||||||||||||||||||
2 | Management & Documentation
Coding Tasks
Testing
Documentation
|
18 Jun 2014 |
||||||||||||||||||||
3 | Coding Tasks
Testing
Management & Documentation
|
|||||||||||||||||||||
4 | Management
Coding Tasks
Testing
Documentation
|
|||||||||||||||||||||
5 | Management
Coding Tasks
Injection and Deposits shifted to Iteration 6, to focus on functions planned for Acceptance instead in Iteration 5.
Documentation
|
14 Aug 2014 |
||||||||||||||||||||
6 | Management
Coding Tasks
Modifiable Pull back Formula removed (function was not required, it was initially included due to misunderstanding of requirements on our part.)
Documentation
|
25 Aug 2014 |
||||||||||||||||||||
7 | Management
Coding Tasks
Testing
Documentation
|
05 Sep 2014 |
||||||||||||||||||||
8 | Management
Coding Tasks
E-Payment shifted to later after Midterm
Documentation
|
19 Sep 2014 |
||||||||||||||||||||
9 |
Mid term preparation Management
Coding Tasks
Testing
Documentation
|
10 Oct 2014 |
||||||||||||||||||||
10 | Management
Coding Tasks
Testing
Documentation
|
|||||||||||||||||||||
11 | Management
Coding Tasks
Testing
Documentation
|
27 Oct 2014 |
||||||||||||||||||||
12 |
Prepare for Poster Day Management
Coding Tasks
Testing
|
|||||||||||||||||||||
13 |
Prepare for Final Presentation Management
Testing
Documentation
|
1 Dec 2014 25 Nov 2014 Poster Day 3 Dec 2014 |
Risks & Constraints
Risk Table
Probability | 1-low | 2-medium | 3-high |
---|---|---|---|
Effect | 1-low | 2-medium | 3-high |
Priority | Higher number more important |
Project Risk | |||||
---|---|---|---|---|---|
Possible Risk | Reason & Implications | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Project may not be accepted |
Implications/Reason
Project is being done for the third time
|
Medium(2) | High(3) | 6 | Do our best to satisfy expectations of Course Coordinator.
|
Incompatibility with client’s server when application is deployed |
Implications/Reason
Client has their own server/domain
|
Low (1) | High(3) | 3 | Project Manager to search for plausible solutions.
|
Underestimation of scope during development and testing |
Implications/Reason
Over-confidence of development ability
|
Low (1) | High(3) | 3 | Project Manager to allocate buffer time in schedule and monitor schedule metrics closely. Scheduling of tasks to be adjusted according to metrics.
|
Insufficient users for testing |
Implications/Reason
Lack of incentives for users to do testing for us
|
Medium(2) | Medium(2) | 4 | Business Analyst to discuss with sponsors to provide users with incentives.
|
Inaccurate feedback given by testers |
Implications/Reason
Wrong testing mind-set (i.e. purpose of test is to show that application works, not to find defects or testers’ lack of commitment to support the testing efforts)
|
Medium(2) | Medium(2) | 4 | Team to get non-IT users for testing to ensure that feedback is more applicable to the generic public to ensure user-friendliness.
|
Team Risk | |||||
---|---|---|---|---|---|
Possible Risk | Reason & Implications | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Team is faced with technical difficulties |
Implications/Reason
Inadequate skills
|
Medium(2) | High(3) | 6 | Lead Developer to learn these new skills and teach team.
|
Team member is faced with sudden illness |
Implications/Reason
Virus attack
|
High(3) | High(3) | 9 | Project Manager to reschedule tasks or reallocate tasks to another member.
|
Team member drops module at the eleventh hour |
Implications/Reason
Inability to cope
|
Low(1) | High(3) | 3 | Project Manager to reallocate tasks.
|
Malfunction of software/hardware during development phase |
Implications/Reason
Software crash/hardware malfunction
|
Medium(2) | High(3) | 6 | Project Manager to reschedule tasks.
|
Sponsor Risk | |||||
---|---|---|---|---|---|
Possible Risk | Reason & Implications | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Constantly adding/changing of requirements |
Implications/Reason
Sponsor unsure of all that they want from the very beginning
|
High(3) | High(3) | 9 | Major changes are not permitted after agreement on requirements.
|
Project is not taken up by SMUSA after completion |
Implications/Reason
Users are not comfortable with the system and opt instead to revert back to their old way of doing things
|
High (3) | Low (1) | 3 | Team to organize training sessions for users.
|
SMUSA does not know how to operate the system |
Implications/Reason
SMUSA lacks technical knowledge
|
Medium(2) | Low (1) | 2 | Business Analyst to discuss with SMUSA on whether to add user manuals.
|
Miscommunication between Business Analyst and SMUSA |
Implications/Reason
Language interpretation issues
|
High(3) | Low (1) | 3 | Team to discuss with supervisor before proceeding. |
External Risk | |||||
---|---|---|---|---|---|
Possible Risk | Reason & Implications | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Application will not be used after completion |
Implications/Reason
Users are resistant to change
|
Medium(2) | High(3) | 6 | User Champion We have discussed with SMUSA and agreed that the current SMUSA finance secretary - Ellora, is the user champion of the system.
|
No maintenance of system after completion of project |
Implications/Reason
No appointed person to maintain system.
|
Medium(2) | Medium(2) | 4 | We have discussed with our client, and come to this arrangement with our client:
|
Client Relationship
Aside from the regular client meetings, The team decided to take another step in helping to value add to our client's project and plans. One of the main aim of this project is for its implementation to come to fruition as this is already the third time this project was proposed to SMU IS480. Our team hopes to help pave the way for implementation by:
- Helping users cope, adapt and learn the new system to help ease the learning. Having been equipped with better knowledge through guidance, we hope the users will be more keen on using the system.
- Ensuring there is maintenance for at least a year, and hence, a form of continuity in the project. In preparation for handing over, the set-up guides and technical documents would come in handy.
To ensure users have a smooth learning, the team has arranged for trainings with SMUSA as well. On 7th November, Team Chocolicious organized a training session to help new CBd Finance Secretaries familiarize with the system in preparation for budgeting. There will also be another training for all student leaders in the coming SMU Leadership Symposium.
To aid students in learning at their own pace, the team has also come up with online video tutorials embedded in the system. Since the system went live on 7th November till today, the team has been providing steady support for users in case of any doubts or help. To ensure maintenance for at least a year after FYP, SMUSA will be paying one of the team members to help maintain the system, fix bugs, make minor business rule changes and ensuring system availability. OSL and SMUSA will co-own the system after the FYP. To prepare for handover, the team has come up with Technical Documents for set up, architecture and application guide.
While the system has successfully gone live, our team hopes that in taking the steps mentioned, we can give value to the implementation of the project and to our client's plans for the future.
Metrics
Schedule Metrics
The formula for calculating schedule metrics is as follows: Estimated time / Actual Time * 100
Score (S) tiers | Actions to take |
---|---|
S <= 50% | Team's progress is TOO SLOW!!!
|
50% < S <= 90% | Team's progress is too slow. Tasks are possibly under-estimated.
|
90% < S <= 110% | Estimations are fairly accurate. |
110% < S <= 150% | Team's progress is too fast
|
150% < S | Team's progress is TOO FAST!!!
|
Schedule Log | ||||
---|---|---|---|---|
Iteration | Planned Duration | Actual Duration | Metric Score | Action |
1 | 20 | 20 | 1.00 | Proceed as planned |
2 | 13 | 14 | 0.93 | Proceed as planned |
3 | 13 | 12 | 1.08 | Proceed as planned |
4 | 21 | 22 | 0.95 | Proceed as planned |
5 | 13 | 13 | 1.00 | Proceed as planned |
6 | 13 | 15 | 0.87 | Workload was increased in Iteration 6 to prepare for UAT 1 (which was confirmed recently) in Iteration 7. However we underestimated the complexity of coding tasks which resulted in a drop in the metric score. Upon evaluation PM is to redistribute tasks in Iterations 7 and 8 so as to avoid a similar drop in metrics score without compromising UAT 2. PM is to arrange more time for similar tasks in future iterations. |
7 | 13 | 13 | 1.00 | Proceed as planned |
8 | 13 | 13 | 1.00 | Proceed as planned |
9 | 14 | 12 | 1.17 | Proceed as planned |
10 | 12 | 12 | 1.00 | Proceed as planned |
11 | 13 | 13 | 1.00 | Proceed as planned |
12 | 13 | 13 | 1.00 | Proceed as planned |
13 | 12 | 12 | 1.00 | End of FYP |
Bug Metrics
Severity | Description |
---|---|
Low impact (1 point) | Unimportant. Typo error or small user interface alignment issues. |
High impact (5 points) | The system runs. However, some non-critical functionalities are not working. |
Critical impact (10 points) | The system is down or is un-usable after a short period of time. We have to fix the bugs to continue. |
Points Calculation: Total = 1 x num (low) + 5 x num (high) + 10 x num (critical)
Points in iteration (P) | Action |
---|---|
P <= 5 | Fix during buffer time only. |
5 < P < 10 | Use the planned debugging time. |
10 <= P | Stop current development and resolve the bug immediately. Project Manager reschedules the project. |
Bug Log | ||
---|---|---|
Iteration | Remarks | Points |
3 | When record contains multiple clubs, only some will get deleted even though all are selected to be deleted | 5 |
3 | Add and delete options work only from second try onwards | 1 |
4 | Able to set amount to negative number | 1 |
4 | Error when submitting too large an amount for claims | 1 |
4 | Error when duplicate club id | 1 |
4 | Able to add club with neither club id nor club name | 5 |
4 | Able to submit claim without entering claim amount (amount will be nil) | 1 |
4 | Error when adding non-existent clubfinsec | 1 |
5 | Clicking on "confirm email" brings user to wrong page | 5 |
5 | Entering large amounts for claims, deposits and budgets causes program to crash | 10 |
6 | not selecting category when creating new budget event causes program to crash | 10 |
6 | Remember me when logging in doesn't work | 1 |
6 | Club deposit in SMUSA President - acknowledge then cancel causes "undefined" to come out | 1 |
6 | Club claims in SMUSA President - acknowledge then cancel causes "undefined" to come out | 1 |
7 | Updating expenditure account with large values causes program to crash | 10 |
7 | Rejecting claim with long remarks causes program to crash | 10 |
7 | Club and CBD Fin secs are able to add themselves as president | 5 |
8 | Budget request sac can become negative (because they made income more than expenditure) | 5 |
8 | Able to backdate budget to long long time ago (able to budget for 1923) | 1 |
8 | When a user with no role assigned tries to edit profile, the redirection to home page will cause error500 page | 5 |
10 | Auto Reconcile did not have validation for file input, wrong file upload will crash the application | 10 |
11 | CBd Fin Sec unable to view CBd Budget Breakdown | 5 |
11 | App crashes when attempting to sign in if user attempted to sign up with a wrong email | 10 |
12 | Wrong error shown if when reserves withdrawal is same as balance | 1 |
12 | Logic error when reviewing a budget of a club without reserve account | 5 |