1

CHAPTER 1

INTRODUCTION

1.1 COMPANY PROFILE

Ideal Stores, based at Coimbatore, Tamil Nadu, India, is in the business of
retailing in Kitchen & travel related goods since 1948, has 4 showrooms with
dedicated team strength of over 150.

Ideal Stores offers a variety of Italian Modular Kitchens - Either designing a

kitchen for a new house or renovating an existing kitchen, Ideal Stores would help
decide the right kind of Italian modular kitchen. In-house architects specialized in
interior design will assist in planning, designing and installation of the modular
kitchen. With the latest design software, one could even see how a completed kitchen
will look.

Kitchen appliances including Microwave ovens, Dish washers, Kitchen &

electrical house hold appliances – (110 V & 240 V), cooking range, gas stoves, Hobs
& hoods, sinks & faucets, glass ware, crockery & cutlery, cook ware from leading
national and multinational brands – Siemens, Bosch, Elica, Panasonic, Aran, Glen,
Franke, Hawkins, Prestige, Corelle, Faber, Dankotuwa, Philips, Ultra, Laopala,
Borosil, Luminarc, Morphy Richards, Forbes, Pure It, IFB etc. makes Ideal Stores
your destination for total kitchen Solutions.

Ideal Stores has a wide range of travel & travel related goods, life style
products etc., from renowned brands - VIP, Samsonite, American Tourister etc.,

Ideal Stores also offers total solution to commercial kitchen needs - from
plan, design, execution and supply of custom built Commercial Kitchen equipments.
 2

Ideal stores is also a one-stop shop for a wide range of gifts for corporate and
individuals.

Generations of families have experienced the convenience of shopping at

Ideal Stores. This is a reflection of the value and trust, Ideal Stores has built over
these years. Now it’s your turn and Ideal Stores has made shopping even more
convenient. Just order online and ensure delivery at your door step. Ideal Stores has
tied up with reputed & leading courier agents to ensure delivery, anywhere in India
and across the globe.
The company works with the mission “Experience Ideal Stores. Experience
the convenience of shopping”

The features of the company includes

 24 Hours Support
 Shipping to all over the world
 Money back guarantee
 Secured Process

1.2 OBJECTIVE
This software product of product purchase is a Complete Software Package
for department .This Product handles all the market. It can be customized for a
variety of product such as Markets etc. This Product is handling all the functioning of
the shop, from the point of purchase to the end result that is department. The Purpose
of this software is to make all the functioning of a store in a systematic and organized
manner.

Based on these daily updates product are purchased to fulfill dealer

requirements in a given time. This process will continue for every week based on the
updates of dealer’s customer management software will draw schedule of delivery
and schedule of stock requirement.
 3

Main advantages of this project is every operation from purchase and analysis
is transparent market so there is no chance of wrong deal and every operation is
performed through internet which is visible from any location and it is secure and
provide efficient business solution.

 Developing the distinct function of the department store towards marketing of

goods and services;

 Building up and inspiring a body of focused research into the architecture,

aesthetic and design aspects of department centre’s;

 Encouraging the development and spread of sophisticate management

paradigm and maintenance methods;

 Being a knowledge resource store that collects, analyses and disseminates

information on techniques of profitable operation;

 Delving into macroeconomic, legislative and marketing factors with bearing

on the department store industry; and
 4

CHAPTER 2

SYSTEM ANALYSIS

2.1 EXISTING SYSTEM

In existing system customer need to come to shop and provide requirement
details in the form of document. Customers are located at various locations so it is
not efficient method.

Proposed system is a windows based software application through which

customer can update sales details every week based on these status department store
can manufacture stock for next week and provide stock in given schedule. This
application provides scheduling, cost, requirement to customer and department store.

Drawbacks
 Some people (including management, team members, and stakeholders) can
find them difficult to understand;
 Tools can sometimes take too much time just to maintain the data and keep
the tool updated - Don't under estimate the cost of capturing the data;
 They take time and effort and funding to train the staff to use;
 Often can often be expensive and there is a license fee attached to the tool (if
not developed in house) and annual maintenance charges;
 Change them and updating can be costly and complex;
 Staff can use them inappropriately and not enter the required data to make
them worthwhile (e.g. risk management tools).
 5

2.2 PROPOSED SYSTEM

This proposed software is going to be developed using the latest technology
from Microsoft called Microsoft. NET and it is the software that connects
information, people, systems, and devices. It spans clients, servers, and developer
tools.

