finalvdb

8/16/2019 Finalvdb

http://slidepdf.com/reader/full/finalvdb 1/57

1.Introduction

1.1 Objective&scope of the project:

The main objective of the online buying is to enable a customer to buy the

products through the net. Many people choose to conduct shopping online because of

the convenience.The purpose of the document is to describe the requirements for an

online bookshop, also describes the interface for the system. This document is the

only one that describes the requirements of the system.

A web based application for online book shop. The main objective of

thesystem is to guide the users how to get the books from the webby selecting one

from no of books it gives the detail description of book in detail. Performance is quite

ecellent and user understandable.

• !bject oriented software engineering "#ernd #ruegge, Allen $. %utoit

• &eb technology and design " '. (avier

The present system does not have efficient search operations, low privileges

for administrators and even some book stores are lack in security optionsThe proposed system provides efficient search operations by author, category, title search,

efficient options as unregister user cannot logged into registered users or

administrators, provide several options for administrators to perform efficient

operations.

1.2 Background Details:

The manual system gives us very less security for saving data and some data

may be lost due to miss)management.The *ystem not providing any on line interface ,so

the paper work is taking a lot of time to maintain and communicate, which is hence very

laborious and epensive.This system is not also providing any report generation facility

for user specific requirements.The system is not also providing any online facility to

reserve their bookings for cargo shipments and also for passenger voyages.This system

has no facilities to store different stock details, maintenance details and bill details which

+

8/16/2019 Finalvdb


can be accessed instantly as per requirement.The system is not maintaining an user

hierarchy. The system is giving only less memory usage for the users.

The development of this new system contains the following activities, which try to

automate the entire process keeping in the view of database integration approach.This

system maintains users personal, address, and contact details.-ser friendliness is

provided in the application with various controls provided by system rich user

interface.This system makes the overall project management much easier and

fleible.arious classes have been used for maintain the details of all the users and

catalog. Authentication is provided for this application only registered users can

access.The users information files can be stored in 'entrali/ed database which can be

maintained by the system.This system is providing more memory for the users tomaintain data. This system is providing accessibility control to data with respect to

users.This system is providing on line facilities to book both cargo ships and passenger

ships for voyages.This is providing facilities to store different type of administrative data

through online like ship details, ship parts stock, employee details, ship reservation

details, purchase details and different pay bill details etc.

1.3 Definition of the roble!:

To develop an online comprehensive book shop, to engage public to meet their

needs, this project is designed. The purpose of the document is to describe the

requirements for an online bookshop. 0t also describes the interface for the system.

0n contrast, online shopping helps consumers avoid these disadvantages.

&ith online shopping, a person logs onto the 0nternet, visits the store1s website,

andchooses the items she desires. The items are held in a virtual shopping cart until she is

ready to make her purchase.

2

8/16/2019 Finalvdb


2. "#ste! $e%uire!ents "pecification

2.1 unctional $e%uire!ents:

Particular requirements mainly used directly in system development. This functional

requirement also eplains the interaction between system and its environment .

3unctional requirements are divided into two categories.

• -ser requirements

• Administrator requirements

-ser requirements4

• To view the books by author, by title or search by categories.

• The books viewed can be added to the shopping cart of the user.

• %isplay the contents of the cart when required and manage the cart.

• 'ustomer should register at the website to buy books at book bu//.

• -sers are allowed to change their password

Administrator 5equirements4

• Managing books and categories.

• Managing users.

• iew feedback provided by the users.

• iew the history of the orders.

6

8/16/2019 Finalvdb


2.2 'on unctional $e%uire!ents:

Particular requirements used indirectly in the system development.

1. (ser interfaces and hu!an factor:An interface has been provided to client that is compatible with windows

environment and is designed to be friendly

2. Docu!entation:

%esign level %ocument is used as a guide for developers and is given with the

system to the client. 0mplementation level document may also be prepared to have better

resolution when any conflict occurs.

3. erfor!ance characteristics:

5equest should be processed within 27 seconds.

Providing the 289: service availability to the customers

). *rror handling and e+tre!e conditions:

0n case of user error, the system should display a meaningful error message to the

user, such that the user can correct his error .

,. -ualit# issues:

%ata provided by the system is reliable as it directly interacts with user.

;. "#ste! !odification:

The present system can be modified such that etra constraints can be added

