Ask a question to Desklib · AI bot
Meeting Engagement and Tracking System SRS Document and Use Case
Added on -2019-09-22
This SRS document provides an overview of the requirements for an online meeting management system called MEAT. It includes information on the product perspective, user interfaces, hardware and software interfaces, and functional and performance requirements. The use case diagram and descriptions are also included.
| 18 pages
| 2820 words
| 497 views
Trusted by 2+ million users,
1000+ happy students everyday
MEETING ENGAGEMENTAND TRACKING SYSTEMSRS DOCUMENT AND USECASESTUDENT
Contents1. INTRODUCTION............................................................................................................................21.1PURPOSE............................................................................................................................21.2SCOPE.................................................................................................................................21.3BENEFITS............................................................................................................................31.4ABBREVIATIONS...............................................................................................................31.5REFERENCES....................................................................................................................31.6OVERVIEW..........................................................................................................................32.OVERALL DESCRIPTION.........................................................................................................32.1PRODUCT PERSPECTIVE...............................................................................................42.1.1User interfaces.............................................................................................................42.1.2Hardware interfaces....................................................................................................42.1.3Software interfaces.....................................................................................................42.1.4Communications interfaces........................................................................................52.1.5Memory Constraints....................................................................................................52.2PRODUCT FUNCTIONS...................................................................................................52.3USER CHARACTERISTICS..............................................................................................52.4CONSTRAINTS...................................................................................................................62.5ASSUMPTIONS..................................................................................................................63.REQUIREMENTS.......................................................................................................................63.1EXTERNAL INTERFACE REQUIREMENTS..................................................................63.1.1User Interfaces............................................................................................................63.1.2Hardware interfaces....................................................................................................73.1.3Software interfaces.....................................................................................................83.1.4Communications interfaces........................................................................................83.2FUNCTIONAL REQUIREMENTS.....................................................................................83.3PERFORMANCE REQUIREMENTS................................................................................83.4DESIGN CONSTRAINTS..................................................................................................93.5OTHER REQUIREMENTS................................................................................................93.5.1Security.........................................................................................................................93.5.2Maintainability..............................................................................................................93.5.3Portability......................................................................................................................9USECASE DIAGRAM......................................................................................................................10USECASE DESCRIPTION..............................................................................................................111 | Page
2 | Page
1. INTRODUCTIONThe SRS is about an online meeting management system. The application will track and engage employees as well as manage other schedules of the meetings and will be called ‘MEAT’ app. It will an online portal where employees can book rooms for meetings, search rooms for meetings, send emails to associated employees about meetings and much more. In the following sub-sections of the SRS document there will be an overview about the requirements provided by the user for the development of the system before we create a hard coded design and implement it on user machines. This document will act as an overview for the developers to provide insights about what to build. 1.1PURPOSEThe purpose of the project is to provide an online facility to the employees to manage and track the meetings. The system will avoid last minute changes or miscommunications. Everybody can be alerted about the schedules, pre-plans can be made and there will be no clashes. Empty meeting rooms can be booked and reminders can be sent before the meeting starts. 1.2SCOPESince the organization is large enough so at times there can be clashes related to rooms or timing of work. Thus this meeting manager will handle everything, providing convenience in return. The web application that will be used to process meeting requests online is “MEAT”. The app will reduce the overall scheduling time as well as make it an easier task for employees to handle. The employees can login and look for calendars and schedules. They can even edit info add members or remove them from the meeting schedule. There will be universal calendars to manage everything and process every request. 3 | Page
Found this document preview useful?
You are reading a preview
Upload your documents to download
or
Become a Desklib member to get accesss
Paid Plans
Free Plan
Single Unlock
Monthly Plan
Yearly Plan