EX NO SOFTWARE REQUIREMENT SPECIFICATION

DATE FOR CONFERECE MANAGEMENT SYSTEM

Problem Statement
Drafting a Software Requirement Specification (SRS) for Software Personnel Management
System.
Design Approach
1.0 Introduction
1.1 Purpose
The purpose of this document is to provide a detailed description of the requirements for the
Conference Management System.

1.2 Scope of the Project

The main goal of a conference management system is to make organizing and running conferences
easier and more efficient. It’s key objective of to reduce the workload of organizers by saving time,
facilitating better communication with participants, and ensuring smooth event operations. Ultimately, the
system aims to create successful conferences.

1.3 Glossary
Term Definition
Admin The person in charge of managing and organizing everything in the conference system
like creating conferences, assigning roles, managing participants, accessing submitted
papers, publishing papers, receiving feedback, and moderating forums.
Attendee An attendee is someone who participates in the conference.
Author The person who submits research papers or articles to be reviewed and potentially
published in conference proceedings or journals.
CMS Conference Management System – A software system designed to help managing
conferences, including tasks such as registration, scheduling, and communication.
Conference A large formal meeting at which there are groups of talks on a particular subject.
Forum A digital platform within the conference management system where attendees and
administrators can engage in discussions, ask questions, share insights, and exchange
information related to the conference topics.
Research A written document that presents the findings, analysis, and conclusions of original
Paper research conducted by the authors on a specific topic. Research papers are submitted for
review and publication in conferences or academic journals.
Review A written evaluation of a research paper or article submitted for publication. Reviews
may include comments, suggestions, and recommendations for improvement or approval
for publication.
Reviewer A person responsible for evaluating submitted research papers or articles, providing
feedback, and recommending whether they should be accepted for publication.
Speaker Speaker is an in individual scheduled to deliver presentations or talks at the conference,
often experts in their field.
Webform A digital form accessed through the Conference Management System, allowing authors
to interact with the system by submitting research papers, viewing conference details, and
accessing reviews for their submitted papers.
1. References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements Specifications.
IEEE Computer Society, 1998.

1.4Overview of Document
The next chapter, the Overall Description section, of this document gives an overview of the
functionality of the product. It describes the informal requirements and is used to establish a context for the
technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written primarily for the
developers and describes in technical terms the details of the functionality of the product.
Both sections of the document describe the same software product in its entirety, but are intended for
different audiences and thus use different language.

2.0 Overall Description

2. System Environment

Admin

Author
Conference
Creation

Research
Paper

Reviewer Online
Conferenc
Streaming
Services

Conference
Management System

Attendee
Figure 3.1 – System Environment
 The Conference Management System has four active actors and one cooperating system. The
Attendee, Author or Reviewer accesses the System through internet. The Attendees can communicate with
each other through an online forum created especially for each one of the conferences. The Administrator
can access the system directly. There is a link to access external online streaming platforms where the
conferences, workshops or webinars will be conducted.

2.2 Functional Requirements Specification

2.2.1. Attendee Use Cases

Use Case: Browse Conference Information

Diagram

Browse

Attendee

Brief Description

The participant accesses the conference management system to view information regarding the conference.

Initial Step-By-Step Description

Before this use case can be initiated, the participants have already registered into the Conference Management
System

1. The participant selects the Browse option.

2. The system displays categories or sections available for browsing, such as papers, presentations,
schedules, and forums.
3. The participant selects a specific category of interest to view relevant details.
4. The system displays the full details of the selected item, including abstracts, authors, and additional
information.

Use Case: Register for conference

This use case extends the Register for Conference use case.
Diagram

Register for Conference

Brief Description
The Attendee registers for a new conference.
Initial Step by Step Description
Before this use case can be initiated, the Attendee has already accessed the main page of the Conference
Management System and has viewed all the conferences available.
1. The Attendee chooses the desired conference.
2. The Attendee selects to Register.
3. The system presents a choice of entering as an Author, or a Reviewer or just as a participant.
4. The Attendee chooses to enter as a participant.
5. The system presents a confirmation message.

Use Case: Forum Access

This use case extends the Register for conference use case.

Diagram

Forum access

Brief Description

The Attendee gains access to conference forum.

Initial Step-By-Step Description

Before this use case can be initiated, the Attendee has already registered for the conference using the
Register for Conference use case.

1. The Attendee selects to Forum.

