Presented by Michael Hale Nelson Lopez Malini Srinivasan Sai Prasanth Sridhar

1. OmniSoft Distributed Meeting Scheduler Phase 2(Final) – The Steelers Spring - 2010 Presented by Michael Hale Nelson Lopez Malini Srinivasan Sai Prasanth Sridhar Wanjun Huang Limin Tang Rutvij Desai

2. Quick Start • Simple web based system • Easy to handle • Interactive • No downloads required • Precise system , eliminates hassle

3. Agenda • Targets to achieve • Stake Holders • New Updated Requirements and Issues • Process Specification • Product Specification • SIG • Vision • Fishbone Analysis • Updated Traceability • Changeability

4. Targets to achieve • Initiate a new meeting. • Choose location and equipments for meeting • summarizes their responses • updates initiator on the results • sends confirmations • sends optional reminders prior to meeting • cancel/reschedule meetings • minimizes rounds of negotiations • categorize participants if necessary • conduct virtual meetings • schedule meetings in parallel

5. Stake Holders • Meeting Initiator • Participants • Requirement Engineer • Project Manager • Domain Expert

6. Requirements Process

7. Role Actor Diagram (RAD)

8. Requirement Types • Domain Assumption • Functional Requirement • Non-Functional Requirement

9. Issue Types • Ambiguous • Incomplete • Inconsistent • Unsound

10. New Updated Requirement & Issues

11. New DA Issues and Solutions • Issue – • Requirement -Some meetings are organized and scheduled at the same time, where partial attendance can be allowed. • Description – The requirement is inconsistent with the former description and it is ambiguous. One attendance cannot attend multi-meetings at the same time. • Possible Solutions -

12. Option 1 - ignore this specification. • Option 2 - change the former description. • Option 3 - some meetings can be organized and scheduled at the same time at different places. However, same person can only attend one meeting at one time. • Optimal Solution - Option 3 + Option 4 • Rationale - some meetings can be organized and scheduled at the same time at the same building. So that same person can attend multiple meetings which are scheduled at the same time and same building, i.e. the person can attend each meeting partially as long as these meetings are scheduled in the same building.

13. New FR Issues & Solutions • Requirement - For helping with conflict resolution and negotiation support, video conferencing (e.g., through Skype) should be available on the system and each video conferencing session should be recorded and analyzed for the purpose of monitoring. [IFR – 23]. • Description – The requirement is ambiguous. The terms conflict and analyze can have different meanings. • Possible Solutions -

14. Option 1 – The definition of conflict shall be the same as the former requirement, so that the definition of the term can be consistent. When there are conflicts between participants, for example, meeting time or meeting location, video conferencing can be one solution. • Option 2 – We can have many different kind of analyze methods; however this is out of the range of the meeting scheduler system. The system shall only keep the record of the video conference. • Optimal Solution - Option 1 + Option 2 • Rationale – Video conferencing is a good solution when conflict happens. It is easy for the system to record video clips of the conference.

15. New NFR Issues & Solutions • Requirement - Meeting locations should be convenient, and information about meetings should be secure. [INFR-13] • Description – convenient is already defined in the phase-1 requirement. • Possible Solutions -

16. Option 1 - each user is assigned one unique user id and password. The password must be at least 8 characters long and contain at least one uppercase letter, one lowercase letter and one number. • Option 2 - each user is assigned one unique user id and password. The password must be at least 8 characters long and contain at least one uppercase letter, one lowercase letter and one number. • Optimal Solution -Option 1 + Option 2 • Rationale - the system is still simple to run, and also guarantee some kind of the security.

17. Process Specification

18. Process Model

19. SADT MODEL Level 0

20. Level 1/A0

21. A 01

22. A 02

23. A 06

24. IEDF Models Level 0

25. Level 1

26. Level 2

27. Level 3

28. Product Specification

29. System Use Case Diagram

30. Essential Use Case Diagram

31. Fully Dressed Format • Few fully dressed format for your view

33. Sequence Diagram Re-plan/Reschedule Meeting • Few sequence diagrams for your view

34. Removing Users

35. SIG • Product NFR – • Security • Performance • Process NFR - • Usability • Reliability

36. SIG - Security

37. SIG - Usability

38. Vision

39. Problem Statement & Solution

40. Fishbone Analysis Miscommunication between attendees Changing minds of people Limited resources, Less functionalities OmniSoft DMS Manually Schedule Meetings More Conflicts Time Consumption

41. Updated Traceability

42. Traceability Types • Forward Traceability • Backward Traceability

43. Example – Backward Traceability

44. Changeability • Changes in requirement specification are certain. • % of change – 15 Variance - +/- 5 • Reason – • Prototype – The amount of change in the prototype model • The change from Old requirements to New modified requirements • The screenshots & requirement traceability factors.

45. Reference • http://www.utdallas.edu/~chung/RE/Presentations09F/ • http://www.meetingwizard.com/mwiz/home/default.cfm • www.utdallas.edu/~yxm076000/RE/SRS_SDMS.pdf

46. Thank you! Questions ?