IS480 Team wiki: 2010T2 Pointers Secret Portal
- 1 Team Pointers
- 2 Project Scope
- 3 Project Progress Summary
- 4 Project Management
- 5 Quality of Product
- 6 Reflections
You can contact us at firstname.lastname@example.org
Customer satisfaction is a key consideration for Resorts World Sentosa (RWS).
Collectively called PointIT, our project will consist of 3 systems:
1. Flash Web Application
Helps patrons create a customised itinerary for their length of stay at RWS after they have selected their preferences.
2. Mobile Web Application
Allows a patron to access his already customised itinerary via his smartphone so he will have the information regarding his itinerary at his fingertips.
3. Management Portal
Aid the RWS Management Team in managing all the variables in RWS with Create, Read, Update and Delete functions.
PointIT Web Application
The Flash Web Application is a web-based system where the patron will be able to input his preferences based on parameters such as time, personality and lifestyle. The system will utilise a method called greedy algorithm to generate the itinerary. This algorithm will take into consideration factors such as the distance between attractions as well as the estimated time required for a patron to stay at that attraction.
The system encompasses intelligence by gathering information from the patrons’ preferences before generating an itinerary that optimises their preferences and duration of stay at RWS. Our web application also allows patrons the option to customise the itinerary after our system has generated a suggested one for him. Customisation options include that of adding or removing locations and adjusting the duration spent at each location. Once he has confirmed his selections and itinerary, he just has to input his unique email ID to enable retrieval on mobile phone later on.
Click here for the detailed requirements and features.
PointIT Mobile Web Application
The Mobile Web Application enables the patron to view his personalised itinerary from the Flash Web Application, accessed through his smartphone. Using his email ID previously inputted, the patron will login and view his itinerary in a list view.
The Mobile Web Application will display 2 itineraries:
- Patron’s overall itinerary of RWS
- USS (only available if this variable is part of his itinerary)
When a patron clicks on the USS component, the system will generate the USS itinerary based on the patron’s preferences (database will store the patron’s preferences based on his email ID). The USS itinerary will incorporate living analytics where it will take into consideration current environment attributes such as the weather and most updated queuing times as well.
Our system leverages on social networking too as patrons have the option to to “share” our PointIT application on Facebook.
Click here for the detailed requirements and features.
PointIT Management Portal
The Management Portal is a system where the Management Team at RWS is able to create, read, update and delete any information pertaining to the variables at RWS and USS.
Furthermore, this system is integrated where users need not access different software programs just to access the information. This will aid the various management personnel in updating information such as the waiting time of the rides at USS more conveniently. It also allows other authorised users to access this information immediately.
The Management Portal is essential as it is linked to the database where our web application and mobile web application will access the most updated information regarding the variables when planning the customised itinerary for the patrons at RWS.
Click here for the detailed requirements and features.
Click here for the detailed descriptions.
Project Progress Summary
The project had some bumps on the way, but the team has cooperate effectively and overcome it within the tight deadline.
- List of requirement changes
- Our initial recommendation for a USS project became a project for the whole RWS
- Client wanted a functional specification according to their industry standards, which was different from what we had
- Through recommendation from Professor Lau Hoong Chiun, we presented our project to the CMU LARC Director, Professor Steve Feinberg
- With the opening of the Living Analytics Research Centre (LARC) captured on news, our project gained some limelight as the pioneer project team for LARC
- Click here for the newspaper article
Click on each component for more details of our FYP journey so far.
Click here for our storyboard for final presentation!
Screenshots and descriptions of important functions in our systems.
Breakdown of tasks for the rest of the weeks ahead.
|Week||Kuan Liang||Cindy||Anqi||Joy||Wing Hei||Angeline|
|8||RWS Algorithm / Data Set||RWS Algorithm / Step by step guide / Improve Flash UI / Confirm all RWS locations||USS Algorithm/ Mobile Research||USS Algorithm/ Mobile Research||Overall UI / Update DB / Research||Tidy Up / Mobile Emailer / Retrieve ID, Type, Name, Description|
|9||Able to add new thumbnails into Flash dynamically||Wiki / Assist Flash / Edit Functional Specs for Flash||Mobile UI||Mobile UI||Mobile FB Like/Share / Edit Functional Specs for Mgmt Portal/Mobile||Convert Algorithm into ASP|
|10||Movement of thumbnails (eg. YourSingapore.com) / Support itinerary up to 3 days / Show Time Dimension||ALL UAT (Like Test Cases) / Capture all Flash functions + Flash Instructions (lack print screens)||Mobile Codes||Mobile Codes||ALL UAT (Like Test Cases) / Capture all mgmt/mobile functions / Management Instructions (lack print screens)||Convert Algorithm into ASP|
|11||Show Time Dimension||Test All Algorithm||Mobile Instructions||Mobile Instructions||Test All Algorithm||Update Waiting Time / Allow add and delete function for Mgmt Portal|
|12||Flash Update user form questions||UAT / Poster||UAT (lack print screens)||Presentation||UAT / Poster||Management Portal View and Update|
|13||Flash Update user form questions||UAT / Video||UAT (lack print screens)||Presentation||UAT / Video||Management Portal View and Update|
Project Schedule (Plan Vs Actual)
This section will compare the project plan during acceptance with the actual work done at the end of every week.
Click here for more details of our overall Project Schedule.
Click here for more details of our Project Schedule categorized by the 3 systems.
Project Action Items
- Send Prof our poster for vetting by next week
- Send email about video/storyboard next week
- Show the value-add to visitor
- Show how drag and drop is better than just dead browsing etc.
- Email UAT test plan next week
- Demo for all 3 systems 2 weeks from now
- Skeleton of presentation slides 2 weeks from now
Click here to view Action Items from previous weeks
This section shows the assumptions taken and the risk involved in the project with the respective mitigation steps taken. We have identified 3 different types of risks:
- Team Risk
- Client Risk
- Technology Risk
Click here to view the details of Project Risk.
Algorithm & Incorporating Living Analytics
Aim: Solve the Orienteering Problem
Solution: Click here
The USS itinerary incorporates living analytics to maximise patrons’ time at USS by using the following:
- Real time Waiting time of individual rides
- Real time distance of patrons from point to point
- A Script based language which is an unknown area to many programmers
- When some of the Flash variables transfer to ASP, some of the details may not reflect accurately
- Does not allow the webpage to accommodate different smart phone sizing, which we are still trying to solve
We use SVN to deploy on the UPL server in the school lab. By doing so, we can set it to update daily by just putting the necessary files into the correct folders.
During the debugging phase, we even set that duration to every 10 minutes.
Click here to understand our interesting way of deploying our solutions
Quality of Product
Please click on items under Modules to view in more details*
|Project Management||Minutes||Pointers' Meeting Minutes|
|Metrics||Pointers' Project Metrics|
|Presentation Slides||Acceptance, Midterm, Final|
|Requirements||Functional Requirements||Version 1|
|Analysis||Use Case||Version 1, Version 2, Version 3|
|Solution Architecture Diagram||Version 1, Version 2|
|Screen Shots||CRUD Customer, Trend Analysis|
|Design||ER Diagram||Version 1|
|Deployment Diagram||PointIT's Deployment|
|Testing||PointIT Management Portal||Test Plan, UAT|
|PointIT Web Application|
|PointIT Mobile Web Application|
|Handover||Manuals||User Tutorial, Developer manual, Setup manual|
- Consulted Associate Professor Lau Hoong Chuin of the School of Information Systems regularly
- Algorithm adresses flexibility
Click on the various links below for the deployed versions of our system.
|UPL Server||RWS Server|
|Web Application||Web Application|
|Mobile Web Application||Mobile Web Application|
|Management Portal||Management Portal|
User Acceptance Testing
Click here to access our personalized UAT Portal, which accesses the survey form for testing of the Web Application and Mobile Web Application
Click here for the survey form for testing of the Management Portal
Poster Day is held on the 20th April 2011, Wednesday at SMU Concourse T-Junction.
See you there!
Throughout the course of this project, we gained a higher understanding of web applications, and the advantages they bring rather than just using browser-based: available to a wider range of mobile phone users of different brands. Also, we had to explore different programming languages like C# and Flash, as opposed to the usual Java that were taught to us in school.
We learnt that communication and ample understanding of mutual team members were crucial to making a good team. There has to be discussions depicting our utmost emotions; if unhappy about a certain matter, instead of letting it remain unspoken because of the fear of conflicts and arguments, we have to voice it out. We have learnt to talk it through differences and to make sure everyone is on the same page about this project that we all call our own.
The takeaways so far, are a better understanding of the different programming languages, and various ways to track progress of the project. What seemed to be difficult and cumbersome to do during the first two years of our SMU life (like gantt charts and bug metrics) appears to be integrated well into our project now. In addition, we have also gained a deepened understanding and stronger bonds amongst the team, which is something hard to come by.
Benjamin Gan Reflection:
Describe in a paragraph, the key areas of learning or improvement. These should be personal areas of growth or learning. Each individual should list his/her effort, responsibility, actual contributions and personal reflection. Do not repeat team project contributions or member roles. Link if necessary.
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.