HeaderSIS.jpg

IS480 Team wiki: 2015T2 REALIS - Mid-Term

From IS480
Revision as of 19:41, 22 February 2015 by Jeanne.sim.2012 (talk | contribs)
Jump to navigation Jump to search
REALIS-Banner-main4.png
HOME   PROJECT OVERVIEW   PROJECT MANAGEMENT   DOCUMENTATION   THE TEAM
ACCEPTANCE MID-TERM FINAL

Overview

Slides for Mid-Term Review

REALIS Current Progress Phase5.png

We have completed the primary functionalities of the project scope - the primary architecture of the for each modules. We are currently progressing into the secondary module - Accessibility Module. The project schedule is segregated into different phases to provide an overview for each development phase.

Project Progress

Scope Changes:

  • Schedule is categorized in Phases, followed by Iterations in each Phases, to give a better overview on what the Team aims to achieve for each stage of development.

Time Constraint:

  • Time was required to explore new technologies for the application such as D3 library for Data-Visualization Module, Leaflet for Geo-Visualization Module and PostGIS for Geo-Processing Module.
  • Increased complexity in Phase 3, for Data-Visualization, in preparation for the first User Experience Test with URA to gather feedback on application.

Technical Difficulties:

  • Processing filtered data sets in PostGIS database.

Project Management

Project Status

REALIS ProjectSchedule MidTerm Scope.png

Changes that were made:

  1. Made Tabular View Module part of Data-Visualization Module because this involves just developing of a simple table.
  2. Made Coordinate Linked View Module part of Geo-Visualization Module because this involves interaction between clicking of icons on the map with the charts.
  3. Replaced Analytics Module with Accessibility Module because URA already has a group of Masters students helping them in this area.

About Accessibility Module:
This module involves identifying the accessibility of a property to the nearby facilities. The identified facilities serves the primary needs of the residents, based on walkability or transport. These facilities include bus-stops, primary and secondary schools, parks, community centers, etc. The purpose of having an Accessibility Index is to observe the relationship between Accessibility with the price of the Property.

Given that the main focus of this project is building PostGIS database, this module will be heavily reliant on PostGIS database through processing calculations at the back-end. Further explanation on PostGIS architecture will be in Technical Complexity.

Project Schedule (Plan Vs Actual)

Project Schedule (Plan Vs Actual) - Acceptance

REALIS ProjectSchedule Acceptance.png

Comments by The Team:

  • Scope of modules were overlooked. Some were too simple, while the rest were too complex.
  • Completion of modules were not ranked based on the primary to secondary needs. Instead, modules scheduled based on the importance and simplicity.
  • The team was unclear of the requirements and scope when this was planned, however, changes were made along the way, reflecting on the completion deadline of each modules.

Changes that were made:

  • Added phases to the schedule as a top-level overview for each iterations. The purpose of this is to give an overview of the development progress for the project.
  • Schedule has been edited after the first iteration in the picture above. The newly edited planned schedule is shown below.

Project Schedule (Plan Vs Actual) - Mid-Term

REALIS ProjectSchedule MidTerm PvA.png


