1.0. Certificates 8.2.

T
1.1. Covering Page e
1.2. College Certificate
1.3. Acknowledgement s
1.4. Declaration t
1.5. Abstract

C
2.0. Introduction
2.1. Company Profile a
2.2. Project s
2.3. Overview
e
s
3.0. Literature Survey
4.0. System Analysis 9.0. M
4.1. Existing System
4.2. Proposed System ain
4.3. Feasibility Study
4.4. Project Planning with Graph ten
4.5. Software/ Hardware Requirements
4.6. Modules and its Description an
4.7. Data Flow Diagrams
ce

5.0. Software Requirement Specifications 10.0. F

5.1. Introduction
5.1.1. Scope utu
5.1.2. Purpose
5.1.3. Objective re
5.1.4. Definitions, Acronyms and Abbreviations
5.1.5. References En
5.1.6. Overview
5.1.7. Tools ha

nc
6.0. System Design
6.1. Input Design em
6.2. Output Design ent
6.3. UML Diagrams
11.0. C
6.4. Data Dictionary
6.5. Normalization on
6.6. E-R Diagram clu

sio
7.0. Implementation
n
7.1. Methodology
7.2. Technologies Used

8.0. Testing
8.1. Introduction
12.0. Bibliography

13.0. Screens/ Forms

2-8
 Book Shop Management system

A Book Shop Management system is basically for management of incoming and outgoing material
from the Book shop It also maintain management of all incoming and outgoing finance from the
Shop account section. It will reduce paper work & work load of user. To reduce the Paper work and
provide fast service to customers. The main objective is to provide the customers fast and error
free transaction. It can be used in any Book Shop for maintaining database details and their
quantities. This project is used for handle user needs. It must be outgoing process to know
requirements of customer during whole system development life cycle

Existing system:

The book shop contains different types of books of various subjects with various quality according
to the customer’s needs and requirement. The main thing of the book shop is to maintain lot of
records for the daily transaction of the business. It is necessary for every business to maintain all
records, which show the profit and loss of the business.

Proposed system

While creating new software we should analyze what is the basic need of the software. Analysis is
nothing but a planning of creation of software to get proper output from it. Analysis is details study
of projects that you want to show in your software solving problems. The basic need of the
software is to save the time of the user with the help of all useful information. And also to maintain
the collection of data in your computer systematically, so that it’s easy to understand. The
proposed system provides lot of facility to the user to store information of the Books and it
provides information in quick time in a systematic manner. The processing time on the data is very
fast. It provides required data quickly to the user and also in specified manner to the user.

Modules:

Book Details

Quantities of Books

Customer Details

Sale Details
Customer bill receipt

Rate List


4.1. Software/ Hardware Requirements

Hardware Requirements

• System : Pentium IV 2.4 GHz

• Hard disk : 40 GB

• RAM : 512 MB

Software Requirements

• Operating system : Windows XP Professional

• Technology : Microsoft Visual Studio .Net 2008

• Coding Language : C#

• Back End : SQL Server 2005

2.4 Feasibility study

Depending on the results of the initial investigation the survey is now expanded to a
more detailed feasibility study. “FEASIBILITYSTUDY” 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 candidate system meet them? 2. What resources are available for given
candidate system? 3. What are the likely impacts of the candidate 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.

Feasibility study is the procedure to identify, describe the evaluate candidate system and
select the best possible action for the job. The initial investigation culminated in a proposal
summarized the thinking of the analyst, was presented to the user for review. The
proposal initiated a feasible study to describe and evaluate the best system to choose in
terms of economical, technical and behavioral constraints. The terms constraints involved
in feasibility analysis are-
o Technical

o Economical
o Operational
o Behavioral
2.4.1 Technical Feasibility

 A study of resource availability that may affect the ability to achieve an acceptable
system. This evaluation determines whether the technology needed for the proposed
system is available or not.
 Can the work for the project be done with current equipment existing
software technology & available personal?
 Can the system be upgraded if developed?
 If new technology is needed then what can be developed?

This is concerned with specifying equipment and software that will successfully satisfy
the user requirement. The technical needs of the system may include:
Front-end and back-end selection
An important issue for the development of a project is the selection of suitable front-end
and back-end. When we decided to develop the project we went through an extensive
study to determine the most suitable platform that suits the needs of the organization as
well as helps in development of the project. The aspects of our study included the following
factors.

Front-End selection
1. It must have a graphical user interface that assists employees that are not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.
10. Front-end must support some popular back end like MS Access. According to the
above stated features we selected Java 1.6 as the front-end for developing our
project.
 Back-End Selection

1. Multiple user support.

2. Efficient data handling.
3. Provide inherent features for security.
4. Efficient data retrieval and maintenance.
5. Stored procedures.
6. Popularity.
7. Operating System compatible.
8. Easy to install.
9. Various drivers must be available.
10. Easy to implant with the Front-end.
According to above stated features we selected MS-Access as the backend. The
technical feasibility is frequently the most difficult area encountered at this stage. It is
essential that the process of analysis and definition be conducted in parallel with an
assessment to technical feasibility. It centers on the existing computer system
(hardware, software etc.) and to what extent it can support the proposed system.

