CONFERENCE MANAGEMENT SYSTEM

AIM
To develop a project on Conference management system using Rational Rose
Software and to implement the project in Visual Basic.

PROBLEM ANALYSIS AND PROJECT PLANNING

The Conference Management System is an online website in which candidate can submit
the paper and register themselves and then attend the conference. The paper will be reviewed.
The details of the conference, date and time will be made available to them through the website.
After getting the confirmation details the candidate should submit the revised and camera ready
paper. Then the registration process will be done.

PROBLEM STATEMENT
The process of the candidates is to login the conference system and submit the paper
through online. Then the reviewer reviews the paper and sends the acknowledgement to the
candidate either paper selected or rejected. This process of on conference management
system are described sequentially through following steps,
• The candidate login to the conference management system.
• The paper title is submitted.
• The paper is been reviewed by the reviewer.

•• TBhaseerde voine wtheer sseelnedcsti oacnk, nthoewbleedstgceamnednidt atot

hisescealencdtiedda.t e.
• Finally the candidate registers all details.
SOFTWARE REQUIREMENT SPECIFICATION

S NO SPECIFICATION
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIREMENTS

INTRODUCTION
This software specification document consist full set of features and function for
online conference management system. In this we give specification about the system
requirements that are apart from the functionality of the system to perform the candidate paper
valuation. It tells the usability, reliability defined in use case specification.

OBJECTIVE
The main objective of Conference Management System is to accomplish paper
submission online, update the presentation details and confirm registration. Conference
management system provides online help to the users all over the world.

OVERVIEW
The overview of the project is to design a process which ease the work for the
candidate as well as the reviewer. Candidate can easily submit the paper and go for
registration.
 GLOSSARY

TERMS DESCRIPTION
CANDIDATE
The candidate can login and submit the paper to the reviewer. After getting acknowledgement the candidate wil submit the revised and camera ready paper then registration process
w i l l b e c a r r i e d o u t .

REVIEWER
Reviewer will reviews the paper and sending acknowledgement to the candidate

DATABASE
Database is used to verify login and store the details of selected candidates.

SOFTWARE REQUIREMENT SPECIFICATION This software specification documents full set of features
and funct ion for conference management system.

PURPOSE
The purpose of the conference management system is that the system can easily
review the process. The main process in this document is the submission of paper by the
candidate, reviewing process by the reviewer and sending of acknowledgement to the
candidates whose paper is selected.

SCOPE
The scope of this conference management process is to select the best candidate from the
list of candidates based on their performance in the process.

FUNCTIONALITY
The main functionality of conference system is to select the candidate for the
presentation in conference.

USABILITY
The user interface to make the process should be effective that is the system will help the
candidates to register easily. The system should be user friendly.
PERFORMANCE
It describes the capability of the system to perform the conference process of the
candidate without any error and performing it efficiently.

RELIABILITY
The conference system should be able to serve the applicant with correct information
and day-to-day update of information.

FUNCTIONAL REQUIREMENTS
Functional requirements are those that refer to the functionality of the system that is the
services that are provided to the candidate who register for the conference.

UML DIAGRAMS
The following UML diagrams describe the process involved in the conference
management system.
• Use case diagram
• Class diagram
• Sequence diagram
• Collaboration diagram
• State chart diagram

•• AComctivponeity dntia digraamgr am

• Deployment diagram
• Package diagram

USE CASE DIAGRAM

A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is
represented using ellipse.
Actor is any external entity that makes use of the system being modeled. It is
represented using stick figure.
 login

paper submission

candidate review the paper

reviewer database

paper confirmation details

revised and camera

ready paper submission

registration

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are candidate, reviewer and database. The use cases
are the activities performed by actors.
The actors in this use case diagram are
• Candidate - Logins the conference system and submits the paper then do the
registration process.
• Reviewer – Review the paper , select best candidate and send
acknowledgement to them.
• Databases - verify the login and register details and selected candidate details
are stored in it.
The use cases in this use case diagram are
• Login - Candidate enter their username and password to login to the
conference system.
• Paper sumbission – Candidate submits the paper.
 • Review the paper– The paper is been reviewed by the reviewer and the paper is
