Requirements Specification Document

APRIL, 2011

Online books and journals

Saurabh Singh
301/CO/07

SOFTWARE ENGINEERING LAB

i
 Table of Contents
SOFTWARE ENGINEERING LAB........................................................................................................................i
Table of Contents.....................................................................................................................................................ii
Table of Figures......................................................................................................................................................iii
3.0. Requirement specifications...............................................................................................................................9
3.1. External interface specifications...................................................................................................................9
3.2. Functional Requirements..............................................................................................................................9
3.2.1. Access User Home Page........................................................................................................................9
3.2.2. Register................................................................................................................................................10
3.2.3. Login....................................................................................................................................................11
3.2.4 Make a purchase...................................................................................................................................12
3.2.5. Make a submission...............................................................................................................................13
3.2.6. Submit Review.....................................................................................................................................13
4.0. Index:..............................................................................................................................................................15

ii
 Table of Figures

Figure 1 System Design...........................................................................................................................................2

Figure 2 Access Home Page...................................................................................................................................3
Figure 3 ...................................................................................................................................................................4
Figure 4 User makes a purchase..............................................................................................................................6
Figure 5 Author submitting a new manuscript........................................................................................................7
Figure 7 User Selects Submit review ...........……………………… 11

iii
1.0. Purpose
The purpose of this requirement specification document is to elicit the requirement domain of an
Online books and Journals system through a detailed explanation of various functions involved.

1.1. Introduction
This Software Requirements Specification provides a complete description of all the functions and
specifications of an Online books and journals system that caters to needs of people looking for
online books, technical papers, journals etc.

1.2. Scope
The Online books and journals system is designed to present the option of buying books and journals
to a distant user through internet. The system stores a database of the manuscripts available in form of
books, research papers ,white papers and thesis.

1.3. Glossary
Term Definition

Html Hyper text markup language

IEEE Institute of Electrical and Electronic Engineers
QA Quality assurance
RSD Requirement Specification Document
SEI Software Engineering Institute, Pittsburgh, Pa
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.4. References
[IEEE] The applicable IEEE standards are published in “IEEE Standards Collection,”
2001 edition.

The principal source of textbook material is “Software Engineering: by Sangeeta Sabharwal

1.5. Document overview

The remainder of this document is two chapters, the first providing a full description of the project for
all the functions performed by the system through use case narratives and use case diagrams. The
final chapter concerns details of each of the system functions and actions in full taking into account
functional and non functional aspects associated with the system.

1
2.0. Overall description
The Online manuscripts system encompasses numerous files and information about the books ,
research papers ,journals etc that are available for sale through online transaction. This system will be
completely web-based, linking the user and remote web server housing the mentioned information
from a standard web browser. An Internet connection is necessary to access the system.

2.1. System environment

Figure 1 System Design

The manuscripts web site will be operated from a server. When a User connects to the Server,the
Server will then interact with the Manuscripts Database and consequently the transaction will take
place, which allows the system to transfer data to and from a database.

2.2. Functional requirements definitions

Functional Requirements are those that refer to the functionality of the system, i.e., 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.

2.3. Use cases

The system will consist of Online books and journals Home page with five selections.
The first selection is to register a user . The registration will require taking personal information of
the user followed by assignment of an account to the concerned person for future association with the
system. The user will be asked to give information concerning their address details, contact
information and identity proofs. This information will be retained on the server and an e-mail will be
sent to the designated user.

The second selection is Login section. A registered user can log into the system by providing his or
her username and password. By logging into one’s personal account, user is entitled to privileged
access to the system. He can view credentials, previous history of transactions or can make new
purchase etc.

The third selection is to Book Mart section. Any visitor of the site can visit this section to gather
information on the manuscripts available. There are three choices on this page. One choice is to
search a particular book by providing its title and author name. The second selection of the Book mart
page is to recent manuscripts made available for sale. This selection will enlist all the manuscripts

2
that were added recently to the database. The third selection is for making a purchase for which user
places the order and provides credit card details.

The fourth selection is to search for papers available in form of white papers, thesis or research
articles. An abstract of the searched item will be put up on display to provide an insight into the
contents of the paper. But the paper in complete will only be accessed after making a purchase.

The fifth selection will be for the administrator of the system who is entitled to update the
information about books and papers available and handling any of the registered users information.
All pages will return the Home Page

2.3.1. Use Case: Access Home Page

