0% found this document useful (0 votes)
85 views4 pages

Requirements Specification 1. Requirements Elicitation

This document outlines the functional and non-functional requirements for a book exchange application. It lists 11 functional requirements relating to admin login/view, student registration/login, purchasing/selling books, lending books, fines, online payment, and viewing/modifying personal details. It also lists non-functional requirements around performance (reasonable data access speed, secure site access under 3 seconds), security (secure storage of transactions and user information), safety (data backups and ability to run in safe mode if failures occur), and legal/regulatory compliance (no long term storage of customer account details online).

Uploaded by

Waqar Sheikh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
85 views4 pages

Requirements Specification 1. Requirements Elicitation

This document outlines the functional and non-functional requirements for a book exchange application. It lists 11 functional requirements relating to admin login/view, student registration/login, purchasing/selling books, lending books, fines, online payment, and viewing/modifying personal details. It also lists non-functional requirements around performance (reasonable data access speed, secure site access under 3 seconds), security (secure storage of transactions and user information), safety (data backups and ability to run in safe mode if failures occur), and legal/regulatory compliance (no long term storage of customer account details online).

Uploaded by

Waqar Sheikh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

REQUIREMENTS SPECIFICATION

1. Requirements Elicitation

1.1 Functional Requirements

FR 01:Admin Login
FR 1.1: The admin press the admin button from the home page to redirect to the login section.

FR 1.2: The admin will enter the user ID, password and login the system successfully.

FR 1.3: If the admin entered the wrong password, the system will display the Dialog box and ask
again for the password.

FR 1.4: The admin will enter the password again and login the system if the given password matches
with the admin credentials.

FR 02: Admin View


FR 2.1: After successful login through Admin account, the student will redirect to the admin view
page.

FR 2.2: The admin will add more admins and give them access to admin accounts.

FR 2.3: The admin will go through all sellers' books and he will select the category of books then the
system will show the all books of selected category.

FR 03: Student Registration


FR 3.1: The student will open the application.

FR 3.2: The student will be redirected to the registration page if he is not registered already.

FR 3.3: The student will enter its required information

FR 3.4: The user will then be prompted with the message that he registered successfully.

FR 04: Student Login


FR 4.1: The student will open the application and press the admin interface.

FR 4.2: The student will enter the given password and user ID to login to the application.

FR 4.3: If the student enters the wrong password the application ask for the wrong password and try
again.

FR 4.4: Then the system will be redirected to seller account or buyer account depending upon which
login account chosen.

FR 05: Purchase
FR 5.1: The student will search the book by name or by category.

FR 5.2:The student will select the books which he wants to purchase.

FR 5.3:If the book is in hard form then the student will contact the seller and purchase it by paying its
price.

FR 5.4: But if the book is pdf form then payment method is online .

FR 06: Seller
FR 6.1: After successful login the student will see the form login as seller.

FR 6.2: The student will login with a seller account if he has already his account otherwise will
register.

FR 6.3: The student will add the book by adding its information e.g Title, Author, Price , Book#,
Published_Date, Category etc..

FR 6.4: The student will see the notification form the other students who want to purchase and sell it
to them.

FR 6.5: The student will update the book information and also delete the book after selling it.

FR 07: Lend a Book


FR 7.1: The student will search books by name or by category .

FR 7.2: The student will select the book or books which he wants to lend .

FR 7.3:The student will contact the owner of the book or books and lend it .

FR 7.4: The student will return the lended book within a due date and pay its rent.

FR 08: Fine
FR 8.1: After lending the book the student will return the lended book within a due date and pay its
rent.
FR 8.2: The student will not be able to return it within a due date.

FR 8.3:The system will send him notification of fine.

FR 8.4: If the student will not return the book the fine amount increases every day by 10 rupees per
book.

FR 09: Online Payment


FR 9.1: If the the selected book is in pdf form then system shall redirect the student to the payment

page.

FR 9.2: The student will select the payment option.e.g jazzcash, easypaisa.

FR 9.3:The student will enter the selected amount detail , the amount he wants to pay and submit it.

FR 9.4: The system shall show the confirmation message.

FR 10: See and Modify Personal Details:


FR 10.1: The student will be enabled to see its personal details.

FR 10.2: The system shall allow the student to change its old password.

FR 10.3: The student will enter its old password and new password and submit it.

FR 10.4: The student will also be able to modify its personal information.

FR 10.5: The system shall not allow the student to register more then one account though one email.

FR 11 Log Out:

FR 11.1: The system shall allow the student or admin to logout after completing his/her job

FR 11.2: The system shall return to the login page.


1.1 Non-Functional Requirements
NFR 1: Performance Requirements
NFR 1.1: There needs to be reasonable data access speed on the student side as well as the admin side
of the application.

NFR 1.2:Access to the secure site must be no longer than 3 sec delay.

NFR 2: Security Requirements


NFR 2.1: All transactions must be stored securely

NFR 2.2:Physical storage locations of the data for transactions must be secure

NFR 2.3:All information gained from the end users that is processed must be kept secure.

Safety Requirements ;
NFR 3.1: Backup, recovery & business continuity banks should ensure adequate backup of data as
may be required by their operations..

NFR 3.2: In the event of parts of the system failing the system must be able to be run in a safe mode.

Legal Regulatory;
NFR 3.1: There is a legal requirement that customer account details must not be stored online.

NFR 3.2: But the system shall keeps payment details for some years.

You might also like