Saturday, 3 September 2011

03.09.11 (Meeting Minutes)

Date: 03.09.2011
Venue: Student Lounge, Level 4
Duration: 60 minutes
Attendence: Subash (SB), Wee Ying (WY), Yong Xiang (YX), Melvyn (MB)
 
Discussion of the meeting are as followed:
 
1. Change all the existing documentations/ report (Example: Proposal) into 'Chapters'. Ensure that all the wording forms are standardised. Spelling, vocabulary, grammer mistakes are checked.
 
2. Test Plan shall be the last chapter.
 
3. Add in another chapter for 'Additional Features'. Highlight about why this product can bring us further into the future (future expansion of our product). About 5 more additional features.
 
4. Add in another chapter on what we have learnt, what is the technical problem we have face (as a team and individually).
 
5. Final chapter: Overall conclusion (From the start of the project till the end.)
 
6. Dedicate 2 team members to work on the creation of conference booking audio and video CD ROM. At this same time, this can become part of the group online help.
 
Tips for the Final Presentation:
 
1. Go directly into creating of conference booking. Do not waste time on creating user account, login authentication and so on.
 
2. When the group ppt slide show on the product function, immediately the group should show the product GUI. Do not wait till after going through all the functions in the ppt THEN show the product function in the GUI.
 
3. Create a storyline for the presenting of conference booking.
 
4. Output of booking should store into the CSV file (PCI requirement).
 
5. For the payment part, do mention that "we are ONLY presenting the data format of payment gateway because we are not sure of what will really happen next. But we are still exploring the possibilities."
 
The next meeting with Mr Ee will be scheduled on 17 Sept 2011, at 12PM.

Tuesday, 23 August 2011

20.08.2011 (Meeting Minutes)

Date: 20.08.2011
Venue: Student Lounge, Level 4
Duration: 60 minutes
Attendence: Subash (SB), Wee Ying (WY), Yong Xiang (YX), Melvyn (MB)
Discussion of the meeting are as followed:
  • For the discussion forum and IM, can the group copy and paste images into the chat window?
  • When we only allow the user to view our uploaded document. In order to safeguard the doc copyright, can the group disable the 'Save as ...' button.
  • Stimulating a database table which is always running and it will pull data from the table instead of hard code the booking of flight.
  • Complete the test plan documentation
  • Will meet Mr Ee on the 3rd of Sept; beta version which is close to release.
----------------------------------------------------------------------------------------------

Group have interview with Bernard on 12th August 2011.

SIM Booking System

Q: What are the things you need in a booking system?
Bernard: Need to know time, date, venue and special features. Special functions like can we book projectors, how many seaters (capacity), requirements (extra projectors, extra chairs), and special arrangement of chairs. Nobody (companies) will allow you to choose, you just request what you want.

Q: How you know how the place (conference room) looks like? 
Bernard: Client will come, let you see the place, like go book wedding package, you'll go look at the different wedding hall.

Q: Do you have booking payment system embedded?
Bernard: No payment in the booking system. Normally it is a quotation, will not have payment.

Q: Does the booking system have refreshment menu and do they have choices?
Bernard: Yes. Usually for refreshments, they will give you some choices, if you want to bring outside food, need to pay corkage. They will give you menus, to choose. You might want to add in options for registration table, extra manpower, potted plants, need to do requesting... prices normally will not be known as potted plants might have different prices (i.e. roses $1, orchid $2, etc)

Q: Normally if you have a certain spot cannot book, will the booking system have any AI? 
Bernard: NO, they will not prompt out. They will list out other available slots. If you want to do higher level, when click on the available slots, can see the room hovering.

Q: Do you charge internally using credit cards?
Bernard: Normally will not charge internal dept as its left pocket to right pocket, unless it's for external parties. So payment is relatively not important.

Q: Do you book training sessions for internal training? 
Bernard: SIM book external parties. Our speakers provide us the slides to print, then you have to provide all the services for the speakers, whatever the speakers wants, it is for the representatives to provide, speakers only come and talk.