The .NET Framework 4.5, used for building and running all kinds of
software, including Web-based applications, smart client applications, and XML
Web services components that facilitate integration by sharing data and functionality
over a network through standard, platform-independent protocols such as XML
(Extensible Markup Language), and HTTP.

Developer tools, such as Microsoft Visual Studio.NET 2012, which provides

an integrated development environment (IDE) for maximizing developer
productivity with the .NET Framework.

Advantages
 Help File is there to help the User who use this software
 Effective Search Facility to Search important data with Certain Search
Criteria
 Purchase Module will give a detailed picture about purchases; purchase large
volumes of data can be stored with case.
 Maintenance of file is flexible.
 Records stored are updated now and then.
 Reduces manpower.
 6

CHAPTER 3

SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENT

Processor : Pentium III 500 MHz or Above

RAM : 64 MB or more

Hard disk drive : 10.2GB or higher

Keyboard : SAMSUNG 101 keys

Monitor : Any company’s monitor

Display adapters : Super VGA

CD Drive : Any 52X Drives

Printer : Disk Jet 640 or Above

3.2 SOFTWARE SPECIFICATION

Operating System : WINDOWS 7

Software Tools : Visual Studio 2012

Front End : ASP.NET

Back End : MS SQL

 7

CHAPTER 4

PROJECT DESCRIPTION

4.1 PROBLEM DEFINITION

A departmental store has many departments with a large number of selling
units. Effective co-ordination, supervision and control of all the departments may not
be always possible. This may due to a shortage of qualified staff. Without a team of
professional staff, it creates problems of effective supervision and control over the
work of employees.

A departmental store also has many departments dealing in different lines of

products, since it aims at selling everything under one roof. Such a large retail
organization always requires a large amount of capital to keep business running.

4.2 OVERVIEW OF THE PROJECT

This software product of product purchase is a Complete Software Package for
department .This Product handles all the market. It can be customized for a variety of
product such as Markets etc.

This Product is handling all the functioning of the shop, from the point of
purchase to the end result that is department. The Purpose of this software is to make
all the functioning of a store in a systematic and organized manner.

Project is specially designed in asp.net for organizing schedule details based

on the request of dealers. This application is a web based application through which
dealers will interact with manufacturing shop about sales and product sales.

Based on these daily updates minimum product quantities are maintained to

full fill dealer requirements in a given time. This process will continue for every
 8

week based on the updates of dealer’s customer management software will draw
schedule of delivery and schedule of stock requirement.

4.3 MODULE DESCRIPTION

 Admin Login
 Product Details
 Sales Details
 Stock Details
 Product Analysis
 Customer Details
 Invoice Details
 Report

Admin Login
This module is just an entry point, through which any user/employee can log
into the system and can operate on the system provided they know the Administrator
name and password. In order to log into the system, user/employee has to type the
Administrator name and password in the field provided.

Product Details
A new type of product is added which includes the product id, name, price for
the product. Also the details can be edited if necessary only by the admin.

Sales Details
The day of delivery, as soon as the customer produces the bill of customer id,
product id and his unique customer id number, the user checks in the system whether
that customer id and product id, is available or not. If so he will pass the bill of id to
the production counter. customer id, product id, quantity information is saved in the
database.
 9

Stock Modules
This module Here the product stock information has stored in the system and
a unique product id will be generated from the software. Product id, name, purchase
amount, sales amount, profit details are maintained in database.

Product Analysis
Product and performance details for the product cost can be found below.
This is made using thousands of Performance Test benchmark results and is
updated daily. The graphs show the relative performance of the Product analysis.
If product history data is available for the graph module, a chart with be created
charting price changes.

Customer Details
The user checks in the system whether that customer ID is available or not.
If Customer ID available we can enter the other details. The details are customer
name, Phone no, address, email.id are maintained in database.

Invoice Details
On the day of sales, as soon as the customer produces the bill of product
and his unique bill number, the user checks in the system whether that bill number
is available; if so he will pass the bill of sales to the delivery counter.

Report Module
Only Admin can access the page and check the report.

4.4 DATA FLOW DIAGRAM

A Data flow diagram(DFD) is a graphical representation of the “flow” of
data through an information system.DFD can also be used for the visualization of
data processing(structured design).On a DFD , data items flow from an external
data source or an internal data store or an external data sink, via an internal
process.
 10

