REPORT FOR SUMMER

TRAINING
PROGRAMME CONDUCTED IN
USA TECH

UNDER
Mr. Rajpal Singh
(Vice-President of USA Tech)

REPORT DEVELOPED BY:

VIJAY PATHAK
B.Tech (IVth year)
COMPUTER SCIENCE&
ENGINEERING
NIEC(LUCKNOW)
Roll no.0705610116

1
 ACKNOWLEDGEMENT
First and foremost we would like to express our deep
gratitude to Mr.Rajpal Singh This project was not doable
in the absence of strong guidance of our instructor. His
valuable guidance and many constructive suggestions were
very necessary for the improvement of this project. We are
really indebted to him for kind helps. We are also grateful
to Mr.Rajpal Singh who had provided us infrastructural
and logistical support along with ideas and suggestions to
enhance our project with various features. He had also
provided us an environment that was conducive for out
project.

2
 CERTIFICATE

This Is To Certify That The ONLINE SHOPPING has

Been Developed By VIJAY PATHAKl Of Pre-Final Year
(2009-10) Computer Science & Engineering, Northern
India Engineering College,Lucknow. In The Summer
Training Programme Conducted In The USA Tech
Attended From 21/06/10 To 05/08/10 as a Partial
Fulfillment Of Award To The Degree Of Bachelor Of
Technology In Computer Science & Engineering Of Uttar
Pradesh Technical University ,Lucknow.

Vijay Pathak

B.tech(final year)
(0705610116)

3
 A

Project Report

On

Online Shopping & Management

INDUSTRIAL PROJECT
Session: 2009-10

4
 Index

S No. Title Page No.

1 Introduction

o Overview of the project

o Literature survey
o Objectives & Scope
o Organization of the report

2 Requirement Analysis

o Introduction
o Present Scenario
o Problem Definition
o Proposed system
Requirements specification

o Introduction
o Overall Description
o Product Perspective
3
o Product Functions
o User Characteristics
o Operation Environment
o Constraints

Specific Requirements

o External Interface Requirements

o System Features
o Data Flow Diagrams, Entity Relationship
o Diagrams or UML Diagrams, Whatever
applicable
o Performance Requirements

5
 o Software Quality Attributes
Feasibility Study

o Hardware and Software

4
Specification
o Technical Feasibility
o Economical Feasibility
o Operational Feasibility

5 System Design

o Database Design
o Component Level Design
o User Interface Design
o Data Dictionary
o Reports

6 Technologies Used
7 Coding
8 Testing

o Introduction
o Test Criteria
o Test Cases
9 Implementation

o Installation
o User Manual
10 Cost Estimation of the Project
11 PERT Chart/Network Diagram, Gantt Chart
12 Conclusion and Future work

o Summary
o Future Work
Annexure(if any)
Glossary

6
 Introduction

Overview of the project:

Online shopping is the one of the easiest way of shopping because in today
scenario time is the main factor and with the help of online shopping you can easily shop
24*7.Sometimes information is passed manually between departments. This manual
system will take time to pass the information and sometimes it causes loss of information
also. This causes loss of buyer time also.
Now days the organizations are growing fast and are increasing in size also. So the
organizations shift there business online due to this they can done their business globally
and 7 days in a week.. In the fast growing world the information is needed as quick as
possible. This can be accomplished by passing the information quickly. So we need a
system which is both quick and accurate. This can be achieved by this project.
The following figure depicts an abstract level diagram of the project:

Computer 2 e-shopping
e-shopping

e-shopping
Computer 1 Computer 3

e-shopping e-shopping
Server or
shopping site

Figure1: An abstract level diagram of the online shopping

7
Literature survey

The main aim of this project is sell there product where no requirement of the location. It
is much cheaper than the manual system.
In manual system, communicating with people has been a difficult task. For organizations
with more than hundred or thousands of customers, contact with each customers is
impossible without an efficient system.

Objectives & Scope:

• The main aim of this project is sell there product where no requirement of the location

and 24*7.

• This software provides a user-friendly interface for the user and it reduces the
data redundancy. Centralized information is available which can be accessed by
number of users.
• Improved Processing speed: The inherent speed, with which computers process
information is one reason why organization seeks the development of the system
projects.
• Greater accuracy and consistency: Carrying out computing steps, including
arithmetic, correctly and consistently.
• Better Security: Safeguarding sensitive and important information in form that is
accessible only to authorized person.
• Enhanced Communication: Speeding the flow of information and messages
between remote locations.
• Doing there business effectively and globally with the help of online shopping.

