HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2009T2 The Mighty"

From IS480
Jump to navigation Jump to search
 
(47 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Image:OE_Logo.png | thumb | right |500px | Client Company Logo]] <br>
+
[[Image:OENewLogo.png | thumb | right |500px | Client Company Logo]] <br>
 
[[Image:themighty.gif | thumb | right | 500px | Team Logo]]<br>
 
[[Image:themighty.gif | thumb | right | 500px | Team Logo]]<br>
 
<br>
 
<br>
Line 22: Line 22:
 
==SIS Faculty Introduction==
 
==SIS Faculty Introduction==
 
==Our Course Manager==
 
==Our Course Manager==
[http://www.sis.smu.edu.sg/faculty/infosys/benjamingan.asp Prof Benjamin Gan]
+
[http://www.sis.smu.edu.sg/faculty/infosys/benjamingan.asp Prof Benjamin Gan][mailto:benjamingan@smu.edu.sg]
 +
 
 
==Our Project Supervisor==
 
==Our Project Supervisor==
[http://www.sis.smu.edu.sg/faculty/infosys/fdzhu.asp Prof Zhu Feida]
+
[http://www.sis.smu.edu.sg/faculty/infosys/fdzhu.asp Prof Zhu Feida][mailto:fdzhu@smu.edu.sg]
 
==Our Project Reviewer==
 
==Our Project Reviewer==
[http://www.sis.smu.edu.sg/faculty/infosys/yjli.asp Prof Li Ying Jiu]
+
[http://www.sis.smu.edu.sg/faculty/infosys/yjli.asp Prof Li Ying Jiu][mailto:yjli@smu.edu.sg]
  
 
==Latest Team Happenings==
 
==Latest Team Happenings==
 
<br>
 
<br>
 
Team Progress Updates: <br>  
 
Team Progress Updates: <br>  
''(1)- 12th April 2010, 12noon:'' Final Presentation @ SMU, Venue: SIS Meeting Room 4.5 <br>
+
''Further testing after handover on client's smart phone made it possible to use system on smart mobile phone with javascript and pdf viewer/ office document file viewer. I had personally tested it on my mobile phone as well and it works i am able to generate the crystal report on my phone. Will upload those pictures on it later in the week.
''(2)- 9th April 2010, 7pm:'' Final Presentation Rehearsal@ SMU, Venue: TBA <br>
 
''(3)- 9th April 2010:'' Finalize all deliverables to be submitted and final testing for application <br>
 
''(4)- 9th April 2010:'' Wiki Updates <br>
 
  
 
==Project Description==
 
==Project Description==
Line 354: Line 352:
 
<td>[[Image:Kennylee.jpg‎ | 150px]]</td>
 
<td>[[Image:Kennylee.jpg‎ | 150px]]</td>
 
<td>Project Manager</td>
 
<td>Project Manager</td>
<td>Email: kennylee.2007@sis.smu.edu.sg</td>
+
<td>Email: kennylee.2007@sis.smu.edu.sg [mailto:kennylee.2007@sis.smu.edu.sg]</td>
 
<td>Oversee program development. Develop business process methodologies <br>
 
<td>Oversee program development. Develop business process methodologies <br>
 
Liaise with client and organize collaboration <br>
 
Liaise with client and organize collaboration <br>
Line 365: Line 363:
 
<td>[[Image:Lim yang.jpg | 150px]]</td>
 
<td>[[Image:Lim yang.jpg | 150px]]</td>
 
<td>System Architect </td>
 
<td>System Architect </td>
<td>Email: yangl.2007@sis.smu.edu.sg</td>
+
<td>Email: yangl.2007@sis.smu.edu.sg [mailto:yangl.2007@sis.smu.edu.sg]</td>
 
<td>System design & architecture,Logic and Algorithm Formulation<br>
 
<td>System design & architecture,Logic and Algorithm Formulation<br>
 
Database design <br>
 
Database design <br>
Line 376: Line 374:
 
<td>[[Image:Juiying.jpg | 150px]]</td>
 
<td>[[Image:Juiying.jpg | 150px]]</td>
 
<td>Business Analyst</td>
 
<td>Business Analyst</td>
<td>Email: juiying.tan.2007@sis.smu.edu.sg</td>
+
<td>Email: juiying.tan.2007@sis.smu.edu.sg [mailto:juiying.tan.2007@sis.smu.edu.sg]</td>
 
<td>Understand Business needs, gather/provide feedback from  stakeholders. Ensure requirements are right and ensures <br>
 
<td>Understand Business needs, gather/provide feedback from  stakeholders. Ensure requirements are right and ensures <br>
 
Responsible for documentations <br>
 
Responsible for documentations <br>
Line 386: Line 384:
 
<td>[[Image:Daniel.jpg | 150px]]</td>
 
<td>[[Image:Daniel.jpg | 150px]]</td>
 
<td>Lead Tester</td>
 
<td>Lead Tester</td>
<td>Email: daniel.wuu.2007@sis.smu.edu.sg</td>
+
<td>Email: daniel.wuu.2007@sis.smu.edu.sg [mailto:daniel.wuu.2007@sis.smu.edu.sg]</td>
 
<td>Test plans,Design and lead UATs <br>
 
<td>Test plans,Design and lead UATs <br>
 
Assist in Development <br>
 
Assist in Development <br>
Line 396: Line 394:
 
<td>[[Image:Pengxinag.jpg | 150px]]</td>
 
<td>[[Image:Pengxinag.jpg | 150px]]</td>
 
<td>Lead Developer </td>
 
<td>Lead Developer </td>
<td>Email: px.chiam.2007@sis.smu.edu.sg</td>
+
<td>Email: px.chiam.2007@sis.smu.edu.sg [mailto:px.chiam.2007@sis.smu.edu.sg]</td>
 
<td>Facilitate code reviews <br>
 
<td>Facilitate code reviews <br>
 
Team lead for development<br>  
 
Team lead for development<br>  
Line 404: Line 402:
  
 
==Client Information==
 
==Client Information==
Mr. John Chua
+
Mr. John Chua [mailto:johnchua@orient-explorer.com]
 
<br>'''Position:''' Executive Director, Orient Explorer
 
<br>'''Position:''' Executive Director, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
  
<br>Ms Lim Chee Yi  
+
<br>Ms Lim Chee Yi [mailto:limcheeyi@orient-explorer.com]
 
<br>'''Position:''' Project Manager, Orient Explorer
 
<br>'''Position:''' Project Manager, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
  
<br>Ms Marianne Yee  
+
<br>Ms Marianne Yee [mailto:marianne@orient-explorer.com]
 
<br>'''Position:''' PCO Manager, Orient Explorer
 
<br>'''Position:''' PCO Manager, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
  
<br>Ms Michelle Choy  
+
<br>Ms Michelle Choy [mailto:michelle@orient-explorer.com]
 
<br>'''Position:''' PCO Manager, Orient Explorer
 
<br>'''Position:''' PCO Manager, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
  
<br>Ms Su Myat
+
<br>Ms Su Myat [mailto:su@orient-explorer.com]
 
<br>'''Position:''' IT Web Designer, Orient Explorer
 
<br>'''Position:''' IT Web Designer, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
  
<br>Mr Albert Camacho
+
<br>Mr Albert Camacho [mailto:albert@orient-explorer.com]
 
<br>'''Position:''' IT Web Designer, Orient Explorer
 
<br>'''Position:''' IT Web Designer, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
  
<br>Mr Hasley Fang
+
<br>Mr Hasley Fang [mailto:hasley@orient-explorer.com]
 
<br>'''Position:''' IT Web Programmer, Orient Explorer
 
<br>'''Position:''' IT Web Programmer, Orient Explorer
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
 
<br>'''Involvement:''' Provides direction, user requirements and feedback for the project
Line 435: Line 433:
 
<br>
 
<br>
  
==Our Project Journey==
+
==Our Project Journey & Project Schedule (Week by Week Synopsis)==
  
 
The Team uses Work Breakdown Structure as well as computation of the total team's manpower hours to tabulate our progress and schedule tracking on the project.
 
The Team uses Work Breakdown Structure as well as computation of the total team's manpower hours to tabulate our progress and schedule tracking on the project.
 +
 +
[[Image:Planned_Schedule.png |thumb|right|300px| Team Planned Project Schedule]] <br>
 +
[[Image:Project_Actual_Schedule.png |thumb|right|300px| Team Actual Project Schedule]] <br>
 +
 
<h3>3 Months before school term started...</h3>
 
<h3>3 Months before school term started...</h3>
 
Team formation and brainstorming of the project, finding the a suitable client for the project<br>
 
Team formation and brainstorming of the project, finding the a suitable client for the project<br>
Line 465: Line 467:
 
With this dilemma, team had to decide whether to take up this project and work up a proposal in 5 days or face the consequences of having to re-register the following semester.<br>
 
With this dilemma, team had to decide whether to take up this project and work up a proposal in 5 days or face the consequences of having to re-register the following semester.<br>
 
   
 
   
[[Image:Planned_Schedule.png |thumb|right|300px| Team Planned Project Schedule]] <br>
 
[[Image:Project_Actual_Schedule.png |thumb|right|300px| Team Actual Project Schedule]] <br>
 
  
 
<h3>Start of Project Phase</h3>
 
<h3>Start of Project Phase</h3>
Line 474: Line 474:
  
 
<h3>Week 1</h3>
 
<h3>Week 1</h3>
- Team had to come out with GUI of the System<br>
+
- Team had to come out with UI of the System<br>
 
- Team had delegated task to members to research on functions were we had no prior experience on <br>
 
- Team had delegated task to members to research on functions were we had no prior experience on <br>
 
- Team had Review project schedule <br>
 
- Team had Review project schedule <br>
Line 484: Line 484:
 
- Team had a internal reflection on the proposal results <br>
 
- Team had a internal reflection on the proposal results <br>
 
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan <br>
 
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan <br>
 +
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation<br>
  
 
<h3>Week 3</h3>
 
<h3>Week 3</h3>
Line 490: Line 491:
 
- Team had developed the partial working Report Builder functionality <br>
 
- Team had developed the partial working Report Builder functionality <br>
 
- Created a SVN Repository for our team coding synchronization, after few rounds of testing team found it not compatible with the Team's development effort <br>
 
- Created a SVN Repository for our team coding synchronization, after few rounds of testing team found it not compatible with the Team's development effort <br>
 +
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan <br>
 +
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation<br>
  
 +
<h3>Week 4</h3>
 +
- Team had consulted with Professor Kyriakos MOURATIDIS about our database design <br>
 +
- Team had finalized our database design after the consultation with Professor Kyriakos <br>
 +
- Team had updated of the Report Generator and the form builder features <br>
 +
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology <br>
 +
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan <br>
 +
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation<br>
  
 +
<h3>Week 5</h3>
 +
- Team had refine application form builder and report builder functionality <br>
 +
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology <br>
 +
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan <br>
 +
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation<br>
 +
- Deployed on production server and did alot of testing to ensure bugs had been debug <br>
 +
 +
<h3>Week 6</h3>
 +
- 1st deployment on the production server <br>
 +
- 1st Internal UAT test with the line users <br>
 +
- Debug bugs and troubleshoot deployment problems on working codes <br>
 +
- Test and more test to ensure working code are working stable <br>
 +
- UAT at SMU with Client and Team <br>
 +
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology <br>
 +
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan <br>
 +
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation<br>
 +
 +
<h3>Week 7</h3>
 +
- Complete the additional requirements specified by client (Hotels and Analysis Report) <br>
 +
- Team did further development for Report and Form Builder <br>
 +
- Started on support functionalities <br>
 +
- Improve codes after UAT to meet user expectation <br>
 +
- Did alot of testing to ensure each function that is developed is tested throughly <br>
 +
- Did our mid term reflection <br>
 +
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology <br>
 +
 +
<h3>Week 8</h3>
 +
- Team did further development for Report and Form Builder <br>
 +
- Team did further development for supporting functionalities <br>
 +
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology <br>
 +
- Team did the edit of CSS layout of the form builder <br>
 +
- Development of the back-end integration with the database <br>
 +
- Review on our schedule for subsequent UATs with the client <br>
 +
- Negotiate of a better plan with the client on the USonix Server to provide the capacity to have Crystal Reporting features <br>
 +
 +
<h3>Week 9</h3>
 +
- Team did further development for Report and Form Builder <br>
 +
- Team did further development for supporting functionalities <br>
 +
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology <br>
 +
- Team did further development of CSS layout of the form builder <br>
 +
- Team started on the development of form validation <br>
 +
- Auto Generation of emails to client and admin <br>
 +
 +
<h3>Week 10</h3>
 +
- Started on admin control list <br>
 +
- Schedule one more round of UAT to ensure that requirements and project timeline is according to plan <br>
 +
- Start working on poster <br>
 +
- We finalized the development phrase and are doing intensive testing on our application <br>
 +
- Prepare main project report and clean up wiki <br>
 +
- Further development of validation <br>
  
  
 +
<h3>Week 11</h3>
 +
- The team does an update on the current functionalities of the application <br>
 +
- Further development of validation <br>
 +
- Additional testing and deployment testing <br>
 +
- Refactoring the finalized codes <br>
 +
- Prepare main project report and clean up wiki <br>
 +
- Poster submission <br>
  
<h3>Project Mid-Week</h3>
+
<h3>Week 12, Week 13, Week14</h3>
The team just had their User Acceptance Test on Week 7 with the client as well as our supervisor.<br>
+
- The team is meeting everyday to test, debug, document the project <br>
The UAT was a successful one as the client has expressed interest in expanding the application to other offices in the region. <br>
+
- Since now we have an integrated system on the production server <br>
At the current Week 9, the team is integrating the components of the form builder together, editing the CSS layout of our form builder as well as doing partial stressed testing on our form builder. <br>
+
- Team is now able to conduct the testing and formulate a complete suite of test cases <br>
This is to prepare the team for a 2nd scheduled UAT test with the line users on Week 10. <br>
+
- Team has updated the wiki, report and complete the deployment testing <br>
 +
- Team has will have a presentation rehearsal with Prof Feida on 9th April <br>
 +
- Team final presentation date with our client and profs is scheduled on the 12th April 2010 @ 12noon at SMU School of Information Systems Level 4 Meeting Room 4.5 <br>
 +
- Study for exams, all of use had been working so hard for this project this whole study week we were doing FYP, barely studied!, so now it should be completing now by Saturday. PX and Juiying have 1 paper on Monday, Kenny and Daniel has a paper on Friday and Lim Yang has AA! <br>
  
 
==Our FYP Poster==
 
==Our FYP Poster==
 
[[Image:FYP_Poster_Design.png | thumb |centre | 600px |Our FYP Poster Design]]
 
[[Image:FYP_Poster_Design.png | thumb |centre | 600px |Our FYP Poster Design]]
  
 +
==Our Photo Gallery==
 +
<gallery caption="Client's rebranding campaign " widths="100px" heights="100px" perrow="6">
 +
Image:DSC00701.JPG|Picture 1 (Invitation)
 +
Image:DSC00700.JPG|Picture 2 (The Food!)
 +
Image:DSC00706.JPG|Picture 3 (The Boys!)
 +
Image:DSC00699.JPG|Picture 4 (PX and Yang)
 +
Image:DSC00704.JPG|Picture 5 (Dan and PX)
 +
Image:DSC00697.JPG|Picture 6 (Our Client Mr John Chua)
 +
Image:DSC00698.JPG|Picture 7 (His Business Model)
 +
Image:DSC00707.JPG|Picture 8 (The event venue:RWS Ballroom)
 +
Image:DSC00713.JPG|Picture 9 (Guest of honor: Thailand ambassdor to singapore, his excellency Nopadol Gunavibool)
 +
Image:John_0001.jpg|Picture 10 (Our Client Mr John Chua on Newsweek Coverspread)
 +
Image:John_0002.jpg|Picture 11 (Our Client Mr John Chua's Newsweek Story)
 +
</gallery>
 +
 +
 +
 +
==Team's Collaboration Tools, Project Management Tools and Bug Tracking Tools==
 +
 +
===Zoho Project Management Tools===
 +
 +
[[Image:Zoho.JPG|thumb|200px|right|Image from http://www.zoho.com/]]
 +
Other than keeping an offline excel spreadsheet to manage the project schedule. Team uses Zoho.com to keep all team members informed about the project the schedule and ensure project is on track.<br>
 +
 +
Team Zoho Site Main: https://projects.zoho.com/portal/themightyfyp <br>
 +
 +
''Reference'' <br/>
 +
http://www.zoho.com/
  
==Project Weekly Updates==
+
===Dropbox Collaboration Tools (File Sharing)===
 +
 
 +
[[Image:Dropbox.JPG|thumb|200px|right|Image from https://www.dropbox.com/]]
 +
We used dropbox as a SVN to manage our project  files as a form of a collaboration tools to share files seamlessly with all team members.
 +
<br>
 +
 
 +
Team Dropbox Folder: Only provided when requested <br>
 +
 
 +
''Reference'' <br/>
 +
https://www.dropbox.com/
 +
 
 +
===Bug Tracker Tools===
 +
 
 +
[[Image:16bugs.JPG|thumb|200px|right|Image from http://16bugs.com/]]
 +
To keep track of the bugs or issues escalating for the development thus team is able to avoid those bugs encounter using the solutions discovered by team members to maximize productivity & efficiency in development.
 +
<br>
 +
 
 +
Team Bug Tracker Site: http://themightyfyp.16bugs.com/ <br>
 +
 
 +
''Reference'' <br/>
 +
http://16bugs.com/
 +
 
 +
==Project Weekly Meeting Updates==
 
<h3>Week 1</h3>
 
<h3>Week 1</h3>
- Coming out with GUI<br>
 
- Research on functions<br>
 
- Review project schedule<br>
 
 
[[Meeting Minutes:8_jan_2009.docx]]<br>
 
[[Meeting Minutes:8_jan_2009.docx]]<br>
 
[[Meeting Powerpoint:8_Jan_2009.pptx]]
 
[[Meeting Powerpoint:8_Jan_2009.pptx]]
Line 515: Line 632:
 
   
 
   
 
<h3>Week 2</h3>
 
<h3>Week 2</h3>
- Created a Prototype for web site builder<br>
 
- Research on how to export to PDF and excel file<br>
 
- Creation of database<br>
 
- Team reflection on the proposal results<br>
 
- Meet up with client to verify on the client requirements and expectations<br>
 
 
[[Meeting Minutes:15_Jan_2009.docx]]<br>
 
[[Meeting Minutes:15_Jan_2009.docx]]<br>
 
[[Meeting Powerpoint:15_Jan_2010.pptx]]<br>
 
[[Meeting Powerpoint:15_Jan_2010.pptx]]<br>
Line 526: Line 638:
  
 
<h3>Week 3</h3>
 
<h3>Week 3</h3>
- Able to obtain server capacity and successfully tested the database connection <br>
 
- Partial working of the Form Builder<br>
 
- Obtain the functionalities of the Report Builder<br>
 
- Created a SVN Repository for our team coding synchronization<br>
 
 
[[Meeting Minutes:22_Jan_2009.docx]]<br>
 
[[Meeting Minutes:22_Jan_2009.docx]]<br>
 
[[Meeting Powerpoint:22_Jan_2010.pptx]]
 
[[Meeting Powerpoint:22_Jan_2010.pptx]]
  
 
<h3>Week 4</h3>
 
<h3>Week 4</h3>
- Consulted with Professor Kyriakos MOURATIDIS about our database design.<br>
 
- Finalized our database design<br>
 
- Updates of the Report Generator features<br>
 
- Refine on the whole project<br>
 
- Updates on project schedule for the past 4 weeks<br>
 
- Team direction in the following weeks<br>
 
 
[[Meeting Minutes:29_Jan_2010.docx]]<br>
 
[[Meeting Minutes:29_Jan_2010.docx]]<br>
 
[[Meeting Powerpoint:29_Jan_2010.pptx]]
 
[[Meeting Powerpoint:29_Jan_2010.pptx]]
  
 
<h3>Week 5</h3>
 
<h3>Week 5</h3>
- Schedule with Client for an Interim UAT test<br>
 
- Updates of our Form Builder features<br>
 
- Updates on our Report Builder features<br>
 
 
[[Meeting Minutes:2_Feb_2010.docx]]<br>
 
[[Meeting Minutes:2_Feb_2010.docx]]<br>
 
[[Meeting Powerpoint:5_Feb_2010.pptx]]
 
[[Meeting Powerpoint:5_Feb_2010.pptx]]
  
 
<h3>Week 6</h3>
 
<h3>Week 6</h3>
- Held a formal UAT with the client and our supervisor<br>
 
- Review on our schedule for Week 7,8 and 9<br>
 
- Updates of our Form Builder features<br>
 
- Updates on our Report Builder features<br>
 
 
[[Meeting Minutes (UAT feedbacks):UAT.docx]]<br>
 
[[Meeting Minutes (UAT feedbacks):UAT.docx]]<br>
 
[[Meeting Powerpoint (UAT):UAT_slides.pptx]]
 
[[Meeting Powerpoint (UAT):UAT_slides.pptx]]
  
 
<h3>Week 7</h3>
 
<h3>Week 7</h3>
- Did our mid term reflection<br>
 
- Review on our schedule for Week 7,8 and 9<br>
 
- Further development on our Form Builder features<br>
 
- Further development on our Report Builder features<br>
 
 
[[Meeting Powerpoint (UAT):26feb2010.pptx]]
 
[[Meeting Powerpoint (UAT):26feb2010.pptx]]
  
 
<h3>Week 8</h3>
 
<h3>Week 8</h3>
- Development phase for the team <br>
 
- Edit of CSS layout of the form builder<br>
 
- Development of the back-end integration with the database<br>
 
- Review on our schedule for subsequent UATs with the client <br>
 
- Negotiate of a better plan with the client on the USonix Server to provide the capacity to have Crystal Reporting features <br>
 
 
[[Meeting Powerpoint (UAT):26feb2010.pptx]]
 
[[Meeting Powerpoint (UAT):26feb2010.pptx]]
  
 
<h3>Week 9</h3>
 
<h3>Week 9</h3>
- Development phase for the team <br>
 
- Edit the CSS layout of the form builder<br>
 
- Development of the back-end integration with the database<br>
 
- Review on our schedule for subsequent UATs with the client <br>
 
- Started on the development of form validation <br>
 
 
[[Meeting Powerpoint (UAT):5march2010.pptx]]
 
[[Meeting Powerpoint (UAT):5march2010.pptx]]
  
 
<h3>Week 10</h3>
 
<h3>Week 10</h3>
- Week 10 is a User Acceptance Test for our client <br>
 
- We finalized the development phrase and are doing intensive testing on our application.<br>
 
- Test cases were tailored made for our application.<br>
 
 
[[UAT Week 10 feedbacks:Week_10_UAT_Feedback.docx‎  ]]
 
[[UAT Week 10 feedbacks:Week_10_UAT_Feedback.docx‎  ]]
 
[[Client meeting minutes: 12march2010.docx‎ ‎  ]]<br>
 
[[Client meeting minutes: 12march2010.docx‎ ‎  ]]<br>
Line 591: Line 669:
  
 
<h3>Week 11</h3>
 
<h3>Week 11</h3>
- The team finalized our presentation slides and started on our report <br>
 
- The team does an update on the current functionalities of the application. <br>
 
 
[[Week 11 meeting minutes:19march2010.docx‎  ]]<br>
 
[[Week 11 meeting minutes:19march2010.docx‎  ]]<br>
 
[[Week 11 powerpoint: 19march2010.pptx‎  ]]
 
[[Week 11 powerpoint: 19march2010.pptx‎  ]]

Latest revision as of 09:16, 21 April 2010

Client Company Logo


Team Logo




Team Picture









Contents

Welcome to Team Mighty Wiki

The Team Introduction

Kenny Lee - Project Manager
Chiam Peng Xiang - Lead System Developer
Lim Yang - System Developer
Tan Juiying - Business Analyst
Daniel Wuu - Lead Tester

SIS Faculty Introduction

Our Course Manager

Prof Benjamin Gan[1]

Our Project Supervisor

Prof Zhu Feida[2]

Our Project Reviewer

Prof Li Ying Jiu[3]

Latest Team Happenings


Team Progress Updates:
Further testing after handover on client's smart phone made it possible to use system on smart mobile phone with javascript and pdf viewer/ office document file viewer. I had personally tested it on my mobile phone as well and it works i am able to generate the crystal report on my phone. Will upload those pictures on it later in the week.

Project Description

In the perspective of the company’s requirement for a registration management system, our team has planned for an implementation of management system that could enable the administrator i.e. the department managers and staff to be able to use the form builders to create the dynamic forms for different event registration using the form builder, that will resolve their pain of having to ask the web master for every event to recreate the forms. Note that the requirements for each rate they charge for every event is different and the application will be required to handle such dynamic requirements. To be able to mix and match the different options and rates just like how you will scan the items in a shopping cart in the supermarket, but in this case the database will store the data. The clients (delegates/speakers) will now be able to receive an auto generated form informing them about the payment and the event registration confirmation.

OE's As-Is Process

Before the team begins to develop the application for the company, the team took the countless hours of meeting and interviews with our stakeholder to better understand the company's business process as well as current problems faced by Line users and the management of OE doing up the Company's AS-IS process flow!

AS-IS - Create Form

AS-IS - Processing Registration & Payment

Project Motivation

Problem that the company is facing:

Does not make use of any automated registration management system to handle the registration of an event. There are many manual processes that the client has to manually input the registration data, resulting in the possibility of data inaccuracy and latency due to the volume of data transaction.

Overview of AS-IS of OE's Business Process

Solution Proposed by Team Mighty:
- Implementation of an Automated Registration Management System.

Would not only solve the issue of data inaccuracy, but provides an actual centralized database for the client's daily monitoring activity.
Efficiency in handling the volume of data transaction per day could be largely improved with this implementation.

Overview of TO-BE of OE's Future Business Process

Interim UI Prototype Design (Paper Sketch Design)


Form Builder:

Allows the administrator to dynamically build a form, with his selected fields that was already predefined in the previous form builder.

Interim Form Builder Design

Addition Implementation of a Report Builder. Allows the client company to generate real-time graphical statistics for the benefits of his partnering companies and clients.

Report Generator:
Allows line users to print out statistical reports in graphical manner!

Interim Report Generator Design

Team Mighty 's Motivation


The team strongly believed that an effective communication with our stakeholders is fundamental to a good project management. Hence, other than conducting a weekly meeting with our client, team mighty has also planned for UATs with the line users, even during the implementation phase of our project!

UI Analysis

This is how the UI flow will be for the system:

UI Analysis Model

Project Objective

Main Features:

1. Event registration system - Form Builder


a. To create and customize event form within the form builder and publish on server
b. To edit and delete form in the form builder
c. Ability to capture participates information and store in database

Application Interface Design

Form Builder Create Page 1


This form allows the Administrator to fill in basic particulars of the event, for example would include the time, venue and organizer of the event.

Create Form Screen - Step 1

Form Builder Create Page 2


Page 2 allows Administrator to choose the TYPES of participants details he wants to build for the event form. Page 2 also includes the payment details, the type of payment modes the Administrator wants to include for the event.

Create Form Screen - Step 2


Form Builder Create Page 3


The final page allows the Administrator to create any special packages that is available for that particular event. An example of such packages would be meals package, hotels packages.

Create Form Screen - Step 3

Delete Form


Allows administrator to perform delete the entire form when the form is rendered not of use.

Delete Form Screen

View Form


Allows administrator to view all the forms that is being created previously.

View Form Screen

Edit Functionalities


Allows administrator to edit the forms; according to event details, event hotel packages as well as event price package. The administrator is also able to edit the details information of the participants.

This page enables the administrator to edit the details of the event; which would include the starting and ending dates of the event, the location as well as other miscellaneous naming particulars of the event.
Edit Event Screen
This page is for the administrator to edit the packages that the corresponding hotels is providing for the participants.
Edit Hotel Package Screen
As the price of each package might differ across all the packages, the team specially dedicate a page that caters to the editing of the event package price.
Edit Event Package Price Screen
From this interface page, the administrator would also be able to edit the participants details, that was stored in our team's database.
Edit Participant Details Screen

Search Functionalities


Allows administrator to search for any forms in terms of events or participants with greater ease.

This search page allows the administrator to search for events details. This search page enables filtering, select all features. This search page is also linked to the edit page; where the administrator is able to edit the details of the searched items.
Search Event Screen
This search page allows the administrator to search for participants details. This search page enables filtering, select all features. This search page is also linked to the edit page; where the administrator is able to edit the details of the searched items.
Search Participant Screen

Administrator Features


The features would include login and logout functions and administrator page.

Login and logout page. User have to input the relevant assigned username and password.
Login Logout Screen
In this page, user is able to edit the permission settings of each assigned user.
Admin Control Screen

Customization design of form created


The team has also come out with the ability of the application to customize the design/ layout of the designated forms.

Cool.JPG

Green.JPG

Simple.JPG


2. Event Reporting System - Report Generator


a. Easily monitor progress of sign up rate for event.
b. Generate report containing event statistics (participates attendance) and charts in the reporting builder module to create charts and reports within the builder in crystal report formats.
c. Generation of Financial reports of respective events.

Report Generator Screen

As above, would be the interface to generate the report required.

Generated Report Screen

The above would portray the already generated report. The file format can be selectable from pdf to doc format.

Team MIGHTY Roles

Name Role Responsibilities Contact Job Scope
Kenny Lee Kennylee.jpg Project Manager Email: kennylee.2007@sis.smu.edu.sg [4] Oversee program development. Develop business process methodologies

Liaise with client and organize collaboration
Assist in development

Lim Yang Lim yang.jpg System Architect Email: yangl.2007@sis.smu.edu.sg [5] System design & architecture,Logic and Algorithm Formulation

Database design
Assist in Development

Jui Ying Juiying.jpg Business Analyst Email: juiying.tan.2007@sis.smu.edu.sg [6] Understand Business needs, gather/provide feedback from stakeholders. Ensure requirements are right and ensures

Responsible for documentations

User interface design
Daniel Wuu Daniel.jpg Lead Tester Email: daniel.wuu.2007@sis.smu.edu.sg [7] Test plans,Design and lead UATs

Assist in Development

Peng Xiang Pengxinag.jpg Lead Developer Email: px.chiam.2007@sis.smu.edu.sg [8] Facilitate code reviews

Team lead for development

Client Information

Mr. John Chua [9]
Position: Executive Director, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project


Ms Lim Chee Yi [10]
Position: Project Manager, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project


Ms Marianne Yee [11]
Position: PCO Manager, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project


Ms Michelle Choy [12]
Position: PCO Manager, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project


Ms Su Myat [13]
Position: IT Web Designer, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project


Mr Albert Camacho [14]
Position: IT Web Designer, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project


Mr Hasley Fang [15]
Position: IT Web Programmer, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project



Our Project Journey & Project Schedule (Week by Week Synopsis)

The Team uses Work Breakdown Structure as well as computation of the total team's manpower hours to tabulate our progress and schedule tracking on the project.

Team Planned Project Schedule


Team Actual Project Schedule


3 Months before school term started...

Team formation and brainstorming of the project, finding the a suitable client for the project

2 Months before school term started....

We shortlisted the possible projects to start gathering information and getting the scope of each project
Team shortlisted 3 Projects:

1)Jay Machinery Crane Video Surveillance and Analytics System
2)OE Registration Management System
3)E-Commerce System

1 Month before school term started........

Team had finalized on the Jay Machinery Project, we started to meet the management of the company gathering the project scope, requirements, understanding the company AS-IS and researching on the TO-BE solution for the company.

Over the December Hols!

And before we start formally on our project, we began our internal training!!
This internal training is to build up each members' ability to do C# as well as building team spirit!
Team had also taken this time to formulate on our Interim Proposal and finalize the final proposal getting ready for the new semester.

Before Week 1...Emergency CRISIS!!!

Jay company had a last minute change of plans, therefore with the following 3 reasons we are forced to abandon the project and seek a new one or face the consequences of having to re-register for the following semster:

1)Low Sponsor Budget
2)We met up with the vendor and this meeting made us realize that the quotation is too high
3)Team is inexperience with hardware knowledge
With this dilemma, team had to decide whether to take up this project and work up a proposal in 5 days or face the consequences of having to re-register the following semester.


Start of Project Phase

The implementation phase starts in Week 2 and will continue to Week 9.
Our mid term review as well as out Interim Client review is on Week 6.
From the start of the project, Team had arranged many meetings with the clients in the whole month of January to interview and gather the full picture of the AS-IS process @ OE.

Week 1

- Team had to come out with UI of the System
- Team had delegated task to members to research on functions were we had no prior experience on
- Team had Review project schedule

Week 2

- Team had created a Prototype for web site builder
- Team had to research on how to export to PDF and excel file
- Creation of database
- Team had a internal reflection on the proposal results
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation

Week 3

- Team is able to obtain shared server subscription and successfully tested the database connection
  - Team had developed the partial working Form Builder functionality
- Team had developed the partial working Report Builder functionality
- Created a SVN Repository for our team coding synchronization, after few rounds of testing team found it not compatible with the Team's development effort
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation

Week 4

- Team had consulted with Professor Kyriakos MOURATIDIS about our database design
- Team had finalized our database design after the consultation with Professor Kyriakos
- Team had updated of the Report Generator and the form builder features
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation

Week 5

- Team had refine application form builder and report builder functionality
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation
- Deployed on production server and did alot of testing to ensure bugs had been debug

Week 6

- 1st deployment on the production server
- 1st Internal UAT test with the line users
- Debug bugs and troubleshoot deployment problems on working codes
- Test and more test to ensure working code are working stable
- UAT at SMU with Client and Team
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology
- Team had met up with client to verify on the client requirements and expectations on top of the ongoing effort to gather all information required to formulate the TO-BE plan
- Team had to revise UI and then make changes to the report builder and report generator to ensure that system is aligned with client's expectation

Week 7

- Complete the additional requirements specified by client (Hotels and Analysis Report)
- Team did further development for Report and Form Builder
- Started on support functionalities
- Improve codes after UAT to meet user expectation
- Did alot of testing to ensure each function that is developed is tested throughly
- Did our mid term reflection
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology

Week 8

- Team did further development for Report and Form Builder
- Team did further development for supporting functionalities
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology
- Team did the edit of CSS layout of the form builder
- Development of the back-end integration with the database
- Review on our schedule for subsequent UATs with the client
- Negotiate of a better plan with the client on the USonix Server to provide the capacity to have Crystal Reporting features

Week 9

- Team did further development for Report and Form Builder
- Team did further development for supporting functionalities
- Team had modularize codes for the whole project to ensure that system code adhere to the MVC methadology
- Team did further development of CSS layout of the form builder
- Team started on the development of form validation
- Auto Generation of emails to client and admin

Week 10

- Started on admin control list
- Schedule one more round of UAT to ensure that requirements and project timeline is according to plan
- Start working on poster
- We finalized the development phrase and are doing intensive testing on our application
- Prepare main project report and clean up wiki
- Further development of validation


Week 11

- The team does an update on the current functionalities of the application
- Further development of validation
- Additional testing and deployment testing
- Refactoring the finalized codes
- Prepare main project report and clean up wiki
- Poster submission

Week 12, Week 13, Week14

- The team is meeting everyday to test, debug, document the project
- Since now we have an integrated system on the production server
- Team is now able to conduct the testing and formulate a complete suite of test cases
- Team has updated the wiki, report and complete the deployment testing
- Team has will have a presentation rehearsal with Prof Feida on 9th April
- Team final presentation date with our client and profs is scheduled on the 12th April 2010 @ 12noon at SMU School of Information Systems Level 4 Meeting Room 4.5
- Study for exams, all of use had been working so hard for this project this whole study week we were doing FYP, barely studied!, so now it should be completing now by Saturday. PX and Juiying have 1 paper on Monday, Kenny and Daniel has a paper on Friday and Lim Yang has AA!

Our FYP Poster

Our FYP Poster Design

Our Photo Gallery


Team's Collaboration Tools, Project Management Tools and Bug Tracking Tools

Zoho Project Management Tools

Other than keeping an offline excel spreadsheet to manage the project schedule. Team uses Zoho.com to keep all team members informed about the project the schedule and ensure project is on track.

Team Zoho Site Main: https://projects.zoho.com/portal/themightyfyp

Reference
http://www.zoho.com/

Dropbox Collaboration Tools (File Sharing)

We used dropbox as a SVN to manage our project files as a form of a collaboration tools to share files seamlessly with all team members.

Team Dropbox Folder: Only provided when requested

Reference
https://www.dropbox.com/

Bug Tracker Tools

To keep track of the bugs or issues escalating for the development thus team is able to avoid those bugs encounter using the solutions discovered by team members to maximize productivity & efficiency in development.

Team Bug Tracker Site: http://themightyfyp.16bugs.com/

Reference
http://16bugs.com/

Project Weekly Meeting Updates

Week 1

Meeting Minutes:8_jan_2009.docx
Meeting Powerpoint:8_Jan_2009.pptx


Week 2

Meeting Minutes:15_Jan_2009.docx
Meeting Powerpoint:15_Jan_2010.pptx
Client Meeting Minutes:Client_Meeting_Slides_-_Registration_Management_System_(RMS).pptx


Week 3

Meeting Minutes:22_Jan_2009.docx
Meeting Powerpoint:22_Jan_2010.pptx

Week 4

Meeting Minutes:29_Jan_2010.docx
Meeting Powerpoint:29_Jan_2010.pptx

Week 5

Meeting Minutes:2_Feb_2010.docx
Meeting Powerpoint:5_Feb_2010.pptx

Week 6

Meeting Minutes (UAT feedbacks):UAT.docx
Meeting Powerpoint (UAT):UAT_slides.pptx

Week 7

Meeting Powerpoint (UAT):26feb2010.pptx

Week 8

Meeting Powerpoint (UAT):26feb2010.pptx

Week 9

Meeting Powerpoint (UAT):5march2010.pptx

Week 10

UAT Week 10 feedbacks:Week_10_UAT_Feedback.docx‎ Client meeting minutes: 12march2010.docx‎ ‎
UAT powerpoint: 12march2010.pptx‎ ‎


Week 11

Week 11 meeting minutes:19march2010.docx‎
Week 11 powerpoint: 19march2010.pptx‎

Week 12, 13 and 14

- The team is meeting everyday to test, debug, document the project
- Since now we have an integrated system on the production server
- Team is now able to conduct the testing and formulate a complete suite of test cases
- Team has updated the wiki, report and complete the deployment testing
- Team has will have a presentation rehearsal with Prof Feida on 9th April
- Team final presentation date with our client and profs is scheduled on the 12th April 2010 @ 12noon at SMU School of Information Systems Level 4 Meeting Room 4.5