Q: For the system email function do you do it manually on another system or the booking system has the function?
Bernard: Have to send emails manually, not by system. Different applications cannot integrate as SIM bought different applications. For instances, have to pull data from application 1 to application 2, some softwares cannot talk to each other. 

Q: For example, when you encounter problems, who do you approach? 
Bernard: 2 ways, one internal, one is vendor. Have to be quick, normally is service desk. 


Q: What are the things you need in a booking system?
Bernard: Need to know time, date, venue and special features. Special functions like can we book projectors, how many seaters (capacity), requirements (extra projectors, extra chairs), and special arrangement of chairs. Nobody (companies) will allow you to choose, you just request what you want.

Q: How you know how the place (conference room) looks like? 
Bernard: Client will come, let you see the place, like go book wedding package, you'll go look at the different wedding hall.

Q: Do you have booking payment system embedded?
Bernard: No payment in the booking system. Normally it is a quotation, will not have payment.

Q: Does the booking system have refreshment menu and do they have choices?
Bernard: Yes. Usually for refreshments, they will give you some choices, if you want to bring outside food, need to pay corkage. They will give you menus, to choose. You might want to add in options for registration table, extra manpower, potted plants, need to do requesting... prices normally will not be known as potted plants might have different prices (i.e. roses $1, orchid $2, etc)

Q: Normally if you have a certain spot cannot book, will the booking system have any AI? 
Bernard: NO, they will not prompt out. They will list out other available slots. If you want to do higher level, when click on the available slots, can see the room hovering.

Q: Do you charge internally using credit cards?
Bernard: Normally will not charge internal dept as its left pocket to right pocket, unless it's for external parties. So payment is relatively not important.

Q: Do you book training sessions for internal training? 
Bernard: SIM book external parties. Our speakers provide us the slides to print, then you have to provide all the services for the speakers, whatever the speakers wants, it is for the representatives to provide, speakers only come and talk.

Q: For the system email function do you do it manually on another system or the booking system has the function?
Bernard: Have to send emails manually, not by system. Different applications cannot integrate as SIM bought different applications. For instances, have to pull data from application 1 to application 2, some softwares cannot talk to each other. 

Q: For example, when you encounter problems, who do you approach? 
Bernard: 2 ways, one internal, one is vendor. Have to be quick, normally is service desk. 


Q: We have live help, is it feasible? 
Bernard: Need to see if the personnel are there. Normally... usually should be from IT dept.

Q: Is the GUI fascinating? 
Bernard: No, same as SAP. We have to learn lots of things. Have to take time to learn. Mostly now is mouse over and something will appear.

Q: Do you create accounts for other people?
Bernard: Each of us has an individual account. (All internal staff)

Q: How do the attendees know about agenda?
Bernard: Via email, will let attendees know the agenda (Program list).

Bernard’s Advice:
  •  Have some animations like fading in and out, so that it will not look so plain. But basically, your functions must be good. 
  • Ask for IT show venue booking to enquire about price quotation. 
  • Actually, internal charges exist, but booking staff can't see the money transferring. Only finance staff will move the money around, booking staff doesn’t need to care.

Friday, 12 August 2011

12.08.11 (Interview Session with Bernerd)

Hi all,

Interview session with Bernerd has been confirmed. As below:

Date: 12.08.2011
Venue: SIM, Level6
Attendence: Melvyn (MB), Subash (SB), Wee Ying (WY), Yong Xiang (YX)

See you guys.


06/08/11 (Meeting Minutes)

Date: 06.08.2011
Venue: Student Lounge, Level 4
Duration: 60 minutes
Attendence: Subash (SB), Wee Ying (WY), Yong Xiang (YX)
Absence: Melvyn (MB)

Discussion of the meeting are as followed:
  • In our invitation e-mail, group can include the agenda, map to the LT, etc.
  • Pre-conference which includes a group of speakers with read/write permissions to exchange documents within themselves.
  • Conference which includes everyone including the speakers with read permissions (so no one is able to edit the documents during the conference).
  • Remote help support for live chat.
  • Resolving conflicts such as concurrent booking at the same time (e.g. 2 users booking the same place and time. Will this happen? Will it create duplicate entries? If yes, we will have to resolve this issue).
