Oose

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 16

Aim:

To create a system to perform E- book Management System.

PROBLEM ANALYSIS AND PROJECT PLANNING:


E-book Management System gives an idea about how books are maintained in the
particular websites. The books that are to be purchased, the books that are to be sold are
maintained here. .Further some additional details of the current books that is available in the
store are also given. E-book Management System in this project is done in an authorized
way. The password and user id has been set here.

PROBLEM STATEMENT:
The EBook process is well organized online buying and selling of books. This
system is well developed in various resources, for example Amazon site deals more about e-
booking concepts. This process has various issues in the basics of maintenance of database
and updating sites, and virus problems in PDF books, so we have many issues in this process.
The process of e-books is fully based on online, and the process for this mainly interaction
Between buyer and seller, buyer who enter the site for purchase of book will use search
engine for book to purchase, the search engine will mainly focused on the database process,
It used to search books for the buyer who mentioned the book name, author name, edition,
and publication details in the site, so that the search engine would show many books. There
will be a payment option and option for PDF file or hardcopy delivery to home, the user
should decide whether he wants which one. Whether he choice hardcopy means, full detail
address, driving license no, and then he should login with his username and password, and
then payment through ATM debit or credit card applicable.

SOFTWARE REQUIREMENTS SPECIFICATION:

SNO SOFTWARE REQUIREMENT SPECIFICATION


1 Introduction
2 Purpose
3 Scope
4 Definition ,Acronyms and Abbreviations
5 Reference
6 Technology to be used
7 Tools to be used
8 Overview
9 Overall Description
10 Productive Description
11 Functional Requirements
12 Non Functional Requirements
13 Software interface
14 Hardware interface
15 System Function
16 User characteristics
17 Constraints
18 Assumptions and Dependencies
INTRODUCTION:
E-Book is the interface between the students and Librarian. It aims at improving
the efficiency in the Issue of books or magazines and reduces the complexities involved in it
to the maximum possible extent.

PURPOSE:

If the entire process of 'Issue of Books or Magazines' is done in a manual manner


then it would take several months for the books or magazines to reach the
applicant.Considering the fact that the number of students for Book Bank is increasing every
year, an Automated System becomes essential to meet the demand. So this system uses
several programming and database techniques to elucidate the work involved in this process.
The system has been carefully verified and validated in order to satisfy it.

SCOPE:
The System provides an online interface to the user where they can fill in their
personal details and submit the necessary documents (may be by scanning). The authority
concerned with the issue of books can use this system to reduce his workload.

DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS


1. E-book manager Refers to the super user who is the Central Authority who has
been vested with the privilege to manage the entire system.
2. User One who wishes to obtain the Books or Magazine
3. Visitor One who visits to obtain Books or Magazines.
4. Administrator One who manages and maintains Books or Magazines.
REFERENCES:
IEEE Software Requirement Specification format

TOOLS TO BE USED:
Environment Argo UML tool (for developing UML Patterns)

OVERVIEW:
SRS includes two sections: overall description and specific requirements. Overall
description will describe the major role of the system components and inter- connections.
Specific requirements will describe roles & functions of the actors.

OVERALL DESCRIPTION:
It will describe the major role of the system components and interconnections.

PRODUCT PERSPECTIVE:
The SRS acts as an interface between the user and the 'e-book manager'. This system
tries to make the interface as simple as possible and at the same time not risking the security
of data stored in. This minimizes the time duration in which the user receives the books or
magazines.

FUNCTIONAL REQUIREMENTS:
1. Add Book:

New book must be add in database

2. Search Book:

User can search book name and read it

3. Register:

Allow authenticated user

4. Payment:

User should pay the book amount

5. Download:

After the payment user can download the book.

NON FUNCTIONAL REQUIREMENTS:


Safety Requirements:
The database may get crashed at any certain time due to virus or operating system
failure. Therefore it is required to take the database backup.
Security Requirements:
We are going to develop a secured database for the university .There are different
categories of users namely teaching staff, administrator, library, staff, students etc.,
Depending upon the category of user the access rights are decided. It means if the user is an
administrator then he can be able to modify the data, delete, append etc., all other users other
than library staff only have the rights to retrieve the information about the database.
Software Quality Attributes
The Quality of the database is maintained in such a way so that it can be very user
friendly to all the users of the database
Hardware Constraints:

The system requires a database in order to store persistent data. The database
should have backup capabilities.
Software Constraints:
The development of the system will be constrained by the availability of
required software such as database and development tools.

SOFTWARE INTERFACE:
Argo UML
HARDWARE INTERFACE:
The server is directly connected to the client systems. The client systems have access
to the database on the server.

SYSTEM FUNCTIONS:
Secure Registration of information by the Students. Librarians can generate reports
from the information and are the only authorized personnel to add the eligible application
information to the database.

USER CHARACTERISTICS:
User:
They are the people who desire to obtain the books and submit the information to the
database.
Visitor:
They are the person who visits the E-book system
Administrator:
He has the certain privileges to add the books and to approval of the reservation of
books.

CONSTRAINTS:
The Students require a computer to submit their information. Although the security
is given high importance, there is always a chance of intrusion in the web world which
requires constant monitoring.

ASSUMPTIONS AND DEPENDENCIES:


The user and e-book manager must have basic knowledge of computers and English
Language. The user may be required to scan the documents and send.

UML DIAGRAMS:
The following UML diagrams describe the process involved in the stock maintenance
system.
• Use case diagram
• Class diagram
• Sequence diagram
• Collaboration diagram
• State chart diagram
• Activity diagram
• Package diagram

