A conference management system is web-based software that supports the organization of conferences. It helps the program chair(s), the conference organizers, the authors and the reviewers in their respective activities.
The system maintains a website to which various members interested in attending conferences register themselves as members by providing details.
People who are willing to submit their papers will login and submit their papers to the system with the topic and its domain. All other members who have interest on that domain are notified about the article submitted. Those members will view the article and post their reviews.
The purpose of this SRS is to serve as the repository for all of the requirements that the system shall or should possess. If the entire process of managing the conference manually it becomes a tedious process. So the online web application helps for organizing conferences in efficient manner.
CMS is a web application that shall support every aspect of the conference organization process. This includes paper submission, reviewer assignments, revised paper submission, registration handling of the conference participants.
System should be applicable to any scientific/technical conference, which requires peer-reviewed papers.
1.3 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS
➢ SRS – Software Requirements Specification
➢ CMS – Conference Management System
➢ DBMS – Database Management System
➢ VB-Visual Basic
➢ PC – Program Committee
➢ IEEE -The Institute of Electrical and Electronics Engineers, Inc.
➢ HTML-HyperText Markup Language
➢ Article- An Article is something presented in abstracts, PDF upload, paper format based on some topic in which the author is going to present in the conference
The rest of the SRS provides the general description of the project keeps and detailed list of the software requirements
2. OVERALL DESCRIPTION
2.1 PRODUCT FUNCTIONS AND FEATURES
✓ The system shall be able to handle multiple sub-conferences.
✓ The system shall support
• Special sessions.
• Paper submission.
• Anonymzing the article
• Review process.
• Article selection/rejection
• Conference program creation.
• Conference registration.
2.2 USER CHARACTERISTICS
Majority of users will be the academic staff .This also includes people with Higher technical/non technical knowledge and interests .The system & user interface should be intuitive. In case intuitive solutions are not possible, detailed explanations should be provided.
Web server should be reliable. Server uptime is critical around author and reviewer deadlines. Web server and DBMS should be capable of receiving a large (around 50) number of requests simultaneously. Once the user had reviewed an article, he cannot review the same article again. Each member can have maximum of three domains as their area of interest.
2.4 ASSUMPTIONS AND DEPENDENCIES
Although basic password authentication and role based security mechanisms will be used to protect the system from unauthorised access; functionality such as email notifications are assumed to be sufficiently protected under the existing security policies applied by the administrating team. Redundant Database is setup as the role of backup Database Server when primary database is failure.
Once the paper submitted is selected it is assumed to be presented by the author in a real conference management program.
3. SPECIFIC REQUIREMENTS
3.1 HARDWARE REQUIREMENTS
3.1.1 SERVER SIDE
The web application will be hosted on...