Table of Contents Page No ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

SNo 1. 2. 3. .

Particulars Acknowledgment Organization Overview Profile of Project !"isting S#stem .1 Pro$lem in !"isting S#stem .2 %ser &e'uirement )*at+s new in t*e S#stem to $e ,evelo-ment (.1 Pro$lem ,efination (.2 Product ,efination 5.3 System Requirement Defination /easi$ilit# Anal#sis and Pro-osed S#stem 1ec*nologies %sed 0.1 As-.Net 0.2 S23 ,ata$ase ,ata /low ,iagram+s 5,/,+s6 S#stem ,esign 7.1 ,ata$ase ,esign 7.2 /orm ,esign 9m-lementation :aintance ;i$liogra-*#

(.

.. 0.

4. 7. . 18. 11. 21.

A<=NO)3!,>!:!N1 9t would $e ina--ro-riate to call t*is re-ort com-lete and successful? if we don+t thank

the people who guided as in the preparation of this project.

1

1*e su$mission of t*is -roject re-ort gives us an o--ortunit# to conve# our gratitude to all t*ose w*o *ave *el-ed us to reac* stage from w*ere we *ave immense confidence to launc* our carrier in t*e com-etitive world of software. /irst and foremost? we want to offer our t*anks to our -roject officer !r.>enius @ain 5Project Officer? 9ntellisense 1ec*nolog#6 to -rovide us training of AASP.N!15<B6C and *is valua$le *el- during t*e develo-ment of t*is -roject. )it*out *er suggestion and timel# *el- we would not *ave $een a$le to com-lete -roject. S*e *as $een a source of -er-etual ins-iration to us? gentl# guided and ins-ired us towards a $rig*t career. 5Neelam =aur? :an-reet =aur)

O&>AN9SA19ON OD!&D9!)

B A :%319NA19ONA3 )!;S91! ,!D!3OP:!N1 <O:PANE 9ntellisense 1ec*nolog#? as t*e name suggests *as an answer to all #our !F commerce -ro$lems $# -roviding intelligent solutions. )*ere ever #ou are in an# -art of t*e world? we+re *ere to $uild #our )e$ sites and *el- #ou
2

-romote #our $usiness. )e not onl# $uild data$ase we$ sites? $ut also !F <ommerce Sites? ;2;? ;2<? @o$ Portals as well as )e$ Gosting and ,omain &egistration. !sta$lis*ed in 288.? 9ntellisense 1ec*nolog# *as graduated from a small firm to an 9nternational com-an# *aving Overseas Office at <ANA,A? %= Gead Office at @A3AN,GA& 5Punja$ ? 9N,9A6 H Su$ Office at <GAN,9>A&G. ,ue to t*e s*eer *ard work? -ersistence and efforts of its <!O :r. GA&@91 S9N>G? it is engaged in inF*ouse 9nternet :arketing? Software ,evelo-ment? ,omain &egistration and ,esigning of <atalogues? ;roc*ures and >ra-*ics. )e understand #our need for 9nternet :arketing and *ence are availa$le for #ou 2 I0 kee-ing in mind t*e time difference wit* outside countries. )e are constantl# making endeavors to -rovide #ou wit* -rom-t service and *el#ou in ever# -ossi$le wa#. )e look forward to working wit* #ou and are confident t*at #ou will $e satisfied wit* our service. straig*t cost savings. <om-an# is focused on learning and continuousl# im-roving our ca-a$ilities to drive im-rovements in 'ualit# and -roductivit# for our customers.

A;O%1 1G! P&O@!<1 JOnline AuctionJ is an online auction we$ site aimed at taking t*e auction to t*e finger ti-s of as-iring $idders t*ere $# o-ening u- t*e doors of t*e JOP!N Auction GouseC to a wider cross section of Art 3overs and Anti'ue <ollectors. 1*is site also acts as an o-en forum w*ere $u#ers and sellers can come toget*er and e"c*ange t*eir -roducts. 1*e site makes sure t*at t*e sellers get a fair deal and $u#ers get a genuine -roduct. Online Auction F 1*is -age is an interface for $ot* $u#er and seller. ;u#er can see t*e -rofile of t*e $idding *istor# of items w*ic* are still o-en on w*ic* *eIs*e *as alread# $ided. Similarl# t*e seller can see t*e -rogress of $idding on articles *eIs*e *as -laced for $idding. Gig*lig*tsI:odules of 1*e Project 1. Admin :odule 2. %ser :odule 3. ;u#er :odule
3

:odules of AdminKF 3ogin moduleKFLogin

moduel is used for buyer, user

and Admin.
3oginF 1*e :odule collects %ser &egistration F 1*ose w*o wis* to take -art in $idding or sell -roducts at t*e site *ave to register at t*e site as seller or $u#er. Onl# aut*enticated users can take -art in selling or in $idding. 1*e s#stem automaticall# rejects unFaut*enticated users w*o tr# to $id or sell at t*e site. &egister Products F 1*is module is for -resenting items for $idding. Onl# t*ose w*o *ave registered and aut*enticated as sellers can -lace t*eir articles information like Product Name? Product ,etails? Starting ;id amount? 9ncremental value etc. 1*e s#stem automaticall# in-uts t*e closing date. <ategor#KF Add a new categor# Su$mitIu-date categor#

3ist Category

insert delete/list/Modify module !"his module pro#ides option to do following

:odif# an e"isting <ategor# <ategor# 3isting ,elete a <ategor# P&O;3!: ,!/9N919ON 1*e -ro$lem wit* -u$lic auction is t*at t*e -artici-ation of t*e general -u$lic is ver# limited. 1*e aim of t*e -roject is to socialize t*e auction so t*at -eo-le from far H wide and even across t*e continent can -artici-ate in it. 1*e JOnline AuctionJ site is develo-ed wit* a vision to wi-e out t*e in*erent -ro$lems of J<onventional Auction J. 1*e salient features of t*e site are as followsK 1. Pa-erless Auction S#stem 2. 9tLs accessi$le to ever#one? at an# time no matter w*ere t*e# are 3. &elia$le user validation H c*ecking. . !as# online settlement. JOnline AuctionJ is designed in suc* a wa# t*at it is as user friendl# as

-ossi$le. So an# as-iring $idder or seller can visit t*e site and engage in $idding wit* least effort. 1. !M9S19N> SES1!: 1*e e"isting JOP!N Auction GouseJ is managed manuall#. Prior to eac* auction? t*e da# of auction? t*e venue and t*e items on auction are announced t*roug* news media. 1*ose w*o wis* to take -art in t*e auction *ave to arrive at t*e venue on t*at da# on time. 1*is conventional met*od most of t*e times -revent as-iring $idders from -artici-ating in t*e $idding -rocess. Anot*er *eadac*e of t*e old s#stem is to track eac* $idding -rocess and to make it culminate in financial settlement. So t*e s#stem *as to keerecords of $ot* $u#ers and sellers until t*e end of settlement. 1*e -rocess is ver# cum$ersome and time consuming.