Figure 2 Access Home Page

Brief Description:

The System Web Server is waiting on a user to connect.

Initial step-by-step description:

For this use case to be initiated, the user must be connected to the Internet and connected to the Web
Server.
The user enters the web address of the system and reaches the online books and journals home page.

Reference SRS 3.2.1

3
2.3.2. Use Case: User Chooses New registration

Figure 3

Brief Description:
The user chooses to register with the system .

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the System’s Home
Page.
The User selects the “New Registration” link.

The Server returns the registration form.

The User fills in the form.

The User clicks submit.

The Server retains information in the database and designated user will be notified.

The Server returns the User to the User Home Page.

Reference SRS 3.2.2

4
2.3.3.Use Case: User logs in the system
Brief Description:
The user chooses to log into account registered with the system .

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the System’s Home
Page.

The User selects the “Login” link.

The Server returns the Login form.

The User enters username and his/her password

The Server searches the User Database for the User name and password.

The Server returns the User’s data if the password matches.

If the password does not match the Server returns an error message and returns the User to the
previous page.

The User changes the appropriate fields and clicks submit.

The Server returns the User to the CIS Userni Home Page when user clicks on “logout”.

Reference SRS 3.2.3

5
2.3.4 Use Case: Make a purchase

Figure 4 User makes a purchase

Brief Description:
The User chooses to buy manuscripts.

Initial step-by-step description.

For this use case to be initiated the User must be connected to the Internet and on the Book mart page
or personal account page.

The User selects the “Buy books” link.

The Server returns the “Enter Details of Book Form.”

The User fills in the form.

The User clicks submit.

The Server checks to see if all required fields contain data .

If all required entries find a match in the server database, the Server makes necessary calculations to
provide the bill to the user asking for credit card information.

The User makes payment by providing credit card details.

If a required filed is empty the Server returns the form to the User with a message.

The Server updates the database after transaction.

The Server returns the User to the Home Page.

Reference: SRS 3.2.4

6
2.3.5. Use Case: User(Author) making a submission

Figure 5 Author submitting a new manuscript

Brief Description:
The User chooses to submit a new manuscript .

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the Personal
account page.

The User chooses the “Make a submission” option.

The Server presents the User with a form.

The User fills in the details of new submission.

The Server checks to see if all required fields contain data .

If all required fields contain data, the Server returns a successful submission message to the user.

If a required filed is empty the Server returns the form to the User with a message.

The Server updates the database after transaction.

The Server returns the User to the Home Page.

Reference: SRS 3.2.5

7
2.3.6. Use Case: Reviewer submitting a review

Brief Description:
The User chooses to submit a new review .

Initial step-by-step description:

For this use case to be initiated the User must be connected to the Internet and on the Personal
account page.

The User chooses the “Make a review” option.

The Server presents the User with a form.

The User fills in the details of new submission.

The Server checks to see if all required fields contain data .

If all required fields contain data, the Server returns a successful submission message to the user.

If a required filed is empty the Server returns the form to the User with a message.

The Server updates the database after transaction.

The Server returns the User to the Home Page as user clicks on “logout”.

Reference: SRS 3.2.6

8
2.4. Non-functional requirements
There are requirements that are not functional in nature. Specifically, these are the constraints the
system must work within.
The web site must be compatible with different web browsers. And the server which holds the entire
database should be highly efficient.

3.0. Requirement specifications

3.1. External interface specifications
The administrator of the system needs to be well versed with database concepts.The database
should be properly organized to minimize redundancy. Also the user or customer needs to
have the basic knowledge of operating a website.

3.2. Functional Requirements

3.2.1. Access User Home Page

Use Case Name: Access User Home Page

Priority Essential
Trigger Menu selection
Precondition User is connected to the Internet
Basic Path 1. Web Browser links the User to the
Server.
2. The Server presents the User with the
User Home Page.
Alternate Path N/A
Postcondition The User is on the User Home Page
Exception Path If there is a connection failure the Server
returns to the wait state
Other
Reference SRS 2.3.1

9
3.2.2. Register
Use Case Name: Register
Priority Essential
Trigger Selects
Precondition The User is connected to the Internet and on
the Home Page
Basic Path 1. The Server presents the User with a form.
2. The User fills in the form and click
submit
3. The Server checks to see if all required
fields are not empty.
4. If the required fields are not empty, the
Server creates a new record in the User
Database.
5. If any of the required fields are empty,
the Server returns a message and returns
the User to the Survey form.
6. The Server returns the User to the User
Home Page
Alternate Path N/A
Postcondition The survey record is created in the User
Database.
Exception Path 1. If the connection is terminated before the
form is submitted, the fields are all
cleared and the Server is returned to the
wait state.
Other
Reference: SRS 2.3.2

