ABSTRACT

The project is entitled as AUTOMATED SYSTEM FOR JEWELERY SHOP is

a web-based project developed for the purpose of surfing the various available jewel designs.
The end-users are permitted to select the interested designs and can purchase. This project has
been designed with modules consisting of several user-friendly interfaces to surf through
various designs.

This project consists of several modules such as registration, collections,

billing and so on. The user interface is designed using VB.NET with VB as front end and
ODBC connect with MS ACCESS as backend.

The project is user friendly that is, it will help the customer in online shopping
for the purchase of solid jewels from Automated System for Jewellery System purchasing
through online . Basically online purchases is based on time consuming to the customer for
shopping of jewels and search for designs which is available in the web and it is easy for the
customer to purchase who have little knowledge of browsing.

PROBLEM DEFINITION
Automated System for Jewellery Shop is aimed to provide an excellent Management
of resource. The main goal of this project is to increase the efficiency and decrease the manual
entries. It allows the customers to know the status of their resume/application instantly.
This Project helps in saving time, human power and any one can know information
about the jobs. This system will help to reduce the mistakes and also allows any future
updation.

PROBLEM DOMAIN

The activities are to be done to do this system is to analyze the system and to
known about the existing and proposed systems. System models are used to gain

precision and to avoid the ambiguities often found in the natural languages system
description modeling technique used in system analyze is avoids ambiguity by using
precise modeling constructors and process description. It describes the requirements of
the system. This includes finding how the system works and what is does. It also
includes systems problems and what the end-users require of any new or change
system.

2. SYSTEM ANALYSIS
A series of discussion was held among the authorities concerned with the existing
system. Periodic reviews with duty offers were held to monitor the progress, give proper
guidance and direction whenever necessary.

1. Existing System
The existing system carried out manually.
Lot of registers and paper files are maintained to store the information.
Due to lot of paper work, retrieval of information is very difficult.
This process is very time consuming and monotonous which leads to human errors.
Due to paper work storage overheads increases.

2. Proposed System
ASP.Net with VB .Net (Access) with operating system windows XP is used on proposed
system. We convert the existing system into computerized system as accurate and the data
can be stored sequentially. The time consuming is low and processing is speedily.
Proper updating modifications can be easily done by issuing the proposed system.
Reports in Automated System for Jewellery Shop can be verified easily whenever
necessary computerized reports are better than manually prepared reports. Using the menuselected information can be selected easily.

Main Features of the Proposed System

Data accuracy can be achieved by using proper validations and error detection
mechanisms.
Speed processing and easy retrieval of data.
Proper and regular updating of various files.
Complex document can be generated easily and quickly.
A variety of useful reports can be generated

3. REQUIREMENT ANALYSIS
Requirement Analysis is done in order to understand the problem the software system is
to solve. The problem could be automating an existing manual process, developing a new
automated system, or a combination of the two. For large systems that have many features,
and that need to perform may different tasks, understanding the requirement of the system is
a major task. The emphasis in requirements analysis is on identifying what is needed from the
system, not how the system will achieve its goals.

3.1 HARDWARE & SOFTWARE SPECIFICATION

(a)Hardware:
The configuration of the system on which the package is developed is as follows:
(1) Processor

866 MHz Pentium III or higher.

(2) Monitor

VGA or SVGA Color.

(3) Hard disk

80 GB

(4) Ram

512 MB

(5) Key Board

104 Keys

(6) Mouse

Any

(7) Printer

Any

(b)Software:
(1) Operating system

(2) Front End Tool

: ASP.Net with VB.Net

(3) Back End Tool

Windows XP.
SQL Server 2005

3.2. Feasibility Study

The feasibility study is necessary to determine whether the proposed system feasible
considering the technical, operational and economical factors. By having a detailed feasible
study the Maintenance will have a clear-cut view of the proposed system with the benefits
and drawbacks.
All projects are feasible given unlimited resources and infinite time! Unfortunately,
the development of computer-based system or product is more likely plagued by a scarcity of
resources and difficult delivery dates. It is both necessary and prudent to evaluate the
feasibility of a project at the earliest possible time.

3.2.1. Technical Feasibility:

The project Automated System for Jewellery Shop is technically feasibility
because of the below mentioned feature. The project was developed in MS-Access 2007 and
ASP.Net with graphical user interface. It provides the high level of reliability, availability and
compatibility.

3.2.2. Economical Feasibility:

Since the proposed system is an integral part of the decentralized computerization of
total organizational transactions, it is worth to purchase the hardware needed. Thus the
proposed system is economically feasible.

3.3.3. Operation Feasibility

Since the Proposed system is easy to use and there is not any necessary to train the
users to adopt new system. Any user with a little bit knowledge of computers can handle the
system.
There is no resistance from users to the proposed system.
The proposed system provides better service to the employee and maintenance.
The proposed system reduces the work efforts.

Conclusion of Feasibility Study

The proposed system is economically, technically, operationally feasible. So the
proposed system is accepted.

3.3 Development Methodology

Systems Development Life cycle (SDLC) or sometimes just (SLC) is defined by the
U.S. Department of Justice as software development process, although it it also a distinct
process independent of software or to their information technology considerations.
It is used by a systems analyst to develop an information system, including
requirements, validation, training, and user ownership through investigation, analysis, design,
implementation and maintenance. SDLC is also known as information systems development
or application development.
An SDLC should result in a high quality system that meets or exceeds customer
expectations, within time and cost estimates, works effectively and efficiently in the current
and planned information technology infrastructure, and is cheap to maintain and costeffective to enhance.
SDLC is a systematic approach to problem solving and is composed of several phases,
each comprising multiple steps:
The software concept-identifies and defines a need for the new system.
A requirement analysis-analyzes the information needs of the end users

mplementation
Feasibility Study

Feasibility Study
Feasibility Study

Analysis

The architectural design-creates a blueprint for the design with the necessary
specifications for the hardware, software, people and data resources.
Coding and debugging creates and programs the final system
System testing evaluates the systems actual functionality in relation to
expected or intended functionality.

Testing
Analysis
Analysis
Analysis

Design
Design

Development

Implementati

Implementation
Development

on
Maintenance
Testing

Maintenance

or
or

Implementation

or
or

Mainte
nance

Design

Including

Feasibility Study)
Feasibility Study

Evaluation
Design

Developme

Implementation

Evaluation

Implementation

Testing

or

nt
Analysis

Design

Evaluation

Mainte
nance

Requirement
Analysis

System Design

Testing

Maintenance

Implementation

Fig: SDLC LIFE CYCLE

4. SYSTEM DESIGN
Introduction
In developing a design a system, it is advisable for all proposals to be bill from top to
bottom that are most beneficial to the college. The purpose of the preliminary design is to
evaluate project requests. In detailed study, the collection of details to complexity, describe
the system initial and internal issues involved in the design process.
The data that analysts collect during preliminary design through two primary
methods, they are submitting titles and selecting titles. The technical issues usually raised
during the feasibility design like does that necessary technology exists to do what better
analysis to design transition, design of data base interaction design for data communications.
The design of an information system produces the details that state how a system will
meet the requirements identifiers during systems analysis. Systems design process by
identifying reports and other outputs the system will produce the system design, which also
describes the data be entered or input, calculated values or storage of required data into files
or database.
Although the review of a user developed application may not take long, this process
allows a project selection to keep abreast of the applications that are under development and
see how project requests, regardless of their origin, must be evaluated for their operations,
technical and economical factors will influence the preliminary design.
The documents containing the design specifications portray the design in different
ways. The preliminary design is responsible for providing programmers with complete and
clearly outlined software specifications.