selected.
• Paper confirmation details – The reviewer can send the confirmation details to
the candidate.
• Revised and camera ready paper – After the paper is selected and the
camera ready paper should be submitted to the reviewer by candidate.
• Registration – After submitting the revised paper the candidate wants to
register.

CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle with
three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has three classes candidate, reviewer and database.
• Candidate – Its attributes are name , collegename , department , paper title.
The operations performed in the candidate class are login, submit the paper,
submit revised and camera ready paper and registration.
• Reviewer – Its attributes are name, department, reviewer ID The
operations performed are review the paper and send the paper confirmation
details.
• Database –The operations performed are storing candidate details and
verifying login .

SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
SEQUENCE DIAGRAM FOR LOGIN

candidate login database

1: enter the user

name 2: enter the

password

3: submit

4: verification process

5: incorrect username or pass word

6: login again
DOCUMENTATION OF SEQUENCE DIAGRAM
LOGIN
This sequence diagram describes the sequence of steps to show
• The candidate login in to the conference system and register for job.
• The verification done in the database .

PAPER SUBMISSION
This sequence diagram shows steps to show
• The candidate sumbit the paper.

•• TThehe r ceavindiewdaetrer seubmviewists t rheevi paseped ar and cnd saemndse

arceknowady plaepgeerm. ent to the candidate.

• This candidate will registers their detials.

COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram,. A sophisticated modeling tool can easily convert a collaboration diagram into a
sequence diagram and the vice versa. A collaboration diagram resembles a flowchart that
portrays the roles, functionality and behavior of individual objects as well as the overall
operation of the system in real time

COLLABRATION DIAGRAM FOR LOGIN

6: login again

1: enter the user name

2: enter the password
3: submit
candidate login

5: incorrect username or pass word

4: verification process

database
COLLABRATION DIAGRAM FOR PAPER SUBMISSION

1: submit the paper

4: revised and camera ready paper submission
candidat submit
e

5: registration
paper confirmation details
2: review the paper

reviewer dataebas

DOCUMENTATION OF COLLABRATION DIAGRAM

LOGIN
This collaboration diagram is to show how the applicant login in the conference
system. Here the sequence is numbered according to the flow of execution.
PAPER SUBMISSION
This collaboration diagram is to show the submitting paper process of the candidate for
the conference. The flow of execution of this selection process is represented using the numbers.

STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round box,
which may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
 login

submit the
paper

review
the paper

sending paper
confirmation
details

submit revised
and camera ready
paper

registration

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behaviour of the system.
• First state is login where the candidate login to the conference system.
• The next state is submitting the paper .
• Then review the paper if it is selected the process will continue..
• The candidate should submit revised and camera ready paper.
• Then registration process will be carried out.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-step
workflows of components in a system. An activity diagram shows the overall flow of control.
An activity is shown as an rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in recruitment system.
• First the candidate login to the database.
• Then the candidate should submit the paper.
• If it is selected the acknowledgement will send to the candidate.
• After submitting revised paper the registration proces will be done.

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies are
represented by communication association.
 DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show "the allocation of
artifacts to nodes according to the Deployments defined between them. It is represented by 3-

dimensional box. Dependencies are represented by communication association.

conference
management system

candidate1 reviewer1 database1

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the conference management system
which is the main part and the devices are the candidate, appear for do conference , reviewer
will reviews paper , database will store all details which are the some of the main activities
performed in the system.

RESULT:-
Thus the project to develop conference management system using Rational Rose Software and
to implement the project in Visual Basic is done successfully.
Thus the project to develop conference management system using Rational Rose
Software and to implement the project in Visual Basic is done successfully.