Difference between revisions of "IS480 Team wiki: 2011T2 iNstaNex Mid Term Wiki Page"
Line 367: | Line 367: | ||
== Quality of product == | == Quality of product == | ||
− | === Intermediate Deliverables === | + | === Intermediate Deliverables === |
+ | |||
+ | {| class="wikitable" cellpadding="15" style="border: 2px solid black;" | ||
+ | ! align="left" width="80px" style="background: #FC9" style="border: 2px solid black; background: #EE82EE" align="center"| Stage | ||
+ | ! align="left" width="380px" style="background: #FC9" style="border: 2px solid black; background: #EE82EE" align="center"| Specifications | ||
+ | ! align="left" width="125px" style="background: #FC9" style="border: 2px solid black; background: #EE82EE" align="center"| Modules | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |style="border: 2px solid black;"| 1 | ||
+ | |style="border: 2px solid black;"| • Gathering of business requirements | ||
+ | • Generation of project ideas | ||
+ | |style="border: 2px solid black;"| 05/10/11 - 10/10/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black;"| 2 | ||
+ | |style="border: 2px solid black;"| • Finalize project proposal | ||
+ | • Proposal Submission | ||
+ | |style="border: 2px solid black;"| 01/10/11 - 24/10/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black;"| 3 | ||
+ | |style="border: 2px solid black;"| • Refine project scope | ||
+ | • User interface design mock up | ||
+ | |||
+ | • Use case diagram | ||
+ | |||
+ | • Wiki design | ||
+ | |||
+ | • Business process workflow diagram | ||
+ | |style="border: 2px solid black;"| 25/10/11 - 06/11/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| '''4 ( Shifted to after Acceptance Test )''' | ||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| • Setting up connection to database | ||
+ | • Connect application to database | ||
+ | |||
+ | • Read/retrieve/edit/delete of data in database | ||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| 07/11/11 - 16/11/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| '''5 ( Shifted to after Acceptance Test ) | ||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| • Login/Logout function | ||
+ | • Login\Logout UI | ||
+ | |||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| 17/11/11 - 23/11/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| '''6 ( Shifted to after Acceptance Test )''' | ||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| • Product Catalogue | ||
+ | • Add/filter of product catalogue | ||
+ | |||
+ | • Algorithm of product catalogue quotation | ||
+ | |||
+ | • '''User Acceptance test 1.0''' | ||
+ | |||
+ | • '''Acceptance Presentation''' | ||
+ | |style="border: 2px solid black; background-color:#D8BFD8;"| 24/11/11 - 15/12/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |- | ||
+ | |style="border: 2px solid black;"| 5 | ||
+ | |style="border: 2px solid black;"| • Login/Logout of different users | ||
+ | • Login\Logout Validation | ||
+ | |||
+ | • Login\Logout User interface | ||
+ | |||
+ | |style="border: 2px solid black;"| 16/12/11 - 25/12/11 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |style="border: 2px solid black;"| 6 | ||
+ | |style="border: 2px solid black;"| • Product Catalogue | ||
+ | • Add/filter of product catalogue | ||
+ | |||
+ | • Algorithm of product catalogue quotation | ||
+ | |||
+ | |style="border: 2px solid black;"| 26/12/11 - 12/01/12 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black;"| 7 | ||
+ | |style="border: 2px solid black;"| • Schedule appointment notification | ||
+ | • Access Google calender for scheduling through Application | ||
+ | |||
+ | • Announcement board for LG representatives | ||
+ | |style="border: 2px solid black;"| 13/01/12 - 20/01/12 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |style="border: 2px solid black;"| 8 | ||
+ | |style="border: 2px solid black;"| • Intranet system for inventory management | ||
+ | • Inventory database design and setup | ||
+ | |||
+ | • Intranet system user interface | ||
+ | |style="border: 2px solid black;"| 21/01/12 - 25/01/12 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black;"| 9 | ||
+ | |style="border: 2px solid black;"| • SMS notification of installer delivery | ||
+ | • Call notification to customer | ||
+ | |||
+ | |style="border: 2px solid black;"| 26/01/12 - 31/01/12 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |||
+ | |style="border: 2px solid black;"| 10 | ||
+ | |style="border: 2px solid black;"| • Retrieval of current date's job list | ||
+ | • Confirmation update of job status | ||
+ | |||
+ | |style="border: 2px solid black;"| 01/02/12 - 10/02/12 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |style="border: 2px solid black;"| 11 | ||
+ | |style="border: 2px solid black;"| • System Integration and testing | ||
+ | |style="border: 2px solid black;"| 11/02/11 - 24/02/12 | ||
+ | |||
+ | |- | ||
+ | |||
+ | |||
+ | |} | ||
+ | |||
=== Deployment === | === Deployment === | ||
=== Testing === | === Testing === |
Revision as of 19:00, 22 February 2012
Project Progress Summary
Project Highlights
As for midterm, we have completed our core functionality such as the
1. Product Catalogue,
2. Product Catalogue Quotation,
3. Retrieval of Job List and
4. Intranet System for Inventory Management.
We have completed about 50 percent of our core functionality.
The remaining functionality such as the
1. Geo-location of Delivery Teams,
2. Digital Signature on Order Receipt, and
3. Google Calender for Scheduling
is scheduled to be done after mid-term.
We also faced a few unexpected events like having a team member leave the team shortly after the Initial Acceptance Phase, client changing / removing core functionality [SMS notification to customers removed], the absence of another team member for 3 weeks, and the incorrect system architecture of iPhone application.
However, all these unfortunate events have been resolved and we have moved on with our progress to prevent further delay on schedule.
Project Management
Project Status
System | Function | Status | Confidence Level | Comment | |||
---|---|---|---|---|---|---|---|
iPhone Application | |||||||
Administrative Functions
• Login/Logout Functionality • Login/Logout Validation • Locate Us • Contact Us • About Us • Electromax website |
Fully deployed and tested 100% | 1 | |||||
Product Catalogue | Fully deployed and tested 100% | 1 | |||||
Product Catalogue Quotation | Fully deployed and tested 100% | 1 | |||||
Job List Retrieval | Fully deployed and tested 100% | 1 | |||||
SMS Notification to customers | Removed | - | Client's request | ||||
Intranet System | Inventory Management
• Update Installer Retrieval • Update Bracket Stock • Update TV Stock • View Installer Retrieval History • Report Spoilt Brackets • Return Failed Delivery Brackets |
Fully deployed and tested 100% | 1 | ||||
Scheduled after Mid Term | |||||||
iPhone Application | |||||||
Delivery Scheduling
• Google Calendar • Bulletin Board |
25/02/12 - 02/03/12 | - | - | ||||
Geo Location for Delivery Teams
• Delivery Team location update |
03/03/12 - 23/03/12 | - | - | ||||
Digital Signature | 23/03/12 - 05/04/12 | - | - |
Project Schedule (Planned vs Actual)
Iterations | Project Tasks | Planned Duration | Actual Duration | Schedule Metric | Remarks: |
---|---|---|---|---|---|
1 | • Gathering of business requirements
• Generation of project ideas |
05/10/11 - 10/10/11 | 05/10/11 - 10/10/11 | 100% | On Time |
2 | • Finalize project proposal
• Proposal Submission |
01/10/11 - 24/10/11 | 01/10/11 - 24/10/11 | 100% | On Time |
3 | • Refine project scope
• User interface design mock up • Use case diagram • Wiki design • Business process workflow diagram |
25/10/11 - 06/11/11 | 25/10/11 - 06/11/11 | 100% | On Time |
4 ( Shifted to after Acceptance Test ) | • Setting up connection to database
• Connect application to database • Read/retrieve/edit/delete of data in database |
07/11/11 - 16/11/11 | - | - | |
5 ( Shifted to after Acceptance Test ) | • Login/Logout function
• Login\Logout UI |
17/11/11 - 23/11/11 | - | - | Postpone |
6 ( Shifted to after Acceptance Test ) | • Product Catalogue
• Add/filter of product catalogue • Algorithm of product catalogue quotation • User Acceptance test 1.0 • Acceptance Presentation |
24/11/11 - 15/12/11 | - | - | Postpone |
5 | • Login/Logout of different users
• Login\Logout Validation • Login\Logout User interface |
16/12/11 - 25/12/11 | 16/12/11 - 10/01/12 | 38.5% | Behind Schedule |
6 | • Product Catalogue
• Add/filter of product catalogue • Algorithm of product catalogue quotation |
26/12/11 - 12/01/12 | 26/12/11 - 31/01/12 | 22.7% | Behind Schedule |
7 | • Schedule appointment notification
• Access Google calender for scheduling through Application • Announcement board for LG representatives |
13/01/12 - 20/01/12 | - | - | Postpone |
8 | • Intranet system for inventory management
• Inventory database design and setup • Intranet system user interface |
21/01/12 - 25/01/12 | 21/01/12 - 25/01/12 | 100% | On Time |
9 | • SMS notification of installer delivery
• Call notification to customer |
26/01/12 - 31/01/12 | - | - | Removed (Client's request) |
10 | • Retrieval of current date's job list
• Confirmation update of job status |
01/02/12 - 10/02/12 | 01/02/12 - 10/02/12 | 100% | On Time |
11 | • System Integration and testing | 11/02/11 - 24/02/12 | 11/02/11 - 24/02/12 | 100& | On Time |
Project Metrics
Schedule Metric
View Calculation of Team Schedule Metric here
As shown in the graph, our team is on schedule from iterations 1 to 3.
However, we faced some difficulties during iteration 4 where we were supposed to set up the database for our application. While planning this schedule, we have assigned the setting up of database connection to the iPhone application for iteration 4. Our team then realised it was a mistake to assign it as an iteration because iPhone application database connection should not be consider as a functionality.
We shouldn't put it under a iteration because every core functionality in our iPhone app would require the developer to develop his function on the PHP script and the XCode platform and every core function that is to be developed would require its own PHP script to connect to the database. Since database connection is done continuously when core functionality is being developed, iteration 4 is not feasible.
The period in iteration 4 is spend researching and exploring how an iPhone application is being connected to the database before realising our mistake.
As for iteration 5 and 6, we were behind schedule due to the unfamiliarity with XCode. Much time was taken reading up the guide book for XCode before the actual start of the development.
When we were halfway through iteration 6, one of our team member was uncontactable and did not turn up for our FYP meetings. The team member had already did research and have experienced in the functionality we planned to implement in iteration 7 so his disappearance was a disruption to our flow.
We then decided to postpone the whole functionality in iteration 7 and start working on the iteration 8. This action was done because we were giving the team member time to return. Additionally, we did not want to disrupt the schedule any further as we were already behind time.
Fortunately, we were able to complete iteration 8 within the time scheduled and we were back on track. We have decided to postpone the functionality in iteration 7 after mid term.
In iteration 9, we were researching and exploring the SMS notification functionality. However, when we updated our client on our progress and the unfortunate events that had happened in the previous iterations, we were informed that our client had already outsourced the SMS notification function to a more experienced partner so we were told to drop that functionality. That explains why there is no metrics recorded in iteration 9.
Project Risks
Team/Project Management Risk
Technology/Design Risk
Technical Complexity
The technical complexity we have faced are ranked starting with the highest level of difficulty.
1.
Quality of product
Intermediate Deliverables
Stage | Specifications | Modules |
---|---|---|
1 | • Gathering of business requirements
• Generation of project ideas |
05/10/11 - 10/10/11 |
2 | • Finalize project proposal
• Proposal Submission |
01/10/11 - 24/10/11 |
3 | • Refine project scope
• User interface design mock up • Use case diagram • Wiki design • Business process workflow diagram |
25/10/11 - 06/11/11 |
4 ( Shifted to after Acceptance Test ) | • Setting up connection to database
• Connect application to database • Read/retrieve/edit/delete of data in database |
07/11/11 - 16/11/11 |
5 ( Shifted to after Acceptance Test ) | • Login/Logout function
• Login\Logout UI |
17/11/11 - 23/11/11 |
6 ( Shifted to after Acceptance Test ) | • Product Catalogue
• Add/filter of product catalogue • Algorithm of product catalogue quotation • User Acceptance test 1.0 • Acceptance Presentation |
24/11/11 - 15/12/11 |
5 | • Login/Logout of different users
• Login\Logout Validation • Login\Logout User interface |
16/12/11 - 25/12/11 |
6 | • Product Catalogue
• Add/filter of product catalogue • Algorithm of product catalogue quotation |
26/12/11 - 12/01/12 |
7 | • Schedule appointment notification
• Access Google calender for scheduling through Application • Announcement board for LG representatives |
13/01/12 - 20/01/12 |
8 | • Intranet system for inventory management
• Inventory database design and setup • Intranet system user interface |
21/01/12 - 25/01/12 |
9 | • SMS notification of installer delivery
• Call notification to customer |
26/01/12 - 31/01/12 |
10 | • Retrieval of current date's job list
• Confirmation update of job status |
01/02/12 - 10/02/12 |
11 | • System Integration and testing | 11/02/11 - 24/02/12 |