Project Manager YX has dedicated the following tasks to the members:

  • YX and SB will work on the coding.
  • WY will create the Facebook, Twitter and Gmail accounts. (Group take note that out gmail account ID is conorganizer@gmail.com, apply to the rest of the created accounts too.)
  • MB willl help to talk to the hosting people.
  • YX will drop an e-mail to Bernard and ask him if we can have a session with him to ask him more about conferences and seek his views on our organizer. 
Our next meeting with the supervisor is on 20th August at 10.30am. We'll meet at the student lounge again. We need to present to him the alpha version.

Friday, 22 July 2011

17.07.11 (Meeting Minutes)

Date: 19.07.2011
Venue: Student Lounge, Level 4
Duration: 60 minutes
Attendence:   Melvyn (MB), Subash (SB)
Absence: Wee Ying (WY), Yong Xiang (YX)
 
Discussion of the meeting are as followed:
  • Group will meet Mr Ee next on 6 aug 10am to show him 75% of our product completed.
  • Group are told to host it and show to assessor that it is able to be accessed anywhere as long as we are connected to the internet. 

16.07.11 (2nd Lecture)

Date: 16.07.2011 (Mid Presentation)
Venue: Level 4-25
Duration: 45 minutes
Attendence: Yong Xiang (YX),  Melvyn (MB), Wee Ying (WY), Subash (SB)


  •  Jappi mention that the group submitted documentation belongs to the RUP model documentation rather than the Waterfall model documentation, but he mention that is okay. Group do not need to make any changes.
  • Jappi reminded the group to upload all the documentation to the project website. Website should be password protected and group should inform Mr Ee and access-or of the website protected password.
  • Jappi highlighted to the group that the website search engine should be smart enough to  filter result according to the user search criteria, else if none of the search criteria match; the search engine should filter to the result closest to the user search criteria.
---------------------------------------------------------------------------------------------

Internal Discussion
  • Though group SMS Gateway fail to work but group have decided to at least configure our website in a way similiar to Outlook. Least it will be able to send notification to keep track of attendance (Accept, Reject, Tentatively...)

Tuesday, 12 July 2011

11.07.11 (Meeting Minutes)

Date: 11.07.2011
Venue: Student Lounge, Level 4
Duration: 180 minutes
Attendence: Yong Xiang (YX),  Melvyn (MB), Wee Ying (WY)
Absence: Subash (SB)
 
Discussion of the meeting are as followed:
 
  • Mr Ee mentioned to the group to consider about the 'Commerical Conferencing' available in the market. Commerical ways of conferencing which will help the organizer to sell conference tickets. (Example: Notification alert of how many tickets has been sold.)
  • Mr Ee mentioned to the group to think through what will be the next stage of development as project accessor will most lightly question on. Group need to take note that the project accessor will joint down accordingly what the group mention can be done. These 'mention can be done' will be expected to be shown during the final presentation.
  • It will be good for the group to provide an explaination on the project scope (Internal or external conference organizer).
  • Mr Ee advice group to think through on the 'Add-on services' rather than a 'Book-on services'.
  • Mr Ee advice group to think more about the complexity of the project, and not just the basic functions.
  • Mr Ee reminder the group to print out all the documentation and burn into CD ROM for submittion.
  • Group will meet Mr Ee on next Tuesday 12.07.11 tentatively.
