1 / 33

Meeting Scheduler

Interim Presentation -1 on SDMS. Meeting Scheduler. Carl Fernandes Mahbubur Rahman Haque Muaz Jamshed Ramakrishnan Jayavelu Sujith John Zachariah. Instructor: Dr. Lawrence Chung. Agenda. Overview – Why ,What ,How Project Process Enterprise Requirements

gabriel-bailey
Télécharger la présentation

Meeting Scheduler

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. Interim Presentation -1 on SDMS Meeting Scheduler Carl Fernandes Mahbubur Rahman Haque Muaz Jamshed Ramakrishnan Jayavelu Sujith John Zachariah Instructor: Dr. Lawrence Chung

  2. Agenda • Overview – Why ,What ,How • Project Process • Enterprise Requirements • System Functional Requirements • System Non-Functional Requirements • Prototype • Requirement Sources

  3. Overview • Web Based System intended to help people schedule meetings • Efficient communication and monitoring • Effective negotiation & Conflict resolution • Supports Virtual Meetings and Teleconferencing

  4. Why? Problems - • Time is ineffectively managed. • Meeting Scheduling a tedious job • Meeting initiation not collaborative. • Communication between participants not effectively managed.

  5. Why ? Solutions - • Automatic Scheduling – Reduces time • Collaborative Scheduling - Reduces Interactions required for scheduling • Synchronous Communication – Effective Communication

  6. What ? System - Functional Requirements • Monitor Meetings • Plan Meeting - Scheduling - location ,date • Replan Meeting - Rescheduling – new date , location - Cancel • Conflict Resolution - Client Resolution Policy

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

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

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

  10. How ? • Usability – Use by Non-Experts • Customizability – Professional and Personal Meeting • Extensibility – Delegation, explicit priorities

  11. Project Process • Incremental Approach • Identify roles and stakeholders System World - Mahbubur User World – Carl , Ramakrishna Subject World - Sujith Developer World – Muaz • Manage activities

  12. Enterprise Requirements –Why? • How do PW, SW and HW interact within the domain? – Domain level questions • Two types: - Functional - Non Functional

  13. Dependency Diagram: Initial Understanding of Enterprise Req.

  14. Issues: Enterprise Requirements • Ambiguous: • issue -1: Initiator may ask active participants to provide any special equipment requirements on the meeting location. • soln: Initiator asks the active participants to provide meeting equipments or he provides them himself. • issue -2: Initiator could also ask important participants to provide any special location they prefer. • soln: Initiator asks important participants to provide their preferred meeting places or he decides the place himself.

  15. Issues: Enterprise Requirements • Incomplete: • issue -3: Participants are not defined properly (e.g. "potential participants" ) • soln: Yet to be resolved. • issue -4: How do we make sure if the meeting place has sufficient equipments? • soln: An update should be made, within the SDMS system, if all the meeting equipments are available. • issue -5: What happens when there are different meeting places proposed by important participants? • soln: The initiator resolves this by choosing a meeting place, especially when same number of important participants choose different meeting locations.

  16. Issues: Enterprise Requirements • Incomplete: • Issue -6: virtual meeting place - Incomplete definition (uses only examples) • soln: For the time being, we consider virtual meeting place as only teleconferencing using via laptops / desktops. (But we have plans to come up with a better solution in future.) • Issue -7: virtual meeting place - should we consider it a special type of meeting place ? or a different type of entity ? • soln: We consider virtual meeting place as a different type of place than a physical meeting place and kept it separate from the physical meeting places.

  17. Issues: Enterprise Requirements • issue -8: Only dates are specified in the preferred sets, but not time. What if a person is available at daytime but not some time, say, 10:00 pm. Should he put that particular date in his preferred set or exclusion set? • soln: We assume, for the time being, that the individual is available for the whole day. • Inconsistent / Redundant: • issue -9: Virtual meeting place - absolutely necessary • soln: The word "absolutely necessary" is highly inconsistent because there is no absolute thing with humans. So, we got rid of it.

  18. Dependency Diagram: Improved Understanding of Enterprise Req.

  19. System Functional Dependency (Preliminary)

  20. Issues(System Functional) • Incomplete or Omission: functional system requirements states: to support conflict resolution according to the policies stated by the client but there are no such policies defined any where in the system functional requirements. • soln: Contacted the Client to resolve the issue • Ambiguity: Monitor meetings in system functional requirements is not well defined, very vague. No where does it mention what aspect needs to be monitor. • soln:Due to its vague nature and the fact that it could not be quantified we moved it over to non-functional system requirements • Redundancy:Making participants aware and informing participants in the system functional requirements seem redundant. • soln:Merged informing and awareness • Misclassification:In the midst of the managing interactions for the system functional requirements the term reliability was used which is purely suppose to be a non functional requirement • soln:Moved reliability to non functional system requirements

  21. Parallel meeting request System Functional Specifications (Final) Meeting Meeting Meeting request 1 request 3 request 2 Resolution policy Conflict Informing and resolution awareness Getting Managing Planning under replies interactions constraints Changing user Meeting date Communicating constraints and location requests Replanning New date and Cancelled Location

  22. Monitor Who and What are the processes used by non-experts?. Customizability Parallel meeting meeting? request Resolution policy? Preliminary System Non-Functional requirements Meeting Meeting Meeting request 2 request 3 request 1 Which part of system needs high performance? User friendliness?? Which process needs privacy and which doesn’t? Minimal interaction Conflict resolution Informing and awareness Planning under Getting constraints replies Communicating Managing Meeting date requests interactions and location Which part of the system needs to be Flexible and to what extent? Convenient and as early as possible?? Changing user constraints Re-planning New date and Cancelled Location Dynamically and with as much flexibility as possible Availability

  23. Issues with Non-Functional requirements Ambiguity Description using abstract terms like flexibility, reliability, System, Non-experts sounds ambiguous which leads to many assumptions. Repetitions Several requirements description come repeatedly irrespective of classifications making unwanted distractions. Inconsistency The requirements are stated randomly rather than clearly stating the user and system needs, so it makes the requirements inconsistent. Incompleteness Lack of clear description and technical specifications leaves the requirements incomplete. A perfect implementation of the requirements needs everything till the end details.

  24. Parallel meeting request Meeting Meeting Meeting request 2 request 3 request 1 Resolution policy Conflict resolution Informing and awareness Planning under Getting constraints replies Communicating Managing Meeting date requests interactions and location Changing user constraints Re-planning New date and Cancelled Location Should be done by non-experts Customizability System Non-Functional requirements Minimal interaction Privacy User friendliness High-level of performance Convenient and as early as possible Flexibility Dynamically and with as much flexibility as possible Availability

  25. SYSTEM PROTOTYPE

  26. Log In

  27. Welcome

  28. Up coming Meetings

  29. Select Meeting Dates

  30. Meeting Date

  31. Requirement Sources • Previous Projects – • SDMS – Jung-Chi Lin , Arundhati • SDMS - Yasaman Haghpanah,Ravindra Rudraraju, Sowjanya Sakruti, Jim Whitaker • Customer interviews • Meeting Maker http://www.meetingmaker.com/products/meetingmaker/white_paper.cfm#anchor1

  32. Questions?

More Related