1. Project Presentation-Phase 2 Requirements Elicitation Specification Validation T ERA S OFT D ISTRIBUTED M EETING S CHEDULER Team Blitzkrieg: ADITYA DHAMANKAR, AJAY NARASIMMAMOORTHY, BRYAN PARKER JASSEM SHAKIL, JEEVAN KUMAR, Meghana Satpute, MUHAMMAD ABDULLAH, PREETI GANESHMOHAN, SEAN WILSON, VINAY SAMPATHKUMAR Instructor: Dr. Lawrence Chung 1

2. A GENDA  Process Specification  New Enterprise Requirements and Issue Analysis  Product Specification  Prototype 2

3. P ROBLEM S TATEMENT The problem ofscheduling meetings in manual method Affectsmeeting coordinator and attendees the impact of which is Conflicts, delay, improper maintenance and difficulty in managing meetings and resolving date and time conflicts a successful solution would beMonitor Meetings → Accurately control and manage the entire meeting scheduling process Plan Meeting → Select most convenient meeting date and time, and location Re-plan Meeting → Support variations and changes in the Schedule Resolve Conflicts → Perform negotiations Manage Interactions → Maintain necessary but minimal communication Manage Concurrent Meetings → Allow users to submit and manage multiple meeting requests 3

4. P ROBLEM A NALYSIS - F ISHBONE 4

5. U SER R OLES M EETING I NITIATOR  Adds a Meeting to the System  Provides Meeting Details including time frame and freeze time  Add Active, Important and Regular Participants to the Meeting  Invite Participants to the meeting  Cancel meeting  Reschedule a Meeting  Monitor the overall status of the meeting and resolve conflicts as needed 5

6. U SER R OLES - P ARTICIPANTS (R EGULAR /A CTIVE /I MPORTANT )  Specify Preference Set  Specify Exclusion Set  Cancel Participation  If the Participant is Active, he would be specifying the Equipment Requirements if he wants to, in addition to points 1,2, and 3  If the Participant is Important, he would be specifying the preferred meeting location, in addition to points 1,2, and 3 6

7. Process Specification 7

8. P ROCESS O VERVIEW I NTERIM 8

9. P ROCESS O VERVIEW F INAL 9

10. P ROCESS M ODEL 10

11. P ROCESS S ADT L EVEL 0 11

12. P ROCESS S ADT L EVEL 1 12

13. P ROCESS S ADT L EVEL 2 13

14. A CTIVITY D IAGRAM I NTERIM 14

15. A CTIVITY D IAGRAM F INAL 15

16. New Enterprise Requirements 16

17. D OMAIN R EQUIREMENTS  The meeting initiator can cancel or reschedule a meeting.  All participants can fully, partially or not attend a meeting.  The meeting can be scheduled to be one-time or recurring.  Meeting locations should be convenient 17

18. I SSUES IN D OMAIN R EQUIREMENTS "All participants can fully, partially or not attend a meeting." Problem:(Type of Issue: ambiguity) The statement sounds suggestive and partial attendance is not clearly defined. Option 1:Define partial attendance as the 50% or more participants attend the meeting. Option 2:Define partial attendance as same participant can attend different meetings partially. Option 3:Define partial attendance as same participant can attend different meetings partially but in non-overlapping manner. Solution:Option 3 18

19. I SSUES IN D OMAIN R EQUIREMENTS " The meeting can be scheduled to be one-time or recurring..” Problem:(Type of Issue: ambiguity) Here the word “recurrence” does not explicitly say when the meeting can be recurrent. Also the statement sounds suggestive and a more defined approach needs to be taken. Option 1:The meeting is recurrent every day at the time specified. Option 2:The meeting is recurrent every week at the day and time specified. Option 3:The meeting is recurrent every month at the date and time specified. Option 4:The meeting is recurrent every year at the date and time specified. Option 5:The meeting coordinator decides when the meeting should reoccur.. Solution:Option 5 19

20. F UNCTIONAL R EQUIREMENTS  FR18 Some meetings are scheduled and organized at the same time where partial attendance can be allowed  FR19 Each of the different type of user should have different access privileges  FR20 A secure login username and password is required for each of the user to access the system  FR21 A participant should only be able to see the meeting information that he/she initiated or is part of  FR22 A participant should only be able to search the meeting information that he/she initiated or is part of 20

