Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Specification
For
Page | 1
Table of Contents
Description Page No.
1. Introduction
1.1. Purpose 33333333
1.2. Scope _ 3333
1.3. Definition
1.4. Overview
2. Overall Description
2.1. Product Perspective
2.2. Product Function
2.3. User Characteristics
2.4. Architecture Design
2.5. Use Case Model Description
2.6. Class Diagram
2.7. Sequence Diagram
2.8. Database Design
2.8.1. ER Diagram
2.8.2. Schema Design
2.9. Assumptions and Dependencies
2.9.1. Context Diagram
3. Specific Requirements
3.1. Use Case Reports
3.2. Supplementary Requirements
Chapter 1
1. Introduction
Page | 2
1.1 Purpose
Online Book Store. This system will help the users to know automatically when certain
book requested by them has arrived once they have registered with the website. It will
also help the users to know the latest books of their interests being introduced into the
market like fiction, science, technology, romance etc.
1.2 Scope
1.3. Definitions
1.4 Overview
Existing System:
Manually Registration
Page | 3
Drawbacks:
No webcam support
Not all users can have access to website
People who doesn’t have a knowledge of computer and internet cannot use the
system
Proposed System:
Registration for users(customers)
Sale of books with email intimation.
Notification through mobile message when new books arrive.
Our Plan:
Registration for members.
Online maintenance of books and sales.
Acknowledgment for registration, sales and arrival of new books through
Emil.
Feedback from user
Chapter 2
General Description
2.1. Product Perspective
The Online book store network doesn’t work independently. It has to work together with
the computers software owned by Store. There are clearly defined interfaces for the
different systems
Page | 4
2.2. Product Function
Online Book Store: will help the users to know automatically when certain book
requested by them has arrived once they have registered with the website. It will also help
the users to know the latest books of their interests being introduced into the market like
fiction, science, technology, romance etc. Some of the features of the product are as
follow:
1. It focused on the acquisition, distribution and management of books.
2. It mainly emphasized creation and implementation of a book sales management
information system.
3. It automated the system with the help of SMS that informs the user about the
availability, price and method of purchasing the book.
4. It will ease and speed up the planning decision making process
process, secure confidential and reliable reports
5. It help for addressing problems of security secrecy and confidentially of customer
records.
6. Used to check the delays errors inconsistencies in records and access to historical
records.
7. It has eased the control and distribution of books in various parts of the country basing
on regional demands
Page | 5
Application Layer Business Layer Database
Layer
Registration
Registration
Registration of Registration
members
Feedback by Feedback
Member Feedback
Page | 6
Use cases were designed for object oriented software development they focus on what
the user need to do with the system. This approach is more powerful as compared to
traditional approach. It used a combination of text and pictures in order to improve
the understanding of requirements. The use case describe ‘what of a system and not
how of a system’. They only give the functional view of the system.
Login
Login
New User Registered
Members
Searc
Searc BUY
BUY Feedbac
Feedbac Profile
Profile
hh kk
ee
Manage
Manage Profile
Profile
Administrator
Manage
Manage
Registration
Registration
Grant
Grant
permissions
permissions
Add
Add or
or
delete
delete
members
members
Page | 7
2.6. Class Diagram
Book_id() login()
Total_amount()
Book_name() Order buy()
Book_genere() Book_id()
Book_publication() Book_name()
Book_price() Book_quantity()
Book_price()
Total_amount()
Account Created
View profile
Successful login
Page | 9
2.8. Database Design
2.8.1 Entity-Relationship Diagram
Contact
Contact Password
Password
Address
Address no
no
Sign
Sign up
up
city
city
User_id
User_id
Search Buy
Buy Username
Username
Search
Buy
Buy EmailID
EmailID
Feedback
Feedback
Register
Register
User
User Is
Registered
Registered Member
Member
registe
r
Delete
Delete
Is Updation
Updation members
members
Admin
Add
Add
members
members Stock
Stock
add/del
add/del
Administrator managem
managem
Administrator
ent
ent
Generatio
Generatio
nn
ENTITY-RELATIONSHIP DIAGRAM
Page | 10
Page | 11
2.9. Data Flow Diagram
Users
Sign search buy
A
d
m LOGIN Login M
i View Feedback search books e
n Registered users Online Book buy books m
i Store b
Stock availability Feedback
s e
Add/Delete Members request new books
t r
r Notify through SMS s
a
t
o
r
Page | 12
Chapter 3
3.0. Specific Requirement.
Login user
Enter Registration
Not Valid
User Already Exists
Fill Required Field
Valid
Not Valid
Valid
Go to Home Page
Page | 13
Search book
Buy book
Verification
Rejected Approved
Go to Home Page
3.3Supplementary Requirement
Safety Requirements
Highly recommend Quick Heal 2017 internet security to been Installed in
users Pc to prevent the harm that may occurs by unwanted malicious
software’s, phishing URLs and all the types of virus attacks during using
this application..
Security Requirements
All users should be properly authenticated before allowed entry into the
system authentication will be based on an E-mail address, and a password.
All activities on the system must be logged.
Page | 14
Non-Functional Requirements
Secure access of confidential data (user’s details). SSL can be used.
24 X 7 availability.
Better component design to get better performance at peak time.
Flexible service based architecture will be highly desirable for future
extension.
Other Requirements
The user must be agreed with all the term and conditions that have
provided by the System Administrator, local authority and Should Obey to
the all International standards and Protocols.
Page | 15