In: Computer Science
The following is a narrative description of the business process of a conference with regards to the submitting, reviewing and accepting papers.
The author completes an online form that requests the user to input author name, correspondence address, email and title of paper. The system validates this data and if correct, asks the author to submit the paper. The author then browses to find the correct paper on their system and submits it. Once received and stored, the system returns to the author a reference number for the paper. Authors may submit as many papers as they like to be considered for acceptance to the conference up until the deadline date for submissions. Papers are allocated to referees for assessment. They review each paper and submit to the system their decision. Once the programme organiser has agreed with the decisions, authors are informed by email. Accepted papers are then schedule to be delivered at a conference. This involves allocating a date, time and place for the presentation of the paper.
Analyse the above text to do the following:
Actors identified are:
1. Author
2. Referees
3. programme organiser
4. System (Admin)
Author
Author is an external type user. Author will interact with the system for present a paper. Author is a primary user. So he has high priority. Author can do below activities, Author can register, Submit his papers, Receive reference number Present the paper in the conference.
Referees
Referees are reviewers in the system. They can review the paper submitted by the author. The system allocates the paper to referees. They can submit their decision about the paper to the system.
Programme organiser
Program organiser will verify the decision made by referees. Accept or reject the paper. Inform the author about the decision. Schedule the conference for deliver the paper. Allocate date, time and place
System (Admin)
Main user of the application.So have high priority. Admin verify the author. allocate paper to referee, give reference number to author etc.
Usecase diagram
Usecases:
Usecase1:
Usecase Description: Submit the paper
Actor: Author, System (Admin)
Pre-condition: System must be connected to the network.
Post-Condition: Successfully submit the paper and get a reference number
Main Scenario:
1. Author enter name, address, email, title of paper
2. Click on submit
3. System verify
4. Display page to submit the paper
5. Use browse the correct paper
6. Display a reference number
Alternate Scenario:
1. Author enter name, address, email, title of paper
2. Click on submit
3. System verify
4. Display Incorrect data please enter correct data
Use Case 2:
Usecase Description: Verify the paper
Actor: System (Admin), referee
Pre-condition: System must be connected to the network and paper available for review.
Post-Condition: Successfully submit the decision
Main Scenario:
1. Admin select a paper
2. Search for a referee
3. Allocate the paper
4. Referee review paper
5. Enter the decision
6. Enter submit
Alternate Scenario:
1. Admin select a paper
2. Search for a referee
3. Display Message shows “No referee available, Please try again”
Usecase 3:
Usecase Description: Final Result preparation
Actor: System (Admin), Programme organiser
Pre-condition: System must be connected to the network and paper available for result.
Post-Condition: Successfully submit result and schedule the conference
Main Scenario:
1. Select the paper
2. View decision
3. Click Accept button
4. Open the page for schedule and mail
5. Send mail to author
6. Allocate time, place and date.
Alternate Scenario:
1. Select the paper
2. View decision
3. Click Reject button
4. Send mail to author