Meeting Scheduling System DescriptionWith the advent of globalization, companies and organizations are increasingly distributed over multiplesites and countries. Dhahran Software Services $($DSS$)$ has identified a large potential market for meeting$-$scheduling software exploiting internet$-$based communications technologies. In general, meetings tendto be organized poorly and late; important people sometimes do not show up$,$ and the scheduling processhas a significant, unnecessary overhead.Meetings are typically scheduled as follows. A meeting initiator informs potential participants about theneed for a meeting and specifies a date range within which the meeting should occur, asking people toreturn their availability constraints within the interval. Constraints are typically expressed as two sets: anexclusion set specifying dates within the date range when the participant could not attend and an optionalpreference set specifying dates within the date range on which the participants would prefer the meetingto take place $($date may refer to a full day or a period in a day$).$ In some cases, the initiator may also askparticipants who will play an active role in the meeting for specific requirements regarding the meetingroom $($e$.$g$.,$ projector, laptop, network connections, videoconferencing facilities, etc.$).$ Importantparticipants may optionally be asked to state preferences for meeting locations.The scheduled meeting date should belong to the stated date range and none of the exclusion sets; itshould ideally belong to as many preference sets as possible. The meeting venue should ideally fit thepreferences of important participants. A date conflict occurs when no date can be found outside allexclusion sets. A room conflict occurs when no room can be found at any date outside all exclusion setsthat meet the room requirements. Conflicts can be resolved in several ways: the initiator may extend thedate range, some participants may remove dates from their exclusion set, or some participants maydecline the invitation to attend. A new scheduling cycle may thus be required in case of conflict.The new meeting scheduler must be able to handle multiple meeting requests in parallel. Meetingrequests can compete by overlapping in time or space. Concurrency must thus be managed under physicalconstraints; a person may not be in two different places at the same time, and a meeting room may notbe allocated to more than one meeting at a time.To allow as much flexibility as possible, dynamic preplanning of meetings should be supported. On theone hand, participants should be allowed to modify their exclusion set, preference set, and $/$or preferredlocation until the meeting is scheduled. On the other hand, exceptional constraints should beaccommodated after a meeting is scheduled, such as the need to schedule an urgent, more importantmeeting. The original meeting date or location may need to be changed; sometimes, it may even becanceled. In all cases some way of preplanning should be set up$.$Using UCM, model the scenario where the meeting scheduler system receives a meetingrequest from the meeting initiator, checks availability of important participants on therequested date, then availability of requested meeting location. If important people are notavailable, the meeting scheduler system rejects the meeting request and ask for a newrange of dates. If the requested meeting location is not available, the meeting schedulersystem recommends other available locations and wait for the approval from the meetingrequester. If the dates and location are available, the meeting scheduler system sends aconfirmation to the meeting initiator

Draw