IS480 Team wiki: 2013T2 SkyTeam Midterm Wiki
Project Progress Summary | Project Management | Product Quality | Reflections |
To view our midterm slides, please click here
Project Highlights
Project Scope Changes
Changes | Acceptance | Current |
---|---|---|
Functionality Names |
|
|
Priority |
|
|
Number of Functions |
|
|
Functions Completed | Functions Left |
---|---|
|
|
Changes in Requirements
Affected Functionality | Acceptance | Current | Managing Changes |
---|---|---|---|
(+) Added Point-of-Interest |
There was no functionality to view the Points-of-Interest (POI) like convenience stores, fire stations, supermarkets, hospitals, police stations, train stations around a specific building location. |
Our sponsors requested that we add this feature to find the POIs near the selected markers and to sort them according to the distance from the markers. This is meaningful for the end-users to estimate the social risk of the area, on top of the natural disaster risk that we calculated using the Risk Calculation Widget. |
|
(+) Added Historical Analysis |
There was no functionality to view the historical risk data of a particular location. Initially, our Interactive Graph function allowed us to view a static pie chart depicting the total risk of a particular building to floods, fires and earthquakes. Although it was meaningful, we felt we could develop this into something better. |
We decided to value-add to the Interactive Graph function by showing a dynamic graph that allows you to view the risk probabilities (flood, fire, earthquake, total) of a building with respect to time (years). |
|
Platform |
We were developing our Business Intelligence dashboard on Openshift. |
Our sponsors requested that we change platforms from Openshift to Google App Engine since it would be easier for them to manage and maintain the dashboard after completion. |
|
Data Mapping |
Initially, we intended to use Google Map Engine to display the shape files on our map, but after trying it out, we realised if we were to store them in the GME's database, we are unable to associate new attributes to the shapefiles. The database of GME is not robust enough. |
We embedded the shape files into Google Fusion Tables to view the shape files. |
|
Location Search |
Previously called "Spatial Query", this function allowed users to search for a specific building, landmark or location using latitude-longitude, postal-code and address from the client's uploaded data. There was a slight overlap with our "Filtering Tool" widget, because the filtering tool allows you to hand-pick datasets and/or attributes to display from the uploaded datasets. |
Users can search for a specific building, landmark or location using building name, latitude-longitude, postal-code and address, not just from the client's uploaded data. It's now similar to a Google Map Search. |
|
Interactive Map |
Upon hovering over a region, the area and perimeter is highlighted and region name pops up. |
Upon hovering over a location marker, a pop-up containing its building name, latitude and longitude appear instead. |
|
Widget Dashboard |
We intended to have a fixed sidebar on the left of the screen to let the user view a maximum of 3 widgets. However, the space allocation for most of the widgets was limited. This would also constrain the map size making it too small and difficult to navigate. |
Widgets are now draggable and not fixed. |
|
Project Challenges
Technical
Learning Geospatial Analytics Frameworks
- Prior to this project, none of us had exposure to geospatial analytics, let alone hear the phrase. Hence there was a huge learning gap to bridge in order for us to develop such a robust application.
- We needed to learn the lingo and tehcnical terms used in Geospatial Analytics e.g. Geovisualization, Thematic Mapping, Latitude-Longitude
- We needed to learn how to program, work with and style layers for our maps
- We needed to get familiar with using Google Fusion Tables for creating and embedding our shape files
- Resources like ArcGis helped us acquire a deeper understanding of the key concepts
- Prior to this project, none of us had exposure to geospatial analytics, let alone hear the phrase. Hence there was a huge learning gap to bridge in order for us to develop such a robust application.
Understanding Risk Assessment
- Similar to Geospatial Analytics, most of our statistics knowledge dates up to our compulsory Statistics 101 module, and is still very fundamental.
- We needed to read up on various flood, fire and earthquake risk assessment research papers before finalizing on our current model
- We consulted Prof Seema and Risk Experts from Aon Benfiled to get a deeper understanding on risk assessment, and enhance our risk algorithm
- Similar to Geospatial Analytics, most of our statistics knowledge dates up to our compulsory Statistics 101 module, and is still very fundamental.
Non-Technical
Accomodating Requirement Changes
- Having our sponsors request for additional functionalities, and change our development platform necessitated our team to have certain protocol in place for managing these changes.
- We carried out a Cost-Benefit Analysis during our meeting to assess the pros and cons of implementing such functions, we had a deeper look into the practicality and feasibility of accepting such changes
- The actions we took are reflected in the table above
- Having our sponsors request for additional functionalities, and change our development platform necessitated our team to have certain protocol in place for managing these changes.
Miscommunication between the Team and our Sponsors
- On a number of occassions, our team had to play the "waiting game" with our sponsors when we required data vital for the progress of our development.
- We now give our sponsors a deadline for when we need the data, and make a gentle reminder a day or two before to prompt them on the impending deadline. We also have a 1-2 day buffer in case they cannot meet the deadline.
- In the event a buffer after the stated deadline for data cannot be met, we readjust our project schedule and compromise on buffer days in other iterations.
- On a number of occassions, our team had to play the "waiting game" with our sponsors when we required data vital for the progress of our development.
Project Achievements
- 75% of our project has been completed, (9/12 functionalities)
- 8 out of 13 iterations completed
- 2 User Tests successfully conducted
- 1 Heuristic Evaluation successfully conducted