Difference between revisions of "IS480 Team wiki: 2012T1 Rainbow Solutions"
Hajam.2009 (talk | contribs) |
Hajam.2009 (talk | contribs) |
||
Line 8: | Line 8: | ||
{| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
| style="width:100%; vertical-align:top; border:1px solid #abd5f5; background:#f1f5fc;"| | | style="width:100%; vertical-align:top; border:1px solid #abd5f5; background:#f1f5fc;"| | ||
− | <div style="border-bottom:1px solid #abd5f5; background:#d0e5f5; padding:0.2em 0.5em; font-size: | + | <div style="border-bottom:1px solid #abd5f5; background:#d0e5f5; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> |
Rainbow Solutions</div> | Rainbow Solutions</div> | ||
<div style="padding:0.4em 1em 1em;"> | <div style="padding:0.4em 1em 1em;"> | ||
Line 72: | Line 72: | ||
|} | |} | ||
− | ===Team Goals= | + | <!------------------------------------Team Goals---------------------------------------> |
+ | {| cellspacing="0" cellpadding="0" style="margin:0 0 1em; width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #abd5f5; background:#f1f5fc;"| | ||
+ | <div style="border-bottom:1px solid #abd5f5; background:#d0e5f5; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Team Goals</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
+ | |||
+ | |||
+ | </div> | ||
+ | |} | ||
− | ==Project Scope | + | <!------------------------------------Project Scope---------------------------------------> |
+ | {| id="mainpage-welcome-box" style="margin:0 0 1em; width:100%; background:#f6f6f6; border:1px solid #ccc;" | ||
+ | | style="width:61%; text-align:center; white-space:nowrap; color:#000;" id="mf-welcome" | | ||
+ | <div style="font-size:150%; border:none; margin:0; padding:.1em; color:#000;">Project Scope</div> | ||
+ | |} | ||
− | ===Project Description= | + | <!------------------------------------Project Description---------------------------------------> |
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Project Description</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
The focus of our project is to create mobile queue booking application by leveraging on location based service technology which will enable the lawyers to do self-check-in while within a pre-defined radius from the building. | The focus of our project is to create mobile queue booking application by leveraging on location based service technology which will enable the lawyers to do self-check-in while within a pre-defined radius from the building. | ||
− | === | + | </div> |
+ | |} | ||
+ | |||
+ | <!------------------------------------Motivation---------------------------------------> | ||
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Motivation</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
+ | |||
+ | Currently the Queue services available for Lawyers are accessed through the Kiosk at the Supreme Court. This is a problem as Lawyers have to go to the Kiosk physically to register and wait near the Kiosk to check the queue status and access the hearing lists. There is a lot of waiting time as they do not know the timing of their hearing. By having a mobile application, the waiting time is reduced as they will be better informed of the status. This would increase the lawyers’ efficiency and productivity. Supreme Court is interested to invest in applications for Mobile Platforms as the trend is moving towards mobile. | ||
− | + | </div> | |
+ | |} | ||
− | ===Project Timeline= | + | <!------------------------------------Project Timeline---------------------------------------> |
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Project Timeline</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
− | |||
− | === Deliverable === | + | </div> |
+ | |} | ||
+ | |||
+ | <!------------------------------------X-Factor---------------------------------------> | ||
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | X-Factor</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
+ | |||
+ | |||
+ | </div> | ||
+ | |} | ||
+ | |||
+ | <!------------------------------------Deliverable---------------------------------------> | ||
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Deliverable</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
*'''Outcomes''': Mobile Web Application that is able to be deployed on Multiple Platforms, i.e. iOS, Android, Windows Mobile and BlackBerry<br> | *'''Outcomes''': Mobile Web Application that is able to be deployed on Multiple Platforms, i.e. iOS, Android, Windows Mobile and BlackBerry<br> | ||
Line 103: | Line 155: | ||
** Way Finder – to provide direction to Supreme Court building | ** Way Finder – to provide direction to Supreme Court building | ||
** Enhanced Way Finder - to use Augmented Reality to provide real-time direction with Google Street images. | ** Enhanced Way Finder - to use Augmented Reality to provide real-time direction with Google Street images. | ||
+ | </div> | ||
+ | |} | ||
+ | |||
+ | <!------------------------------------Process Flow---------------------------------------> | ||
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Process Flow</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
+ | [[Image:RainbowProcessDiagram.jpg | center]] | ||
+ | </div> | ||
+ | |} | ||
+ | |||
+ | <!------------------------------------Use Case---------------------------------------> | ||
+ | {| cellspacing="0" cellpadding="0" style="width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
+ | <div style="border-bottom:1px solid #fad67d; background:#faf6ed; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Use Case</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
+ | '''Use Case Diagram''' | ||
+ | |||
+ | '''Use Case Description''' | ||
+ | |||
+ | </div> | ||
+ | |} | ||
+ | |||
+ | |||
− | |||
− | |||
==Project Progress Summary== | ==Project Progress Summary== |
Revision as of 16:37, 11 August 2012
Welcome to Rainbow Solutions FYP page!
|
Rainbow Solutions
Rainbow Solutions is building a Q-Ticket Mobile Application for Supreme Court of Singapore. This solution would enhance the lawyers’ efficiency and productivity by reducing the waiting time and be better informed about the Queue Status and Hearing List. This application also allows Lawyers to stay up-to-date through RSS feeds about the latest developments in the law industry. |
Rainbow Solutions & Stakeholders
|
Stakeholders
Supervisor
Sponsor and Client
|
Team Goals
|
Project Scope
|
Project Description
The focus of our project is to create mobile queue booking application by leveraging on location based service technology which will enable the lawyers to do self-check-in while within a pre-defined radius from the building. |
Motivation
Currently the Queue services available for Lawyers are accessed through the Kiosk at the Supreme Court. This is a problem as Lawyers have to go to the Kiosk physically to register and wait near the Kiosk to check the queue status and access the hearing lists. There is a lot of waiting time as they do not know the timing of their hearing. By having a mobile application, the waiting time is reduced as they will be better informed of the status. This would increase the lawyers’ efficiency and productivity. Supreme Court is interested to invest in applications for Mobile Platforms as the trend is moving towards mobile. |
Project Timeline
|
X-Factor
|
Deliverable
|
Process Flow
|
Use Case
Use Case Diagram Use Case Description |
Project Progress Summary
Project Highlights
Our Journey
Our Achievements
Project Management
1. Schedule Overview
For information about the overview of our schedule, please click on the link below:
Schedule Overview - Rainbow Solutions
2. Detailed Project Schedule (Planned vs Actual)
Detailed project schedule with comparison between planned and actual duration can be found over the link below:
Detailed Project Schedule-Rainbow Solutions
3. Project Metrics
Metrics provides measuring units to depict values, constraints, durations, maximums and minimums. Our team decided to utilize three project metrics; Schedule Metric, Bug Metric, and Project Risk/Constraint Metric.
A. Schedule Metrics
The objective of the team's schedule metric is to review the progress of different iteration and perform necessary action on the corrective measures, based on calculated percentage. Schedule Metrics
Formulation: For each iteration, calculate {[actual duration] – [planned duration] / [actual duration]}. Actions are taken based on table inside the metric and its corresponding percentage.
B. Bug Metrics
The objective of the team’s bug metric is to track the level of complexity and severity of any present bugs. By doing so, we will analyze how these bugs are affecting the development progress of our project
Formulation: The total points will be based on the bug rating from the bug severity table, action will be taken based on its corresponding total points.
Project Risks
Quality of Product
Project Deliverable
Quality
Deployment
User Acceptance Testing
Reflections
Learning Outcome
Team Reflection
Individual Reflection
Supervisor Reflection
Client Reflection
References
- To view project snapshot at the Acceptance phase, see the Acceptance Page.