2.4.2 Economic Feasibility

Economic justification is generally the “Bottom Line” consideration for most
systems. Economic justification includes abroad range of concerns that includes cost benefit
analysis. In this we weight the cost and the benefits associated with the candidate system
And if it suits the basic purpose of the organization i.e. profit making, the project is
making to the analysis and design phase. The financial and the economic questions during
the preliminary investigation are verified to estimate the following:

 The cost to conduct a full system investigation.

 The cost of hardware and software for the class of application being considered.
 The benefits in the form of reduced cost.
 The proposed system will give the minute information, as a result the performance
is improved which in turn may be expected to provide increased profits.
2.4.3 Operational Feasibility
It is mainly related to human organizations and political aspects. The points to
be considered are:

 What changes will be brought with the system?

 What organization structures are disturbed?

 What new skills will be required?

Do the existing staff members have these skills? If not, can they be trained in
due course of time? The system is operationally feasible as it very easy for the End-users
to operate it. It only needs basic information about Windows platform.

2.4.4 Behavioral Feasibility

After considering the following point that the system is behaviorally feasible. The
project is carried out on the request of the users. To a greater extent, the proposed
system aims at maximizing user friendliness. This is intended to overcome resistance to
change by
the exiting staff. Users are quite experienced in handling the computerized system. Users are
aware of the software and hardware environment.
 3) Project Design

3.1 Entity Relationship Diagram

3.2 Data Flow Diagram

Customer
New Details
Customer Book
Purchase Shop Class
Order Manage Details
ment Order
Sales System Details
Bills
Details
3.2.1 Basic

3.2.2 First Level DFD

3.2.3 Second Level DFD
3.2.4 Third Level DFD
 7.0. IMPLEMENTATION

7.1. Methodology:

Waterfall - Software Development Model

Software products are oriented towards customers like any other engineering products. It is
either driver by market or it drives the market. Customer Satisfaction was the main aim in the
1980's. Customer Delight is today's logo and Customer Ecstasy is the new buzzword of the
new millennium. Products which are not customer oriented have no place in the market
although they are designed using the best technology. The front end of the product is as crucial
as the internal technology of the product.

A market study is necessary to identify a potential customer’s need. This process is also called
as market research. The already existing need and the possible future needs that are combined
together for study. A lot of assumptions are made during market study. Assumptions are the
very important factors in the development or start of a product's development. The assumptions
which are not realistic can cause a nosedive in the entire venture. Although assumptions are
conceptual, there should be a move to develop tangible assumptions to move towards a
successful product.

Once the Market study is done, the customer's need is given to the Research and Development
Department to develop a cost-effective system that could potentially solve customer's needs
better than the competitors. Once the system is developed and tested in a hypothetical
environment, the development team takes control of it. The development team adopts one of
the software development models to develop the proposed system and gives it to the
customers.

This model has the following activities.

1. Software Requirements Analysis

2. Systems Analysis and Design
3. Code Generation
4. Testing
5. Maintenance
1) Software Requirement Analysis

Software Requirement Analysis is also known as feasibility study. In this requirement analysis
phase, the development team visits the customer and studies their system requirement. They
examine the need for possible software automation in the given software system. After
feasibility study, the development team provides a document that holds the different specific
recommendations for the candidate system. It also consists of personnel assignments, costs of
the system, project schedule and target dates.

The requirements analysis and information gathering process is intensified and focused
specially on software. To understand what type of the programs to be built, the system analyst
must study the information domain for the software as well as understand required function,
behavior, performance and interfacing. The main purpose of requirement analysis phase is to
find the need and to define the problem that needs to be solved.

2) System Analysis and Design

In System Analysis and Design phase, the whole software development process, the overall
software structure and its outlay are defined. In case of the client/server processing technology,
the number of tiers required for the package architecture, the database design, the data
structure design etc are all defined in this phase. After designing part a software development
model is created. Analysis and Design are very important in the whole development cycle
process. Any fault in the design phase could be very expensive to solve in the software
development process. In this phase, the logical system of the product is developed.

3) Code Generation

In Code Generation phase, the design must be decoded into a machine-readable form. If the
design of software product is done in a detailed manner, code generation can be achieved
without much complication. For generation of code, Programming tools like Compilers,
Interpreters, and Debuggers are used. For coding purpose different high level programming
languages like C, C++, Pascal and Java are used. The right programming language is chosen
according to the type of application.

4) Testing

After code generation phase the software program testing begins. Different testing methods are
available to detect the bugs that were committed during the previous phases. A number of
testing tools and methods are already available for testing purpose.

5) Maintenance