8
Organization of the report:
The report consists of twelve (12) chapters each consisting of subsections. Each chapter
conveys an insight to the project. The first chapter Introduction reveals the basic
idea of the project, its scope, its purpose and overview.
The second chapter Requirement Analysis takes into account the problem, the
present scenario, and the proposed system. The Requirement Analysis is one of the most
important stages of project life cycle.
The third chapter Requirements specification describes the overall description of the
project, its characteristics, operating environment, user characteristics, constraints,
dataflow diagrams, entity relationship diagrams etc.
The fourth chapter Feasibility Study expresses the level with which the project is feasible,
it includes hardware & software feasibility, technical feasibility, economical feasibility,
economic feasibility, operational feasibility.
The next chapter System Design describes tables and database used, components
involved, the user interfaces, data dictionary, reports.
The next chapter Technologies Used gives the description of the technologies used in the
project.
The chapter Coding gives the view of codes and logic being implemented. The Design is
followed by coding in the project life cycle hierarchy.
The next chapter Testing specifies the mode of testing done in the project, test criteria
followed and the test cases prepared.
The following chapter Implementation specifies the installation process, and brief
description of the user manual.
The next chapter Cost Estimation of the Project specifies the cost involved in the project.
The next chapter PERT Chart/Network Diagram, Gantt Chart gives the view if the
project plan, the schedule followed in the project development phase.

9
The last chapter Conclusion and Future work summarizes the work done in the project
and the future enhancement which can be done.

10
 Requirement Analysis
Introduction

The aim of online shopping & management System is to computerize shopping

process for people present geographically. Its basic objectives are to extend their
reach to geographically scattered customers, reducing time in activities, centralized
data handling and paperless shopping with reduced manpower. Main challenges are
effectively sync internal and external operations in such a manner that job can be
finished within time limit.

Present Scenario

Existing system work manually. The existing system has got lot of intricacies within
itself and need lot of human effort and paper works. All above the data need to be
maintained on ledgers and maintaining this is a tedious and risky process.
present system was not transparent much paper work was evolved there was no
interface for public viewing there was not enough time for purchasing or compare
price so buyer not have enough time to best deal. To view a data may need lot of
paper to be searched.

Some of the negative aspects of the existing system are as follows:

1) Action is time consuming. Wherever a need for search arises, the process
evolves search through paper records.
2) So many products in the market so user is much confused.
3) Paper records are easily damaged in course of time. The life time of paper
record is unreliable less that it easily gets spoiled.
4) Manual system needs added man power.
5) Prone to corruption by unauthorized users. Securing of manual system is
not fully guaranteed. Inaccuracy can be expected. Data can get easily
scratched.

Problem Definition

There was bulk amount of data from different institutions each having its
Own data no centralization candidate has limited time period and limited
Options handling of this large data was a major problem faced single view
Was available for everyone. Much paper work was involved. Hence a
Centralization of information was required to reduce paper work and

11
 Simplify operating procedures. Analyst, working closely with the employees and
managers, must study the Counseling process to answer

These key questions:

 What is being done?

 How is it being done?
 How frequent does it occur?
 How great is the volume of decisions?
 How well is the task being performed?
 Does a problem exist?
 If problems exist, how serious is it?
 If a problem exists, what is the underlying cause?

Proposed system

The proposed system is a computerized one. This has greater accuracy and
efficiency. This takes only limited time for calculation.
The proposed system can be used to maintain efficiently the Administrator
Department. In the college employees are large. At that time also the proposed
system is useful and helpful.

The system includes three users.

1) Administrator
2) buyer
3) customer
4) visitors
The buyer gets into the system using user name and a unique password. Each
buyer has his own accessibility permission to accomplish his task flawlessly.
Now visitors has to logon to website and are required to signup after that only
he/she purchase. They will be given a unique user. The procedure of
exercising choices is menu driven. It guides the buyer through appropriate
choices.

12
 Requirements Specification

Introduction:
The aim of online shopping & management System is to computerize shopping
process for people present geographically. Its basic objectives are to extend their
reach to geographically scattered customers, reducing time in activities, centralized
data handling and paperless shopping with reduced manpower. Main challenges are
effectively sync internal and external operations in such a manner that job can be
finished within time limit.