toimprove its performance

:. h#sical environ!ent:

The present system can be implemented in substitution to all

metrological stations situatedacross the nation.

<. "ecurit# issues:

Administrator login details are not visible to second person

=. $esource issues:

8

8/16/2019 Finalvdb


The database should not become corrupted in case of system crash or power

failure.

3. $e%uire!ent nal#sis Docu!ent

3.1 "#ste! /odels:

3.1.1 Identif#ing ctors:

A scenario is an instance of a use case describing a concrete set of

actions. *cenario is an eample describing all common cases.

&e describe a scenario using a template with three fields

+. *cenario name

2. Participating Actor

6. 3low of >vent

-se case name Administrator

Participating actor Administrator, database

>ntry condition Administrator should be logged in.

3low of events +. $e can change his password.

2.$e can manage registered users

6. $e can search books by author or title or

edition.

8.$e can add or delete books

7.$e can update price of books

>it condition Manage book bu// website

3.2 (se case!odel:

3.2.1 Identif#ing (se 0ases:

7

8/16/2019 Finalvdb


0t is used in requirements engineering and analysis. 0t is used to specify

The functionality of system is defined in terms of actors and use cases. The actor is an

eternal entity that interacts with the system.

-se case is a sequence of events. 0t eplains all possibleactions between actor

and system. The actors are outside of the boundary and usecases are inside this

boundary.

3.2.2 (se case Diagra!s:

(se case Diagra! or d!instrator:

delivery report

update

login

admin

select

pay cash

logout

registrations

cust

3ig4 6.+4 -se 'ase %iagram for !nline #ook *hop

;

8/16/2019 Finalvdb


(se 0ase Diagra! or 0usto!er:

type of book

select author

place in cart

select book from cart

cust

3ig4 -se case %iagram for 'ustomer

:

8/16/2019 Finalvdb


3.3Object /odel

3.3.1 Data Dictionar#:

" 'o able na!e ttribute "#nta+

'a!e Data t#pe isibilit#

+ admin Aname

Pwd

archar2?6@

archar2?2@

Public

Private

'reate table admin?aname

varchar2?6@primary key,

pass varchar2?2@B

2 customer 3name

lname

uname

pswd

address

eid

mob

gender

archar2?6@

archar2?2@

archar2?2@

archar2?+@

archar2?7@

archar2?2@

0nteger?+7

archar2?7

Public

Public

Public

private

Public

Public

Public

Public

'reate table cust

?fname varchar2?6@,lname

varchar2?2@,uname

varchar2?2@,pswd

varchar2?+@,address

varchar2?7@,eid

varchar2?2@,mob

integer?+7,gender

varchar2?2@,city

varchar2?2@B

<

8/16/2019 Finalvdb


city archar2?2@ Public

6 books #name

aname

edition

price

*ummary

archar2?6@

archar2?6@

archar2?6@

archar2?6@

archar2?6@

Public

Public

Public

Public

Public

'reate table

#ooks?bname

varchar2?6@,aname

varchar2?6@,edition

varchar2?6@,price

varchar2?6@,summary

varchar2?2@B

=

8/16/2019 Finalvdb


3.3.2 0lass Diagra!s:

The class diagram eplains the structure of a system in terms of'lass, attributes

and their operations. The class is nothing but the abstract representation of a system. 0teplains the system in terms of set of objects the object is nothing but the instance of a

class. There are created dynamically once completion of the task the object is destroyed.

registrations

cid : string()

cpswd : st ring

cname : string

caddress : stringphone num : int

checks user details()

accepts registration()

user

uid : string

upswd : st ring

registers into site()

logs into site()

searches books()

selects books()

log outs()

admin

aid : stringapswd : st ring

controls website()

logs into site()

checks customer pswd()

maintains books details()

books

author : string

type of book : string

selects type of book()

selects author name()

database

db

paymentsuid : int

upswd : string

uaddress : string

draws the amount()

3ig4 6.24 'lass %iagram for !nline #ook *hop

+@

8/16/2019 Finalvdb


3.)D#na!ic /odels

3.).1 "e%uence Diagra!s:

The sequence diagrams mainly used to visuali/e the communication between the

set of the objects.

"e%uence Diagra!:

++

8/16/2019 Finalvdb


: cust

:registrations

: books : payments : admin : database

2: enter details

3: verify

4: enter user name and password

1: maintains

5: check details

: valid

!: permint access

": select type of book

#: display results

1$: places in cart

12: pays the amount

13: delivers report

11: payment details

3ig

4 6.64 *equence diagram for customer

"e%uence Diagra! for ad!in:

+2

8/16/2019 Finalvdb


: admin

:registrations

: database: books

1: enter details

2: check

3: verify

4: valid

!: display form

": fill form

5: add%delete%update

: perform action

#: return updates

1$: view orders for bboks

11: get orders

12: return orders list

13: display orders

3ig4 *equence %iagram for admin

3.).2 "tatechart Diagra!s:

+6

8/16/2019 Finalvdb


*tatechart diagram eplains each object different state and transitions. *tate is

nothing but set of values of an object transition is nothing but future state of an object.

3ig4 *tate 'hart %iagram for !nline #ook *hop

3.).3 ctivit# Diagra!s:

