1. Synergy Meeting Scheduler System GeetanjaliJeffYogita

2. Agenda Overview :Why, What, How? Overview :Why, What, How? Project Goals Project Goals Requirement Sources Requirement Sources Project Process Project Process Enterprise/System Functional Requirements Enterprise/System Functional Requirements Issues Issues Prototype Prototype

3. SDMS Overview SDMS is a web-based meeting scheduler system used to efficiently schedule meetings. SDMS is a web-based meeting scheduler system used to efficiently schedule meetings.  It accelerates the communication process and supports negotiation mechanism.  It helps the scheduler to resolve the conflicts and also supports virtual meetings/teleconferencing.

4. Why a Scheduling System? Problems Problems Lot of time spent in scheduling meetingsLot of time spent in scheduling meetings Too much work for the Initiator: inviting participants, resolving conflicts, rescheduling, sending reminders, awaiting responses, etc. Too much work for the Initiator: inviting participants, resolving conflicts, rescheduling, sending reminders, awaiting responses, etc. Manage interactions between the team participants.Manage interactions between the team participants. Traveling costsTraveling costs Participants in different geographical locations Participants in different geographical locations

5. Why a Scheduling System? Reduces time in scheduling meetings Reduces time in scheduling meetings Less time spent in scheduling meetings locations, dates, resources.Less time spent in scheduling meetings locations, dates, resources. Manage interactions between the participants effectively Manage interactions between the participants effectively Automation of typical tasks: invitations, responses, etc.Automation of typical tasks: invitations, responses, etc. Increasing employee productivity Increasing employee productivity Initiator can schedule more meetings in less time.Initiator can schedule more meetings in less time. Reduce traveling costs Reduce traveling costs Virtual meetings Virtual meetings

6. What to build? Functional requirements Functional requirements Plan meetingPlan meeting Meeting scheduling Meeting scheduling Date selection Date selection Re-plan, cancel meetings Re-plan, cancel meetings Schedule Conflict resolutionSchedule Conflict resolution Manage InteractionsManage Interactions Monitor MeetingMonitor Meeting

7. How to build ? Non-Functional Requirements Non-Functional Requirements Minimal InteractionMinimal Interaction Fast SchedulingFast Scheduling Through electronic messaging Through electronic messaging ComplianceCompliance All the manual processes must be available All the manual processes must be available Convenient Dates and LocationsConvenient Dates and Locations DecentralizedDecentralized Meetings can be scheduled independent of initiator location. Meetings can be scheduled independent of initiator location.

8. How? Uniqueness Uniqueness Locations, Participants and ResourcesLocations, Participants and Resources Performance Performance Constraints in responses and communicationsConstraints in responses and communications Privacy Privacy User-friendliness User-friendliness Customizable Customizable Private and ProfessionalPrivate and Professional Flexibility Flexibility Meeting updatesMeeting updates Extensible Extensible Support of different date formats and timezones.Support of different date formats and timezones.

9. Projects Goals To identify the requirements of customers To identify the requirements of customers  To provide and help the team participants to schedule the meeting time, date and location efficiently. Provides a prototype for customer feedback. Provides a prototype for customer feedback.

10. Previous Projects Previous Projects Customer interviews Customer interviews Group domain experiences Group domain experiences Internet Internet Requirement Sources

11. Project Process Identify Stakeholders and sources Identify Stakeholders and sources Model Enterprise and System Functional requirements Model Enterprise and System Functional requirements Model Non-functional reqs with dependency graph Model Non-functional reqs with dependency graph Specify constraints Specify constraints Document all issues Document all issues Further develop the system with resolving issues. Further develop the system with resolving issues. Develop the prototype Develop the prototype

12. Enterprise Requirements Domain level Questions Domain level Questions Identify stakeholders Identify stakeholders Environment for meetings Environment for meetings How will they take place How will they take place Issues to set up the meeting agenda Issues to set up the meeting agenda

13. Enterprise Reqs

14. Enterprise Non-functional Reqs Negotiations should be minimal Negotiations should be minimal Availability of equipments should be updated Availability of equipments should be updated All conflicts should be quickly resolved All conflicts should be quickly resolved The system should be flexible The system should be flexible

15. System Functional Requirements

16. Non-Functional Req Dependency Graph

17. Issues Incompleteness Incompleteness The system extensibility can be enhanced additionally by allowing a participant to attend only part of the meeting. The system extensibility can be enhanced additionally by allowing a participant to attend only part of the meeting. It [meeting room] should ideally belong to one of the locations preferred by as many important participants as possible. It [meeting room] should ideally belong to one of the locations preferred by as many important participants as possible. The amount of interaction among participants should be kept minimal. The amount of interaction among participants should be kept minimal. Ambiguous Ambiguous A meeting should be accurately monitored, especially when it is held in a virtual place. Here, nomadicity will then be important to consider. A meeting should be accurately monitored, especially when it is held in a virtual place. Here, nomadicity will then be important to consider.

18. Issues Difference between potential meeting attendees and participants. Difference between potential meeting attendees and participants. Clarification of criteria for expanding date range. Clarification of criteria for expanding date range. Misclassified Misclassified To make them confident about the reliability of the communications. To make them confident about the reliability of the communications. Physical constraints should not be broken. Physical constraints should not be broken. Missing Missing Missing Login and Logout requirements. Missing Login and Logout requirements. The system doesn't specify how many participants at the most can be there in a meeting. The system doesn't specify how many participants at the most can be there in a meeting. Redundancy Redundancy ‘Make participants aware of what is going on’ and ‘Keep participants informed about schedules and changes’. ‘Make participants aware of what is going on’ and ‘Keep participants informed about schedules and changes’.

19. Prototype Login Screen

20. Main Page

21. New Meeting

22. New Meeting Time Query

23. Meeting Notice (attendee)

24. Meeting Planning (Initiator)

25. Thanks!!!