Design Process
Software design is an interactive process through which the requirements are
translated into a blue print for constructing the software.
The three characteristics that serve as a guide for the evolution of good design of a
software design are as follows.
The design must implement all of the explicit requirements contained in the analysis
model and it must accommodate all of the implicit requirements of customer.
The design must be readable, understandable guide for those who generates code and
for those who test and subsequently maintain the software.
The design should provide a complete picture of the software addressing the data
functional and behavioral domains from an implementation perspective.
The guidance for the evolutions of the quality of the design representations are:
A design should exhibit a hierarchical organization that makes intelligent
Use of control among elements of software.
A design should be modular that is software should be logically partitioned into
elements that perform specific functions and sub functions.
A design should contain both data and procedural abstractions.
A design should lead modules that exhibit independent functional Characteristics.

Design Principles
Software design is both a process and a model. The design process set of steps that
enable the designer to describe all aspects of the software to be built.
The design model is the equivalent of an architects plan for a house. It begins by
representing the totally of the thing to be built, and slowly refines the thing that guide for
consulting each design.
Basic design principles that enable the software engineer to navigate the design
processes are:
The design process should not suffer from Tunnel Vision
The design should be traceable to the analysis model.

 The design principles should not reinvent the wheel.

The design should minimize the intellectual distance between the software and the
problem as it exists in the real world.
The design should exhibit uniformity and integrity.
The design should be structured be structured to accommodate changes.

4.1 Database Design

Databases are normally implemented by using a package called a Data Base
Maintenance System (DBMS). Each particular DBMS has somewhat unique characteristics,
and so such, general techniques for the design of database are limited. One of the most useful
methods of analyzing the data required by the system for the data dictionary has developed
from research into relational database, particularly the work.
This method of analyzing data is calledNormalization. Unnormalized data are
converted into normalized data by three stages. Each stage has a procedure to follow.

4.1.1. Normalization
Normalization is the process of simplifying the relationship between data elements in
a record. Through this technique, a collection of data in a record structure is replaced by
successive record structures that are simples and more predictable and therefore more
manageable.
Normalization is the formal approach, which examines data and group data item.
Together in a form that is better able to accommodate future changes and to minimize the
impact of that change on that application.
Normalization is carried out of the following reasons:
To structure the Mobile Showroom details data so that any persistent relationship
between entities can be represented.
To permit simple retrieval of Mobile Showroom Maintenance System data in
response to query and report requests.

 To simplify the maintenance of the Mobile Showroom Maintenance System data

through updates insertions and deletions.
To reduce the need to restructure are recognize the data when new application
requirement arise.
This attempt to remove redundant data, avoid data inconsistencies and prevent update
anomalies.
This results in a simpler or more natural data model. A normalized database more
clearly reflects the natural entities and a relationship in the real world. Relational
database theory outlines five normal forms of which three normal forms are used in
this project. The rules and methods of first three normal forms are given below:

First Normal Form

A relation in is 1NF if the intersection of any column and row contains only one
value(no repeating groups).

Methods:
Identify suitable primary key from a pool of un normalized data. Remove any item
that repeats within a single value of this key to another relation bringing within them. The
Primary key to form part of a new composite key in the new relation.

Second Normal Form

A table in 2NF is also in 1NF if the values in every column are functionally dependent
on the complete primary key.

Methods:
For every relation within a single data item making up the primary key, this rule
should always be true. For those with a compound key examines every column and
determines whether its value depends upon the whole of the compound key or just some of
the part it. Remove those that depends only a part of the key to new relation with that part as
the primary key.

Third Normal Form

Columns are not transitively dependent on the primary key. A relation is 2NF is also
in 3NF if the values in every non-key column are not transitively depend on the primary key.

Methods:
Examine every non-key column and question its relationship with every other nonkey column. It for a value for column there is only on value for column B, remove both
columns to a separate relation and mark the question unique as a primary key.
A Mobile Showroom Maintenance System databases tables involved here needs
normalization technique so that it should be flexible to Oracle and store the value in it. So the
third normal form is applied and all the tables are normalized according to that. This system
supports 3 normal forms.

Data Modeling
The information flow defined as a process of the business modeling is refined into set
of data objects that are needed to support the business. The characteristics(called attributes)
of each object are identified and relationships between these objects are defined.

Process Modeling
The data objects defined in the data-modeling phase are transformed to achieve the
information flow necessary to implement a business function. Processing description are
created for addition, modifying, deleting or retrieving a data project.

2.1. Introduction to ASP.Net:

VB.NET is a server side scripting technology that enables scripts (embedded in web
pages) to be executed by an Internet server.

VB.NET is a technology of ASP.NET Microsoft Technology

ASP stands for Active Server Pages

ASP.NET is a program that runs inside IIS

IIS (Internet Information Services) is Microsoft's Internet server

IIS comes as a free component with Windows servers

IIS is also a part of Windows 2000 and XP Professional

ASP.NET combines unprecedented developer productivity with performance, reliability,

and deployment.
Developer Productivity:
VB.NET helps you deliver real world Web applications in record time.

Easy Programming Model. VB.NET makes building real world Web applications
dramatically easier. VB.NET server controls enable an HTML-like style of declarative
programming that let you build great pages with far less code than with classic ASP.
Displaying data, validating user input, and uploading files are all amazingly easy. Best
of all VB.NET pages work in all browsers -- including Netscape, Opera, AOL, and
Internet Explorer.