Software will definitely go through change once when it is delivered to the customer. There are
large numbers of reasons for the change. Change could happen due to some unpredicted input
values into the system. In addition to this the changes in the system directly have an effect on
the software operations. The software should be implemented to accommodate changes that
could be happen during the post development period.
7.2. Technologies Used:

Overview of the .NET Framework

The .NET Framework is a new computing platform that simplifies
application development in the highly distributed environment of
the Internet. The .NET Framework is designed to fulfill the
following objectives:

 To provide a consistent object-oriented programming

environment whether object code is stored and executed
locally, executed locally but Internet-distributed, or
executed remotely.

 To provide a code-execution environment that minimizes

software deployment and versioning conflicts.

 To provide a code-execution environment that guarantees

safe execution of code, including code created by an
unknown or semi-trusted third party.

 To provide a code-execution environment that eliminates

the performance problems of scripted or interpreted
environments.

 To make the developer experience consistent across

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

 To build all communication on industry standards to

ensure that code based on the .NET Framework can
integrate with any other code.

The .NET Framework has two main components: the common

language runtime and the .NET Framework class library. The common
language runtime is the foundation of the .NET Framework. You can
think of the runtime as an agent that manages code at execution
time, providing core services such as memory management, thread
management, and remoting, while also enforcing strict type safety
and other forms of code accuracy that ensure security and
robustness. In fact, the concept of code management is a
fundamental principle of the runtime. Code that targets the runtime is
known as managed code, while code that does not target the runtime
is known as unmanaged code. The class library, the other main
component of the .NET Framework, is a comprehensive, object-
oriented collection of reusable types that you can use to develop
applications ranging from traditional command-line or graphical user
interface (GUI) applications to applications based on the latest
innovations provided by ASP.NET, such as Web Forms and XML Web
services.

The .NET Framework can be hosted by unmanaged components that

load the common language runtime into their processes and initiate
the execution of managed code, thereby creating a software
environment that can exploit both managed and unmanaged features.
The .NET Framework not only provides several runtime hosts, but
also supports the development of third-party runtime hosts.

For example, ASP.NET hosts the runtime to provide a scalable,

server-side environment for managed code. ASP.NET works directly
with the runtime to enable Web Forms applications and XML Web
services, both of which are discussed later in this topic.

Internet Explorer is an example of an unmanaged application that

hosts the runtime (in the form of a MIME type extension). Using
Internet Explorer to host the runtime enables you to embed managed
components or Windows Forms controls in HTML documents. Hosting
the runtime in this way makes managed mobile code (similar to
Microsoft® ActiveX® controls) possible, but with significant
improvements that only managed code can offer, such as semi-
trusted execution and secure isolated file storage.

Features of the Common Language Runtime

The common language runtime manages memory, thread
execution, code execution, code safety verification, compilation,
and other system services. These features are intrinsic to the
managed code that runs on the common language runtime.

With regards to security, managed components are awarded

varying degrees of trust, depending on a number of factors that
include their origin (such as the Internet, enterprise network, or
local computer). This means that a managed component might or
might not be able to perform file-access operations, registry-
access operations, or other sensitive functions, even if it is being
used in the same active application.

The runtime enforces code access security. For example, users

can trust that an executable embedded in a Web page can play an
animation on screen or sing a song, but cannot access their
personal data, file system, or network. The security features of the
runtime thus enable legitimate Internet-deployed software to be
exceptionally feature rich.

The runtime also enforces code robustness by implementing a

strict type- and code-verification infrastructure called the common
type system (CTS). The CTS ensures that all managed code is
self-describing. The various Microsoft and third-party language
compilers generate managed code that conforms to the CTS. This
means that managed code can consume other managed types and
instances, while strictly enforcing type fidelity and type safety.

In addition, the managed environment of the runtime eliminates

many common software issues. For example, the runtime
automatically handles object layout and manages references to
objects, releasing them when they are no longer being used. This
automatic memory management resolves the two most common
application errors, memory leaks and invalid memory references.

The runtime also accelerates developer productivity. For

example, programmers can write applications in their development
language of choice, yet take full advantage of the runtime, the
class library, and components written in other languages by other
 developers. Any compiler vendor who chooses to target the
runtime can do so. Language compilers that target the .NET
Framework make the features of the .NET Framework available to
existing code written in that language, greatly easing the migration
process for existing applications.

While the runtime is designed for the software of the future, it

also supports software of today and yesterday. Interoperability
between managed and unmanaged code enables developers to
continue to use necessary COM components and DLLs.

The runtime is designed to enhance performance. Although the

common language runtime provides many standard runtime
services, managed code is never interpreted. A feature called just-
in-time (JIT) compiling enables all managed code to run in the
native machine language of the system on which it is executing.
Meanwhile, the memory manager removes the possibilities of
fragmented memory and increases memory locality-of-reference to
further increase performance.

Finally, the runtime can be hosted by high-performance, server-

side applications, such as Microsoft® SQL Server™ and Internet
Information Services (IIS). This infrastructure enables you to use
managed code to write your business logic, while still enjoying the
superior performance of the industry's best enterprise servers that
support runtime hosting.

