Professional Documents
Culture Documents
Version 1.4
May 22, 2011
Amardeep
Anjeet
Rajshekhar
Ihsan
Sushmit
Revision History
ii
Table of Contents
Table of Contents ..............................................................................................................................................iii
Table of Figures .................................................................................................................................................iv
1.
Introduction ................................................................................................................................................. 2
1.1.
Purpose ..................................................................................................................................................... 2
1.2.
Intended Audience And Reading Suggestions ......................................................................................... 2
1.3.
Scope ........................................................................................................................................................ 2
1.4.
Glossary .................................................................................................................................................... 4
1.5.
References ................................................................................................................................................ 4
1.6.
Document overview.................................................................................................................................. 4
2.
Overall description..................................................................................................................................... 6
2.1.
System environment ................................................................................................................................. 6
2.2.
Functional requirements definitions ......................................................................................................... 6
2.3.
Use cases .................................................................................................................................................. 7
2.3.1.
Use Cases related to Administrators.................................................................................................. 8
2.3.1.1.
Use Case: Admin Login ............................................................................................................. 8
2.3.1.2.
Use Case: Admin Adds Book Into SHAISTA Database............................................................ 9
2.3.1.3.
Use Case: Admin Removes Book From SHAISTA Database ................................................. 10
2.3.1.4.
Use Case: Admin Updates Book Details Into SHAISTA Database......................................... 11
2.3.1.5.
Use Case: Admin Adds Customer/Vendor Details Into SHAISTA Database ......................... 12
2.3.1.6.
Use Case: Admin Removes Or De-registers Customer/Vendor............................................... 12
2.3.1.7.
Use Case: Admin Updates Details Of Customer/Vendor Into SHAISTA Database................ 12
2.3.1.8.
Use Case: Admin Manually Validates Vendor/Vendors Book Registration And Approves
The Registration ........................................................................................................................................ 12
2.3.2.
Use Cases related to Customers ...................................................................................................... 13
2.3.2.1.
Use Case: Customer Registers For A Secure Login Account .................................................. 13
2.3.2.2.
Use Case: Customer Login ....................................................................................................... 14
2.3.2.3.
Use Case: Customer Wants to De-registers Customer/Vendor ................................................ 14
2.3.2.4.
Use Case: Customer Wants To Updates His Details In SHAISTA Database .......................... 14
2.3.2.5.
Use Case: Customer Searches For A Book .............................................................................. 14
2.3.2.6.
Use Case: Customer Want To Read A Few Pages Of A book ................................................. 15
2.3.3.
Use Cases related to Vendors .......................................................................................................... 16
2.4.
Non-functional requirements.................................................................................................................. 16
iii
SRS 05/27/11
Table of Figures
Figure 1 System Design .......................................................................................................................................... 6
Figure 2 Admin Login (Success) ............................................................................................................................ 8
Figure 3 Admin adds book details........................................................................................................................... 9
iv
SRS 05/27/11
1. Introduction
1.1. Purpose
The SHAISTA Online Bookstore is a web application, which provides a single point of
Vendors (or book publishers): to make available the details of their books and
The expected audience of this document is the developer, SHAISTA Online Bookstore
administrators, SHAISTA Online Bookstore employees who work on this system. A part of
this document can be used to prepare the user guide that can be provided to the customers
1.3. Scope
The SHAISTA Online Bookstore Web Accessible Books Database is designed to run on
o Login
o Add a book
o Remove a book
2
SRS 05/27/11
Allow vendors to
o Login
o De-register
o Register a book
o De-register a book
NOTE: Here book details include info about the book (like Title, author, category
etc), number of books available, listed price, selling price (after discount, if any),
Allow customers to
o Login
o De-register
3
SRS 05/27/11
o Track orders
1.4. Glossary
Term Definition
CI Configuration Item
Html Hyper text markup language
QA Quality assurance
SCMP Software Configuration Management Plan
SDD Software Design Document
SQAP Software Quality Assurance Plan
SRS Software Requirements Specification
Tbd To be decided
Tbn To be named
Web Site A place on the world wide web
1.5. References
1. The applicable IEEE standards are published in IEEE Standards Collection,
2001 edition.
2. The principal source of textbook material is Software Engineering: An Object-
Oriented Perspective by Eric J. Bruade (Wiley 2001).
functional description of the project SHAISTA Online Bookstore. The Chapter-3 concerns
4
SRS 05/27/11
details of each of the system functions and actions in full for the software developers
5
SRS 05/27/11
2. Overall description
The SHAISTA Online Bookstore encompasses numerous files and information from
the Database called SHAISTA Database. This system will be completely web-based,
linking to SHAISTA Database and the remote web server from a standard web browser. An
The user connects to the SHAISTA Online Bookstore Web Server, to interact with the
SHAISTA Database through BDE, which allows the Windows type program to transfer data
what services it will provide to the user. Nonfunctional (supplementary) requirements pertain
to other information needed to produce the correct system and are detailed separately.
6
SRS 05/27/11
following selections:
1. Login Section:
a. Login into the system with their registered user id and password. If the user
provides correct login credentials, then the system will display a web page
similar to the home page except the login section. If the login credentials are
not correct, the system will display the home page with an error message that
b. Register a new user: With this selection, the system opens a webpage where a
user can enter his details like, Name, DOB, Gender, email id, phone, address
and select a user id, password and password recovery phrase to register. On
and the user account can become active once the user validates the email id.
c. Reset password of a registered user: With this selection, the system opens a
webpage where the user is asked to enter his user id and password recovery
phrase. If the details are correct, it displays that the password has been reset
and sent to email id, else it specifies that the details are incorrect.
2. Search Section: Allow users to search for books based on various parameters such as
category, it lists out the books in the order of latest book in the system.
7
SRS 05/27/11
4. New Releases Section: This section lists the hot selling newly released books. When
a book is clicked, it displays the entire details of the book plus an option to preview
Brief description:
The Admin wants to login into the system.
1. The Admin enters his user id and password in the login section and clicks on login
button.
2. The system validates the login credentials entered by the Admin against the information
stored in the SHAISTA Database.
8
SRS 05/27/11
3. If the credentials are correct, the system displays the Admin home page.
4. If the credentials do not match, the system returns a failure message on the home page of
SHAISTA Online Bookstore.
2.3.1.2.
UseCaseDiagram5.svg
Use Case: Admin Adds Book Into SHAISTA Database 5/27/11 1:13 AM
<<include>>
Enter Details Of The Book To Add Validate Book Details
Admin <<include>>
<<include>>
Update Book Details Into SHAISTA Database
Brief description:
The Admin wants to add book details into SHAISTA Database.
1. The Admin selects the Add Book option, which displays a webpage with a form to fill in
the book details to be added.
2. The Admin enters the book details and selects the submit option.
3. The system validates the book details entered by the Admin against the information
stored in the SHAISTA Database.
4. If similar book with identical information is available, then it will update the existing
record by increasing the number of books available else it will create a new record for the
book details entered by Admin.
file:///Users/Shared/StudyMaterials/Manipal/Semester-1/CSE601_ObjectOrientedSystems/Assignment/UseCaseDiagrams/UseCaseDiagram5.svg Page 1 of 1
SRS 05/27/11
5. Once the book details are updated into the SHAISTA Database, a webpage confirming
the details of the book that was added is displayed.
<<include>>
Enter Book Details For Deletion Validate Book Details
<<include>>
<<include>>
Admin Remove Book Details From SHAISTA Database
SHAISTA Database
Admin Removes
Book Details
Brief description:
The Admin wants to remove book details from SHAISTA Database.
1. The Admin selects the Remove Book option, which displays a webpage with a form to
fill in the book details to be removed.
2. The Admin enters the book details and selects the submit option.
3. The system validates the book details entered by the Admin against the information
stored in the SHAISTA Database.
4. If there are no books with the details entered by Admin, then it displays an error message
on the same page.
5. If the book details entered by the Admin exist then it deletes the record or subtracts the
number of books to be deleted.
10
file:///Users/Shared/StudyMaterials/Manipal/Semester-1/CSE601_ObjectOrientedSystems/Assignment/UseCaseDiagrams/UseCaseDiagram6.svg Page 1 of 1
SRS 05/27/11
6. Once the book details are updated into the SHAISTA Database, a webpage confirming
the details of the book that was removed is displayed.
UseCaseDiagram7.svg 5/27/11 1:36 AM
2.3.1.4. Use Case: Admin Updates Book Details Into SHAISTA Database
<<include>>
Enter Book Details To Update Validate Book Details
<<include>>
<<include>>
Admin
Update Book Details Into SHAISTA Database
SHAISTA Database
Admin Updates
Confirmation: Details Of The Book Updated Book Details
Brief description:
The Admin wants to update book details into SHAISTA Database.
1. The Admin selects the Update Book option, which displays a webpage with a form to fill
in the book details to be updated.
2. The Admin enters the book details and selects the submit option.
3. The system validates the book details entered by the Admin against the information
stored in the SHAISTA Database.
4. If there are no books with the details entered by Admin, then it displays an error message
on the same page.
5. If the book details entered by the Admin exist then it updates the details accordingly.
11
file:///Users/Shared/StudyMaterials/Manipal/Semester-1/CSE601_ObjectOrientedSystems/Assignment/UseCaseDiagrams/UseCaseDiagram7.svg Page 1 of 1
SRS 05/27/11
6. Once the book details are updated into the SHAISTA Database, a webpage confirming
the details of the book that was updated is displayed.
This is similar to the section 2.3.1.2 Admin Adds Book Details Into SHAISTA Database
This is similar to the section 2.3.1.3Admin Removes Book Details From SHAISTA
Database
This is similar to the section 2.3.1.4Admin Updates Book Details In SHAISTA Database.
Admin
SHAISTA Database
Brief description:
The Admin Validates the Vendor registration details and approves the registration.
12
SRS 05/27/11
For this use case to be initiated the Admin must be connected to the Internet and should
1. The Admin selects the Validate Vendors option, which loads the webpage with list of
vendor details waiting for approval.
2. The Admin verifies each vendor details and approves the registration if the details are
found to be authentic.
<<include>>
SHAISTA Database
Confirmation: User Customer Accounted Crrated
Brief description:
The Customer wants to register for a secure account on SHAISTA Online Bookstore.
2. The system displays a webpage where the customer can enter the details required to
create an account.
3. The system validates the account details to be created against the information stored in
the SHAISTA Database.
13
SRS 05/27/11
4. If the details are not already present in SHAISTA Database, then the system creates the
customer account by updating the details into SHAISTA Database.
This is similar to the section 2.3.1.4Admin Updates Book Details In SHAISTA Database.
Customer2.svg 5/27/11 4
2.3.2.5. Use Case: Customer Searches For A Book
<<include>>
Customer
SHAISTA Database
Search Engine: Searches For The Book
<<include>>
Customer
Displays The Search Result Searches
For A Book
14
SRS 05/27/11
Brief description:
The Customer wants to search for a book in SHAISTA Online Bookstore.
1. The Customer selects Search Book option from the search section.
2. The system displays a webpage where the customer can enter the details of the book he
wants to search.
3. The system invokes the search engine and displays the results in a new webpage.
Customer3.svg 5/27/
2.3.2.6. Use Case: Customer Want To Read A Few Pages Of A book
Customer <<include>>
SHAISTA Database
Search Engine: Searches For The Book
<<include>>
Customer:
Preview The Selected Book Preview
A Book
Brief description:
The Customer wants to read a few pages of a book in SHAISTA Online Bookstore.
15
SRS 05/27/11
For this use case to be initiated the Customer must be connected to the Internet and
1. The Customer selects Search Book option from the search section.
2. The system displays a webpage where the customer can enter the details of the book he
wants to search.
3. The system invokes the search engine and displays the results in a new webpage.
4. Alongside the results, there will be a option for preview of the book.
5. When the customer selects the preview option, few pages of the respective book are
displayed.
The web site must be compatible with both the Netscape and Internet Explorer web
browsers. This system will have a search engine optimized to give the results within 2 secs.
16