Flexible Language Options. ASP.NET lets you leverage your current programming
language skills. Unlike classic ASP, which supports only interpreted VBScript and
JScript, ASP.NET now supports more than 25 .NET languages (including built-in
support for VB.NET, C#, and JScript.NET -- no tool required), giving you
unprecedented flexibility in your choice of language.

Great Tool Support. You can harness the full power of ASP.NET using any text editor
-- even Notepad! But Visual Studio 2005 adds the productivity of Visual Basic-style
development to the Web. Now you can visually design ASP.NET Web Forms using
familiar

drag-drop-double-click

techniques,

and

enjoy

full-fledged

code

support including statement completion and color-coding. VS.NET also provides

integrated support for debugging and deploying ASP.NET Web applications.

Rich Class Framework. Application features that used to be hard to implement, or

required a 3rd-party component, can now be added in just a few lines of code using
the .NET Framework. The .NET Framework offers over 4500 classes that encapsulate
rich functionality like XML, data access, file upload, regular expressions, image
generation, performance monitoring and logging, transactions, message queuing,
SMTP mail, and much more!

Improved Performance and Scalability:

VB.NET lets you use serve more users with the same hardware.

Compiled execution. ASP.NET is much faster than classic ASP, while preserving the
"just hit save" update model of ASP. However, no explicit compile step is required!
VB.NET will automatically detect any changes, dynamically compile the files if
needed, and store the compiled results to reuse for subsequent requests. Dynamic
compilation ensures that your application is always up to date, and compiled execution
makes it fast. Most applications migrated from classic ASP see a 3x to 5x increase in
pages served.

Rich output caching VB.NET output caching can dramatically improve the
performance and scalability of your application. When output caching is enabled on a
page, ASP.NET executes the page just once, and saves the result in memory in addition
to sending it to the user. When another user requests the same page, VB.NET serves
the cached result from memory without re-executing the page. Output caching is
configurable, and can be used to cache individual regions or an entire page. Output
caching can dramatically improve the performance of data-driven pages by eliminating
the need to query the database on every request.

Web-Farm Session State. VB.NET session state lets you share session data userspecific state values across all machines in your Web farm. Now a user can hit
different servers in the web farm over multiple requests and still have full access to her
session. And since business components created with the .NET Framework are freethreaded, you no longer need to worry about thread affinity.

Microsoft .NET Outperforms J2EE. In a head-to-head comparison of performance and

scalability between Sun's Java Pet Store J2EE blueprint application and the ASP.NET
implementation, Microsoft .NET significantly outperformed J2EE. The bottom line:
the ASP.NET implementation required only 1/4th as many lines of code, was 28x faster
(that's 2700%), and supported 7.6x as many concurrent users as J2EE, with only 1/6 th
as much processor utilization.

Enhanced Reliability:
VB .NET ensures that your application is always available to your users.

Memory Leak, DeadLock and Crash Protection. ASP.NET automatically detects and
recovers from errors like deadlocks and memory leaks to ensure your application is
always

available

to

your

users.

For example, say that your application has a small memory leak, and that after a week
the leak has tied up a significant percentage of your server's virtual memory.
ASP.NET will detect this condition, automatically start up another copy of the
ASP.NET worker process, and direct all new requests to the new process. Once the
old process has finished processing its pending requests, it is gracefully disposed and
the leaked memory is released. Automatically, without administrator intervention or
any interruption of service, ASP.NET has recovered from the error.

Easy Deployment:

VB.NET takes the pain out of deploying server applications.

"No touch" application deployment. VB.NET dramatically simplifies installation of

your application. With VB.NET you can deploy an entire application as easily as an
HTML page: just copy it to the server. No need to run regsvr32 to register any
components, and configuration settings are stored in an XML file within the
application.

Dynamic update of running application. VB.NET now lets you update compiled
components without restarting the web server. In the past with classic COM
components, the developer would have to restart the web server each time he deployed
an update. With ASP.NET, you simply copy the component over the existing DLL -ASP.NET will automatically detect the change and start using the new code.

Easy Migration Path. You don't have to migrate your existing applications to start
using ASP.NET. VB.NET runs on IIS side-by-side with classic ASP on Windows 2000
and Windows XP platforms. Your existing ASP applications continue to be processed
by ASP.DLL, while new ASP.NET pages are processed by the new ASP.NET engine.
You can migrate application by application, or single pages. And ASP.NET even lets
you continue to use your existing classic COM business components.

2.2. Introduction MS-Access:

MS Access:
Microsoft Access is a fully featured database Management system that lets us
collect, Organize, find, display and print information about and business life. The amount
and variety of information can deal with is staggering.
Feature:
Access comes with wizards and variety of predefined data base elements that
lets us keep track of the following common features:
Asset Tracking
Book Collection
Event Management
Expenses
Household Inventories
Ledgers
Memberships
Picture Libraries
Recipes
Resource scheduling
Service Call Management
Time & Billing Word outs.
Database:
A database is simply a collection of useful data. The database includes objects such
as tables, queries, forms and more.

System Design
4.1. Data Flow Diagram:
Basic DFD Symbols data flow is a route, which enables packets of data to travel from the
point to another. Data may flow from a source to a processor and from a data store.
It is used to store the data in
that database.

The flow is depicted by an arrow

line, with the arrow head pointing
in the direction flow.

A process is represented by bubbles. A

process
where

represents
incoming

transformation

data

flows

are

changed into outgoing data flows. They

must have clear informative names.

A rectangle represents source or sink,

is a person or part of an organization
which enter or receives information
from the system but is considered to
be outside the context of data flow
model.

Context Level

Login

Customers

Administrator

Level 1:

Registration

Password

Customers

Collection

Credit card

Level 4.1:

Admin Login

Product Add

Item Report

Transaction
Report

Customer
Report

Level 4.1.1

Collections

Bangles

Rings

Bracelets
Nose pins

Watches

Earrings

Necklac
es

4.2. Table Lists

A table is the basic structure in a relational system. In access a table in which
information about a particular subject or subject matter is stored. The structure of a table
consists of rows and columns.
Registrations
Item lists
Transactions
Billing
4.3. Data Dictionary
After carefully understanding the requirements of the client entire data storage
requirements are divided into tables. The below tables are normalized to avoid any anomalies
during the course of the data entry.
Table Name: Registration
Field Name
cid
Cname
Pword
Eid
dob
gender
Mblno
Address
City
State
Country
Pincode
Cname
Ctype
Cno
Cdate
Holder name

Data Type
Varchar(50)
Varchar(50)
Varchar(50)
Varchar(50)
Number(10)
Varchar(50
Number
Varchar(25)
Varchar(25)
Varchar(25)
Varchar(25)
Number(10
Varchar(25)
Varchar(25)
Number(25)
Date
Varchar(25)

Table Name: Item

Field Name
Pid
Pname
Qty
Rate
Weight
Picture
Catg

Data Type
Number(10)
Varchar(50)
Number(10)
Number(10)
Number(20)
Varchar(25)
Varchar(25)

Table Name: Transaction

Field Name
Pid
Pname
Qty
Rate
Weight
cid

Data Type
Number(10)
Varchar(50)
Number(10)
Number(10)
Number(20)
Varchar(25)

Table Name: Billing

Field Name
Pid
Pname
Qty
Rate
Weight
cid

Data Type
Number(10)
Varchar(50)
Number(10)
Number(10)
Number(20)
Varchar(25)

4.4 ARCHITECTURE DESIGN

JEWELLERY SHOP

User

Admin

Registration
Customer
Creditcard Details
Product Items
Transactions
Sales
Reports

Jewel Selection

Bill Reports

4.6 ER-DIAGRAMS

The entity Relationship Diagram(ERD) depicts the relationship between the

data objects. The ERD is the notation that is used to conduct the date
modeling activity the attributes of each data object noted is the ERD can be
described resign a data object descriptions.

The set of primary components that are identified by the ERD are
o Data Object
o Relationships
o Attributes
o Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

Notations:

Represents Entity

Represents Attributes

Represents Primary Key

Represents Relationships

Represents Links

Represents Aggregation

Represents Specialization and Generalization

ER-Diagram

C NAME

CADDR
ESS
ADDRE
SS

CSELECTE
D ITEMS

PID

PRODUC
T PRICE

CID

JEWEL
LARY

CUSTOMER

ADMIN

PRODU
CT
DETAIL
S

SALE
S

SALES DETAILS
PRODUCT

Tran
sacti
ons

PRICE

PID

NO.OF
CUSTOM
ERS

PID

PITEM
NO.OF
PRODUCT
S

STOCK

Total
Price
PID

No. of
Items

PITEM

NOOF
ITEMS

Login

HOME PAGE

REGISTRATION

CREDIT CARD

COLLECTIONS

BILLING

PAYMENT

Admin Side:
Item Add:

Item Report:

Customer Report:

Transaction Report:

SYSTEM TESTING
Testing is the process of exercising or evaluating a system or system component by
manual or automated means to verify that it satisfies specified requirements. Testing is a
process of executing program with the intent of finding errors. A good test case is one that has
highly probability of finding an error. A successful test case is one that detects an as yet
undiscovered error.
Testing involves operation of a system or application under controlled conditions and
evaluating the results. The controlled conditions should include both normal and abnormal
conditions. Testing should d intentionally attempt to make things go wrong to determine if
things happen when they shouldnt or things dont happen when they should.
Testing Objective:
1. Testing is a process of executing a program with the intent of finding an error.
2. A good test case is one that has a high probability of finding an as yet undiscovered error.
3. A successful test is one that uncovers an as yet undercover error
Secondary benefits includes

1. Demonstrates the software functions appear to be working according to specifications.

2. That performance requirements appear to have been met.
3. Data collected during testing provides a good indication of software reliability and some
indication of software quality.

Levels of Testing
In order to uncover the errors present in different phases we have the concept of
levels of testing. The basic levels of testing are as shown below

Client Needs
Acceptance
Testing

System Testing
Requirements
Integration Testing
Design

Code

Unit Testing

7.1 Test case design

To have a comprehensive testing scheme the test must cover all methods or a good
majority of them all the services of your system must be checked by at least one test.
To test a system you must construct some test input cases, and then describe how the output
will look. Next, perform the tests and compare the outcome with the expected outcome the
objectives of testing are:
Testing is the process of executing a program with the intent of finding errors.
A good test case is the one that as a high probability of detecting an as yet
undiscovered error.
A successful test case is the one that detects an as ye undiscovered error. If testing is
conducted successfully it will uncover errors in software, Testing cannot show the
absences of defects are present. It can only show that software defects are present.

7.1.1 White Box Testing

Knowing the internal working of a product, tests can be conducted to ensure that
all gears mesh, that is, that internal operation performs according to specifications and
all internal components have been adequately exercised.
It is predicted on close examinations of procedural detail logical providing test
cases that exercise specific sets of conditions and/or loops tests paths through the
software. Basis path testing is a white box testing technique. The basis path method
enables the test case designer to derive a logical complexity of a procedural design and use
this measure as a guide for defining as basis set of execution paths.
We used white box testing for proper execution of loops, functions in the
advocate assistant system.
7.1.2 Black Box Testing
Black box testing allows to tests that are conducted at the software interface. These
are used to demonstrate the software functions operational that input is properly accepted
and the output is correctly produced, at the same time searching for error.
In this system, we checked by using sample input for setting proper output and this
works and black box testing was used.
7. 2 Testing Strategies
A strategy for software testing must accommodate low level tests that are necessary
to verify that a small source code segment has been correctly implemented as well as high
level tests that validate major system functions against customer requirements. A strategy
must provide guidance for the practitioner.

Different Testing strategies

7.2.1 Unit Testing
Unit testing focuses verification efforts in smallest unit of software design the module.
Using the procedural design description as a guide, important control paths are tested uncover
error with in the boundary of the module. The relative complexity of the tests and uncovered
errors is limited by the constrained scope established for unit testing, the unit test is normally
a white box testing oriented and the step can conducted in parallel for multiple modules.
1. Unit test considerations
2. Unit test procedures
7.2.2 Integration Testing
Integration testing is a systematic technique for constructing the program structure
while conducting tests to uncover errors associated with interfacing. There are two types of
integration testing:
1. Top-Down Integration: Top down integration is an incremental approach to construction
of program structures. Modules are integrated by moving down wards throw the control
hierarchy beginning with the main control module.
2. Bottom-Up Integration: Bottom up integration as its name implies, begins construction
and testing with automatic modules.
3. Regression Testing: In this contest of an integration test strategy, regression testing is the
re execution of some subset of test that have already been conducted to ensure that
changes have not propagate unintended side effects.

7.2.3System Testing
The following testing strategies have to be followed by the programmers during the
development and the coding phase of the project. Develop each unit separately and then
perform Unit Test for proper functioning. During this check whether the unit is properly
functional using some of the following methods.
Condition Testing
Properly exercise the logical conditions in a program module. Avoid Boolean operator
errors, variable error, parenthesis errors, relational operators errors and arithmetic errors as
far as possible.
Data Flow Testing
This test is to be carried out as follows. Select test paths of program according to
locations of definitions and uses of variable in the program. Now, consider the selected flow
one by one and test it to proper functioning.
Loop Testing
Loop testing is to be performed on all types of the loops, nested loops, concatenated
loops and unconditional loops. Simple loops may not have errors but even then they dont
leave them untested. Properly dry run and examine the nested loops, concatenated and
unstructured ones.
Once you complete development of the units, the next step is to integrate these units as
a package. During integration of these units, perform integration testing and regression testing
so that integration of these units may not create any problems. Repeat this entire test as
recursive activity so that there is minimum possibility of error.
These tests are to be carried out by the programmer of the project.
Any engineering product can be tested in one of two ways:
White Box Testing: This testing is also called as glass box testing. In this testing, by
knowing the specified function that a product has been designed to perform test can be
conducted that demonstrates each function is fully operation at the same time searching for
errors in each function. It is a test case design method that uses the control structure of the
procedural design to derive test cases. Basis path testing is a white box testing.

Basis Path Testing:

i.

Flow graph notation

ii.

Cyclomatic Complexity

iii.

Deriving test cases

iv.

Graph matrices

Control Structure Testing:

i.

Condition testing

ii.

Data flow testing

iii.

Loop testing

Black Box Testing: In this testing by knowing the internal operation of a product, tests
can be conducted to ensure that all gears mesh, that is the internal operation performs
according to specification and all internal components have been adequately exercised. It
fundamentally focuses on the functional requirements of the software.
The steps involved in black box test case design are:
i.

Graph based testing methods

ii.

Equivalence partitioning

iii.

Boundary value analysis

iv.

Comparison testing

7.2.4 Validation Testing

At the culmination of integration testing, software is completely assembled as a
package; interfacing errors have been uncovered and corrected, and a final series of software
tests validation testing may begin. Validation can be fined in many ways, but a simple
definition is that validation succeeds when software functions in a manner that can be
reasonably expected by the customer.
Reasonable expectation is defined in the software requirement specification a
document that describes all user-visible attributes of the software. The specification contains a
section titled Validation Criteria. Information contained in that section forms the basis for a
validation testing approach.
7.2.5 ALPHA AND BETA TESTING

It is virtually impossible for a software developer to foresee how the customer will
really use a program. Instructions for use may be misinterpreted; strange combination of data
may be regularly used; and output that seemed clear to the tester may be unintelligible to a
user in the field.
When custom software is built for one customer, a series of acceptance tests are
conducted to enable the customer to validate all requirements. Conducted by the end user
rather than the system developer, an acceptance test can range from an informal test drive to
a planned and systematically executed series of tests.

8. SYSTEM IMPLEMENTATION
Implementation is the process of having systems personnel check out and put new equipment
into use, train users, install the new application depending on the size of the organization that
will be involved in using the application and the risk associated with its use, systems
developers may choose to test the operation in only one area of the firm, say in one
department or with only one or two persons. Sometimes they will run the old and new systems
together to compare the results. In still other situation, developers will stop using the old
system one-day and begin using the new one the next.
Once installed, applications are often used for many years. However, both the
organization and the users will change, and the environment will be different over weeks and
months. Therefore, the application will undoubtedly have to be maintained; modifications and
changes will be made to the software, files, or procedures to meet emerging user
requirements. Since organization systems and the business environment undergo continual
change, the information systems should keep pace. In this sense, implementation is ongoing
process.
Evaluation of the system is performed to identify its strengths and weakness. The
actual evaluation can occur along any of the following dimensions.
Operational Evaluation: assessment of the manner in which the system functions,
including ease of use, response time, suitability of information formats, overall reliability, and
level of utilization.
Organization Impact: Identification and measurement of benefits to the organization
in such areas as financial concerns operational efficiency, and competitive impact. Includes
impact on internal and external information flows.
User Manager Assessment: Evaluation of the attitudes of senior and user mangers
within the organization, as well as end-users.
Development Performance: Evaluation of the development process in accordance
with such yardsticks as overall development time and effort, conformance to budgets and
standards, and other project management criteria. Includes assessment of development
methods and tools.

Overview of ASP.NET with VB .Net

The purpose of this tutorial is to provide you with a brief introduction to ASP.NET
MVC views, view data, and HTML Helpers. By the end of this tutorial, you should
understand how to create new views, pass data from a controller to a view, and use HTML
Helpers to generate content in a view.
Understanding Views
For ASP.NET or Active Server Pages, ASP.NET MVC does not include anything that
directly corresponds to a page. In an ASP.NET MVC application, there is not a page on disk
that corresponds to the path in the URL that you type into the address bar of your browser.
The closest thing to a page in an ASP.NET MVC application is something called a view.
ASP.NET MVC application, incoming browser requests are mapped to controller
actions. A controller action might return a view. However, a controller action might perform
some other type of action such as redirecting you to another controller action.
Listing 1 contains a simple controller named the HomeController. The HomeController
exposes two controller actions named Index() and Details().
Listing 1 HomeController.cs
using System.Web.Mvc;
namespace MvcApplication1.Controllers
{
[HandleError]
public class HomeController : Controller
{
public ActionResult Index()
{
return View();
}
public ActionResult Details()
{
return RedirectToAction("Index");
}
}
}

You can invoke the first action, the Index() action, by typing the following URL into your
browser address bar:
/Home/Index
You can invoke the second action, the Details() action, by typing this address into your
browser:
/Home/Details
The Index() action returns a view. Most actions that you create will return views. However, an
action can return other types of action results. For example, the Details() action returns a
RedirectToActionResult that redirects incoming request to the Index() action.
The Index() action contains the following single line of code:
View();
This line of code returns a view that must be located at the following path on your web server:
\Views\Home\Index.aspx
The path to the view is inferred from the name of the controller and the name of the controller
action.
If you prefer, you can be explicit about the view. The following line of code returns a view
named Fred:
View(Fred);
When this line of code is executed, a view is returned from the following path:
\Views\Home\Fred.aspx
If you plan to create unit tests for your ASP.NET MVC application then it is a good idea to be
explicit about view names. That way, you can create a unit test to verify that the expected
view was returned by a controller action.
Adding Content to a View
A view is a standard (X)HTML document that can contain scripts. You use scripts to
add dynamic content to a view.
For example, the view in Listing 2 displays the current date and time.
Listing 2 \Views\Home\Index.aspx
<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage" %>

<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

1.0

Transitional//EN"

<html xmlns="http://www.w3.org/1999/xhtml" >

<head id="Head1" runat="server">
<title>Index</title>
</head>
<body>
<div>
The current date and time is
<% Response.Write(DateTime.Now);%>
</div>
</body>
</html>
Notice that the body of the HTML page in Listing 2 contains the following script:
<% Response.Write(DateTime.Now);%>
You use the script delimiters <% and %> to mark the beginning and end of a script. This script
is written in C#. It displays the current date and time by calling the Response.Write() method
to render content to the browser. The script delimiters <% and %> can be used to execute one
or more statements.
Since you call Response.Write() so often, Microsoft provides you with a shortcut for calling
the Response.Write() method. The view in Listing 3 uses the delimiters <%= and %> as a
shortcut for calling Response.Write().
Listing 3 Views\Home\Index2.aspx
<%@ Page Language="C#" Inherits="System.Web.Mvc.ViewPage" %>
<!DOCTYPE
html
PUBLIC
"-//W3C//DTD
XHTML
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head id="Head1" runat="server">
<title>Index</title>
</head>
<body>
<div>

1.0

Transitional//EN"

The current date and time is

<%=DateTime.Now %>
</div>
</body>
</html>
You can use any .NET language to generate dynamic content in a view. Normally, youll use
either Visual Basic .NET or C# to write your controllers and views.
Using HTML Helpers to Generate View Content
To make it easier to add content to a view, you can take advantage of something called
an HTML Helper. An HTML Helper, typically, is a method that generates a string. You can use
HTML Helpers to generate standard HTML elements such as textboxes, links, dropdown lists,
and list boxes.
For example, the view in Listing 4 takes advantage of three HTML Helpers -- the
BeginForm(), the TextBox() and Password() helpers -- to generate a Login form (see Figure
1).
Using View Data to Pass Data to a View
You use view data to pass data from a controller to a view. Think of view data like a
package that you send through the mail. All data passed from a controller to a view must be
sent using this package. For example, the controller in Listing 6 adds a message to view data.
Summary
This tutorial provided a brief introduction to ASP.NET MVC views, view data, and
HTML Helpers. In the first section, you learned how to add new views to your project. You
learned that you must add a view to the right folder in order to call it from a particular
controller. Next, we discussed the topic of HTML Helpers. You learned how HTML Helpers
enable you to easily generate standard HTML content. Finally, you learned how to take
advantage of view data to pass data from a controller to a view.
ASP.NET MVC Overview (VB.Net)

The Model-View-Controller (MVC) architectural pattern separates an application into three

main components: the model, the view, and the controller. The ASP.NET MVC framework
provides an alternative to the ASP.NET Web Forms pattern for creating MVC-based Web
applications. The ASP.NET MVC framework is a lightweight, highly testable presentation
framework that (as with Web Forms-based applications) is integrated with existing ASP.NET
features, such as master pages and membership-based authentication. The MVC framework is
defined in the System.Web.Mvc namespace and is a fundamental, supported part of the
System.Web

namespace.

MVC is a standard design pattern that many developers are familiar with. Some types of Web
applications will benefit from the MVC framework. Others will continue to use the traditional
ASP.NET application pattern that is based on Web Forms and postbacks. Other types of Web
applications will combine the two approaches; neither approach excludes the other.
The MVC framework includes the following components:

Figure 01: Invoking a controller action that expects a parameter value

Models. Model objects are the parts of the application that implement the logic for the
application's data domain. Often, model objects retrieve and store model state in a
database. For example, a Product object might retrieve information from a database,
operate on it, and then write updated information back to a Products table in SQL
Server.

In small applications, the model is often a conceptual separation instead of a physical one. For
example, if the application only reads a data set and sends it to the view, the application does
not have a physical model layer and associated classes. In that case, the data set takes on the
role of a model object.

Views. Views are the components that display the application's user interface (UI).
Typically, this UI is created from the model data. An example would be an edit view of
a Products table that displays text boxes, drop-down lists, and check boxes based on
the current state of a Products object.

Controllers. Controllers are the components that handle user interaction, work with
the model, and ultimately select a view to render that displays UI. In an MVC
application, the view only displays information; the controller handles and responds to
user input and interaction. For example, the controller handles query-string values, and
passes these values to the model, which in turn queries the database by using the
values.

The MVC pattern helps you create applications that separate the different aspects of the
application (input logic, business logic, and UI logic), while providing a loose coupling
between these elements. The pattern specifies where each kind of logic should be located in
the application. The UI logic belongs in the view. Input logic belongs in the controller.
Business logic belongs in the model. This separation helps you manage complexity when you
build an application, because it enables you to focus on one aspect of the implementation at a
time. For example, you can focus on the view without depending on the business logic.
In addition to managing complexity, the MVC pattern makes it easier to test applications than
it is to test a Web Forms-based ASP.NET Web application. For example, in a Web Formsbased ASP.NET Web application, a single class is used both to display output and to respond
to user input. Writing automated tests for Web Forms-based ASP.NET applications can be
complex, because to test an individual page, you must instantiate the page class, all its child
controls, and additional dependent classes in the application. Because so many classes are
instantiated to run the page, it can be hard to write tests that focus exclusively on individual
parts of the application. Tests for Web Forms-based ASP.NET applications can therefore be
more difficult to implement than tests in an MVC application. Moreover, tests in a Web
Forms-based ASP.NET application require a Web server. The MVC framework decouples the
components and makes heavy use of interfaces, which makes it possible to test individual
components

in

isolation

from

the

rest

of

the

framework.

The loose coupling between the three main components of an MVC application also promotes
parallel development. For instance, one developer can work on the view, a second developer
can work on the controller logic, and a third developer can focus on the business logic in the
model.
Deciding When to Create an MVC Application
You must consider carefully whether to implement a Web application by using either the
ASP.NET MVC framework or the ASP.NET Web Forms model. The MVC framework does
not replace the Web Forms model; you can use either framework for Web applications. (If you
have existing Web Forms-based applications, these continue to work exactly as they always
have.)
Before you decide to use the MVC framework or the Web Forms model for a specific Web
site, weigh the advantages of each approach.
Advantages of an MVC-Based Web Application
The ASP.NET MVC framework offers the following advantages:

It makes it easier to manage complexity by dividing an application into the model, the
view, and the controller.

It does not use view state or server-based forms. This makes the MVC framework
ideal for developers who want full control over the behavior of an application.

It uses a Front Controller pattern that processes Web application requests through a
single controller. This enables you to design an application that supports a rich routing
infrastructure. For more information on the MSDN Web site.

It provides better support for test-driven development (TDD).

It works well for Web applications that are supported by large teams of developers and
Web designers who need a high degree of control over the application behavior.

Advantages of a Web Forms-Based Web Application

The Web Forms-based framework offers the following advantages:

It supports an event model that preserves state over HTTP, which benefits line-ofbusiness Web application development. The Web Forms-based application provides
dozens of events that are supported in hundreds of server controls.

It uses a Page Controller pattern that adds functionality to individual pages. For more
information on the MSDN Web site.

It uses view state or server-based forms, which can make managing state information
easier.

It works well for small teams of Web developers and designers who want to take
advantage of the large number of components available for rapid application
development.

In general, it is less complex for application development, because the components

(the Page class, controls, and so on) are tightly integrated and usually require less code
than the MVC model.

ASP.NET: Accessing Data with SqlServer

Introduction:
When working with classic asp we had ADO, object model for communication with the
database. Microsoft.NET has introduced ADO.NET components that lets the developer
communicate with the database more efficiently and easily. In this article we will see how we
can make use of the ADO.NET classes to perform different operations on the database.
ADO. NET Classes:
ADO .NET classes are put in the System.data namespace. You can access the classes using the
following
code:
using

System.Data.SqlClient;

using

System.Data.Odbc;

using

System.Data.OleDb;

using

System.Data.Oracle;

Different

classes

are

used

for

different

purpose.

System.Data.SqlClient: This class is used to communicate with the Sql Server database. The
database
can
be
version
7.0
or
version
2005.
System.Data.SqlClient: This class is used to perform operations on the MySQL databases.
System.Data.OleDb: This class is used to perform operations on the Access Database.
System.Data.Oracle: This class is used to perform operations on the Oracle database.
In this article we will focus on the Sql Server 2000 database and hence we will be using
System.Data.SqlClient namespace to perform different operations on the Sql Server 2000
Database.
Making

the

Database

Connection

Let's see how we can make a database connection. There are several ways of making a
database connection. You can simple drag and drop the database connection on the asp.net

web form and the connection will be made. Let's see how we can do that:
Open you Visual Studio.NET and start a new asp.net web application. In the toolbox you will
see a tab called data. Click on the tab and it will dropdown showing various ADO objects.
Drag and Drop the SqlConnection object on the screen. As soon as you drop the connection
object

you

will

see

it

at

the

bottom

of

the

screen.

Right click on the connection object and select properties. In the properties you can see the
property named "ConnectionString". When you click on it will take you to a wizard where
you can select your database. In this article I will be using Northwind database which can be
found

in

every

Sql

Server

2005

database.

Once you select the database, test your connection by clicking on the Test connection button.
If the connection is correct a message box will pop saying that the connection has been tested
and connection is right.
Problems

using

this

approach

of

making

the

connection

String:

As you have just seen that we just dragged and dropped the connection string on the screen
and the new connection to the database was made in seconds. This approach should never be
used since if in the future you change your connection string you will have to change every
where in the application.
Using Web.config to store the connection String:
As you can see above that you can make your connection string with just one line. Take a look
at the "key" represents the keyword that we will use to refer to it in our application.
"value"

contains

the

connection

string.

"database" contains the name of the database which in this case is Northwind.
I have to point out that saving the connection string like this is not secure. Usually you store
the connection string after encrypting it. I will not perform encryption in this article and keep
the article simple enough.

Accessing database from webpage:

Now you have added the connection string in the web.config file. Let's see some code that we
can use to access the database. We want to load some data from the database when the page is
loaded for the first time.

private

void

Page_Load(object

sender,

System.EventArgs

e)

{
if(!Page.IsPostBack)
{
string connectionString = (string) ConfigurationSettings.AppSettings["ConnectionString"]
SqlConnection

myConnection

new

SqlConnection(connectionString)

SqlDataAdapter ad = new SqlDataAdapter("SELECT * FROM Categories",myConnection)

DataSet

ds

new

DataSet()

ad.Fill(ds,"Categories")
myDataGrid.DataSource
myDataGrid.DataBind()
}
}

ds

First, we check that if it's not a postback we load data. For this example to work you need to
add the namespace:
using System.Configuration;
Let's

see

what

is

going

on

here:

1) string connectionString receives the string from the web.config file which is referred by the
"ConnectionString"

key

we

set

in

the

web.config

file.

2) We make the object of the SqlConnection class which deals with SQL Server databases.
3) We made the data adapter object. Data adapter is a kind of connection to the database. In
the data adapter object we specify that what we want from the database. In this case we want
all the rows of the Categories table.
NOTE:
Always use stored procedures for accessing the data. Accessing or running Ad-hoc queries are
dangerous

as

they

are

open

for

SQL

Injections.

4) Next we made an instance of the DataSet class. DataSet will contain the result of the
SqlDataAdapter
5)