Overall Description:
Online shopping is the one of the easiest way of shopping because in today scenario time
is the main factor and with the help of online shopping you can easily shop
24*7.Sometimes information is passed manually between departments. This manual
system will take time to pass the information and sometimes it causes loss of information
also. This causes loss of buyer time also.
Now days the organizations are growing fast and are increasing in size also. So the
organizations shift there business online due to this they can done their business globally
and 7 days in a week.. In the fast growing world the information is needed as quick as
possible. This can be accomplished by passing the information quickly. So we need a
system which is both quick and accurate. This can be achieved by this project.
The following figure depicts an abstract level diagram of the project.

Product Perspective:
The product perspective can be understood under following sub headings:

Product Functions:
The main aim of this project is sell there product where no requirement of the location and

24*7.

13
 • This software provides a user-friendly interface for the user and it reduces the
data redundancy. Centralized information is available which can be accessed by
number of users.
• Improved Processing speed: The inherent speed, with which computers process
information is one reason why organization seeks the development of the system
projects.
• Greater accuracy and consistency: Carrying out computing steps, including
arithmetic, correctly and consistently.
• Better Security: Safeguarding sensitive and important information in form that is
accessible only to authorized person.
• Enhanced Communication: Speeding the flow of information and messages
between remote locations.
• Doing there business effectively and globally with the help of online shopping.

User Characteristics:
There are following types of users in the Online Shopping & management.
• Administrator: The administrator verifies the user (employee) after he/her
registers. He can also block the feedback & add the requested product. He
specifies the news and event etc.
• Buyer: Buyer are the registered the customers they online shop or purchase
product.
• Customer: Customers are those put there advertisement on the website.
• Visitors: Visitors are online visit the website and see the product

Operation Environment:
Online Shopping & Mnagement application will run on any internet browser supporting
JavaScript for client side checks and validation. Terminals running the internet browser
may or may not be intelligent.

14
Constraints:

Online shopping & management application will run on any internet browser supporting
JavaScript for client side checks and validation. The system is to run under the
WINDOWS operating system. The application will run on a workstation with 512 MB
RAM.

External Interface Requirements

User Interfaces
There are various kind of user in the system .These are Administrator, counseling
controller, Candidate etc .All these interacts with the system.

Hardware Interfaces

CLIENT SIDE

Processor RAM Disk Space

INTERNET Pentium II at 500 MHz 64 MB 1GB
EXPLORER 6.0
FIREFOX 1.5 Pentium II at 500 MHz 64 MB 1GB

SERVER SIDE

Processor RAM Disk Space

INTERNET Pentium IV at 1 GHz 1 GB 1 GB
INFORMATION
SERVICES
SQL SERVER 2005 Pentium IV at 1 GHz 1 GB 1 GB

15
Software Interfaces

Software will depend on the security features provided by the operating system and the
language C#.

Client on Internet
• Web Browser
• Operating System(windows)

Database Server
• SQL Server 2005
• Operating System

Development End
• ASP.NET
• HTML
• Java Script
• SQL Server 2005
• Operating System
• Web Server

Communications Interfaces

The system requires a SMTP server and a web connection with the direct connection to
the internet. It assumed that database connection established.

• Client on Internet will be using HTTP/HTTPS protocol.

• Client on Internet will be using TCP/IP protocol.

System Features
The various features or functional requirements of Intranet Mailing And Chatting are:
• The administrator can verify registrations of the new users.
• The administrator can also block or activate users account.
• The administrator can specify news and events.
• The buyer can purchase product,add product request give there feedback after
successful logging in to the project.
• The user can also send there billing details.

16
ENTITY RELATIONSHIP DIAGRAM

• ERD can express the overall logical structure of a database graphically.

• ERD are simple and clear qualities that may well account in large part for the
widespread use of the ER-Model.

• The basic object that the ER model represents is an entity, which is a “Thing” in
the real world with an independent existence.

• A particular entity will have a value for each of its attributes.

• The attribute values that describe each entity become a major part of the data
stored in the database.

(The E-R Diagram is shown at next page)

17
 catid Discount
catname P_id

Product
Category

Product
id
Produc
Bill
Price t name
can

Purchase
id
Purchase Bill id

Date
Purchase
date
Total

Qty

Sub cat Bill Detail

id
Sub
category
Login id
Sub cat
name
U name
Passwor Login
d

DOB log

Address

User id

User
Password

User name
Bill Payment
no

Card validity
User name

amount
Card type

18
DATA FLOW DIAGRAM (DFD)

• DFD are commonly used during problem analysis.

• A DFD shows the flow of data through a system.

• The DFD aims to capture the transformation that take place within the
System to the input data so that eventually the out put data is produced.