+8

8/16/2019 Finalvdb


Activity diagram eplains internal of set of activities. 0t is similar to flow chart

ecept that it contains the synchroni/ation. The synchroni/ation specifies completion of

one activity only the net activity will be started.

home

user

enter user

name and pwd

see books select books

display booksdisplay payment

details

pay cash

admin

enter user aname

and apwd

add books update books

e&it

valid

not valid

valid

not valid

3ig4 6.;4 Activity %iagram for !nline #ook *hop

). "#ste! Design Docu!ent:

+7

8/16/2019 Finalvdb


admin sub

system user subsystem

main system

update informationprovide information to user

Request for book information

).1 "ubs#ste! Deco!position:

This describes the decomposition into subsystems and the responsibilities of

each. This is the main product of system design.

5egistration *ubsystem4

0t looks after registration login details and allows profile viewing.

'ommunication *ubsystem4

The entire system can be decomposed into two subsystems. They are4

Admin subsystem4 0t is responsible for generation of logins, viewing details,

giving responses to the requests posted by users.

-ser subsystem4 0t is responsible for registrations, selecting the book and the

type of book.

3ig. *ubsystem decomposition for !nline #ook *hop

+;

8/16/2019 Finalvdb


).2Design oals:

*ystem designs the transformation of analysis model into a system design

model. %uring the system design developers defines the design goals of project and

decompose the system into smaller into subsystems that can be reali/ed by individual

teams. *trategic for building system such hardware software are selected.

i. ortabilit#:

3or programs to be dynamically downloaded to all the various types of

platforms that are connected to the 0nternet, some means of generating portable

eecutable code is needed .As you will see, the same mechanism that helps

ensure security also helps create portability. 0ndeed, Cavas solution to these two

problems is both elegant and efficient.

ii. "ecurit#:

>very time you that you download a DnormalE programB you are risking

a viral infection. Prior to Cava, most users did not download eecutable

programs frequently, and those who scanned them for viruses prior to eecution.

Most users still worried about the possibility of infecting their systems with a

virus. 0n addition, another type of malicious program eists that must be guarded

against. This type of program can gather private information, such as credit card

numbers, bank account balances, and passwords. Cava answers both these

concerns by providing a DfirewallE between a network application and your

computer.

iii. $obustness:

The multi)platform environment of the &eb places etraordinary

demands on a program, because the program must eecute reliably in a variety

of systems. The ability to create robust programs was given a high priority in the

design of Cava. Cava is strictly typed languageB it checks your code at compile

time and run time.

Cava virtually eliminates the problems of memory management and de)

allocation, which is completely automatic. 0n a well)written Cava program, all

run time errors can "and should "be managed by your program.

+:

8/16/2019 Finalvdb


iv. /e!or#:

This requires large amount of memory inorder to store all registered

member details.

,. Object Design Docu!ent:

,.1Object Design /odel:

• The entire system is projected with a physical diagram which specifics the

actual storage parameters that are physically necessary for any database to be

stored on to the disk. The overall systems eistential idea is derived from this

diagram.

+<

8/16/2019 Finalvdb


• The relation upon the system is structure through a conceptual >5)%iagram,

which not only specifics the eistential entities but also the standard relations

through which the system eists and the cardinalities that are necessary for the

system state to continue.

>5)%iagrams4

• The entity 5elationship %iagram ?>5% depicts the relationship between the

data objects. The >5% is the notation that is used to conduct the date modeling

