HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2010T2 Pointers"

From IS480
Jump to navigation Jump to search
Line 351: Line 351:
  
 
=== <font face="Hobo Std" size="+2" color="#bc944d">Sponsor Comment:</font> ===
 
=== <font face="Hobo Std" size="+2" color="#bc944d">Sponsor Comment:</font> ===
 +
Sometimes, the client writes a report to feedback on the system; this sponsor report can be included or linked from here.
 +
 +
<br>

Revision as of 00:58, 10 March 2011

Pointers Team Logo



Team Pointers

Team Members

Team Pointers

You can contact us at pointers.smu@gmail.com

Project Scope

Project Description

Customer satisfaction is a key consideration for Resorts World Sentosa (RWS). Hence, our goal is to maximise the patrons’ time at RWS and improve their experience. Collectively called PointIT, our project will consist of 3 systems. The 1st system is an Intelligent Integrated Itinerary Planner (IIIP) that helps patrons create a customised itinerary for their length of stay at RWS after they have selected their preferences. The 2nd would be a Smart Traveller system that allows a patron to access his customised itinerary via his smartphone so he will have the information regarding his itinerary at his fingertips. The 3rd is a Management Portal that will aid RWS Management Team in managing all the variables in RWS with create, read, update and delete functions.

PointIT Web Application

PointIT Web Application

Intelligent Integrated Itinerary Planner is a web-based system where patrons will be able to input his preferences based on parameters such as time, time of traveller, personality/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 variables as well as the estimated time required for a patron to stay at that variable.

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 variables and adjusting the duration spent at each variable. Once he has confirmed his selections and itinerary, a unique planner ID will be assigned to him.

Click here for the detailed requirements and features.

PointIT Mobile Web Application

PointIT Mobile Web Application

Smart Traveller System is a mobile web application where patrons will be able to view his personalised itinerary from the IIIP portal accessed through his smartphone. This is based on the unique planner ID assigned to him when he previously used the web application on a laptop/computer to create his customised itinerary. Using his planner ID, the patron will login and view his itinerary in a list view.

Smart Traveller 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 planner 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 “like” RWS and their customised itinerary on Facebook.
Click here for the detailed requirements and features.

PointIT Management Portal

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.

Stakeholders

Pointers' Stakeholders


Project Timeline

Project Schedule

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.

Project Highlights

What unexpected events occurred?

  • Team members too busy with other work
  • 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
  • ...
  • etc.


Our Journey

Click on each component for more details of our FYP journey so far.



Project Management

Individual Tasks

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 ALL UAT (Like Test Cases) / Capture all Flash functions + Flash Instructions Mobile Codes Mobile Codes ALL UAT (Like Test Cases) / Capture all mgmt/mobile functions / Management Instructions 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 Presentation UAT / Poster UAT Presentation UAT / Poster Presentation

Project Status

The project status highlights the changes to modules, the completion status, the confidence level and comments of the project.

Click here to view the full details.

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

Week 9

  • Algorithm
    • Add to greedy algorithm
    • Heuristics
  • UAT Test plan
    • Different devices
    • Different browsers
    • Different types of tests
    • Check that itinerary is as expected Eg. Adventurous…as opposed to leisure
      • Look at those more popular attractions: we should calculate ratings
      • Look for statistics (how many times a particular attraction comes out in itinerary)
      • Test on date sensitive events
  • Demo of Mobile Web Application (whatever we can show) with USS algorithm hopefully
  • Architecture diagram to show how our code is manageable and easy to understand


Click here to view Action Items from previous weeks

Project Risk

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.

Technical Complexity

Technology Used

Technology Used

Algorithm & Incorporating Living Analytics

Aim: Solve the Orienteering Problem
Solution: Construct an acyclic path beginning at a specific origin that maximizes the user preference while not exceeding a designated time limit
Methods used:
Greedy Algorithm

  • Simple and Straightforward
  • Shortsighted
  • Decisions made without basis of information at hand
  • Ignoring effect of decisions may have in future

Tree Heuristics

  • Introduced by Kantor and Rosenwein in Journal of the Operational Research Society in 1992
  • Generate a list of feasible path
  • Then select the most profit path from the list

--> Therafter generate a list of Priority Points over Distance table

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


Adobe Flash

  • 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


ASP.NET

  • Does not allow the webpage to accommodate different smart phone sizing, which we are still trying to solve



Quality of Product

Project Deliverables

Please click on items under Modules to view in more details*

Stage Specification Modules*
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
Screen Shots CRUD Customer, Trend Analysis
Design ER Diagram Version 1
Deployment Diagram PointIT's Deployment
Testing PointIT Management Portal Test Plan, UAT User Manual
PointIT Web Application Test Plan, UAT User Manual
PointIT Mobile Web Application Test Plan, UAT User Manual
Handover Manuals User Tutorial, Developer manual, Setup manual
Code client server
Deployment Diagram Instructions


Quality

Architecture design

Have you designed the architecture, use a design pattern, etc? Does your architecture address scalability, performance, reliability, availability, fault tolerance, usability, etc. Does your design address maintainability, flexibility, configurability, etc. Be brief here but you can link to diagrams or code detail pages. Do not repeat the technical complexity part, link to it if necessary.

Algorithm design

  • Consulted Associate Professor Lau Hoong Chuin of the School of Information Systems regularly
  • Algorithm adresses flexibility
  • ...


Deployment

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

For business users and testers, click on the links below to feedback after testing our system.
UAT Issue Tracker for the general public
UAT Issue Tracker for RWS business users

Reflections

Team Reflection:

Team Pointers

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.