• A DFD does not represent procedural information.

• DFD is a logical design of the flow of information between the modules.

• The DFD shows the interaction of one module with the other module.

There are several level of DFD are used to describe the flow of information

19
 Context Level ‘DFD’

Normal Visitor Normal Visitor

Come To view Get
product list information

Delivered
Purchase Order User / Client
User / Client Online To
Items
shopping &
management
Manage View All
Information information

Administrator
Administrator

‘1st’Level’ DFD

Query Content
User DB

Query
Client Validate-ID Save DB
& The
Valid ID
Password Contents
User ID &
Password
Reject Confirmation

Client

20
 2nd Level DFD

User DB

Validate ID Shopping
Client & Valid Shopping ID Bag
ID &
Password ID Mart Generate
Password
ID
Rejected
Category DB

Select ID and Category View

Items Selected Select ID Category
To Categories Available
Purchas For Items
e
Shopping Bag
ID &
Items
Generate
Pay Slip Client
For ID Tax ID Generate ID &
Items Calculation Overall Slip Payment
Detail Pay Slip Modes

Tax Details
Pay Price DB DB Message To
Delivered
Client
Payment

Accounts
Department
21
 SHOPPING DFD

Category DB
User DB

New Validate View

Client ID & Categories
Password Shopping Available
Valid ID Valid ID
User ID & Mart
Password
Message ID
To
Select
Be Categories
Delivered Payment Select Items ID &
To Category For Items
Range ID &
Purchase
Client Item Selected

Item
DB
Shopping
Bag
New Client

Necessary
information
User DB

New Client
Save
Sign Up Registration
Necessary
Form
Valid ID Information

Optional
Reject
Client Information
Submit
Confirmation Save
Optional User DB
Information

22
Performance Requirements
There are following performance requirements:
• 24x7 availability.
• Better component design to get better performance.
• The PC on which the online shopping & management resides will have its own
safety by controlling the physical access.
• Secure access of confidential data.
• The server on which the online shopping & management resides will have its
own security to prevent unauthorized write/delete access.
• There is no restriction on read access for the legitimate user

Software Quality Attributes

The main attribute is ease of use, while constrained by previous operation. If is being
designed for robustness and is written as a complete package so it can be inserted into
another application.

Reliability
Any existing Web site that relies on the manual duplication of data from
another system is one that can be improved. Most of the business data in the
world today exists in enterprise servers that can be connected to the Web servers
to make this process far more effective. Web application developers should not
spend valuable time worrying about how to maintain sessions within the
application. The Web Application Server should provide these services.

Availability

Because system can be automated process, so it can stay open for 24 hours a day. If the
base is now the entire world, staying open 24 hours a day becomes critical. System will
require to be available 24X7 so UPS support must be on server site for at least 8 hours in
case the power failure.

Security
• Database access permissions for end users read permission only.
• Password protection provided for every user by generating an automated
password.

23
Maintainability
Many early Web implementations consisted of static HTML pages. This becomes very
difficult to manage if the number of pages gets too large. An effective system should be
largely dynamic taking advantage of technology that automates this process rather than
relying on manual processes. Application should serve dynamic user based customized
web pages to its clients from server

24
 Feasibility Study

Depending on the results of the initial investigation the survey is now expanded to a
more detailed feasibility study. “FEASIBILITY STUDY” is a test of system proposal
according to its workability, impact of the organization, ability to meet needs and
effective use of the resources. It focuses on these major questions:

1. What are the user’s demonstrable needs and how does a system meet them?

2. What resources are available for given buyer system?

3. What are the likely impacts of the buyer system on the organization?

4. Whether it is worth to solve the problem?

During feasibility analysis for this project, following primary areas of interest are to
be considered. Investigation and generating ideas about a new system does this. Steps
in feasibility analysis. Eight steps involved in the feasibility analysis are:

• Form a project team and appoint a project leader.

• Prepare system flowcharts.
• Enumerate potential proposed system.
• Define and identify characteristics of proposed system.
• Determine and evaluate performance and cost effective of each proposed
system.
• Weight system performance and cost data.
• Select the best-proposed system.
• Prepare and report final project directive to management.

Hardware and Software Specification

Hardware Requirement

Main Processor Pentium IV

Hard-disk Capacity 8 G.B
RAM 512 MB
Clock Speed 2.8 Hz
Floppy Drive 1.44MB
Keyboard 104 Key
Monitor V.G.A

25
Software Requirement

