Difference between revisions of "IS480 Team wiki: 2015T2 T-Club Final"
Line 33: | Line 33: | ||
− | % Completion for the iteration: | + | % Completion for the iteration: 90% |
<br> | <br> | ||
Revision as of 20:43, 9 April 2015
Home | Team T-Club | Project Overview | Project Management | Project Documentation |
Project Summary | Project Management | Quality of Products | Analytics | Reflections |
Contents
|
No. | Risk | Type | Likelihood | Impact | Risk Level | Risk Management | Status |
---|---|---|---|---|---|---|---|
1 | Change in requirements from Salesforce | Business | Medium | High | A | Project manager is to compare and determine the difference in scope and how it will impact the project. Inform project supervisor and course coordinator immediately and seek advice on how the team should proceed. Pm is to review the project plan and identify new milestones and delegate work to the respective members. | Activated |
2 | Insufficient technical knowledge to code out the function | Technical | Medium | High | A | PProject manager is to review the plan and track the progress of the team members. Prioritise the tasks that needs to be done first and schedule a meeting to relay these to the team members. Work on the unfinished task once they are done with the critical task | Activated |
3 | Unresolved backlog bugs | Technical | Medium | Medium | B | Backlog bugs are bugs that but will not affect the entire system. Bugs should be log down in the bug metrics and pm is to assign members to resolved the bug asap when they have nothing on their plate or to resolve it during the debugging phase | Activated |
Future Risk
No. | Risk | Type | Likelihood | Impact | Risk Level | Risk Management | Status |
---|---|---|---|---|---|---|---|
1 | Kaleea Owners unfamiliar with how to use the salesforce system to add products and track orders upon handling over the system to them | Technical | Medium | High | B | User manual with step by step guide to teach them how to use the system |
|} Click here for a comprehensive risk assessment for every iterations
Change Management
** Changes after Mid-Term
Click here to view the Mid-Term Change Metrics
Change Task/Event | Mitigation Plan |
---|---|
Low | Functions can be added to tertiary/good-to-have functions. Team will implement this function only if the core and secondary functions are done. |
Medium | Team is to only work on these function if the core functions are fulfilled. PM is to reschedule the task based on the level of priorities. |
High | Tasks is to be included in project schedule immediately. PM to reschedule tasks. Inform project supervisor if necessary to seek advice on how the team is going to proceed. |
Change Task/Event | Type | Requestor | Priority | Description | Member in charge | Date Changed | For Which Iteration | Inform Team? | Inform Supervisor? | Inform Sponsor? |
---|---|---|---|---|---|---|---|---|---|---|
Delay in Product Launch | Business | Team | High | Delay in the product launch due to problem deploying paypal live which resulted in the manual update of inventory | Gerald | 28/02/2015 | 10 | Yes | Yes | Yes |
Shift Product Suggestion function from iteration 10 to 11 | Technical | Team | High | Dropped this function due to some limitation in salesforce where all users share the same public cart when they are not logged in. Refer to project highlights for more info. | Hexing | 08/03/2015 | 12 | Yes | No | No |
Drop Checkout as Guest Function | Technical | Team | High | Dropped this function due to some limitation in Salesforce where all users share the same public cart when they are not logged in. Refer to project highlights for more info. | SMU | 02/04/2015 | 12 | Yes | Yes | Yes |
Technical Complexity
1. Checkout as Guest Function
- Each site has a special user with a user type called guest user type
- There is no session for guest browsing
- Each guest user (site) has a unique profile (public access settings)
- Guest profiles are called Guest User Licenses
These profiles are associated to guest user licenses which give the ability to read/create on standard objects and full CRUD on custom objects. However, by default no CRUD is given. Admins needs to enable the right level of access based on their flow
At the moment, no solution are available. Moreover, our team has consulted with both our sponsors and clients and we have come to an agreement to drop this functionality.
2. Paypal IPN
When a customer makes a payment on Kaleea, PayPal will post a notification to our server at the URL we specified. Included in this notification will be all the customer’s payment information (e.g. customer name, payment amount) as well as a piece of encrypted code. When our server receives a notification, it will then post the information, including the encrypted code, back to a secure PayPal URL. PayPal will authenticate the transaction and send confirmation of its validity back to our server. Receiving IPN is crucial as it triggers our update inventory function.
We have done the following steps to receive IPN on our web:
- Establish a publically visible end point
- Implement a custom controller to execute the behaviour
3. Change of Domain
Domain names are used in URLs to identify particular Web pages. For example, in the URL http://www.pcwebopedia.com/index.html, the domain name is pcwebopedia.com. As we all know, our e-commerce site are build on Force.com platform. Force.com Sites enables us to build and deploy public web sites and web applications using Force.com. These Web sites can be assigned custom domain names, letting us run Kaleea web sites on the platform. During the initial phase of the project, we register our domain name as tclub.force.com. This can only be done once. However, we run into issues when our client decide to host and change the domain name to their store name (Kaleea).
As a result,
- Force.com sites provides built-in registration and login logic
- Registration and Login method will throw error to Force.com sites domain
- Recoded the entire Registration & Login logic
- Catch all the wrong condition!
References:
https://help.salesforce.com/apex/HTViewSolution?id=000006778&language=en_US
http://www.webopedia.com/TERM/D/domain_name.html
https://developer.salesforce.com/page/An_Introduction_to_Force.com_Sites
Quality of Products
Intemediate Deliverables
Stage | Specification | Links |
---|---|---|
Project Management | Metrics |
|
Minutes | ||
Requirements | Prototype Mockups | |
Analysis | Use Cases Workflow | |
System Architecture Diagram | ||
Architecture Diagram | ||
Workflow | ||
Design | Technical Diagram | |
Class Diagram |
Deployement
Testing
Download a copy of our test plan here: UAT 1 | UAT 2 |
User Test | Date of Test | Objectives of Test | Number of participants | Age range |
User Test 1 (Client & Sponsors) | 13-Feb-14 | RE-ALIGN BUSINESS REQUIREMENTS
For more information, please click here |
4 | 25-30 |
User Test 2 (Users & Client) | 23-Feb-14 to 24-Feb-14 |
Evaluation of Usability For more information, please click here |
10 | 20 - 35 |
User Test 3 (Users & Client) | 5th -7th April | Sampling of Kaleea’ customers
For more information, please click here |
15 | 20 - 35 |
Analytics
Click here for more information on our analysis
Reflection
Team Reflection
Our team has learnt the importance of effective communications and teamwork to achieve a common goal. The regular meetings that we have allow us to ensure that all members are on the same page and none are neglected before we move on to our specific tasks. Also, we support and learnt from one another by lending a helping hand if anyone has difficulties in completing the tasks and move forward as a team. In any event there is any doubts, we also learnt to express our opinions via the meetings, whatsapp or email.