E-BOOK MANAGEMENT SYSTEM PowerPoint Presentation

How to manage the e book

1. E-BOOK MANAGEMENT SYSTEM Submitted by Nawej Debjani Aman & Hrishikesh

2. CONTENTS Introduction………………………………………………………… Problem Analysis…………………………………………………… Objective & Purpose……………………………………………....... Scop of the Project…………………………………………………. Software provides facilities for customers & Merchant……………... Requirements………………………………………………………. Module Description …………………………………………………. Domain Model………………………………………………………. Partial Layered Architecture………………………………………... Logical Architecture………………………………………………… Risk Activity…………………………………………………………. Safety & Security Requirements……………………………………….

3. Gantt Chart…………………………………………………………… User Interface Layer…………………………………………………. UML Use case Diagram………………………………………………. UML Class Diagram…………………………………………………. UML Sequence Diagram……………………………………………… UML Activity Diagram………………………………………………. UML Collaboration Diagram…………………………………………. UML Component Diagram……………………………………………… UML Development Diagram…………………………………………… Implementation & Testing……………………………………………… Future Scope…………………………………………………………… Conclusion………………………………………………………………

4. Introduction:   Bibliophilic eBooks is an online website where the customer can read and purchase eBooks online. This web project is developed using HTML, CSS, JavaScript, PHP. Through a web browser the customers can search for a book by its title or author, later can add to the shopping cart and finally purchase using online transaction. The user can login using his account details or new customers can set up an account very quickly. They should give the details of their name, contact number and email address. The user can also give feedback to a book by giving ratings on a score of five. The books are divided into many categories based on genre like Fiction, Non-Fiction, Si-Fi, etc .

5. 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. E-Books of various authors can be found in ease.

6. 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 an EBOOK based on Object Oriented Analysis and Design concept

7. SCOPE OF THE PROJECT : The software provides the visitor, customer and administrator a easy and efficient way to buy and manage books in online.

8. 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

9. SOFTWARE REQUIREMENTS : - OS - windows XP/vista.   Front end Tool - Rational Rose Enterprise suite.   Back-end Tool - Oracle 10i. HARDWERE REQUIREMENTS: - Processor - Intel Pentium IV-2.0 GHZ.   Hardware - 40 GB(Seagate)   RAM - 512mb   DVD RAM - 1 nos. 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 . 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 REQUIREMENTS

10. SOFTWARE REQUIREMENTS : - OS - windows XP/vista.   Front end Tool - Rational Rose Enterprise suite.   Back-end Tool - Oracle 10i. HARDWERE REQUIREMENTS: - Processor - Intel Pentium IV-2.0 GHZ.   Hardware - 40 GB(Seagate)   RAM - 512mb   DVD RAM - 1 nos. 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 . 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

11. MODULE DISCRIPTION : 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:   Virtual Tutor :   The search book module contains 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. DOWNLOAD: The download module contains the downloading option for where purpose where we can download, whatever e-book 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 whether 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 slashed. 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 users registered  Registered user viewing.  Downloading by user.  Payment affeered by user.

12. DOMAIN MODEL: A domain model is a visual representation of conceptual classes or real situations object in a domain.    In object-oriented analysis, the domain model is the most important.  It illustrates the concept in the domain.  It acts as a source of inspiration for designing some software objects

13. PARTIAL LAYERED ARCHITECTURE: Sequence diagram is an interaction overview diagram. It provides a big picture overview of how a set of interaction are related in terms of logic and process .This Partial layer architecture shows the interface of the sequence diagram, here the administrator shows the interface by displaying act or symbol.

14. LOGICAL ARCHITECTURE: The Logical architecture is large scale organization of software class into packages, sub system layer, It is called logical architecture because ther is no direction about how these elements are display on different operating system.   RISK ACTIVITY:   If the system fails to update the book details of unnecessary confusion may be avoided. When the member may not register the form correctly. It may affect the login.  If the administrator fails to save the new register and new visitor may affect in update. Failure of Backup details.

15. SAFETY REQUIREMENTS: The database must be maintained effective from hacking.   SECURITY REQUIREMENTS: Password for registered accounts are stored securely in a hash, the uploads made by the user must be checked and then accepted.

16. GANTT CHART: It describes the time schedule for the planning to complete the corresponding and after completion of core product, what is the time taken for the project action of core product.

17. USER INTERFACE LAYER: ADMIN: The administrator is used to register a new visitor for the website. Admin can keep those records update. Admin keep sales record i.e , now much book is downloaded and how much book is buyed newly with copy write etc. ii. REGISTERED USER: Registered user can search the book whatever needs and can read the book in online. If user is satisfied with this book, can download the book but after payment.   VISITOR: The visitor can register the application form and become a member of the website. The visitor can search books and read the book but he must register to buy or download the book.

18. 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.

19. 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

20. UML SEQUENCE DIAGRAM :   A sequence diagram illustrates a kind of format in which each object interacts via message. It is generalized between two or more specialized diagram

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

22. UML COLLABRATION 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

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

24. UML DEPLOYEMENT 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

25. IMPLEMENTATION: After the completion of UML diagrams for E-Book Management we should generate the code. Select the tools option from main menu then select the sub option program module in which we are going to generate the code in JAVA/VB/J2EE. Then go ahead and select the generate code option as a result of code generation

26. TESTING: To perform the testing for the generated code again select the tools option from menu bar and choose quality architecture option a sub window gets opened. We are going to perform Unit Test and Scenario testing for our project. So, select these testing option one by one and testing activity is carried out for all the coding and testing is carried out.

27. FUTURE SCOPE: The eBook management system is gaining huge popularity among the readers. This system is helpful for the bibliophiles who are always travelling and find it hard to carry books everywhere. It provides with all kinds of eBooks which you can read at anytime and anywhere. And by each day this system is increasing its popularity. It can be accessed anywhere and anytime around the world

28. CONCLUSION: Thus, the project for E-BOOK MANAGEMENT has been successfully executed and codes are generated. In conclusion we implemented all the functionalities stated in the requirement, all were tested and it showed that they are all working properly. Also, we implemented the system requirement quality like responsiveness so on different devices the system adapts to suit it, and also it works on these browsers like safari, google chrome properly