Later,

we

even
filled

if

the

the

database

dataset

with

connection
the

data

is
using

not

made.

dataadapter.

6) And finally we assigns the datagrid to the dataset and binds it on the screen.
Pretty

simple

right?

Lets see if we can improve the code above:

private

void

Page_Load(object

sender,

System.EventArgs

e)

{
if(!Page.IsPostBack)
{
string connectionString = (string) ConfigurationSettings.AppSettings["ConnectionString"];
SqlConnection

myConnection

SqlDataReader
SqlCommand

new

reader
myCommand

myCommand.CommandType

SqlConnection(connectionString);
=

new

null;

SqlCommand("GetData",myConnection);

CommandType.StoredProcedure;

try
{
myConnection.Open();
reader

myDataGrid.DataSource
myDataGrid.DataBind();
}

myCommand.ExecuteReader();
=

reader;

catch(Exception

ex)

{
//

Catches

and

logs

the

exception

}
finally
{
reader.Close();
myConnection.Close();
}
}
}

In the code above we are using the SqlCommand object and stored procedure. You might have
noted SqlDataReader, if you want to merely iterate through the database rows and select them
its best to use SqlDataReader since its much faster than DataSet

Login page
Imports ADODB
Partial Class _login
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim reg As New ADODB.Recordset
Dim bill As New ADODB.Recordset
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button1.Click
If T1.Text = "administrator" And T2.Text = "admin" Then
Response.Redirect("itemadd.aspx")
Else
cn.Open("nisha")
reg.Open("select * from register where cid='" + T1.Text + "' and pword='" + T2.Text +
"'", cn, 1, 2)
If reg.EOF Then
reg.Close()
cn.Close()
MsgBox("user name or Password wrong", 16, "Password")
T1.Text = ""
T2.Text = ""
T1.Focus()
Else
Session("cid") = T1.Text
Session("cname") = reg.Fields("nam").Value
T1.Text = ""
T2.Text = ""
reg.Close()
bill.Open("select * from billing", cn, 1, 2)
If Not bill.EOF Then
bill.MoveFirst()
While Not bill.EOF
bill.Delete()
bill.MoveNext()
End While
End If
bill.Close()
cn.Close()
Response.Redirect("usermenu.aspx")
End If
End If
End Sub

Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)