Operating System Window XP

Backend tool SQL Server 2005
Front-end tool HTML, ASP.NET, JavaScript

Technical Feasibility

It is a measure of the practically of a specific technical solution and the availability of

technical resources and expertise

• The proposed system uses ASP.NET as front-end and SQL

SERVER 2005 as back-end tool.
• SQL Server 2005 is a popular tool used to design and
develop database objects such as table views.
• The above tools are readily available, easy to work with
and widely used for developing commercial application.
• The proposed system requires the following:

HARDWARE
Main Processor Pentium IV
Hard-disk Capacity 8 G.B
RAM 512 MB
Clock Speed 2.8 Hz
Keyboard 104 Key
Monitor V.G.A

SOFTWARE
Front End HTML, ASP.NET
Back End SQL Server 2005
Operating system Windows XP

With all the above requirements, the software is technically feasible.

26
 Economical Feasibility

It looks at the financial aspects of the project. It determines whether the management
has enough resources and budget to invest in the proposed system and the estimated
time for the recovery of cost incurred. It also determines whether it is worth while to
invest the money in the proposed project. Economic feasibility is determines by the
means of cost benefit analysis. The proposed system is economically feasible because
the cost involved in purchasing the hardware and the software are within
approachable. The personal cost like salaries of employees hired are also nominal,
because working in this system need not required a highly qualified professional. The
operating-environment costs are marginal. The less time involved also helped in its
economical feasibility. It was observed that the organization has already using
computers for other purpose, so that there is no additional cost to be incurred for
adding this system to its computers.
The backend required for storing other details is also the same database that is
Sql Server 2005. The computers in the organization are highly sophisticated
and don’t needs extra components to load the software. Hence the
organization can implement the new system without any additional
expenditure. Hence, it is economically feasible.

Operational Feasibility

The system will be used if it is developed well then be resistance for users that
undetermined
• No major training and new skills are required as it is based on
DBMS model.
• It will help in the time saving and fast processing and dispersal
of user request and applications.

• New product will provide all the benefits of present system

with better performance.

27
• Improved information, better management and collection of the
reports.
• User support.
• User involvement in the building of present system is sought to
keep in mind the user specific requirement and needs.
• User will have control over there own information. Important
information such as pay-slip can be generated at the click of a
button.
• Faster and systematic processing of buyer application approval,
purchasing, payments, etc. used had greater chances of error
due to wrong information entered by mistake.

28
 System Design

Database Design

Tables

Name Type Null?

adminname varchar(50) Allow nulls

adminpassword varchar(50) Allow nulls

Name Type Null?

dloginname varchar(50) Allow nulls

cardnumber varchar(50) Allow nulls
cardvalidity varchar(50) Allow nulls
cardnumber varchar(50) Allow nulls
vccnumber varchar(50) Allow nulls
amount varchar(50) Allow nulls

Name Type Null

cart_id varchar(50) Allow nulls
productid varchar(50) Allow nulls
qty Numeric(9,2) Allow nulls
total Numeric(9,2) Allow nulls

Name Type Null

cart_id varchar(50) Primary key
qty Numeric(9,2) Allow nulls
loginname varchar(50) Allow nulls
date datetime Allow nulls
total Numeric(9,2) Allow nulls

Name Type Null

catid varchar(20) Primary key
catname varchar(30) Allow nulls

29
 Name Type Null
Name varchar(50) Allow nulls
Address varchar(50) Allow nulls
contactnumber varchar(50) Allow nulls
email varchar(50) Allow nulls
feedback Varchar(MAX)
varchar(MAX) Allow nulls
status varchar(50) Allow nulls

Name Type Null

fname varchar(50) Allow nulls
lname varchar(50) Allow nulls
dob datetime Allow nulls
sex varchar(50) Allow nulls
address varchar(50) Allow nulls
location varchar(50) Allow nulls
dloginname varchar(50) Allow nulls
password varchar(50) Allow nulls
retypepassword varchar(50) Allow nulls
email varchar(50) Allow nulls
squestion varchar(50) Allow nulls
yanswer varchar(50) Allow nulls

Name Type Null

imgid int primary key
imgname varchar(200) allow nulls
imgpath varchar(300) allow nulls
productid varchar(20) foreign key

Name Type Null

product id varchar(20) primary key
name varchar(30) allow nulls
price varchar(20) allow nulls
discount varchar(20) allow nulls
subid varchar(20) foreign key
catid varchar(20) foreign key

30
 Name Type Null
