User Guide

User Manual:

Open the PDF directly: View PDF PDF.
Page Count: 4

User Guide
1. Configuration
1.1 Environment
This software is developed using Microsoft Visual Studio 2015 with local database file generated by
VS.
1.2 Setting
In the archived file, click CMS.sln to load the whole program into VS environment, then start to run
it.
If there’s an error about entity framework connect to database, please follow the instructions
below:
1. In Visual Studio, select Tools > Extensions and Updates
2. In the Extensions and Updates pop-up box, select Installed > Updates
3. Highlight Microsoft SQL Server Update for database... and click the Update button. If
Microsoft SQL Server Update for database... is not listed, you can download
SSDTSetup.exe from https://msdn.microsoft.com/en-us/mt186501.
4. Your default Web browser will prompt a download of SSDTSetup.exe
5. In your Downloads folder, run SSDT Setup
6. Follow the prompts of the installer
Current user information for logging in:
User Name
Password
Role
Conference
Clyne
fc
Admin
N/A
Jason
Ja
Chair
N/A
Chris
ch
Reviewer
InnovateBopitech2017
Lily
li
Author
InnovateBopitech2017
Noting: if register for new user, chair’s registration must be approved by admin and reviewer’s
registration must be approved by chair
1.3 Noting
Due to Windows Form Application’s mechanism on using local database file, at design-time,
CMS\Database\CMSDB.mdf is used by the data tools. At run-time, the app will be using the
database under the output folder. As a result of the copy, many people have the impression that the
app did not save the data to the database file. So it is normal that you use the app to save some new
data and check it in VS design model’s database finding there’s no changes, the actual database
used at run time is under bin\Debug\Database.
2. Functionalities
1. General Functions
1) Registration
2) Log In
3) Log Out
4) Account Setting
2. Admin Functions
1) Retrieve conferences’ Information
2) Retrieve users’ Information
3) Retrieve papers’ information
3. Chair Functions
1) Retrieve conference’s Information
2) Launch conference
3) Assign reviewers to a paper
4) Make final decision and give feedback to a paper
4. Reviewer Functions
1) Retrieve conference information
2) Review papers
5. Author Functions
1) Retrieve conference information
2) Submit papers
3) Check paper status
3. Description
3.1 General Functions
3.1.1 Registration
Registration is implemented by providing user interface to create a new user stored in
the database.
3.1.2 Log In
Log In is implemented by comparing log in input with data in database, if data exists
user can log in. Plus, the main system page will generate different interface of different
functions according to user’s role.
3.1.3 Log Out
Log out is implemented by closing current page and returning to a new login page
3.1.4 Account Setting
Account Setting is implemented by retrieving user’s information, and providing interface
to change those information
3.2 Admin Functions
3.2.1 Retrieve conferences’ Information
Retrieve conferences’ information is implemented by retrieving information of all
conferences in the database.
3.2.2 Retrieve users’ Information
Retrieve users’ information is implemented by retrieving information of all users in the
database.
3.2.3 Retrieve papers’ information
Retrieve papers’ information is implemented by retrieving information of all papers in
the database.
3.3 Chair Functions
3.3.1 Retrieve conference’s Information
Retrieve conference’s Information is implemented by retrieving information of all
conferences launched by current chair.
3.3.2 Launch conference
Launch conference is implemented by providing chair an interface to create a new
conference stored in database.
3.3.3 Assign reviewers to a paper
Assign reviewers to a paper is implemented by retrieving information of papers
submitted to the conference of this chair, retrieving information of all reviewers in each
conference and providing an interface for chair to give the review permission to a
reviewer.
3.3.4 Make final decision and give feedback to a paper
Make final decision and give feedback to a paper is implemented by retrieving
information of papers submitted to the conference of this chair with its review
information, and providing chair an interface to write feedbacks for each paper and
make decision on whether to accept or not.
3.4 Reviewer Functions
3.4.1 Retrieve conference information
Retrieve conference information is implemented by retrieving members and submitted
papers of current conference.
3.4.2 Review papers
Review papers is implemented by retrieving papers that current reviewer has been
assigned to review, and providing an interface for the reviewer to rate papers.
3.5 Author Functions
3.5.1 Retrieve conference information
Retrieve conference information is implemented by retrieving members and submitted
papers of current conference.
3.5.2 Submit papers
Submit papers is implemented by providing author an interface to submit a new paper
to the conference. An author can submit as many papers as he/she want.
3.5.3 Check paper status
Check paper status is implemented by retrieving status information of the papers that
current user has submitted.
4 Important features
4.1 Request validation
This system has request validation function, under which mechanism chairs’ registration need to be
approved by admin and reviewers’ registration need to be approved by the chair, otherwise
unauthorized chairs and reviewers cannot log into the system.
4.2 Sending email automatically
Email will be sent automatically by the system on following scenario:
1. When users (chairs or reviewers) registration request has been approved, an email contains the
message of the success of registration will be sent.
2. When the chair has given feedbacks and made a final decision to a paper, an email contains
feedback messages will be sent to the author of the paper.
Noting: Sending email function is commented due to there’s no valid email address in database. If want
to use this function, please add valid email address in database, or register a new user with valid email
address, then uncomment following code:
Send email when the registration has been approved: In “RequestValidate.cs”, line 140 and line
149
Send email when chair make final decision: In “FinalDecision.cs”, line 215
4.3 Basic validation
Basic input validation has been added to the system on every input scenario, providing basic protection
for the system on the input level.
5 Extra credit
This system is implemented using Windows Form Application structure, which provides users with
graphic interface to interact with.

Navigation menu