21. I SSUES IN F UNCTIONAL R EQUIREMENTS ISSUE STATEMENT: [FR18] “Some meetings are scheduled and organized at the same time where partial attendance can be allowed.” Problem:(Type of Issue: ambiguity) The statement sounds vague and partial attendance is not clearly defined. Also who schedules and organizes these meetings isnt defined clearly Option 1:Define partial attendance as continue with holding the meeting even if 50% or more participants attend the meeting. Option 2:Define partial attendance as same participant can choose to attend or not attend different meetings partially as per his/her will. Option 3:Define partial attendance as same participant can attend different meetings partially but in non-overlapping manner. Solution:Option 3 21

22. ISSUE STATEMENT: [FR19] “Each of the different type of user should have different access privileges.” Problem:(Type of Issue: ambiguity) The statement sounds vague and here “different” in terms of user types and access privileges arent listed which would make the requirement more clear. Also the statement sounds suggestive and a more defined approach needs to be taken. Option 1:Define access privilege as any meeting participant shall be able to invite and include another participant to the meeting. Option 2:Define access privilege as any meeting participant shall not be able to include another participant to the meeting. He/She can invite another person to the meeting only through the meeting coordinator. Solution:Option 2. 22 I SSUES IN F UNCTIONAL R EQUIREMENTS

23. N ON F UNCTIONAL R EQUIREMENTS  NFR18 Information about meetings should be secure. 23

24. I SSUES IN N ON F UNCTIONAL R EQUIREMENTS ISSUE STATEMENT: [NFR18] “Information about meetings should be secure.” Problem:(Type of Issue: incompleteness) The requirement is incomplete as it does not specify what exactly expected by “secure” system and what information needs to be secure. i.e. the information about the participants or the meeting details. Option 1:Define security as the access privileges for each type of user. Users shall be able to log into the system via a login screen with a user name and password. A participant should only be able to see and search the meeting information that he/she initiated or is part of. Option 2:All participants will have same privileges. Option 3:Meeting details will be kept secret. Solution:Option 1 24

25. Requirement Engineering Process 25

26. Product Specification 26

27. U SE C ASE D IAGRAM 27

28. C LASS D IAGRAM 28

29. SEQUENCE DIAGRAM INITIATE MEETING REQUEST 29

30. SEQUENCE DIAGRAM SCHEDULE MEETING 30

31. P RODUCT A RCHITECTURE 31

32. P RODUCT C APABILITY Customer BenefitSupporting Features Access to the system with easeAccess via the Internet through a user friendly GUI Initiate meetings convenientlyAllow easy forms with menus, calendars Respond to meeting invitation with simplicityEasy options while filling up forms Interoperability with other applicationSynchronization with other applications Virtual meetings Able to remotely connect to the meeting via a bridge line and UI. Less time involvedDynamic conflict resolution: date, time and location decided instantly 32

33. PRODUCT SADT LEVEL 0 33

34. P RODUCT SADT L EVEL 1 34

35. TRACEABILITY ( REQUIREMENTS TO PROTOTYPE)

36. USE OF SEMIFORMAL NOTATIONS FOR ADDING NEW REQUIREMENTS

37. Flexibility

38. SIG FOR NFR S ECURITY 38

39. SIG FOR NFR S ECURITY 39

40. SIG FOR NFR USABILITY 40

41. K AOS M ODELING S ECURITY 41

42. KAOS M ODELING U SABILITY 42

43. PRODUCT DEMO  Blitzkrieg Distributed Meeting Scheduler 43

44. WHY OUR PRODUCT BETTER  1. Separate interface for each type of participants to handle meeting requests  2. Efficient because we are maintaining deadlines for participant's input  3. Clear traceability from user requirements to FR, NFR and FR, NFR to Prototype features.  4. User Profile / Availability page that allows user to edit his/her profile and also the weekly preference/exclusion sets

45. WHY OUR PRODUCT BETTER  5. A visible calendar on each page that shows the upcoming meetings.  6. Search bar to quickly find meeting requests.  7. Similar features of MS Outlook ensures user interoperability.  8. Little to NO cost!

46. T HANK Y OU ! Any Questions? 46