The purpose of the meeting scheduler system is to support the organization of meetings - that is, to determine, for each meeting request, a meeting date and location so that most of the intended participants will effectively participate. The meeting date and location thus be as convenient as possible to all participants. Information about the meeting also be made available as early as possible to all potential participants by email for all meeting participants. The intended system considerably reduce the amount of overhead usually incurred in organizing meetings where potential attendees are distributed over many different places. On another hand, the system reflect as closely as possible the way meetings
The system should assist users to plan meetings under the constraints expressed by participants, re-plan a meeting dynamically to support as much flexibility as possible. On one hand, participants should be allowed to modify their exclusion set, preference set and/or preferred location before a meeting date/location is proposed. On the other hand, it should be possible to take some external constraints into account after a date and location have been proposed - e.g., due to the need to accommodate a more important meeting. The original meeting date or location may then need to be changed; sometimes the meeting may even be cancelled. In all cases some bound on re-planning should be set up.
- Every project include mechanisms for signing up, signing in, and signing out.
- Signing up process should include the following a. The form must use a captcha whether online or offline like “google captcha” …etc. b. During the registration the user will not supply a password c. After the form submission an email will be sent to the user with a generated temporary password to login the application with it.
- All users should be able to change their information in the profile page like password, display name…etc. except for the username.
- Sessions must be enforced with the user’s interaction.
- The project must use a unified CSS style for all the pages you can build your own or.
- Ajax should be used in at least three different scenarios including signing up (to check if the user registered before).
- All input forms must be validated either by using HTML5 controls, Java script or jQuery
- Every interaction from the user must be presented with a proper feedback from the system like success / failure messages, alert…etc.
- Usage of “Hibernate” for the DB communication is encouraged.
- Meaningful data examples should be present in your database at least five examples in every table are presented.
- The word “Manage” in the requirements is translated to all the CRUD operations (Insert/add – Update – Delete – Select)
- Create, Update, Edit Meetings
- View All Meeting with list and Cards View
- Signup ,Login Users
- Make Meetings Rooms with (chat - share screen - share vedio - record vedio and screen - share room url )
we use intellij IDE and use mysql workbench 8.0 and tomcat server
Note : Meeting room create by two providers, i use this two rooms providers because I encountered many problems with jsp servlet technology in this part (makeing meeting room) so i use this two providers and generate meeting room urls.
Mohamed Hamdy Mohamed - @LinkedIn - LinkedIn