Difference between revisions of "IS480 Team wiki: 2011T1 Kopa Wheel"
(46 intermediate revisions by 2 users not shown) | |||
Line 86: | Line 86: | ||
<td>System Analyst</td> | <td>System Analyst</td> | ||
<td>Set up database and ensure smooth running of Database <br/> | <td>Set up database and ensure smooth running of Database <br/> | ||
− | Maintains Wiki | + | Maintains Wiki <br/> |
</td> | </td> | ||
</tr> | </tr> | ||
Line 103: | Line 103: | ||
|- | |- | ||
! style="width: 140px;" | Role | ! style="width: 140px;" | Role | ||
− | ! style="width: | + | ! style="width: 350px;" | Scope |
− | ! style="width: | + | ! style="width: 150px;" | In-Charge |
|- | |- | ||
| style="text-align: center" | Project Manager | | style="text-align: center" | Project Manager | ||
Line 116: | Line 116: | ||
* In Charge of User Interface Design | * In Charge of User Interface Design | ||
* Research on the most appropriate Technology | * Research on the most appropriate Technology | ||
− | * Main Developer of the | + | * Main Developer of the web portal |
* Provide guidance to team mates in need of help | * Provide guidance to team mates in need of help | ||
+ | * In Charge of Integration | ||
| style="text-align: center" | [mailto:james.koh.2007@business.smu.edu.sg James KOH Yi Zhi] | | style="text-align: center" | [mailto:james.koh.2007@business.smu.edu.sg James KOH Yi Zhi] | ||
|- | |- | ||
Line 128: | Line 129: | ||
| style="text-align: center" | System Architect | | style="text-align: center" | System Architect | ||
| style="text-align: Left" | | | style="text-align: Left" | | ||
− | * | + | * Organize the Data Flow of ISES |
− | * | + | * Research on the most appropriate Technology |
− | * | + | * Main Developer of the web portal |
+ | |||
| style="text-align: center" | [mailto:feixianghe.2008@sis.smu.edu.sg HE Feixiang] | | style="text-align: center" | [mailto:feixianghe.2008@sis.smu.edu.sg HE Feixiang] | ||
|} | |} | ||
Line 227: | Line 229: | ||
##User Subscription | ##User Subscription | ||
##Builder | ##Builder | ||
− | For detailed scope, please click [[Media:Kopa Wheel Project Scope | + | <b> For detailed scope, please click [[Media:Kopa Wheel Project Scope Final.pdf | here.]]</b> <br> |
====Project Documentation==== | ====Project Documentation==== | ||
{| class="wikitable" style="border: 5px solid #C7A317;" | {| class="wikitable" style="border: 5px solid #C7A317;" | ||
|- | |- | ||
− | ! style="width: | + | ! style="width: 200px; background: black; color: white" | Specifications |
! style="width: 200px; background: black; color: white" | Documents | ! style="width: 200px; background: black; color: white" | Documents | ||
|- | |- | ||
Line 248: | Line 250: | ||
|- | |- | ||
| style="text-align: center; background: white" | Corporate Client Manual Guides | | style="text-align: center; background: white" | Corporate Client Manual Guides | ||
− | | style="text-align: left; background: white" | | + | | style="text-align: left; background: white" | [[Media:CSISG Online User Manual for CS.pdf | User Manual for Corporate Clients]] |
|- | |- | ||
| style="text-align: center; background: white" | Administrator Manual Guides | | style="text-align: center; background: white" | Administrator Manual Guides | ||
− | | style="text-align: left; background: white" | | + | | style="text-align: left; background: white" | [[Media:CSISG Online User Manual for Administrators.pdf | User Manual for Administrators]] |
|- | |- | ||
| style="text-align: center; background: white" | Deployment Manual Guides | | style="text-align: center; background: white" | Deployment Manual Guides | ||
− | | style="text-align: left; background: white" | | + | | style="text-align: left; background: white" | [[Media:CSISG Online Deployment Details.pdf | CSISG Online Deployment Guide]] |
|} | |} | ||
− | ==== | + | |
− | [[ | + | ====Technologies Used==== |
+ | [[Image:Technologies used.PNG | Technologies Used ]] | ||
<br/> | <br/> | ||
− | + | Please refer to [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel#Documentation detailed explanation] of what each of the technology is about and applied in the development of our web portal. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel | ||
− | |||
</div> | </div> | ||
<div style="width:800px; height:80px; clear:both;"></div> | <div style="width:800px; height:80px; clear:both;"></div> | ||
Line 299: | Line 293: | ||
On top of this, we will be also adopting a part of the Scrum methodology as we will be holding weekly sprint(iteration) review meetings with our client. This is to ensure that the objectives set out at the start of each sprint (iterations) has been met at the end of the sprint (iterations) before the next sprint (iterations) begins. The Scrum approach will also allows us to understand the complex business sce | On top of this, we will be also adopting a part of the Scrum methodology as we will be holding weekly sprint(iteration) review meetings with our client. This is to ensure that the objectives set out at the start of each sprint (iterations) has been met at the end of the sprint (iterations) before the next sprint (iterations) begins. The Scrum approach will also allows us to understand the complex business sce | ||
− | + | ||
====Project Schedule==== | ====Project Schedule==== | ||
− | |||
<b>Milestones</b> | <b>Milestones</b> | ||
<br/> | <br/> | ||
− | [[Image: | + | [[Image:Planned vs schedule.jpg | 600px ]] |
Click [[Kopa Wheel Project Schedule|<font size="3"><b><u>here</u></b></font>]] to view the detailed project schedule. | Click [[Kopa Wheel Project Schedule|<font size="3"><b><u>here</u></b></font>]] to view the detailed project schedule. | ||
Line 364: | Line 357: | ||
|} | |} | ||
--> | --> | ||
− | |||
For detailed schedule in gantt chart, please click [[Media:Kopa Wheel's Schedule v1.7.pdf | here.]] | For detailed schedule in gantt chart, please click [[Media:Kopa Wheel's Schedule v1.7.pdf | here.]] | ||
− | |||
− | |||
====Change Request Management==== | ====Change Request Management==== | ||
− | |||
<b>Change Request Log</b><br/> | <b>Change Request Log</b><br/> | ||
This is a change request document that keeps a record of all the changes in requirements.[[Media:Change Request Log.xlsx | Click here to view.]]<br/><br/> | This is a change request document that keeps a record of all the changes in requirements.[[Media:Change Request Log.xlsx | Click here to view.]]<br/><br/> | ||
Line 384: | Line 373: | ||
! style="width: 60px; background: black; color: white" | UAT | ! style="width: 60px; background: black; color: white" | UAT | ||
! style="width: 400px; background: black; color: white" | Description | ! style="width: 400px; background: black; color: white" | Description | ||
− | ! style="width: | + | ! style="width: 200px; background: black; color: white" | Date |
! style="width: 110px; background: black; color: white" | Time | ! style="width: 110px; background: black; color: white" | Time | ||
! style="width: 200px; background: black; color: white" | UAT Test Scripts | ! style="width: 200px; background: black; color: white" | UAT Test Scripts | ||
Line 391: | Line 380: | ||
| style="text-align: center; background: white" | UAT 1 | | style="text-align: center; background: white" | UAT 1 | ||
| style="text-align: left; background: white" | The purpose of this UAT is to conduct a Functional Testing with our client(ISES) and their Corporate client. We have managed to get 1 UOB Client & 4 ISES Staff to do the User Acceptance Test. The UAT is guided with the test scripts provided. | | style="text-align: left; background: white" | The purpose of this UAT is to conduct a Functional Testing with our client(ISES) and their Corporate client. We have managed to get 1 UOB Client & 4 ISES Staff to do the User Acceptance Test. The UAT is guided with the test scripts provided. | ||
− | | style="text-align: left; background: white"| 20 September 2011 | + | | style="text-align: left; background: white"| |
+ | *19 & 20 September 2011 | ||
| style="text-align: left; background: white" | 10:30am | | style="text-align: left; background: white" | 10:30am | ||
| style="text-align: left; background: white"| | | style="text-align: left; background: white"| | ||
Line 402: | Line 392: | ||
| style="text-align: left; background: white" | This UAT has been divided into 2 parts: functional test and usability test. The objective of functional test is to get our client and their corporate clients to test the functionality and the usability of the web portal. Whereas for the usability test, the objective was to get both technical and non-technical students to test out the usability of the web portal. | | style="text-align: left; background: white" | This UAT has been divided into 2 parts: functional test and usability test. The objective of functional test is to get our client and their corporate clients to test the functionality and the usability of the web portal. Whereas for the usability test, the objective was to get both technical and non-technical students to test out the usability of the web portal. | ||
| style="text-align: left; background: white"| | | style="text-align: left; background: white"| | ||
− | *9 & 10 November | + | *<b>Functional Test</b> |
− | *9 to 15 November | + | **9 & 10 November |
− | | style="text-align: left; background: white" | | + | *<b>Usability Test</b> |
+ | **9 to 15 November | ||
+ | | style="text-align: left; background: white" | 11:30am | ||
| style="text-align: left; background: white"| | | style="text-align: left; background: white"| | ||
*[[Media:User Acceptance Testing 2 - Corporate Client SINGTEL.pdf | Scripts for Corporate Clients]] | *[[Media:User Acceptance Testing 2 - Corporate Client SINGTEL.pdf | Scripts for Corporate Clients]] | ||
Line 413: | Line 405: | ||
====Risks==== | ====Risks==== | ||
+ | =====Identified Risks===== | ||
+ | Identified Risk at the start of the project: | ||
+ | {| class="wikitable" style="border: 5px solid #C7A317;" | ||
+ | |- | ||
+ | ! style="width: 200px; background: black; color: white" | Category | ||
+ | ! style="width: 200px; background: black; color: white" | Detailed Explanation | ||
+ | |- | ||
+ | | style="text-align: center; background: white" | Project and Team Risks | ||
+ | | style="text-align: left; background: white" |[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel/Project_and_Team_Risks Project and Team Risks] | ||
+ | |- | ||
+ | | style="text-align: center; background: white" | Client Relationship Risks | ||
+ | | style="text-align: left; background: white" |[https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel/Client_Relationship_Risks Client Relationship Risks] | ||
+ | |- | ||
+ | | style="text-align: center; background: white" | Technology Risks | ||
+ | | style="text-align: left; background: white" | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel/Technology_Risks Technology Risks] | ||
+ | |- | ||
+ | | style="text-align: center; background: white" | Resource Risks | ||
+ | | style="text-align: left; background: white" | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel/Resource_Risks Resource Risks] | ||
+ | |- | ||
+ | |} | ||
+ | |||
+ | =====Risks Occurred in the duration of project===== | ||
+ | |||
Week 2 - Dependency Risk <br/> | Week 2 - Dependency Risk <br/> | ||
Week 3 - Technology( R Scripts) & Resource Risk <br/> | Week 3 - Technology( R Scripts) & Resource Risk <br/> | ||
Week 4 - Technology( R Scripts) & Unexpected Difficulty of Admin Function <br/> | Week 4 - Technology( R Scripts) & Unexpected Difficulty of Admin Function <br/> | ||
Week 5 - Technology ( R Scripts & Graphiz) <br/> | Week 5 - Technology ( R Scripts & Graphiz) <br/> | ||
− | + | Week 8 - Technology (D3 Technology)<br/> | |
− | <br> | + | [[Image:Risk occurance.JPG]] |
− | [ | ||
− | |||
− | [ | ||
− | |||
− | |||
====Metrics==== | ====Metrics==== | ||
− | 1. Schedule Metric <br> | + | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel/Schedule_metrics 1. Schedule Metric] <br> |
− | 2. Bug Metric <br> | + | [https://wiki.smu.edu.sg/is480/IS480_Team_wiki:_2011T1_Kopa_Wheel/Bug_metrics 2. Bug Metric] <br> |
− | + | [[Kopa Wheel Metrics | <b>3. Burn up Chart</b>]] | |
− | + | <br/> | |
====<font face="Segoe UI" color="black" >Collaboration Tools</font>==== | ====<font face="Segoe UI" color="black" >Collaboration Tools</font>==== | ||
Line 435: | Line 445: | ||
====Technical Complexity==== | ====Technical Complexity==== | ||
− | [[Image: | + | [[Image:Technology architecture.jpg | 600px ]] |
====Meeting Minutes Repository==== | ====Meeting Minutes Repository==== | ||
Line 443: | Line 453: | ||
<b>Yuting</b> | <b>Yuting</b> | ||
<ul> | <ul> | ||
− | <li>Learn about managing and organizing the project with | + | <li>Learn about managing and organizing the project with various stakeholders </li> |
<li>Learn new tools and understand how these tools can help to transform business requirements into an online portal</li> | <li>Learn new tools and understand how these tools can help to transform business requirements into an online portal</li> | ||
</ul> | </ul> | ||
Line 449: | Line 459: | ||
<b>James</b> | <b>James</b> | ||
<ul> | <ul> | ||
− | <li> | + | <li>The amount of effort to bring a seemingly possible scenario to fruition is more than expected</li> |
− | <li> | + | <li>Keeping the team motivated is very important. Finding a source of motivation for the team is difficult</li> |
</ul> | </ul> | ||
Line 502: | Line 512: | ||
**[http://code.google.com/p/canviz/ '''canviz'''] <b>:</b> Visualisation of dot language on html | **[http://code.google.com/p/canviz/ '''canviz'''] <b>:</b> Visualisation of dot language on html | ||
**[http://www.graphviz.org/ '''Graphviz'''] <b>:</b> Converts dot language into various outputs, it will feed canviz | **[http://www.graphviz.org/ '''Graphviz'''] <b>:</b> Converts dot language into various outputs, it will feed canviz | ||
+ | **[http://code.google.com/p/wkhtmltopdf/ '''WKHTMLTOPDF''']<b>:</b> Converts our data into PDF Format | ||
+ | **D3 Technology | ||
<br/> | <br/> | ||
*Client Website | *Client Website | ||
**[http://www.smu.edu.sg/centres/ises/ '''The Institute of Service Excellence at SMU''' (ISES)] | **[http://www.smu.edu.sg/centres/ises/ '''The Institute of Service Excellence at SMU''' (ISES)] |
Latest revision as of 14:16, 25 November 2011
Overview
Final Wiki Page
Click here to view final wiki page.
Midterm Progress Wiki Page
Click here to view midterm progress wiki page.
Team Members
Role | Scope | In-Charge |
---|---|---|
Project Manager |
|
Wee Yuting |
System Analyst (UI & PHP & Database) |
|
James KOH Yi Zhi |
System Analyst (R Language & Linux Environment) |
|
PAN Liang Hua |
System Architect |
|
HE Feixiang |
Stakeholders
Role | Name | Position | Project Involvement |
---|---|---|---|
Client | Marcus Lee | Academic Director for the Institute of Service Excellence at SMU (ISES) | Provide user requirements
Provide feedbacks |
ISES Analysts | ISES Analysts provide data analysis and manage the web portal | Provide technical and administrator requirements | |
Advisors/Practitioners | Benjamin GAN Kok Siew | Practice Associate Professor | Provide guidance and advices to the team |
Beneficiaries | Corporate Clients of ISES | Marketing Department of the Corporate Clients of CSISG | Provide user requirements |
Driving Singapore's Service Excellence
Driving Singapore's Service Excellence is an initiative developed by the Institute of Service Excellence at SMU (ISES), in an aim of raising service standards and promoting a culture of service excellence in Singapore.
Project Overview
We have built an interactive and dynamic web portal for its corporate subscribers to better understand the various service indices, such as the Customer Satisfaction Index of Singapore (CSISG). These indices offer businesses an objective appraisal of customer satisfaction levels of their company and its competitive insights into other organisations industry wide.
Business Process
Scope
Project Description
The aim of the project, Driving Singapore's Service Excellence, is to build an interactive and dynamic web portal that allows corporate customers to better understand their company's customer satisfaction through analyzing the Customer Satisfaction Index. It also allows them the freedom to individually create their own customized reports of the CSISG in a guided environment. The web portal will be a comprehensive and flexible tool to replace existing methods of producing and delivering manual reports. To achieve this vision, KopaWheel will conduct thorough usability research into the needs of the corporate clients, catering for both simple and advanced users. The features of the web portal consist of: (1) Dashboard, (2) Explorer, (3) Predictive Analysis, (4) Report Organizer (5) FAQ and (6)Administrative Functions: Builder & User Management.
The web portal will be customized based on dynamic portal engine(Joomla) through secure hosting on ISES premises.
Business Value
Deliverables
Deployed the CSISG online web portal for ISES on http://csisg.org:8080/ after 2 user acceptance testing. The online web portal is deployed on ISES's standalone Apple Xserve that is running Mac OS X Server 10.6.
X-factor
- Interactivity and Usability of the Web Portal
- Flexibility in accommodating to client's change request
Functionalities Overview
There is a total of 6 functions in our web portal.
- Dashboard
- CSISG Explorer
- Predictive Analysis
- Report Organizer
- FAQ
- Administrative Functions
- User Subscription
- Builder
For detailed scope, please click here.
Project Documentation
Specifications | Documents |
---|---|
Use Case Diagram | Use Case Diagram |
ERD Diagram | ERD Diagram |
UI Mockup | UI Mockup |
Deployment Diagram | Deployment Diagram |
Corporate Client Manual Guides | User Manual for Corporate Clients |
Administrator Manual Guides | User Manual for Administrators |
Deployment Manual Guides | CSISG Online Deployment Guide |
Technologies Used
Please refer to detailed explanation of what each of the technology is about and applied in the development of our web portal.
Project Management
Methodology
Our team will be using a combination of RUP and Scrum methodology to carry out the project. This approach will be ideal for our project where requirements change will occur throughout the duration of the project. By planning a overall schedule consisting of a number of iterations (in the construction phase) and buffer time as well as having an initial detailed scope, we are adopting the RUP approach. The plan is end-date driven and consist of milestones.
On top of this, we will be also adopting a part of the Scrum methodology as we will be holding weekly sprint(iteration) review meetings with our client. This is to ensure that the objectives set out at the start of each sprint (iterations) has been met at the end of the sprint (iterations) before the next sprint (iterations) begins. The Scrum approach will also allows us to understand the complex business sce
Project Schedule
Click here to view the detailed project schedule.
For detailed schedule in gantt chart, please click here.
Change Request Management
Change Request Log
This is a change request document that keeps a record of all the changes in requirements. Click here to view.
Change Request Document
This is a list of Change request document, detailing the specific changes in the project scope. Click here to view change request 1.
User Acceptance Testing (UAT)
Our team have conducted 2 UATs during the course of the project. Details of the UAT are as follows:
UAT | Description | Date | Time | UAT Test Scripts | UAT Results |
---|---|---|---|---|---|
UAT 1 | The purpose of this UAT is to conduct a Functional Testing with our client(ISES) and their Corporate client. We have managed to get 1 UOB Client & 4 ISES Staff to do the User Acceptance Test. The UAT is guided with the test scripts provided. |
|
10:30am | UAT1 Results & Feedbacks | |
UAT 2 | This UAT has been divided into 2 parts: functional test and usability test. The objective of functional test is to get our client and their corporate clients to test the functionality and the usability of the web portal. Whereas for the usability test, the objective was to get both technical and non-technical students to test out the usability of the web portal. |
|
11:30am | UAT2 Results & Feedbacks |
Risks
Identified Risks
Identified Risk at the start of the project:
Category | Detailed Explanation |
---|---|
Project and Team Risks | Project and Team Risks |
Client Relationship Risks | Client Relationship Risks |
Technology Risks | Technology Risks |
Resource Risks | Resource Risks |
Risks Occurred in the duration of project
Week 2 - Dependency Risk
Week 3 - Technology( R Scripts) & Resource Risk
Week 4 - Technology( R Scripts) & Unexpected Difficulty of Admin Function
Week 5 - Technology ( R Scripts & Graphiz)
Week 8 - Technology (D3 Technology)
Metrics
1. Schedule Metric
2. Bug Metric
3. Burn up Chart
Collaboration Tools
Technical Complexity
Meeting Minutes Repository
Learning Outcomes
Yuting
- Learn about managing and organizing the project with various stakeholders
- Learn new tools and understand how these tools can help to transform business requirements into an online portal
James
- The amount of effort to bring a seemingly possible scenario to fruition is more than expected
- Keeping the team motivated is very important. Finding a source of motivation for the team is difficult
Feixiang
- Hopes to better analyze client's business requirements and transform them into a system's functional and non-functional requirements
Liang Hua
- Wants to create new ideas and translate client's verbal/written requirements into system requirements, which can be troublesome, and making amendments accordingly
Documentation
Resourses & References
- General Resources
- IS480 Home : For all course related information
- Podio : Project management assistant dashboard
- Dropbox : Large file sharing
- Tortoise SVN : Source code control
- Knowledge Base
- Joomla: Content Management System
- PHP: Programming Language
- XAMPP: Server Package
- R Language: Statistical Computing & Graphics
- JQuery: JavaScript Library
- canviz : Visualisation of dot language on html
- Graphviz : Converts dot language into various outputs, it will feed canviz
- WKHTMLTOPDF: Converts our data into PDF Format
- D3 Technology
- Client Website