IS480 Team wiki: 2015T2 REALIS - Final

From IS480
Jump to navigation Jump to search

Links and Slides

View our final presentation slides 21 Apr 2015 Final
View our application HERE
View our pitch video HERE

Project Progress Summary

  • Current Iteration: 8, Final Presentation Preparation
  • 16 April 2015 - 22 April 2015
  • Till date, we have completed 100% of our functions.
  • We have conducted 5 user tests with URA staffs.

Project Highlights

  • Application is now deployed in URA's internal environment.
  • Main features of the application has been expanded from two to three (Data Visualization, Accessibility and Project Comparison).
  • Project Comparison Module has been added to the secondary scope on 13 March 2015 as per sponsor's request.
  • Login function has be removed from the tertiary scope.

Project Challenges

  • Displaying filtered results (approximately 25,000 property transactions) in a tabular and graphical view in less than 1 seconds.
  • Carefully crafting geospatial query to Postgres upon user’s input parameters.
  • Processing accessibility index algorithm using PostGIS database

Project Achievements

  • Successfully implemented all the functions using opensource libraries as per required by our stakeholders.
  • Live deployment within URA's internal environment for Property Research Analysts and Physical Planners to conduct their various analysis.
  • Conducted all user tests with real users (URA staff).

Project Management

Overall Timeline

REALIS Overall Schedule.png

Project Scope

REALIS Scope.png

Project Schedule (Planned vs Actual)

REALIS Schedule PvA.png

Iterations Planned Actual Days Changed Remarks
1 6 Oct 2014 – 15 Nov 2014 6 Oct 2014 – 31 Nov 2014 +15

Review on feedback from acceptance.
Preparation for final exams.

2 16 Nov 2014 – 31 Dec 2014 1 Dec 2014 – 31 Dec 2014 -15

Research on new technologies.

3 1 Jan 2015 – 21 Jan 2015 1 Jan 2015 – 31 Jan 2015 +7

Increased scope in data visualization. Developed more charts than required for clients to choose from.

4 22 Jan 2015 – 11 Feb 2015 1 Feb 2015 – 21 Feb 2015 -

On schedule

5 12 Feb 2015 – 25 Feb 2015 22 Feb 2015 – 3 Mar 2015 -8

Changed to preparation for and review after mid-term presentation.

6 26 Feb 2015 – 11 Mar 2015 4 Mar 2015 – 21 Mar 2015 +8

Required more time to develop Accessibility Module due to complexity in the algorithm used.
Required more time to debug on Data Visualization Module as there were lagged time when filtered data were selected.

7 12 Mar 2015 – 25 Mar 2015 22 Mar 2015 – 11 Apr 2015 +7

Additional module (Project Comparison) requested by client.

8 26 Mar 2015 – 8 Apr 2015 12 Apr 2015 – 22 Apr 2015 0

On schedule.

9 9 Mar 2015 – 22 Apr 2015 - -

Iteration removed.

Project Metrics


REALIS SM index.png


Bugs Index Per Iterations
REALIS Bugs index.png

Bugs Score Per Iteration
REALIS Bugs Score.png

Top 3 Risks

Risk Probability Impact Result Mitigation
Unsuccessful deployment of application in URA. High High A Do early deployment in URA 3 weeks prior to product delivery.
Underestimate the complexity of functions suggested by sponsors. High High A When developing functions:

1. Evaluate importance
2. Do research
3. Determine schedule feasibility before agreeing to sponsors request.

Processing massive data may lead to slow response time of the application. High High A
  1. Determine possible factors leading to slow response time (Database retrieval , cross filter, map interaction etc.)
  2. Research on methodologies to increase efficiency of identified factor

Technical Complexity

REALIS Tech Com.png

1. Crossfilter

REALIS Tech Com CF1.png
REALIS Tech Com CF2.png
REALIS Tech Com CF3.png

The complexity is to overwrite the default attribute writer in the library. This is complex because there is no method provided in the library to overwrite this. The attribute writer defines how to write the data in each table row and the format desired.

  1. Filtered results (25000 records) are displayed on charts within 1 second
  2. Create 10 dimensions for data visualization
  3. Use of cache to render the data for table (The most Critical Factor)

2. Formulate Geospatial Query

Transformation of user inputs to PostGIS SQL script for accessibility calculation.

  • Flexible selection of facilities and their importance rating
  • Create individual query tables based on selected facilities
  • Insert utility statements to construct main table as result output
  • Convert results into GeoJSON for frontend consumption

REALIS Tech Com Geo1.png
REALIS Tech Com Geo2.png
REALIS Tech Com Geo3.png

3. Accessibility Algorithm

REALIS Tech Com1a.png

1. Create predefined hexagons in Singapore
Radius = 100m, only centroids that contain transactions for computational efficiency

2. Each hexagon has an accessibility score
Calculate distance from its centroid to different facilities, in metres

3. For each centroid, calculate accessibility
Assign a score for each individual facility based on percentile distribution
Final Score = Total Score / Full Mark (Full Mark = 5 * no. of facilities)
Study percentile distribution of final scores, assign a rank & colour

4. Display hexagons & accessibility on map
Map view of all hexagons, which are coloured differently according to rank
When clicking a hexagon, a spider diagram showing score composition will pop up

Quality of Product

Project Deliverables

Stage Specification Modules
Project Management Minutes Minutes
Schedule Metrics Metrics
Requirements Design Specifications Project Scope
Analysis Use case Use case Diagram
Architecture Diagram Architecture Diagram
Workflow Diagram Workflow Diagram
Design UI Mockups UI Mockups
Testing User test plan User Tests


Quick loading time: Output of data is dynamically displayed within 1 second.


The application is successfully deployed in URA's internal environment.


Team Reflection

  • Manage client's expectations.
  • Challenge ourselves to work beyond our limits to add value to the application.
  • Learn new technologies given the short time-frame.
  • Learn to manage other modules' workload with FYP project.

Individual Reflection

Jeanne Sim

  • Executing a plan is different from a planned schedule. I have to be adaptable especially when hiccups surfaced during the schedule.

Jovin Hoon

  • Translating business requirement to technical requirements was not as simple as it seems. It is a two-way collaboration approach with the stakeholders.

Tan Yihao

  • Solving bugs is not as straight-forward as it seems, often times, an alternative method is required to solve them when a direct solution turns out to be unsuccessful.

Zheng Boyang

  • Learning new technologies within a short period was fulfilling. This broadens my knowledge in the various development tools.

"The team has come very far since the day we met and they have implemented very good ideas that we have not thought of. Certain features such as the accessibility and data visualization can be implemented in other applications by URA too."