E-Bazar Computer Project in Asp.Net with Project Report

ACKNOWLEDGEMENT

We thank the almighty for giving us the courage & perseverance in completing the project. This project itself is an acknowledgement for all those who have given us their heart-felt-co-operation in making it a grand success.

We are thankful to our principal, Prof.------------ for providing the necessary infrastructure and labs. We are greatly indebted to, Head of nformation Technology, Mr.------------ for providing valuable guidance at every stage of this project work.

We are also thankful to the project coordinator, Mr.-------

for

e!tending their sincere & heartfelt guidance through out this project work. Without their supervision and many hours of devoted guidance, stimulating & constructive criticism, this thesis would never come out in this form.

t is a pleasure to e!press our deep and sincere gratitude to the project "uide Mr,---------and are profoundly grateful towards the unmatched help rendered by him. #ur special thanks to all the lectures of nformation Technology, for their valuable advises at every stage of this work.

$ast but not the least% we would like to e!press our deep sense and earnest thanks giving to our dear parents for their moral support and heartfelt cooperation in doing the project. We would also like to thank our friends,

whose direct or indirect help has enabled us to complete this work successfully.

ABSTRACT The -&onnect is an application that has been developed for a wellestablished regional bank operating primarily in south ndia. The bank has several branches in key cities and towns in the north. n the world of this competitive environment and technological development, the bank has been totally computeri'ed in the last ( years, and to increase its customer base has started planning, for a concept called as e-banking% with this concept the bank wants to move very nearer to the customers and increase its basic operational strategies. Through -&onnectthe bank wants to introduce the core concept of T based )nabled *ervices + T)*,. The -&onnectservices are e!ecuted only upon the customer, and these -&onnectservices would fully integrate with the core banking solution that is already in usage. The major idea is to provide a series of services to the customer through the internet, and make the customer feel fle!ible in calling out simple tasks faster instead of making visit to the bank every time. The -&onnectservice is open only to savings bank. &ustomers and not for current account holders. The customer is privileged to use most of the system only as a viewing phase, the only online transactions the customer can do are che-uebook re-uisition and fund transfer among his personal accounts. The project ahs been planned to be having the view of distributed architecture, with centrali'ed storage of the database. The application for the storage of the data has been planned. .sing the constructs of /**0$*erver1222 and all the user interfaces have been designed using the 3*4.5et technologies. The database connectivity is planned using the 6*0$ &onnection7 methodology. The standards of security and data protective mechanism have been given a big choice for proper usage. The application

takes care of different modules and their associated reports, which are produced as per the applicable strategies and standards that are put forwarded by the administrative staff. CONTENTS

1. i. ii. iii. 2. i. ii. iii. 3. . i. ii. iii. iv. v. !. i. ii. iii. ".

INTRODUCTION 4.84#*) #9 48#:)&T *&#4) #9 48#:)&T 48#:)&T #;)8; )W PROJECT ANALYSIS )< *T 5" *=*T)/ 48#4#*)> *=*T)/ H?W and *?W *4)& 9 &3T #5* SYSTEM DEVELOPMENT ENVIRONMENT PROJECT DESIGNING >9> +>ata 9low >iagrams, ./$ >iagrams )8 >iagrams >@ >esign *creens PROJECT TESTING 4erformance Testing .nit Testing ntegration Testing CONCLUSION

#. &.

$UTURE EN%ANCEMENT BIBLIOGRAP%Y

INTRODUCTION 1.1 P'r(o)* of Pro+*,-

This document contains a description for .E-B/012034 enhancement. This document will contain the functional re-uirements of the project and how the developers will enhance the project to achieve all the objectives. The *8* will serve as a guide for the client and the developers. *ection 1 is concentrated more on the

1.2

S,o(* of -5* (ro+*,-

The entire project has been developed keeping in view of the distributed client server computing technology, in mind. The specification have been normali'ed up to (59 to eliminate all the anomalies that may arise due to the database transaction that are e!ecuted by the general users and the organi'ational administration. The user interfaces are browser specific to give distributed accessibility for the overall system. The internal database has been selected as /**0$ server 122.The basic constructs of table spaces, clusters and inde!es have been e!ploited to provide higher consistency and reliability for the data storage. The /*-*0$ server 122 was a choice as it provides the constructs of high-level reliability and security. The total front end was dominated using the 3*4.5et technologies. 3t all proper levels high care was taken to check that the system manages the data consistency with proper business rules or validations. The database connectivity was planned using the latest 7*0$ &onnection7 technology provided by /icrosoft &orporation. The authentication and authori'ation was crosschecked at all the relevant stages. The user level accessibility has been restricted into two 'ones namely. The administrative 'one and the normal user 'one.3bout the #rgani'ationThe 5ational @ank +T5@, is a well-established regional bank operating primarily in south ndia, but with several branches in key cities and towns in the 5orth. >fgegdfgdfgdfgdf

PROJECT OVERVIEW

The general description gives an Ae!ecutive overviewA and is very client-oriented. t e!pounds on the functional and data re-uirements of the application. t also lists the limitations, assumptions and dependencies of the application. *ection (.2, the specific re-uirements section, includes the developersB technical view of the clientCs e!pectation of the application. t also touches on the performance and -uality re-uirements of the application and provides a solid definition of the interface Number of Modules The system after careful analysis has been identified to be presented with the following modules.
D. E6(7o8** 20for6/-2o0 6o9'7*: The module manages the information of all the employees who practically e!ist for this organi'ation. )ach employee is e!clusively associated through a specific department and authori'ed designation. The module manages all the transactional relations that generically arise as and when the system has been e!ecuted, upon the re-uirements. 1. B/01) I0for6/-2o0 6o9'7*: This module specifies the integrated and interrelation information alert the banks and their branches. The module also specifically states the different services each bank can provide and integrates itself with customerBs accounts information. (. C')-o6*r) /,,o'0-) 20for6/-2o0 6o9'7*: The module

maintains the actual customers list that have availed bank accounts upon this system. The module integrates itself with the banks and the types of services the bank can provide.

E. C')-o6*r -r/0)/,-2o0 6o9'7*: This module maintains the information related to all the transaction that are e!ecuted by the customer upon the the transaction. -&onnectapplication. The module integrates itself with entities like transaction types to check the consistency of

5. $'09 Tr/0)f*r 6/)-*r: This module maintains the information
related to the funds that have been transferred by the customer from one of his account to another account of his own. This module helps the customer in e!ecuting the fund transfer with out the physical visit to the banks premises.

C5*;'**) A'-5or) T5* M*/0) To