Handles Me.Load
End Sub
End Class

Registation Form:
Imports ADODB
Partial Class register
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim reg As New ADODB.Recordset
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button1.Click
cn.Open("nisha")
reg.Open("select * from register where cid='" + cid.Text + "'", cn, 1, 2)
reg.Fields("cid").Value = cid.Text
reg.Fields("nam").Value = nam.Text
Dim nish As Date
nish = DateValue(Trim(D2.Text) + "/" + Trim(D1.Text) + "/" + Trim(D3.Text))
reg.Fields("dob").Value = nish
reg.Fields("mblno").Value = Val(mbl.Text)
reg.Fields("address").Value = adrs.Text
reg.Fields("city").Value = city.Text
reg.Fields("state").Value = state.Text
reg.Fields("country").Value = contry.Text
reg.Fields("pincode").Value = Val(pin.Text)
reg.Update()
MsgBox("Saved ur account", 64, "Registration")
reg.Close()
cn.Close()
Call clear()
End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
contry.Text = "India"
If Not Page.IsPostBack = True Then
cid.Text = Session("cid").ToString
cn.Open("nisha")
reg.Open("select * from register where cid='" + cid.Text + "'", cn, 1, 2)
nam.Text = reg.Fields("nam").Value
Dim nish As Date
nish = IIf(IsDBNull(reg.Fields("dob").Value), Today.Date, reg.Fields("dob").Value)
D1.Text = nish.Day

