Download
1 / 19
200 likes | 308 Vues
This document discusses critical issues regarding the eMeet meeting scheduler's features, specifically in comparison to Microsoft Outlook. Stakeholders have requested clear specifications on meeting functionalities, such as reminders and notifications. It also explores the concept of "chunk" meetings allowing partial attendance without conflicts among overlapping schedules. Security concerns are highlighted, with proposed measures for protecting meeting information through unique user credentials. The goal is to refine these features to enhance user experience and meet stakeholder expectations.
E N D
eMeet Meeting Scheduler & Virtual Meeting Location
Issues with Changes to Preliminary Definition • (e.g., incompleteness, inconsistency, ambiguity, redundancy, unsoundness)
MS Outlook (Adeel) • Context: ”Some stakeholder have also requested that your meeting system provide such features that can be found, for example, in Microsoft Office Outlook.” • Issue: "Such features” is ambiguous. We need to know exactly which features need to implemented. • Options: • Have meeting reminders with snooze option • Have meeting reminder SMS system • Have host get notified whenever users accept or reject meeting invitation • Decision and Rationale: 1 & 2 • {provide rationale}
Partial Attendance (Jay) • Context: “Some meetings are organized and scheduled at the same time, as a chunk, where partial attendance can be allowed.” • Issue: What is a chunk? How do we allow partial attendance? • Options: • Meeting chunks are meetings scheduled for the same time (but different days) where all meetings need not be attended. (Like a series of certification classes where the participant need not attend every class). • A “chunk of meetings” could be a group of meetings that are related and happen to overlap in time. In this case, partial attendance is the ability to attend all of these meetings without the system flagging the conflict that would result from normal meetings happening at the same time. • Decision & Rational: 2 • {provide rationale}
Security (Jason) • Context: “Information about meetings should be secure.” • Issue: How do we define secure? • Options: • Have all participants in a meeting enter a unique user name and password combination before being able to view any information regarding a meeting sent through an email notification or other notification. • Have users enter in a unique username and password when creating/editing meetings through the eMeet site. • Have our central database which stores all meeting information be secure. • Decision & Rationale: 2 & 3 • {provide rationale}
Sequence Diagrams (MK) Plan Meeting Update Meeting
