TABLE OF CONTENTS

1.0 Introduction
1.1 Purpose…………………………………………………………………. 2
1.2 Scope of Project…………………………………………………….. 2
2.0 System requirement analysis
2.1 Information gathering
2.1.1 Functional Requirement……………………………. 3
2.1.2 Non Functional Requirement……………………. 4
3.0 System design
3.1 Class Diagram………………………………………………………… 5
3.2 Use Case Diagram………………………………………………….. 6
3.3 Sequence Diagram
3.3.1 Sequence Diagram for Customer………………. 7
3.3.2 Sequence Diagram for Admin……………………. 8
3.4 Collaboration Diagram……………………………………………. 9
3.5 Data Flow Diagram
3.5.1 Level 0 Data Flow Diagram……………………….. 10
3.5.2 Level 1 Data Flow Diagram……………………..... 10
3.5.3 Level 2 Data Flow Diagram……………………….. 11
4.0 Database design
4.1 Data design……………………………………………………………… 13
4.1.1 ER Diagram……………………………………………….. 13
4.2 System Architecture
4.2.1 Architecture chart……………………………………... 14
5.0 Platform specification
5.1 Hardware……………………………………………………………….. 15
5.2 Software…………………………………………………………………. 15
6.0 Technical…………………………………………………………………………… 16

7.0 Economical……………………………………………………………………….. 16

1
1.0. Introduction
1.1. Purpose

The purpose of this document is to present a description and overview of everything

included in this Report. The Report is designed to document and describe the agreement
between the customer and the developer regarding the specification of the software product
requested. Its primary purpose is to provide a clear and descriptive “statement of user
requirements” that can be used as a reference in further development of the software system.
This document is broken into a number of sections used to logically separate the software
requirements into easily referenced parts.
This Report aims to describe the Functionality, External Interfaces, Attributes and Design
Constraints imposed on Implementation of the software system described throughout the rest
of the document. Throughout the description of the software system, the language and
terminology used should be unambiguous and consistent throughout the document.

1.2. Scope of Project

The software system being produced is called Book rental System. It is being produced for a
customer interested in renting books via the Internet. This system is designed to “provide
automation support” for the process of ordering books on rent.
The Book Rental System will allow any user to create an account to become a customer. The
customer, through the process of account creation, will have the option to become a member of
the site. It will enable the users (customers) to view the real time inventory and extract book
information, enable users to place orders online and pick up books in-store and access to a
personalized account profile etc. The system will allow customers to browse, search, select, and
add books to a shopping cart. Then, provided they have books in their shopping cart, check out
books in shopping cart and decrement the stock that the inventory the system maintains. The
Book Rental System also allows a manager to manage the inventory with full create, retrieve,
update and delete (CRUD) functionality with regards to books in the system.

2
2. System Requirement Analysis
System Analysis refers into the process of examining a situation with the intent of improving it
through better procedures and methods. System Analysis is the process of planning a new
System to either replace or complement an existing system. But before any planning is done the
old system must be thoroughly understood. The goal of the coding phase is to translate the
design of the system into code in a given programming language. Hence during coding, the focus
should be on developing programs that are easy to read and understand, and not simply on
developing programs that are easy to write.
2.1. Information Gathering
2.1.1 Functional Requirement
After analyzing the problem domain and concluding the solution, the function requirements that
will satisfy the need are following:

 The system should provide a registration page for users.

 User and admin must be verified using login module.
 System should provide a search book mechanism.
 The system should provide complete details of books along with cover page.
 The customer should be able to rent book.
 Rent should be calculated on the basis of period of rent and market price of book.
 Order id and user id must be given to customer by system.
 Customer should be able to return book
 Admin should be able to add, update and delete books.
 Admin should be able to view the registered users and remove them if required.
 System should provide a way to add books to cart.
 System should display total rent of books.
 System should provide mechanism to logout.

3
2.1.2 Nonfunctional Requirement
 Performance Requirement: The project is web based so it will require a good

internet connection to process faster. The software will be efficient if powerful

server is available the speed of processing of input and generation of output will
also depend on hardware i.e. processor an advanced processor will fulfill the needs
more faster as compared to an older and slower one.

 Size Requirement: The website should use minimum space at user side the website will

use only 15 MB space at user side. But at server side a large database space is required to
store information about thousands of books and users.
 Portability Requirement : The website should be portable enough this means that the