D2.Text = nish.Month
D3.Text = nish.Year
mbl.Text = IIf(IsDBNull(reg.Fields("mblno").Value), "", reg.Fields("mblno").Value)
adrs.Text = IIf(IsDBNull(reg.Fields("address").Value), "", reg.Fields("address").Value)
city.Text = IIf(IsDBNull(reg.Fields("city").Value), "", reg.Fields("city").Value)
state.Text = IIf(IsDBNull(reg.Fields("state").Value), "", reg.Fields("state").Value)
contry.Text = IIf(IsDBNull(reg.Fields("country").Value), "",
reg.Fields("country").Value)
pin.Text = IIf(IsDBNull(reg.Fields("pincode").Value), "", reg.Fields("pincode").Value)
reg.Close()
cn.Close()
Button1.Text = "Update"
End If
End Sub
Protected Sub clear()
cid.Text = ""
nam.Text = ""
D1.Text = ""
D2.Text = ""
D3.Text = ""
mbl.Text = ""
adrs.Text = ""
city.Text = ""
state.Text = ""
contry.Text = ""
pin.Text = ""
End Sub
Protected Sub R1_Checked(ByVal sender As Object, ByVal e As System.EventArgs)
Handles R1.CheckedChanged
If R1.Checked = True Then
R2.Checked = False
End If
End Sub
Protected Sub R2_Checked(ByVal sender As Object, ByVal e As System.EventArgs)
Handles R2.CheckedChanged
If R2.Checked = True Then
R1.Checked = False
End If
End Sub
End Class
Credit Card Form:
Imports ADODB
Partial Class creadircard
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection

