Online Shopping Mall project

Surjyendu Ray,
Suvendu Bhattacharya,
Sandip Shaw,
Souvik Sett
Web Application Final year Project
SkyNet
Online Shopping Mall
PROJECT REPORT
Team name: - SkyNet
Version: - 1.0
http://osmlite.googlecode.com SkyNet, 2009 Page 2
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.! "e#initions, $cronyms and $%%re&iations 9
1.' (e#erences 10
1.) *echnologies to %e used 10
1.+ ,&er&ie- 10
2. ,&erall "escription 10
2.1 Product perspecti&e 10
2.2 Product #unctions 11
2.! .ser characteristics 11
2.' /onstraints 12
2.) .se0/ase 1odel Sur&ey 12
2.+ $rchitecture diagram 12
12
2.2 "ata%ase design 1
2. $ssumptions and "ependencies 19
!. Speci#ic (e3uirements 19
!.1 .se0/ase (eports 19
'. So#t-are System $ttri%utes !)
'.2.1 $&aila%ility !+
). $/*I,N S45.4N/4S !2
http://osmlite.googlecode.com SkyNet, 2009 Page !
CERTIFICATION
*his is to certi#y that the pro6ect entitled 7Online Shopping Mall8 is a
%ona #ide record o# -ork done %y:
Surjyendu Ray: -
.
Sandip Shaw: -
.
Suvendu Bhattacharya:-
..
Souvik Sett:-

.nder my guidance and super&ision, su%mitted as partial #ul#illment o# the

re3uirements #or the a-ard o# Bachelor of Technology degree in o!puter
Science " #ngineering %y 9est :engal .ni&ersity o# *echnology.
;;;;;;;;;. ;;;.;.;;;;;;;;;;;;;;;;;;;;;;;;
$r. %Mr&.' (nanya )anjilal
(SS*ST(+T ,RO-#SSOR %*T $#,(RTM#+T'
:.P.P,""$( INS*I*.*4 ,< 1$N$=414N*
(+$ T#.+O/O01
http://osmlite.googlecode.com SkyNet, 2009 Page '
Project Synopsis
Online Shopping Mall
Description of the Project
*he ,nline Shopping 1all >,S1? application ena%les &endors to set up online
shops, customers to %ro-se through the shops, and a system administrator to
appro&e and re6ect re3uests #or ne- shops and maintain lists o# shop categories.
$lso on the agenda is designing an online shopping site to manage the
items in the shop and also help customers purchase them online -ithout ha&ing to
&isit the shop physically.
,ur online shopping mall -ill use the internet as the sole method #or
selling goods to its consumers. *he consumer -ill %e in complete control o#
his/her shopping e@perience %y using the 7unique storefront8 concept. Shopping
-ill %e highly personaliAed and the mall -ill pro&ide lo-er prices than most
competitors. *his, in %rie#, is a description o# our product -hich -ill sho-case a
complete shopping e@perience in a small package.
Purpose
*oday the internet and its %oom ha&e created a ne- economic scenario
that not only stresses on the classical concept o# the 7product8 %ut also on
the modern concept o# 7service8. It is this le&el o# ser&ice that dictates
-hether a commercial &enture -ill succeed or not in the market. *o
pro&ide a high accessi%ility o# ser&ice -e -ill design the online shopping
-e%site, so that potential customers need not go to a physical shop to %uy
products or ser&ices. *hey 6ust need to online to complete their purchases.
.nlike the pre&ailing 7%rick and mortar8 shops -hich ha&e physical
e@istence, -e -ill operate solely #rom cy%erspace.

1ost current systems ha&e a physical #oundation that is the root cause to
3uite a num%er o# pro%lems. :y maintaining multiple store #ronts, itsel#
%eing an e@pensi&e proposition, store prices are #orced to rise. *hus, %y
using our product, our clientsB competitors are at a disad&antage %ecause
their costs are signi#icantly higher than our costs, allo-ing our clients to
sell the same goods at a lo-er price. $s people %ecome more accustomed
to using the internet, they &ie- ordering products and ser&ices online as a
time0sa&ing and cost0sa&ing e@perience, -hich is the &ery essence o# our
online shopping system.
http://osmlite.googlecode.com SkyNet, 2009 Page )
*his pro6ect en&isages %ridging the gap %et-een the seller, the retailer and the
customer. $ &ery high #le@i%ility is %eing maintained in the design process so that
this pro6ect can take the #ollo-ing path : 0
$ multiple merchant &enue -ith each merchant ha&ing his/her o-n
-indo- -hich the customer can &isit to %ro-se and su%se3uently
%uy the products #rom
1aintaining the deli&era%le goods as -ell as ser&ices through single or multiple
-indo-s is also on the agenda.

Target users
(Tentative list only)
Mall !"#inistrator *he 1all $dministrator is the super user
and has complete control o&er all the acti&ities that can %e
per#ormed. *he application noti#ies the administrator o# all shop
creation re3uests, and the administrator can then appro&e or re6ect
them. *he administrator also manages the list o# a&aila%le product
categories. *he administrator can also &ie- and delete entries in
the guest%ook.
Shop O$ner $ny user can su%mit a shop creation re3uest
through the application. 9hen the re3uest is appro&ed %y the 1all
$dministrator, the re3uester is noti#ied, and #rom there on is gi&en
the role o# Shop ,-ner. *he Shop ,-ner is responsi%le #or setting
up the shop and maintaining it. *he 6o% in&ol&es managing the su%0
categories o# the items in the shop. $lso, the shop o-ner can add
or remo&e items #rom his shop. *he Shop ,-ner can &ie-
di##erent reports that gi&e details o# the sales and orders speci#ic to
his shop. *he Shop ,-ner can also decide to close shop and
remo&e it #rom the mall.
Mall Custo#er%&uests $ 1all /ustomer can %ro-se through
the shops and choose products to place in a &irtual shopping cart.
*he shopping cart details can %e &ie-ed and items can %e remo&ed
#rom the cart. *o proceed -ith the purchase, the customer is
prompted to login. $lso, the customer can modi#y personal pro#ile
in#ormation >such as phone num%er and shipping address? stored
%y the application. *he customer can also &ie- the status o# any
pre&ious orders.
#!ployee&:
Purchase department under a Purchase manager to o&erlook
purchasing acti&ities i# -arehousing needs arise.
http://osmlite.googlecode.com SkyNet, 2009 Page +
Sales department under a Sales manager -ho -ill look
a#ter the sale o# products and ser&ices.
$ccounts department under an $ccounts manager to look
a#ter the accounting acti&ities o# the enterprise.
http://osmlite.googlecode.com SkyNet, 2009 Page 2
Soft$are Re'uire#ents
() *ntro"uction
()( Purpose
*he ,nline Shopping 1all >,S1? -e% application is intended to pro&ide
complete solutions #or &endors as -ell as customers through a single get -ay
using the internet as the sole medium. It -ill ena%le &endors to setup online shops,
customer to %ro-se through the shop and purchase them online -ithout ha&ing to
&isit the shop physically. *he administration module -ill ena%le a system
administrator to appro&e and re6ect re3uests #or ne- shops and maintain &arious
lists o# shop category
*his document is meant to delineate the #eatures o# ,S1, so as to ser&e as a guide
to the de&elopers on one hand and a so#t-are &alidation document #or the
prospecti&e client on the other.
()+ Scope
Initial #unctional re3uirements -ill %e: 0
Secure registration and pro#ile management #acilities #or /ustomers
:ro-sing through the e01all to see the items that are there in each category o#
products like $pparel, Citchen accessories, :ath accessories, <ood items etc.
$de3uate searching mechanisms #or easy and 3uick access to particular products
and ser&ices.
/reating a Shopping cart so that customers can shop DnB no. o# items and checkout
#inally -ith the entire shopping carts.
(egular updates to registered customers o# the ,S1 a%out ne- arri&als.
.ploading D1ost PurchasedB Items in each category o# products in the Shop like
$pparel, Citchen accessories, :ath accessories, <ood items etc.
Strategic data and graphs #or $dministrators and Shop o-ners a%out the items that
are popular in each category and age group.
1aintaining data%ase o# regular customers o# di##erent needs.
Shop employees are responsi%le #or internal a##airs like processing orders, assure
home deli&ery, getting customerEs deli&ery0time #eed%ack, updating orderEs status
and ans-ering clientEs 3ueries online.
<eed%ack mechanism, so that customers can gi&e #eed%ack #or the product or
ser&ice -hich they ha&e purchased. $lso #acility rating o# indi&idual products %y
rele&ant customers. $lso #eed%ack can %e gi&en on the per#ormance o# particular
&endors and the entire mall as -ell.
$de3uate payment mechanism and gate-ay #or all popular credit cards, che3ues
and other rele&ant payment options, as a&aila%le #rom time to time.
http://osmlite.googlecode.com SkyNet, 2009 Page
<or the pre&ious paragraph, depicting the #unctions o# the system, #rom the
perspecti&e o# the &arious users o# the system, the #ollo-ing colour codes has
%een used :
(4" #or administrator
:F.4 #or customer o# the shopping mall
=(44N #or the employees.
Initial non #unctional re3uirements -ill %e: 0
Secure access o# con#idential data >userBs details?. SSF can %e used.
2' G 2 a&aila%ility
:etter component design to get %etter per#ormance at peak time
$d&ertisement space -here it -ill e##ecti&ely catch the customerBs attention and
as a source o# re&enue.
In addition to the a%o&e mentioned points, due to the highly e&ol&ing nature o# the
pro6ect, the #ollo-ing are planned to %e deli&ered i# deemed necessary:
9arehousing -ithin the &ery am%its o# the pro6ect
1ore payment gate-ays.
"ynamic price model %y -hich prices can %e changed %ased on demand and
supply
"ynamic Store#ront: 4ach customer -ill ha&e a -e% page personaliAed %ased on
his or her recent purchases. *his is the e3ui&alent o# ha&ing a uni3ue store#ront
#or each customer in hopes o# dra-ing in as many return customers as possi%le.
*his list is %y no means, a #inal one. *he #inal list -ill %e dictated %y
implementation constraints, market #orces and most importantly, %y end user
demands #or -hom this is %eing %uilt.
(), Definitions- !crony#s an" !bbre.iations
SF$: Ser&ice Fe&el $greement or SF$ is a #ormal -ritten agreement made
%et-een t-o parties, the ser&ice pro&ider H the ser&ice recipient. It de#ines the
term o# engagement 0 the #undamental rules that -ill go&ern the relationship.
4I:: 4nterprise Ia&a :eans.
I$J$ 44: Ia&a 4nterprise 4dition ) is a programming plat#ormK part o# the Ia&a
Plat#orm0#or de&eloping and running distri%uted multi0tier architecture Ia&a
applications, %ased largely on modular so#t-are components running on an
application ser&er.
L**P: Lyperte@t *rans#er Protocol is a transaction oriented client/ser&er protocol
%et-een a -e% %ro-ser H a 9e% Ser&er.
L**PS: Secure Lyperte@t *rans#er Protocol is a L**P o&er SSF >secure socket
http://osmlite.googlecode.com SkyNet, 2009 Page 9
layer?.
*/P/IP: *ransmission /ontrol Protocol/Internet Protocol, the suite o#
communication protocols used to connect hosts on the Internet. */P/IP uses
se&eral protocols, the t-o main ones %eing */P and IP.
()/ References
I444 S(S <ormat
()0 Technologies to be use"
Programming languages:
I$J$ 44: Ia&a 4nterprise 4dition is a programming plat#ormK part o# the Ia&a
Plat#orm0#or de&eloping and running distri%uted multi0tier architecture Ia&a
applications, %ased largely on modular so#t-are components running on an
application ser&er.
L*1F, G1F: Lyper *e@t 1arkup Fanguage and 4@tensi%le markup Fanguage
are the predominant markup languages #or -e% pages. It pro&ides a means to
descri%e the structure o# te@t0%ased in#ormation in a document and to supplement
that te@t -ith interacti&e #orms, em%edded images, and other o%6ects.
Ia&aScript: $ client side scripting language used to create dynamic -e% content
and user inter#ace.
*ools H "e&elopment 4n&ironment
$pache *omcat +.0.1 Ser&er: $pache *omcat is a Ser&let container de&eloped
%y the $pache So#t-are <oundation >$S<?. *omcat implements the Ia&a Ser&let
and the Ia&aSer&er Pages >ISP? speci#ications #rom Sun 1icrosystems, and
pro&ides a Mpure Ia&aM L**P -e% ser&er en&ironment #or Ia&a code to run.
4/FIPS4 I244: 4clipse is a toolkit -hich is designed #or the creation o# comple@
pro6ects, pro&iding #ully dynamic -e% application utiliAing 4I:Bs. *his consist o#
4I: tools , /1P ,data mapping tools H a uni&ersal test client that is designed to
aid testing o# 4I:Bs.
()1 O.er.ie$
*he rest o# this S(S is organiAed as #ollo-s: Section 2 gi&es an o&erall
description o# the so#t-are. It gi&es -hat le&el o# pro#iciency is e@pected o# the
user, some general constraints -hile making the so#t-are and some assumptions
and dependencies that are assumed. Section ! gi&es speci#ic re3uirements -hich
the so#t-are is e@pected to deli&er. <unctional re3uirements are gi&en %y &arious
use cases. Some per#ormance re3uirements and design constraints are also gi&en.
+) O.erall Description
+)( Pro"uct perspecti.e
,S1 is aimed to-ards the &endors -ho -ant to reach out to the ma@imum cross0
section o# customer and common people -ho can %e potential customer. *his
http://osmlite.googlecode.com SkyNet, 2009 Page 10
pro6ect en&isages %ridging the gap %et-een the seller, the retailer and the
customer. ,S1 should %e user0#riendly, D3uick to learnB and relia%le so#t-are #or
the a%o&e purpose. ,S1 is intended to %e a stand0alone product and should not
depend on the a&aila%ility o# other so#t-are. It should run on %oth .NIG and
9indo-s %ased plat#orm.
+)+ Pro"uct functions
.ser: 1all $dministrator
<unctions: *he 1all $dministrator is the super user and has complete control
o&er all the acti&ities that can %e per#ormed. *he application noti#ies the
administrator o# all shop creation re3uests, and the administrator can then appro&e
or re6ect them. *he administrator also manages the list o# a&aila%le product
categories. *he administrator can also &ie- and delete entries in the guest%ook.
.ser: Shop ,-ner
<unctions: $ny user can su%mit a shop creation re3uest through the application.
9hen the re3uest is appro&ed %y the 1all $dministrator, the re3uester is noti#ied,
and #rom there on is gi&en the role o# Shop ,-ner. *he Shop ,-ner is
responsi%le #or setting up the shop and maintaining it. *he 6o% in&ol&es managing
the su%0categories o# the items in the shop. $lso, the shop o-ner can add or
remo&e items #rom his shop. *he Shop ,-ner can &ie- di##erent reports that gi&e
details o# the sales and orders speci#ic to his shop. *he Shop ,-ner can also
decide to close shop and remo&e it #rom the mall.
.ser: 1all /ustomer/=uests
<unctions: $ 1all /ustomer can %ro-se through the shops and choose products
to place in a &irtual shopping cart. *he shopping cart details can %e &ie-ed and
items can %e remo&ed #rom the cart. *o proceed -ith the purchase, the customer
is prompted to login. $lso, the customer can modi#y personal pro#ile in#ormation
>such as phone num%er and shipping address? stored %y the application. *he
customer can also &ie- the status o# any pre&ious orders, and cancel any order
that has not %een shipped yet.
.ser: 4mployees
<unctions: Purchase department under a Purchase manager to o&erlook
purchasing acti&ities i# -arehousing needs arise.
<unctions: Sales department under a Sales manager -ho -ill look a#ter the sale o#
products and ser&ices, the most important acti&ity.
<unctions: $ccounts department under an $ccounts manager to look a#ter the
accounting acti&ities o# the enterprise
+), 2ser characteristics
*he user should %e #amiliar -ith the Shopping 1all related terminology like
Shopping cart//hecking out/*ransaction etc.
http://osmlite.googlecode.com SkyNet, 2009 Page 11
*he user should %e #amiliar -ith the Internet.
+)/ Constraints
*here is no maintaina%ility o# %ack up so a&aila%ility -ill get a##ected.
Fimited to L**P/L**PS.
(eal0li#e credit card &alidation and :anking system is not implemented.
No multilingual support
+)0 2se3Case Mo"el Sur.ey
-igure 2: 3&er hierarchy
http://osmlite.googlecode.com SkyNet, 2009 Page 12
-igure 4: 3&e ca&e diagra! for u&to!er " 5i&itor
-igure 6: 3&e ca&e diagra! for Shop owner
http://osmlite.googlecode.com SkyNet, 2009 Page 1!

