Meeting Scheduler Requirements Engineering

6459 Words26 Pages
Meeting Scheduler Software Requirements Specification 1 Introduction This document specifies all the requirements for the Meeting Scheduler software system that aimed to help people scheduler their meetings. 1. Purpose 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. 2. Scope This document is intended for providing a well-defined functional and non-functional requirement specification. The scope of this document…show more content…
The Meeting Scheduler shall be working with each web browser easily. 2.2 Product Functions The Meeting Scheduler System is responsible for managing meetings between various potential meeting attendees. It will determine the meeting time depending on the potential attendee’s personal agenda. The potential attendees will always be kept up to date when they are invited to a meeting, the meeting information is changed and the meeting is cancelled. The Meeting Scheduler will be responsible for allocating location, room and equipment requirements. The Meeting Scheduler will allow meeting initiator and potential attendees to re-plan of a meeting. 2.3 User Characteristics The target groups of the Meeting Scheduler System are: • Non-expert users; thus, the system will provide a very easy-to-use user interface. • System users (in hierarchical order); system engineers, administrator, initiator and non-expert users • Frequency of use (in hierarchical order); administrator, initiator, non-expert users and system engineers 2.4 General Constraints The system will be designed by using PHP and HTML languages. The system will be merged with Joomla content management application. The system will support any kind of platform that has a web browser. The system will support concurrent user requests. The system will not allow multiple authentications. Apache Tomcat will be used as database. 2.5 Assumptions and
Open Document