Synergy Distributed Meeting SchedulerHigh Fliers

Deepthi Durgempudi

Nithya Bondalapati

Mahitha Devalapalle

Puneeth Simha

Ragavika Tarigopula

Siddharth Dhall

Sindhura Vallabhaneni

Team

Purpose Process Fishbone Analysis Business Use Case Diagram i* Diagram Business Class Diagram Constraints Specification Models Issues and Solutions Addressing Requirement Changes Prototypes

Agenda

Develop a software that would help users schedule meetings more easily and intelligently

The software should outperform any such system that is currently available in the highly competitive market

The software should be adaptable to any application, such as scheduling courses, flights, room assignments at hospitals and hotels, and much more

Purpose

Process SADTs

Process SADT –Level 1

Process of SDMS

Preliminary Requirement Document

Existing Models

Refined Prototype

Requirements Engineer

Refined SRS

UserDomain Expert

Software Engineer

UMLDiagrmsSIG

Vision Doc

Process SADT – Level 2

Process SADT - Level 3

A011

Eliciting

A012

Understanding

A013

Analysing

A01

Requirement Engineeer

Domain Expert

End User

Preliminary Requirement Document

Existing Models

Specification

FISHBONE ANALYSIS

problem :Inefficient and time consuming process of scheduling meetings manually

Affects: Company work force The impact is :Loss of productive time

which in-turn affects the company’s productivity.

A successful solution: A flexible and efficient system to schedule meetings in a less time consuming manner.

Problem Statement

Problem Fish Bone Diagram

Unauthorized users may access the meeting information

Difficulty in keeping track of the meeting location and meeting date

Large number of negotiations

Time consuming process of selecting a meeting date that is convenient to all the attendees

People are facing many difficulties while Scheduling meetings manually

Difficulty in monitoring meetings

Difficult to schedule a meeting whenever we want (anytime-24/7)

Difficulty in scheduling meetings if attendees cannot be physically present during the meeting

Hard to reflect changing participants’ constraints

Business Use Case Diagram

LoginSignUp

extends

Initiate Meeting

Reschedule Meeting

Administrator

Manage User Accounts

Resolve Conflicts

extends

Accept Meeting Request

Participant

Select Location, Equipment and dateMeeting Initiator

Cancel Meeting

I* Diagram

I * Diagram

Business Class Diagram

Product SADTs

Product SADT – Level 0

Product SADT – Level 1

Specification Models

System Use Case Diagram

System Sequence Diagram

: MeetingInitiator : MeetingInitiator : Participant : Participant

Meeting System Scheduler

Meeting System Scheduler

1: Login

2: Login Successful

3: Initiate Meeting with desired set of dates,equipment and locations

4: Renders back with possible set of dates, equipment and locations

5: Schedule Meetings with convenenient dates and locations

6: Notify to all participants

7: send across preferred time and location

8: Resolve Conflicts

9: Notify

10: Accept

11: Send Report

System Activity Diagram

System Class Diagram

Constraints

Security

Reliability

Maintainability

Issues and Resolutions

What does the term “monitor meetings” refer to?

Solution 1: Record the entire meeting in video format. Solution 2: Record the entire meeting in audio format. Solution 3: Keep a record of meeting minutes.

Final Resolution: The first two solutions are out of the control of SDMS. Moreover, the meeting initiator can request for recording equipment while initiating the meeting (or later) if required. Therefore, the third solution has been chosen as the optimal one.

Issue 1 – Monitor meetings

How to determine if one meeting is important than the other?

Solution 1: The system shall accept an “importance rating” along with other meeting details from the meeting initiator while scheduling a meeting. When two meetings contend for the same location at the same time, the system shall determine which is more important based on this “importance rating”.

Solution 2: When there is contention for meeting location, the system shall notify the meeting initiators of both the meetings, who can then negotiate external to the system to decide which meeting should be given preference.

Final Resolution: The first solution can be misleading, because the “importance rating” will be based on the perception of the meeting initiator and cannot be considered as a standard. Therefore, the second solution has been chosen as the optimal resolution for this issue.

Issue 2 – Need to accommodate a more important meeting

Addressing Requirement Changes

Some meetings are organized and scheduled at the same time, as a chunk, where partial attendance can be allowed.

How to allow partial attendance? Solution 1: Participants can specify to the meeting

initiator that they will be attending only part of the meeting by adding comments along with acceptance of a meeting invitation.

Solution 2: Do not allow partial attendance at all Final Resolution: Since it is possible that a person

wants to go to both the meetings scheduled at the same time, solution 1 has been chosen as the appropriate option.

Requirement change 1

Meeting locations should be convenient, and information about meetings should be secure.

Location Convenience: Already addressed as the system allows important participants to specify their location preferences.

Information Security: Since the system shall be accessible by only authorized users, it can be ensured that “outsiders” cannot access meeting information. Also, one user cannot access the calendar of another user within the system.

Requirement Change 2

Prototypes

Prototype – Welcome Page

Prototype – Admin Screen

Prototype – User Login

Prototype – User Functions

Prototype – Meeting Details

Prototype – Initiate Meeting

THANK YOU!!!