Difference between revisions of "IS480 Team wiki: 2012T1 Rainbow Solutions"
Line 196: | Line 196: | ||
<div style="background:#CD0000; width:5%; text-align:center">'''BONUS'''</div> | <div style="background:#CD0000; width:5%; text-align:center">'''BONUS'''</div> | ||
[[Image:RSAuthenticationBonus600px.png | center]] | [[Image:RSAuthenticationBonus600px.png | center]] | ||
+ | |||
<div style="background:#CD0000; width:5%; text-align:center">'''BONUS'''</div> | <div style="background:#CD0000; width:5%; text-align:center">'''BONUS'''</div> |
Revision as of 12:08, 17 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 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
|
Stakeholders
Supervisor
|
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. |
Project Timeline
|
X-Factor
This application allows user to be more connected with the law agency. 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. Furthermore, geo-fencing allows the law agency to track the location of the app user. This is a relatively new concept that have not been widely used in other applications. |
Deliverable
|
Project Documentation
|
Features & Functions
Functional Requirements
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
BONUS
BONUS
Non-Functional Requirements CORE
Security
Maintainability
Documentation
BONUS
Security
Compatibility
Use Case Diagram |
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
|
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 |