name varchar(50) allow nulls
contactno varchar(50) allow nulls
emailed varchar(50) allow nulls
whatproductyouwant varchar(50) allow nulls

Name Type Null

subid varchar(20) Primary key
subname varchar(30) allow nulls
catid varchar(20) Foreign key

Name Type Null

cat_id int
qty numerc(9,2) allow nulls
productid varchar(50) allow nulls
price numerc(9,2) allow nulls

31
 Component Level Design

There are following modules involved in the Online shopping & management:

Module 1: Registration and profile management

In this module all the user are required to get registered yourself before purchase
anything and profile of The users are saved so in the future company promote their
brands.

Module 2: cart/bill management

In this module customer purchase anything then all the details regarding bill are to be
maintained in this module.

Module 3: advertise management

In the advertise management registered customer are put their brand advertisement to
promote their brand so regarding their like payment details and the status of their
advertisement are to be managed
.

Module 4: administrator management

In this module administrator level activities are performed like profiling,

purchasing/carting details about promotions of brands

Module 5: feedback

In the feedback module feedback are to be stored and viewed by the customer while
purchasing so that it is beneficial for customer choose the best among them.

Module 6: news & events

In this module all the current news regarding brands there promotion are displayed.
.
Reports:
This module is handled by the admin section. He can generate the reports such as List of
Employees in an Organization, Report for new events and news.

32
 Technologies Used
Front End Tool

HTML
HTML (Hyper Text Markup Language): A markup language used to structure text
and multimedia documents and to set up hypertext links between documents, used
extensively on the World Wide Web. HTML is a display language, not a programming
language. HTML is a markup language (the ML in HTML) that uses a fixed set of
markup tags.

 HTML itself is the set of customizable “markup” tags that are inserted into
HTML document govern its format, multimedia content, and hyperlinks. Any
HTML viewer can display such documents but they are normally viewed using a
Web browser.

 HTML is a programming language in that an HTML document is a program that,

when “run” by a browser, displays its text as hypermedia (multimedia with
hyperlinks).
 The “language” HTML is really only a collection of predefined tags which , when
inserted into regular text, tell a web browser how to work.

JAVASCRIPT
JavaScript is a compact, object-based scripting language. It can provide interactive
web pages, validate from data, and make your web page clearer. JavaScript is a
lightweight interpreted scripting language. The language is most well known for its
use in websites. It was originally developed by Brendan Each of Netscape
Communications. It adds interactive functions to HTML pages, which are otherwise
static. JavaScript is easier to use than Java, but not as powerful and deals mainly with
the elements on the Web page. On the client, JavaScript is maintained as source code

33
 embedded into an HTML page. On the Server, it is compiled into byte
code(intermediate language), similar o Java programs.

ASP.NET
 ASP Stands for Active Server Pages.
 Microsoft ASP. Net is a technology that allows Programmer to create Dynamic
Web Application.
 ASP. Net is a program that runs inside IIS.
 IIS (Internet Information Services) is Microsoft’s Internet Server.
 ASP. Net file has the file extension “.aspx”.
 ASP. Net file can contain HTML, XML and scripts.
 The .NET Framework is an architecture that’s makes it easier to design.
 The Common Language Runtime (CLR) provides a set of services for all ASP.
Net Languages.

Programming Language : C#
• C# is purely Object Oriented Language.
• C# directly related to C,C++ and Java.

Back End Tool

SQL Server 2005
 Microsoft Server-2005 is a full featured Relational Database
Management System (RDBMS).
 Online Transaction Processing (OLTP) system must be capable of
handling thousands of order placed at the same time.
 MSSQL Server-2005 has verity of Tools.
Enterprise Manager.
Query Analyzer
SQL Profile

34
 Service Manager
Data Transformation Service
Books Online

Testing
Introduction

Reviews are human processes - can not catch all defects. Hence there will be
requirement defects, design defects and coding defects in code. These defects have to be
identified by testing. Therefore testing plays a critical role in ensuring quality. All defects
remaining from before as well as new ones introduced have to be identified by testing.
Here the System testing involved is the most widely used testing process consisting of
five stages as shown in the figure. In general, the sequence of testing activities is
component testing, integration testing, and then user testing. However, as defects are
discovered at any one stage, they require program modifications to correct them and this
may require other stages in the testing process to be repeated.

Unit testing

Module
testing

Sub-system
testing
System
testing

Acceptance
testing

35
(Component testing) (Integration testing) (User testing)