software should support different web browsers and no. of popular platforms such as
Linux and windows .the graphical user interface should support different devices with
varying size this can be done using programming techniques such as bootstrap and html
5.
 Security Requirement: The security system of the website should be strong enough to
prevent any unauthorized access privacy of the personal details of customer must be
maintained. User provides access will be doe through user id and password which will be
unique for each user. The password will be at least six digit string user access should be
limited in a way that it cannot harm the stored data such as book details.
 External Requirement: the website is logically approved as it does not disobey any low.

The website is ethical at it is helpful to users and looking at boarder aspect help to save
environment.

4
3. SYSTEM DESIGN

Design is meaningful activity needed to develop a quality product. Design is the only way by
which we can accurately translates the customer’s requirement into a finished software product
or system.
3.1 Class diagram
It is the main building block of any object oriented solution. It shows the classes in a system,
attributes and operations of each class and the relationship between each class. Different
relationships between
Classes are shown by different types of arrows.

5
3.2 Use case diagram

A use case diagram at its simplest is a representation of a user's interaction with the system that shows
the relationship between the user and the different use cases in which the user is involved. A use case
diagram can identify the different types of users of a system and the different use cases and will often be
accompanied by other types of diagrams as well.

6
 Figure 3.2 Use Case Diagram

3.3 Sequence Diagram

Sequence diagrams in UML show how objects interact with each other and the order those
interactions occur. It’s important to note that they show the interactions for a particular
scenario. The processes are represented vertically and interactions are show as arrows.

3.3.1 Sequence Diagram for Customer

7
 Figure 3.3.1 Sequence Diagram for Customer

3.3.2 Sequence Diagram for Admin

8
Figure 3.3.2 Sequence Diagram for Admin

9
3.4 Collaboration diagram
A collaboration diagram, also called a communication diagram or interaction diagram, is an
illustration of the relationships and interactions among software objects in the Unified Modeling
Language.

Figure 3.4.1 Collaboration Diagram

10
3.5 Data flow diagram
A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and
outputs. As its name indicates its focus is on the flow of information, where data comes from,
where it goes and how it gets stored.

3.5.1 level-0 data flow diagram

Figure 3.5.1 level-0 data flow diagram

3.5.2 level-1 data flow diagram

Figure 3.5.2 level-1 data flow diagram

11
4.0 DATABASE DESIGN
4.1 Data Design
Data design is used to transfer the information domain model of analysis phase into the data structures.
Those data structure play an important role in software implementation.
4.1.1 ER Diagram
The entity relationship model is a way of graphically representing the logical relationships of entities in
order to create a database .An entity relationship model is a systematic way of describing a business
process. The ER model defines the conceptual view of a database. It works around real world entities and
the association among them.

Figure 4.1.1 E-R Diagram

12
4.2 System Architecture
4.2.1 Structure chart
The structure chart is principal tool of structured design. The basic element in the structured chart is
module. Module is defined as the collection of program with four attributes.
 Input and output: What the module gets from the invoker is called input and what the receiver
gets from the module is called output.
 Function: the function process the input and produces output.
 Mechanics: The code or the logic by which the function is carried out.

Figure 4.2.1 Structure chart

13
5.0 Platform Specification

5.1 Hardware
 Processor : Intel P4 or Above 2.5Ghz
 RAM : 512 MB RAM or Above
 HDD : 20 GB or Above

5.2 SOFTWARE
 OS : Windows 7 & above
 Web Browser : Internet Explorer/ Mozilla/ Fire fox/Google Chrome
 Web server : Wamp server
 Database server : MYSQL
 Development technologies : HTML5, CSS, MYSQL, PHP

14
6.0 Technical

This is concerned with the specifying equipment and software that will successfully satisfy the
requirements the proposed system is technically feasible as it can be developed easily with the
help of available technology these may be different technical needs but on broader aspect it will
include the following:

 Better GUI on platforms such as windows 7 and above

 Producing outputs in less time
 User friendly website not much technical knowledge required
 Support different web browsers such as Google chrome, Firefox, internet explore

7.0 Economical

This kind of feasibility study is done for cost or benefit analysis. In this study the benefit of
proposed system are identified and the corresponding costs are determined.In this website the
books are provided at rent so multiple books can be rented by a user. This will prove beneficial
for user as well as owner as:

 User need not buy book

 Same book can be rented many times generating profit for owner
 Specifying particulars

 75% of money will be given back if book rented for one month
 60% of money will be given back if book rented for Three month
 50% of money will be given back if book rented for Six month

15