-igure 7: 3&e ca&e diagra! for #!ployee&
-igure 8: 3&e ca&e diagra! for (d!ini&trator
http://osmlite.googlecode.com SkyNet, 2009 Page 1'
=i&en %elo- is an o&erall picture o# the system, as depicted in the a%o&e use0case diagrams:
(d!ini&trator:
$ata9a&e Manage!ent: /ontrol the data%ase and keep track o# all records o# customers and
employee details.
ontact and 0iving ,er!i&&ion to 5endor&: /ontact -ith the &endors and gi&e permission to
sell their product under the site a#ter testing the productBs 3uality.
5iew all detail&: Jie- the details o# all employees and control the -hole site.
(dverti&ing the Site: (esponsi%le #or making ad&ertisements #or the site.
u&to!er&:
/ogin: /ustomers must ha&e a &alid login id to enter into the site.
Regi&tration: Ne- users can sign up %y creating ne- I".
5iew and edit Own $etail&: /an &ie-/edit his personal details, payment details, and details
a%out ser&ices pro&ided.
hoo&ing and co!paring product&: /an &ie- all a&aila%le products and can compare them and
make a choice #or purchasing products.
,urcha&ing: /an purchase any product through &alid credit card.
0iving -eed9ack to u&to!er are: /an gi&e #eed%ack to the 2'G2 /ustomer /are Ser&ice
center a%out their impression #or the site and ser&ices.
5i&itor&:
5i&iting the Site: /an only &isit the site -ithout registration.
Regi&ter :
Shop Owner:
Taking ,er!i&&ion fro! (d!ini&trator: Jendors must take permission #rom the $dministrator
#or selling their products under the site. $dministrator -ill test productBs 3uality according to its
market price to permit &endor #or selling purpose.
on&ulting with (d!ini&trator: /an consult -ith the $dministrator regarding productBs 3uality
and ad&ertisements.
(dverti&ing 5endor:& Own ,roduct&: (esponsi%le #or making ad&ertisements o# his products,
%ut the site -ill not %e responsi%le #or any kind o# ad&ertisements a%out products.
http://osmlite.googlecode.com SkyNet, 2009 Page 1)
Sale& Manager:
5iew cu&to!er detail&: Jie- the personal details o# the customer.
Managing Sale& to u&to!er&: (esponsi%le #or properly allocating the selected product
according to the customerBs choice and deli&ering product to the customer.
5iew ,roduct Stock&: Ceep track o# each product itemBs stocks #or selling purpose.
ontacting with (d!ini&trator: (esponsi%le #or in#orming administrator -hen any product
itemBs stock goes under the minimum le&el.
,urcha&e Manager:
on&ulting with (d!ini&trator: *aking permission #rom the $dministrator #or the product to
%e purchased #rom &endor.
,roduct Stock Manage!ent: (esponsi%le #or managing stocks o# each product items.
(ccount& Manager:
Regulating ,ay!ent&: Ceep track o# all the payment transactions made %y the customers and
update the payment in#ormation.
on&ulting with Bank&: (esponsi%le #or contacting the %anks #or the &alidation o# the a/c
num%er pro&ided %y the customer -hile purchasing and make the transaction #rom the gi&en a/c.
on&ulting with (d!ini&trator: /onsult -ith the $dministrator a%out the payment details o#
the customers #or the updating o# the data%ase.
u&to!er are:
0etting -eed9ack fro! the u&to!er&: (esponsi%le #or recei&ing complaints, 3ueries and
#eed%ack #rom the customers.
,roviding Solution& to u&to!er&: Pro&ide #easi%le solutions to the customers on their
complaints and 3ueries.
http://osmlite.googlecode.com SkyNet, 2009 Page 1+
+)1 !rchitecture "iagra#

http://osmlite.googlecode.com SkyNet, 2009 Page 12
+)4 Database "esign
http://osmlite.googlecode.com SkyNet, 2009 Page 1
+)5 !ssu#ptions an" Depen"encies
*he details related to the product, customer, payment and ser&ice transaction
pro&ided manually.
$dministrator is created in the system already.
(oles and tasks are prede#ined.
,) Specific Re'uire#ents
,)( 2se3Case Reports
$dministrators:
$ata9a&e Manage!ent: /ontrol the data%ase and keep track o# all records o# customers and
employee details.
,recondition&: $dministrator is already logged in.
+or!al flow of event&:
1? Normal check o# the data%ase %y the $dministrator.
2? .pdating the data%ase >i# re3uired?.
(lternate flow of event&: None.
,o&t ondition: $l-ays updated data%ase.
ontact and 0iving ,er!i&&ion to 5endor&: /ontact -ith the &endors and gi&e permission
to sell their product under the site a#ter testing the productBs 3uality.
,recondition&: 1? $dministrator is already logged in.
2? Jendor contacts -ith $dministrator.
+or!al flow of event&: Negotiation is success#ul.
(lternate flow of event&: Negotiation is #ailed.
,o&t ondition: possi%ilities o# ne- product items
ontacting Bu&ine&& ,artner&: (esponsi%le #or contacting -ith :usiness Partners -ho -ill
sponsor the site and help in conducting the %usiness process.
,recondition&: 1? $dministrator is already logged in.
2? :usiness Partner contacts -ith $dministrator.
+or!al flow of event&: Negotiation is success#ul.
http://osmlite.googlecode.com SkyNet, 2009 Page 19
(lternate flow of event&: Negotiation is #ailed.
,o&t ondition: possi%ilities o# ne- sponsors and raise in
in&estments.
(dverti&ing the Site: (esponsi%le #or making ad&ertisements #or the site.
,recondition&: $dministrator is already logged in.
+or!al flow of event&: 1? /ontacting di##erent media.
2? 1aking ad&ertisements #or the site.
(lternate flow of event&: None.
,o&t ondition: populariAing the site.
5iew all detail&: Jie- the details o# all employees and control the -hole site.
,recondition&: $dministrator is already logged in.
+or!al flow of event&:
1? $dministrator &ie-s the details o# all employees.
2? /ontrols the -hole site.
(lternate flow of event&: None.
,o&t ondition: 4&erything is completely under control.
http://osmlite.googlecode.com SkyNet, 2009 Page 20
http://osmlite.googlecode.com SkyNet, 2009 Page 21
/ustomers:
,recondition&: /ustomer must ha&e a &alid user I".
+or!al flow of event&:
1? Fog in.
2? Jie- and edit ,-n "etails
!? /hoosing and comparing products
'? Purchasing
)? Fogout
(lternate flow of event&:
1? Ne- customer registration
2? /omplaining to /ustomer /are
,o&t ondition: $ happy /ustomerN
http://osmlite.googlecode.com SkyNet, 2009 Page 22
Jisitors:
,recondition&: $dministrator is already logged in.
+or!al flow of event&:Jisiting the Site
(lternate flow of event&: None.
,o&t ondition: Proper separation %et-een customers and -indo-0
shoppers.
Jendor:
,recondition&: /an consult -ith the $dministrator regarding productBs
3uality and ad&ertisements.
+or!al flow of event&: /an consult -ith the $dministrator regarding
productBs 3uality and ad&ertisements.
(lternate flow of event&: /an lea&e the pro6ect.
,o&t ondition: Jarious attracti&e items #or customers.
http://osmlite.googlecode.com SkyNet, 2009 Page 2!
Sales 1anager:
Sales 1anager can &ie- customer details and responsi%le #or managing sales to customers,
&ie-ing product stocks and contacting -ith the administrator.
5iew u&to!er $etail&: Jie- personal details o# the customers.
Managing Sale& to u&to!er&: (esponsi%le #or properly allocating the
selected product according to the customerBs choice and deli&ering product
to the customer.
5iew ,roduct Stock&: Ceep track o# each product itemBs stocks #or
selling purpose.
ontacting with (d!ini&trator: (esponsi%le #or in#orming administrator -hen any product
itemBs stock goes under the minimum le&el.
+a!e of the u&e ca&e: Jie- customer details.
$e&cription: Jie- the personal details o# the selected customer.
,recondition: Sales manager is already logged in.
+or!al flow of event&:
Select customer.
*he details o# customer &ie-ed.
(lternate flow of event&: None
,o&t condition: None.
http://osmlite.googlecode.com SkyNet, 2009 Page 2'
O O :x.exc_:
_eox
O _:_eox.
_ooo:
O oc_c_:
_eox
M(+(0*+0 S(/#S TO 3STOM#RS:
;;include<< $dd purchase details
;;include<<
.pdate purchase
PPe@tendQQ 1anage purchase ;;include<<
details Jie- purchase details
PPe@tendQQ
1anaging sales ;;include<<
/reate an SF$
;;include<<
1anage ser&ice le&el agreement PPincludeQQ

Jie- an SF$
.pdate SF$
+a!e of the u&e ca&e: $dd/update and &ie- purchase details.
$e&cription: Store the details o# the product sold, customer id, supply details and any changes in
product details can %e made and &ie- purchase details.
,recondition: Sales 1anager is already logged in. *he customer is registered and the products are
already present.
+or!al flow of event&:
Select a customer.
Select a product.
4nter/update purchase details.
Sa&e ne- data.
(lternate flow of event&:
I# the customer is not registered, ask #or registration.
I# the product is out o# stock, send error message.
,o&t condition: Sale id is generated.
http://osmlite.googlecode.com SkyNet, 2009 Page 2)
+a!e of the u&e ca&e: /reate/update a ser&ice le&el agreement.
$e&cription: Store the details o# the ser&ices pro&ided to a customer, duration o# the ser&ices
and details o# the terms and conditions
,recondition: Sales manager is already logged in. *he product and the ser&ices to %e pro&ided are
already present.
+or!al flow of event&:
Select product.
Select ser&ices
http://osmlite.googlecode.com SkyNet, 2009 Page 2+
OO O oc_c_:_
eox
OOO O oc_xe.
_c_
O O O :x.exxoo:_
xo_oeq
O O O q.xxexo::o
o
oo:_x
.
_ooo.o
_oeq
O _e_x
oo:_
x.
ooooo
ooo_:
O _e_oo
oooo
o
OOOOO O ooxe._c
_
OOO R O .._.o_.o
_o
$&aila%le
OOO O O _o_xcoo:._o
oo:
4nter details o# the ser&ice le&el agreements.
$dd / update the data.
(lternate flow of event&:
I# the product is not present, send error message.
,o&t condition: SF$ is created / updated.
+a!e of the u&e ca&e: Jie- ser&ice le&el agreement.
$e&cription: *o see the details o# the agreement.
,recondition: Sales manager is already logged in. *he product and the ser&ices to %e pro&ided are
already present.
http://osmlite.googlecode.com SkyNet, 2009 Page 22
OOO O oc_xe.
_c_
O O O q.xxexo::o
o
ooooo
ooo_:
OOO O O :x.ex:xoc
:
O _e_oo
oooo
o
ooooo
o
O oc_:xo
c
OOO ORO O .._.o_.o
_o
OOOOOOO O O OOOOOOOOOOOOOOOOOOOOOO :x.ex_
OOOOOOOOOO_ooo:
+or!al flow of event&:
Select product.
Select date.
*he details o# the SF$ are sho-n to the sales manager.
(lternate flow of event&:
I# the product is not present, send error message.
,o&t condition: None.
+a!e of the u&e ca&e: Jie- product stock and contact -ith the administrator.
$e&cription: Jie- stock o# a speci#ic product and i# stock is lo- contact -ith the administrator.
,recondition: Sales manager is already logged in.
+or!al flow of event&:
Select product
Jie- stock.
(lternate flow of event&:
http://osmlite.googlecode.com SkyNet, 2009 Page 2
OOO O oc_xe.
_c_
O O O q.xxexo::o
o
ooooo
ooo_:
OOO O O :x.ex:xoc
:
O _e_oo
oooo
o
ooooo
o
O oc_:xo
c
OOOOOOO O OOOOOOOOOOOOOOOOOOOOOO _o_
OOOOOOOOOO_ooo:
I# the product is not present, send error message.
I# stock is lo- report to administrator.
,o&t condition: None.
Purchase 1anager:
Purchase 1anager is responsi%le #or recei&ing products #rom &endors , managing product stocks
and consulting -ith the administrator.
on&ulting with (d!ini&trator: *aking permission #rom the $dministrator #or the
product to %e purchased #rom &endor.
,urcha&e Order: (esponsi%le #or re3uesting the Jendors to supply re3uired product
items o# re3uired amount -ithin time.
,roduct Stock Manage!ent: (esponsi%le #or managing stocks o# each product items.
+a!e of the u&e ca&e: /onsulting -ith the administrator, re3uesting the &endors #or re3uired
products and updating stocks.
$e&cription: /onsult -ith the administrator the products re3uired to %e purchased #rom the &endors,
order the products and update stock.
,recondition: Purchase 1anager is already logged in.
http://osmlite.googlecode.com SkyNet, 2009 Page 29
OO O oc_xe.
_c_
OOOOO O _o:_ecx
O O O q.xxexo::o
o
O O ex_o.ooqo
:_xo_ex
ooooo
o
ooooo
ooo_:
O _e_oo
oooo
o
ocx
O _ecx
oe
+or!al flow of event&:
*ake permission #rom administrator.
Place order to &endors.
1anage stock.
(lternate flow of event&: None.
,o&t condition: None.
$ccounts 1anager:
$ccounts 1anager is responsi%le #or recei&ing customer payments, managing customer payment
details and consulting -ith the administrator.
Regulating ,ay!ent&: Ceep track o# all the payment transactions made %y the customers
and update the payment in#ormation.
on&ulting with Bank&: (esponsi%le #or contacting the %anks #or the &alidation o# the
a/c num%er pro&ided %y the customer -hile purchasing and make the transaction #rom the
gi&en a/c.
on&ulting with (d!ini&trator: /onsult -ith the $dministrator a%out any payment
transaction pro%lems.
http://osmlite.googlecode.com SkyNet, 2009 Page !0
O oxxoo::o
O O eq.xeoo.
ooqo:_xo
_ex
OOO O O oocex.x_
O e
OOOOOOOO_q.ex:
co.
OOOO O _.o_:_e
cx
_xoq_.
R#03/(T*+0 ,(1M#+TS:
;;include<< $dd payment details


PPe@tendQQ 1anage payment ;;include<<
transaction details 4dit payment details
PPe@tendQQ
(egulating payments


Jie- history
+a!e of the u&e ca&e: $dd / edit payment transaction details
$e&cription: $ll the payment transaction details are entered or edited.
,recondition: $ccounts manager has logged in.
+or!al flow of event&:
Select the customer.
Select the product .
Select transaction id.
4nter / edit the details o# payment.
Sa&e the payment details.
(lternate flow of event: None.
,o&t condition: None.
http://osmlite.googlecode.com SkyNet, 2009 Page !1
+a!e of the u&e ca&e: Jie- history.
$e&cription: Jie- the payment details o# the selected customer.
,recondition: $ccounts manager is already logged in.
+or!al flow of event&:
Select customer.
*he payment details o# customer is &ie-ed.
(lternate flow of event&: None
,o&t condition: None.
http://osmlite.googlecode.com SkyNet, 2009 Page !2
OO O oc_c_:_
eox
OOO O oc_xe.
_c_
OOOOOOOOO O oc_
OOOxoq:oc_o
O eqo.
OOOOOO ORO _q_x.o_
OOO O o:oq_._o
oo:
OOOOOOOOOOOo
OOO O o:oq_._o
oo:
+a!e of the u&e ca&e: /onsulting -ith %ank and consulting -ith administrator.
$e&cription: /onsulting the %ank #or the customer payment and in case o# any pro%lem consulting
-ith the administrator.
,recondition: $ccounts manager is already logged in.
+or!al flow of event&:
Select transaction id.
Jie- transaction details.
/ontact %ank.
(ecei&e payment.
1anage payment
(lternate flow of event&:
I# any pro%lem contact -ith administrator.
,o&t condition: None.
http://osmlite.googlecode.com SkyNet, 2009 Page !!
O O :x.exc_:
_eox
OOOOOO O _:_eoxo
O :oq_:._o
oo:
O oc_c_:
_eox
/ustomer /are:
(esponsi%le #or getting #eed%ack #rom customers and pro&iding solutions to them.
0etting -eed9ack fro! the u&to!er&: (esponsi%le #or recei&ing complaints, 3ueries
and #eed%ack #rom the customers.
,roviding Solution& to u&to!er&: Pro&ide #easi%le solutions to the customers on their
complaints and 3ueries.
+a!e of u&e ca&e : =etting #eed%ack and pro&iding solutions.
$e&cription : *o get #eed%ack #rom customers a%out products and ser&ices pro&ided and gi&ing
solutions accordingly.
http://osmlite.googlecode.com SkyNet, 2009 Page !'
OOOOOOOOO O oc_
OOOxoq:oc_o
O eqo.
OOOO O eq_oc_o
oqx
O O O coo:oq_
OOOOOOOOOO_o
OOOOOOxoq:oc_o
O eq
OOOOOOOOO._ooo:
OOOOOOOO O eq_oc_
OOOOo.ooqo:_
xo_ex
_cc::
xeoo
o
O O _oqooo:oq
O _
+or!al flow of event :
Select customer.
=et #eed%ack.
Pro&ide solutions.
(lternate flow of event&:
I# customer is not registered ask #or registration at #irst.
,o&t condition: None.
/) Soft$are Syste# !ttributes
Since, there are a num%er o# attri%utes o# so#t-are that can ser&e as re3uirementsS the #ollo-ing items
pro&ide a partial list. *hese are also kno-n as non0#unctional re3uirements or 3uality attri%utes.
*hese are characteristics the system must possess, %ut that might per&ade through the design.
http://osmlite.googlecode.com SkyNet, 2009 Page !)
OOO O oc_c_:_
eox
O O O q.xxexo::o
o
ocx
OOOOO O OR __..oocx
OOOOOOOOOOO_x:
OOOOO O _e_x
oo:_
x.
oo:_x
.
O oc_:xo
c
O xeo.:eo
OOOOOOOOOOOOOOOOOOOOOO __oeq:
OOOOOOOOOO
4.2.1 Availability
*he system should %e a&aila%le at all times, meaning the user can access it using a -e%
%ro-ser, only restricted %y the do-n time o# the ser&er on -hich the system runs. In case o# a o# a
hard-are #ailure or data%ase corruption, a replacement page -ill %e sho-n. $lso in case o# a
hard-are #ailure or data%ase corruption, %ackups o# the data%ase should %e retrie&ed #rom the ser&er
and sa&ed %y the administrator. *hen the ser&ice -ill %e restarted.
'.2.2 Reliability
*he relia%ility o# the o&erall program depends on the relia%ility o# the separate components.
*he main pillar o# relia%ility o# the system is the %ackup o# the data%ase -hich is continuously
maintained and updated to re#lect the most recent changes. $lso the system -ill %e #unctioning inside
a container >since the implementation is I244 oriented?. *hus the o&erall sta%ility o# the system
depends on the sta%ility o# container and its underlying operating system.
'.2.! Security
Pass-ords -ill %e sa&ed encrypted in the data%ase in order to ensure the userEs pri&acy.
*he userEs IP -ill %e logged.
Sensiti&e data -ill %e encrypted %e#ore %eing sent o&er insecure connections like the internet.
/ertain #unctions -ill %e assigned to certain modules only.
"ata integrity -ill %e checked #or critical &aria%les.
'.2.' Maintainability
$ commercial data%ase is used #or maintaining the data%ase and the application ser&er takes
care o# the site. In case o# a #ailure, a re0initialiAation o# the program -ill %e done. $lso the so#t-are
design is %eing done -ith modularity in mind so that maintaina%ility can %e done e##iciently.
'.2.) Portability
*he application is I244 %ased and should %e compati%le -ith all other systems -hich ha&e a
nati&e Ia&a implementation. *he end0user part is #ully porta%le and any system using any -e%
%ro-ser should %e a%le to use the #eatures o# the application, including any hard-are plat#orm that is
a&aila%le or -ill %e a&aila%le in the #uture.
http://osmlite.googlecode.com SkyNet, 2009 Page !+
0) !CT*ON SE62ENCES
*his section descri%es in detail the se3uence o# steps that are needed to %e done %y the users o#
the system to utiliAe the #unctionalities %eing pro&ided %y this -e% application. =rouping the
actions %y users, -e start #rom the #ollo-ing user o# the system:
*he customer :
*he customer is the main user o# the sopping mall -e%site and is the main reason
-hy this -e% application e@ists in the #irst place. *he customer can %ro-se
through the shops and choose products to place in a &irtual shopping cart. *he
shopping cart details can %e &ie-ed and items can %e remo&ed #rom the cart. *o
proceed -ith the purchase, the customer is prompted to login. $lso, the customer
can modi#y personal pro#ile in#ormation >such as phone num%er and shipping
address? stored %y the application. *he customer can also &ie- the status o# any
pre&ious orders, and cancel any order that has not %een shipped yet.
Since the customer is the main user o# the system, -e -ill #ollo- the customer as he or she goes
a%out -ith the &arious acti&ities in the shopping mall. *his -ay -e -ill ha&e e@plored all the
-ays this shopping mall #unctions as -ell as o%tained an 7algorithm8 o# the steps o# #unctioning
o# the entire shopping mall application.
*he algorithm is:
Step 1: $ potential customer G &isits the -e%site o# ,S1.
Step 2: G either kno-s the product he or she is searching #or or is una-are o# his e@pectations
#rom the shopping mall.
Step !a: I# G kno-s the product he is searching #or he enters the name o# the %rand o# that
product in the search %o@ on the home page itsel#. Le is then -hisked right to the separate page
#or that %rand, -here he can choose the product according to his liking.
Step !%: I# G -ants to %ro-se the products %e#ore deciding -hat to %uy, then he can choose the
categories o# the products in the home page itsel#. <rom there he -ill %e taken to the product
categories page #rom -here he can choose the %rand that appeals to him.
Step ': $#ter selecting the %rand o# the product, G can click on a particular product -hich -ill
take him to the product page #or that particular product. *his page contains all the detailed
in#ormation a%out the product.
Step ): No- that the product has %een selected, G might -ant to actually %uy the product. Le
-ill then ha&e to log in to the -e%site to actually a##ect the %uying process.
http://osmlite.googlecode.com SkyNet, 2009 Page !2
Step )a: I# G is a ne- user, he -ill ha&e to #irst register in the -e%siteBs ne- user registration
page. *hen he -ill %e a%le to login to the -e%site and complete he transaction.
Step )%: G may also -ish to &ie- his account detail in the account details page. *here he can
check and change his contact in#ormation. Le can also &ie- his shopping cart including any
incomplete shopping carts -hich ha&e not matured to the %uying status.
Step +: 9hen G selects to %uy the product he may #ollo- t-o paths.
Step +a: G may add one item to his shopping cart and then keep on %ro-sing the store #or more
good things. 9hen he has #illed his cart to the %rim, he can rush to checkout the shopping cart on
the shopping cart page.
Step +%: ,r G may decide to %uy 6ust one product and rush to checkout the product. Le can then
in the checkout page put in his credit card in#ormation and su%mit the in#ormation. *hat -ill
complete the transaction process.
Step +c: ,r a#ter %ro-sing #or some products, G can come %ack to his incomplete cart and
complete the payout process.
Step 2: G -ill ha&e to pro&ide his credit card details and then proceed to check out. *hen he -ill
%e gi&en a con#irmation that his credit card has %een &alidated and that he -ill recei&e the
product -ithin a stipulated time #rame.
http://osmlite.googlecode.com SkyNet, 2009 Page !
*he #lo-chart #or the a#orementioned steps:
http://osmlite.googlecode.com SkyNet, 2009 Page !9
Jie- category
Jie- category
Select category
Select category
Select product
Select product
Search
Search
Cno- product
Fog in
Fog in
(egistration
(egistration
4lse
I# success#ul
Jie-/edit pro#ile
Jie-/edit pro#ile
Select product
Select product
:uy directly
:uy directly
$dd to cart
$dd to cart
*o shop
more and
add more
products
/heckout
/heckout
Input payment details
Input payment details
=et con#irmation
=et con#irmation
1) 2SER *NTER7!CE DES*&N
4&ery user inter#ace0 -hether it is designed #or a 9e%$pp, or a traditional so#t-are application0
should e@hi%it the #ollo-ing characteristics:
4asy to use.
4asy to learn.
4asy to na&igate.
Intuiti&e.
/onsistent.
4##icient.
4rror0#ree.
<unctional.
It should pro&ide the end0user -ith a satis#ying and re-arding e@perience. ,ur ,S1 -e%
application #ollo-s all these principle o# e##ecti&e user inter#ace design. Fike an e##ecti&e
inter#ace, ,S1 is &isually apparent and #orgi&ing, instilling in its users a sense o# control. .sers
3uickly see the %readth o# their options, grasp ho- to achie&e their goals, and do their -ork. It
does not concern the user -ith the inner -orkings o# the system and the users ha&e the #ull
option to undo acti&ities at any time eg. to remo&e item #rom the shopping cart.
Fike e##ecti&e applications and ser&ices, ,S1 per#orms a ma@imum o# -ork, -hile
re3uiring a minimum o# in#ormation #rom the users.
http://osmlite.googlecode.com SkyNet, 2009 Page '0
Screenshots of the OSM $ebsite
*he #irst screenshot is that o# the home page or the inde@ page -hich comes #irst to the
%ro-ser -hen someone -ill %e &isiting the -e%site o# ,S1.
http://osmlite.googlecode.com SkyNet, 2009 Page '1
*he second screen shot is that o# the login page, -hich -ill pop up -hen someone -ill
try to %uy a product #rom the shopping mall.
http://osmlite.googlecode.com SkyNet, 2009 Page '2
*he third screen shot is that o# a category page -hich is sho-ing all the products that are
a&aila%le in a category o# products >here computers is the category?.
http://osmlite.googlecode.com SkyNet, 2009 Page '!
*he #ourth screen shot is that o# the shopping cart -here customers o# the shopping mall
can keep the goods -hich they -ant to %uy. $ loaded shopping cart is %eing sho-n here.

http://osmlite.googlecode.com SkyNet, 2009 Page ''
*he #i#th screen shot is that o# the %uy page -here the customer -ill ha&e to pro&ide
his/her credit card details to complete the shopping process.
http://osmlite.googlecode.com SkyNet, 2009 Page ')
4) 8E9 !PP:*C!T*ON TEST*N&
9e% application >9e%$pp? testing is a collection o# related acti&ities -ith a single goal: to
unco&er errors in 9e%$pp content, #unction, usa%ility, na&iga%ility, per#ormance, capacity, and
security. *o accomplish this, a testing strategy that encompasses %oth re&ie-s and e@ecuta%le
testing is applied throughout the 9e% engineering process. I# end users encounter errors that
shake their #aith in the 9e%$pp, they -ill go else-here #or the content and #unction they need,
and the 9e%$pp -ill #ail. <or this reason as many errors as possi%le must %e eliminated %e#ore
the 9e%$pp goes online.
*he 9e%$pp testing process %egins %y #ocusing on user0&isi%le aspects o# the 9e%$pp
and proceeds to tests that e@ercise technology and in#rastructure. In some instances a 9e%$pp
test plan is produced. In e&ery instance, a suite o# test cases is de&eloped #or e&ery testing step
and an archi&e o# test results is maintained #or #uture use.
5uality is incorporated into a -e% application as a conse3uence o# good design. In our pro6ect as
-ell, the #ollo-ing 3uality dimensions ha&e al-ays %een the cap stones in the de&elopment
process:
Content is e&aluated at %oth the syntactic and semantic le&el.
Function is tested to unco&er errors that indicate lack o# con#ormance to customer
re3uirements.
Structure is assessed to ensure that it properly deli&ers content and #unction, that it is
e@tensi%le, and that it can %e supported as ne- content or #unctionality is added.
Usai!ity is tested to ensure that each category o# user is supported %y the inter#ace.
Navi"ai!ity is tested to ensure that all na&igational synta@ and semantics are e@ercised to
unco&er any na&igational errors.
#erformance is tested under a &ariety o# operating conditions to ensure that the system is
responsi&e to user interaction and operates -ithout unaccepta%le operational degradation
in contingency situations.
Compatii!ity is tested %y e@ecuting the -e% application in a &ariety o# di##erent hosts on
%oth the client and ser&er sides.
$nteroperai!ity is tested to ensure that the 9e%$pp properly inter#aces -ith other
applications and/or data%ases.
Security is tested %y assessing potential &ulnera%ilities and attempting to e@ploit each.

*he color codes that ha&e %een used here signi#y the e@tent o# testing that the ,S1 product has
undergone in its #irst &ersion.
=reen signi#ies that the components ha&e %een tested according to the descri%ed path-ay.
http://osmlite.googlecode.com SkyNet, 2009 Page '+
(ed signi#ies that the components ha&e not %een tested according to the descri%ed path-ay due
to lack o# in#rastructure %ut -ill %e tested in the ne@t &ersion.
Jiolet signi#ies that the components ha&e %een tested partially according to the descri%ed
path-ay and ne- #eatures -ill %e added in the ne@t &ersion.
Some test cases -hich -e ha&e utiliAed to test our product:
*est premise: *o test -hether users can log into their respecti&e accounts and &ie- their
contact and shopping cart details, -hether employees and the administrators can login to
their respecti&e accounts.
*est type: Security.
*est structure:
o 9e created se&eral dummy accounts #or all the types o# users like customers,
employees and administrators. 9e then logged into the respecti&e accounts using
the corresponding user names and pass-ords.
*est result: Success.
o 9e then mi@ed up the user names and the pass-ords and tried to log into the
respecti&e accounts. :ut -e could not since each user has a uni3ue user name and
pass-ord. *hus all the user accounts are sa#e #rom unauthoriAed intrusion. $lso
the %ro-ser 7%ack8 %utton cannot %e misused to gain access to the respecti&e
account a#ter a user has success#ully logged out
*est result: Success.
*est premise: *o search #or products and %ro-se the catalogue o# products.
*est type: Na&iga%ility, /ontent.
*est structure:
o 9e tested the na&iga%ility o# the -e%site %y %ro-sing the entire catalogue o#
products. 9e -ent to the di##erent categories and looked #or product inside the
category. 9e did a random sampling o# product paths #rom &arious points in the
-e%site to sni## out any dead links.
*est result: Success.
o 9e also searched #or a particular product #rom the home page and the search page
to #ind out -hether our searches are producing rele&ant results. 9e also tested the
content o# e&ery product page to #ind out -hether the content pro&ided is the same
as that pro&ided %y the manu#acturer o# the product.
*est result: Success.
*est premise: *o add/remo&e items #rom the shopping cart and update it as -ell.
*est type: .sa%ility, Structure.
*est structure:
o 9e tested the usa%ility o# the shopping cart mechanism %y repeatedly adding and
su%se3uently remo&ing items #rom the shopping cart. 9e also checked the
corresponding money &alue o# the shopping cart to #ind out -hether it truly
re#lects the present contents o# the shopping cart.
*est result: Success.
o 9e also tested the update #eature o# the shopping cart %y #irst loading the
http://osmlite.googlecode.com SkyNet, 2009 Page '2
shopping cart -ith products and then na&igating a-ay to the home page to %ro-se
and add more products to the shopping cart. 9e came %ack to the shopping cart to
check:
9hether the pre&ious items in the cart are still there in the cart.
9hether the ne-ly added items ha&e %een added properly and in
the right 3uantity -hich -e selected #or each product.
$nd, -hether the total money &alue o# the cart e3uals the total o#
the costs o# all the goods in the cart.
*est result: Success.
*est premise: *o test -hether the e@act amount o# money &alue o# products -hich the
customer has %ought has %een %illed to him.
*est type: <unction.
*est structure:
o 9e tested -hether the total &alue o# a shopping cart o# a particular customer has
%een %illed to the corresponding customer and not to any other customer. 9e also
checked the data%ase entries to #ind out -hether e&ery customer account has the
right amount o# money %illed to him or her and -hether that amount o# money
signi#ies the current &alue o# the shopping cart.
*est result: Success.
http://osmlite.googlecode.com SkyNet, 2009 Page '
5) !C;NO8:ED&EMENT
$ study or a pro6ect o# this &olume can ne&er %e the outcome o# a single person or
6ust a mere group o# dedicated students. (ather it is the culmination o# the leadership and &alued
guidance o# a leading #igure -ho inspires and -hips up a #renAy o# acti&ity, yet keeping the
entire team #ocused on the #inal goal. So -e are happy to present a &ote o# thanks to them #or
their sincere ad&ice and co0operation that they ha&e lent us unconditionally.
9e are inde%ted to "rs. Mr&. (nanya )anjilal and Sa9na! Sengupta >(&&i&tant ,rofe&&or
%*T $epart!ent'= B. ,. ,oddar *n&titute of Manage!ent " Technology? #or %eing the
epitome o# guidance during the entire pro6ect.
*hey ha&e encouraged us -hene&er -e ha&e %een in e@igency situations and ha&e kept us
#ocused on the -ork at hand no matter ho- high a mountain -e #aced. 9ithout their painstaking
and a-esome e##orts in keeping e&erything pristine and per#ect the pro6ect -ould not ha&e
reached its present immaculate state.
9e must not #orget the role o# >e&t Bengal 3niver&ity of Technology -here the authorities
decided upon incorporating such pro6ects in our course -hich helped us to understand and learn
a lot through practical e@periences.
9e are also thank#ul to other faculty !e!9er& #or their encouragement. 9ithout their help this
pro6ect -ould not ha&e seen the light o# day.
Surjyendu Ray % UNIVERSITY ROLL NO-228?4?84??@'
Sandip Shaw % UNIVERSITY ROLL NO-228?4?84??4'
Suvendu Bhattacharya %UNIVERSITY ROLL NO-228?4?82?2A'
Souvik Sett %UNIVERSITY ROLL NO-228?4?82?24'
$#,(RTM#+T- *+-ORM(T*O+ T#.+O/O01%*T'
S#M#ST#R - @T.
O//#0#- B.,.,O$$(R *+ST*T3T# O- M(+(0#M#+T (+$ T#.+O/O01
http://osmlite.googlecode.com SkyNet, 2009 Page '9
<) 9*9:*O&R!P=>
*o %ring the pro6ect to a #ruit#ul completion -e ha&e consulted se&eral -e%sites and %ooks. 9e
are gi&ing a list o# the important %ooks and -e%sites. *hese -ere the initial points o# our research
#or this pro6ect.
Software Engineering by Roger S. Pressman
Internet an orl! i!e eb "ow to Program by #eitel an! #eitel
$a%a "ow to Program by #eitel an! #eitel
http:&&www.tgmc.in&project'scenario'%iew.php(page)*+i!),
Professional $a%a Ser%er Programming -.Press/.
.n! for e%erything else0 we ha! http:&&www.ibm.com&!e%eloperwor1s&ja%a&library&
http://osmlite.googlecode.com SkyNet, 2009 Page )0
http://osmlite.googlecode.com SkyNet, 2009 Page )1