2. PROPOSED SYSTEM
1*e slogan of t*e new site is AAA? LAn#one? An#time? An#w*ereL. 1*at w*at it reall# is 1*e JOnline AuctionJ is online auction *ouse so t*e seller or $idder doesnLt need to go an#w*ere? instead t*e# can take -art in t*e auction just sitting in t*e comfort of t*eir living room? $e it during t*e da# or nig*t. 1*e -ro-osed com-uterized JOnline AuctionJ site *as made auction -rocess sim-le. 1*e onl# ( -reFcondition is t*at t*e user must register and aut*enticate $efore *eIs*e can take -art in t*e $idding -rocess. 1*e s#stem uses G11P forms aut*entication w*ic* creates a session cookie for an# signed in user. 1*roug* out t*e s-an of t*e session t*e cookie remains valid until t*e user logs out. An auction *ouse needs to *ave -roducts to auction? so in t*e -ro-osed s#stem t*is is done using -roduct registration module. 1*e module is o-en to user w*o is registered sellers and t*e# need to aut*enticate $efore t*e# register an# -roduct. 1*e s#stem controls t*e closing date $# adding 1 da#s to t*e su$mitting date t*ere $# restricting t*e $idding -rocess to go on indefinitel#. Anot*er im-ortant module in t*e -ro-osed -roject is t*e J;idding module J. Gere one can see t*e details of an# -articular -roduct and also t*e $idding *istor#. 1*e user can $id on t*at item $# entering an# amount greater t*an or e'ual to t*e incremental $id amount. Gere also s#stem c*ecks to see w*et*er t*e user *as *is credential verified ot*erwise *eIs*e will $e directed to t*e loginIregistration -age. 1*e last $ut t*e least module is t*e J AdministrationJ module. 1*e module is onl# o-en to t*e we$ administrator due to securit# reasons. 9n t*is module t*e administrator can add -roduct categoriesN t*is is to avoid ram-ant
(

creation of categories. 1*e 2nd t*ing is t*e o-tion to edit an# given -roduct. 1*is will $e necessar# w*en some of t*e details of t*e -roduct need to $e edited for one reason or ot*er. 1*e 3rd and last t*e closed $id manager w*ere t*e administrator notifies $ot* t*e seller and $u#er t*e need to com-lete t*e transaction. 1*ere is anot*er module w*ic* runs more or less like $ackground -rocess. 1*e function of t*e module is to close $id of t*ose -roducts w*ose closing date is less t*an t*e current date. 1*e -rocess is automatic and *idden from t*e we$ users. 3. SES1!: S1%,E 1*e s#stem stud# -*ase involves t*e investigation of t*e structure of current s#stem? wit* t*e o$jective of identif#ing t*e -ro$lem and difficulties wit* t*e e"isting s#stem. 1*e major ste-s involved in t*is -*ase included defining t*e user re'uirements and stud#ing t*e -resent s#stem to verif# t*e -ro$lem. 1*e -erformance e"-ected $# t*e new s#stem was also defined in t*is -*ase in order to meet t*e user re'uirements. 1*e information gat*ered from various documents were anal#zed and evaluated and t*e findings reviewed in order to esta$lis* s-ecific s#stem o$jectives. 3.1 SES1!: ANA3ES9S S#stem Anal#sis is an investigation into a -ro$lem and *ow a new s#stem will solve it. 9t is t*e most essential -art of t*e develo-ment of a -roject of a s#stem anal#sis. S#stem anal#sis consists of s#stem element? -rocess and tec*nolog#. 1o anal#ze a s#stem? *as to stud# t*e s#stems in details. 1*e anal#st *as to understand t*e functioning and conce-t of t*e s#stem in detail? $efore design t*e a--ro-riate com-uter $ased s#stem t*at will meet all t*e re'uirements of t*e e"isting s#stem. 1*e s#stem anal#st *as to carr# out a customar# a--roac* to use t*e com-uter for -ro$lem solving. S#stem anal#sis includes t*e following $asic conce-ts O Preliminar# investigation O &e'uirements s-ecification O /easi$ilit# stud# O ,etailed investigation O ,rawing u- of strategies O ,esign and coding O 1esting and training O 9m-lementation 1*e a$ove ste-s constitute t*e logical framework for t*e s#stem anal#sis. After t*e -reliminar# investigation and feasi$ilit# stud#? t*e sco-e of t*e
.

defined and com-ara$le items are set fort* and *ence detailed investigation is e"ecuted. 1*is allows t*e s#stem anal#st to com-re*end t*e full sco-e of t*e -roject. Soon after t*e im-lementation of t*e newl# develo-ed s#stem? followed $# t*e training of t*e users? t*e s#stem anal#sis is included. . P&!39:9NA&E 9ND!S19>A19ON A re'uest to receive assistance from information s#stem can $e made for man# reasons? $ut in case a manager? em-lo#ee or s#stem s-ecialist initiates t*e re'uest. )*en t*at re'uest is made? t*e first s#stem activit# -reliminar# investigation $egins. 1*e activit# *as t*ree -arts P &e'uest clarificationK t*e re'uest from em-lo#ee ma# not $e well stated. Sometimes t*e re'uest ma# not $e well defined. 1*erefore $efore an# s#stem investigation can $e considered? t*e -roject re'uest must $e e"amined to determine -recisel# t*e actual re'uirements of t*e organization. P /easi$ilit# stud#K t*e $asic idea $e*ind feasi$ilit# stud# is to determine w*et*er t*e -roject is feasi$le or not. P &e'uest a--rovalK all -rojects t*at are re'uested are not desira$le or feasi$le .some organization receive so man# -rojects re'uests from em-lo#ee t*at onl# a few of t*em can $e -ursued. Gowever t*ose -rojects t*at are feasi$le and desira$le s*ould -ut into a sc*edule. 1*e management decides re'uest t*at are most im-ortant. After a -roject re'uest is a--roved t*e cost -riorit#? t*e com-letion time and t*e -ersonal re'uired are estimated. Once t*e re'uest is a--roved? t*e collection of data and determination of re'uirements can $e started. (.1 /!AS9;9391E S1%,E 1*e $asic idea $e*ind feasi$ilit# stud# is to determine w*et*er t*e -roject is feasi$le or not. A feasi$ilit# is conducted to identif# a $est s#stem t*at meets all t*e re'uirements. 1*is includes an identification ?descri-tion? an evaluation of t*e -ro-osed s#stems and selection of t*e $est s#stem for t*e jo$ . 1*e re'uirements of t*e s#stem are s-ecified wit* a set of constraints suc* as s#stem o$jectives and t*e descri-tion of t*e out -uts. 9t is t*en dut# of t*e anal#st to evaluate t*e feasi$ilit# of t*e -ro-osed s#stem to generate t*e a$ove results. 1*ree ke# factors are to $e considered during t*e feasi$ilit# stud#. (.1.1 O-eration /easi$ilit# An estimate s*ould $e made to determine *ow muc* effort and care will go into t*e develo-ing of t*e s#stem including t*e training to $e given to t*e user. %suall#? -eo-le are reluctant to c*anges t*at come in t*eir -rogression. 1*e com-uter initialization will certainl# affected t*e turn over? transfer and
0

em-lo#ee jo$ status. Gence an additional effort is to $e made to train and educate t*e users on t*e new wa# of t*e s#stem. (.1.2 1ec*nical /easi$ilit# 1*e main consideration is to $e given to t*e stud# of availa$le resources of t*e organization w*ere t*e software is to $e im-lemented. Gere t*e s#stem anal#st evaluates t*e tec*nical merits of t*e s#stem giving em-*asis on t*e -erformance? relia$ilit#? maintaina$ilit# and -roductivit#. ;# taking t*e consideration $efore develo-ing t*e -ro-osed s#stem? t*e resources availa$ilit# of t*e organization was studied. 1*e organization was immense com-uter facilities e'ui--ed wit* so-*isticated mac*ines and t*e software *ence t*is tec*nicall# feasi$le. (.1.3 !conomic /easi$ilit# !conomic feasi$ilit# is t*e most im-ortant and fre'uentl# used met*od for evaluating t*e effectiveness of t*e -ro-osed s#stem. 9t is ver# essential $ecause t*e main goal of t*e -ro-osed s#stem is to *ave economicall# $etter result along wit* increased efficienc#. <ost $enefit anal#sis is usuall# -erformed for t*is -ur-ose. 9t is t*e com-arative stud# of t*e cost verses t*e $enefit and savings t*at are e"-ected from t*e -ro-osed s#stem. Since t*e organization is well e'ui--ed wit* t*e re'uired *ard ware? t*e -roject was found to $e economicall#. (.2 GA&,)A&! &!2%9&!:!N1S P&O<!SSO& K P!N19%: 999 or A$ove &A: K 2(.:; or more G,, K 8>; :ON91O& K SD>A <O3O& =!E ;OA&, K 181 =!ES :O,!: K (. =;PSIA,S3 ;road$and :O%S! K PS2I Serial /,, K 1. :; (.3 SO/1)A&! &!2%9&!:!N1S OP!&A19N> SES1!: K )9N,O)S 2888IMPI2883 server ;&O)S!& K 9N1!&N!1 !MP3O&!& (.( O& ANE G11P ;&O)S!& ,A1A;AS! 3AE!& K :S S23 288( )!; S!&D!& K 99S ( or a$ove S!&D!& S9,! S<&9P19N>
4

K ASP.N!1 H <B <39!N1 S9,! S<&9P19N> <ONN!<19ON K A,O.N!1 P&O1O<O3 K G11P? S:1P (. 1!<GNO3O>E SP!<9/9<A19ON P 3F 1ier Arc*itecture 9n 3F 1ier arc*itecture an a--lication is $roken into t*ree se-arate logical la#ers? eac* wit* a well F defined set of interfaces. 1*e first tier is referred to as t*e -resentation la#er and t#-icall# consists of gra-*ical user interface of some kind. 1*e middle tier? or $usiness la#er? consists of a--lication or $usiness la#er and t*e t*ird la#erF t*e data la#er contains t*e data t*at is needed for t*e a--lication. 1*e middle tier is $asicall# t*e code t*at t*e user calls u-on to retrieve t*e desired data. 1*e -resentation la#er t*en receives t*e data and formats it for dis-la#. 1*is se-aration of a--lication logic from t*e user interface adds enormous fle"i$ilit# to t*e design of a--lication. 1*e t*ird tier contains t*e data t*at is needed for t*e a--lication. P nF 1ier Arc*itecture 9n an n F tier arc*itecture t*e a--lication logic is divided $# function rat*er t*an -*#sicall#. N F 1ier arc*itecture t*en $reaks down like t*isK QRST A user interface t*at *andle t*e userLs interaction wit* t*e a--licationN t*is can $e we$ $rowser running t*roug* a firewall? a *eavier desktoa--lication or even a wireless device QRST Presentation logic t*at defines w*at t*e user interface dis-la#s and *ow a userLs re'uests are *andledF de-ending on w*at user interfaces are su--orted we need to *ave slig*tl# different versions of t*e -resentation logic to *andle t*e client a--ro-riatel#. QRST ;usiness logic t*at models t*e a--licationLs $usiness rules? often t*roug* t*e interaction wit* t*e a--licationLs data. QRST 9nterface services t*at -rovide additional functionalit# re'uired $# t*e a--lication com-onents? suc* as messaging? transactional su--ort etc. QRST 1*e ,ata la#er w*ere t*e enter-riseLs data resides. SES1!: ,!S9>N 1*e $asic goal of s#stem design is to -lan a solution for t*e -ro$lem. 1*is -*ase is com-osed of several s#stems. 1*is -*ase focuses on t*e detailed im-lementation of t*e feasi$le s#stem. 9t em-*asis on translating design s-ecifications to -erformance s-ecification. S#stem design *as two -*ases of develo-ment logical and -*#sical design.
7

,uring logical design -*ase t*e anal#st descri$es in-uts 5sources6? out-uts 5destinations6? data$ases 5data stores6 and -rocedures 5data flows6 all in a format t*at meets t*e user re'uirements. 1*e anal#st also s-ecifies t*e user needs and at a level t*at virtuall# determines t*e information flow into and out of t*e s#stem and t*e data resources. Gere t*e logical design is done t*roug* data flow diagrams and data$ase design. 1*e logical design is followed $# -*#sical design or codingKF . P*#sical design -roduces t*e working s#stem $# defining t*e design s-ecifications? w*ic* tell t*e -rogrammers e"actl# w*at t*e candidate s#stem must do. 1*e -rogrammers write t*e necessar# -rograms t*at acce-t in-ut from t*e user? -erform necessar# -rocessing on acce-ted data t*roug* call and -roduce t*e re'uired re-ort on a *ard co-# or dis-la# it on t*e screen. .1 3O>9<A3 ,!S9>N 3ogical design of an information s#stem s*ows t*e major features and also *ow t*e# are related to one anot*er. 1*e first ste- of t*e s#stem design is to design logical design elements. 1*is is t*e most creative and c*allenging -*ase and im-ortant too. ,esign of -ro-osed s#stem -roduces t*e details of t*e state *ow t*e s#stem will meet t*e re'uirements identified during t*e s#stem anal#sis t*at is? in t*e design -*ase we *ave to find *ow to solve t*e difficulties faced $# t*e e"isting s#stem. 1*e logical design of t*e -ro-osed s#stem s*ould include t*e details t*at contain *ow t*e solutions can $e im-lemented. 9t also s-ecifies *ow t*e data$ase is to $e $uilt for storing and retrieving data? w*at kind of re-orts are to $e created and w*at are t*e in-uts to $e given to t*e s#stem. 1*e logical design includes in-ut design? out-ut design? and data$ase design and -*#sical design ..2 9NP%1 ,!S9>N 1*e in-ut design is t*e link $etween t*e information s#stem and t*e user. 9t com-rises t*e develo-ing s-ecification and -rocedures for data -re-aration and t*ose ste-s are necessar# to -ut transaction data into a usa$le form for -rocessing data entr#. 1*e activit# of -utting data into t*e com-uter for -rocessing can $e ac*ieved $# ins-ecting t*e com-uter to read data from a written or -rinted document or it can occur $# *aving -eo-le ke#ing t*e data directl# into t*e s#stem. 1*e design of in-ut focuses on controlling t*e amount of in-ut re'uired? controlling errors? avoiding dela#? avoiding e"tra ste-s and kee-ing t*e -rocess sim-le. 1*e s#stem needs t*e data regarding t*e asset items? de-reciation rates? asset transfer? -*#sical verification for various validation? c*ecking? calculation
18

and re-ort generation.. 1*e error raising met*od is also included in t*e software? w*ic* *el-s to raise error message w*ile wrong entr# of in-ut is done. So in in-ut design t*e following t*ings are considered. )*at data s*ould $e given as in-ut O Gow t*e data s*ould $e arranged or coded O 1*e dialogue to guide t*e o-erating -ersonnel in -roviding in-ut. O :et*ods for -re-aring in-ut validations and ste-s to follow w*en error occur O 1*e sam-les of screen la#out are given in t*e a--endi". ..3 O%1P%1 ,!S9>N <om-uter out-ut is t*e most im-ortant and direct information source to t*e user. Out-ut design is a -rocess t*at involves designing necessar# out-uts in t*e form of re-orts t*at s*ould $e given to t*e users according to t*e re'uirements. !fficient? intelligi$le out-ut design s*ould im-rove t*e s#stemLs relations*i- wit* t*e user and *el- in decision making. Since t*e re-orts are directing referred $# t*e management for taking decisions and to draw conclusions t*e# must $e designed wit* almost care and t*e details in t*e re-orts must $e sim-le? descri-tive and clear to t*e user. So w*ile designing out-ut t*e following t*ings are to $e considered. O ,etermine w*at information to -resent O Arrange t*e -resentation of information in an acce-ta$le format O ,ecide *ow to distri$ute t*e out-ut to intended recei-ts ,e-ending on t*e nature and future use of out-ut re'uired? t*e# can $e dis-la#ed on t*e monitor for immediate need and for o$taining t*e *ardco-#. 1*e o-tions for t*e out-ut re-orts are given in t*e a--endi". .. PGES9<A3 ,!S9>N 1*e -rocess of develo-ing t*e -rogram software is referred to as -*#sical design. )e *ave to design t*e -rocess $# identif#ing re-orts and t*e ot*er out-uts t*e s#stem will -roduce. <oding t*e -rogram for eac* module wit* its logic is -erformed in t*is ste-. Pro-er software s-ecification is also done in t*is ste-. ..( :O,%3A& ,!S9>N A software s#stem is alwa#s divided into several su$ s#stems t*at makes it easier for t*e develo-ment. A software s#stem t*at is structured into several su$s#stems makes it eas# for t*e develo-ment and testing. 1*e different su$s#stems are known as t*e modules and t*e -rocess of dividing an entire s#stem into su$s#stems is known as modularization or decom-osition.
11

A s#stem cannot $e decom-osed into several su$s#stems in an# wa#. 1*ere must some logical $arrier? w*ic* facilitates t*e se-aration of eac* module. 1*e se-aration must $e sim-le $ut #et must $e effective so t*at t*e develo-ment is not affected. 1*e s#stem under consideration *as $een divided into several modules taking in consideration t*e a$oveFmentioned criteria. 1*e different modules are 16 %ser &egistration :odule 26 ;u#er &egistration :odule 26 Product &egistration :odule. 36 ;idding :odule 6 <losed ;id :anager :odule (6 Online Auction :odule ,A1A;AS! ,!S9>N 1*e overall o$jective in t*e develo-ment of data$ase tec*nolog# *as $een to treat data as an organizational resource and as an integrated w*ole. ,;:S allow data to $e -rotected and organized se-aratel# from ot*er resources. ,ata$ase is an integrated collection of data. 1*e most significant form of data as seen $# t*e -rogrammers is data as stored on t*e direct access storage devices. 1*is is t*e difference $etween logical and -*#sical data. ,ata$ase files are t*e ke# source of information into t*e s#stem. 9t is t*e -rocess of designing data$ase files? w*ic* are t*e ke# source of information to t*e s#stem. 1*e files s*ould $e -ro-erl# designed and -lanned for collection? accumulation? editing and retrieving t*e re'uired information. 1*e organization of data in data$ase aims to ac*ieve t*ree major o$jectivesK F O ,ata integration. O ,ata integrit#. O ,ata inde-endence. 1*e -ro-osed s#stem stores t*e information relevant for -rocessing in t*e :S S23 S!&D!& 288( data$ase. 1*is data$ase contains ta$les? w*ere eac* ta$le corres-onds to one -articular t#-e of information. !ac* -iece of information in ta$le is called a field or column. A ta$le also contains records? w*ic* is a set of fields. All records in a ta$le *ave t*e same set of fields wit* different information. 1*ere are -rimar# ke# fields t*at uni'uel# identif# a record in a ta$le. 1*ere are also fields t*at contain -rimar# ke# from anot*er ta$le called foreign ke#s. 0.1 NO&:A39UA19ON
12

Normalization is a refinement -rocess to resolve t*e issues like inconsistenc#? am$iguit# and redundanc#. 9t is also used to avoid insertion? deletion and u-dating anomalies. All t*e ta$les *ave $een normalized u- to t*e t*ird normal form. 9n s*ort t*e rules for eac* of t*e t*ree normal forms are as $elow. O /irst normal form A relation is said to $e in 1N/ if and onl# if all t*e attri$utes of t*e relation are atomic in nature. O Second normal form 1*e 2N/ is $ased on t*e conce-t of full functional de-endenc#. A relation said to $e in 2N/ if and onl# if it is in 1N/ and no -artial de-endenc# e"ists $etween nonFke# attri$utes and ke# attri$utes. O 1*ird normal form 1*e 3N/ is $ased on t*e conce-t of transitive de-endenc#. A relation in 2N/ is said to $e in 3N/ if no transitive de-endenc# e"ists $etween nonFke# attri$utes and ke# attri$utes. 4. SES1!: 9:P3!:!N1A19ON 9m-lementation includes all t*ose activities t*at take -lace to convert from t*e old s#stem to t*e new. 1*e old s#stem consists of manual o-erations? w*ic* is o-erated in a ver# different manner from t*e -ro-osed new s#stem. A -ro-er im-lementation is essential to -rovide a relia$le s#stem to meet t*e re'uirements of t*e organizations. An im-ro-er installation ma# affect t*e success of t*e com-uterized s#stem. 4.1 9:P3!:!N1A19ON :!1GO,SK 1*ere are several met*ods for *andling t*e im-lementation and t*e conse'uent conversion from t*e old to t*e new com-uterized s#stem. 1*e most secure met*od for conversion from t*e old s#stem to t*e new s#stem is to run t*e old and new s#stem in -arallel. 9n t*is a--roac*? a -erson ma# o-erate in t*e manual older -rocessing s#stem as well as start o-erating t*e new com-uterized s#stem. 1*is met*od offers *ig* securit#? $ecause even if t*ere is a flaw in t*e com-uterized s#stem? we can de-end u-on t*e manual s#stem. Gowever? t*e cost for maintaining two s#stems in -arallel is ver# *ig*. 1*is outweig*s its $enefits. Anot*er commonl# met*od is a direct cut over from t*e e"isting manual s#stem to t*e com-uterized s#stem. 1*e c*ange ma# $e wit* in a week or wit* in a da#. 1*ere are no -arallel activities. Gowever? t*ere is no remed# in case of a -ro$lem. 1*is strateg# re'uires careful -lanning. A working version of t*e s#stem can also $e im-lemented in one -art of t*e organization and t*e -ersonnel will $e -iloting t*e s#stem and c*anges can $e made as and w*en re'uired. ;ut t*is met*od is less -refera$le due to t*e
13

loss of entiret# of t*e s#stem. 4.2 9:P3!:!N1A19ON P3ANK 1*e im-lementation -lan includes a descri-tion of all t*e activities t*at must occur to im-lement t*e new s#stem and to -ut it into o-eration. 9t identifies t*e -ersonnel res-onsi$le for t*e activities and -re-ares a time c*art for im-lementing t*e s#stem. 1*e im-lementation -lan consists of t*e following ste-s. o 3ist all files re'uired for im-lementation. o 9dentif# all data re'uired to $uild new files during t*e im-lementation. o 3ist all new documents and -rocedures t*at go into t*e new s#stem. 1*e im-lementation -lan s*ould antici-ate -ossi$le -ro$lems and must $e a$le to deal wit* t*em. 1*e usual -ro$lems ma# $e missing documentsN mi"ed data formats $etween current and files? errors in data translation? missing data etc. 7 SES1!: O&9!N1A19ON AN, 1&A9N9N> 1*e im-lementation of t*e -ro-osed s#stem includes t*e training of s#stem o-erators. 1raining t*e s#stem o-erators includes not onl# instructions in *ow to use t*e e'ui-ment? $ut also in *ow to diagnose malfunctions and in w*at ste-s to take w*en t*e# occur. So -ro-er training s*ould $e -rovided to t*e s#stem o-erators. No training is com-lete wit*out familiarizing users wit* sim-le s#stem maintenance activities. Since t*e -ro-osed s#stem is develo-ed in a >%9? training will $e com-arativel# eas# t*an s#stems develo-ed in a nonF>%9. 1*ere are different t#-es of training. )e can select offFsite to give de-t* knowledge to t*e s#stem o-erators. Success of t*e s#stem de-ends on t*e wa# in w*ic* it is o-erated and used. 1*erefore t*e 'ualit# of training given to t*e o-erating -erson affects t*e successful im-lementation of t*e s#stem. 1*e training must ensure t*at t*e -erson can *andle all t*e -ossi$le o-erations. 1raining must also include data entr# -ersonnel. 1*e# must also $e given training for t*e installation of new *ardware? terminals? *ow to -ower t*e s#stem? *ow to -ower it down? *ow to detect t*e malfunctions? *ow to solve t*e -ro$lems etc. t*e o-erators must also $e -rovided wit* t*e knowledge of trou$le s*ooting w*ic* involves t*e determination of t*e cause of t*e -ro$lem. 1*e -ro-osed s#stem re'uires trained -ersonnel for o-erating t*e s#stem. ,ata entr# jo$s must $e done utmost carefull# to avoid errors. 1*is will reduce t*e data entr# errors considera$l#. 9t is -refera$le to -rovide t*e -erson wit* some kind of o-erating manuals t*at will e"-lain all t*e details of t*e s#stem. 7.1 POS1 9:P3!:!N1A19ON &!D9!) After t*e s#stem is im-lemented? a review s*ould $e conducted to determine
1

w*et*er t*e s#stem is meeting e"-ectations and w*ere im-rovements are needed. S#stem 'ualit# ? user confidence and o-erating s#stems statistics are accessed t*roug* suc* tec*ni'ue event logging ? im-act evaluation and attitude surve#s. 1*e review not onl# assesses *ow well t*e -ro-osed s#stem is designed and im-lemented? $ut also is a valua$le source of information t*at can $e a--lied to a critical evaluation of t*e s#stem. 22 1*e reviews are conducted $# t*e o-erating -ersonals as well as t*e software develo-ers in order to determine *ow well t*e s#stem is working? *ow it *as $een acce-ted and w*et*er adjustments are needed. 1*e review of t*e s#stem is *ig*l# essential to determine t*e future en*ancements re'uired $# t*e s#stem. 1*e s#stem can $e considered successful onl# if information s#stem *as met its o$jectives. 1*e review anal#ses t*e o-inion of t*e em-lo#ees and identifies t*e attitudes towards t*e new com-uterized s#stem. Onl# w*en t*e merits and demerits of t*e im-lemented s#stem are known? one can determine w*at all additional features it re'uires are. 18.SES1!: 1!S19N> S#stem testing is a critical as-ect of Software 2ualit# Assurance and re-resents t*e ultimate review of s-ecification? design and coding. 1esting is a -rocess of e"ecuting a -rogram wit* t*e intent of finding an error. A good test is one t*at *as a -ro$a$ilit# of finding an as #et undiscovered error. 1*e -ur-ose of testing is to identif# and correct $ugs in t*e develo-ed s#stem. Not*ing is com-lete wit*out testing. 1esting is t*e vital to t*e success of t*e s#stem. 9n t*e code testing t*e logic of t*e develo-ed s#stem is tested. /or t*is ever# module of t*e -rogram is e"ecuted to find an error. 1o -erform s-ecification test? t*e e"amination of t*e s-ecifications stating w*at t*e -rogram s*ould do and *ow it s*ould -erform under various conditions. %nit testing focuses first on t*e modules in t*e -ro-osed s#stem to locate errors. 1*is ena$les to detect errors in t*e coding and logic t*at are contained wit*in t*at module alone. 1*ose resulting from t*e interaction $etween modules are initiall# avoided. 9n unit testing ste- eac* module *as to $e c*ecked se-aratel#. S#stem testing does not test t*e software as a w*ole? $ut rat*er t*an integration of eac* module in t*e s#stem. 1*e -rimar# concern is t*e com-ati$ilit# of individual modules. One *as to find areas w*ere modules *ave $een designed wit* different s-ecifications of data lengt*s? t#-e and data element name. 1esting and validation are t*e most im-ortant ste-s after t*e im-lementation of t*e develo-ed s#stem. 1*e s#stem testing is -erformed to ensure t*at
1(

t*ere are no errors in t*e im-lemented s#stem. 1*e software must $e e"ecuted several times in order to find out t*e errors in t*e different modules of t*e s#stem. Dalidation refers to t*e -rocess of using t*e new software for t*e develo-ed s#stem in a live environment i.e.? new software inside t*e organization? in order to find out t*e errors. 1*e validation -*ase reveals t*e failures and t*e $ugs in t*e develo-ed s#stem. 9t will $e come to know a$out t*e -ractical difficulties t*e s#stem faces w*en o-erated in t*e true environment. ;# testing t*e code of t*e im-lemented software? t*e logic of t*e -rogram can $e e"amined. A s-ecification test is conducted to c*eck w*et*er t*e s-ecifications stating t*e -rogram are -erforming under various conditions. A-art from t*ese tests? t*ere are some s-ecial tests conducted w*ic* are given $elowK Peak 3oad 1estsK 1*is determines w*et*er t*e new s#stem will *andle t*e volume of activities w*en t*e s#stem is at t*e -eak of its -rocessing demand. 1*e test *as revealed t*at t*e new software for t*e agenc# is ca-a$le of *andling t*e demands at t*e -eak time. Storage 1estingK 1*is determines t*e ca-acit# of t*e new s#stem to store transaction data on a disk or on ot*er files. 1*e -ro-osed software *as t*e re'uired storage s-ace availa$le? $ecause of t*e use of a num$er of *ard disks. Performance 1ime 1estingK 1*is test determines t*e lengt* of t*e time used $# t*e s#stem to -rocess transaction data. 9n t*is -*ase t*e software develo-ed 1esting is e"ercising t*e software to uncover errors and ensure t*e s#stem meets defined re'uirements. 1esting ma# $e done at levels O %nit 3evel O :odule 3evel O 9ntegration H S#stem O &egression %N91 1!S19N> A %nit corres-onds to a screen Iform in t*e -ackage. %nit testing focuses on verification of t*e corres-onding class or Screen. 1*is testing includes testing of control -at*s? interfaces? local data structures? logical decisions? $oundar# conditions? and error *andling. %nit testing ma# use 1est ,rivers? w*ic* are control -rograms to coFordinate test case in-uts and out-uts? and 1est stu$s? w*ic* re-lace lowFlevel modules. A stu$ is a dumm# su$-rogram. 18.2 :O,%3! 3!D!3 1!S19N>
1.

:odule 1esting is done using t*e test cases -re-ared earlier. :odule is defined during t*e time of design. 18.3 9N1!>&A19ON H SES1!: 1!S19N> 9ntegration testing is used to verif# t*e com$ining of t*e software modules. 9ntegration testing addresses t*e issues associated wit* t*e dual -ro$lems of verification and -rogram construction. S#stem testing is used to verif#? w*et*er t*e develo-ed s#stem meets t*e re'uirements. 18. &!>&!SS9ON 1!S19N> !ac* modification in software im-acts unmodified areas? w*ic* results serious injuries to t*at software. So t*e -rocess of reFtesting for rectification of errors due to modification is known as regression testing. 9nstallation and ,eliver# 9nstallation and ,eliver# is t*e -rocess of delivering t*e develo-ed and tested software to t*e customer. &efer t*e su--ort -rocedures Acce-tance and Project <losure Acce-tance is t*e -art of t*e -roject $# w*ic* t*e customer acce-ts t*e -roduct. 1*is will $e done as -er t*e Project <losure? once t*e customer acce-ts t*e -roductN closure of t*e -roject is started. 1*is includes metrics collection? P<,? etc. 11.:A9N1!NAN<! :aintenance is making ada-tation of t*e software for e"ternal c*anges 5re'uirements c*anges or en*ancements6 and internal c*anges 5fi"ing $ugs6. )*en c*anges are made during t*e maintenance -*ase all -receding ste-s of t*e model must $e revisited. 1*ere are t*ree t#-es of maintenanceK 1. <orrective 5/i"ing $ugsIerrors6 2. Ada-tive 5%-dates due to environment c*anges6 3. Perfective 5!n*ancements? re'uirements c*anges. 12. 1A;3!S 1a$le 12.1 %S!&9N/O /ield 1#-e <onstraints %ser 9d Num$er Primar# ke# 3oginName Darc*ar Passwd Darc*ar /irstName Darc*ar 3astName Darc*ar &ole Small9nt &eg,ate ,ate1ime Address Darc*ar !mail Darc*ar
10

1*e a$ove ta$le stores t*e user details of t*ose w*o register at t*e site. 1*e a$ove ta$le stores details of Products availa$le for $idding. 1a$le 12. ;9,1&ANSA<19ON /ield 1#-e <onstraints 1rans9d Num$er Primar# =e# %ser9d Num$er /oreign =e# Prod9d Num$er /oreign =e# 9ncAmt :one# ;idAmt :one# ,ate<reated ,ate1ime 1*e a$ove ta$le stores t*e details of ;idding 1ransaction. 1a$le 12.( <3OS!,;9,S <GAP1!& 13 /9>%&!S /ig 13.1 3O) 3!D!38 ,/, Seller <ollects ;id Amt /ig13.2 G9>G 3!D!3 ,/, /ig 13.3 GO:! PA>! /ig 13.( P&O,%<1 &!>9S1&A19ON /O&: Seller *ave to register *is -roducts $efore -lacing it for $idding. /ig 13.. ;9,,9N> /O&: ;idders can -lace $id value for t*eir favourite -roducts t*roug* t*is form. /ig 13.0 <A1!>O&E A,,919ON /O&: )e$Administrator can add categories t*roug* t*is form. /ig 13.18 <3OS!, ;9, :ANA>!& )e$Administrator can notif# $ot* seller and $u#er and can -erform u-dation o-eration t*roug* t*is form. <GAP1!& 1 <ON<3%S9ON 1*e -roject re-ort entitled JON39N! A%<19ONJ *as come to its conclusion. 1*e new s#stem *as $een develo-ed wit* so muc* care t*at it is free of errors and at t*e same time efficient and less time consuming. S#stem is ro$ust. Also -rovision is -rovided for future develo-ments in t*e s#stem. APP!N,9<!S OD!&D9!) O/ :9<&OSO/1.N!1 .N!1 re-resents :icrosoftLs vision of t*e future of a--lications in t*e 9nternet age. .N!1 -rovides en*anced intero-era$ilit# features $ased u-on o-en 9nternet standards. :icrosoft .N!1 re-resents a great im-rovement. . :icrosoft .N!1 -rovides t*e followingK QRST A ro$ust runtime -latform? t*e <3& QRST :ulti-le language develo-ment
14

QRST An e"tensi$le -rogramming model? t*e .N!1 /ramework? w*ic* -rovides a large class li$rar# of reusa$le code availa$le from multi-le languages QRST A networking infrastructure $uilt on to- of 9nternet standards t*at su--orts a *ig* level of communication among a--lications QRST A new mec*anism of a--lication deliver#? t*e )e$ service? t*at su--orts t*e conce-t of an a--lication as a service QRST Powerful develo-ment tools .N!1 /ramework Overview 1*e .N!1 /ramework consists of t*e <3&? t*e .N!1 /ramework <lass 3i$rar#? t*e <ommon 3anguage S-ecification 5<3S6? a num$er of .N!1 languages? and Disual Studio .N!1. <ommon 3anguage &untime 1*e runtime environment -rovided $# .N!1? t*e <3&? manages t*e e"ecution of code and -rovides useful services. 1*e services of t*e <3& are e"-osed t*roug* -rogramming languages. 1*e s#nta" for t*ese services varies from language to language? $ut t*e underl#ing e"ecution engine -roviding t*e services is t*e same. Not all languages e"-ose all t*e features of t*e <3&. 1*e language wit* t*e $est ma--ing ( to t*e <3& is t*e new language <B. D;.N!1? *owever? does an admira$le jo$ of e"-osing t*e functionalit#. .N!1 /ramework <lass 3i$rar# 1*e .N!1 /ramework class li$rar# is *uge? com-rising more t*an 2?(88 classes. All t*is functionalit# is availa$le to all t*e .N!1 languages. 1*e li$rar# consists of four main -artsK 1. ;ase class li$rar# 5w*ic* includes networking? securit#? diagnostics? 9IO? and ot*er t#-es of o-erating s#stem services6 2. ,ata and M:3 classes 3. )indows %9 . )e$ services and )e$ %9 <ommon 3anguage S-ecification 1*e <3S is an agreement among language designers and class li$rar# designers a$out t*ose features and usage conventions t*at can $e relied u-on. <3S rules a--l# to -u$lic features t*at are visi$le outside t*e assem$l# w*ere t*e# are defined. 3anguages in .N!1 :icrosoft itself is -roviding four <3SFcom-liant languages. D;.N!1? <B? and <VV wit* managed e"tensions are e"tenders. @scri-t .N!1 is a
17

consumer. Disual Studio .N!1 2883 Disual Studio .N!1 2883 includes a range of new features and en*ancements for ever# t#-e of develo-er? and offers ke# im-rovements directed at mo$ile device develo-ers and enter-rise develo-ers. ;ase classes -rovide standard functionalit# suc* as in-utIout-ut? string mani-ulation? securit# management? network communications? t*read management? te"t management? and user interface design features. 1*e A,O.N!1 classes ena$le develo-ers to interact wit* data accessed in t*e form of M:3 t*roug* t*e O3! ,;? O,;<? Oracle? and S23 Server interfaces. 1*e ASP.N!1 classes su--ort t*e develo-ment of )e$F$ased a--lications and )e$ services. 1*e )indows /orms classes su--ort t*e develo-ment of deskto-F$ased smart client a--lications. ASP.N!1 ASP.N!1 is a -rogramming framework $uilt on t*e common language runtime t*at can $e used on a server to $uild -owerful )e$ a--lications. ASP.N!1 offers several im-ortant advantages over -revious )e$ develo-ment modelsK !n*anced Performance ASP.N!1 is com-iled common language runtime code running on t*e server. %nlike its inter-reted -redecessors? ASP.N!1 can take advantage of earl# $inding? justFinFtime com-ilation? native o-timization? and cac*ing services rig*t out of t*e $o". 1*is amounts to dramaticall# $etter -erformance $efore #ou ever write a line of code )orldF<lass 1ool Su--ort 1*e ASP.N!1 framework is com-lemented $# a ric* tool$o" and designer in t*e Disual Studio integrated develo-ment environment. )ES9)E> editing? dragFandFdro- server controls? and automatic de-lo#ment are just a few of t*e features t*is -owerful tool -rovides. Power and /le"i$ilit#. ;ecause ASP.N!1 is $ased on t*e common language runtime? t*e -ower and fle"i$ilit# of t*at entire -latform is availa$le to )e$ a--lication develo-ers. 1*e .N!1 /ramework class li$rar#? :essaging? and ,ata Access solutions are all seamlessl# accessi$le from t*e )e$. ASP.N!1 is also languageFinde-endent? so #ou can c*oose t*e language t*at $est a--lies to #our a--lication or -artition #our a--lication across man# languages. Sim-licit# ASP.N!1 makes it eas# to -erform common tasks? from sim-le form su$mission and client aut*entication to de-lo#ment and site configuration.
28

/or e"am-le? t*e ASP.N!1 -age framework allows #ou to $uild user interfaces t*at cleanl# se-arate a--lication logic from -resentation code and to *andle events in a sim-le? Disual ;asic F like forms -rocessing model. Additionall#? t*e common language runtime sim-lifies develo-ment? wit* managed code services suc* as automatic reference counting and gar$age collection :anagea$ilit# ASP.N!1 em-lo#s a te"tF$ased? *ierarc*ical configuration s#stem? w*ic* sim-lifies a--l#ing settings to #our server environment and )e$ a--lications. ;ecause configuration information is stored as -lain te"t? new settings ma# $e a--lied wit*out t*e aid of local administration tools. 1*is Jzero local administrationJ -*iloso-*# e"tends to de-lo#ing ASP.N!1 /ramework a--lications as well. An ASP.N!1 /ramework a--lication is de-lo#ed to a server sim-l# $# co-#ing t*e necessar# files to t*e server. Scala$ilit# and Availa$ilit# ASP.N!1 *as $een designed wit* scala$ilit# in mind? wit* features s-ecificall# tailored to im-rove -erformance in clustered and multi-rocessor environments. /urt*er? -rocesses are closel# monitored and managed $# t*e ASP.N!1 runtime? so t*at if one mis$e*aves 5leaks? deadlocks6? a new -rocess can $e created in its -lace? w*ic* *el-s kee- #our a--lications constantl# availa$le to *andle re'uests <ustomiza$ilit# and !"tensi$ilit# ASP.N!1 delivers a wellFfactored arc*itecture t*at allows develo-ers to J-lug inJ t*eir code at t*e a--ro-riate level. 9n fact? it is -ossi$le to e"tend or re-lace an# su$com-onent of t*e ASP.N!1 runtime wit* #our own customFwritten com-onent. Securit# )it* $uilt in )indows aut*entication and -erFa--lication configuration? #ou can $e assured t*at #our a--lications are secure. 3anguage Su--ort 1*e :icrosoft .N!1 Platform currentl# offers $uiltFin su--ort for t*ree languagesK <B? Disual Studio 3anguage <om-ati$ilit# 1*e differences $etween t*e D;Scri-t used in ASP and t*e Disual ;asic .N!1 language used in ASP.N!1 are $# far t*e most e"tensive of all t*e -otential migration issues. Not onl# *as ASP.N!1 de-arted from t*e D;Scri-t language to JtrueJ Disual ;asic? $ut t*e Disual ;asic language itself *as undergone significant c*anges in t*is release. 1OO3 S!3!<1!,K D;. N!1 Disual ;asic.Net is designed to $e a fast and eas# wa# to create .N!1
21

a--lications? including )e$ services and ASP.N!1 )e$ a--lications. A--lications written in Disual ;asic are $uilt on t*e services of t*e common language runtime and take full advantage of t*e .N!1 /ramework. Disual ;asic .N!1 5D;.N!16 is an o$jectForiented com-uter language t*at can $e viewed as an evolution of :icrosoftLs Disual ;asic 5D;6 im-lemented on t*e :icrosoft .N!1 framework. 9ts introduction *as $een controversial? as significant c*anges were made t*at $roke $ackward com-ati$ilit# wit* D; and caused a rift wit*in t*e develo-er communit#. 9t is full# integrated wit* t*e .N!1 /ramework and t*e common language runtime?1 w*ic* toget*er -rovide language intero-era$ilit#? gar$age collection? en*anced securit#? and im-roved versioning su--ort. :9<&OSO/1 S23 S!&D!& 288( S23 Server 288( e"ceeds de-enda$ilit# re'uirements and -rovides innovative ca-a$ilities t*at increase em-lo#ee effectiveness? integrate *eterogeneous 91 ecos#stems? and ma"imize ca-ital and o-erating $udgets. S23 Server 288( -rovides t*e enter-rise data management -latform #our organization needs to ada-t 'uickl# in a fastFc*anging environment. )it* t*e lowest im-lementation and maintenance costs in t*e industr#? S23 Server 288( delivers ra-id return on #our data management investment. S23 Server 288( su--orts t*e ra-id develo-ment of enter-riseFclass $usiness a--lications t*at can give #our com-an# a critical com-etitive advantage. !as#FtoF%se ;usiness 9ntelligence 1*ese tools t*roug* ric* data anal#sis and data mining ca-a$ilities t*at integrate wit* familiar a--lications suc* as :icrosoft Office? S23 Server 288( ena$les #ou to -rovide all of #our em-lo#ees wit* critical? timel# $usiness information tailored to t*eir s-ecific information needs. !ver# co-# of S23 Server 288( s*i-s wit* a suite of ;9 services. SelfF1uning and :anagement <a-a$ilities &evolutionar# selfFtuning and d#namic selfFconfiguring features o-timize data$ase -erformance? w*ile management tools automate standard activities. >ra-*ical tools and wizards sim-lif# setu-? data$ase design? and -erformance monitoring? allowing data$ase administrators to focus on meeting strategic $usiness needs. ,ata :anagement A--lications and Services %nlike its com-etitors? S23 Server 288( -rovides a -owerful and com-re*ensive data management -latform. !ver# software license includes e"tensive management and develo-ment tools? a -owerful e"traction? transformation? and loading 5!136 tool? $usiness intelligence and anal#sis services? and new ca-a$ilities suc* as Notification Services. 1*e result is t*e $est overall $usiness value availa$le.
22

S23 Server 288( !nter-rise !dition !nter-rise !dition includes t*e com-lete set of S23 Server data management and anal#sis features and is uni'uel# c*aracterized $# several features t*at make it t*e most scala$le and availa$le edition of S23 Server 288(. 9t scales to t*e -erformance levels re'uired to su--ort t*e largest )e$ sites? !nter-rise Online 1ransaction Processing 5O31P6 s#stems and ,ata )are*ousing s#stems. 9ts su--ort for failover clustering also makes it ideal for an# mission critical lineFofF$usiness a--lication. &!S%:! 1*e develo-ed s#stem is fle"i$le and c*anges can $e made easil#. 1*e s#stem is develo-ed wit* an insig*t into t*e necessar# modification t*at ma# $e re'uired in t*e future. Gence t*e s#stem can $e maintained successfull# wit*out muc* rework. One of t*e main future en*ancements of our s#stem is to en*ance t*e s#stem securit# $# adding t*e o-tion of ;lacklisting defaulting $idders. 1*ere also can $e o-tion for rating sellers. Online -a#ment settlement can $e incor-orated into t*e s#stem.

ASP.N!1 <ON1&O3SK 1.DA39,A19ON <ON1&O3K a.&e'uired/ieldDalidatorK F 1*e &e'uired/ieldDalidator control ensures t*at t*e re'uired field is not em-t#. 9t is generall# tied to a te"t $o" to force in-ut into t*e te"t $o". $.&egular !"-ression DalidatorKF 1*e &egular!"-ressionDalidator allows validating t*e in-ut te"t $# matc*ing against a -atter against a regular e"-ression. 1*e regular e"-ression is set in t*e Dalidation!"-ression -ro-ert#.

23

c.<om-areDalidatorKF 1*e <om-areDalidator control com-ares a value in one control wit* a fi"ed value? or? a value in anot*er control. d.&angeDalidatorK 1*e &angeDalidator control verifies t*at t*e in-ut value falls wit*in a -redetermined range.

2.,A1A ;O%N, <ON1&O3SK a.>rid viewKFA recurring task in software develo-ment is to dis-la# ta$ular data. ASP.N!1 -rovides a num$er of tools for s*owing ta$ular data in a grid? including t*e >ridDiew control. )it* t*e >ridDiew control? #ou can dis-la#? edit? and delete data from man# different kinds of data sources? including data$ases? M:3 files? and $usiness o$jects t*at e"-ose data. $. ,ata3ist KF,ata3ist )e$ server control dis-la#s rows of data$ase information in a customiza$le format. 1*e format for dis-la#ing t*e data is defined in tem-lates t*at #ou create. Eou can create tem-lates for items? alternating items? selected items? and edit items. Geader? footer? and se-arator tem-lates are also availa$le to let #ou customize t*e overall a--earance of t*e ,ata3ist. ;# including ;utton )e$ server controls in t*e tem-lates? #ou can connect t*e list items to code t*at allows users to switc* $etween dis-la#? selection? and editing modes. c.3ist DiewKF 1*e ASP.N!1 3istDiew control ena$les #ou to $ind to data items t*at are returned from a data source and dis-la# t*em. Eou can dis-la# data in -ages. Eou can dis-la# items individuall#? or #ou can grou- t*em.

d.&e-eaterKF 1*e &e-eater )e$ server control is a dataF$ound container control t*at -roduces a list of individual items. Eou define t*e la#out of individual items on a )e$ -age $# using tem-lates. )*en t*e -age runs? t*e control re-eats t*e la#out for eac* item in t*e data source. 3.A@AMK A@AM stands for As#nc*ronous @avaScri-t and M:3. 1*is is a cross -latform tec*nolog# w*ic* s-eeds u- res-onse time. 1*e A@AM server controls add scri-t to t*e -age w*ic* is e"ecuted and -rocessed $# t*e $rowser. Aja" <ontrol 1oolkit K

/illterd te"t $o"KF/iltered1e"t;o" is an e"tender w*ic* -revents a user from entering invalid c*aracters into a te"t $o". Note t*at since t*is effect can $e avoided $# deactivating @avaScri-t? #ou s*ould use t*is e"tender as a convenience for #our users? $ut #ou must never e"-ect t*at t*e data $eing sent to t*e server consists of JvalidJ c*ars onl#.

<alander e"tenderK F<alendar is an ASP.N!1 A@AM e"tender t*at can $e attac*ed to an# ASP.N!1 1e"t;o" control. 9t -rovides clientFside dateF-icking functionalit# wit* customiza$le date format and %9 in a -o-u- control. Eou can interact wit* t*e calendar $# clicking on a da# to set t*e date? or t*e J1oda#J link to set t*e current date.

<olla-si$lePanelK F1*e <olla-si$lePanel is a ver# fle"i$le e"tender t*at allows #ou to easil# add colla-si$le sections to #our we$ -age.

2(

1*is e"tender targets an# ASP.N!1 Panel control. 1*e -age develo-er s-ecifies w*ic* control5s6 on t*e -age s*ould $e t*e o-enIclose controller for t*e -anel? or t*e -anel can $e set to automaticall# e"-and andIor colla-se w*en t*e mouse cursor moves in or out of it? res-ectivel#.

Password Strengt*K FPasswordStrengt* is an ASP.N!1 A@AM e"tender t*at can $e attac*ed to an ASP.N!1 1e"t;o" control used for t*e entr# of -asswords. 1*e PasswordStrengt* e"tender s*ows t*e strengt* of t*e -assword in t*e 1e"t;o" and u-dates itself as t*e user t#-es t*e -assword. 1*e indicator can dis-la# t*e strengt* of t*e -assword as a te"t message or wit* a -rogress $ar indicator.

4.

,A1A /3O) ,9A>&A:S 5,/,6KF A ,/, i.e. ,ata /low ,iagram is a gra-*ical tool?

w*ic* *as t*e -ur-ose of clarif#ing s#stem re'uirements and identif#ing major transformation t*at will $e -rograms in t*e s#stem design. 9t de-icts t*e information flow and transformation t*at occurs? as data moves from in-ut to out-ut. 1*e ,/, -rovides a mec*anism for functional modeling as well as information flow modeling. An e"ternal entit# w*ic* can $e a source or a destin# is re-resented $# a solid s'uare. 9t lies outside t*e conte"t of t*e s#stem. A -rocess indicates t*e work t*at is -erformed on data. A circle re-resents a -rocess. ,ata flow takes -lace $etween various com-onents of t*e s#stem H *ence re-resented $# an arrow mark. A data store is a re-ositor# for data. 9t is re-resented $# an o-enFended rectangle. :ain S#stem ,/, Database
S#stem

End User

2.

:ain S#stem take t*e data from t*e data$ase wit* -ro-er administration and -rovide it to t*e !ndusers.

AON39N! A%<19ONC -rovide real s#stem to $u#er?seller and admin select t*e -roducts and make account in our s#stem.

<ON1!M1 ,9A>&A: O/ WON39N! SGOPP9N>+ 1*e S#stem -rovide Account information to t*e !ndFusers and also -rovide good knowledge of new -roducts w*ic* are new launc*ed in t*e market And also -rovide *ome deliver# of -erc*ased items $# enduser. !nduser can -a# t*e $ill online and offline $ut it is necessar# to -a# some amount of $ill w*en user make t*e order.

)*en t*e S#stem is loaded ? first of all *ome-age is loaded. After t*is ?it de-end u-on t*e user w*ic* t*ings *e want to -urc*ase. )e -rovide man#

20

direct links and searc* tec*ni'ues so t*at user ca eas# find t*e desired -roduct. and its -rice and no of items -erc*ased. 3ogin PanelK 9t is login -anel . Ge can c*ange username?-assword ot*er information. %ser can c*eck *is -urc*ased items along wit* s*i--ing detail . 1*is s#stem also -rovide com-lete access to t*e items w*ic* user *as -erc*ased and

3O>9N Panel

7. SES1!: ,!S9>N
24

7.1 ,A1A;AS! ,!S9>NK Admin ta$le

<ategor# 1a$le

27

;id Product

9.2 FORM DESIGN: 9.2.1 HOMEPAGE :38

Admin Panel

&egistration

31

3ogin;u#erI%ser5Seller6

32

%serIAddProduct

%serI:#Product

33

;u#erI,etail of -roduct

;u#erI;id-roduct

%serI:#$idPrduct

A$out %s

3(

<ontact %s

3.