Logiciel Mid Term Wiki

From IS480
Jump to navigation Jump to search

Return to Main

Project Progress Summary

View our Midterms Slide

View our Demonstration Walkthrough.

View our Project Overview & Description.

Project Status

  • Currently at Sprint 6 (14 Feb 2013 to 21 Feb 2013). View our Sprint Progress here.
  • Completed approx 60% of our Project.
  • Usability Testing conducted on Sprint 5. View our UT Results here.
  • Last Client Feedback Session on Sprint 4 (25 Jan 2013). View the Meeting Minutes here.
  • Upcoming Sprint 7 (21 Feb 2013 to 28 Feb 2013). Sprint 7 have not started, view our Product Backlog here.

Project Management

Overview of Project Schedule

Our Project currently has 9 Sprints in total. Below is the comparison between our current schedule and our initial schedule we drafted at acceptance.

View our Product Backlog to see the Complete Breakdown for each sprint.


Schedule/Burndown Charts

Below are all our Burndown chart since inception. These Burndown chart tracks how much work has been completed and the rate at which we complete our tasks during the sprint.

View our Logiciel Project Management Wikipage to see the breakdown of tasks for each sprint.

Overall Burndown Chart

Logiciel Overall Burndown.png

Sprints Burndown Comparison

Burndown Spreadsheets
Sprint 0 Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6
Logiciel Burndown Comparison.jpg

Risk Management Plan & Risk Backlog

The table below showcase our Outstanding Risks as of the current Sprint, Sprint 6.

View our Risk Backlog to see our mitigated Risks.

View our Risk Management Plan to find out how we identify Risks and formulate our action plan.

Risk Resolve-By Date Risk Score Action Plan Contingency Plan Current Status / Updates
Adoption resistance One risk our project faces is that of resistance in adopting our portal as a strategy formulation tool – to be used concurrently with SalesForceDotCom. As the use of SFDC is entrenched into our client’s business process, and managers and senior management are used to their usual modes of reporting and gathering data, a problem will be to integrate the use of our portal in a way that is as seamless as possible 26/4/2013 8 Dedicating a portion of the UAT to finding out the preferences of our client; assessing the tweaks or things we should implement to aid adoption Hold training and briefing sessions, as well as provide demonstrations of the use of our portal so as to allow the main groups of users to be familiarized with the portal. This will be more so catered when we hand over the project – should not all the groups be available, we will conduct the briefing/handover to the IT team at TR. NIL
Graphs Rendering Response time for graphs may be unacceptable by client. Usually graphs render under 1s, but it can take 3s sometimes 14/3/2013 6 Do caching for graphs. Have separate table that stores requests for json data, so that identical requests will read from the same data. If we are unable to implement caching, we will need to negotiate Quality Attributes with the client. If the change does not produce significant results, we will need to do logging to find out where is the delay NIL
Sentimental Analysis Library maui, may not be able to run effective topic extraction and possible polarity analysis on answers 21/2/2013 4 Perform thorough research on the functions to become more familiar with the technology Look for other implementations of KEA, or consider using vanilla KEA to perform task. Also consider dropping polarity of topic analysis Research in progress
Search Engine Apache Solr, may not be able to implement multiple document types on a single page 21/2/2013 4 Perform thorough research on the functions to become more familiar with the technology Stick with single document type for Solr Research in progress

Bug Tracking

View our Bug Log and Bug Metrics

Development Overview & Technical Summary

Technical Complexities

Read more about our Client Side, Server-Side, Development Patterns and Architecture Diagram on our Logiciel Technology page.

Find out about the technologies that we use, what we are trying to achieve, why we chose them, how we use them, what were the actual development work done while using them, how we felt using it, and what we learnt. Read all about it in a story form on our Technical Blog.

