Limited Offer Get 25% off — use code BESTW25
No AI No Plagiarism On-Time Delivery Free Revisions
Claim Now

Software Requirements Specification

Software Requirements Specification

for

<Assignment Allocator>

Version 1.0 approved

Prepared by <Saksham Sharma, Yashwant Reddy Katpally, Chakradhar Reddy Devarinti>

<Reddy’s>

<06/06/2020>

Table of Contents

Table of Contents ii

3. Specific System Requirements 7

3.1 Login 7

3.2 Submissions and grades 9

Appendix B: Analysis Models 17

Appendix C: Issues List 19

SPECIFIC SYSTEM REQUIREMENTS

USE CASE: LOGIN

Actors: The users (students/staff members/coordinators) who want to access the system are the actors in this use case.

Trigger: The user wants to login to access the system.

Type: Primary, essential

Description: The user wants to login into the System to access the home screen of the System. The System would ask for the Login Credentials from the user to allow him to access the system.

Pre-conditions: The user must have their student/staff ID number and password. The user should also have registered him/her in the system.

Process:

  1. The user opens the site to access the system.
  2. The system chooses to login by entering username and password.
  3. The system asks the user to enter the username and password.
  4. The user enters the username and password.
  5. The system verifies the username and password (or student/staff ID).
  6. The system gives access to the user if the login details are correct.
  7. The system records the date and time of login.

Variations:

  • 2a. User chooses to sign up
  1. The system asks the user to enter Student/staff Id.
  2. The system asks the user to set user name and password.
  3. The use case continues at step 5.
  • 2b. User chooses to login through registered email.
  1. The user enters registered email.
  2. The system sends a one-time password.
  3. The user enters the password.
  4. The use case continues at step 5.
  • 2c. User clicks on the forgot password option.
  1. The system asks the user to enter student/staff ID.
  2. The use case continues at step 5.
  • 5a. Wrong details entered.
  1. The system displays an error.
  2. The use case continues at step 3.

Figure 1 Data flow diagram for the Use Case: Login

USE CASE: SUBMISSION AND GRADES

Actors: The students who want to submit their work or the students who have already submitted their works.

Trigger: The students wants to submit his work or wants to access his grades

Type: Primary, essential

Description: The student wants to submit his/her work for evaluation. The student gets grades and feedback for his/her work.

Preconditions: The student must make submissions before the deadline.

Process:

  1. The student submits his/her work for evaluation.
  2. The system makes a plagiarism check for the work.
  3. The system notes the date and time of submission.
  4. The system sends a conformation email to the student who submitted the work.
  5. The system automatically displays the grades and feedback as soon as they are entered by the coordinator.

Variations:

  • 1a. Submission is an unacceptable format.
  1. The student submits the work which is an unacceptable format.
  2. The system displays an error message.
  • 2a. High plagiarism score.
  1. The plagiarism score for the work submitted by the student is above the acceptable score.
  2. The system displays an error message.

Extends: Use Case: Plagiarism Check

Figure 2: Data flow diagram for the Use Case: Submissions and Grades

The post Software Requirements Specification appeared first on My Assignment Online.

Plagiarism Free Assignment Help

Expert Help With This Assignment — On Your Terms

Native UK, USA & Australia writers Deadline from 3 hours 100% Plagiarism-Free — Turnitin included Unlimited free revisions Free to submit — compare quotes
Scroll to Top