Dim rs As New ADODB.Recordset

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button1.Click
cn.Open("nisha")
rs.Open("select * from register where cid='" + t1.Text + "'and pword='" + T2.Text + "'",
cn, 1, 2)
If rs.EOF Then
rs.Close()
cn.Close()
MsgBox("Your customer ID is wrong")
Else
rs.Fields("cnam").Value = T3.Text
rs.Fields("ctype").Value = D1.Text
rs.Fields("cno").Value = T4.Text
Dim n As Date
n = DateValue(Trim(D3.Text) + "/" + Trim(D2.Text) + "/" + Trim(D4.Text))
rs.Fields("cdate").Value = n
rs.Fields("chnam").Value = T5.Text
rs.Update()
rs.Close()
cn.Close()
MsgBox("Your Credit card Details are saved successfully", 64, "credit card detial")
Call clear()
End If
End Sub
Protected Sub clear()
t1.Text = ""
T2.Text = ""
T3.Text = ""
D1.Text = ""
T4.Text = ""
D3.Text = ""
D2.Text = ""
D4.Text = ""
T5.Text = ""
End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
If Not Page.IsPostBack = True Then
t1.Text = Session("cid").ToString
cn.Open("nisha")
rs.Open("select * from register where cid='" + t1.Text + "'", cn, 1, 2)
T2.Text = IIf(IsDBNull(rs.Fields("cnam").Value), "", rs.Fields("cnam").Value)
D1.Text = IIf(IsDBNull(rs.Fields("ctype").Value), "", rs.Fields("ctype").Value)
T3.Text = IIf(IsDBNull(rs.Fields("cno").Value), "", rs.Fields("cno").Value)
Dim nish As Date
nish = IIf(IsDBNull(rs.Fields("cdate").Value), Today.Date, rs.Fields("cdate").Value)
D1.Text = nish.Day

