Synergy Distributed Meeting Scheduling System

1
Synergy Distributed Meeting Scheduling System

• Francisco Puente
• Arundhati Solapurkar
• Jung-Chi Lin

2
Agenda

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

3
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.

4
SDMS Overview
5
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

6
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

7
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

8
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.

9
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.

10
 
Activity Diagram using IDEF0 Top Level Diagram







11
Detailed Top Level Diagram
12
Third Level Diagrams Login Module
13
Third Level Diagrams -Plan Meeting Module
14
Third Level Diagrams Resolve Conflict Module
15
Third Level Diagrams Manage Interactions Module
16
Domain Model
17
(No Transcript)
18
(No Transcript)
19
Sequence Diagram resolve conflict (extend date
range)
20
Design Class Diagram resolve conflict (extend
date range)
21
Sequence Diagram resolve conflict (Add
preference range)
22
Design Class Diagram resolve conflict (Add
preference range)
23
Sequence Diagram resolve conflict (Remove
exclusion range)
24
Design Class Diagram resolve conflict (Remove
exclusion range)
25
Sequence Diagram resolve conflict (Withdraw
participant)
26
Prototype
27
Meeting Detail
28
Meeting History
29
Participant response