2. The system presents a forum exclusive to that conference.
3. The Attendee posts their query or express their thoughts regarding the conference.
4. Thus they can communicate with other members of the community by posting the message.

Use Case: Attend Conference

This use case extends the Register for conference use case.

Diagram
 Attend Conference

Brief Description

The Attendee gains access to conference.

Initial Step-By-Step Description

Before this use case can be initiated, the Attendee has already registered for the conference using the
Register for Conference use case.

1. The Attendee selects the Join button.

2. The system presents a link to the conference.
3. The Attendee accesses the link to join the conference.

Use Case: Give Feedback

This use case extends the Register for conference use case.

Diagram

Give Feedback

Brief Description

The Attendee gives feedback on the conference.

Initial Step-By-Step Description

Before this use case can be initiated, the Attendee has already registered for the conference using the
Register for Conference use case.

1. The Attendee selects the Feedback button displayed after the conference.
2. The system presents a feedback pop up.
3. The Attendee enters their feedback.
4. Then they click the Submit button.
5. The Admin can access the feedback.
2.2.2 Author Use Case
Use Case: Submit Paper
This use case extends the Register for Conference use case.
Diagram

Submit Paper

Author

Brief Description
The Author submits their research paper or resubmits an edited version of their paper.
Initial Step by Step Description
Before this use case can be initiated, the Author has already connected to the Conference Management System
and is registered as a Author.
1. The Author chooses to publish their research paper.
2. The System uses a webform to collect the details.
3. The Author fills the form and attaches their research paper.
4. The Author chooses the submit paper button.

Use Case: See Reviews

This use case extends the Submit Paper use case.
Diagram

Sees Review

Author

Brief Description
The Author accesses and view the reviews for their article.
Initial Step by Step Description
Before this use case can be initiated, the Author has already connected to the Conference Management System
and has submitted a research paper.
1. The Author chooses to view the reviews for their research paper.
2. The Author views the conference tab to select the conference.
3. The Author can see the status of their paper like submitted, under review, see review.
4. The Author chooses the view review button if the review is available.
5. Thus the Author can access the reviews to their paper and perform necessary revision to their paper.

2.2.3 Reviewer Use Case

Use Case: Access Papers
Diagram

Accesses Paper

Reviewer

Brief Description
The reviewer access the research papers that are assigned to them for review.
Initial Step by Step Description
Before this use case can be initiated, the Reviewer has already connected to the Conference Management
System and is registered as a Reviewer.
1. The Reviewer chooses the Papers to Review tab.
2. The System presents the list of papers that have been assigned to the reviewer.
3. The Reviewer chooses the view paper button to access the papers.

Use Case: Review Paper

This use case extends the Access Papers use case.
Diagram

Review Paper

Reviewer

Brief Description
The Reviewer writes a review for the papers.
Initial Step by Step Description
Before this use case can be initiated, the reviewer has already accessed the Papers to Review tab and the
reviewer should have been assigned some papers for reviewing by the admin.
1. The Reviewer chooses the view paper button to access the papers.
2. The System presents the paper submitted by an Author.
3. The Reviewer chooses the show details button to see other information about the document
provided when submitting the paper.
4. The Reviewer selects the write review option to write a review for the paper.
5. The System presents a web form that is to be filled by the Reviewer.
6. The Reviewer chooses the submit review button.

2.2.4 Administrator Use Case

Use Case: Create Conference

Diagram

Create

Admin
Brief Description

The admin initiates the process to create a new conference within the system.

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System.

1. The admin navigates to the Create Conference section.

2. The admin fills in the input details such as conference title, description, date, location and
speaker bio.
3. The system creates the conference and notifies the admin of successful creation.
Use Case: Manage Participant

Diagram

Manage Participants

Admin

Brief Description

The admin manages participants registered for a conference, including adding or removing participant

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System

1. The admin selects the Manage Participants option.

2. The system presents a list of participants registered for the conference.
3. The admin selects an action: add or remove participant.
4. If adding a participant, the admin fills in the required details and, if removing a participant, the
admin selects the participant to be removed submits the form.
5. The admin receives confirmation of the changes.

Use Case: Assign Reviewer

Diagram

Assign Reviewer

Admin

Brief Description

The admin assigns a reviewer to evaluate submissions for a specific conference.

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System

1. The admin selects the Assign Reviewer option.

