For Online Students


Object Oriented Analysis and Design Lab E-BOOK MANAGEMENT

Click here to download the below document with Diagrams…

E-BOOK MANAGEMENT

1.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.
2.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 correspondance.
  • Provides Backup facility.

Software provides the following facilities to the merchant.

  • Manages the Transportation of hard copy of Book.
  • Look after the payment method.

3.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 naïve as well as experianced user of the computer.
4.REQUIREMENTS:
(a).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

(b).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.

(c).HARDWERE REQUIREMENTS:
1. Processor – Intel Pentium IV-2.0 GHZ.
2. Hardware – 40 GB(segate)
3. RAM – 512mb
4. DVD RAM – 1 nos.
(d).SOFTWARE REQUIREMENTS:
1. OS – windows XP/vista.
2. Front end Tool – Rational Rose Enterprise suite.
3. Back end Tool – Oracle 10i.
5.MODULE DISCRIPTION:
In this project we have defined different modules to enable the E-Book Management in successful mannner.
i. REGISTER:
The register module contains the applicaton form or registration form which contains following details.

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

ii. LOGIN:
The Login module contain the form which contain membership name and mamber password.
It includes Username and Password.
iii. 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.
iv. DOWNLOAD:
The download module contains the downloading option for where purpose where we can download,whatever ebook we search and found.
v. 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.
vi. 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 for dowloading the book.
vii. 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.
  •  Downlaoding by user.
  •  Payment affered by user.

6: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 act as a source of inspiration for designing some software objects.

DOMAIN MODEL
7:PARTIAL LAYERED ARCHITECTURE:
Sequense diagram is an interaction overview diagram.It provides a big picture overview of how a set of interaction are related interms of logic and process flow.
This Partial layer architecture shows the interface of the sequence diagram, here the administrator shows the interface by displaying actor symbol.
8:LOGICAL ARCHITECTURE:
The Logical architecture is large scale organisation 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.
9: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 adminstrator fails to save the new register and new visitor may affect in update.
  •  Failure of Backuo details.

10:GANTT CHART:
It describe 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.
11:POST- FUNCTION AND PRE-FUNCTION:
i. REGISTER:
PRE-FUNCTION: Enter details in registration form.
POST-FUNCTION: Verify details in registration form.
ii. LOGIN:
PRE-FUNCTION: Enter user name and password.
POST-FUNCTION: Verify user name and password.
iii. SEARCH BOOK:
PRE-FUNCTION: Enter name of book,authour and category for searching.
POST-FUNCTION: Check wheather the book is available in the database.
iv. DOWNLOAD:
PRE-FUNCTION: Entering the name of book to be download.
POST-FUNCTION: After downloading the book the user must pay the money.
v. PAYMENT:
PRE-FUNCTION: Enter the tyoe of payment for downloading book wheather through online credit card,debit,cheque.
POST-FUNCTION: Check wheather the transaction is vaild or not wheather the money is in transaction card or cheque is valid or not.
vi. SALES RECORD AND UPDATE:
PRE-FUNCTION: Before downloading the books the adminstrator keep the book sales account correctly and updately.
POST-FUNCTION: After downloading the book,the adminstrator update the record at time whenever the book in downloaded.
12:UML PACKAGE DIAGRAM:
A package diagram provides a way to group element. Here we have grouped the 6 main elements of software project grouped the in order register,login,serach book.It goes to update and sales record. A package name may be based on tab if the package shows the inner member of main package.
13:TECHNICAL SERVICES LAYER:
Thechnical service layer describes the relationship between different actors,components of the software process for any admin seek the registration for new visitor. So that the new visitor can login the website and search for book and if need can buy it.
14:DOMAIN SERVICES LAYER:
After technical services layer from partial layered aechicectuer,we are going to generate the coading in java or VB the project domain is now finalized in JAVA/VB.
15:USER INTERFACE LAYER:
i. 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.
iii. VISITOR:
The visitor can register the application form and become a member of the website. The visitor can search books and read the boook but he must register to buy or download the book.
UML USECASE DIAGRAM:
Uml provides use case diagram natation to iilustrate the names of use case and author relationship between them. Use case diagram and case relationship are secondary in use case work usecase text document.
USECASE DIAGRAM
UML CLASS DIAGRAM:
The Uml class diagram is to illutrates class interfaces ans their actions.They are used for ststic object modeling, we have already introduced and used their uml diagram while domain modeling.
CLASS DIAGRAM
UML SEQUENCE DIAGRAM:
A sequence diagram illustrate akind of format in which each object interact via message. It is generalize between two or more specialized diagram.
SEQUENCE DIAGRAM
PARTIAL LAYER ARCHITECTURE DIAGRAM:
Sequense diagram is an interaction overview diagram.It provides a big picture overview of how a set of interaction are related interms of logic and process flow.
This Partial layer architecture shows the interface of the sequence diagram, here the administrator shows the interface by displaying actor symbol.
PARTIAL LAYER ARCHITECTURE
UML COLLABRATION DIAGRAM:
Communicaton diagram illustrate that object interact on a graph or network format in which object can be placed where an thw diagram. In collabration diagram the object can be placed in anywhere on the daigram. The collabration comes from sequence diagram.
COLLABRATION DIAGRAM
UML STATE CHART DIAGRAM:
A Uml state machine represents the interaction events and states of an object and behaviour of an object in reaction to an event.. Transaction shown as allows labelled with their event. It is included with initial psedo state and fins end state.
STATE CHART DIAGRAM

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

ACTIVITY DIAGRAM

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
UML DEPLOYEMENT DIAGRAM:
Deployement diagram shows the assignment of concrete software artifact to computational nodes. It shows the deployement of software elements to the physical elements. Deployement diagram are useful to communicate or deployement architecture.
DEPLOYEMENT DIAGRAM
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 .
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 thse testing option one by one and testing activity is carried out for all the coadings and testing is carried out.
CONCLUSION:
Thus the project for E-BOOK MANAGEMENT has been successfully executed and codes are generated.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

%d bloggers like this: