IS480 Team wiki: 2012T2 Team Tenacity Midterm Wiki
Project Progress Summary
Project Highlights
General Information
Please visit our website at: http://www.senghupauto.com
Please view our midterm slides here: Team Tenacity's Midterm Slides
Our proposal can be found here: Project Proposal
A short description of our project can be found here: Project Overview & Description
For more information on the functional specifications of the modules that we have built so far, please refer to: Functional Specifications
Acceptance to Midterm
We did not develop extensively for Acceptance because we were only required to show a demonstration of our application. We had built the login and inventory management modules in part and concentrated on working on the mockups (you can also see the evolution of the UI from its inception - during Acceptance, to its current form - during Midterms) for the whole application. We also wanted to set up the project management documents, complete the requirements gathering and come up with the algorithms for the analytics modules before Acceptance. Beyond Acceptance, we have completed almost all the core functionalities (excluding analytics) for the Midterms. We will be demonstrating the capabilities of our application in this Midterm presentation.
Change Management
Although, the whole fyp journey has been hectic thus far, nothing really drastic or serious has happened so far. Our project is generally going as planned. We are keeping to schedule and we are accommodating changes along the way. Our change management approach is listed below:
- Step 0: Reject all requests
- Step 1: Assess Request (Classify whether it is of High, Mid or Low priority)
- High - Will affect subsequent modules that are going to be built
- Mid - Important functions within modules will be affected
- Low - Cosmetic changes that do not affect functionality
- Step 2: Identify resources available
- Review schedule and see if there is resources available to cater for change management. Over a couple of sprints, we have learnt to be more conservative with our resource allocation so as to cater for possible request for change.
- Step 3: Final Decision
- Answer for each request = Yes or No. If yes - when?
A sample of our change management document is shown below:
Please refer to our change management document for more details: Change Management Document
Beyond Midterm
We will be making changes to the usability of our application based on the results of the first UAT that we had conducted. We will also be proceeding with the building of the analytic components. For more information on the analytics functions, please refer to: Analytics. A point to note is that we will be exploring the usage of 'R' programming to build our analytics components as well. We are proud to announce it as our X-Factor too!
Project Management
* Note that only sprints which involved development work are reflected in this section
Project Status
Functionality | Status | Confidence Level (0 - 1) | Comments | Links |
---|---|---|---|---|
Login and Inventory Management Functions | Fully deployed and tested 100% | 1 | Client has approved and is satisfied | Inventory |
Order Enquiry and Price Recommendation Functions | Fully deployed and tested 100% | 1 | Client has approved and is satisfied | Order, Analytics |
Order Fulfillment and Customer Management Functions | Fully deployed and tested 100% | 1 | Client has approved and is satisfied | Order, Customer |
Order Status Functions | Fully deployed and tested 100% | 1 | Client has approved and is satisfied | Order |
Role Based Access Control | 0% | 1 | We are confident of implement the RBAC function as we have thoroughly discussed it among ourselves and with our clients too | Role |
Implement Changes from UAT 1 | 0% | 1 | We are confident of changing all important aspects of usability based on the feedback received | |
Analytics - Warehouse Space Optimization | 0% | 0.5 | We have not started building it but we have obtained advice from Prof. Leong Thin Yin and our client on how we can go about building it | Analytics |
Analytics - Customer Behavioral Analysis | 0% | 0.5 | We have not started building it but we have obtained advice from Prof. Leong Thin Yin and our client on how we can go about building it | Analytics |
Finishing Touch: Implement Changes from UAT 2 | 0% | 1 | We are confident of changing all important aspects of usability based on the feedback |
Project Schedule (Planned Vs Actual)
Project is going as planned. Sprint 2 ended quite badly because of bad planning. We exceeded our plan by 16 days. However, we managed to re-calibrate our schedule to accommodate higher workload and change requests for the later sprints. Although, we managed to stick to our schedule almost 100% of the time for sprints 3 - 5, we were overworked during a couple of the sprints. This is evident from our Effort Metrics in the next section. Our metrics are based on our re-calibrated schedule that was drawn up immediately after acceptance. Our sprint reports will give a good indication of our progress since Acceptance too: Progress Reports
Sprints | Functionality | Proposal Planned Start | Proposal Planned Finish | Sprints | Functionality | Midterm Actual Start | Midterm Actual Finish | Comments |
2 | Login and Inventory Management Functions | 26 Oct 2012 | 01 Nov 2012 | 2 | Login and Inventory Management Functions | 26 Oct 2012 | 20 Nov 2012 | 100% of the Login functions and 30% of the Inventory Management Functions were completed prior to Acceptance. They were demonstrated during the Acceptance too. The remaining 70% of the Inventory Management Functions were completed after Acceptance. |
4 | Order Management CRUD Functions | 06 Nov 2012 | 15 Nov 2012 | 3 | Order Enquiry, Price Recommendation Functions | 17 Dec 2012 | 17 Jan 2013 | Had to take a break to study for exams and complete school work. |
5 | Order Management Invoice & DO Generation | 17 Nov 2012 | 19 Nov 2012 | 4 | Order Fulfillment and Customer Management Functions | 18 Jan 2013 | 29 Jan 2013 | |
6 | Order Management, Order Tracking & Enquiry | 07 Dec 2012 | 13 Dec 2012 | 5 | Order Status Functions | 30 Jan 2013 | 07 Feb 2013 | |
7 | Customer Management CRUD | 16 Dec 2012 | 19 Dec 2012 | 6 | Implement Changes from UAT 1 | 27 Feb 2013 | 28 Feb 2013 | We have not started to work on the feedback yet. We are confident of changing all important aspects of usability based on the feedback. |
Nothing planned | Role Based Access Control | 01 Mar 2013 | 01 Mar 2013 | We are confident of implement the RBAC function as we have thoroughly discussed it among ourselves and with our clients too. | ||||
8 | Analytics - Warehouse Space Optimization | 23 Dec 2012 | 21 Jan 2013 | 7 | Cluster Analytics | 02 Mar 2013 | 12 Mar 2013 | We have not started building it but we have obtained advice from Prof. Kam Tim Seong, Prof. Leong Thin Yin and our client on how we can go about building it. |
9 | Analytics - Customer Behavioral Analysis | 02 Feb 2013 | 10 Feb 2013 | 8 | RFM | 13 Mar 2013 | 24 Mar 2013 | We have not started building it but we have obtained advice from Prof. Kam Tim Seong, Prof. Leong Thin Yin and our client on how we can go about building it. |
10 | Price Recommendation | 25 Feb 2013 | 07 Mar 2013 | 9 | Finishing Touch & Deployment | 05 Apr 2013 | 14 Apr 2013 | We are confident of changing all important aspects of usability based on the feedback after they have been collected. |
11 | Finishing Touch | 12 Mar 2013 | 31 Mar 2013 |
Project Metric
Schedule Metric
Sprints | Functionality | Tracker Index | Health Status |
---|---|---|---|
2 | Login and Inventory Management Functions | 0.56 | Poor - Planned schedule exceeded by 16 days. Underestimated available resources and existing workload when committing to tasks. |
3 | Order Enquiry and Price Recommendation Functions | 1.00 | Good - On time |
4 | Order Fulfillment and Customer Management Functions | 1.00 | Good - On time |
5 | Order Status Functions | 1.00 | Good - On time |
Effort Metric
Sprints | Functionality | Tracker Index | Health Status |
---|---|---|---|
2 | Login and Inventory Management Functions | 0.60 | Too many tasks and too few hours allocated to complete tasks. Over-utilization of resources. Project members were overworked. |
3 | Order Enquiry and Price Recommendation Functions | 0.98 | Fairly good allocation of resources |
4 | Order Fulfillment and Customer Management Functions | 1.05 | Fairly good allocation of resources |
5 | Order Status Functions | 1.08 | Fairly good allocation of resources |
Kindly refer to: Project Schedule for more details on our schedule, and schedule and bug metrics
Bug Metric
Sprints | Functionality | No. of Easy Bugs (1 point) | No. of Moderate Bugs (5 points) | No. of Hard Bugs (15 points) | Total No. Bugs Found | Bugs Oustanding | Bug Points |
---|---|---|---|---|---|---|---|
2 | Login and Inventory Management Functions | 4 | 0 | 4 | 8 | 0 | 64 |
3 | Order Enquiry and Price Recommendation Functions | 0 | 5 | 0 | 5 | 0 | 25 |
4 | Order Fulfillment and Customer Management Functions | 4 | 2 | 0 | 6 | 0 | 14 |
5 | Order Status Functions | 1 | 0 | 0 | 1 | 0 | 1 |
Kindly refer to: Bug Metric for more details on our bug metrics
Project Risks
Please refer to our Risks page for the risks that we had identified prior to Acceptance
Risk | Type | Probability | Impact | Mitigation |
---|---|---|---|---|
|
Skill | High | High |
|
|
Skill | Medium | High |
|
|
Resource | High | High |
|
Technical Complexity
- Integrating 'R' with PHP
- Evaluating what the ‘right’ models would be
- Assessing the usefulness of the models
- Judging the value created by the models
- Formulating the Pricing Algorithm
- Recommending minimum selling price
- Applying Management Science Principles to project
- Implementing conceptualized idea into an algorithm
- For example, there is a 'calculator' within the Inventory module that automatically calculates the cost of parts based on prices when a car gets scrapped. This is based on the weights that are placed on each part. Within the Order module, there are business intelligence related features added throughout the process. First, there are price indicators, where appropriate, for each item that is added into the shopping cart. These include the minimum price, last ordered price, last quoted price and intelligence to hint to the sales staff if the quoted price needs to be dropped (based on the quote pattern of that particular item). Also, there are business rules that give rise to flags, that are being queried from the Inventory module. This enables the sales staff to make recommendations with more comprehensive information.
- AJAX implementations for search functionalities in order and inventory modules
- This allows a sales staff to find out more about a part with as little clicks or keystrokes as possible.
- Integrating FPDF external library into PHP application
- Understanding and utilizing the library to generate PDF invoices
Quality of Product
Intermediate Deliverables
Deployment
- Our application has been deployed on the server provided by Client via Cpanel Control Panel Interface and FTP transfer
- Client just has to access the link: Seng Hup Auto to access the system
- Client has to input username and password (sensitive information that cannot be placed here) to log into the system
- The security, business continuity and data backup will be fully taken care of by the service providers