2. The system presents a list of available reviewers and the admin selects a reviewer from the list.
3. The admin confirms the assignment.
4. The system updates the conference with the assigned reviewer.
5. The assigned reviewer receives a notification about the assignment.
Use Case Access Submitted Paper

Diagram

Access Submitted Papers

Admin

Brief Description

The admin accesses papers submitted by authors for a specific conference.

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System

1. The admin selects the conference for which they want to access submitted papers.
2. The system displays a list of submitted papers for the chosen conference.
3. The admin selects a paper to access its details. The system presents the full text of the paper
along with any accompanying files.
4. The admin can download, view, or provide feedback on the submitted paper.

Use Case: Publish Paper

Diagram

Publish Paper

Admin
Brief Description

The admin publishes accepted papers to make them available to conference attendees and the wider audience.

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System.

1. The system displays a list of accepted papers awaiting publication from which the admin selects
the papers they wish to publish.
2. The admin confirms the selection and initiates the publishing process.
3. The published papers become accessible to conference attendees and are made available for
public viewing.
Use Case: Receive Feedback

Diagram

Receive
Feedback

Admin

Brief Description

The admin reviews and acts upon feedback received from reviewers and participants regarding various
aspects of the conference.

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System

1. Feedback is submitted by reviewers and participants through the conference management system.
2. The admin accesses the feedback section within the system.
3. The system categorizes feedback types like paper reviews, session feedback and overall conference
feedback.
4. The admin selects specific feedback for detailed review.
5. The admin evaluates feedback and takes necessary actions, such as addressing concerns, planning
improvements, or acknowledging positive feedback.

Use Case: Create Forum

Diagram

Create Forum

Admin
Brief Description

The admin initiates the creation of the forum section, providing conference participants with a platform to
engage in real-time discussions during scheduled conference sessions.

Initial Step-By-Step Description

Before this use case can be initiated, the admin has already logged into the Conference Management System

1. The admin selects the option to create a forum section.

2. The system prompts the admin to input details such as the forum title and description.
3. The system creates the forum section and notifies the admin of successful creation.
4. The forum section becomes available for participants to use during scheduled conference sessions.
5. Participants engage in real-time discussions within the forum, as facilitated by the admin’s creation.
2.3 User Characteristics

 Attendees should be proficient in internet usage and able to navigate web interfaces for
conference registration and participation in discussions.
 Authors should be skilled in internet usage for submitting conference materials electronically.
 Administrators should possess computer skills for managing the system’s operations and user
accounts.
 Reviewers need internet proficiency for evaluating submissions and providing feedback through
the system’s interface.

2.4 Non-Functional Requirements

The Conference Management System (CMS) will be hosted on a server with high-speed internet
capability, allowing for efficient access and responsiveness. The system is designed to support connectivity
between web pages and the database, with a focus on compatibility with various server environments. The
speed of participants’ conference activities will be influenced by individual hardware and network
capabilities, rather than intrinsic characteristics of the CMS. The CMS software will be developed to ensure
optimal performance and responsiveness, recognizing the diversity of user environments. Additionally, the
system will be compatible with the Windows operating system, providing seamless integration for users
operating within this environment.

3.0 Requirements Specification

3.1Functional Requirements

3.1.1 Browse Conference Information

Use Case Name Browse