Common Type System

The common type system defines how types are declared, used,
and managed in the runtime, and is also an important part of the
runtime's support for cross-language integration. The common type
system performs the following functions:

Establishes a framework that enables cross-language integration,

type safety, and high performance code execution.

Provides an object-oriented model that supports the complete

implementation of many programming languages.
 Defines rules that languages must follow, which helps ensure that
objects written in different languages can interact with each other.

In This Section Common Type System Overview

Describes concepts and defines terms relating to the common type

system.

Type Definitions
Describes user-defined types.
Type Members
Describes events, fields, nested types, methods, and properties, and
concepts such as member overloading, overriding, and inheritance.

Value Types
Describes built-in and user-defined value types.
Classes
Describes the characteristics of common language runtime classes.
Delegates
Describes the delegate object, which is the managed alternative to
unmanaged function pointers.
Arrays
Describes common language runtime array types.

Interfaces
Describes characteristics of interfaces and the restrictions on
interfaces imposed by the common language runtime.

Pointers
Describes managed pointers, unmanaged pointers, and unmanaged
function pointers.
Related Sections
. NET Framework Class Library
Provides a reference to the classes, interfaces, and value types
included in the Microsoft .NET Framework SDK.

Common Language Runtime

Describes the run-time environment that manages the execution of
code and provides application development services.
Cross-Language Interoperability
The common language runtime provides built-in support for language
interoperability. However, this support does not guarantee that
developers using another programming language can use code you
write. To ensure that you can develop managed code that can be fully
used by developers using any programming language, a set of
language features and rules for using them called the Common
Language Specification (CLS) has been defined. Components that
follow these rules and expose only CLS features are considered CLS-
compliant.

This section describes the common language runtime's built-in

support for language interoperability and explains the role that the
CLS plays in enabling guaranteed cross-language interoperability.
CLS features and rules are identified and CLS compliance is
discussed.

In This Section
Language Interoperability
Describes built-in support for cross-language interoperability and
introduces the Common Language Specification.

What is the Common Language Specification?

Explains the need for a set of features common to all languages and
identifies CLS rules and features.

Writing CLS-Compliant Code

Discusses the meaning of CLS compliance for components and
identifies levels of CLS compliance for tools.

Common Type System

Describes how types are declared, used, and managed by the
common language runtime.
Metadata and Self-Describing Components
Explains the common language runtime's mechanism for describing a
type and storing that information with the type itself.

. NET Framework Class Library

The .NET Framework class library is a collection of reusable types
that tightly integrate with the common language runtime. The class
library is object oriented, providing types from which your own
managed code can derive functionality. This not only makes the .NET
Framework types easy to use, but also reduces the time associated
with learning new features of the .NET Framework. In addition, third-
party components can integrate seamlessly with classes in the .NET
Framework.

For example, the .NET Framework collection classes implement a set

of interfaces that you can use to develop your own collection classes.
Your collection classes will blend seamlessly with the classes in
the .NET Framework.

ADO.NET Overview
ADO.NET is an evolution of the ADO data access model that directly addresses customer
requirements for developing scalable applications. It was designed specifically for the web with
scalability, statelessness, and XML in mind.

ADO.NET uses some ADO objects, such as the Connection and Command objects, and also
introduces new objects. Key new ADO.NET objects include the Dataset, Data Reader, and Data
Adapter.

The important distinction between this evolved stage of ADO.NET and previous data architectures is that
there exists an object -- the Dataset -- that is separate and distinct from any data stores. Because of that,
the Dataset functions as a standalone entity. You can think of the DataSet as an always disconnected
record set that knows nothing about the source or destination of the data it contains. Inside a Dataset,
much like in a database, there are tables, columns, relationships, constraints, views, and so forth.

A Data Adapter is the object that connects to the database to fill the Dataset. Then, it connects back to
the database to update the data there, based on operations performed while the Dataset held the data.
In the past, data processing has been primarily connection-based. Now, in an effort to make multi-tiered
apps more efficient, data processing is turning to a message-based approach that revolves around
chunks of information. At the center of this approach is the Data Adapter, which provides a bridge to
retrieve and save data between a Dataset and its source data store. It accomplishes this by means of
requests to the appropriate SQL commands made against the data store.

The XML-based Dataset object provides a consistent programming model that works with all models of
data storage: flat, relational, and hierarchical. It does this by having no 'knowledge' of the source of its
data, and by representing the data that it holds as collections and data types. No matter what the source
of the data within the Dataset is, it is manipulated through the same set of standard APIs exposed
through the Dataset and its subordinate objects.

While the Dataset has no knowledge of the source of its data, the managed provider has detailed and
specific information. The role of the managed provider is to connect, fill, and persist the Dataset to and
from data stores. The OLE DB and SQL Server .NET Data Providers (System.Data.OleDb and
System.Data.SqlClient) that are part of the .Net Framework provide four basic objects: the Command,
Connection, DataReader and DataAdapter. In the remaining sections of this document, we'll walk
through each part of the DataSet and the OLE DB/SQL Server .NET Data Providers explaining what they
are, and how to program against them.

