Objective

The main objective of the document is to illustrate the Requirements of project E-Book Management system. The document gives the detailed description of both functional and non-functional requirements. It will also explain about the features of the system interface of the system. What the system will do, the constraint under which it must operate and how the system will react to external stimuli. The document is developed after a number of consultations with team members and specification of the given project.

Scope Of The Project

The software provide the visitor, customer and administrator a easy and efficient way to buy and manage books in online.
Software provides following facilities to customer:

  • Facilitates easy shopping online.
  • Provides information about the products in categories.
  • Provides e-mail facility for future correspondence.
  • Provides Backup facility.
  • Software provides the following facilities to the merchant.
  • Manages the Transportation of hard copy of Book.
  • Look after the payment method.

Project Description

This software is totally self contained and works relatively an efficient on the package relates to the software. It provides simple database rather than complex one for high requirement and it provides a good and easy graphical user interface to both new and naive as well as experienced user of the computer.

Requirements

Functional Requirements

  • Register – Enter details in application form.
  • Login – Enter Username and Password.
  • Search – Search book by attribute.
  • Buy – Download softcopies and order for hard copy.
  • Payment – Pay for books in different method.
  • Update – Update User details

Non- Functional Requirements

  • Bookmark – Bookmark the Website.
  • Categories – Book categories in Website.
  • Most Downloaded – Highest purchased book.
  • Offers – Offer given by merchant.
  • Carting – Mark and select multiple books.

Module Description

In this project we have defined different modules to enable the E-Book Management in successful manner.

Register

The register module contains the application form or registration form which contains following details.

Name, Address, Contact number, E-mail id, Password etc.

Login

The Login module contain the form which contain membership name and member password.
It includes Username and Password

Search Book

The search book module contain list of books,from this list we search for the book which we need.This also containes another field called as categories where can select the category of the book.

Download

The download module contains the downloading option for where purpose where we can download,whatever Ebook we search and found.

Payment

After the book is searched and found. Then the user is going to download the book. Before the downloading the books needs payment for that book. So user has to select the type of transaction wheather credit card (or) debit card (or) cash (or) cheque (or) DD.

Sales Record

The website admin has to maintain the sales record where the record should be in updated, where how many books is sales ed. How much amount credited and names of user who downloaded that book and how much they paid for downloading the book.

Update

The update module should maintained by the website administrator. The admin should update each and every process like.

  • Number of user registered
  • Registered user viewing.
  • Downloading by user.
  • Payment offered by user.

Uml Use case Diagram

Uml provides use case diagram notation to illustrate the names of use case and author relationship between them. Use case diagram and case relationship are secondary in use case work use case text document.

E-Book Management System use case

Uml Activity Diagram

A Uml activity diagram shows sequential and parallel activities in a process, work flows, data flows and compiler algorithm.

E-Book Management System activity Diagram

Uml Class Diagram

The Uml class diagram is to illustrates class interfaces and their actions. They are used for static object modeling, we have already introduced and used their uml diagram while domain modeling.

E-Book Management System class diagram

Uml Sequence Diagram

A sequence diagram illustrate a kind of format in which each object interact via message. It is generalize between two or more specialized diagram.

E-Book Management sequence Diagram

Uml Collaboration Diagram

Communication diagram illustrate that object interact on a graph or network format in which object can be placed where an the diagram. In collaboration diagram the object can be placed in anywhere on the diagram. The collaboration comes from sequence diagram.

E-Book Management collaboration Diagram

Uml State Chart Diagram

A Uml state machine represents the interaction events and states of an object and behavior of an object in reaction to an event.. Transaction shown as allows labeled with their event. It is included with initial pseudo state and fins end state.

E-Book Management state chart

Uml Component Diagram

Components are slightly fuzzy concept in this Uml,because both class and components can be used to model the something.

component diagram e book management

Uml Deployment Diagram

Deployment diagram shows the assignment of concrete software artifact to computational nodes. It shows the deployment of software elements to the physical elements. Deployment diagram are useful to communicate or deployment architecture.

Deployment Diagram

Conclusion

Thus the project for E-BOOK MANAGEMENT has been successfully executed and codes are generated.

Download Project

 

E-Book Management System Project Report