---------------------------------------------------------------------------------------------
INTERNAL GROUP DISCUSSION
  
  • Instead of paying by Paypal/Visa, group has discussed to make the payment to 'check-out' a lists of items (2 suggested methods: 1. Attachment of PDF (Background job processing) 2. Copy & Paste into Clipboard > click on 'confirmation button' > Pop out a Microsoft Exchange email (Email 'To' will be the reporting supervisor for approval) Amount will be deducted from the individual Head of Department yearly budget sum for such events.
  • Group understand that it is a rather reluctant job for the user to do the online feedback. Group has decided in order to encourage user to provide feeedback to us, online evaluation (which include rating of speaker) using the 'Randomese method' (something like a lucky draw!)
  • Sending SMS Config to record 'attendance' and choosing of food types:
Attendance:
Reply 1. Attending 0. Not Attending
Food Types:
Reply 0. Chinese 1. Western 2. Muslim 3. Vegeterian
Followed by confirmation reply from the server:
Thank you for participating. / Thank you. We have acknowledge your food choice.  
  • Group has discussed to use Vista.uow discussion forum layout.
  • User will ONLY make payment after the event has been carried (as it is only for our own internal staff usage). 
  • Group discussed to add in the 'Department' textbox in the admin control panel. It will be a dropdownlist which consist of director, manager, junior. This will help in the 'payment', 'To' email will use the email listed and shown in the 'To' textbox.
  • Group is to think through on what will be the most lightly asked question during the presentation.
  • Group selling points will be 1. Book accomodation. 2. Book transport 3. Training for our speakers 4. Google map 5. Statistical surveys 6. Forum 7. Live Chat
 

Friday, 8 July 2011

Postponing of 9th July FYP meeting

Due to a last minute teaching class by Mr. Ee, the FYP meeting on Saturday will be postponed to next Monday, 11th July 7.30pm, at Student Lounge (level 4).

Friday, 1 July 2011

25.06.11 (Meeting Minutes)

Date: 25.06.2011
Venue: Student Lounge, Level 4
Duration: 90 minutes
Attendence: Yong Xiang (YX), Subash (SB), Melvyn (MB)
Absence: Wee Ying (WY)
Discussion of the meeting are as followed:
  • Group need to present at least 25% of our product to assessor on 16 July 2011 (2nd lecture). We will present the Admin Control Panel module.
  • Once Mr Ee has approved all the documentations group need to print them out for submittion.
  • Group product name will be iCO (i-ConferenceOrganizer).
  • Group will adapt the color of white and grey.

04.06.2011 (Meeting Minutes)

Date: 04.06.2011
Venue: Room 6 Theta at Level 3.05A
Duration: 90 minutes
Attendence: Yong Xiang (YX), Melvyn (MB), Wee Ying (WY)
Absence: Subash (SB)  
Mr Ee has reviewed our documentation as followed:
  • Software Requirements Analysis (Include: Functional and Non-Functional Requirements)
  • Database Design (ER diagrams)
  • Software Architecture Design
Mr Ee has given us the head go to proceed on with the other documention cover as follow:
  • GUI Design (Submittion on 7 June 2011)
  • System Component Design (Submittion on 20 June 2011)

YX has dedicated roles delegation for the group as follow:


YX:
  • Handle User Profile (all), Attendees Group (Delete), Booking (all except 1, 3 and 4) and Discussion Forum GUI design. 
MB:
Database Design documentation:

  • Add multiplicity
  • Describe what each class does in short sentences
  • Describe relationship between classes 
Software Requirement Analysis documentation:
  • Check through the document, make sure there's a paragraph description below each use case/sequence diagram.
  • Check non-functional requirements and paragraph nicely.
Handle Conference (all)

SB:
  •  Give some explaination on Software Architure Documentation (Page 5 -7)
WY:
  • Handle Admin Control Panel (all)

Group members are to complete the above tasks dedicated by latest Monday night for review before final submittion to Mr Ee. Thanks. The next FYP meeting is scheduled on Saturday, 25 June at 9.45am (TBC).

Tuesday, 31 May 2011

Meeting scheduled on 04.06.11

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.

30.05.11 (Meeting Minutes)

Date: 30.05.2011
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 has dedicated roles delegation for the group as follow:
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
MB:
  • Admin and Representative sequence diagrams for CONFERENCE
SB:
  • Non-functional requirements
Breakdown of CONFERENCE and BOOKING functions are as follow:

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:
  • Software Requirements Analysis (Include: Functional and Non-Functional Requirements)
  • Database Design (ER diagrams)
  • Software Architecture Design
Attendence is compulsory. Thank you.

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.

Meeting on 19.05.11 rescheduled to 21.05.11

Date: 21.05.11
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. 
Group should amend each of these and submit to Mr Ee before Tuesday 2359PM. This amended project proposal will be in version0.2.

Wednesday, 18 May 2011

Meeting scheduled on 19.05.11

Hi all,


Meeting with Mr Eee will be as scheduled:


Date: 19.05.2011
Venue: Room 6 Theta at Level 3.05A
Time: 8PM


Attendence is compulsory. Thank you.

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:
  • 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.).
