Software Requirements

Specification
for

Online Conference Publication

Version 2.0 approved

Prepared by Anshuman Pandey

Techno Main Salt Lake

16.11.202

i|Page
Contents
1. Introduction.....................................................................................................................................................2
1.1. Purpose/Objective...................................................................................................................................2
1.2. Document Conventions (Definition, Acronyms, Abbreviations)............................................................3
2. History/Background Study (Sources of Domain Knowledge)........................................................................3
2.1. Technical Literature................................................................................................................................3
2.2. Existing Applications..............................................................................................................................4
2.3. Customer Surveys...................................................................................................................................4
2.4. Expert Advice.........................................................................................................................................9
3. Overall Description.........................................................................................................................................9
3.1. Product Functions...................................................................................................................................9
3.1.1. Hardware Requirement...................................................................................................................9
3.1.2. Software Requirement..................................................................................................................10
3.2. Functional Requirements......................................................................................................................10
3.2.3. Conference Admin........................................................................................................................10
3.2.4. Notifications and Alerts................................................................................................................10
3.2.5. User Interaction.............................................................................................................................11
3.3. Non-Functional Requirements..............................................................................................................11
3.3.1. Correctness Requirement..............................................................................................................11
3.3.2. Portability Requirement................................................................................................................11
3.3.4. Usability Requirement..................................................................................................................11
3.3.5. Reusability Requirement...............................................................................................................11
3.3.6. Maintainability Requirement........................................................................................................12
3.4. User Characteristics..............................................................................................................................12
3.5. Design & Implementation Constraints..................................................................................................12
3.6. Assumptions & Dependencies...............................................................................................................12
4. Interface Requirements.................................................................................................................................12
4.1. Author Interfaces..................................................................................................................................12
4.2. Hardware Interfaces..............................................................................................................................12
4.3. Communication Interfaces....................................................................................................................13
5. Conclusion....................................................................................................................................................13

1. Introduction
1.1. Purpose/Objective

2|Page
 The main purpose of this SRS document is to define the functional and non-functional requirements
for an Online Conference Publication System. It provides a platform for researchers to submit their
papers electronically, streamlining the submission process and making it accessible to a wider
audience. The system also automates the review process, assigning papers to reviewers, tracking
deadlines, and managing the review feedback. Once papers are accepted, the system can be used to
publish the conference proceedings online, making them accessible to a global audience. This
ensures wider dissemination of research findings and promotes knowledge sharing

1.2. Document Conventions (Definition, Acronyms, Abbreviations)

Definition
SRS: Software Requirements Specification, a document outlining functional and non-functional
requirements.
API: Application Programming Interface, a set of tools and protocols for building software
and applications.
GUI: Graphical User Interface, the interface through which users interact with electronic
devices.
DBMS: Database Management System, software for creating and managing databases.
Acronyms and Abbreviations
UI: User Interface
API: Application Programming Interface
DBMS: Database Management System
HTTP: Hypertext Transfer Protocol
XML: Extensible Markup Language

1.3. Scope
Public Conference provides a versatile environment to Share ideas and opinions in text or audio
formats. Explore ideas through personalized recommendations. Interact with other users via comments
and feedback. Authors can submit papers electronically, and reviewers can assess them online.
Accepted papers are published online, ensuring wider accessibility. Organizers can manage
registrations, scheduling, and other logistics. Authors and reviewers can communicate through the
platform.

1.4. References
Online Websites
https://www.computer.org/conferences/cps
https://www.webofconferences.org/

2. History/Background Study (Sources of Domain Knowledge)

2.1. Technical Literature
3|Page
 Books and Articles
"Modern Meteorology: Techniques and Applications" by James Cook
"Weather Forecasting Handbook" by Tim Vasquez
Online Resources
Universities and research institutions often provide access to digital libraries and conference
proceedings.

2.2. Existing Applications

This section reviews existing Conference Publication systems to identify best practices and areas for
improvement:
 Zoom
 Open conf
 Ex ordo
 Conf tool

2.3. Customer Surveys

Customer Form
Responses

4|Page
5|Page
6|Page
7|Page
8|Page
 2.4. Expert Advice
When it comes to online conference publication, experts in the field often recommend a structured
approach to ensure the conference is professionally managed, the content is properly disseminated,
and the publication is accessible to a wide audience. Below are some expert recommendations and
advice for organizing and publishing online conference materials:

2.5. Current/Future requirements

The requirements for online conference publication are evolving, driven by advancements in
technology, shifting academic and professional needs, and the increasing demand for more interactive,
accessible, and collaborative formats. Efficient submission, peer review, and selection processes.

3. Overall Description
3.1. Product Functions

An online conference publication platform or application typically serves several key functions that
facilitate the management, publication, and dissemination of conference materials, including
research papers, presentations, proceedings, and more. Here’s an outline of the key features and
functionalities an online conference publication platform

3.1.1. Hardware Requirement

Server Requirements:
 Processor: High-performance CPU to handle data processing and real-time updates.
 Memory: Sufficient RAM (at least 8 GB) and storage (minimum 1 TB SSD) for data
storage and processing.
 Network: High-speed internet connection for real-time data fetching and updates.
User Devices:
 Modern web browser compatibility (e.g., Chrome, Firefox, Edge)
 Mobile devices with iOS or Android for app usage

9|Pag
 3.1.2. Software Requirement

Operating System:
 Server: Reliable OS (e.g., Linux-based systems)
 User Devices: Compatibility with common OS (e.g., Windows, iOS, Android)