The following sections will introduce you to some objects that have evolved, and some that are new.
These objects are:

 Connections. For connection to and managing transactions against a database.

 Commands. For issuing SQL commands against a database.

 DataReaders. For reading a forward-only stream of data records from a SQL Server
data source.

 DataSets. For storing, remoting and programming against flat data, XML data and
relational data.

 DataAdapters. For pushing data into a DataSet, and reconciling data against a
database.

When dealing with connections to a database, there are two different options: SQL Server .NET Data
Provider (System.Data.SqlClient) and OLE DB .NET Data Provider (System.Data.OleDb). In these
samples we will use the SQL Server .NET Data Provider. These are written to talk directly to Microsoft
SQL Server. The OLE DB .NET Data Provider is used to talk to any OLE DB provider (as it uses OLE DB
underneath).

Connections

Connections are used to 'talk to' databases, and are respresented by provider-specific classes such as
SQLConnection. Commands travel over connections and resultsets are returned in the form of streams
which can be read by a DataReader object, or pushed into a DataSet object.
Commands

Commands contain the information that is submitted to a database, and are represented by provider-
specific classes such as SQLCommand. A command can be a stored procedure call, an UPDATE
statement, or a statement that returns results. You can also use input and output parameters, and return
values as part of your command syntax. The example below shows how to issue an INSERT statement
against the Northwind database.

DataReaders

The DataReader object is somewhat synonymous with a read-only/forward-only cursor over data. The
DataReader API supports flat as well as hierarchical data. A DataReader object is returned after
executing a command against a database. The format of the returned DataReader object is different
from a recordset. For example, you might use the DataReader to show the results of a search list in a
web page.

DataSets and DataAdapters

DataSets
The DataSet object is similar to the ADO Recordset object, but more powerful, and with one other
important distinction: the DataSet is always disconnected. The DataSet object represents a cache of
data, with database-like structures such as tables, columns, relationships, and constraints. However,
though a DataSet can and does behave much like a database, it is important to remember that DataSet
objects do not interact directly with databases, or other source data. This allows the developer to work
with a programming model that is always consistent, regardless of where the source data resides. Data
coming from a database, an XML file, from code, or customer input can all be placed into DataSet
objects. Then, as changes are made to the DataSet they can be tracked and verified before updating the
source data. The GetChanges method of the DataSet object actually creates a second DatSet that
contains only the changes to the data. This DataSet is then used by a DataAdapter (or other objects) to
update the original data source.

The DataSet has many XML characteristics, including the ability to produce and consume XML data and
XML schemas. XML schemas can be used to describe schemas interchanged via WebServices. In fact,
a DataSet with a schema can actually be compiled for type safety and statement completion.

DataAdapters (OLEDB/SQL)

The DataAdapter object works as a bridge between the DataSet and the source data. Using the
provider-specific SqlDataAdapter (along with its associated SqlCommand and SqlConnection) can
increase overall performance when working with a Microsoft SQL Server databases. For other OLE DB-
supported databases, you would use the OleDbDataAdapter object and its associated OleDbCommand
and OleDbConnection objects.
The DataAdapter object uses commands to update the data source after changes have been made to
the DataSet. Using the Fill method of the DataAdapter calls the SELECT command; using the Update
method calls the INSERT, UPDATE or DELETE command for each changed row. You can explicitly set
these commands in order to control the statements used at runtime to resolve changes, including the use
of stored procedures. For ad-hoc scenarios, a CommandBuilder object can generate these at run-time
based upon a select statement. However, this run-time generation requires an extra round-trip to the
server in order to gather required metadata, so explicitly providing the INSERT, UPDATE, and DELETE
commands at design time will result in better run-time performance.

1. ADO.NET is the next evolution of ADO for the .Net Framework.

2. ADO.NET was created with n-Tier, statelessness and XML in the forefront. Two new
objects, the DataSet and DataAdapter, are provided for these scenarios.

3. ADO.NET can be used to get data from a stream, or to store data in a cache for
updates.

4. There is a lot more information about ADO.NET in the documentation.

5. Remember, you can execute a command directly against the database in order to do
inserts, updates, and deletes. You don't need to first put data into a DataSet in order
to insert, update, or delete it.

6. Also, you can use a DataSet to bind to the data, move through the data, and navigate
data relationships

ASP.NET

Server Application Development

Server-side applications in the managed world are implemented through runtime
hosts. Unmanaged applications host the common language runtime, which allows your
custom managed code to control the behavior of the server. This model provides you
with all the features of the common language runtime and class library while gaining the
performance and scalability of the host server.
The following illustration shows a basic network schema with managed code
running in different server environments. Servers such as IIS and SQL Server can
perform standard operations while your application logic executes through the
managed code.