Group please refer to your email for example. Thanks.

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.

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)


  • 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.
Tentatively the next meeting will be scheduled on 9 May 2011.


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)

  • 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.
The next meeting will be scheduled on 5 May 2011.

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.


Saturday, 30 April 2011

Reminder

* Group take note to book meeting room on 19 May 2011 at 8PM, with the supervisor.
* Group will be meeting on next Tuesday (3 May 2011) to discuss on the scope of work.

Lecture 1 Briefing + Meeting Minutes

Project Plan consist of:
  • Project description
  • Planned scheduled
  • Create Blog
  • Specific requirement (Role & Responsibilities)
Major Steps:
  1. Receive project plan
  2. Conduct research
  3. Identify functionalities
  4. Summarize research findings
  5. Firm up on the functionalities
  6. Choose development method
  7. Choose development tools
  8. Create prototype (Week 7)
  9. Create premliminary documents
* Kindly note that all documents must be identified with group number.


30 April 2011 Meeting minutes 
Conducted By: Mr Ee Kiam Keong
  • Send email of group member names (including the student number), email address, contact number and appoint a Project Manager by today.
  • Develop a product that must be used!*
  • Market research of similiar various of product in the market.
  • The good function of these market (choose at least 5 types).
  • Why are they not doing very well compared to the others market.
  • What are they lack of (user expect they have but they dont have).
  • Who is your target audience (finalise on this then define your product functionality).
  • 45%  is what the competitor doing very well, 30% is what they are not doing very well and 25% is what they are lack of.
  • Type of programming language and structure.
  • By next friday supervisor will expect the scope of work from the group.
  • Recording capabilites of the meeting minutes must be in place.
  • Supervisor must be inform of the selected blog.
  • What is the team strategy in presentation.
  • Online survey, feedback, analysis the market statictics can all be showcast in the presentation.
  • Is ONLY after the scope of work is agreed then the group work on the functional and non-functional requirement.
  • Prototype start on Week 7.
All the group members have attended the FYP first lecture. We have discussed and appointed Yong Xiang as the Project Manager. He will be sending email of the group members details to inform Mr Ee.

FYP - Project Allocation

As scheduled (Lecture 1):
Date: 30th April 2011
Day: Saturday
Time: 10AM - 12PM
Venue: LT 3-16

Upcoming (Lecture 2):
Date: 16th July 2011
Day: Saturday
Time: 10AM - 12PM
Venue: LT 4-25 (Lecture follow by BIT demo)


FYP Project Allocation:
Topic                : Conference Organizer
Group               : IT11/2G
Assessor           : Mr Premarajan
Assessor Email  :  premrajan_p@yahoo.com
Supervisor         : Mr Ee Kiam Keong
Supervisor Email: kkeesg@yahoo.com.sg


Group members include:
Name  : Low Wee Ying (3998599) 
Email   : low_wee_ying@hotmail.com 
Contact: 9144 7629


Name  : Melvyn Dominic Brown (3934287)
Email   : melvyn_d_brown@hotmail.com
Contact: 9139 8254


Name  : Peechampilly Raman Subash Sharma (3934858)
Email   : subhash007@gmail.com
Contact: 8268 9807


Name  : Soh Yong Xiang (3934834)
Email   : wallacesoh@gmail.com
Contact: 9790 5807