Synergy Meeting Scheduler System

Abhinav Reddy TummalapallyLavanya DevaraSwetha Vangala

Satyanarayana Karthik Upadrasta

• Subject World – Abhinav Reddy

• System World – Karthik & Swetha

• User World – Lavanya

• Developer World – Team Work

Stakeholders

• End users• Participants in meetings• Meeting schedulers/initiators• Project management teams• Requirement engineers• Test Engineers• Developers Network support group• Potential customers who will use the system

Preference Sets

Exclusion Sets Date Range Special

Equipment

Date Conflict

Proposed Meeting

Date

Location

Meeting Room

Potential Participants

Important ParticipantsMeeting Initiator

Active Participants

SDMS Semi-Formal Specification --- Unresolved

Participants

Meeting Initiator

Requirements

Potential Participant

Important Participants

Active Participants

All Meeting Attendees

Whose Presence is crucial for meeting

Who are involved in the presentation

Date ConflictDepends on preferred sets, exclusion sets

and date range

Different Participants - Resolved

Preference Sets

Exclusion Sets Date Range Special

Equipment

Date Conflict

Proposed Meeting

Date

Location

Meeting Room

Potential Participants

Important ParticipantsMeeting Initiator

Active Participants

SDMS Semi-Informal Specification --- Resolved

Enterprise Requirements

• Issue: A meeting date shall be defined perhaps by a pair (calender date, time period)

• REQ: A meeting date shall be defined by a pair (calender date, time period)

• Issue: The initiator could also ask, in a friendly manner, active participants to provide any special equipment requirements on the meeting location.

• REQ: The initiator shall determine a) special equipment by herself b) special equipment by asking the active participants

• Issue: The initiator may ask the important participants to state preferences about the meeting location.

• REQ: The initiator shall determine Location a) By herself

b) By asking important participants to state preferences about the meeting location

Enterprise Requirements Contd..• Issue: The proposed meeting date should belong to the stated date range and to

none of the exclusion sets; furthermore it should ideally belong to as many preference sets as possible.

• REQ: The proposed meeting date shall belong to a) As many preference sets as possible b) No preference sets (Corresponds to a weak conflict)

• Issue: Each conflict resolution should be done as quickly as possible and with no more interactions than is really needed.

• REQ: Each conflict resolution should be done as quickly as possible and with least number of interactions.

• Issue: It is absolutely necessary, however, to allow each meeting to take place in a virtual place.

• REQ: It is necessary, however, to allow each meeting to take place in a virtual place.

SDMS

Interaction Management

Plan Meetings

Re-plan Meetings

Conflict Resolution

Monitor Meetings

Parallel Meeting

Requests

SDMS Functional Requirements

Conflict Resolution

Client

Plan Meetings Participants

Monitor Meetings

Re-Plan Meetings

Changing User

constraints

Bound on Re-Planning

SDMS Functional Requirements – Unresolved

Manage Interactions

Replies from Participants

Negotiation & Conflict

Resolution

Communicate Requests

Schedule information to participants

Awareness among

participants

Make them confident about the reliability of the communications

SDMS Functional Requirements – Unresolved Contd..

Conflict Resolution

Meeting Initiator

Plan Meetings Potential Participants

Monitor Meetings

Re-Plan Meetings

User’schanging

constraints

Bound on Re-Planning

Meeting Initiator

Any change in meeting schedule

or location

SDMS Functional Requirements – Resolved

Manage Interactions

Replies from Participants

Negotiation & Conflict

Resolution

Communicate Requests

Schedule information to participants

Awareness among

participants

Make them confident about the reliability of the communications

INFEASIBLE

SDMS Functional Requirements – Resolved Contd..

Monitor meeting

Re-Plan meetings

Manage Interactions

Accuracy Nomadicity

Physical Constraints

Dynamic Flexibility

Minimal

SDMS Non-functional Requirements

Plan Meetings

Usability

Performance

Amount of Overhead

Privacy Rules

Customizability and Extensibility

Independent Authorized

Meeting Request

Convenient Date and Location

Manage Decentralized

Requests

SDMS Non-functional Requirements Contd..

Non- Functional Requirements - Resolved We have connected the given non-functional requirements to the

corresponding functional requirements.

• AccuracyAny change in meetings shall be informed to all the participants without any delay.

• Physical ConstraintsA person shall not be at two different places at the same time.A meeting room shall not be accommodated to more than one

meeting at a time.

• DynamicChange in a location or meeting date shall be immediately informed to all the participants.

Non-Functional Requirements - Resolved - Contd..

• FlexibleIt shall be easier to re-plan meetings and manage interactions

• Performance The elapsed time between the submission of a meeting request

and the computation time to schedule a date and to find a location for the meeting should be minimal.

• Usability The system shall be usable by non-experts, in which case the user can learn to operate with less effort.

Non-Functional Requirements - Resolved - Contd..

• ExtensibilityThe system shall be able to handle new changes including

upgradations or changes to the existing system. It shall be easily modified to accommodate the enhancements

• Customizable The system shall be customizable to two modes (1) Private (2)

Professional meetings –Characterized by different restrictions on the time period that may be allocated (e.g. meeting during office hours, private activities during leisure time).

Mock Up Screen shots

Suggestions?