Synergy Distributed Meeting Scheduling System Francisco Puente Arundhati Solapurkar Jung-Chi Lin

Agenda  Overview: Why, What and How?  Structural Requirements  Domain Model  Sequence Diagrams in a nutshell  If time permits: Prototype overview

SDMS Overview  Consider the following scenario A mid-size Software company with 80 employees working in the Professional Services department and handling 15 to 20 projects. How many meetings will be required on each project with an average of 7 participants in each meeting? Now assume that you are in charge of setting all those meetings.

SDMS Overview

Why a Scheduling System?  Common problems –Time spend in scheduling meetings  Too many activities for Initiator: participant invitations, conflict resolution, reminders, responses, etc –Interactions  Participants interactions require a lot time to be compiled by initiator.  Responses synchronization. –Traveling costs  Participants in different geographical locations

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

What to build?  Functional requirements –Plan meeting  Meeting scheduling  Date selection, Participants  Re-plan, cancel meetings –Conflict resolution  Automate resolution of common conflicts: –Date, Resource and Location –Manage Interactions  Handle communications, reminders and responses –Monitor Meeting

How ?  Non-Functional Requirements –Minimal Interaction –Fast Scheduling  Through electronic messaging –Compliance  All the manual processes must be available –Convenient Dates and Locations –Decentralized  Meetings can be scheduled independent of initiator location.

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

Activity Diagram using IDEF0 Top Level Diagram

Detailed Top Level Diagram

Third Level Diagrams Login Module

Third Level Diagrams -Plan Meeting Module

Third Level Diagrams –Resolve Conflict Module

Third Level Diagrams –Manage Interactions Module

Domain Model

Sequence Diagram – resolve conflict (extend date range)

Design Class Diagram – resolve conflict (extend date range)

Sequence Diagram – resolve conflict (Add preference range)

Design Class Diagram – resolve conflict (Add preference range)

Sequence Diagram – resolve conflict (Remove exclusion range)

Design Class Diagram – resolve conflict (Remove exclusion range)

Sequence Diagram – resolve conflict (Withdraw participant)

Prototype

Meeting Detail

Meeting History

Participant response