Integration and APIs:
 APIs to connect with meteorological data sources and services
 Compatibility with data formats like XML and JSON
Maintenance and Monitoring:
 Remote monitoring and diagnostics software to track system performance
 Automated update mechanisms for software and data sources

3.2. Functional Requirements

3.2.1. Author
 Description: Register and login to the system
 Input: Upload and submit papers
 Output: Receive confirmation of submission
 Error: Invalid credentials, duplicate accounts.
3.2.2. Reviewer
 Description: Register and login to the system
 Input: Review papers and submit reviews
 Output: Receive paper assignments
 Error: Data feed interruptions, integration failures,
Prediction inaccuracies, data processing errors.
3.2.3. Conference Admin
 Description: Manage user accounts (authors, reviewers)
 Input: Manage the conference database
 Output: Review reviews comments and make publication decisions
 Error: Prediction inaccuracies, data processing errors.

3.2.4. Notifications and Alerts

 Description: Notify Author about paper submission.
 Input: Details such as the submission ID, timestamp, and next steps are included.

10 | P a g
  Output: successful submission and notifications.
 Error: Notification delivery failures, incorrect alerts.
.
3.2.5. User Interaction
 Description: Facilitate user interaction and feedback.
 Input: User feedback, preferences.
 Output: User support responses, preference settings.
 Error: Feedback submission errors, preference update failures.
.

3.3. Non-Functional Requirements

3.3.1. Correctness Requirement
he correctness requirement of an online conference publication system ensures that the
system consistently produces accurate and reliable results throughout its operation. It
focuses on maintaining data integrity, adhering to predefined workflows, and meeting
the expectations of users.
3.3.2. Portability Requirement
Portability requirements ensure that the system can be easily transferred and operated across
different environments without significant modification. This is essential for an online
conference publication system, as users and organizers may work with diverse platforms and
devices. The system should function seamlessly on various operating systems, including
Windows, macOS, and Linux, for desktop users.

3.3.3. Efficiency Requirement

The efficiency requirement for an online conference publication system focuses on ensuring
the system performs its functions quickly and seamlessly, meeting the demands of all users—
authors, reviewers, and organizers—while handling high volumes of data and interactions
without degradation in performance. The system must deliver responses to user actions (e.g.,
uploading a manuscript, submitting a review, or generating reports) within a few seconds to
ensure a smooth user experience.

3.3.4. Usability Requirement

 Description: The system should offer a user-friendly interface that is easily accessible to
both technical and non-technical users.
 Measurement: User satisfaction surveys should reflect a usability score of at least 4.5 out of 5.
3.3.5. Reusability Requirement
 Description: The system must be available 24/7, with robust backup and recovery processes in

11 | P a g
 place to ensure continuous access.
 Measurement: System uptime should be 99.9% or higher, with backup processes executed
at least every 30 minutes.
3.3.6. Maintainability Requirement
 Description: The system should be designed for ease of maintenance and updates,
with modular components and effective error handling.
 Measurement: Average time to implement updates or fixes should be under 1 hour,
with documented procedures for handling errors efficiently.
3.4. User Characteristics
In an online conference publication system, various types of users interact with the platform, each
with distinct characteristics and need-Authors submit research papers, abstracts, or presentations for
review and publication. Focus on user-friendly submission forms.


3.5. Design & Implementation Constraints
When designing and implementing an online conference publication system, several constraints must
be considered to ensure the system is functional, efficient, and user-friendly. The system should be
accessible on multiple devices and browsers (e.g., desktop, tablet, and mobile), ensuring compatibility
with major web browsers like Chrome, Firefox, and Safari.
3.6. Assumptions & Dependencies
The system assumes that users (authors, reviewers, organizers) have reliable internet access to
submit and review papers. Users are assumed to have basic technical knowledge to interact with
the system, including uploading documents and using online tools for reviews.

4. Interface Requirements
4.1. Author Interfaces
Upload manuscripts, add metadata (title, authors, abstract, keywords). View and manage
revisions or resubmit based on reviewer feedback, Track the paper's status (submitted, under
review, accepted, rejected), Receive notifications and communicate with organizers/reviewers,
Access formatting templates and conference submission rules.
4.2. Hardware Interfaces
 Description: The hardware interfaces should support various devices, including smartphones,
tablets, and desktop computers. The system should adapt to different screen sizes and input
methods (e.g., touch, keyboard, mouse).
 Example: The system should be responsive, ensuring seamless functionality conference Pub
accessed on a mobile device or a desktop computer, with support for touch input on mobile
devices.

12 | P a g
 4.3. Communication Interfaces
Effective communication is critical in an online conference publication system, as it involves
multiple stakeholders, including authors, reviewers, conference organizers, and attendees. A
well-designed communication interface ensures seamless interaction and information
exchange. Enables authors to submit papers, track the review process, and receive feedback.
Uploading and versioning of manuscripts. Notifications for submission confirmation, review
updates, and publication status. Messaging options for clarifying review comments.
5. Conclusion
the development of an online conference publication system offers significant advantages to conference
organizers, authors, and attendees. By streamlining the submission, review, and publication processes,
the system enhances efficiency, reduces manual overhead, and ensures greater transparency. Features like
automated notifications, version tracking, and robust review workflows contribute to maintaining high
publication standards. Additionally, integrating user-friendly interfaces and secure data management
ensures that all stakeholders can interact seamlessly with the system. This fosters a collaborative
environment that encourages academic growth and knowledge dissemination.

13 | P a g