NITCONF is a conference website designed to facilitate paper submissions for evaluation. The platform enables reviewers to assess papers assigned to them by the Program Committee. The repository encompasses the entire Reviewers Project for this conference.
- Introduction
- 1.1 Purpose
- 1.2 Document Conventions
- 1.3 Intended Audience and Reading Suggestions
- 1.4 Product Scope
- 1.5 References
- Overall Description
- External Interface Requirements
- 3.1 User Interfaces
- 3.2 Hardware Interfaces
- 3.3 Software Interfaces
The Reviewers section in the NITCONF explains what reviewers can do. It gives rules and steps for reviewers to easily and smoothly judge and rate papers that people send in.
This document follows IEEE formatting requirements.
The document is intended to serve several groups of audience members :
- System Designer:
- They are the primary audience. It provides crucial information guiding the design phase.
- Program Committee:
- They are expected us to provide the required resources mentioned in the SRS Document.
- Author:
- They are expected to upload the Document/ Thesis in the specified format.
- Tester:
- They will refer to the SRS to ensure that the actual implementation aligns seamlessly with the specified requirements.
- User Authentication:
- A secure login page for reviewers to access the system.
- Reviewer Dashboard:
- Upon logging in, reviewers are directed to a personalized homepage, presenting a comprehensive overview of papers assigned to them.
- Paper Presentation:
- The system organizes assigned papers in a clear and systematic row-wise fashion for easy navigation.
- Reviewing Functionality:
- Reviewers have the capability to thoroughly evaluate papers, with options to edit and submit reviews seamlessly. These features collectively form the product scope, ensuring an efficient and user-friendly platform for the review process.
Refer to the following links for additional resources:
- https://www.springer.com/gp/computer-science/lncs/online-conference-service
- https://support.springer.com/en/support/solutions/articles/6000245514-description-of-the-end-to-end-process-in-equinocs
The reviewers page in NITCONF will serve as an interface for the reviewers to mark their review, add comments, feedbacks and ratings to the papers assigned to them by the Programme Committee. The Reveiwers would be provided with a login page where they can login with their credentials. There will be 3 sections under it
- To Review - All the papers that has to be reviewed and submitted to PC would be displayed here along with the deadline. After submission, these papers will go to the Reviewed session.
- Reviewed - The papers submitted to PC would be displayed along with the deadlines. The reviewer has the option to edit it and resubmit before the deadline. After deadline these papers will go to history.
- History - The history tab will show all the papers reviewed by that reviewer so far with the status and date.
- Notifications - All notifications from the PC would be here.
User - Reviewer
- Frequency of use: Reviewers engage with the system intensively during the conference periods.
- Functions used:
- paper review: reviewers will be able to give the review based on some metrics such as originality, relevance, quality, readability, technical soundness etc, additionally they would be able to give a confidence rating. finally they can accept/reject the paper or click on another option called revise. After finalizing the changes they can submit the review to the PC.
- Commenting and Feedback: They provide detailed comments and feedback for each paper, which may include critiques, suggestions for improvement, and overall assessments.
- Technical Expertise: A simple understanding of basic computer based tasks is enough to navigate the system as it is user friendly.
- ** Security Levels**: Reviewers require secure login credentials to login in to the system, this is done to ensure the integrity and confidentiality of the reviewing process.
- Educational Level and Experience: They possess significant expertise in their respective academic or industry fields. They must also have experience in the reviewing process which would enable them to critique better and provide some insightful comments.
Pertinent Requirements
- easy access to assigned papers because of the user friendly UI.
- divided into two sections : to review and review
- deadline tracking and submission status.
- a visible and clear display of the deadline for each paper to support timely reviews and submission along with reminders and notifications.
- real time status updation once the reviewer has submitted his review.
- decline to review.
- this option would be provided to the reviewer if they wish to decline to give a review.
- edit and resubmit capabilities available for reviewers.
- confidentiality and anonymity between reviewers and the authors of the paper by enforcing a double blind situation.
General requirements: NITCONF designed to be lightweight and accessible on platforms such as desktop computers and laptops. -Performance Specification: for optimal performance any modern processor, at least 8gb of ram and a stable internet connection re recommended for laptop and desktop users. -Cross platform compatibility irrespective of the OS , this application (NITCONF) can run smoothly.
Server Requirements -Platform: Java-compatible server environment, as Spring Framework is Java-based. -Web Server: Compatible with servers like Apache Tomcat, Jetty, or similar servlet containers. -Java Version: Requires Java JDK 8 or higher, considering Spring Framework's requirements. -Memory and Storage: Sufficient RAM and disk space for handling concurrent user sessions and data storage. The exact requirements depend on the expected user load and data volume.
Client-Side Requirements -Web Browsers: Compatible with modern web browsers including Google Chrome, Mozilla Firefox, Microsoft Edge, and Safari. The application should be tested across these browsers for consistency. -JavaScript Enabled: As modern web applications often rely on JavaScript for dynamic content, users should have JavaScript enabled in their browsers.
Network Requirements -Bandwidth and Connectivity: Adequate network speed and stability for seamless access and data exchange, especially important for data-intensive operations or real-time features. -Security Protocols: Utilizes HTTPS for secure communication over the internet.
Software Dependencies -Spring Framework -Database: Compatible with relational databases like MySQL, MySQL workbench, PostgreSQL, or similar, depending on the application's data persistence requirements. -Frontend Technologies: Includes HTML5, CSS3, JavaScript.
Deployment Environment Containerization: The application is containerized using Docker, Kubernetes. API testing tools: Postman, swagger.io, SoapUI. CI/CD Pipelines: Integration with continuous integration and continuous deployment tools.
- Security Concerns: Risks of unauthorized access and data breaches.
- User Authentication and Authorization: Potential issues in login processes and user permission management.
- User Experience (UX):Possible usability issues impacting user satisfaction.
- Data Integrity and Validation:Risks of data corruption or acceptance of invalid data.
- Scalability:Potential performance degradation with increased usage.
- File Uploads:Security vulnerabilities and risks associated with file uploads.
- Review Workflow: Inefficiencies or confusion in the paper review process.
- Backup and Recovery: Potential data loss without regular backups and recovery plan.
- Login: Reviewers log in with their credentials and are directed to the reviewer dashboard.
- Profile: The user's profile icon is displayed in the top right corner, linking to the profile page.
- homepage: contains links/buttons to the following options:
- To Review: A list of papers assigned for review.
- Reviewed: Papers that have been reviewed by the user.
- View History: A history of papers reviewed in the past 6 months.
- Layout: Displays assigned papers in a row-wise manner.
- Columns:
-
Pdf id and Downloads: Includes a pdf id, 'Abstract' and 'PDF Download' buttons.
-
Paper Title and Actions: Shows the paper's title with 'Review' and 'Display All Reviews' options. 'Review' opens a pop-up for rating, commenting, and final actions ('Accept', 'Reject', or 'Revise'). 'Display All Reviews' reveals all previous comments/reviews.
-
Status: Indicates the current status of the paper (Accept/Reject/Pending).
-
Revision: Shows the revision round of the paper (e.g., first, second).
-
Deadline: Lists the review deadline set by the Program Committee.
-
Decline: A button that can be pressed if the reviewer chooses not to review that paper.
-
- Content: Lists all reviewed papers.
- Columns:
- Pdf id and Downloads: Includes a pdf id, 'Abstract' and 'PDF Download' buttons.
- Paper Title and Edit Options: Displays the paper's title with 'Edit' and 'Display All Reviews' buttons. 'Edit' allows modification of the most recent review. 'Display All' shows all past reviews.
- Status: The final status of the paper (Accept/Reject).
- Revision: Shows the revision round of the paper (e.g., first, second).
- Deadline: The review deadline, after which the paper is removed from this page.
- Content: Lists all reviewed papers in the last 6 months.
- Columns:
- Pdf id and Downloads: Includes a paper pdf id, 'Abstract' and 'PDF Download' buttons.
- Paper Title and Edit Options: Displays the paper's title with a 'Display All Reviews' button.
- Status: The final status of the paper (Accept/Reject).
- Revision: Shows the revision round of the paper (e.g., first, second).
- Deadline: The review deadline, after which the paper is removed from this page.
- Content: Lists all notifications from PC, like paper assignments and deadline reminders.
- Third-Party Components: Assuming the availability and reliability of third-party libraries or frameworks used in the development of the website.
- Internet Connectivity: Assuming that users and reviewers have consistent internet access for seamless interaction with the platform.
- Browser Compatibility: Assuming standard browser compatibility for optimal user experience.
- User Cooperation: Assuming users will follow proper guidelines for paper submissions and reviews.
- Work Flow: Assigned by the program committee, reviewers submit their evaluations, and the committee provides the final response to authors. All communication between reviewers and authors is facilitated through the program committee for efficiency and coherence.
- External APIs:Dependency on external APIs for features like user authentication or data retrieval.
- Database System:Dependency on the chosen database system for storing and retrieving paper and user data.
- Hosting Service:Dependency on a reliable hosting service for the website to be accessible online.
- Development Tools:Dependency on specific development tools, languages, or frameworks.
Our platform's user interface has been meticulously crafted to provide a user-friendly and efficient experience for reviewers. Upon logging in, reviewers will be greeted with a clean and intuitive dashboard that offers quick access to their assigned submissions. The interface incorporates clear navigation menus, allowing reviewers to seamlessly move between different sections of the platform.
Within each submission, the user interface allows reviewers to access abstracts, full papers, and supplementary materials with ease. A centralized hub for reviewing activities, including providing feedback, assigning scores.
-
Desktop/Laptop:
-
Processor: A dual-core processor or equivalent for smooth processing.
-
RAM: 4 GB or higher to handle multiple tasks concurrently.
-
Display: A screen resolution of 1280x800 or higher for an optimal viewing experience.
-
- Integration with External Software Components:
-
a. Database Management System:
- Name and Version: MYSQL 8.0
-
b. Operating System:
- Name and Version: Ubuntu / MacOS / Windows
-
c. Frontend Framework:
- Name and Version: HTML, CSS, JS
- Data Flow and Messages:
-
a. Incoming Data:
- Submission Data: Handled by Spring MVC controllers, data from submitted papers will be processed and stored in the MYSQL database.
-
b. Outgoing Data:
- Review Feedback: Managed by Spring MVC controllers, sending review feedback stored in MYSQL to the frontend.