REALIS ProjectSchedule MidTerm GranttChart.png
Overall
Phase Iteration Planned Duration Planned Start Planned End Actual Duration Actual Start Actual End Delay Comments
[1] Requirements Gathering 1 30 days 06/10/2014 05/11/2014 37 days 06/10/2014 12/11/2014 7 days Review application after acceptance. Reviewed schedule for iteration 2.
[2] Technology Exploration 2 48 days 13/11/2014 31/12/2014 48 days 13/11/2014 31/12/2014 0 days Different personal schedules for every teammates as everyone was travelling. Tasks were switched to research module to explore the technologies used for this project.
[3] Wire-frames and Mockup Designs 3 21 days 01/01/2015 21/01/2015 31 days 01/01/2015 31/01/2015 10 days Increased in scope for Data-Visualization module, and stopped development to solve high impact bugs found.
[4] Architecture Designs 4 21 days 01/02/2015 21/02/2015 21 days 01/02/2015 21/02/2015 0 days On track
Phase 1: Requirements Gathering
Task Planned Duration Planned Start Planned End Actual Duration Actual Start Actual End Delay Comments
Iteration 1 30 days 06/10/2014 05/11/2014 37 days 06/10/2014 12/11/2014 7 days Review application after acceptance. Reviewed schedule for iteration 2.
Bootstrap Module
CSV file upload 3 days 22/10/2014 24/10/2014 3 days 22/10/2014 24/10/2014 0 days NA
Convert data into GeoJSON objects 2 days 25/10/2014 26/10/2014 2 days 25/10/2014 26/10/2014 0 days NA
Geo-Visualization Module
Pin-Mapping, Tool-tip, Interactive Legend and Clustering 3 days 28/10/2014 30/10/2014 3 days 28/10/2014 30/10/2014 0 days NA
Testing and Debugging
Regression testing 1 day 31/10/2014 31/10/2014 1 day 31/10/2014 31/10/2014 0 days NA
Debugging 3 day 1/11/2014 3/10/2014 4 day 1/10/2014 4/10/2014 1 days NA
Phase 2: Technology Exploration
Task Planned Duration Planned Start Planned End Actual Duration Actual Start Actual End Delay Comments
Iteration 2 48 days 13/11/2014 31/12/2014 48 days 13/11/2014 31/12/2014 0 days Different personal schedules for every teammates as everyone was travelling. Tasks were switched to research module to explore the technologies used for this project.
Research Module
Heatmap and Chloropleth 48 days 13/11/2014 31/12/2014 48 days 13/11/2014 31/12/2014 0 days NA
Database Selection and Design 48 days 13/11/2014 31/12/2014 48 days 13/11/2014 31/12/2014 0 days NA
Charts and D3 Graphs 48 days 13/11/2014 31/12/2014 48 days 13/11/2014 31/12/2014 0 days NA
Phase 3: Wire-frames and Mockup Designs
Task Planned Duration Planned Start Planned End Actual Duration Actual Start Actual End Delay Comments
Iteration 3 21 days 01/01/2015 21/01/2015 31 days 01/01/2015 31/01/2015 10 days Increased in scope for Data-Visualization module, and stopped development to solve high impact bugs found.
Research Module
PostGIS architecture 31 days 01/01/2015 31/01/2015 31 days 01/01/2015 31/01/2015 0 days NA
Leaflet and mapping 31 days 01/01/2015 31/01/2015 31 days 01/01/2015 31/01/2015 0 days NA
Data-Visualization Module
Line Chart 4 days 06/01/2015 09/01/2015 8 days 06/01/2015 13/01/2015 4 days Stopped development and solved bug.
Histogram 3 days 14/01/2015 16/01/2015 3 days 14/01/2015 16/01/2015 0 days NA
Box Plot New task 4 days 16/01/2015 19/01/2015 0 days NA
Pie Chart New task 4 days 20/01/2015 23/01/2015 0 days NA
Testing and Debugging
Testing: User Experience Test at URA 1 day 28/01/2015 28/01/2015 1 day 28/01/2015 28/01/2015 0 days NA
Debugging: Dynamic interaction of charts and map 3 day 29/01/2015 31/01/2015 3 day 29/01/2015 31/01/2015 0 days NA
Phase 4: Architecture Designs
Task Planned Duration Planned Start Planned End Actual Duration Actual Start Actual End Delay Comments
Iteration 4 21 days 01/02/2015 21/02/2015 21 days 01/02/2015 21/02/2015 0 days NA
Geo-Processing Module
Develop schema for database 2 days 01/02/2015 02/02/2015 3 days 01/02/2015 03/02/2015 1 day This belongs to scripting instead of diagram.
Converting Geo JSON to X,Y Coordinates 2 days 03/02/2015 04/02/2015 2 days 04/02/2015 05/02/2015 0 days NA
Import facility database 2 days 05/02/2015 06/02/2015 4 days 06/02/2015 09/02/2015 0 days NA
Implement geospatial joint 3 days 07/02/2015 09/02/2015 3 days 10/02/2015 12/02/2015 0 days NA
Import result into database 1 day 10/02/2015 10/02/2015 Pushed to next iteration 0 days NA
Geo-Visualization Module
Generate heatmap for accessibility index 2 days 11/02/2015 12/02/2015 Pushed to next iteration 0 days NA
Polygon selection on map with dynamic charting New Task 7 days 11/02/2015 15/02/2015 3 days NA
Data-Visualization Module
Time Series Charts with horizontal line to reflect on percentile level 2 days 07/02/2015 08/02/2015 3 days 07/02/2015 09/02/2015 0 days NA
Box plot with selectable outliers 3 days 10/02/2015 12/02/2015 4 days 10/02/2015 13/02/2015 0 days NA
Dynamic charting per region interacting with map 2 days 17/02/2015 19/02/2015 2 days 17/02/2015 19/02/2015 0 days On track
Scatter plot on price vs accessibility index 3 days 14/02/2015 16/02/2015 Pushed to next iteration 0 days NA
Testing and Debugging
Testing: User Experience Test at URA 1 day 12/02/2015 12/02/2015 1 day 12/02/2015 12/02/2015 0 days NA
Debugging: Results of specific selection on dates reflecting on charts and map 4 day 13/02/2015 16/02/2015 4 day 13/02/2015 16/02/2015 0 days NA

Project Metrics

Schedule Metric

REALIS SM index.png

Bugs Metric

REALIS Bugs index.png

Project Risks

Technical Complexity

Quality of Product

Intermediate 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

Deployment

Testing

29 January 2015 & 12 February 2015 : User Experience Test
Objective Questions Asked Feedback Solution

To gather user experience feedback on the prototype after demonstrating the application to the participants.

  1. What information presented on the tooltip is considered irrelevant to you?
  2. Which charts are redundant?
  3. Which charts are difficult to understand?
  4. Which charts are useful for your analysis?
  5. What charts do you use in your daily job?
  6. Is the layout of the application aesthetically pleasing?
  7. What do you think of the placement of the map and charts?
  8. What other features would you like to see on this application?
  9. Which feature(s) you think is/are useful but needs improvement?

3 Property Analysts and 2 IT System Analysts

  1. Too many graphs/buttons to click on. It is confusing and aesthetically unpleasing. Graphs like bar chart, line chart and pie chart are enough
  2. Selection of base maps is not required. They are good with just one layout
  3. Include search by tenant, district and properties that are nearby and comparable, size of property
  4. PDF download of data in various format
  5. Select an area to choose multiple points
  6. Need to improve on accuracy
  7. Cut down on the amount of information shown in the tool tip to 4-5 lines
  8. Change the x-axis units of the graphs to month instead of days
  9. Fixed layout for the graphs are preferable
  10. Do drop down for categories like districts etc

3 Physical Planners

  1. Good to have an option to search by postal code
  2. Improve on the accuracy in mapping postal code to lat long
  3. Too many different combinations of pictures and colors in markers which are confusing
  4. Draw a polygon on the map to select multiple markers and show the results
  5. Add in the ability to have street view. This is important to the planners
  1. Select multiple markers to compare
  2. Search function for postal code, districts etc
  3. Cut down on the number of options available yet serves its purpose. Cut down on redundancies

Reflection

Jeanne Sim

Jovin Hoon

Tan Yihao

Zheng Boyang