activity the attributes of each data object noted is the >5% can be described

resign a data object descriptions.

•

The set of primary components that are identified by the >5% are

%ata object 5elationships

Attributes arious types of indicators.

• The primary purpose of the >5% is to represent data objects and their

relationships.

-nified Modeling Fanguage %iagrams4

• The unified modeling language allows the software engineer to epress an

analysis model using the modeling notation that is governed by a set of

syntactic semantic and pragmatic rules.

• A -MF system is represented using five different views that describe the

system from distinctly different perspective. >ach view is defined by a set of

diagram, which is as follows.

-ser Model iew4

• This view represents the system from the users perspective.

• The analysis representation describes a usage scenario from the end)

users perspective.

*tructural model view4

+=

8/16/2019 Finalvdb


• 0n this model the data and functionality are arrived from inside the system.

• This model view models the static structures.

#ehavioral Model iew4

0t represents the dynamic of behavioral as parts of the system, depicting the

interactions of collection between various structural elements described in the user

model and structural model view.

0mplementation Model iew4

0n this the structural and behavioral as parts of the system are represented as

they are to be built.

>nvironmental Model iew4

0n this the structural and behavioral aspects of the environment in which the

system is to be implemented are represented.

2@

8/16/2019 Finalvdb


4. ront *nd nd Back *nd ools

4.1 Details about ront *nd:

4.1.1 ront *nd or (ser Design Interface:

The entire user interface is planned to be developed in browser specific

environment with a touch of 0ntranet)#ased Architecture for achieving the %istributed

'oncept.

The browser specific components are designed by using the $TMF standards,

and the dynamism of the designed by concentrating on the constructs of the Cava

*erver Pages.

4.1.2 0o!!unication or Database 0onnectivit# ier:

The 'ommunication architecture is designed by concentrating on the

*tandards of *ervlets and >nterprise Cava #eans. The database connectivity is

established by using the Cava %ata #ase 'onnectivity.

The standards of three)tire architecture are given major concentration to keepthe standards of higher cohesion and limited coupling for effectiveness of the

operations.

4.1.3 eatures of the 5anguage used:

0n my project, 0 have chosen Java language for developing the code.

6ava4

0nitially the language was called as DoakE but it was renamed as DCavaE in +==7. The

primary motivation of this language was the need for a platform)independent ?i.e.,

architecture neutral language that could be used to create software to be embedded in

various consumer electronic devices.

Cava is a programmers language.

Cava is cohesive and consistent.

2+

8/16/2019 Finalvdb


>cept for those constraints imposed by the 0nternet environment, Cava gives

the programmer, full control.

3inally, Cava is to 0nternet programming where ' was to system programming.

pplications and pplets:

0t can react to the user input and dynamically change. An application is a

program that runs on our 'omputer under the operating system of that computer. 0t is

more or less like one creating using ' or 'GG. Cavas ability to create Applets makes it

important. An Applet is an application designed to be transmitted over the 0nternet and

eecuted by a Cava "compatible web browser. An applet is actually a tiny Cava

program, dynamically downloaded across the network, just like an image. #ut thedifference is, it is an intelligent program, not just a media file

eatures of 6ava:

"ecurit#:

>very time you that you download a DnormalE program, you are risking a viral

infection. Prior to Cava, most users did not download eecutable programs frequently,

and those who did scanned them for viruses prior to eecution. Most users still

worried about the possibility of infecting their systems with a virus. 0n addition,

another type of malicious program eists that must be guarded against. This type of

program can gather private information, such as credit card numbers, bank account

balances, and passwords. Cava answers both these

concerns by providing a DfirewallE between a network application and your

computer.

&hen you use a Cava)compatible &eb browser, you can safely download Cava

applets without fear of virus infection or malicious intent.

ortabilit#:

3or programs to be dynamically downloaded to all the various types of

platforms connected to the 0nternet, some means of generating portable eecutable

code is needed .As you will see, the same mechanism that helps ensure security also

helps create portability. 0ndeed, Cavas solution to these two problems is both elegant

and efficient.

22

8/16/2019 Finalvdb


he B#te code:

The key that allows the Cava to solve the security and portability problems is that

the output of Cava compiler is #yte code. #yte code is a highly optimi/ed set of

instructions designed to be eecuted by the Cava run)time system, which is called the

