HeaderSIS.jpg

IS480 Team wiki: 2012T1 Rainbow Solutions

From IS480
Revision as of 22:54, 6 September 2012 by Wilfredphua.2008 (talk | contribs)
Jump to navigation Jump to search
Welcome to Rainbow Solutions FYP Wiki!
Project Scope Project Documentation Project Management Project Progress Summary Quality of Product Reflections


Rainbow Solutions
RainbowBanner

Rainbow Solutions is building a Q-Ticket Mobile Application for a organization. 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
RainbowSolRR.png
Stakeholders

Supervisor

Name Organization Designation
Debin GAO Singapore Management University Assistant Professor, SIS
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.

X-Factor

Queue management made easy by making it mobile with dynamic feedback on user location and notification to users.

X-Factor
    • Provide lawyers with a more convenient platform to request queue tickets.
    • Reduce waiting time from at least 47 minutes time to less than 5 minutes
    • Decrease number of re-queueing by x% due to poor information
    • Increase accessibility to the law firm as information will be readily available on Mobile Apps
Deliverable
  • Outcomes: Mobile Application that is able to be deployed on Multiple Platforms, i.e. iOS and Android
  • Value Statement: Efficient Queue System with increased efficiency and productivity
  • Scope:
    • Queue Ticket Registration
    • Search/View Hearing List
    • Access/Share news feeds
    • Way Finder
    • Augmented Way Finder
    • Search/View Past Cases
    • Lawyer Schedule
Project Documentation
Features & Functions

Functional Requirements


CORE
RSGeoLocation600px.png


CORE
RSAccountManagement600px.png


CORE
RSAppRegistration600px.png


CORE
RSAuthentication600px.png


CORE
RSQTRegistration600px.png


CORE
RSQStatusAlert600px.png


CORE
RSQStatusEnquiry600px.png


CORE
RSAccessHearingList600px.png


CORE
RSAccessNewsFeed600px.png


CORE
RSWayFinder600px.png


CORE
RSAuthenticationBonus600px.png


CORE
RSGeoFencing600px.png


Non-Functional Requirements

Security

  • Password Requirement - length, special characters, expiry, recycling policies
  • Inactivity Timeouts - 30 minutes, logout

Maintainability

  • Conform to the law agency's architecture

Documentation

  • Document for each item, including constraints and possible loops

Security

  • Open SSL for secured transmissions

Compatibility

  • Deploy on four platforms, iOS, Android, Windows and Blackberry


Presentations

Acceptance

To view project snapshot at the Acceptance phase, see the Acceptance Page.

Mid-Term

Final

Project Management
Schedule

Detailed project schedule with comparison between planned and actual duration can be found over the link below:
Detailed Project Schedule-Rainbow Solutions

Milestones 1 – Proposal Submission (20 June)
Iteration 1 – Account Management (18 June – 18 July)
Iteration 2 – App Registration / Authentication (18 July – 8 Aug)
Iteration 3 – Q-Ticket Registration / Queue Status Enquiry (10 Aug – 6 Sep)

Milestone 2 – Acceptance Presentation (17 Aug)

Milestone 3 – First UAT (7 Sep)
Iteration 4 – Geo-location (7 Sep – 28 Sep)

Milestone 4 – Prototype 1 (28 Sep)
Iteration 5 – Q-Status Notification (28 Sep – 19 Oct)

Milestone 5 – Mid-Term Presentation (3 Oct)

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.

Schedule.png

Schedule Metric

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.

Screen Shot 2012-08-17 at 1.55.05 PM.png
Screen Shot 2012-08-17 at 1.55.12 PM.png

Bug Metric

Project Risks
Technology Used
TechUsedUpdated850px.png
Project Progress Summary
Notification

Last Team Meeting

11 Aug 2012

Upcoming Team Meeting

18 Aug 2012

Last Supervisor Meeting

11 Aug 2012

Upcoming Supervisor Meeting

16 Aug 2012

Last Client Meeting

2 Aug 2012

Upcoming Client Meeting

14 Aug 2012