D2.Text = nish.Month
D3.Text = nish.Year
T4.Text = IIf(IsDBNull(rs.Fields("cno").Value), "", rs.Fields("cno").Value)
T5.Text = IIf(IsDBNull(rs.Fields("chnam").Value), "", rs.Fields("chnam").Value)
cn.Close()
End If
End Sub
End Class
Change Password:
Imports ADODB
Partial Class changepassword
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button1.Click
cn.Open("nisha")
rs.Open("select * from register where cid='" + T1.Text + "' and pword='" + T2.Text + "'",
cn, 1, 2)
If rs.EOF Then
rs.Close()
cn.Close()
MsgBox("Your old password is wrong", 64)
Else
rs.Fields("pword").Value = T3.Text
rs.Update()
rs.Close()
cn.Close()
MsgBox("Your password successfully changed", 64)
End If
End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
T1.Text = Session("cid").ToString
End Sub
Protected Sub Button2_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button2.Click
Response.Redirect("login.aspx")
End Sub
End Class
Collections:

Imports ADODB
Partial Class jewsel
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
End Sub
Protected Sub GridView1_SelectedIndexChanged(ByVal sender As Object, ByVal e As
System.EventArgs) Handles GridView1.SelectedIndexChanged
Dim row As GridViewRow = GridView1.SelectedRow
cn.Open("nisha", "scott", "tiger")
rs.Open("select * from billing", cn, 1, 2)
rs.AddNew()
rs.Fields("pid").Value = row.Cells(1).Text
rs.Fields("pnam").Value = row.Cells(2).Text
rs.Fields("wht").Value = row.Cells(3).Text
rs.Fields("qty").Value = row.Cells(4).Text
rs.Fields("rate").Value = row.Cells(5).Text
rs.Update()
rs.Close()
cn.Close()
End Sub
End Class

Billing:
Imports ADODB
Partial Class trans
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Protected Sub GridView1_SelectedIndexChanged(ByVal sender As Object, ByVal e As
System.EventArgs) Handles GridView1.SelectedIndexChanged
Dim row As GridViewRow = GridView1.SelectedRow
cn.Open("nisha", "scott", "tiger")
Dim raj As Integer
raj = Val(row.Cells(0).Text)
MsgBox(raj)
rs.Open("select * from billing where pid=" & raj, cn, 1, 2)
If Not rs.EOF Then
rs.Delete()
End If
rs.Close()
cn.Close()
Response.Redirect("trans.aspx")
End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button1.Click
Response.Redirect("billing.aspx")
End Sub
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
End Sub
End Class
Conform Billing:
Imports ADODB
Partial Class billing
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim tra As New ADODB.Recordset
Dim sum As Long = 0
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Me.Load
cn.Open("nisha")
rs.Open("select * from billing", cn, 1, 2)
If rs.EOF Then
sum = 0
MsgBox("select Item and click it", 64, "Not Selected")

Else
rs.MoveFirst()
While Not rs.EOF
sum = sum + rs.Fields("rate").Value
rs.MoveNext()
End While
GridView1.ShowFooter = True
GridView1.FooterRow.Cells(1).Text = "Total Amount"
GridView1.FooterRow.Cells(4).Text = sum
rs.Close()
cn.Close()
End If
End Sub
Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)
Handles Button1.Click
cn.Open("nisha")
rs.Open("select * from billing", cn, 1, 2)
tra.Open("select * from transaction", cn, 1, 2)
rs.MoveFirst()
While Not rs.EOF
tra.AddNew()
tra.Fields("pid").Value = rs.Fields("pid").Value
tra.Fields("pnam").Value = rs.Fields("pnam").Value
tra.Fields("wht").Value = rs.Fields("wht").Value
tra.Fields("qty").Value = rs.Fields("qty").Value
tra.Fields("rate").Value = rs.Fields("rate").Value
tra.Fields("cid").Value = Session("cid").ToString
tra.Update()
rs.MoveNext()
End While
tra.Close()
rs.Close()
cn.Close()
MsgBox("Your Purchased Item will be delivered within a week", 64, "Delivery Report")
End Sub
End Class
ADMIN PAGE
Item Add:
Imports ADODB
Partial Class itemadd
Inherits System.Web.UI.Page
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset

Protected Sub Button1_Click(ByVal sender As Object, ByVal e As System.EventArgs)

Handles Button1.Click
cn.Open("nisha")
rs.Open("select * from item", cn, 1, 2)
rs.AddNew()
Dim filename As String
filename = FileUpload1.FileName
FileUpload1.SaveAs(Server.MapPath(".\images\") + filename)
rs.Fields("pname").Value = T2.Text
rs.Fields("qty").Value = Val(T3.Text)
rs.Fields("rate").Value = Val(T4.Text)
rs.Fields("picture").Value = "./images/" + filename
rs.Fields("weight").Value = Val(T5.Text)
rs.Fields("catg").Value = D1.Text
rs.Update()
rs.Close()
cn.Close()
T2.Text = ""
T3.Text = ""
T4.Text = ""
T5.Text = ""
MsgBox("One Item Inserted", 64)
End Sub
End Class

8. Conclusion

The project entitled Rajendra Jewellery has been successfully developed and
implemented. The testing was carried out by dividing the project into different modules. This
project is successful in replacing the existing system and reduces the workload.

BIBLIOGRAPHY
BOOKS:

Professional ASP.Net 1.1

-

Alex Homer, Dave Sussman, Rob Howard, Brain francis, Karli Watson,
Richard Anderson

ASP.Net Developers Guide- Buczek

Microsoft Visual C#.Net Step By Step

- Jhon sharp, Jon Jagger

WEBSITE:
www.google.com