Difference between revisions of "IS480 Team wiki: 2012T1 Rainbow Solutions"
Line 101: | Line 101: | ||
| style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | | style="width:100%; vertical-align:top; border:1px solid #fad67d; background:#faecc8;"| | ||
<div style="border-bottom:1px solid #fad67d; background:#FFC768; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | <div style="border-bottom:1px solid #fad67d; background:#FFC768; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
− | + | Project Goals</div> | |
<div style="padding:0.4em 1em 1em;"> | <div style="padding:0.4em 1em 1em;"> | ||
− | + | *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 | |
</div> | </div> | ||
Line 263: | Line 263: | ||
Detailed project schedule with comparison between planned and actual duration can be found over the link below:<br> | Detailed project schedule with comparison between planned and actual duration can be found over the link below:<br> | ||
[https://docs.google.com/spreadsheet/ccc?key=0At5-RZtLjDcodEtLWnl1am5XOXNxMDNHZ2UxSElWSEE#gid=16 Detailed Project Schedule-Rainbow Solutions]<br><br> | [https://docs.google.com/spreadsheet/ccc?key=0At5-RZtLjDcodEtLWnl1am5XOXNxMDNHZ2UxSElWSEE#gid=16 Detailed Project Schedule-Rainbow Solutions]<br><br> | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
</div> | </div> | ||
Line 290: | Line 281: | ||
Formulation: | Formulation: | ||
− | For each iteration, calculate {[actual duration] | + | For each iteration, calculate {[actual duration]/[planned duration]}. Actions are taken based on table inside the metric and its corresponding percentage. |
[[Image:Schedule.png | center]] | [[Image:Schedule.png | center]] | ||
Line 333: | Line 324: | ||
<div style="padding:0.4em 1em 1em;"> | <div style="padding:0.4em 1em 1em;"> | ||
[[Image:TechUsedUpdated850px.png | center]] | [[Image:TechUsedUpdated850px.png | center]] | ||
+ | </div> | ||
+ | |||
+ | |} | ||
+ | |||
+ | <!------------------------------------Learning Outcome---------------------------------------> | ||
+ | {| cellspacing="0" cellpadding="0" style="margin:0 0 1em; width:100%; background:white;" | ||
+ | | style="width:100%; vertical-align:top; border:1px solid #F2CEE0; background:#FFF5FA;"| | ||
+ | <div style="border-bottom:1px solid #BFA3B1; background:#F2CEE0; padding:0.2em 0.5em; font-size:130%; font-weight:bold;"> | ||
+ | Learning Outcome</div> | ||
+ | <div style="padding:0.4em 1em 1em;"> | ||
+ | |||
+ | *Integration of Business & Technology in a sector context | ||
+ | **Business IT Value Linkage | ||
+ | ***Understanding & creating the linkages between business strategy and business value creation (end-user engagement) <br><br> | ||
+ | |||
+ | *IT Architecture, Design & Development Skills | ||
+ | **System Requirements Specification Skills | ||
+ | ***Learn to elicit functional and non-functional requirements from clients, formalize them, and then develop a solution | ||
+ | **Implementation Skills | ||
+ | ***Increase Competency in JQuery and Android OS Developing Language <br><br> | ||
+ | |||
+ | *Communication Skills | ||
+ | **Presentation Skills | ||
+ | ***More experience in terms of project presentation to real client from real industry | ||
+ | **Writing Skills | ||
+ | ***Produce constant update to business client and supervisors | ||
</div> | </div> | ||
Line 359: | Line 376: | ||
'''Last Team Meeting''' | '''Last Team Meeting''' | ||
− | + | 25 Aug 2012 | |
'''Upcoming Team Meeting''' | '''Upcoming Team Meeting''' | ||
− | + | 8 Sep 2012 | |
'''Last Supervisor Meeting''' | '''Last Supervisor Meeting''' | ||
− | + | 22 Aug 2012 | |
'''Upcoming Supervisor Meeting''' | '''Upcoming Supervisor Meeting''' | ||
− | + | 14 Sep 2012 | |
'''Last Client Meeting''' | '''Last Client Meeting''' | ||
− | + | 29 Aug 2012 | |
'''Upcoming Client Meeting''' | '''Upcoming Client Meeting''' | ||
− | + | 12 Sep 2012 | |
</div> | </div> | ||
|} | |} |
Revision as of 07:45, 7 September 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. |
X-Factor
Queue management made easy by making it mobile with dynamic feedback on user location and notification to users. |
Project Goals
|
Deliverable
|
Project Documentation
|
Features & Functions
Functional Requirements
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
CORE
Non-Functional Requirements Security
Maintainability
Documentation
Security
Compatibility
|
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]}. 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
|
Learning Outcome
|
Project Progress Summary
|
Notification
Last Team Meeting 25 Aug 2012 Upcoming Team Meeting 8 Sep 2012 Last Supervisor Meeting 22 Aug 2012 Upcoming Supervisor Meeting 14 Sep 2012 Last Client Meeting 29 Aug 2012 Upcoming Client Meeting 12 Sep 2012 |