Testing is the process of detecting errors. Testing performs a very critical role for
quality assurance and for ensuring the reliability of the software. The results of testing are
used later on during maintenance also.

Testing is vital to the success of the system. System testing makes a logical assumption
that if the parts of the system are correct, the goal will be successfully achieved. In
adequate testing or non-testing leads to errors that may not appear until months or even
years later (Remember the New York three day power failure due to a misplaced ‘Break’
statement).

This creates two problems:

1. The time lag between the cause and the appearance of the problem.
2. The time interval effect of the system errors on files and the records on the
system.

Test Criteria

WHITE BOX TESTING

This is a unit testing method, where a unit will be taken at a time and tested thoroughly at
a statement level to find the maximum possible errors.

I tested step wise every piece of code, taking care that every statement in the
code is executed at least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data, which is used to check all
possible combinations of execution paths through the code at every module level.

36
White-box test focuses on the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to
ensure that all statement in the program has been executed at least once during testing
and that all logical conditions have been exercised. Basis path testing, a white box
technique, makes use of program graphs (or graph matrices) to derive the set of
linearly independent test that will ensure coverage. Condition and data flow testing
further exercising degrees of complexity.

BLACK BOX TESTING

This testing method considers a module as a single unit and checks the unit at
interface and communication with other modules rather getting into details at
statement level. Here the module will be treated as a block that will take some input
and generate output. Output for a given set of input combinations are forwarded to
other modules.
Black-box test are designed to uncover errors functional requirement without
regard to the internal workings of a program. Black-box testing techniques focus on
the information domain of the software, deriving test cases by partitioning the input
and output domain of a program in manner that provides through test coverage. The
black-box test is used to demonstrate that software functions are operational, that
input is properly produced, and that the integrity of external information are
maintained. A black-box test examines some fundamental aspect of a system with
little or no regard for the integral logical structure of the software.

Graph based testing methods explore the relationship between and behavior of
program objects. Equivalence partitioning divides the input classes of data are likely
to exercise specific software function. Boundary values analysis probes the program’s
ability to handle data at the limits of acceptability.

37
TEST INFORMATION FLOW

A strategy for software testing may also be viewed in the context of the spiral.
Unit testing begins at the vortex of the spiral and, concentrates on each unit,
component of the software as implemented in source code. Testing progresses
moving outward along the spiral to integration testing, where the focus is on
designed the construction of the software architecture. Taking another turn
outward on spiral, we encounter validation testing, where requirements
established as part of software requirements analysis are validated against the
software that has been constructed. Finally, we arrive at system testing, where the
software and other system elements are tested as a whole. To test computer
software, we spiral out along stream lines that broaden the scope of testing with
each turn.

Considering the process from a procedural point of view, testing within the
context of software engineering is actually a series of four steps that are
implemented sequentially. The steps are shown in Figure. Initially, tests focus on
each component individually, ensuring that it functions properly as unit. Hence,
the name unit testing. Unit testing makes heavy use of white-box testing
techniques, exercising specific paths in module’s control structure to ensure
complete coverage and maximum error detection.

38
 System Testing

Validation Testing

Integration Testing

Validation testing

Code
System Security

INFORMATION FLOW OF DATA FOR TESTING

Design

System Engineering

Evaluatio
Software n
Configuration
Test Results

Error
Error Rate Data

Expected Results
Testing
Debug

Reliability
Model
Test Configuration
39
 Predicated Reliability
Correction
Test Cases:

1: Logging in to the system without entering the username/password.

Expected Output: The user should not be purchased

Observed Output: Test case passed

2: Logging in to the system with incorrect username/password.

Expected Output: An error should be generated

Observed Output: Test case passed

3: After successfully logging in as a legitimate user, the URL (address) is copied and
pasted in a new browser.

Expected Output: The legitimate account should not be logged in

Observed Output: Test case passed

4: Submitting the signup form without entering the data

Expected Output: The form should not be posted

Observed Output: Test case passed

5: After successful signup, the user trying to login to the system, the admin ahs not
approved the user as yet

Expected Output: An error should be generated

Observed Output: Test case passed

40
6: If incorrect username is entered

Expected Output: An error should be generated

Observed Output: Test case passed

7: After successfully logging in as a admin, the URL (address) is copied and pasted in a
new browser.

Expected Output: The legitimate account should not be logged in

Observed Output: Test case passed

8: Submitting the signup form without entering the data

Expected Output: The form should not be posted

Observed Output: Test case passed

41
 Implementation