USE CASE DIAGRAM:


Use-case diagrams describe the high-level functions and scope of a system. These
diagrams also identify the interactions between the system and its actors. The use cases and
actors in use-case diagrams describe what the system does and how the actors use it, but not
how the system operates internally.

The actors in this use case diagram are visitor, register user and administrator. The
use cases are the activities performed by actors.
□ The administrator will give the books available.
□ Register and visitor will login and check the list of e-Books in the database.
□ The database will be updated according to the purchase done and it will be up to date.
The use cases in the use case diagram are Search book, download, payment and
Sales person.
□ Select books will gives us the status of the purchasing order details
□ Login will give us the entry for the customer of this project.
□ Database will give us the details about the total eBook available.
□ Purchase will give us the details about the details and the history of eBooks
purchased.

NOTATIONS:
CLASS DIAGRAM:
The class diagram, also referred to as object modeling is the main static analysis
diagram. The main task of object modeling is to graphically show what each object will
do in the problem domain. The problem domain describes the structure and the
relationships among objects.
This class diagram has three classes administrator, Register user and Visitor
□ Administrator – is the class name. Its attributes are name. The operations
performed are update and sales record
□ Register User – is the class name. Its attributes are name, id, password, security
question answer. The operations performed are search, Download and Payment.
□ Visitor – is the class name. Its attribute are customer name, contact number and id.
The operations performed are register and search book.

NOTATIONS:
SEQUENCE DIAGRAM:
A sequence diagram represents the sequence and interactions of a given
USE-CASE scenario. Sequence diagrams can capture most of the information about the
system.
The sequence diagram describes the sequence of steps to show
□ The Customer enters the E-Book website.
□ They search for login if already registered.
□ Customer should register the site if it was not already registered.
□ After successful registration the site is available for the user.
□ Customer can select the book and Pay money to the Website

NOTATIONS:
COLLABORATION DIAGRAM:
□ The first collaboration diagram is to show how the customer login and getting
details of e-Books in the e-Book management system.
□ Here the sequence is numbered according to the flow of execution.

NOTATIONS:
STATE CHART DIAGRAM:
□ A State chart diagram describes different states of an object and these states
are controlled by external or internal events.
□ The states are changed by events
□ The E-books can be read online after login to a certain e-book site.
□ The registration can be done and the required books are obtained online.
□ User can pay for it and update wherever needed

NOTATIONS:
ACTIVITY DIAGRAM:
This activity diagram flow of stepwise activities performed in recruitment system.

□ First Customer login then checks books available.


□ The book list is verified and is given in an ordered format.
□ The needed book is selected.
□ We can download the book.
□ Enter your account details and purchase the book.

NOTATIONS:
DEPLOYMENT DIAGRAM:
A deployment diagram is a diagram that shows the configuration of run time
processing nodes and the components that live on them. Deployment diagrams is a kind
of structure diagram used in modeling the physical aspects of an object-oriented system.
They are often be used to model the static deployment view of a system (topology of
the hardware).

NOTATIONS:
Code Generation:
STEPS TO GENERATE CODE USING ARGO UML:

Step 1: Draw Class diagram with all its notations.


Step 2: Select all the classes.
Step 3: Choose Generation menu for code generation.
Step 4: Choose the required classes
Step 5: Browse the location to locate the code.
Step 6: Apply Generate
SOFTWARE TESTING:

Software testing is a process used to identify the correctness, completeness,


security, and quality of developed computer software.

TYPES OF TESTING:
There are many types of testing like
• Integration Testing

• Unit Testing

• Black box Testing

• White box Testing

• Functional Testing

• System Testing

• Stress Testing

• Performance Testing

• Acceptance Testing

• Regression Testing

• Beta Testing

Integration Testing:
It is conducted to evaluate the interaction between integrated units or
components of a software system. The main aim is to detect any interface defects
between these units or components.

White Box Testing:


Unlike black-box testing, in white-box testing, the tester has knowledge of the
internal workings of the software being tested. It is also known as clear-box or
transparent testing.

Functional Testing:
This type of testing verifies that each function of the software application
operates in conformance with the requirement specification.
System Testing:
System testing tests the entire software system, as a whole. It ensures that all
components integrated together as expected, and the system meets the specified
requirements.

Stress Testing:
Stress testing is a type of software testing that determines the robustness of
software by testing it under extreme conditions. It involves testing beyond normal
operational capacity, often to a breaking point, to observe the results.

Performance Testing:
Performance testing evaluates the speed, responsiveness, and stability of a
system under a particular workload. The main goal is to determine the speed,
responsiveness, and stability of a system under a specific workload.

Acceptance Testing:
This testing is performed to determine if the software system has met the
required specifications and is accepted by the customer or end-users.

Regression Testing:
Regression testing is carried out to ensure that a recent program or code change
has not adversely affected existing features.

Beta Testing:
Beta testing is the final testing done by end-users. It allows users to provide
feedback about the product before the full launch.

Unit Testing:
Unit testing involves testing individual units or components of a software
application in isolation from the rest of the system. The goal is to validate that each unit
of the software performs as designed.
Black Box Testing:
This testing technique focuses solely on the functionality of the software.
Testers are not concerned with the internal workings of the system; they test the
software based on its specifications.

Result:
Thus the domain E-Book Management System was designed, tested and the
code was generated successfully using Argo UML Tools.

You might also like