Hi all,
This is a reminder. Upcoming scheduled meeting with Mr Ee will be scheduled on:
Date: 04.06.2011
Venue: Room 6 Theta at Level 3.05A
Time: 0945AM
Attendence is compulsory. Thanks.
Tuesday, 31 May 2011
30.05.11 (Meeting Minutes)
Date: 30.05.2011
CONFERENCE:
1. Search: TBA
2. Create: TBA
3. Modify: TBA
4. Upload documents: Admin / Presenter / Representative (help 3rd party speaker)
5. Manage read/write permissions: Admin / Presenter / Representative (help 3rd party speaker)
6. Send conference invites: Admin / Representative
7. Send SMS alerts: Admin
8. Record conference: TBA
9. Upload conference videos: Admin
10. Send PM: All
11. Conference agenda (e.g. list of conferences for next month): Admin
BOOKING:
1. Search: Admin / Presenter / Representative
2. Flash overview: All
3. Create: Admin / Representative
4. Modify: Admin / Representative
5. Booking history: Admin / Representative
6. Cancel: Admin / Representative
7. Extra equipments: Admin / Presenter / Representative
8. Refreshments: Admin / Representative
9. Payments: Admin / Representative
10. Request travel and accommodation: Admin / Presenter / Representative
Note: Group memebers kindly try to do everything and submit early. Perhaps before June 1-2.
So we got enough time to review together. Thanks!
Venue: SIM Lect 3-17
Duration: 90 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
Discussion on the upcoming submittion of documention cover as follow:There will be 4 actors:
- Admin
- Presenter / Speaker
- Representative
- Attendees
YX:
- Edit the existing use case diagram (overview) according to the attached scanned picture
- Edit the existing individual use cases for each module to add in actors for each individual functions
- Presenter sequence diagram for CONFERENCE
- Presenter sequence diagram for BOOKING
- All sequence diagrams for USER PROFILE
- All sequence diagrams for DISCUSSION FORUM
- Admin and Representative sequence diagrams for ATTENDEES GROUP
WY:
- Admin and Representative sequence diagrams for BOOKING
- Admin sequence diagram for ADMIN CONTROL
- Admin and Representative sequence diagrams for CONFERENCE
SB:
- Non-functional requirements
CONFERENCE:
1. Search: TBA
2. Create: TBA
3. Modify: TBA
4. Upload documents: Admin / Presenter / Representative (help 3rd party speaker)
5. Manage read/write permissions: Admin / Presenter / Representative (help 3rd party speaker)
6. Send conference invites: Admin / Representative
7. Send SMS alerts: Admin
8. Record conference: TBA
9. Upload conference videos: Admin
10. Send PM: All
11. Conference agenda (e.g. list of conferences for next month): Admin
BOOKING:
1. Search: Admin / Presenter / Representative
2. Flash overview: All
3. Create: Admin / Representative
4. Modify: Admin / Representative
5. Booking history: Admin / Representative
6. Cancel: Admin / Representative
7. Extra equipments: Admin / Presenter / Representative
8. Refreshments: Admin / Representative
9. Payments: Admin / Representative
10. Request travel and accommodation: Admin / Presenter / Representative
Note: Group memebers kindly try to do everything and submit early. Perhaps before June 1-2.
So we got enough time to review together. Thanks!
Tuesday, 24 May 2011
Meeting scheduled on 04.06.11
Hi all,
The next scheduled meeting with Mr Ee will be scheduled on:
Date: 04.06.2011
Venue: Room 6 Theta at Level 3.05A
Time: 0945AM
Document to be completed before the scheduled meeting with Mr Ee:
The next scheduled meeting with Mr Ee will be scheduled on:
Date: 04.06.2011
Venue: Room 6 Theta at Level 3.05A
Time: 0945AM
Document to be completed before the scheduled meeting with Mr Ee:
- Software Requirements Analysis (Include: Functional and Non-Functional Requirements)
- Database Design (ER diagrams)
- Software Architecture Design
21.05.11
After discussion, Project manager YX has dedicated amendment of project proposal work task to the group members. As below:
WY: Categorizing the scope into 3 main categories (Administrative, Security and User Functions).
MB: Restructure BACKGROUND into paragraphs and come up with a comparison table of features for RESEARCH.
SB: Come up with 2-3 comparisons and brief description for each development tool.
YX: Come up with 2-3 comparisons and brief description for development methodology, move Risk Analysis table to Appendix and restructure numbering of report.
At the same time, YX has also dedicated the work task of the Software Requirements Analysis documentation as below:
WY: Administrative use cases and sequence diagrams.
MB: User Attendees use cases and sequence diagrams.
SB: Non-Functional Requirements.
YX: User Presenters use cases and sequence diagrams.
YX will be booking the discsussion room scheduled on 04.06.11 with Mr Ee.
WY: Categorizing the scope into 3 main categories (Administrative, Security and User Functions).
MB: Restructure BACKGROUND into paragraphs and come up with a comparison table of features for RESEARCH.
SB: Come up with 2-3 comparisons and brief description for each development tool.
YX: Come up with 2-3 comparisons and brief description for development methodology, move Risk Analysis table to Appendix and restructure numbering of report.
At the same time, YX has also dedicated the work task of the Software Requirements Analysis documentation as below:
WY: Administrative use cases and sequence diagrams.
MB: User Attendees use cases and sequence diagrams.
SB: Non-Functional Requirements.
YX: User Presenters use cases and sequence diagrams.
YX will be booking the discsussion room scheduled on 04.06.11 with Mr Ee.
Meeting on 19.05.11 rescheduled to 21.05.11
Date: 21.05.11
Venue: Room 6 Theta at Level 3.05A
Mr Ee has went through the project proposal with the group. As below are the number of things he highlighted :
Venue: Room 6 Theta at Level 3.05A
Time: 1015AM
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)Mr Ee has went through the project proposal with the group. As below are the number of things he highlighted :
- Proposal should have chapters.
- Proposal should not be in point form, it should be in proper paragraphe.
- Proposal should be formal; more to a client base.
- 'Core functions' should be further catergorise. (Example: Network, security and so on.)
- Comparsion of group V-Model with at least 3 other types of model.
- Comparsion of group Database with at least 3 other types of database. (Example: Oracle.)
- 'Risk List' should include 'A table of Risk Analysis perform by group is referred to Annex A.'
- 'Research' should include a checklist of features between group and competitior.
Wednesday, 18 May 2011
Meeting scheduled on 19.05.11
Saturday, 14 May 2011
13.05.11 (Meeting Minutes)
Date: 13.05.2011
Venue: SIM Lab 5-19
Duration: 45 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
Upcoming project proposal consist of:
Venue: SIM Lab 5-19
Duration: 45 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
Upcoming project proposal consist of:
- Use case digram (Include user login, administrator login, finance personnel login).
- Database conceptual schema diagram.
- System architecture (choice of programming language).
- Types of application used (Example: Web application).
- System specification (Example: Window server 2003).
- Security and privacy.
- System testing (White and black box testing. Requirement need to be defined.).
Tuesday, 10 May 2011
Project scope
Fyp project proposal has been finalise. Mr Ee has given us the green light to proceed with the project proposal. Thanks Mr Ee for the prompt response.
Functions as below:
1. Separate login page for users & administrators (Segregate duties assigned.)
2. Authentication method for applied for the user and attendees with the backend database.
3. Information of the presenter, attendees and delegates will be stored in the backend database.
4. Book a conference room based on availability. (Example: Date, Time, Room No.)
5. User able to search for free booking slots based on a particular conference room /all conference rooms.
6. Users can modify an existing booking
7. Able to view existing booking made by the logged in user.
8. Cancel the existing booking.
9. User able to book extra equipments needed for the conference (Microphone, Projector, White Board etc).
10. User able to book refreshments for the conference attendees.
11. A GUI of the flash movie overview of the conference room seating arrangements will be displayed.
12. Web site allow the the presenter or speaker to upload presentation documents.
13. Web site allow the presenter to assign read/write permissions for selected users to read/write the presentation documents.
14. Web site support email notification alert each time a creation or modification of documentation was make by the users or attendees.
15. Allow the presenter to select a list of users and send them conference invitation to their respective emails.
16. Allow the presenter to make payment using credit card for the services and conference room booking.
17. Allow the presenter to request for Flight ticket and / or accommodation booking for specific dates.
18. Allow the application admin to add/delete conference rooms, add/delete conference equipments, update the rental rates for conference rooms and AV equipments, view the booking report monthly / weekly, add/delete the refreshment items etc
19. Book a Cab using SMS.
20. Web site is able to send SMS alerts to conference attendees regarding conference detail before the actual day.
21. Provide Live help (Live Chat) with the site administrator
22. Allow presenter to record attendance of attendee’s during the conference.
23. Allow the presenter to upload conference videos for those who have missed to attend the conference.
24. Provide online survey regarding the conference.
25. Allow the users of the site to send private messages.
26. Allow the users to follow the website on Facebook, Twitter, etc.
27. Provide an agenda of the conferences for a month.
28. Provide detailed agenda of the conference with description.
29. Allow the user to register for website news letter through email.
30. Allow the users of the website to search a specific street name and display the location in an interactive map (Using Google Maps).
31. Provide a discussion forum so that attendees can discuss conference matters with presenters.
Special features:
1. Provide speaker training.
2. Give them a rundown sheet or a checklist.
3. Send example videos from previous years.
4. Provide a volunteer in the room during the session.
5. Provide confidence monitors in event room.
6. Rate your speakers and share the data.
7. Provide audience demographics.
8. Provide the attendees with a floor plan of the conference room.
Functions as below:
1. Separate login page for users & administrators (Segregate duties assigned.)
2. Authentication method for applied for the user and attendees with the backend database.
3. Information of the presenter, attendees and delegates will be stored in the backend database.
4. Book a conference room based on availability. (Example: Date, Time, Room No.)
5. User able to search for free booking slots based on a particular conference room /all conference rooms.
6. Users can modify an existing booking
7. Able to view existing booking made by the logged in user.
8. Cancel the existing booking.
9. User able to book extra equipments needed for the conference (Microphone, Projector, White Board etc).
10. User able to book refreshments for the conference attendees.
11. A GUI of the flash movie overview of the conference room seating arrangements will be displayed.
12. Web site allow the the presenter or speaker to upload presentation documents.
13. Web site allow the presenter to assign read/write permissions for selected users to read/write the presentation documents.
14. Web site support email notification alert each time a creation or modification of documentation was make by the users or attendees.
15. Allow the presenter to select a list of users and send them conference invitation to their respective emails.
16. Allow the presenter to make payment using credit card for the services and conference room booking.
17. Allow the presenter to request for Flight ticket and / or accommodation booking for specific dates.
18. Allow the application admin to add/delete conference rooms, add/delete conference equipments, update the rental rates for conference rooms and AV equipments, view the booking report monthly / weekly, add/delete the refreshment items etc
19. Book a Cab using SMS.
20. Web site is able to send SMS alerts to conference attendees regarding conference detail before the actual day.
21. Provide Live help (Live Chat) with the site administrator
22. Allow presenter to record attendance of attendee’s during the conference.
23. Allow the presenter to upload conference videos for those who have missed to attend the conference.
24. Provide online survey regarding the conference.
25. Allow the users of the site to send private messages.
26. Allow the users to follow the website on Facebook, Twitter, etc.
27. Provide an agenda of the conferences for a month.
28. Provide detailed agenda of the conference with description.
29. Allow the user to register for website news letter through email.
30. Allow the users of the website to search a specific street name and display the location in an interactive map (Using Google Maps).
31. Provide a discussion forum so that attendees can discuss conference matters with presenters.
Special features:
1. Provide speaker training.
2. Give them a rundown sheet or a checklist.
3. Send example videos from previous years.
4. Provide a volunteer in the room during the session.
5. Provide confidence monitors in event room.
6. Rate your speakers and share the data.
7. Provide audience demographics.
8. Provide the attendees with a floor plan of the conference room.
Friday, 6 May 2011
05.05.11 (Meeting Minutes)
Date: 5 May 2011
Venue: SIM Lab 5-14
Duration: 50 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
Below are the chain of email of ideas the group have contributed
(Do click on the picture for a clearer view.):
Venue: SIM Lab 5-14
Duration: 50 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
- Finalise on the scope of work to be accomplished before submittion to Mr Ee.
- Go through each of the special features mentioned contributed by the group.
- Discusson on speaker being able to book flight ticket in our web page.
- Corporate organisation will be the group target audience.
- Functionality like Paypal payment and booking of flight might involve third party application.
Below are the chain of email of ideas the group have contributed
(Do click on the picture for a clearer view.):
03.05.11 (Meeting Minutes)
Date: 3 May 2011
Venue: SIM LT 2-09B
Duration: 1 hour 40 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
Venue: SIM LT 2-09B
Duration: 1 hour 40 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB), Wee Ying (WY)
- Group unsure about the job scope.
- After reading the project specification, group concluded that the project is more like a internal conference organizer. (Internal conference organizer means that we rent out our space for event, rather than sourcing out for space available.)
- Group do not understand project specification on '..by working paper, camera ready, publication date..' Is this web conferencing or...?
- Privilege right for administrator, financial personnel, user login should be catergories differently.
- Group need to apply domain name for our own website?
- About the payment part, is it paypal hosting or in order for the payment to work we can propose to request the customer to download and fill in the payment form > scan > send it over to us. But in this way, it will be insecured.
- Discussion on the user right of each personnel. Read, write, execute.
- Brainstorm on the 'X' factor about us as a conference organizer and who will be our target audience.
- Uploading of files to the web is sharing to a web server or a local host.
- Discussion on security issue like HTTPS, SSL, CA to tighten security on our project.
Sunday, 1 May 2011
Plan and Checklist
Mr Ee have sent us project plan and preparation checklist. Project group please check your email. Thanks.
Roles and Responsibilities Assigned
Upon agreed on the roles and responsibilities assigned to each individual, Project Manager Yong Xiang have sent Mr Ee email on group members information + roles and responsibilites documentation.
![]() |
| Table of Roles & Responsibilities. |
Subscribe to:
Comments (Atom)