Figure 4.1 DFD diagram of Admin/User Module

Figure 4.2 DFD diagram of Admin Module

 11

Figure 4.3 DFD diagram of User Module

4.5 ER DIAGRAM
In software engineering, an entity–relationship model (ER model) is a data
model for describing the data or information aspects of a business domain or its
process requirements, in an abstract way that lends itself to ultimately being
implemented in a database such as a relational database. The main components of ER
models are entities (things) and the relationships that can exist among them.
 12

Figure 4.4 ER diagram

.
 13

5.6 DATABASE DESIGN

It is the process of producing a detailed data model of a database. This logical

data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a Data Definition Language, which
then can be used to create a database. A fully attributed data model contains detailed
attributes for each entity.

Table Name : ADMIN_LOGIN

Primary Key : Username
Description : This table contains information about the login details

Table 4.1 ADMIN_LOGIN

Fields Data Constraints Description Example

type(Size)
Username varchar(20) Primary Key Username Admin
Password varchar(20) Not null Password Admin

Table Name : CUSTOMER _DETAILS

Primary Key : custid
Description : This table contains information about the Customer details

Table 4.2 CUSTOMER _DETAILS

Fields Data Constraints Description Example
type(Size)
Custid Varchar(20) Primary Key Customer Id C10
Custfname Varchar(20) Not null Customer First Name Sabi
Custlname Varchar(20) Not null Customer Last Name Mano
Age varchar(3) Not null Family Member Age 40
Gender varchar(5) Not null Customer Gender Male
 14

Table 4.2 (Continues)

Date Date Not null Customer Date Of 5/1/1965

Birth
City varchar(20) Not null City Coimbatore
State varchar(20) Not null State Tamil nadu
Country varchar(20) Not null Country India
Pincode Varchar(6) Not null Pin code 601025
Contactno Varchar(10) Not null Contact Number 9874561230

Table Name : PRODUCT _DETAILS

Primary Key : Prductid
Description : This table contains information about the product details

Table 4.3 PRODUCT _DETAILS

Fields Data type Constraints Description Example
Prductid varchar(20) Primary Key Product Id P101
Prductname varchar(20) Not null Product Name Toys
Prducttype varchar(20) Not null Product Type Kid Item
Date Date Not null Purchase date 1/5/15
Qnty int(20) Not null Quantity 10
Peramt float(20) Not null Per Amount 100
Totamt float(20) Not null Total Amount 1000
Sid varchar(20) Not null Supplier Id Stk10
Sname varchar(20) Not null Supplier Name Sree
Addr varchar(20) Not null Supplier Address Cbe
Scntno varchar(20) Not null Supplier Contact No 9547816230
Emaiid varchar(20) Not null Supplier Email Id sree@gmail.com
 15

Table Name : SALES _DETAILS

Foreign Key : Custid Refer customerdetails(Table 4.2)
Description : This table contains information about the sales details

Table 4.4 SALES _DETAILS

Fields Data type(Size) Constraints Description Example
Custid varchar(20) Foreign Key Customer Id C10
Custfname varchar(20) Not null Customer Name Sabi

Prductid varchar(20) Foreign Key Product Id P101

Prductname varchar(20) Not null Product Name Toys
Prducttype varchar(20) Not null Product Type Kid Item
Date Date Not null Sales Date 1/65/15
Qunty int(20) Not null Quantity 5
Perqntyprc float(20) Not null Per Quantity Price 200
Totlprc float(20) Not null Total Price 1000

Table Name : STOCK _DETAILS

Primary Key : Stkid
Foreign Key : Productid Refer product_details (Table 5.3)
Description : This table contains information about the stock details

Table 4.5 STOCK_DETAILS

Fields Data type(Size) Constraints Description Example
Stkid varchar(20) Primary key Stock id Stk101
Prductid varchar(20) Foreign key Product Id P101
Prducttype varchar(20) Not null Product Type Kid Item
Date Date Not null Stock Date 1/6/15
Stock int(20) Not null Total stock 10
Pamt float(20) Not null Purchase Amount 100
Samt float(20) Not null Selling Amount 200
 16

Table 4.5 (Continues)

Profit float(20) Not null Profit Amount 100

TotalSold int(20) Not null Total Sold 5
Availbl int(20) Not null Available Product 5

Table Name : SUPPLIER _DETAILS

Primary Key : Sid
Description : This table contains information about the supplier details