Cava irtual Machine ?CM. That is, in its standard form, the CM is an interpreter

for byte code.

Translating a Cava program into byte code helps makes it much easier to run a

program in a wide variety of environments. The reason is, once the run)time package

eists for a given system, any Cava program can run on it.

Although Cava was designed for interpretation, there is technically nothing about Cava

that prevents on)the)fly compilation of byte code into native code. *un has just

completed its Cust 0n Time ?C0T compiler for byte code. &hen the C0T compiler is a

part of CM, it compiles byte code into eecutable code in real time, on a piece)by)

piece, demand basis. 0t is not possible to compile an entire Cava program into

eecutable code all at once, because Cava performs various run)time checks that can

be done only at run time. The C0T compiles code, as it is needed, during eecution.

6ava7 irtual /achine 86/9:

#eyond the language, there is the Cava virtual machine. The Cava virtual machine is an

important element of the Cava technology. The virtual machine can be embedded

within a web browser or an operating system. !nce a piece of Cava code is loaded

onto a machine, it is verified. As part of the loading process, a class loader is invoked

and does byte code verification makes sure that the code thats has been generated by

the compiler will not corrupt the machine that its loaded on. #yte code verification

takes place at the end of the compilation process to make sure that is all accurate and

correct. *o byte code verification is integral to the compiling and eecuting of Cava

code.

Overall Description:

26

8/16/2019 Finalvdb


Cava .class

Picture showing the development process of CAA Program

Cava source code is located in a. Cava file that is processed with a Cava compiler called

javac. The Cava compiler produces a file called a. class file, which contains the byte

code. The. 'lass file is then loaded Cava programming uses to produce byte codes and

eecutes them. The first bo indicates that the across the network or loaded locally on

your machine into the eecution environment is the Cava virtual machine, which

interprets and eecutes the byte code.

6ava rchitecture:

Cava architecture provides a portable, robust, high performing environment for

development. Cava provides portability by compiling the byte codes for the Cava

irtual Machine, which is then interpreted on each platform by the run)time

environment. Cava is a dynamic system, able to load code when needed from amachine in the same room or across the planet.

0o!pilation of code:

&hen you compile the code, the Cava compiler creates machine code ?called byte

code for a hypothetical machine called Cava irtual Machine ?CM. The CM is

supposed to eecute the byte code. The CM is created for overcoming the issue of

portability. This machine is called Cava irtual Machine.

4.2 Details about Back *nd:

$ole Of Oracle In Database:

28

Cava source Cava byte code Cava M

8/16/2019 Finalvdb


!racle +@g is one of the many database services that plug into a client H server

model. 0t works efficiently to manage resources, a database information, among the

multiple clients requesting I sending.

"tructured -uer# 5anguage 8"-59:

• *JF is an inter)active language used to query the database and access data in

database. *JF has the following features4

• 0t is a unified language.

• 0t is a common language for relational database

• 0t is a non)procedural language.

Introduction oOracle4

!5A'F> is a comprehensive operating environment that packs the power of a

mainframe system into user microcomputer. 0t provides a set of functional programs that

user can use as tools to build structures and perform tasks. #ecause application developed

on oracle are completely portable to environment and then move it into a multi user

platform. -sers do not have to be an epert to appreciate !5A'F>, but the better user

understands the programmer, the more productivity and creativity you will use the tools it

provides.

hat is a$elational Database /anage!ent "#ste!:

A relational database management system ?5%#M* can perform a wide array of

tasks. 0t acts as a transparent interface between the physical storage and a logical

presentation of data. 0t provides a set of more or less fleible and sophisticates tools for

handling information. -ser can use this tool to4

%efine a database

Juery the database

Add, edit and delete data

Modify the structure of database

*ecure data from public access

'ommunicate within the networks

>port and 0mport data

#ecause it gives so much control over data, a relational %#M* can also save as the

foundation for products that generate application and etract data.

A %atabase Management system may be called fully relational if it supports4

27

8/16/2019 Finalvdb


+. 5elational %atabases and

2. A language that is at least as powerful as the relational algebra

%r. >.3.'odds 5ules.>.3.'odd specified a set of rules that an 5%#M* has to dofollowing +2 rules

+. Infor!ation rule: All information in a relational database including table names,

column names, and domain names is represented eplicitly by values in tables. &ith

this design speed and productivity will be improved.

