This document specifies all the requirements for the Meeting Scheduler software system that aimed to help people scheduler their meetings.
The purpose of this document is to provide a software requirement specification for the Meeting Scheduler software system by listing the system functional and non-functional requirements. This document also presents non-functional requirements system dependency, non-functional software goal analysis, requirements dependency matrix and business continuity plan.
This document is intended for providing a well-defined functional and non-functional requirement specification. The scope of this document is the elaboration of Meeting Scheduler Software System’s functional, non-functional requirements and their dependencies. This specification is not concerned with defining stakeholders, system architecture, providing abstract overview of the system and design issues.
1.3 Definitions, Acronyms, and Abbreviations
SRS - Software Requirements Specifications
Meeting Initiator: The user who initiates the meeting
Exclusion set: a set of dates on which participants cannot attend the meeting
Preference set: a set of dates on which participants would prefer the meeting to take place
Date range: a time interval established by the meeting initiator during which he would like the meeting to occur
Active participant: a participant who will play a major role in the meeting and is responsible for specifying equipment requirements; is identified by the meeting initiator
Important participant: a participant who is necessary to the purpose of the meeting and is given the privilege of requesting a meeting location preference; is identified by the meeting initiator
Potential meeting participant (attendee) - A person who has been invited to a proposed meeting that has not either accepted (“will attend”) or refused (“will not attend”)
Meeting proposal - An invitation to a meeting including the meeting topic, date range, and duration that is sent to a list of potential meeting participants
Duration - The time span of a proposed meeting
Strong date conflict: a conflict when scheduling the meeting date that occurs when no date can be found within the date range and outside all exclusion sets
Weak date conflict: a conflict when dates can be found within the date range and outside all exclusion sets, but no date can be found at the intersection of all preference sets.
Virtual meeting - A meeting simultaneously held at multiple remote locations, e.g. teleconferencing
 IEEE 830-1993: IEEE Recommended Practice for Software Requirements Specifications" IEEE Standards Collection, IEEE, 1997.
The second section will define the main functions of the Meeting Scheduler System as well as define borders to its supporting systems. The third section will define system functional requirements, non-functional requirements and their dependencies.
1. General Description
2.1 Product Perspective
2.1.1 System Interfaces
The Meeting Scheduler System depends on prevalent calendar date and time interface in order to schedule meetings notwithstanding that allocating meeting locations, rooms and equipment requirements. The Meeting Scheduler System will use a database for data storage and backup.
2.1.2 User Interfaces
The Meeting Scheduler System will provide a very simple easy-to-use graphical user interface, which has a prevalent look to provide user familiarity.
2.1.3 Hardware Interfaces
2.1.4 Software Interfaces
The Meeting Scheduler System will only be communicating with an external database (Apache Tomcat) to get the required information.
2.1.5 Communication Interfaces
The Meeting Scheduler System will use e-mail communication to notify users and also to get confirmation messages. The Meeting Scheduler System will...