Table 4.6 SUPPLIER_DETAILS

Fields Data type(Size) Constraints Description Example
Sid varchar(20) Primary Key Supplier Id Stk10
FirstName varchar(20) Not null User First Name Sree

LastName varchar(20) Not null User Last Name San

Age varchar(3) Not null Supplier Age 55
Gender varchar(5) Not null Supplier Gender Male
Date Date Not null Supplier Date Of 5/1/1960
Birth
Address varchar(30) Not null Address Cbe
City varchar(20) Not null City Coimbatore
State varchar(20) Not null State Tamilnadu
Country varchar(20) Not null Country India
Pcode int(6) Not null Pin code 601024
MobNo varchar(10) Not null Supplier Mobile 9547816230
Number
Emaiid varchar(20) Not null Supplier Email Id sree@gmail.com
 17

Table Name : PRODUCT ANALYSIS_DETAILS

Foreign Key : Productid Refer product_details (Table 4.3)
Description : This table contains information about the product analysis
Details

Table 4.7 PRODUCT_ANALYSIS_DETAILS

Fields Data type(Size) Constraints Description Example
Prductid varchar(20) Foreign key Product Id P101
Prductname varchar(20) Not null Product Name Toys
Price float(20) Not null Product Price 1000

Table Name : INVOICE_DETAILS

Primary Key : Billid
Foreign Key : Custid Refer customerdetails (Table 4.2)
Description : This table contains information about the invoice details

Table 4.8 INVOICE_DETAILS

Fields Data type(Size) Constraints Description Example
Billid varchar(20) Primary key Bill Id B1
Prductid varchar(20) Foreign key Product Id P101
Prductname varchar(20) Not null Product Name Toys

Custid varchar(20) Foreign key Customer Id C10

Custfname varchar(20) Not null Customer Name Sabi

Date Date Not null Billing Date 1/6/15

Qunty int(20) Not null Quantity 5
Totlprc float(20) Not null Total Price 1000
 18

4.7 INPUT DESIGN

Login
Login form will allow the user name and password values such as
Authentication process of the admin (Refer Figure 8.1)

Customer details
This maintenance form will allow the user to enter Customer details such as
Customer name, pickup address, drop address and mobile number (Refer figure 8.2)

Product details
This maintenance form will allow the user to enter the product details such as
product name, product type, date of purchase, quantity and amount (Refer figure 8.3)

Sales details
This maintenance form will allow the user to enter the sales details such as
Customer id, customer name, product id, pname and product type (Refer figure 8.4)

Stock details
This maintenance form will allow the user to enter the stock details such as
product id, pname, product type, stock, profit, and available stock (Refer figure 8.5)

Supplier details
This maintenance form will allow the user to enter the Supplier details such
as Supplier id, name, address, date, email id and mobile number (Refer figure 8.6)

Product analysis details

This maintenance form will allow the user to enter the product analysis details
such as product id, product name and price (Refer figure 8.7)
 19

Invoice details
This maintenance form will allow the user to enter the invoice details such as
product id, product name, customer id, customer name, date, quantity and price
(Refer figure 8.8)

4.7 OUTPUT DESIGN

Login
The Admin user name and password to be stored in a database (shown in the figure
8.1)

Customer details
All the customer details will be stored the database (Refer figure 8.2)

Product details
All the product details will be stored the database (Refer figure 8.3)

Sales details
All the sales details will be stored the database (Refer figure 8.4)

Stock details
All the stock details will be stored the database (Refer figure 8.5)

Supplier details
All the supplier details will be stored the database (Refer figure 8.6)

Product analysis details

All the product analyzing details will be stored the database (Refer figure 8.7)

Invoice details
All the invoice details will be stored the database (Refer figure 8.8)
 20

CHAPTER 5

SYSTEM TESTING

5.1 TESTING
Testing is vital to the success of the system. System testing makes a logical
assumption that if all the part of the system is correct, the goal will be successfully
achieved. It is the major quality measure used to determine the status and usefulness
of the system. Its basic function is to find the error in the software by examining all
possible loopholes.

5.2 MODULE TESTING

Tested the small piece of software for separate specification exists. The
software was executed in an emulator for the module test. The fetching of data will
be done successfully as given below. Refer to figure8.5
Form name : product details form.
Description : This form is tested by giving product details.
Input : all the product details
Output : The details to be saved

5.3 INTEGRATION TESTING