2. uaranteed access rule: using a combination of table name, a primary key value and

a column name can access >very piece of data in a relational database. &ith this

productivity is improved since there is no need to resort to using physical pointers of

address and provides data independence.

6. "#ste!atic treat!ent of null values: The 5%#M* distinguishes between blanks

nulls in records and handles such values in consistent manner that produces correct

answers on comparison and calculations. &ith these users can distinguish results of

queriesHoperations that involve nulls, /eroes and blanks.

8. ctive on;line catalog based on <the relational !odel:The description of a database

and its contents are database tables and therefore can be queried on)line via the

database language. &ith this the %#As productivity is improved since the changes

are common in catalog to all tables for all queries and reports.

7. 0o!prehensive data sub;language rule: An 5%#M* language supports definitions

of tablesHviews. Juery and update data, integrity constraints, authori/ations,

definitions of transactions. &ith this user productivity is improved since there is a

single approach for all database operations.

;. ie= updating rule: Any view that is theoretically updateable can be updated using

5%#M*. &ith this data consistency is ensured since changes in the underlying tables

are transmitted to the view their support.

:. >igh;level insert7 update and delete: The 5%#M* supports insertion, updating

deletion at al table level. &ith this the performance is improved by optimi/ing the

path for eecution.

<. h#sical data independence: The eecution of adhoc requests and application

programs are not affected by the changes in the physical data access methods. &ith

this %#A can make changes in application programs or adhoc requests.

2;

8/16/2019 Finalvdb


=. 5ogical data independence: Fogical changes in tables and views do not require

changes in the application programs or in the format of adhoc requests. &ith this

databases can change and grow without changes in applications.

+@. Integrit# independence: *ince constraints are stored in system catalog, they can be

changed without changing application program. &ith this maintenance costs are

reduced since only system catalog need to be changed.

++. Distribution independence: Application programs and adhoc requests are not

affected by changes in the distribution of physical data. &ith this system reliability

will be improved since application programs will work even if the programs and dare

are shifted.

+2. 'on;"ubversion rule: 0f the 5%#M* has languages that access a record of a time it

cannot be used to bypass integrity. &ith this data integrity is achieved since the

system catalog is musts

a. 'ode defined a relationally complete set of operations taking one or more

relation as their operands. The operators are two groups4 the traditional set of

operators union, intersection, difference and 'artesian product and the special

operators selection, projection, join and division.

b. A fully relational %#M* has to support the above operations.

he Oracle *nviron!ent

!5A'F> is modular system that consists of the !5A'F> database and

several functional programs. !5A'F> tools had four kinds of works4

%atabase management

%ata access and manipulations

Programming

'onnectivity

Database /anage!ent ools:

This is usually ?known as 5%#M* by !5A'F> includes the core programs of

!racles database management system, the !5A'F> database with its associated tablesand views, which are stored in the !racles data dictionary and a group of helpful

2:

8/16/2019 Finalvdb


activities. The data dictionary sores information related to every facet of database system.

-ser names, user access rights, table storage information and auditing data for the disaster

recovery are all stored in the data dictionary.

Data ccess and /anipulations :

All of !racles data access and manipulation tools are firmly based on AK*0

standard *JF. 0n !racle, the tools that a user will use to access and manipulate data, has

well as to design or use applications. >ach provides separate point of entry and unique

speech to the !racle system

?. "creens

>o!e age:

2<

8/16/2019 Finalvdb


5ogin age:

2=

8/16/2019 Finalvdb


urchase Order age:

6@

8/16/2019 Finalvdb


urchase Order 5ist age:

6+

8/16/2019 Finalvdb


"tock (tili@ation age:

62

8/16/2019 Finalvdb


"tock ransfer age:

66

8/16/2019 Finalvdb


"tock lo= age:

68

8/16/2019 Finalvdb


0ities age:

67

8/16/2019 Finalvdb


ublishers age:

6;

8/16/2019 Finalvdb


0ategories age:

6:

8/16/2019 Finalvdb


Book age:

6<

8/16/2019 Finalvdb


Bookshop 5ogin age:

6=

8/16/2019 Finalvdb


*ntering Details age:

8@

8/16/2019 Finalvdb


urchase Order Detail age:

8+

8/16/2019 Finalvdb


82

8/16/2019 Finalvdb


A. $eports

