Title: Synergy Distributed Meeting Scheduling System
1Synergy Distributed Meeting Scheduling System
- Francisco Puente
- Arundhati Solapurkar
- Jung-Chi Lin
2Agenda
- Overview Why , What and How?
- Structural Requirements
- Domain Model
- Sequence Diagrams in a nutshell
- If time permits Prototype overview
3SDMS 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.
4SDMS Overview
5Why 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
6Why 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
7What 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
8How ?
- 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.
9How?
- 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.
10Â
Activity Diagram using IDEF0 Top Level Diagram
11Detailed Top Level Diagram
12Third Level Diagrams Login Module
13Third Level Diagrams -Plan Meeting Module
14Third Level Diagrams Resolve Conflict Module
15Third Level Diagrams Manage Interactions Module
16Domain Model
17(No Transcript)
18(No Transcript)
19Sequence Diagram resolve conflict (extend date
range)
20Design Class Diagram resolve conflict (extend
date range)
21Sequence Diagram resolve conflict (Add
preference range)
22Design Class Diagram resolve conflict (Add
preference range)
23Sequence Diagram resolve conflict (Remove
exclusion range)
24Design Class Diagram resolve conflict (Remove
exclusion range)
25Sequence Diagram resolve conflict (Withdraw
participant)
26Prototype
27Meeting Detail
28Meeting History
29Participant response