REQUIREMENTS ENGINEERING

Siddharth PhadkarPratyush Chandra.

MDeepak V Shenoy

Rahul Kotian

SynergySoft Distributed Meeting Scheduler System

Project Overview The system aims to coordinate

referred meeting dates and venues obtained from all the participating individuals and come up with the best meeting schedule possible.

Requirement Sources Existing ‘Meeting Scheduler’

softwares Internet Interviews Personal Experiences

Objectives Outperform existing systems by

Microsoft, IBM etc. Efficient and Usable Meeting

Scheduler. A huge target audience (user group). Development within given time frame

(November 28, 2006)(2 months).

Team Involved Deepak Shenoy: User World Rahul Kotian: Subject World Siddharth Phadkar: System World Pratyush Chandra: Developer

World

Functional Requirements Plan meetings under constraints

stated by participants. Replan meetings to account for

changing user constraints. Support conflict resolution. Manage interactions among

participants. Manage concurrency

Issues Ambiguous: Issue: A meeting should be accurately monitored, especially when it is

held in a virtual place.• Resolution: Here Monitoring will include the various events taken place till

the meeting is scheduled and conveying the various events to the concerned people.

Issue: Who decides who the potential meeting attendees are?• Resolution: The Meeting Initiator will decide this. Issue: To make them confident about the reliability of the

communications.• Resolution: The System will have to send timely and accurate updates about

the various events in the scheduling of meetings.

Issues Redundancy: Issues: ‘Make participants aware of what is going on’

and ‘Keep participants informed about schedules and changes’.

Issues Incomplete: Issues: “The intended system should considerably

reduce the amount of overhead usually incurred in organizing meetings…..”

• Resolution : The system will be using the email system which the user uses and not have email service of its own.

Issue: No criteria for expanding date range is specified.

Functional Requirements

SDMS

Monitor Meetings Plan

Meetings Replan Meetings

Modify Preference Set/exclusion set

External Constraint

Accommodate Important Meeting

Cancel Meeting

Change Date& Location

Manage ConcurrencySupport

Conflict Resolution

Policies by Client

Manage Interactions

Updates Support Negotiations

Non Functional Requirements Flexibility Minimal interaction among participants Convenient to users Dynamic Performance Usable by non experts Customizable Maintain privacy Within physical constraints

Mapping functional to non functional requirements

Manage Interactions Minimal

Support conflictresolution

Manage

concurrency

Replan meetings

Plan meetings

Monitor meetings

Manage physicalconstraints

Dynamic

Convenient date and locations

Maintain privacy

Accommodate decentralized meetings

Reduce overhead

FlexibleImproved Performance???

Usable???

Customizable???

Non-Functional Requirements

Usable

Customizable

Flexible

ExtensibleImproved Performance

SDMS

System inputsThe inputs to the system can be listed

as: Available participants A roster consisting of available dates

for each participant Meeting date range ( provided by

Initiator ) Preferred Locations ( provided by

Initiator )

Use Case Diagram

Initiate Meeting

Participant

Resolve Conflict

Manage User

Login

Respond to Meeting

Administrator

View Meeting Details

Authorized User

Re-schedule Meeting

Meeting Initiator<<extend>>

Sequence Diagram

8: Accepts

: Administrator : Meeting Initiator

: Participant

Meeting Scheduler System

1: Login

3: Initiates meeting with desired set of dates

4: Renders back with possible sets of dates

2: Render View (Admin logs onto system)

In case of conflicts the system will suggest some possible dates

5: Resolve Conflicts

6: Schedule Meeting with resolved dates

7: Notify it to all participants

9: AcceptsIf everyone accepts the dates and confirms

10: Suggest Location

11: Request For Equipment

Their Preference are set and the final report of meeting time , date and location are viewed by all members

12: View Report

13: View Report

Activity Diagram

Initiate meeting

Request special equipment

Request Location

Resolve conflict

Send to all participants

[ Passed ]

Manage preferences

Approved by all participants

Meeting canacelled

Participant withdraws[ No ]

[ Yes ]

Meeting finalized

Change in date range

Availibility check[ Failed ]

[ yes ]

[ No ]

[ Yes ]

Domain ModelAdministrator

(f rom Actors)

Database

Meeting Initiator

Virtual Meeting

potential participants

Active Particpants Important Particpants

Required Equipment

Time Slot

Date range

Location

Final Particpants

proposal

Meeting

Conflict

Conflict Resolution

Screen Shots --- Login Page

Registration Page

Schedule Meeting

View Schedule

Meeting Attendance

Bibliography Presentaion 1 Summer 2006 Presentaion 2 Summer 2006

Questions? Comments? Suggestions?