1. Synergy Distributed Meeting Scheduler(SDMS) TEAM:4 Rutvij Mehta Shruti Mehta Shveta Mupparapu Meghna Swetha Raguraman Rakesh Sanapala Venkata Jaganadh Sandeep Sistla Sabareesan Soundarapandian Instructor: Dr. Lawrence Chung

2. Agenda Introduction Why? -Enterprise Requirements What? -System Functional Requirements How? -System Non-Functional Requirements Prototype Next step

3. Introduction to RE Process Introduction to RE Process for prototyping for prototyping [Kotonya&Sommerville98]

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

5. Team Roles Team memberRoleFunction Sabareesan Soundarapandian Shveta Mupparapu User World: End-User Meeting Participant Project Manager Meeting Initiator Describe functions from the enterprise perspective. Describe constraints from the enterprise perspective. Describe user interface. Make project plan. Shruti Mehta Subject World: Domain Expert Customer Describe functions from the enterprise and system perspective Describe constraints from the enterprise and system perspective Describe the market position of the system Sandeep Sistla Rakesh Sanapala System World: Requirements Engineer Software Engineer Specify requirements and dependency graphs Validate requirements with customers and users, talk about open issues and improve understanding Rutvij Mehta Meghna Swetha Raguraman Developer World: Product Manager Developer Review Product Development Process. Build prototype

6. Why? Problems Interactions Complex multiple interactions leads to conflicts. Time consuming Initiator has to perform many activities: -To invite the participants. -To resolve conflicts. Traveling costs Participants from different locations.

7. Why? Solutions Personalize – Give your Availability Share your available and busy time with others, vastly simplifying the meeting scheduling process. Resource Utilization & Management Reserve conference rooms, Audio/Video equipment or other shared resources for your meeting. Simplified Scheduling Just plan the available dates and the system takes care of the priorities and schedules the meeting along with the necessary reminders.

8. Dependency Diagram: Initial Understanding of Enterprise Requirements Dependency

9. *As many preference sets as possible *Earliest Possible Date Initiator Active participants Meeting participantsDate RangeProposed Date Important participantsDate Conflict Meeting Place Virtual Meeting Place Equipment Flexibility Conflict resolution Preference Set Exclusion Set Weak Date Conflict Strong Date Conflict

10. Meeting Place conflict *Fast Conflict Resolution *Minimal Negotiation Modify Exclusion or Preference Set Conflict resolutionRe-propose Meeting Some Participants Withdraw Extend Date Range Initiator Meeting participants *Maximum Preference by important participants * Room Availability

11. What? System - Functional Requirements Monitor Meetings Plan Meeting - Scheduling - location,date Re-plan Meeting - Rescheduling –date, location - Cancel Conflict Resolution - Client Resolution Policy

12. What? Manage Interactions - Communicate Requests - Replies - Informing and Awareness

13. Dependency Diagram: Initial Understanding of System Functional Req.

14. Plan Parallel Meeting Meeting Request2 Meeting Request3 Manage Interactions Re-plan Meeting Changing User Constraints New Date and Location Inform & Create Awareness Communicate requests Get Replies SDMS Conflict resolution Resolution Policies Client Monitor Meeting Cancel Meeting Modify Exclusion Set Modify Preference Set Modify Preferred location External Constraint changes Meeting Request1

15. How? System Non-Functional Requirements Performance -Quick Meeting Proposal Efficiency - Fast Conflict Resolution, Minimal Negotiations Flexibility – Virtual Meeting Uniqueness – Participants,Locations, Resources Reliability – Trustable Communication Concurrency – Parallel Meetings Accuracy – Virtual Meeting Monitoring

16. How ? Dependability – Manage Varying Participant data Security – Login Dynamic – Replanning Meeting Reduce Overhead – Distributed Meeting Convenience - Meeting Date and Location Privacy - Participant constraints kept secret

17. Dependency Diagram: Initial Understanding of System Non-Functional Requirements

