Difference between revisions of "Logiciel Finals Wiki"
Tllim.2010 (talk | contribs) |
|||
(44 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[[IS480 Team wiki: 2012T2 Logiciel|Return to Main]] | [[IS480 Team wiki: 2012T2 Logiciel|Return to Main]] | ||
==<div style="background: #006064; padding: 13px; font-weight: bold; line-height: 0.4em; text-indent: 20px;font-size:26px;"><font color= #ffffff>Project Overview</font></div>== | ==<div style="background: #006064; padding: 13px; font-weight: bold; line-height: 0.4em; text-indent: 20px;font-size:26px;"><font color= #ffffff>Project Overview</font></div>== | ||
− | View our '''[https://www.dropbox.com/s/ | + | View our '''[https://www.dropbox.com/s/98y2cp1k7yishoo/Team%20Logiciel%20IS480%20Final%20Presentation.pptx Finals Presentation Slides]''' |
View our '''[http://202.161.45.127/EagleEye/ Deployed Site]''' | View our '''[http://202.161.45.127/EagleEye/ Deployed Site]''' | ||
Line 108: | Line 108: | ||
| style="background:#ffffcc;"|Workflow - interview forms are likely to take longer than expected due to unforseen complexities and interaction between different roles||style="background:#ffffcc;"|28/2/2013||style="background:#ffffcc;"|6||style="background:#ffffcc;"|Increase the estimated points for this task. Will probably have to drop certain upcoming tasks | | style="background:#ffffcc;"|Workflow - interview forms are likely to take longer than expected due to unforseen complexities and interaction between different roles||style="background:#ffffcc;"|28/2/2013||style="background:#ffffcc;"|6||style="background:#ffffcc;"|Increase the estimated points for this task. Will probably have to drop certain upcoming tasks | ||
|- | |- | ||
− | | Search Engine - Apache Solr, may not be able to implement multiple document types on a | + | | 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 |
|- | |- | ||
| | | | ||
Line 221: | Line 221: | ||
===<div style="background: #009999; padding: 13px; font-weight: bold; line-height: 0.3em; text-indent: 20px;font-size:20px;"><font color= #ffffff>Project Deliverables</font></div>=== | ===<div style="background: #009999; padding: 13px; font-weight: bold; line-height: 0.3em; text-indent: 20px;font-size:20px;"><font color= #ffffff>Project Deliverables</font></div>=== | ||
− | {| border=" | + | {| border="0" |
− | |- style="background: | + | |- style="background:#009999; font color:#ffffff" |
− | |align="center"| Stage | + | |align="center style="background:#cc6600"| Stage |
− | |align="center"| Specification | + | |align="center style="background:#cc6600"| Specification |
− | |align="center"| Modules | + | |align="center style="background:#cc6600"| Modules |
|- | |- | ||
− | |rowspan="2"| Project Management | + | |rowspan="2" style="background:#ffcc99"| Project Management |
− | || Minutes | + | |style="background:#ffcc99"| Minutes |
− | || [https://www.dropbox.com/sh/l72mc260h9oe5br/xvDQHzwzoG Sprint Minutes], [https://www.dropbox.com/sh/8nstn6eor8l87tv/4fRZzP8jq1 Weekly Supervisor Meetings], [https://www.dropbox.com/sh/olq882ju77m8lb2/1LzANJ02EU Client Meetings] | + | |style="background:#ffcc99"| [https://www.dropbox.com/sh/l72mc260h9oe5br/xvDQHzwzoG Sprint Minutes], [https://www.dropbox.com/sh/8nstn6eor8l87tv/4fRZzP8jq1 Weekly Supervisor Meetings], [https://www.dropbox.com/sh/olq882ju77m8lb2/1LzANJ02EU Client Meetings] |
|- | |- | ||
− | || Metrics | + | |style="background:#ffcc99"| Metrics |
− | || [https://docs.google.com/spreadsheet/ccc?key=0AiHB7xA5vDvvdGlrUW01ZTZwenZielc1VGs1TDcwVXc#gid=0 Risk BackLog], [https://docs.google.com/document/d/1pIxTSaBjnp0Jx3DriCzpNWLEjEP11wI7qcqiBulhu5U/edit Risk Management Plan], [https://docs.google.com/spreadsheet/ccc?key=0AitZMTdeSyk6dHJJU21jR3NXd05Zdk5YanNHSDhBalE#gid=1 Bug Metric] | + | |style="background:#ffcc99"| [https://docs.google.com/spreadsheet/ccc?key=0AiHB7xA5vDvvdGlrUW01ZTZwenZielc1VGs1TDcwVXc#gid=0 Risk BackLog], [https://docs.google.com/document/d/1pIxTSaBjnp0Jx3DriCzpNWLEjEP11wI7qcqiBulhu5U/edit Risk Management Plan], [https://docs.google.com/spreadsheet/ccc?key=0AitZMTdeSyk6dHJJU21jR3NXd05Zdk5YanNHSDhBalE#gid=1 Bug Metric] |
|- | |- | ||
− | |rowspan="1"| Requirements | + | |rowspan="1" style="background:#ffffcc"| Requirements |
− | || Schedule||Project Timeline | + | |style="background:#ffffcc"| Schedule||style="background:#ffffcc"|[https://www.dropbox.com/s/e42od3bpo1k5n7r/Timeline.png Project Timeline] |
|- | |- | ||
− | |rowspan="3"| Analysis | + | |rowspan="3" style="background:#ffcc99"| Analysis |
− | || Use | + | |style="background:#ffcc99"| Use Case||style="background:#ffcc99"|[https://www.dropbox.com/s/4uml0hvucbbtpu3/Use%20Case%20Diagram.pdf Use Case][https://docs.google.com/spreadsheet/ccc?key=0AlCZlfsG7fcSdGlQTzZSOWNLQ2txMUNQVmhPN05jclE#gid=0 Use Case Scenario] |
|- | |- | ||
− | || Architecture Diagram||[https://wiki.smu.edu.sg/is480/Image:Architectural_Diagram.png Architecture Diagram] | + | |style="background:#ffcc99"| Architecture Diagram||style="background:#ffcc99"|[https://wiki.smu.edu.sg/is480/Image:Architectural_Diagram.png Architecture Diagram] |
|- | |- | ||
− | || Stakeholders||Internal Stakeholder | + | |style="background:#ffcc99"| Stakeholders||style="background:#ffcc99"|[https://wiki.smu.edu.sg/is480/Eagle_Eye%E2%80%99s_Stakeholders Stakeholder Information],[https://docs.google.com/spreadsheet/ccc?key=0ArFKIjb54F1IdEZaRG5vYUNyVVgtQUtubXlSb3Q1UFE#gid=0 Internal Stakeholder] |
|- | |- | ||
− | |rowspan="1"| Design | + | |rowspan="1" style="background:#ffffcc"| Design |
− | || Coding Considerations||Logiciel Technical Blog | + | |style="background:#ffffcc"| Coding Considerations||style="background:#ffffcc"|[http://logicieltechthoughts.wordpress.com/ Logiciel Technical Blog],[https://wiki.smu.edu.sg/is480/Logiciel_Technology Technologies] |
|- | |- | ||
− | |rowspan="1"| Testing | + | |rowspan="1" style="background:#ffcc99"| Testing |
− | || User Tests|| | + | |style="background:#ffcc99"| User Tests||style="background:#ffcc99"|[https://docs.google.com/presentation/d/1BRLQe5zYO7tusseNJ8vkd1le6Iwi7h6g2nGG5UlpBzw/edit#slide=id.gda4c4b96_2_99 UT 1 Plan Details],[https://docs.google.com/forms/d/1bVFrr54oNUiyBIKNNcbByMQpvu2p1_pndbkSNqZDQj4/viewform UT 1 Survey],[https://docs.google.com/presentation/d/12cfdOr-NHFDCJ2MrJveIThJcFG7EILDVU0s75aoMa0g/edit#slide=id.p UT 1 Results & Findings],[https://docs.google.com/document/d/13XJOn63fMVlXcAiVw5BYIaUk1zDFG9GEbcu4ybAxNCI/edit UT 1 Tools Use & Justification],[https://docs.google.com/presentation/d/1p-Nwly8nwNPbpx_0MW1JJ8Y1gmRhErJ3h544Tbgd43A/edit#slide=id.p UT 2 Plan Details],[https://docs.google.com/forms/d/150TO3OuM6c11twy4nbp-ugpYSikjMfkUW6QchKQiYCA/viewform UT 2 Survey],[https://docs.google.com/document/d/1eF_mxOf0_ZvLQIqvGULIgCGqWbUAptGxI0j7Aiee2kI/edit Test Schedule],[https://drive.google.com/folderview?id=0B7FKIjb54F1IWExmZ3NaUDdZNWc&usp=sharing UT 2 Other Documents],[https://docs.google.com/spreadsheet/ccc?key=0ArFKIjb54F1IdFhuU3dHZjg5bllpOGFWb0RhSExjcWc#gid=0 Test Cases],[https://docs.google.com/spreadsheet/viewform?formkey=dEt3U1lBblNidUlVbVBUWDNzeXZ2a0E6MQ#gid=0 Usability Test],[https://docs.google.com/spreadsheet/ccc?key=0Av7OMCSbuh1KdGNHb0NwendLbUhteGxnU3JmWEdoWVE&usp=sharing User Test Findings],[https://wiki.smu.edu.sg/is480/Eagle_Eye_Quality_%26_Assurance Client User Testings] |
|- | |- | ||
− | |rowspan="3"| Handover | + | |rowspan="3" style="background:#ffffcc"| Handover |
− | || Manuals | + | |style="background:#ffffcc"| Manuals |
− | || User tutorial, Developer manual, Setup manual | + | |style="background:#ffffcc"| User tutorial, Developer manual, Setup manual |
|- | |- | ||
− | || Code | + | |style="background:#ffffcc"| Code |
− | || Client server | + | |style="background:#ffffcc"| Client server |
|- | |- | ||
− | ||Deployment (On-Site)|| | + | |style="background:#ffffcc"|Deployment (On-Site)|| |
|- | |- | ||
Latest revision as of 12:29, 18 April 2013
Contents
Project Overview
View our Finals Presentation Slides
View our Deployed Site
View our EagleEye Overview & Description.
Project Status
- Ending our Final Sprint 9. View our Final Sprint 9 Sprint Burndown.
- Completed 2 Client User Testing (UT). View our UT1 Results & Findings and UT2 Results & Findings.
Project Management
Overview of Project Schedule
Our Project has 9 Sprints in total. Below is comparison between our Final-Term schedule and our Mid-Term Schedule after Mid-Terms Presentation.
|
View our Product Backlog to see the Overall Breakdown for each Sprint and view Individual Sprint Burndown Tracking for all 9 Sprints below.
Burndown Spreadsheets | |||||||||
Sprint 0 | Sprint 1 | Sprint 2 | Sprint 3 | Sprint 4 | Sprint 5 | Sprint 6 | Sprint 7 | Sprint 8 | Sprint 9 |
Schedule/Burndown Charts
Below are our Burndown charts for the last 3 Sprints. 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 all the breakdown of task for each sprint.
Overall Burndown Chart
Sprints Burndown Comparison
Risk Management Plan & Risk Backlog
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.
The table below highlights some of our more prominent risks and how we mitigated them.
Risk Issue | Resolved Date | Risk Score | Action Taken |
Client scoping | 31/1/2013 | 9 | To confirm all deliverables by 'resolve-by' date with client by proposing functions and confirming business value. |
Specific graph descriptions, data fields and purpose have not been determined. This may cause scope to drastically change if defined only late in the project. | 13/12/2012 | 9 | Risk can be avoided by liaising with sponsor to determine exact charts |
D3.js: This technology is mainly used for our visual analytics, and our team has no prior experience with this tool. Learning time may be high and the technology might not be able to produce the results we want. | 25/10/2012 | 6 | The team will find examples of applications of D3.js, and understand the Javascript library to see the feasibility. We will also have lessons for members to understand the code. |
Export Graphs: There are several technologies that cannot work with our application to export pngs of our graphs. Several new technologies have been found which might work but it's take quite a long time to learn and test out each one of them. | 5/2/2013 | 6 | Resolve the export function by the resolve-by date, or else consider dropping of the functionality |
Workflow - interview forms are likely to take longer than expected due to unforseen complexities and interaction between different roles | 28/2/2013 | 6 | Increase the estimated points for this task. Will probably have to drop certain upcoming tasks |
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 |
Bug Tracking
Below are the Bug Tracking Graphs for the entire project. View our Bug Log and Bug Metrics
- As noticed, there's a huge spike in bugs in Sprint 8. Sprint 8 marks the completion of the workflow, role management, and custom report functions. As these functions entails an integrated use of codes, we were bound to uncover bugs that were not covered in previous test cases. The complexity of these functions created bugs of its own as well.
- Although there are little functions to develop and test in Sprint 9, we discovered more bugs as we wrote more integrative and thorough test cases for existing functions.
Development Overview & Technical Summary
Technical Complexities
Read more about our Client Side, Server-Side, Development Patterns and Architecture Diagram on our Logiciel Technology page.
|
Other Challenges
|
Quality of Product
Project Deliverables
Stage | Specification | Modules |
Project Management | Minutes | Sprint Minutes, Weekly Supervisor Meetings, Client Meetings |
Metrics | Risk BackLog, Risk Management Plan, Bug Metric | |
Requirements | Schedule | Project Timeline |
Analysis | Use Case | Use CaseUse Case Scenario |
Architecture Diagram | Architecture Diagram | |
Stakeholders | Stakeholder Information,Internal Stakeholder | |
Design | Coding Considerations | Logiciel Technical Blog,Technologies |
Testing | User Tests | UT 1 Plan Details,UT 1 Survey,UT 1 Results & Findings,UT 1 Tools Use & Justification,UT 2 Plan Details,UT 2 Survey,Test Schedule,UT 2 Other Documents,Test Cases,Usability Test,User Test Findings,Client User Testings |
Handover | Manuals | User tutorial, Developer manual, Setup manual |
Code | Client server | |
Deployment (On-Site) |
Quality
Design Patterns
- Multiple thoughts have been put into design patterns, method naming, class designs, to make the code and service infrastructure reusable. It may be noted that within 1 sprint, we developed Custom Reports that made use of almost all data types due to the design of the classes. To see more details and examples, follow the link below to our patterns section.
- Link to patterns
Fault Tolerance
- To handle any server faults, users are directed to a user-friendly error page that abstracts the problem away from the user, and allows the user to re-login. An option is available on the page to view more details about the error when necessary.
- When creating a new deal, if the deal already exists(we know from an ajax request), a cue is provided to the user so that he/she knows to use another id.
- More covered under usability.
Performance Considerations
- To improve the loading times of graphs, we used a post-processing caching mechanism to cache all identical requests for graph data. The cache will stay for a day, or until the user 'force' updates the graphs. This improved loading times by 10 times, from an average of 659ms to 66ms.
- Care is taken when performing calculations in the back-end to make sure that as few iterations are used to accomplish a task as possible.
- Graph data are calculated on separate threads on the server while loading, to improve loading times.
Security
- To protect the user's privacy, the passwords are hashed using SHA1 hash function such that our database does not store any users' password.
- User access to pages are limited and controlled by their roles. When a user tries to access a page that he/she does not have access to, the user will be redirected to their home page.
Usability & Others
- The web-application is designed to prevent the user from doing wrong things. We take care to validate controls and limit choices that the users can make, and provide feedback to the user so that he/she knows what is going on.
- Drop-down lists are populated dynamically, they only contain options that are available in the database
- Cues(loading symbol, text) on the dashboard to indicate if the graphs are still loading, or if there are no available data.
Deployment
The following items will eventually be deployed and hosted on the client's server
- WAMP Server – Used to establish the connection with the database
- MySQL Workbench – Main database
- SQL Scripts – Imported into the database with a handful of administrator users
- Apache Tomcat Server – Application web server to handle various applications
- EagleEye Application – Main application that will be deployed and ready for use
- Java PHP Bridge – Enables the use of PHP script for exporting functions
- Apache Solr Search Engine – Leverage on the multi-core queries to access indexed data in the database
- Solr Configuration Files – Configured settings to allow Solr to run smoothly with Tomcat
- PHP for Windows
User Testing
Client UT Phase 1
Client User Testing 1 was conducted in Sprint 7, 5 Mar 2013 to 15 Mar 2013.
- Sample Size of 5 Thomson Reuters testers
- Role tested : Sale Managers & Senior Management
- View Sale Managers & Senior Management Survey.
- View Client User Testing 1 Finding.
|
Findings
Team
- How to deploy, configure and use a web-service based search engine: Apache Solr.
Description | Before | After |
Implement Help Tooltip for Clarity | ||
Increase Font Size for Readability | ||
Show Teams as Labels | ||
Show Currency Unit on Axis | ||
Show Competitors as Labels and Enhanced Competitor Name Display | ||
Show Products as Labels | ||
Add Period Filters and Timestamp to Dashboard |
Client UT Phase 2
Client User Testing 2 was conducted in Sprint 8, 2 Apr 2013 to 10 Apr 2013.
- Sample Size of 9 Thomson Reuters testers
- Role tested : Sale Managers & Senior Management , Technical support (Interviewer) , Sale representatives and Admin
- View Sales Managers & Senior Management Testing Survey and Manual.
- View Technical Support (Interviewer) Testing Survey and Manual.
- View Sales Representative Testing Survey and Manual.
- View Administrator Testing Survey and Manual.
- View Client User Test 2 Findings.
|
Findings
Changes & Developments
Description | Before | After |
Colour Gradient for increase distinctiveness | ||
Competitor is no longer compulsory |
Learning Outcomes
Team
- How to deploy, configure and use a web-service based search engine: Apache Solr amongst other technological tools.
- Communication is key - to stakeholder management, internal goal alignment and conflict management
- Prudence in planning - it is one thing to set a schedule with healthy pressure, but another thing to manage stakeholder's expectations on the schedule.