EX NO: DATE:

EBOOK MANAGEMENT SYSTEM

Problem Analysis:
The problem is to find out the book that we need with reference to the prescribed author .The books will be categorized in to various sections .Some of the sections include Novels, Love and Romance etc. EBooks of various authors can be found in ease.

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.

PURPOSE:
The system is designed with end user requirements as main criteria. It includes front end tool to receive data needed and to validate the entries. It has backend access to store validate data for future reference .To analyzes and design a EBOOK based on Object Oriented Analysis and Design concept.

SCOPE OF THE PROJECT:

The software provides 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 method. payment

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 nave 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:

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

HARDWERE REQUIREMENTS:
Processor - Intel Pentium IV-2.0 GHZ. Hardware - 40 GB(Seagate) RAM - 512mb DVD RAM - 1 nos.

SOFTWARE REQUIREMENTS:
OS - windows XP/vista. Front end Tool - Rational Rose Enterprise suite. Back end Tool - Oracle 10i.

DOCUMENT CONVENTIONS: Administrator - The person who has the full authority over the system. He can view all registered users.

Job Seekers - the person who registers in the system in search of jobs. Company - A company can register itself, select the required employees and provide information about the result. 1.4. REFERENCES: www.timesjob.com: 2 OVERALL DESCRIPTIONS: 2.1 PRODUCT PERSPECTIVE: This project is a self-contained project for convenient recruitment process. 2.2 PRODUCT FUNCTIONS: The front end of the project is where the visitors or job seekers do their enrollment. The back end is managed by the administrator effectively 2.3 TOOLS TO BE USED Rational Rose Enterprise Edition, AgroUML 3. SYSTEM FEATURES 3.1 APPLYING FOR JOB: 3.1.1 SYSTEM DESCRIPTION AND PRIORITY: This feature allows the job seeker to apply for job. 3.1.2 STIMULUS AND RESPONSE SEQUENCE: When the user types the book, a list of possible e-books has to be displayed along with other details 3.1.3 FUNCTIONAL REQUIREMENTS: REQ1: Only registered users can search and download. 4 OTHER NON-FUNCTIONAL REQUIREMENTS: 4.1 PERFORMANCE MANAGEMENT: To increase the performance and free up database resources, the default features are written to cache files on their initial load. 4.2 SAFETY REQUIREMENTS: The database must be maintained effective from hacking. 4.3SECURITY REQUIREMENTS: Password for registered accounts are stored securely in a hash, the uploads made by the user must be checked and then accepted. GANTT CHART:

UML USECASE 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.

register

visitor

login

search book

registered user download

payment

adminstrator sales person

UML CLASS DIAGRAM

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

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

UML ACTIVITY DIAGRAM:

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

login

register

welcome page

search book

online reading

download

payment

update

ACTIVITY DIAGRAM: REGISTER

The register module contains the application form or registration form which contains following details. Address, Contact number, E-mail id, Password etc.

enter the user details

name

user id

password

email-id

security question

verification

re enter the user details

valid no yes display

ACTIVITY DIAGRAM: LOGIN:

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

enter the username and password

verification

reenter the username and password

valiid no yes display

ACTIVITY DIAGRAM: SEARCH BOOK:

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

enter the book details

book name

book no

authour name

published by

published at

display

ACTIVITY DIAGRAM: DOWNLOAD:

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

download

setup execution

run

installing

display

ACTIVITY DIAGRAM: 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 whether credit card (or) debit card (or) cash (or) cheque (or) DD.

select payment

cash

credit card

cheque

enter the credit card number

re enter credit card number

valid no yes pay

ACTIVITY DIAGRAM:SALES RECORD:

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

sales person details

name

contact number

e-mail id

accept the order

adminiistrator

register user

visitor

1: seek login

2: login agreed 3: after register to the site 4: seek for registers

5: register is granted 6: seek for downloading books

7: downloading the book 8: seek for payment

9: payment transaction is submitted

adminiistrator

5: register is granted 4: seek for registers

1: seek login 7: downloading the book 2: login agreed 6: seek for downloading books 8: seek for payment 9: payment transaction is submitted

3: after register to the site visitor register user

administrator

visitor

register user

#include "administrator.h"

//##ModelId=512B3AC4002E administrator::update() { }

//##ModelId=512B3ACC033C administrator::sales record() { }

#ifndef ADMINISTRATOR_H_HEADER_INCLUDED_AEBBEBCA #define ADMINISTRATOR_H_HEADER_INCLUDED_AEBBEBCA

//##ModelId=512B3A77000F class administrator { public: //##ModelId=512B3AC4002E update();

//##ModelId=512B3ACC033C sales record();

private: //##ModelId=512B3ABC02EE name; };

#endif /* ADMINISTRATOR_H_HEADER_INCLUDED_AEBBEBCA */

#include "reg user.h"

//##ModelId=512B3B4D001F reg user::search() { }

//##ModelId=512B3B560177 reg user::download() { }

//##ModelId=512B3B5A0128 reg user::payment() { }

//##ModelId=512B3BAD0196 reg user::ebook reader() { }

#ifndef REG_USER_H_HEADER_INCLUDED_AEBBFAE8 #define REG_USER_H_HEADER_INCLUDED_AEBBFAE8

//##ModelId=512B3ADB0186 class reg user { public: //##ModelId=512B3B4D001F search();

//##ModelId=512B3B560177 download();

//##ModelId=512B3B5A0128 payment();

//##ModelId=512B3BAD0196 ebook reader();

private: //##ModelId=512B3AFC03A9 name; //##ModelId=512B3B0602DE user id; //##ModelId=512B3B0B02EE

password; //##ModelId=512B3B1903B9 email id; //##ModelId=512B3B230196 security question; //##ModelId=512B3B31003E answer; };

#endif /* REG_USER_H_HEADER_INCLUDED_AEBBFAE8 */

#include "vistor.h"

//##ModelId=512B3C4300BB vistor::Register() { }

//##ModelId=512B3C51004E vistor::Search book() { }

#ifndef VISTOR_H_HEADER_INCLUDED_AEBBD8F1 #define VISTOR_H_HEADER_INCLUDED_AEBBD8F1

//##ModelId=512B3BE60251 class vistor { public: //##ModelId=512B3C4300BB Register();

//##ModelId=512B3C51004E Search book();

private: //##ModelId=512B3C0203B9 user id; //##ModelId=512B3C0B006D password; //##ModelId=512B3C1000BB customer name; //##ModelId=512B3C2B031C contact number; //##ModelId=512B3C3702BF

email id; };

#endif /* VISTOR_H_HEADER_INCLUDED_AEBBD8F1 */