1 / 46

Web Based Meeting Scheduler System

Web Based Meeting Scheduler System. Presented by. Team “Call of Duty”. CS 6361, University of Texas At Dallas. 29 th April 2010. Team. Anuj Gupta Hariharan Rajagopalan Kawaljit Grover Kerem Kulak Neha Priyadarshini Priya Priya Satwant Singh Sujatha Sridhar.

tbean
Download Presentation

Web Based Meeting Scheduler System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Based Meeting Scheduler System Presented by Team “Call of Duty” CS 6361, University of Texas At Dallas 29th April 2010

  2. Team • Anuj Gupta • HariharanRajagopalan • Kawaljit Grover • Kerem Kulak • NehaPriyadarshini • PriyaPriya • Satwant Singh • Sujatha Sridhar

  3. Discussion Highlights • Purpose • Vision • Process Specification • Product specification • New Requirements • UML Modeling • NFR Specification • Traceability • Demo • Questions

  4. Purpose • To help users schedule meetings more easily and efficiently • Monitor meetings, especially held in a distributed environment • Re-planning of meetings to support changing user constraints • Support conflict resolution

  5. Vision - Problem Statement

  6. Vision -Stakeholder's summary

  7. Vision -User summary

  8. Fishbone Analysis Date not Available Unexpected change in Meeting Schedules/Cancellation by Attendees Attendees Location Attendees Not available at given date time Different Location Different Time Different places different holidays Scheduling meeting takes lot of time effort and cumbersome task Attendee have to attend a different meeting Attendees Not available at given date time No Partial Meeting allowed No virtual meetings Lack of updated Information

  9. Business Use case

  10. Process Specification Hierarchical Overview of the Project Phases

  11. Level 0 Context Diagram for Process UML/other notation requirements Project constraints SRS Process requirements Problem description Prototype Process specification A0 Requirements engineer Software engineer Software developer Domain expert

  12. Level 1 for Process UML/other notation requirements Project constraints Process phase - I Problem description 1 SRS Prototype Process phase - II Changed Requirements 2 Process specification A0 Requirements engineer Software engineer Software developer Domain expert Test engineers

  13. Level 2 for Process UML/other notation requirements Project constraints Process phase – 11 Process phase – 1.2 Problem description SRS A1 Process phase – 2.2 Prototype Process phase – 21 Changed Requirements Process specification A2 A0 Domain expert Software engineer Requirements engineer Software developer Test engineers

  14. Process Specification (Activity diagram of the Project)

  15. Product Specification • System decision for New Requirements • Implementation of the new requirements-shown using demo • Use case modeling for the requirements • Soft Interdependency graph (SIG) diagrams

  16. Level 0 – Context diagram for product User authentication Initiator decision Conflict constraints Login Process meetings Meetings Scheduled Password A0 System User

  17. Requirement Changes 1. Some meetings are organized and scheduled at the same time, as a chunk, where partial attendance can be allowed. Solution 1: Important and active participants shall be allowed to attend only part of the meeting by choosing the attend partial option along with acceptance of a meeting invitation. Solution 2: Do not allow partial attendance at all Final Resolution: Option 1 was chosen as it provides more flexibility for the important and active users to attend more than one meeting in case their presence is expected in more than one meetings. While resolving conflicts, meeting schedule of active/important participants shall not show as conflict for partial attendance meeting. Option2 imposes a more restricted rule hence is not considered as an option. 2. Meeting locations should be convenient, and information about meetings should be secure. Final Resolution: Location convenience is already addressed as important participants are allowed to specify location. Only important and active participants location preferences are considered while resolving location conflicts. Secure means that only authorized users are allowed to use the system. Users shall be able to register in the system, but permission will be provided only after receiving the email confirmation from the admin. Users shall be able to view the meetings that are either initiated by them or to which they are invited, they shall not be able to view other users meeting details.

  18. Requirement Changes • 3. For helping with conflict resolution and negotiation support, video conferencing would be available on the system and each video conferencing session should be recorded and analyzed for the purpose of the meeting. • Solution 1: The system shall provide video conferencing option between 2 geographical locations. • Solution 2: Do not allow video conferencing option • Final Resolution: Option 1 is chosen as it provides the ability to schedule and monitor virtual meetings without having restrictions on the geographical location of the participants. • 4. Some stakeholder has also requested that your meeting system provide such features that can be found, for example, in Microsoft Office Outlook. • Solution 1 : Some of the features provided by outlook • Cancel meeting and notify users by email • Provision to decline meetings • Respond to meeting with preferences • Send meeting Reminders and reminders to respond to meeting requests via email • Solution 2: Requirement is ignored • Final Resolution: Option 1 is selected as it provides more user friendly features offered by other meeting scheduler products like Outlook

  19. UML Modeling- Use Case Diagram

  20. UML Modeling -Class Diagram

  21. UML Modeling – Sequence Diagram I Initiate Meeting

  22. UML Modeling – Sequence Diagram II Respond to Meeting

  23. UML Modeling – Sequence Diagram III Cancel Meeting

  24. KAOS Schedule Chunk Meetings Reduce the overhead in organizing meetings Choose convenient meeting locations Reduce the number of interactions between attendees and the initiator Allow partial attendance Convenient for 100% of the multiple meeting attendees Convenient for 50% of the single meeting attendees Maintain [Partial attendance timing] Allow Virtual meeting Monitor Meeting Avoid [Redundant interactions]

  25. SIG: Usability

  26. SIG: Performance

  27. SIG: Maintainability

  28. SIG: Reliability

  29. Use Case – Requirement Mapping

  30. Traceability –(Domain vs System)

  31. Traceability –Functional Vs Non Functional

  32. Demo Screenshots

  33. Login page

  34. Register page

  35. Home page

  36. Meeting Initiate page

  37. Meeting Status page

  38. Pending Request page

  39. Meeting initiator view: User Responses

  40. Meeting initiator view: User Responses

  41. Meeting Initiator view: Virtual Meeting Wizard

  42. Meeting initiator view: Virtual Meeting Status

  43. Meeting initiator view: Cancel Meeting

  44. References • http://www.cs.cmu.edu/afs/cs/project/able/ftp/intro_softarch/intro_softarch.pdfhttp://www.utdallas.edu/~chung/RE/syllabus.htm • http://en.wikipedia.org/wiki/Traceability • http://www.jiludwig.com/Traceability_Matrix_Structure.html • http://www.utdallas.edu/~chung/RE/Presentations09S/ • http://www.utdallas.edu/~chung/RE/Presentations08F/

  45. Questions ?

  46. Thank You

More Related