If the user accepts the condition and terms then must load the next form.
Refer to figure 8.4
Form name : customer registration form.
Description : This form is tested by giving customer details.
Input : customer details
Output : “produce customer id”
 21

5.4 VERIFICATION TESTING

Verification is the process to make sure the product satisfies the conditions
imposed at the start of the development phase. The mobile number field should be
validated for each and every form. Refer figures 8.5
Form name : customer registration form.
Description : This form is tested by giving invalid mobile.
Input
Mobile : mobile number is given as alphabet
Output : “only use 0-9 values”

5.5 UNIT TESTING

Unit testing is usually conducted as part of a combined code and unit test
phase of the software lifecycle, although it is not uncommon for coding and unit
testing to be conducted as two distinct phases. Refer to Figures 8.1
Form name : login form.
Description : This form is tested by giving valid username.
Input
Username : admin
Password : admin
Output : “Navigate to homepage”
 22

5.5 TEST CASES

Table 5.1 Test Cases

Form Expected Actual

Type of test Input Status
name output output

Give valid Navigate to

user name and Home page Navigate
Admin Test
Unit testing password to Home
login success
Refers to page
figure 8.2

Need to give Alert

product only the message-
Alert
Verification registration numbers in enter the Test
message
testing form product id valid success
displayed
field Refers to product id
figure 8.5 number

Give all All entries

details and are saved All
check every or highlight entries
fields are not and focus are saved
Functionality Test
Sales null Refers to the fields or
testing success
details figure 8.6 Alert highlight
message- and focus
enter the all the fields.
the details

Need Alert
Customer Alert
Verification to give message- Test
registration message
testing the enter the success
Details displayed
valid

Table 5.1(Continued)
 23

numbers in Mobile
Mobile no number
field ,if not
Refers to
figure 8.4

Need to give Generate

Navigate
Integration the Bill details the Bill slip Test
Bill details to Bill
testing Refer figure Success
slip page
8.7 and 8.8

Need to give Alert

only valid message-
Customer Alert
Verification email id enter the Test
registration message
testing Refer figure valid email success
Details displayed
8.4 id
 24

CHAPTER 6

SYSTEM IMPLEMENTATION

6.1 IMPLEMENTATION
“Consumer Durables” Admin can login to homepage through login page.
Admin can enter the details of customer, product and sales details. By clicking the
bill button the bill will be generated automatically.

The admin has the rights to access the details of the entire database. Bill will
be calculated automatically based on the product and the product quantity details.
The admin can only delete the details from database.

The solution file will be generated automatically when the files are stored.
The solution file will be given to clients and the client can use the system by clicking
the solution.
 25

CHAPTER 7

CONCLUSION AND FUTURE ENHANCEMENT

7.1 CONCLUSION
The package was designed in such a way that future modifications can
be done easily. The following conclusions can be deduced from the
development of the project.

 Automation of the entire system improves the efficiency

 It provides a friendly graphical user interface which proves to be better when
compared to the existing system.
 It gives appropriate access to the authorized users depending on their
permissions.
 It effectively overcomes the delay in communications.
 Updating of information becomes so easier.
 System security, data security and reliability are the striking features.
 The System has adequate scope for modification in future if it is necessary.

7.2 FUTURE ENHANCEMENT

The project ‘Inventory Management System’ has been developed with
the drawback of existing system. it is designed in such a way to solve all problems
existing system. Further ONLINE ORDER can be included as new module. Payment
gateway can also be added as a new feature to support online shopping.
 26

CHAPTER 8

APPENDICES

8.1 SOURCE CODE

using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Data.SqlClient;
using System.Web.Configuration;
public partial class Admin_Product : System.Web.UI.Page
{
string constring =
WebConfigurationManager.ConnectionStrings["Department"].ConnectionString;
SqlConnection con = new SqlConnection();
SqlCommand cmd = new SqlCommand();
decimal quan, price, total;
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{

con = new SqlConnection(constring);

con.Open();
SqlCommand com = new SqlCommand("select count(*) from Product", con);
txtpid.Text = ("DPID" + (Convert.ToInt16(com.ExecuteScalar().ToString())
+ 1).ToString());
con.Close();
 27

}
}