SERVER-SIDE MANAGED CODE

 ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use
IIS and ASP.NET as the publishing mechanism for applications, and both have a
collection of supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are
distributed, server-side application components similar to common Web sites. However,
unlike Web-based applications, XML Web services components have no UI and are not
targeted for browsers such as Internet Explorer and Netscape Navigator. Instead, XML
Web services consist of reusable software components designed to be consumed by
other applications, such as traditional client applications, Web-based applications, or
even other XML Web services. As a result, XML Web services technology is rapidly
moving application development and deployment into the highly distributed
environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately notice
the improvements that ASP.NET and Web Forms offers. For example, you can develop
Web Forms pages in any language that supports the .NET Framework. In addition, your
code no longer needs to share the same file with your HTTP text (although it can
continue to do so if you prefer). Web Forms pages execute in native machine language
because, like any other managed application, they take full advantage of the runtime. In
contrast, unmanaged ASP pages are always scripted and interpreted. ASP.NET pages
are faster, more functional, and easier to develop than unmanaged ASP pages
because they interact with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services
are built on standards such as SOAP (a remote procedure-call protocol), XML (an
extensible data format), and WSDL ( the Web Services Description Language).
The .NET Framework is built on these standards to promote interoperability with non-
Microsoft solutions.
For example, the Web Services Description Language tool included with
the .NET Framework SDK can query an XML Web service published on the Web, parse
its WSDL description, and produce C# or Visual Basic source code that your
application can use to become a client of the XML Web service. The source code can
create classes derived from classes in the class library that handle all the underlying
communication using SOAP and XML parsing. Although you can use the class library
to consume XML Web services directly, the Web Services Description Language tool
and the other tools contained in the SDK facilitate your development efforts with
the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards,
such as SOAP, WSDL, and XML. Using those classes enables you to focus on the
logic of your service, without concerning yourself with the communications
infrastructure required by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will
run with the speed of native machine language using the scalable communication of
IIS.

ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on the common language runtime

that can be used on a server to build powerful Web applications. ASP.NET offers
several important advantages over previous Web development models:
 Enhanced Performance. ASP.NET is compiled common language runtime code
running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of
early binding, just-in-time compilation, native optimization, and caching services right out of
the box. This amounts to dramatically better performance before you ever write a line of
code.
 World-Class Tool Support. The ASP.NET framework is complemented by a rich
toolbox and designer in the Visual Studio integrated development environment. WYSIWYG
editing, drag-and-drop server controls, and automatic deployment are just a few of the
features this powerful tool provides.
 Power and Flexibility. Because ASP.NET is based on the common language runtime,
the power and flexibility of that entire platform is available to Web application developers.
The .NET Framework class library, Messaging, and Data Access solutions are all
seamlessly accessible from the Web. ASP.NET is also language-independent, so you can
choose the language that best applies to your application or partition your application
across many languages. Further, common language runtime interoperability guarantees
that your existing investment in COM-based development is preserved when migrating to
ASP.NET.
 Simplicity. ASP.NET makes it easy to perform common tasks, from simple form
submission and client authentication to deployment and site configuration. For example, the
ASP.NET page framework allows you to build user interfaces that cleanly separate
application logic from presentation code and to handle events in a simple, Visual Basic - like
forms processing model. Additionally, the common language runtime simplifies
development, with managed code services such as automatic reference counting and
garbage collection.
 Manageability. ASP.NET employs a text-based, hierarchical configuration system,
which simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be applied
without the aid of local administration tools. This "zero local administration" philosophy
extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework
application is deployed to a server simply by copying the necessary files to the server. No
server restart is required, even to deploy or replace running compiled code.
 Scalability and Availability. ASP.NET has been designed with scalability in mind, with
features specifically tailored to improve performance in clustered and multiprocessor
environments. Further, processes are closely monitored and managed by the ASP.NET
runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its
place, which helps keep your application constantly available to handle requests.
 Customizability and Extensibility. ASP.NET delivers a well-factored architecture that
allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to
extend or replace any subcomponent of the ASP.NET runtime with your own custom-written
component. Implementing custom authentication or state services has never been easier.
 Security. With built in Windows authentication and per-application configuration, you
can be assured that your applications are secure.

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages: C#,
Visual Basic, and JScript.

WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language

runtime programming model that can be used on the server to dynamically generate
Web pages.
 Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility
with existing pages), the ASP.NET Web Forms framework has been specifically
designed to address a number of key deficiencies in the previous model. In particular, it
provides:
 The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion (not
"spaghetti code").
 The ability for development tools to provide strong WYSIWYG design support for pages
(existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension.
They can be deployed throughout an IIS virtual root directory tree. When a browser
client requests .aspx resources, the ASP.NET runtime parses and compiles the target
file into a .NET Framework class. This class can then be used to dynamically process
incoming requests. (Note that the .aspx file is compiled only the first time it is accessed;
the compiled type instance is then reused across multiple requests).
An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a user's
name and category preference and then performs a form postback to the originating
page when a button is clicked:
ASP.NET provides syntax compatibility with existing ASP pages. This includes support
for <% %> code render blocks that can be intermixed with HTML content within an .aspx file.
These code blocks execute in a top-down manner at page render time.

CODE-BEHIND WEB FORMS

ASP.NET supports two methods of authoring dynamic pages. The first is the
method shown in the preceding samples, where the page code is physically declared
within the originating .aspx file. An alternative approach--known as the code-behind
method--enables the page code to be more cleanly separated from the HTML content
into an entirely separate file.

INTRODUCTION TO ASP.NET SERVER CONTROLS

 In addition to (or instead of) using <% %> code blocks to program dynamic
content, ASP.NET page developers can use ASP.NET server controls to program Web
pages. Server controls are declared within an .aspx file using custom tags or intrinsic
HTML tags that contain a runat="server" attributes value. Intrinsic HTML tags are
handled by one of the controls in the System.Web.UI.HtmlControls namespace. Any
tag that doesn't explicitly map to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericControl.
Server controls automatically maintain any client-entered values between round
trips to the server. This control state is not stored on the server (it is instead stored
within an <input type="hidden"> form field that is round-tripped between requests).
Note also that no client-side script is required.
In addition to supporting standard HTML input controls, ASP.NET enables
developers to utilize richer custom controls on their pages. For example, the following
sample demonstrates how the <asp:adrotator> control can be used to dynamically
display rotating ads on a page.
1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script library or
cookie requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate common functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built by
third parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list server
controls.
8. ASP.NET validation controls provide an easy way to do declarative client or server data
validation.
 5) System Design

Software design is an actually a multi-step process that focuses on four distinct

attributes of program namely data structure, software architecture, interface
representation and procedural details. The design process translates requirements into a
representation of the software that can be assessed for quality before code generation
begins. The design is documented and is part of the software configuration.

Code Generation

The design must be translated into a machine readable form. The code
generation steps perform this task.

Testing

The testing process focuses on the logical internals of the software assuring that
all statements have been tested and on the functional externals that is conducting tests to
uncover errors and ensure that defined input will produce actual results that agree with
required.

Maintenance

Software will undoubtedly undergo changes after it is delivered to the

customer. Change will occur because errors have been
5.1 Data Tables

1) Users Table – Login Information

No. Field Name Data Type

1 User_Name Text

2 Password Text

2) Books Table – Book Information

No. Field Name Data Type

1 BookID Number

2 BookName Text

3 ISBN Text

4 Category Number

5 Author Text

6 Price Number

7 SalePrice Number

8 Stock Number
3) Cat Table – Book Categories Information

No. Field Name Data Type

1 Cat_ID Number

2 Cat_Name Text

4) Customers Table – Customer Information

No. Field Name Data Type

1 Cust_ID Number

2 Cust_Name Text

3 Cust_Addr Text

4 Cust_No Text

5 CreditAmt Number

6 GenTime Date\Time
5) Bills Table – Bills Information

No. Field Name Data Type

1 Bill_ID Number

2 Customer_ID Number

3 BillDate Date\Time

4 Bill_Details Number

5 Bill_Time Date\Time

6 Total Number

7 TotalDisc Number

8 AmtRecv Number

6) Bill Details Table – Bill Item Details Information

No. Field Name Data Type

1 Bill_Details_ID Number

2 Bill_ID Number

3 Book_ID Number

4 Quantity Number

5 Discount Number

6 Cust_ID Number
 8.0. TESTING

8.1. Introduction

Software testing is a critical element of software quality assurance and represents the

ultimate reviews of specification, design and coding. Testing represents an interesting

anomaly for the software. During earlier definition and development phases, it was

attempted to build software from an abstract concept to a tangible implementation. No

system is error free because it is so till the next error drops up during any phase of the

development or usage of the product. A sincere effort however needs to be put to bring

out a product that is satisfactory.

The testing phase involves the testing of development system using various data.

Preparation of the test data plays a vital role in system testing. After preparing the test

data, the system under study was tested using those data. While testing the system, by

using the test data, errors were found and corrected by using the following testing steps

and corrections were also noted for future use. Thus, a series of testing is performed on

the proposed system before the system is ready for implementation.

TEST PLAN:

The importance of software testing and its implications cannot be overemphasized. Software
testing is a critical element of Software Quality Assurance and represents the ultimate review of
the specifications, design and coding.

Software Testing:
As the coding is completed according to the requirement we have to test the quality of
the software. Software testing is a critical element of the software quality assurance and
represents the ultimate review of specification, design and coding. Although testing is to
uncover the errors in the software functions appear to be working as per the
specification, those performance requirements appear top have been met. In addition,
data collected as testing is conducted provide a good indication of software reliability
and some indications of software quality as a whole. To assure the software quality we
conduct both white box testing and black box testing.