System implementation is the stage when the user has thoroughly tested the
system and approves all the features provided by the system. The various tests are
performed and the system is approved only after all the requirements are met and the user
is satisfied.
The new system may be totally new, replacing an existing manual or
automated system, or it may be a major modification to an existing system. In either case,
proper implementation is essential to provide a reliable system to meet organizational
requirements. Successful implementation may not guarantee improvement in the
organization using the new system (that is a design question), but improper will prevent
it.
Implementation is the process of having systems personnel check out and put new
equipment into use, train users, install the new application and construct any files of data
needed to use it. This phase is less creative than system design. Depending on the size of
the organization that will be involved in using the application and the risk involved in its
use, systems developers may choose to test the operation in only one area of the firm with
only one or two persons. Sometimes, they will run both old and new system in parallel
way to com-pare the results. In still other situations, system developers stop using the old
system one day and start using the new one the next.
The implementation of the web based or LAN based networked project has some
extra steps at the time of implementation. We need to configure the system according the
requirement of the software.

Installation

To install the Offline Counselling Admission System, you have to follow

following steps:

42
Operating System: Windows XP
Software requirements: IIS, SQL Server 2005, Visual Studio 2008

1. Database Deployment:
First create a database “eshop”.
Import data provided for different tables into tables.
Now Database is ready to work.

2. Web Application Deployment:

• Add the database as a data source in the IIS

application developer.
• Modify the resource reference in the deployment
descriptor of the project.

3. ASP.NET and C# application client deployment:

Modify the connection string, login id & password to suit your database.
These are located at adminlogin, buyer_login,
Modify the constraints located at product by admin.

43
 User Manual

There are following users who can perform the following tasks from the graphical user
interphase in a very friendly way:

Administrator:
The administrator can perform following function in very easy manner:

Login: The administrator can login in to the project using the home.aspx page. He is just
supposed to enter id & password.

Change Password: The admin can change his password by clicking Change Password
link in the left pane of the my account page. In this, the admin is just supposed to enter
his old password, new password, retype new password. Then he can click the Change
button.

Change Id: The admin can change his login id using this option. The admin just need to
type his new id and click Change button.

Create News & Events: The admin can use this option to create new news and events.

View News & Events: The admin uses this option to view news and events.

View Feedback & Feedback: The admin uses this option to view news and events.

New Users: The admin can use this option to register new users who have just signed in,
without it the new users would not be able to login. In this, the admin just need to check
the checkbox, following the name of the user and click Register button. The admin can
also choose to select all users by clicking the header checkbox. The admin can view
details of user by clicking at the name of the user.

44
View Users: The admin can use this option to view and block registered users. In this,
the admin just need to check the checkbox, following the name of the user and click

Advertiser Info: The admin can use this option to dynamically control the contents that
would be displayed on the advertiserinfo page (static page). The admin just need to type
the content and press Submit button.

Privacy Policy: The admin can use this option to dynamically control the contents that
would be displayed on the privacy policy page (static page). The admin just need to type
the content and press Submit button.

Logout: The admin can click this link to logout.

Client:
The client can perform the following tasks in a very user friendly way:

Signup: The clients can signup by clicking the Signup link. There he supposed to fill the
form by providing details being asked, displayed in the form. After successful signup, the
user is directed to new page, specifying the success of the signup process.

Login: The user can login by clicking on the Login link and entering username and
password. After successful login, the user is redirected to the my account page.

Feedback: The user can send feedback by clicking the feedback link on the my account
page. In this, he is supposed to enter the topic and content, and press submit button.

Logout: The user cans logout by clicking the logout limit.

45
Future scope and further enhancement of the
Project
Since this system has been generated by using Object Oriented programming,
there are many chances of reusability of the codes in other environment even in
different platforms. Also its present features can be enhanced by some simple
modification in the codes so as to reuse it in the changing scenario. The site is
made in all possible way to meet the user requirements using latest version of
available software and hardware. But as user requirements and operating
environment keep changing further extensions can be made on this.

Future Enhances

a) By making some minor changes the system can be put in front of new system,
will perform better in future.

b) The buyer information like buyer ID,Choice of Product can be added which
will increase the efficiency of the system. Mean it can be full information
management system.

c) By making little modification, this system can handle different databases also
other than SQL Server 2005.

46
 Bibliography
1. Visual Studio 3.5 Black Book - Steven Holzner

2. www.naaptol.com

3. www.w3schools

4. Complete Reference C#.

5. www.asp.net.com

6. www.amazon.com

47
48