txtper.Text = dr[7].ToString();
txtdate.Text = dr[8].ToString();
txtdes.Text = dr[9].ToString();

}
}
catch (Exception)
{

}
con.Close();
}
protected void BtnUpdate_Click(object sender, EventArgs e)
{
try
{
con = new SqlConnection(constring);
con.Open();
string qry = "update SalesReturn set Userid='" + txtsuid.Text + "',Name='" +
txtfName.Text + "',Pid='" + txtpid.Text + "',Pname='" + txtmname.Text +
"',Returnqty='" + txtquan.Text + "',Pprice='" + txtper.Text + "',Date='" + txtdate.Text
+ "',Des='" + txtdes.Text + "' where Salesrtnid='" + txtsalesretn.Text + "'";
cmd = new SqlCommand(qry, con);
cmd.ExecuteReader();
Page.ClientScript.RegisterStartupScript(this.GetType(), "click",
"alert('Updated Sucessfully');", true);
}
 28

catch (Exception)
{

con.Close();
}
protected void BtnDelete_Click(object sender, EventArgs e)
{
try
{
con = new SqlConnection(constring);
con.Open();
string qry = "delete from SalesReturn where Salesrtnid='" + txtsalesretn.Text
+ "'";
cmd = new SqlCommand(qry, con);
cmd.ExecuteNonQuery();
Page.ClientScript.RegisterStartupScript(this.GetType(), "click",
"alert('Deleted Sucessfully');", true);
}
catch (Exception)
{

con.Close();
}
protected void BtnClear_Click(object sender, EventArgs e)
{
txtsalesretn.Text = "";
txtsuid.Text = "";
 29

txtfName.Text = "";
txtpid.Text = "";
txtmname.Text = "";
txtquan.Text = "";
txtper.Text = "";
txtdate.Text = "";
txtdes.Text = "";

}
protected void BtnExit_Click(object sender, EventArgs e)
{
Response.Redirect("~/Content/Home.aspx");
}
protected void txtsuid_TextChanged(object sender, EventArgs e)
{
con = new SqlConnection(constring);
string selectquery = "select Name,Pid,Pname from Sales where Userid='" +
txtsuid.Text + "'";
cmd = new SqlCommand(selectquery, con);
con.Open();
SqlDataReader red = cmd.ExecuteReader();

try
{
if (red.Read())
{
txtfName.Text = red[0].ToString();
txtpid.Text = red[1].ToString();
txtmname.Text = red[2].ToString();

con.Close();
 30

}
else
{

}
}
catch (Exception)
{
}
finally { con.Close(); }
}
}
 31

8.2 SCREEN SHOTS

This form is used to enter the users Login to allow the authentication process.

Figure 8.1 Login page

Home Page

This form is used to enter the users into the application.

 32

Figure 8.2 Home Page

Supplier Details form

This form is used to Shows the Supply items.

Figure 8.3 Menu list form

Customer Registration Form

This form is used to register the Customer details.

 33

Figure 8.4 Customer Registration Form

 34

Products Details Form

This form is used to enter the product details.

Figure 8.5 Products Details Form

Sales Department Details Form

This form is used to enter the sales department information.

Figure 8.6 Sales Department Details Form

 35

Customer Billing Details Form

This form is used to produce the customer billing information.

Figure 8.7 Customer Billing Details Form

Customer Bill form

This form produce customer bill.

Figure 8.8 Customer Bill form

 36

CHAPTER 9

REFERENCES

Books Referred:

1. Matthew MacDonald “ User Interfaces in C# Windows Forms and

Custom Controls”, 2003
2. Patrick Smacchia “ Practical .Net2 and C#2 Hames the Platform, the
Language, and the Framework”, 2005
3. Louys Davidson “ SQL Server 2005 Database Design,”2004
4. Chris Ullman, John Kauffman, Chris Hart, David Sussman “ASP.NET 3.5”,
2005
5. Dave Mercer, (2002) “ASP.NET – A Beginner’s Guide”, Tata McGraw –
Hill pub . Company Ltd
6. Paul Nielson, (2006) “SQL Server 2005 Bible / Edition 1”, Wiley, John &
Sons, Incorporated.
7. Roger S Pressman, (2008) – “ Software Engineering a Practioner’s
Approach”, Fifth Edition, McGraw-Hill Higher Education

Sites Referred:

1. http://www.sourcefordge.com
2. http://www.almaden.ibm.com/software/quest/resources/
3. http://www.computer.org/publications/dlib
4. http://www.ceur-ws.org/vol-90/
5. http://www.planetsourcecode.com
6. http://www.w3schools.com