White box testing

White box testing is a test case design method that uses the control structure of the
procedural designs to derive test cases. As we are using a non procedural language,
there is very small scope for the white box testing. Whenever it is necessary, there the
control structures are tested and successfully passed all the control structures with a
very minimum errors.

Black box testing

It focuses on the functional requirements to the software. It enables to derive sets of

input conditions that will fully exercise all functional requirements for a program. The
Black box testing finds almost all errors. It finds some interface errors and errors in
accessing the database and some performance errors. In Black box testing we use two
techniques equivalence partitioning the boundary volume analyzing technique.

System testing:
It is designated to uncover weakness that was not detected in the earlier tests. The total
system is tested for recovery and fallback after various major failures to ensure that no
data are lost. an acceptance test is done to validity and reliability of the system. The
philosophy behind the testing is to find error in project. There are many test cases
designed with this in mond.The flow of testing is as follows
  Code Testing :
Specification testing is done to check if the program does with it should do
and how it should behave under various condition or combinations and submitted for
processing in the system and it is checked if any overlaps occur during the processing.
This strategy examines the logic of the program. Here only syntax of the code is tested.
In code testing syntax errors are corrected, to ensure that the code is perfect.

 Unit Testing :

The first level of testing is called unit testing. Here different modules are
tested against the specification produced running the design of the modules. Unit testing
is done to test the working of individual modules with test oracles. Unit testing comprises
a set of tests performed by an individual programmer prior to integration of the units into
a large system. A program unit is usually small enough that the programmer who
developed it can test it in a great detail. Unit testing focuses first on the modules to
locate errors. These errors are verified and corrected so that the unit perfectly fits to the
project.

 System Testing :

The next level of testing is system testing and acceptance testing. This
testing is done to check if the system has met its requirements and to find the external
behavior of the system. System testing involves two kinds of activities.

 Integration testing
 Acceptance testing

The next level of testing is called the Integration testing. In this many
tested modules are combined into subsystems, which were then tested. Test case data
is prepared to check the control flow of all the modules and to exhaust all possible inputs
to the program. Situations like treating the modules when there is no data entered in the
test box is also tested.
 This testing strategy dictates the order in which modules must be
available, and exerts strong influence on the order in which the modules must be written,
debugged and unit tested. In integration testing, all modules on which unit testing\g is
performed are integrated together and tested.

Acceptance testing:

This testing is performed finally by user to demonstrate that the implemented system
satisfies its requirements. The user gives various inputs to get required outputs.

Specification Testing:

This is done to check if the program does what it should do and how it should behave
under various conditions or combination and submitted for processing in the system and
it is checked if any overlaps occur during the processing.

Performance Time Testing:

This is done to determine how long it takes to accept and respond i.e., the total time for
processing when it has to handle quite a large number of records. It is essential to check
the exception speed of the system, which runs well with only a handful of test
transactions. Such systems might be slow when fully loaded. So testing is done by
providing large number of data for processing. A system testing is designed to uncover
weaknesses that were not detected in the earlier tests.

The total system is tested for recovery and fall back after various major failures to
ensure that no data is lost during an emergency, an acceptance test is done to ensure
about the validity and reliability of the system.
 6) Input / Output Screens

Splash Screen
Login Screen
Main Screen
Sales Operations Screen
New Bill screen
Book Details Screen
Customer Details Screen
Inventory Operations screen

Order Entry
Inventory Details Screen
Reports
Customer Details Report
Stock Report
 8) Future Scope and Limitation

This software has demands in private and public area. This software provides a
great help in managing the data in a well-mannered order. This project is designed specially
to maintain the data in a sequential manner and to save the tome and efforts of database
Administrator. The project is structured according to today’s need.
Due to time constraint it is possible that some points might remain uncovered by us.
In future we will update our software to give valuable information left at present.
Though the system has been designed according to the requirements of the users it has
its own limitation. Thus the limitation of system are-
 No facility to create new users with different roles
 Object oriented Approach has been not been fully utilized
 12.0. BIBLIOGRAPHY

1. Vb. Net Wrox Publications.

2. Unified Modelling Language Grady Booch

3. Software Engeneering Fairely, Pressman

4. Roger S Pressmen, Software Engineering A Practitioner's Approach, Mc-Graw Hill

Publications, Fifth Edition, 200l, New York, Page No. 335-362,477-505

5. Herbert Schildt, the Complete Reference Java 2.0, Tata Mc Graw Hills, Fifth Edition,
1998, New York, Page No. 13-26, 75-316

Websites:

http://www.msdn.microsoft.com/vbasic

http:// www.vbdotnetheaven.com

http:// www.startvbdotnet.com

http:// www.devarticles.com/c/b/VB.Net

http:// www.accelebrate.com/vb.net/default.htm

http:// www.programmersheaven.com/2/VB-NET-School

http:// www.harding.edu/fmccown/vbnet_csharp_comparison.html

http:// www.a1vbcode.com/