Meeting Scheduler
-
Upload
gabriel-bailey -
Category
Documents
-
view
61 -
download
1
description
Transcript of Meeting Scheduler
Meeting Scheduler Carl Fernandes
Mahbubur Rahman HaqueMuaz Jamshed
Ramakrishnan JayaveluSujith John Zachariah
Interim Presentation -1 on SDMS
Instructor: Dr. Lawrence Chung
Agenda Overview – Why ,What ,How Project Process Enterprise Requirements System Functional Requirements System Non-Functional Requirements Prototype Requirement Sources
Overview Web Based System intended to help
people schedule meetings Efficient communication and
monitoring Effective negotiation & Conflict
resolution Supports Virtual Meetings and
Teleconferencing
Why? Problems - Time is ineffectively managed. Meeting Scheduling a tedious job Meeting initiation not collaborative. Communication between
participants not effectively managed.
Why ?Solutions - Automatic Scheduling – Reduces
time Collaborative Scheduling - Reduces
Interactions required for scheduling Synchronous Communication –
Effective Communication
What ? System - Functional Requirements Monitor Meetings Plan Meeting - Scheduling - location ,date Replan Meeting - Rescheduling – new date , location - Cancel Conflict Resolution - Client Resolution Policy
What ? Manage Interactions - Communicate Requests - Replies - Informing and Awareness
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
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
How ? Usability – Use by Non-Experts Customizability – Professional and
Personal Meeting Extensibility – Delegation, explicit
priorities
Project Process Incremental Approach Identify roles and stakeholders System World - Mahbubur User World – Carl , Ramakrishna Subject World - Sujith Developer World – Muaz Manage activities
Enterprise Requirements –Why?
How do PW, SW and HW interact within the domain?
– Domain level questions
Two types: - Functional - Non Functional
Dependency Diagram: Initial Understanding of Enterprise
Req.
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.
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.
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.
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.
Issues: Enterprise Requirements
Dependency Diagram: Improved Understanding of Enterprise Req.
System Functional Dependency (Preliminary)
Meeting Request
Managing Interactions
Informing
Communicating Requests
Getting Replies
Planning Under Constraints
Conflict Resolution
Changing User Constraints
Re-planning
Meeting Date & Location
Monitor Meeting?
Resolution Policy?
Awareness
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
Issues(System Functional)
System Functional Specifications (Final)
Parallel meeting request
Meeting request 2
Meeting request 1
Meeting request 3
Managing interactions
Changing user constraints
Replanning
Informing and awareness
Getting replies
Communicating requests
Cancelled
Resolution policy
Conflict resolution
Planning under constraints
Meeting date and location
New date and Location
Parallel meeting request
Meeting request 1
Meeting request 2
Meeting request 3
Managing interactions
Re-planning
Informing and awareness
Getting replies
Communicating requests
Cancelled
Conflict resolution
Planning under constraints
Meeting date and location
New date and Location
Changing user constraints
Monitor meeting?
Resolution policy?
Preliminary System Non-Functional requirements
Minimal interaction
Who and What are the
processes used by non-
experts?.
Customizability
User friendliness?
?
Which part of system needs
high performance?
Which part of the
system needs to be Flexible and
to what extent?
Dynamically and with as much flexibility as
possible
Availability
Convenient and as early as possible??
Which process
needs privacy and which doesn’t?
Issues with Non-Functional requirements
Ambiguity Description using abstract terms like flexibility, reliability, System, Non-experts sounds ambiguous which leads to many assumptions.
RepetitionsSeveral requirements description come repeatedly irrespective of classifications making unwanted distractions.
InconsistencyThe requirements are stated randomly rather than clearly stating the user and system needs, so it makes the requirements inconsistent.
IncompletenessLack of clear description and technical specifications leaves the requirements incomplete. A perfect implementation of the requirements needs everything till the end details.
System Non-Functional requirements
Minimal interaction
Should be done by
non-experts
Customizability
User friendlinessHigh-level of
performance
Flexibility
Dynamically and with as much flexibility as
possible
Availability
Convenient and as early as
possible
Privacy
Monitor meeting?
Parallel meeting request
Meeting request 1
Meeting request 2
Meeting request 3
Managing interactions
Re-planning
Informing and awareness
Getting replies
Communicating requests
Cancelled
Resolution policy
Conflict resolution
Planning under constraints
Meeting date and location
New date and Location
Changing user constraints
SYSTEM PROTOTYPE
Log In
Welcome
Up coming Meetings
Select Meeting Dates
Meeting Date
Requirement Sources Previous Projects – SDMS – Jung-Chi Lin , Arundhati SDMS - Yasaman Haghpanah,Ravindra
Rudraraju, Sowjanya Sakruti, Jim Whitaker
Customer interviews Meeting Makerhttp://www.meetingmaker.com/products/meetingmaker/white_paper.cfm#anchor1
Questions?