Difference between revisions of "IS480 Team wiki: 2009T2 The Mighty"
Line 530: | Line 530: | ||
- Did our mid term reflection <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> | - 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 and admin control list <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> | ||
+ | |||
+ | |||
Revision as of 21:51, 9 April 2010
Contents
- 1 Welcome to Team Mighty Wiki
- 1.1 The Team Introduction
- 1.2 SIS Faculty Introduction
- 1.3 Our Course Manager
- 1.4 Our Project Supervisor
- 1.5 Our Project Reviewer
- 1.6 Latest Team Happenings
- 1.7 Project Description
- 1.8 OE's As-Is Process
- 1.9 Project Motivation
- 1.10 Interim UI Prototype Design (Paper Sketch Design)
- 1.11 Team Mighty 's Motivation
- 1.12 UI Analysis
- 1.13 Project Objective
- 1.13.1 Main Features:
- 1.13.2 Application Interface Design
- 1.13.2.1 Form Builder Create Page 1
- 1.13.2.2 Form Builder Create Page 2
- 1.13.2.3 Form Builder Create Page 3
- 1.13.2.4 Delete Form
- 1.13.2.5 View Form
- 1.13.2.6 Edit Functionalities
- 1.13.2.7 Search Functionalities
- 1.13.2.8 Administrator Features
- 1.13.2.9 Customization design of form created
- 1.13.2.10 2. Event Reporting System - Report Generator
- 1.14 Team MIGHTY Roles
- 1.15 Client Information
- 1.16 Our Project Journey & Project Schedule
- 1.16.1 3 Months before school term started...
- 1.16.2 2 Months before school term started....
- 1.16.3 1 Month before school term started........
- 1.16.4 Over the December Hols!
- 1.16.5 Before Week 1...Emergency CRISIS!!!
- 1.16.6 Start of Project Phase
- 1.16.7 Week 1
- 1.16.8 Week 2
- 1.16.9 Week 3
- 1.16.10 Week 4
- 1.16.11 Week 5
- 1.16.12 Week 6
- 1.16.13 Week 7
- 1.16.14 Week 8
- 1.16.15 Project Mid-Week
- 1.17 Our FYP Poster
- 1.18 Project Weekly Updates
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
Our Project Supervisor
Our Project Reviewer
Latest Team Happenings
Team Progress Updates:
(1)- 12th April 2010, 12noon: Final Presentation @ SMU, Venue: SIS Meeting Room 4.5
(2)- 9th April 2010, 7pm: Final Presentation Rehearsal@ SMU, Venue: TBA
(3)- 9th April 2010: Finalize all deliverables to be submitted and final testing for application
(4)- 9th April 2010: Wiki Updates
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! |
|
|
Project Motivation
Problem that the company is facing: |
|
Solution Proposed by Team Mighty:
|
|
Interim UI Prototype Design (Paper Sketch Design)
Form Builder: |
|
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:
|
|
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:
Project Objective
Main Features:1. Event registration system - Form Buildera. To create and customize event form within the form builder and publish on server |
|
Application Interface DesignForm Builder Create Page 1
|
|
Form Builder Create Page 2
|
|
Form Builder Create Page 3
|
|
Delete Form
|
|
View Form
|
|
Edit Functionalities
|
|
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. | |
This page is for the administrator to edit the packages that the corresponding hotels is providing for the participants. | |
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. | |
From this interface page, the administrator would also be able to edit the participants details, that was stored in our team's database. | |
Search Functionalities
| |
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. | |
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. | |
Administrator Features
| |
Login and logout page. User have to input the relevant assigned username and password. | |
In this page, user is able to edit the permission settings of each assigned user. |
Customization design of form created
|
2. Event Reporting System - Report Generatora. Easily monitor progress of sign up rate for event. |
As above, would be the interface to generate the report required. |
The above would portray the already generated report. The file format can be selectable from pdf to doc format. |
Team MIGHTY Roles
Client Information
Mr. John Chua
Position: Executive Director, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Ms Lim Chee Yi
Position: Project Manager, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Ms Marianne Yee
Position: PCO Manager, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Ms Michelle Choy
Position: PCO Manager, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Ms Su Myat
Position: IT Web Designer, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Mr Albert Camacho
Position: IT Web Designer, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Mr Hasley Fang
Position: IT Web Programmer, Orient Explorer
Involvement: Provides direction, user requirements and feedback for the project
Our Project Journey & Project Schedule
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.
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 admin control list
- 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 and admin control list
- 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
Project Mid-Week
The team just had their User Acceptance Test on Week 7 with the client as well as our supervisor.
The UAT was a successful one as the client has expressed interest in expanding the application to other offices in the region.
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.
This is to prepare the team for a 2nd scheduled UAT test with the line users on Week 10.
Our FYP Poster
Project Weekly Updates
Week 1
- Coming out with GUI
- Research on functions
- Review project schedule
Meeting Minutes:8_jan_2009.docx
Meeting Powerpoint:8_Jan_2009.pptx
Week 2
- Created a Prototype for web site builder
- Research on how to export to PDF and excel file
- Creation of database
- Team reflection on the proposal results
- Meet up with client to verify on the client requirements and expectations
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
- Able to obtain server capacity and successfully tested the database connection
- Partial working of the Form Builder
- Obtain the functionalities of the Report Builder
- Created a SVN Repository for our team coding synchronization
Meeting Minutes:22_Jan_2009.docx
Meeting Powerpoint:22_Jan_2010.pptx
Week 4
- Consulted with Professor Kyriakos MOURATIDIS about our database design.
- Finalized our database design
- Updates of the Report Generator features
- Refine on the whole project
- Updates on project schedule for the past 4 weeks
- Team direction in the following weeks
Meeting Minutes:29_Jan_2010.docx
Meeting Powerpoint:29_Jan_2010.pptx
Week 5
- Schedule with Client for an Interim UAT test
- Updates of our Form Builder features
- Updates on our Report Builder features
Meeting Minutes:2_Feb_2010.docx
Meeting Powerpoint:5_Feb_2010.pptx
Week 6
- Held a formal UAT with the client and our supervisor
- Review on our schedule for Week 7,8 and 9
- Updates of our Form Builder features
- Updates on our Report Builder features
Meeting Minutes (UAT feedbacks):UAT.docx
Meeting Powerpoint (UAT):UAT_slides.pptx
Week 7
- Did our mid term reflection
- Review on our schedule for Week 7,8 and 9
- Further development on our Form Builder features
- Further development on our Report Builder features
Meeting Powerpoint (UAT):26feb2010.pptx
Week 8
- Development phase for the team
- 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
Meeting Powerpoint (UAT):26feb2010.pptx
Week 9
- Development phase for the team
- Edit the 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
- Started on the development of form validation
Meeting Powerpoint (UAT):5march2010.pptx
Week 10
- Week 10 is a User Acceptance Test for our client
- We finalized the development phrase and are doing intensive testing on our application.
- Test cases were tailored made for our application.
UAT Week 10 feedbacks:Week_10_UAT_Feedback.docx
Client meeting minutes: 12march2010.docx
UAT powerpoint: 12march2010.pptx
Week 11
- The team finalized our presentation slides and started on our report
- The team does an update on the current functionalities of the application.
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