Difference between revisions of "IS480 Team wiki: 2012T1 Rainbow Solutions"
Hajam.2009 (talk | contribs) |
Hajam.2009 (talk | contribs) |
||
Line 195: | Line 195: | ||
Process Flow</div> | Process Flow</div> | ||
<div style="padding:0.4em 1em 1em;"> | <div style="padding:0.4em 1em 1em;"> | ||
− | [[Image:RainbowProcessDiagram. | + | [[Image:RainbowProcessDiagram.png | center]] |
</div> | </div> | ||
|} | |} |
Revision as of 10:53, 13 August 2012
Welcome to Rainbow Solutions FYP Wiki!
|
Project Scope | Project Documentation | Project Management | Project Progress Summary | Quality of Product | Reflections |
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. |
Team Roles
|
Stakeholders
Supervisor
Sponsor and Client
|
Project Scope
|
Project Description
The focus of our project is to create Q-Ticket Mobile 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 Goals
This application aims to provide lawyers with a more convenient platform to request queue tickets for hearing cases. It also aims to be a centralised location where lawyers could obtain information related to Supreme Court as well as the law industry. 1. Reduce waiting time from x amount of time to y amount of time 2. Decreased number of re-queuing by x% due to poor information 3. Increased accessibility to Supreme Court as information is readily available on mobile |
Project Timeline
|
X-Factor
The application makes queuing easier. First, it allows user to register for queue from their comfortable location. Second, Geo-fencing allows the provider to prevent misuse of registration. If the party is not nearby the Supreme Court and they register for a queue and they are called in, it will become a wasted queue. Thirdly, it reduces waiting time for lawyers and crowding at the physical kiosks. This is a relatively new concept that can be widely used in many places. Many of us has the experience of waiting for a long period of time in queues, such as in hospitals and food outlets. With this new concept, user has the ability to eliminate waiting time and the time saved can be transferred and used for other more meaningful purposes. This application also allows user to be more connected with Supreme Court. By being able to access information such as events, hearing lists and pasts cases from mobile, the user would frequent the service to get more updates.
|
Deliverable
|
Process Flow
|
Story Board
|
Project Documentation
|
Features & Functions
Functional Requirements CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
BONUS
BONUS
BONUS
CORE
Security
Maintainability
Documentation
BONUS
Security
Compatibility
Use Case Diagram
Use Case Description To be updated once wiki made private. |
User Interface
ANDROID
Login Landing Page Queue Registration Hearing Lists
News Feed Way Finder Augmented Way Finder iOS
Login Landing Page Queue Registration Hearing Lists
News Feed Way Finder Augmented Way Finder |
Database Design
Entity Relationship Diagram To be updated once wiki made private. Logical Diagram To be updated once wiki made private. |
System Architecture
To be updated once wiki made private. |
Meeting Minutes
Team To be updated once wiki made private. Supervisor To be updated once wiki made private. Client To be updated once wiki made private. |
Presentations
Acceptance
Mid-Term Final |
Project Management
|
Schedule
Detailed project schedule with comparison between planned and actual duration can be found over the link below: |
Project Metrics
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. Formulation: For each iteration, calculate {[actual duration] – [planned duration] / [actual duration]}. Actions are taken based on table inside the metric and its corresponding percentage. 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
|
Technology Used
|
Project Progress Summary
|
Project Highlights
|
Our journey
|
Our Achievements
|
Quality of Product
|
Project Deliverable
|
Quality
|
Deployment
|
User Acceptance Testing
|
Reflections
|
Learning Outcome
|
Team Reflection
|
Individual Reflection
|
Supervisor Reflection
|
Client Reflection
|
References
|
Thank you for Visiting!
|