Trigger Participant selects to browse conference information.
Precondition Participant is authenticated and has access to the system.
Basic Path 1. Participant logs into the system and navigates to the conference information
section.
2. Participant selects the desired category of information (e.g.
3. System displays relevant details within the chosen category.
4. Participant navigates through the information and interacts with the system as
needed.
Alternative Paths If the participant encounters any issues accessing the information, the system
provides troubleshooting options or redirects to the main page.
Postcondition Participant successfully views conference information.
Exception Paths If the selected conference information is not available or cannot be accessed, the
system displays an error message and prompts the participant to try again later or
contact support for assistance.
Other System may provide options for downloading or printing information for reference.
3.1.2 Register for conference

Use Case Name Register for conference

Trigger The Attendee clicks on the register button.
Precondition The Attendee has accessed the Conference Management main screen.
Basic Path 1. Attendee selects the desired conference from list of all conferences displayed.
2. The system presents with register option.
3. After the attendee clicks on register button, they are displayed with options to
attend the conference as an author, a reviewer or as a participant.
4. Attendee opts to register as a participant.
5. The system displays a confirmation message
Alternative In step 3, if there is no option chosen and the user tries to register then the system
Paths prompts to select an option.
Postcondition The Attendee has been added to the database.
Exception Paths The Attendee may abandon the operation at any time.
Other The Conference information includes the name of the conference, domain, keynote
speakers, date and time.

3.1.3 Forum Access

Use Case Name Forum access

Trigger The Attendee clicks on the Forum button.
Precondition The Attendee has accessed the screen of the specific conference they registered for.
Basic Path 1. Attendee clicks on the conference they registered for.
2. The system presents with the screen containing information about that conference.
3. The Attendee clicks on Forum button.
4. Attendee can post their queries by clicking on the message button.
5. Attendee can read the queries of others as well as reply to them using the reply
button.
Alternative None
Paths
Postcondition The Attendee’s message has been added to the database.
Exception Paths The Attendee may abandon the operation at any time.
Other None.

3.1.4 Attend Conference

Use Case Name Attend conference

Trigger The Attendee clicks on the join button.
Precondition The Attendee has accessed the screen of the specific conference they registered for.
Basic Path 1. Attendee clicks on the conference they registered for.
2. The system presents with the screen containing information about that conference.
3. The Attendee clicks on Join button.
4. The system presents with link to that conference.
5. Attendee can access the conference with the link provided.
Alternative None.
Paths
Postcondition The Attendee joins the conference.
Exception Paths The Attendee may abandon the operation at any time.
Other The link provided may lead to external video streaming platforms.
3.1.5 Give Feedback

Use Case Name Give feedback

Trigger The Attendee selects the feedback button.
Precondition The Attendee has accessed the screen of the specific conference they registered for.
Basic Path 1. Attendee clicks on the conference they registered for.
2. The system presents with the screen containing information about that
conference.
3. The Attendee clicks on Feedback button.
4. The system presents with message box.
5. Attendee can type their feedback in there.
6. Attendee clicks the submit button.
Alternative Paths If the Attendee tries to submit without entering message then the system prompts to
enter the feedback.
Postcondition The Feedback message has been added to the database.
Exception Paths The Attendee may abandon the operation at any time.
Other None

3.1.6 Submit Paper

Use Case Name Submit Paper

Trigger The Author proceeds to the paper submission process by clicking the submit paper
button.
Precondition The Author has accessed the conference for which he is submitting his paper.
Basic Path 1. The System uses a webform to collect the details.
2. The Author fills the form and uploads their research paper.
3. The Author chooses the submit button.
Alternative Paths In step 2, the Author may leave out some fields and submit the form. In such cases
alert messages are used to inform them.
Postcondition The database has been updated.
Exception Paths The Author cancels/abandon’s the submission process at any time.
Other The Author fills in the details like their name, topic, submission date, their paper in
pdf file format.

3.1.7 See Reviews

Use Case Name See Reviews

Trigger The Author clicks on the view review button.
Precondition The Author has already accessed the conference from the conference tab.
Basic Path 1. The Author views the conference tab to select the conference.
2. The Author checks the status of their paper.
3. The Author clicks on the view review button if the review is available.
4. The System displays the reviews for the paper.
Alternative Paths In step 2 the paper may be under review or just submitted. In that cases the review
could not be accessed.
Postcondition The Author would be able to view the review.
Exception Paths None
Other The status of the paper can be submitted, under review or see review.
3.1.8 Access Papers

Use Case Name Access Papers

Trigger The Reviewer clicks on the Papers to Review button.
Precondition The Reviewer has already connected to the Conference Management System.
Basic Path 1. The Reviewer chooses the Papers to Review tab.
2. The System presents the list of papers that have been assigned to the reviewer.
3. The Reviewer chooses the view paper button to access the papers.
Alternative Paths In step 2, the Reviewer may not have any papers assigned to them for review.
Postcondition The System displays the paper that is selected to be reviewed by the Reviewer.
Exception Paths None
Other The displayed options may include show details, write review, submit review.

3.1.9 Review Paper

Use Case Name Review Paper

Trigger The Reviewer has clicked on the view paper button.
Precondition The Reviewer has already accessed the papers to review tab.
Basic Path 1. The System presents the paper submitted by an Author.
2. The Reviewer chooses the show details button to see other information about the
document provided when submitting the paper.
3. The Reviewer selects the write review option to write a review for the paper.
4. The System presents a web form that is to be filled by the Reviewer.
5. The Reviewer chooses the submit review button.
Alternative Paths None
Postcondition The Review is updated in the database and reflected across the system.
Exception Paths None
Other The web form will include details like Reviewer name and a review in pdf file
format

3.1.10 Create Conference

Use Case Name Create Conference

Trigger System receives request from Admin to initiate conference creation.
Precondition Admin is authenticated and has access to Conference Management System.

Basic Path 1. System presents Create Conference section to Admin.

2. Admin provides mandatory conference details: title, date, venue, description.
3. Admin configures additional settings: registration fees, deadlines, tracks.
4. Admin submits conference details to System.

Alternative Paths System prompts Admin for missing or erroneous information.

Postcondition System registers new conference entry in database.
Exception Paths Admin cancels conference creation process.
Other System auto-generates unique identifier for conference tracking.
3.1.11 Manage Participant

Use Case Name Manage Participant

Trigger The System receives request from the admin to manage the participants
Precondition Admin is authenticated and has access to the conference management system.
Basic Path 1. The system presents a list of participants with options to add or remove.
2. The admin selects “Add Participant.”
3. The system presents a form to enter participant information.
4. The admin enters the information and submits the form.
5. The system checks that required fields are not blank and updates the participant
list.
Alternative Paths In step 4, if any required field is blank, the Admin is prompted to fill in the missing
information.
Postcondition The new participant has been added or removed to the conference participant list.

Exception Paths The Admin may abandon the operation at any time.
Other Participant information includes name, email, affiliation, and contact number.

3.1.12 Assign Reviewer

Use Case Name Assign reviewer

Trigger The System receives request from the admin to assign the reviewers
Precondition Admin is authenticated and has access to the conference management system.

Basic Path 1. The system presents a list of submissions with options to reviewers.
2. The admin selects a submission to assign a reviewer.
3. The system displays a list of available reviewers.
4. The admin selects a reviewer and submits the assignment.
5. The system updates the database with the reviewer assigned to the submission.

Alternative Paths 1. In step 2, if no submission is selected, the admin is prompted to choose a

submission.
2. In step 4, if no reviewer is selected, the admin is prompted to choose a reviewer.
Postcondition The selected reviewer has been assigned to review the chosen submission.
Exception Paths The admin may abandon the operation at any time.
Other Reviewer assignment includes the submission ID, reviewer ID, and any additional
notes from the Admin.
3.1.13 Access Submitted papers

Use Case Name Access submitted papers

Trigger The System receives request from the admin to access submitted papers
Precondition Admin is authenticated and has access to the conference management system.
Basic Path 1. The system presents a list of submitted papers with options to view or
manage access.
2. The admin selects a submitted paper to access.
3. The system displays details of the selected paper, including author information
and content.
4. The admin can choose to grant or restrict access to the paper.

Alternative Paths In step 2, if no paper is selected, the admin is prompted to choose a paper.
Postcondition The admin has successfully managed the access to the selected submitted paper.

Exception Paths The admin may abandon the operation at any time.
Other Paper details include title, author, abstract, and content. Access management
includes options to grant or restrict access.

3.1.14 Publish Paper

Use Case Name Publish Paper

Trigger Admin initiates the publication process for a submitted paper.
Precondition Admin is authenticated and has access to the Conference Management System.
Basic Path 1. Admin accesses the Publish Paper section in the system.
2. Admin selects the submitted papers for publication.
3. Admin reviews the selected papers for suitability and compliance.
4. Admin confirms the decision to publish the papers.

Alternative Paths 1. If the paper requires revisions, Admin may send it back to the author for
amendments.
2. Admin may choose not to publish certain papers due to non-compliance or other
reasons.
Postcondition Selected papers are published and made accessible to conference attendees.
Exception Paths Admin cancels the publication process.
Other System logs the publication status and timestamps for audit trail.

3.1.15 Receive Feedback

Use Case Name Receive Feedback

Trigger System prompts Admin to review feedback.
Precondition Admin logged into Conference Management System.
Basic Path 1. System notifies Admin of new feedback submission.
2. Admin accesses feedback section within system interface.
3. Admin reviews categorized feedback types
4. Admin selects specific feedback for detailed review.
Alternative Paths 1. If feedback requires further clarification, Admin engages in discussion with
respective reviewers or participants.
 2. Admin may categorize feedback based on severity and prioritize actions
accordingly.
3. In case of controversial feedback, Admin consults with other stakeholders or
organizes a committee for resolution.

Postcondition Feedback status updated in system, reflecting admin actions.

Exception Paths Admin may postpone review of feedback for later action.
Other System tracks feedback status and admin responses for auditing purposes.

3.1.16 Create Forum

Use Case Name Create Forum

Trigger Admin initiates the creation of a new forum.
Precondition Admin authentication and access to Forum Management System.
Basic Path 1. Admin navigates to the Create Forum section.
2. Admin specifies forum details: title, description, rules.
3. Admin configures additional settings: categories, permissions.
4. Admin submits forum creation request to the system.
Alternative Paths System alerts Admin if required details are missing.
Postcondition New forum is successfully created and accessible to users.
Exception Paths Admin cancels forum creation process.
Other System generates unique identifier for forum identification.

3.1.17 Browse

Use Case Name Browse

Trigger Participant selects to browse conference information.
Precondition Participant is authenticated and has access to the system.
Basic Path 1. Participant logs into the system and navigates to the conference information
section.
2. Participant selects the desired category of information (e.g.
3. System displays relevant details within the chosen category.
4. Participant navigates through the information and interacts with the system as
needed.
Alternative Paths If the participant encounters any issues accessing the information, the system
provides troubleshooting options or redirects to the main page.
Postcondition Participant successfully views conference information.
Exception Paths If the selected conference information is not available or cannot be accessed, the
system displays an error message and prompts the participant to try again later or
contact support for assistance.
Other System may provide options for downloading or printing information for reference.
3.2 Detailed Non-Functional Requirements
3.2.1 Logical Structure of the Data

Admin

Creates

Conference

Attendee
Attend
Author

Reviewer
Submits

Sent to

Paper Writes

Review
has

Figure 3.2 – Logical Structure of Conference Management Data

Conference Data Entity

Data Item Type Description Comment
Name Text Name of the Conference
Admin Pointer Admin Entity Name of the admin of the
Conference.
Date Date Date of the conference. Set up by the Admin
Start Time Time Start time of the Conference.
End Time Time End time of the Conference.
Description Text Descriptive text about the conference.
Speaker Text Name of one speaker. May be several
Guest Speaker Text Guest Speaker may be any or NULL Name of the Guest Speaker
Admin Data Entity:
Data Item Type Description Comment
Email Text Email address of the admin
Username Text Username used for login/authentication

Password Text Password for login/authentication

Attendee Data Entity:

Data Item Type Description Comment
Username Text Username of the attendee
Password Text Password of the attendee
Email Text Email address of the attendee
Attended Pointer Conference entity attended by the attendee May be several
Conference
Registered Pointer Conference entity registered by the May be several
Conference attendee

Author Data Entity:

Data Item Type Description Comment
Email Text Email address of the author
Username Text Username used for login/authentication

Password Text Password for login/authentication

Conference Pointer Conference entity May be several
Paper Pointer Paper entity May be several

Reviewer Data Entity

Data Item Type Description Comment
User Name Text Name of the reviewer
Password Text Password of reviewer
Email Text Email ID associated
Paper Pointer Paper entity May be several

Paper Data Entity:

Data Item Type Description Comment
Author Pointer Author entity Pointer to the principal author
of the paper
Reviewer Pointer Reviewer entity Will be several
Review Pointer Review entity Pointer to the review
associated with the paper
Contents Text Content of the paper May be several

Review Data Entity

Data Item Type Description Comment
Paper Pointer Paper entity
Reviewer Pointer Reviewer entity Single Reviewer
3.2.2 Security
 The system will ensure that only authorized personnel, such as admins, authors, reviewers, and
attendees, have access to specific functionalities and data within the conference management system.
 Admins will be granted privileges to create conferences, while authors and reviewers will have
access to research papers relevant to their roles.
 Attendees will have access to conference-related information, such as schedules and sessions, within
their designated roles.
 Security protocols will be in place to prevent unauthorized access to the system’s server, ensuring the
integrity and confidentiality of the data stored within.

4.0 Bibliography

Shobigaa V, Yuvavarshitha K B, Yamini P, Sharmila P. “Software Requirement

Specification for Conference Management System”, CSE PSNA College of Engineering
and Technology, Dindigul, 2024.

Conclusion
Thus Software Requirement specification for conference Management system has been
drafted successfully.