D. 4ublish online documents with headings, te!t, tables, list, photos etc. 1. 8etrive online information via hyperte!t links, at the click of a button (. >esign forms for conducting transactions with remote services, for use in searching information, making reservation, ordering products etc.% E. ncludes spreadsheets, video clips, sound clips, and other applications directly in the documents.

So6* %TML T/3)

KHT/$L

M*tarting an HT/$ tag

KH)3>L

M &reating a web pageBs head

KT T$)L

M "iving a web page Ns body

K?H)3>L

M )nding a web pages head

K?@#>=L

M )nding a web pages body

K?HT/$L

M)nding a web page

K9#8/L

M &reating a HT/$ forms

K 54.T T=4)[email protected]#5L

M &reating a buttons

K 54.T T=4)O&H)&J@#L K@#>=L K*&8 4T $35".3")O7:ava*cript7L K?*&8 4TL K?@#>=LK?HT/$L JAVASCRIPTS OBJECTS :ava*cript is an object-oriented language. :ava*cript comes with a number of predefined objects. O/S,r2(D. >ocumentM &orresponds to the current Web pageBs body. .sing this object, you have access to the HT/$ of the page itself, including the all links, images and anchors in it. 1. 9ormM Holds information about HT/$ forms in the current page. (. 9rameM 8efers to a frame in the browserBs window.

E. HistoryM Holds the records of sites the Web browser has visited before reaching page. G. 5avigatorM 8efers to the browser itself, letting you determine what browser the user has. H. WindowM 8efers to the current browser window. the current page. F. $ocationM Holds information about the location of the current web

JAVASCRIPTS EVENTS

*ome of the events of :ava*cript D. on &hangeM #ccurs when data in a control, like a te!t field, changes. 1. on &lickM #ccurs when an element is clicked. (. on 9ocusM #ccurs when an element gets the focus. E. on /ouse >ownM #ccurs when a mouse button goes down. F. on 8esetM #ccurs when the user clicks the reset button.

JAVASCRIPTS $UNCTIONS

D*,7/r/-2o0 of f'0,-2o0

*ynta!M function function name +, P Q Q R

Write these functions in K*&8 4TL tag.

3. INTRODUCTION ABOUT .NET

O>*r>2*B of -5* .NET $r/6*Bor1 The .5)T 9ramework is a new computing platform that simplifies application development in the highly distributed environment of the nternet. The .5)T 9ramework is designed to fulfill the following objectivesM


To provide a consistent object-oriented programming environment