5ist of Book age:

86

8/16/2019 Finalvdb


urchase Order age:

88

8/16/2019 Finalvdb


(tili@ation Book age:

87

8/16/2019 Finalvdb


0it# "tock (tili@ation age:

8;

8/16/2019 Finalvdb


Book ransfer age:

8:

8/16/2019 Finalvdb


. "ource 0ode

d!in page:

<!DOCTYPE html>

<%@page import="java.sql." %>

<%@page import="ooshop." %>

<%@page import="java.#til." %>

<html>

<% $trig t&pe = '$trig(sessio.get)ttri#te'"t&pe"(*

i+'t&pe.eq#als'"),miistrator"( -- t&pe.eq#als'"$tore aager"((

/

%>

<hea,>

<li rel="st&lesheet" t&pe="te0t12ss" hre+="2ss1st&le.2ss">

<s2riptsr2="js1jq#er&34.45.6.mi.js"><1s2ript>

<s2riptsr2="js1jq#er&.+orm.js"><1s2ript>

<s2riptsr2="js1vali,atios.js"><1s2ript>

<s2ript t&pe="te0t1javas2ript" lag#age="javas2ript">

7',o2#met(.rea,&'+#2tio'(

/

8i,o8.histor&.+or8ar,'4(*

9(*

<1s2ript>

8<

8/16/2019 Finalvdb


<1hea,>

<o,&>

<tale 2lass=:mai:>

<jsp;i2l#,e page="1ea,er.jsp" +l#sh="tr#e" 1>

<tr height="5">

<t, 2lass=:2eter: 8i,th=:4%: valig=:top: >

<r1>

<jsp;i2l#,e page="1Optios.jsp" +l#sh="tr#e" 1>

<1t,>

<t, 2lass=:2eter: 8i,th=:?%: valig=:top: >

<r1>

<tale 2lass=:large3list: >

<tr> <t,>

<,iv i,=:2eter:>

<h6> Ael2ome <1h6>

<1,iv>

<1t,><1tr>

<1tale>

8=

8/16/2019 Finalvdb


<r1>

<1t,>

<jsp;i2l#,e page="1Booter.jsp" +l#sh="tr#e" 1>

<1tale>

<1o,&>

<% 9 %>

7@

8/16/2019 Finalvdb


0usto!er age:

<!DOCTYPE html>

<%@page import="java.sql." %>

<%@page import="ooshop." %>

<%@page import="java.#til." %>

<html>

<% $trig t&pe = '$trig(sessio.get)ttri#te'"t&pe"(*

i+'t&pe.eq#als'"C#stomer"((

/

%>

<hea,>

<li rel="st&lesheet" t&pe="te0t12ss" hre+="2ss1st&le.2ss">

<s2riptsr2="js1jq#er&34.45.6.mi.js"><1s2ript>

<s2riptsr2="js1jq#er&.+orm.js"><1s2ript>

<s2riptsr2="js1vali,atios.js"><1s2ript>

<s2ript t&pe="te0t1javas2ript" lag#age="javas2ript">

7',o2#met(.rea,&'+#2tio'(

/

8i,o8.histor&.+or8ar,'4(*

7'".8ise"(.2hage'+#2tio'(

/

7'"2eter"(.loa,' "ie8ooss.jspF8ise="G 7

'this(.val'( (*

9(*

7+

8/16/2019 Finalvdb


9(*

+#2tio loa,' 2o,e (

/

7' "2eter" (.loa,' :ooDetails.jspF2o,e=:G2o,e (*9

+#2tio get' #rl (

/

7' "2eter" (.loa,' #rl (*

9

+#2tio set' #rl (

/

7':templete:(.attr':a2tio:H #rl (*

7':templete:(.attr':metho,:H :post: (*

7':templete:(.aja0Borm'

/

target; :2eter:

9(.s#mit'(*

9

<1s2ript>

<1hea,>

<o,&>

<tale 2lass=:mai:>

<jsp;i2l#,e page="1ea,er.jsp" +l#sh="tr#e" 1>

<tr height="65">

72

8/16/2019 Finalvdb


<t, 2lass=:2eter: 8i,th=:4%: valig=:top: >

<r1>

<jsp;i2l#,e page="1Optios.jsp" +l#sh="tr#e" 1>

<1t,>

<t, 2lass=:2eter: 8i,th=:?%: valig=:top: >

<r1>


<tr> <t,>

<,iv i,=:2eter:>

<h><spa><%= req#est.getParameter'"message"( %><1spa><1h>

<jsp;i2l#,e page="1ie8ooss.jspF8ise=)ll" +l#sh="tr#e" 1>

<1,iv>

<1t,><1tr>

<1tale>

<r1>

<1t,>

<t, 2lass=:2eter: 8i,th=:4I%: valig=:top:>

<r1>


<tr 2lass=:alt: > <t, alig=:2eter:> Categories<1t,> <1tr>

76

8/16/2019 Finalvdb


<tr><t,><ip#t t&pe=:ra,io: ame=:8ise: 2lass=:8ise: val#e=:)ll: 2he2e,1>

)ll <1t,><1tr>

<% tr&/

Coe2tio 2o = Coe2tioPool.opeCoe2tio'(*

$tatemet st = 2o.2reate$tatemet'(*

Jes#lt$etrs = st.e0e2#teK#er&' "sele2t 2ategor&Li, H ame +rom

2ategories or,er & ame" (*

8hile'rs.e0t'( (

/

$trig 2o,e = rs.get$trig'"2ategor& i,"(*

$trig ame = rs.get$trig'"ame"(*

o#t.pritl' "<tr><t,><ip#t t&pe=:ra,io: ame=:8ise:

2lass=:8ise: val#e=:"G 2o,e G": 1>"G ame G "<1t,><1tr>" (*

9

Coe2tioPool.2loseCoe2tio' 2o (*

92at2h' E02eptio e (

/

$&stem.o#t.pritl' " $tates ; " G e (*

9

%>

<1tale>

<1t,><1tr>

<jsp;i2l#,e page="1Booter.jsp" +l#sh="tr#e" 1>

<1tale>

<1o,&>

78

8/16/2019 Finalvdb


<% 9 %>

<html>

1<.esting

Testing is the process of detecting errors. Testing performs a very critical role for

quality assurance and for ensuring the reliability of software. The results of testing are used

later on during maintenance also.

esting Objectives:

The main objective of testing is to uncover a host of errors, systematically and with

minimum effort and time. *tating formally, we can say,

Testing is a process of eecuting a program with the intent of finding an error.

A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if it eists.

The tests are inadequate to detect possibly present errors.

The software more or less confirms to the quality and reliable standards.

1<.1 (nit esting:

-nit testing focuses verification effort on the smallest unit of software i.e. the

module. -sing the detailed design and the process specifications testing is done to

uncover errors within the boundary of the module. All modules must be successful in the

unit test before the start of the integration testing begins.

0n this project each service can be thought of a module. There are so many

modules like Fogin, $&Admin, MasterAdmin, Kormal -ser, and PManager. Living

different sets of inputs has tested each module. &hen developing the module as well as

finishing the development so that each module works without any error. The inputs are

validated when accepting from the user.

0n this application developer tests the programs up as system. *oftware units in a

system are the modules and routines that are assembled and integrated to form a specific

function. -nit testing is first done on modules, independent of one another to locate

errors. This enables to detect errors. Through this errors resulting from interaction

betweenmodules initially avoided.

77

8/16/2019 Finalvdb


11. 0onclusion

0n this project we eplained how an !KF0K> #!! *$!P can be designed to

provide an easy interface for the customers to know about various books and they can easily

find them through our site and they can easily buy them through online.

This reduces the burden for customer by going to book stores and searching for books

and it saves time also by visiting online.

!ur project also met all the requirements specified in *oftware 5equirement

*pecifications and can also handle various runtime errors caused by irrelevant inputs

given by both student and the administrator. Possible future etensions can also be made to

this system.

7;

8/16/2019 Finalvdb


12.Bibliograph#

• !bject oriented software engineering "#ernd #ruegge, Allen $. %utoit

• &eb technology and design " '. (avier

•$ead first *ervest and C*P)!5eilly, #ryan #asham, athy *ierra and #ert #ates

&ebsites4

+. www.w6schools.com

2.www.projects)forum.com

6. www.uml)diagrams.org

http://www.w3schools.com/

http://www.projects-forum.com/

http://www.uml-diagrams.org/

http://www.projects-forum.com/

http://www.uml-diagrams.org/

http://www.w3schools.com/

finalvdb

Documents