10
3.2.3. Login
Use Case Name: Login
Priority Essential
Trigger Menu selection
Precondition The User must be connected to the Internet
and on the home page.
Basic Path 1. The User clicks on Login.
2. The Server returns a form.
3. The Server queries the User with
username and requesting their password.
4. If the password does not match the
Server returns a message and allows the
User to try again.
5. If after 3 tries the password does not
match, the Server will return a message
telling the User to contact the
administrator.
6. If the password matches go to 8.
7. The Server returns the login form and a
message to reenter the details and click
submit.
8. The Server lets the user enter his
account.
Alternate Path N/A
Postcondition The user is logged into his personal account
already registered with the system.
Exception Path 1. If the connection is terminated before the
form is submitted, the fields are cleared
and the Server is returned to the wait
state.
2. If the connection is terminated after the
form is submitted, but before the User is
returned to the Home Page, the record is
created in the Database.
Other
Reference: SRS 2.3.3

11
3.2.4 Make a purchase
Use Case Name: Purchase
Priority Essential
Trigger Menu selection
Precondition The User must be connected to the Internet
and on the personal account Page or book
mart page.
Basic Path 1. The User selects the “Buy books” link.
2. The Server returns the “Enter Details of
Book Form.”
3. The User fills in the form and clicks
submit.
4. The Server checks to see if all required
fields contain data .
5. If all required entries find a match in the
server database, the Server makes
necessary calculations to provide the bill
to the user asking for credit card
information.
6. The User makes payment by providing
credit card details.
7. If a required filed is empty the Server
returns the form to the User with a
message.
8. The Server updates the database after
transaction.
9. The Server returns the User to the Home
Page as user clicks on logout.

Alternate Path If the required fields are left unmarked the

Server returns to home page.
Postcondition The record in the Database has been updated
and the User is returned to the Home Page.
Exception Path 1. If the connection is terminated before the
form is submitted, the fields are cleared
and the Server is returned to the wait
state.
2. If the connection is terminated after the
form is submitted, but before the User is
returned to the Home Page, the record in
Database is updated and the Server is
returned to the wait state
Other
Reference: SRS 2.3.4

12
3.2.5. Make a submission
Use Case Name: Make a submission
Priority Essential
Trigger Menu selection
Precondition The User is connected to the Internet and on
the Personal account Home Page.
Basic Path 1. The User chooses the “Make a
submission” option.

2. The Server presents the User with a

form.

3. The User fills in the details of new

submission.

4. The Server checks to see if all required

fields contain data .

5. If all required fields contain data, the

Server returns a successful submission
message to the user.

6. If a required filed is empty the Server

returns the form to the User with a
message.
7. The Server updates the database after
transaction.
8. The Server returns the User to the
Personal Home Page.
Alternate Path N/A
Postcondition The User receives the information on
submission and is returned to the Personal
Home Page
Exception Path 1. If the connection is terminated before the
information is returned, the Server is
returned to the wait state.
2. If the connection is terminated after the
information is returned, the database is
updated and Server is returned to the wait
state
Other
Reference: SRS 2.3.5

3.2.6. Submit Review

Use Case Name: Submit review

13
Priority Essential
Trigger Menu selection
Precondition The User is connected to the Internet and on
the Personal account Home Page.
Basic Path 1. The User chooses the “Submit
review” option.

2. The Server presents the User with a

form.

3. The User fills in the details of new

submission.

4. The Server checks to see if all

required fields contain data .

5. If all required fields contain data, the

Server returns a successful
submission message to the user.

6. If a required filed is empty the Server

returns the form to the User with a
message.
7. The Server updates the database after
transaction.
8. The Server returns the User to the
Personal Home Page.
Alternate Path N/A
Postcondition The User receives the information on
submission and is returned to the Personal
Home Page
Exception Path 1. If the connection is terminated
before the information is returned,
the Server is returned to the wait
state.
2. If the connection is terminated
after the information is returned,
the database is updated and Server
is returned to the wait state
Other
Reference: SRS 2.3.6

14
4.0. Index:

15