Technical Complexities Description What is it Complex?
Specialization List This Specialisation List is required for all Drill-down page. It ranks items such as Products, Deal Owners, Factors & Sales Teams so that the Sales Manager will know how well this item is performing with respect to that Drill-down page. Example: List of Deal Owners who are "Specialised" at selling a Thomson Reuter Products
  • The Ranking is based on more than 1 determinant. It is, in fact, an aggregation of 3 factors; Winning Rate (%), Total number of Deals Won (#), Total Value ($)
  • This Ranking algorithm is used in multiple drill-down pages for different items. Hence, the team faces a challenge to make the code highly reusable, scalable and robust.
  • Refer to this document for more details
Topological Graph Renders a Geographical World map that indicates the Strengths and Weakness of a particular Sales Factor. Sales Managers are able to click and zoom-in onto those region they are interested in to find out more details.
  • In order to correctly assigned the Strength & Weakness, we needed to plough through Geographical Data of areas and assign them to the orrect Countries. We also have to take into consideration Thomson Reuter Corporate Operations region divisions. i.e ASEAN vs South East Asia
  • We had to customised the zoom-in function for each region. In order to accomplish this, we needed to calculate the National Boundary of all the countries in the Thomson Reuters specifc region and map the zoom-in accurately with an enlarge view onto these countries.


Recent Usability test was conducted in Sprint 5, 30 Jan 2013 to 1 Feb 2013.

No. Objectives of Test
1 Find out the Clarity of our Graphs
2 Find out whether is the Graph Interaction Intuitive
3 Overall Look & Feel of the Application
4 Find Bugs in the Application
Scope of Test
Functionalities Graph Drilldown Result
Team Performance Tested Tested NA
Revenue by Location Tested Scheduled for Client UAT NA
Losses by Location Tested Scheduled for Client UAT NA
Product by Sales Tested Tested NA
Sales Factor Graphs Tested Scheduled for Client UAT NA
Search NA NA Tested

Qualitative & Quantitative Test Findings

Qualitative UT Findings Quantitative UT Findings
Qualitative UT Findings
Quantitative UT Findings
Changes Description/Illustration
Revamp Tooltip Content on Mouseover Logiciel-UT-Change1.png
Increased Ease in Navigating Back Logiciel-UT-Change2.png
Create a help Tooltip Logiciel-UT-Change3.png

Upcoming Client UAT

We have 2 Upcoming User Acceptance Tests (UAT). For more Details on our testing schedule, view our team Logiciel Testing Schedule.

  • UAT Phase 1 (27 Feb 13 or 6 Mar 13)
  • UAT Phase 2 (14 Mar 13 or 21 Mar 13)
User Acceptance Test Phase 1 User Acceptance Test Phase 2
Testers Amt. Testers Amt.
Taiwanese Sales Manager 1 Regional Sales Manager 2
Korean Sales Manager 1 Sales Representatives 2
Customer Interviewers 2
Administrators 2

User Acceptance Test Scope (Phase 1 Only)

Functionalities Graph Drilldown
Revenue by Location Completed in UT Yes
Losses by Location Completed in UT Yes
Sales Factor Completed in UT Yes
Competitor Trend Yes Yes
Export Yes No Export function in Drilldown page
Account Login Only Sales Manager can see Graph Dashboard Only Sales Manager can see Drilldown
Feedback Form Only Sales Representatives & Customer Interviewer Only Sales Representatives & Customer Interviewer
Manage Accounts Only Admins Only Admins
Manage Questions Only Admins Only Admins

Team Learning Outcomes



Amelia-Photo.jpg Amelia Low


  • Persevere to finding solutions to problems.


  • Revisit alternatives and keep trying.
Elvin-Photo.jpg Elvin Lim


  • Small Details snowball into Huge Successes.


  • Looks good, feels good but not necessarily essential.
Frank-Photo.jpg Frank Lim


  • Always experiment. You will never know what you will find!
Ryan-Photo.jpg Ryan Ng


  • The point of failure, probably occurance and follow up!


  • Proposals and suggestions. Is it technically feasible? Do we have the expertise to implement? Likehood of adoption?
QH-Photo.jpg Qian Hui


  • Failing to plan is planing to fail.


  • Rubbish in , Rubbish out Generate quality feedback which provide insights for the team to evaluate the application.
Vernon-Photo.jpg Vernon Lek


  • Each person have their own strengths, so always use your strengths to coach my peers. It not only clear your teammate’s obstacles, but it carries the team forward also.


  • In a team, you will help out each other and your peers will guide you along in times of difficulties. You don’t work alone on the project so you learn to appreciate each other in the group.