18. Plan Parallel MeetingMeeting Request2 Meeting Request1 Meeting Request3 Manage Interactions Re-plan Meeting Changing User Constraints New Date and Location Inform & Create Awareness Communicate requests Get Replies SDMS Conflict resolution Resolution Policies Client Monitor Meeting Cancel Meeting Modify Exclusion Set Modify Preference Set Modify Preferred location External Constraint changes Customizability *Minimal Interaction *User friendliness *Availability * Convenient and as early as possible Dynamically and with as much flexibility as possible Monitor Accurately Privacy *Usable by Non-experts *Private/Professional Meeting *Physical constraints should not be broken *Flexible *Extensible

19. Issues - Enterprise Requirements Ambiguous 1. A meeting date shall be defined perhaps by a pair (calendar date, time period). Issue: The word perhaps adds to the ambiguity. Solution: Remove the word perhaps A meeting date shall be defined by a pair (Calendar date and time period)

20. Issues - Enterprise Requirements Incomplete 1. Issue: The meaning of the terms potential attendances, active participants, important participants is not specified. Solution: The meeting initiator specifies the role for each of the participants (potential, active and important) for the meeting.

21. Issues - Enterprise Requirements Inconsistent / Redundancy 1. It is absolutely necessary, however, to allow each meeting to take place in a virtual place, e.g., through teleconferencing using laptop computers. Issue: The word absolutely necessary is problematic Solution: Remove the word absolutely It is necessary to allow each meeting to take place in a virtual place, e.g., through teleconferencing using laptop computers.

22. Issues - Software System Functional Requirements Ambiguous 1. To make them confident about the {\it reliability} of the communications. Issue: How to make them confident about the reliability? Solution: The System will have to send timely and accurate updates about the change in schedule of meeting.

23. Issues - Software System Functional Requirements Incomplete 1. In all cases some bound on re-planning should be set up. Issue: The requirement doesnt specify the bounds on re-planning the meeting Solution: Define a limit of number of times a meeting can be re-planned.

24. Issues - Software System Functional Requirements Inconsistent/ Redundancy 1. to make participants aware of what's going on during the planning process; and to keep participants informed about schedules and their changes; Issue: Redundant statements Solution: Maintain only 1 statement Keep participants informed about schedule and any changes in their schedules.

25. Issues - Software System Non- Functional Requirements 1. Ambiguous Issue: The meaning of Monitor Meeting is not clear Solution: Decide who will monitor all the meetings. Clarify what the word Monitor implies in this context. Issue: Re-planning of meeting dynamically and with flexibility is not clear. Solution: Throw more light into how the words dynamically and flexibility imply in the above issue. 2. Incomplete Issue: Nomadicity has no definition. Solution: Get more information from stakeholders

26. Dependency Diagram: Improved Understanding of Enterprise Req.

27. *As many preference sets as possible *Earliest Possible Date Initiator Active participants Meeting participantsDate RangeProposed Date Important participantsDate Conflict Meeting Place Virtual Meeting Place Equipment Flexibility Conflict resolution Preference Set Exclusion Set Weak Date Conflict Strong Date Conflict Non Privileged Meeting participants

28. Meeting Place conflict *Fast Conflict Resolution *Minimal Negotiation *Maximum Preference by important participants * Room Availability Conflict resolutionRe-propose Meeting Some Participants Withdraw Extend Date Range Initiator Non-privileged participants Modify Exclusion or Preference Set Important participants Active participants

29. Dependency Diagram: Improved Understanding of Improved Understanding of System Requirements

30. Plan Parallel Meeting Meeting Request 1 Manage Interactions Re-plan Meeting Changing User Constraints New Date and Location Inform & Create Awareness Communicate requests Get Replies SDMS Conflict resolution Resolution Policies Client Monitor Meeting Cancel Meeting Modify Exclusion Set Modify Preference Set Modify Preferred location Customizability *Minimal Interaction *User friendliness *Availability * Convenient and as early as possible Dynamically and with as much flexibility as possible Monitor Accurately Privacy Performance, Reduce amt of Overhead Accommodate de- centralized requests Meeting Request n External Constraint changes

31. Demo Mock Up