whether object code is stored and e!ecuted locally, e!ecuted locally but nternet-distributed, or e!ecuted remotely.


To provide a code-e!ecution environment that minimi'es software

deployment and versioning conflicts.



To provide a code-e!ecution environment that guarantees safe

e!ecution of code, including code created by an unknown or semi-trusted third party.


To

provide

a

code-e!ecution

environment

that

eliminates

the

performance problems of scripted or interpreted environments.


To make the developer e!perience consistent across widely varying

types of applications, such as Windows-based applications and Web-based applications.


To build all communication on industry standards to ensure that code

based on the .5)T 9ramework can integrate with any other code. The .5)T 9ramework has two main componentsM the common language runtime and the .5)T 9ramework class library. The common language runtime is the foundation of the .5)T 9ramework. =ou can think of the runtime as an agent that manages code at e!ecution time, providing core services such as memory management, thread management, and remoting, while also enforcing strict type safety and other forms of code accuracy that ensure security and robustness. n fact, the concept of code management is a fundamental principle of the runtime. &ode that targets the runtime is known as managed code, while code that does not target the runtime is known as unmanaged code. The class library, the other main component of the .5)T 9ramework, is a comprehensive, object-oriented collection of reusable types that you can use to develop applications ranging from traditional command-line or graphical user interface +". , applications to

applications based on the latest innovations provided by 3*4.5)T, such as Web 9orms and @/* +8elational database management system,. 9or e!ample, if you need to create a connection to a *0$ *erver database, youBll use a connection class named *0$ &onnection. #ne of the key underlying ideas of the 3>#.5)T provider model is that itBs e!tensible. n other words, developers can create their own provider for proprietary data sources. n fact, numerous proof-of-concepts e!amples are available that show how you can easily create custom 3>#.5)T providers to

wrap nonrelational data stores, such as the file system or a directory service. *ome third-party vendors also sell custom providers for .5)T.

The .5)T 9roamework is bundled with a small set of four providersM • SEL S*r>*r Pro>29*r: 4rovides optimi'ed access to a *0$

*erver database+version H.2 or later,. • OLEDB Pro>29*r: 4rovides access to any data source that has an #$)>@ driver. This includes *0$ *erver databases prior to version H.2. • Or/,7* Pro>29*r: 4rovides optimi'ed access to an #racle database+version Ii or later,. • ODBC Pro>29*r: 4rovides access to any data source that has an #>@& driver. !.RDBMS CONCEPTS 1. DATA ABSTRACTION 3 major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. However in order for the system to be usable, data must be retrieved efficiently. The efficiency lead to the design of comple! data structure for the representation of data in the database. &ertain comple!ity must be hidden from the database system users. This accomplished by defining several levels of abstraction at which the database may be viewed. 2. CLASSI$ICATION O$ DATABASE There are ( types of database approaches given below, /. %2*r/r,52,/7 D/-/9> They are represented byM • • • ne!t. $);)$-2 M *=*T)/ 54.T?#.T4.T $);)$-DM*.@*=*T)/ $);)$ >3T39$#W 9.5&T #53$ $);)$-1 M 9 $) $);)$ >)T3 $ >3T3 9$#W.

The input and output data shown should be consistent from one level to the

LEVEL-A:

SYSTEM INPUT?OUTPUT LEVEL

3 level-2 >9> describes the system-wide boundaries, dealing inputs to and outputs from the system and major processes. This diagram is similar to the combined user-level conte!t diagram. LEVEL-1: SUBSYSTEM LEVEL DATA $LOW

3 level-D >9> describes the ne!t level of details within the system, detailing the data flows between subsystems, which makeup the whole.

LEVEL-2:

$ILE LEVEL DETAIL DATA $LOW

3ll the projects are feasible given unlimited resources and infinite time. t is both necessary and prudent to evaluate the feasibility of the project at the earliest possible time. 9easibility and the risk analysis are pertained in many ways. f project risk is great.

FIRST LEVEL DTAFLOW DIAGRAM

$an# %branches registration

Customers registration
Truck Details

Accounts holder

ban#ing

Empl

Transaction type er regis
Admin information Module

Accounts & types registrati on

209 L*>*7 D$D)

D$D $or A9620

A9620 M/)-*r

A9620 M/)-*r

A9620 M/)-*r

I0)*rA9620 V*r2f8 D/-/ 3.1

C5*,1 for E6(7o8** V*r2f8 D/-/ 3.1

Check for User Account

V*r2f8 D/-/ 3.1

C5*,1 for S,5*6* ) Insert

A9620 M/)-*r

DFD For Account Holder

&ser 'aster Page &ser 'aster

,hec# for the &ser Account (older )erify Data 2.1 Profile )erify Data

2.2
,hec# for the &ser Account Details

-nsert

)erify Data

*.+ &ser 'aster

2. Unified Modeling L ngu ge Di gr !" #UML$% • The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules. • A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows. U"er Model Vie& i. ii. This view represents the system from the users perspective. The analysis representation describes a usage scenario from the end users perspective. Structur l !odel 'ie& ? !n this model the data and functionality are arrived from inside the system. ? This model view models the static structures.

(e) 'ior l Model Vie& ? !t represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.

I!*le!ent tion Model Vie&
?

!n this the structural and behavioral as parts of the system are represented as they are to be built.

En'iron!ent l Model Vie& !n this the structural and behavioral aspects of the environment in which the system is to be implemented are represented. UML is specifically constructed through two different domains they are
?

UML Analysis modeling, which focuses on the user model and structural model views of the system"

?

UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model vie

Bank Administrators: These are the actors that authori'e and authenticate the
systems e!istence. They take care of the entire system internal activities. They are highly authori'ed to standardi'e the transactional states of the information master data.

Login

Bank &branches registration Customers registration

Accounts & types registration

?
B/01 A96202)-r/-or)

Service type registration

Transaction type registration

Employees registration

A,,o'0- 5o79*r) or ,')-o6*r): There are the actors who statistically work upon the system with respect to the e!pected services what they need to avail. They are mostly restricted on to such areas where -uery standardi'ation has the highest priority.

Login information

ie! customer information View account types

?
Account "older Register for new password View service types

Execute fund transfer

Request cheque oo!

Elaborated #iagrams$ %an& Administrators .ogin screen nter login name Authenticate login name nter password Authenticate password

0ew ban#s registration

,ollect the ban#s data

Authenticate uni"ueness

Register its branches

nable respecti/e pri/ileges Store

?

0ew customer registration

,ollect the customer data

Authenticate uni"ueness

Authori1e % authenticate relational fields

0ew accounts % type registration

,ollect the accounts data

Authenticate uni"ueness

Store

0ew ser/ice type registration

,ollect the re"uired data for ser/ices

Authenticate uni"ueness

Store

0ew transaction type registration

,ollect the re"uired data

Authenticate uni"ueness

Store

0ew employee registration

,ollect the re"uired information

Authenticate uni"ueness

Store

Account 'older nter login name Authenticate login name nter password Authenticate password

Re"uest for customer nter the customer-D inform

nable respecti/e pri/ileges

Re"uest for account type

nter the specific t nter the old pa p nter new password

?
Re"uest for new Re"uest for ser/ice ty

nter the specific type

Re"uest for find tr

nter source ac

nter destination ac

Account to transfer

Re"uest for c

Raise chec# boo# re"ues

)alidate balance

$ Se+uence Di gr !" Ad!ini"tr tor Login Se+uence

Login screen #nter log name

Administrator login master alidate

Administrator Admin Master login master

alidate &ass!ord $% Check for re'uired (ri)ileges $% Authenticate *he id

Log name $%

#nable the s+stem !ith (ri)ileged access

.

2$ Se+uence Di gr !" Account Holder Login Se+uence

Login screen #nter log name

*ransaction *ransaction login *ransaction login login master master master alidate

alidate &ass!ord $% Check for re'uired (ri)ileges $% Authenticate
,tore the information

Log name $%

*he id

Admin
$o "ame #hone no $o% Address

New Employee Registrations

Admin 0ame

$ranch and mployee details
mployee details

$ranch Details ,ustomer Details &ead 'ffice $etails Transaction details

Service type details

Account details:
$o "ame #hone no $o% Address

New Account Registrations

Account 0ame

,ostumer details

,he"ue details

Account details Change #asswords Transfer Details

-ata Base:

,creens:

Login (age:

A9620:

%o6*:

C5/03* P/))Bor9:

D*)230/-2o0 R*32)-r/-2o0):

%*/9 Off2,* R*32)-r/-2o0):

Br/0,5 Off2,* D*-/27):

E6(7o8** D*-/27):

S*r>2,* R*32)-r/-2o0):

A,,o'0- T8(* R*32)-r/-2o0):

Tr/0)/,-2o0 T8(* 9*-/27):

C')-o6*r R*32)-r/-2o0):

C')-o6*r A,,o'0- R*32)-r/-2o0):

C')-o6*r Tr/0)/,-2o0 D*-/27):

C5*;'*
 

Attachments

Back
Top