SYNOPSIS

This project entitled BSNL SHOW ROOM MANAGEMENT is

useful for purchase and sales SIM card and Datacard form BSNL
Showroom. This project gives the customer and dealer a user friendly
environment. The primary aim of the system is to computerize the
transaction of purchase and sales. The system provides a Datacard show
room which is so effective and useful for the management proprietor. This
project contains seven modules. Such as
Master File

Item
Stock
Sales
Customer

Transaction

Sim Detail
Data Card Detail
Recharge Card Detail
Modem Details
Item Details
Billing Details

Chapter I
INTRODUCTION
1.1. ABOUT THE ORGANIZATION

1.2 ABOUT THE PROJECT

In these Datacards models contains two sub modules, such as
prepaidand another one Postpaid. In this simcard modules deals with all
types of simcards purchase and sales. In this account details contain the
account information about the Datacards and simcards. In this stock
details module maintained to the Datacard stock and simcard stock. In
this bill process module print the reports about the Datacards and
simcards. In this recharge card module maintained the all type of recharge
card purchase and sales. In this data details module maintained input of
Datacard and simcards stock then Datacard and simcard account.

MODULE DESCRTIPTION
Simcards:
In this module contain four sub forms. Such as Aircel, Airtel,
Vodafone, BSNL. These forms contain the details about the all type of
simcards for purchase and sales.
Account details:

In this module contain two sub forms such as Datacard

account and simcard account. These forms maintained the accounts for
Datacards and simcards.
Datacard Account:
In this module contain the information about the account
details for Datacards.

Such as sno, date, Datacard model, purchase

account, sales account, balance account and so on.

Stock Details:
In this module contain two sub forms. Such as stock of Datacard
and stock of simcards. These two forms maintained to the stocks for
Datacards and simcards.
Bill Process:
In this form contain two sub forms. Such as bill process for
Datacard and bill process for simcards. These two forms print the reports
about the Datacards and simcards.
Bill Process for Datacard:
In this form contain the information about the bill details for
Datacard. Such as bill number, date, name, address, Datacard name,
Datacard model, IMEI number, warranty, price, signature and so on.
Bill Process for Simcards:
In this form contain the information about the bill details for
simcards. Such as sno, name, address, contact number, simcard name,
simcard charge, validity period, processing fee, talk value, signature and
so on.
Data Report:
In this module contains the report for Datacard and simcard stock,
then Datacard and simcard account, Bill process for Datacards and
simcards.

Chapter II
REVIEW OF LITERATURE
2.1 EXISTING SYSTEM
Existing system is manual maintenance of records. It makes
the loss of information if the personnel are creates lot of confusion and
improper records of the concern. It takes lot of times so alternate is needs.

2.2 LIMITATIONS OF THE EXIASTING SYSTEM

Separate persons have to be allotted.

Same procedure of work should be adopted.

Lot of human resource need.

Time consuming and tedious process.

Error prone, as found to hand is involved.

Loss of data more occurs.

To reduce the paper work.

Chapter III
SYSTEM STUDY
3.1 PROPOSED

SYSTEM

The proposed is completely menu based. Input screens are properly

designed and online help is also provided. Thus it is very easy for the end
user to work with data fields which are the normalized form thereby data
redundancy.

3.2 ADVANTAGES OF THE PROPOSED SYSTEM:

Immediate accessing of date.

High security.

Providing over all reliability.

Easy data capturing.

Easy and accurate Report generation.

Chapter IV
SYSTEM ANALYSIS
In a process of analyzing a system with the potential goal of
improving or modifying it.

In other words system analysis involves the

study of the present system and formulates the design of something to

achieve a desired goal.

In order to modify it hopefully for the better.

Analysis is the process of breaking down the problems into smaller

elements for study and ultimately solution. The system analysis approach
to a problem differs from trial and error approach.

In trial and error

method, identifying a number of solutions to the problem and then testing

each randomly until the alternative appears to provide can acceptable
solution.

In the system analysis approach all major influences and

constraints are identified and evaluated in terms of this impact on the

various decision points in the system.

A decision point that point in a

system at which some person or automatic mechanism must react to

input output data and make a division.

4.1 DATA FLOW DIAGRAM

LEVEL 0

Administrator

Rejecte
d

Passwor
d
User
Name

Verifying User
Name and
Password

Ok

Enter
Administrator/User

User
Name
Password
Login File

Level 1
Item details
User

Item Code

Item
Detail
s

Sales process

Updating Items

Item
Details

Billing process

Stock Details
Stock File

Bill

4.2 ENTITY RELATIONSHIP DIAGRAM

Customer

Administrator
Recharge card
Modem detail

Controls

Sim detail
Datacard
Name
purchase
Customer

Item Details

Address

Sales Detail

pinno

cusno

Invoice no
Item serial no
price

Tax

offer
Tamount

itemcode

Billing

price

Invoice
no

4.3 SYSTEM SPECIFICATION

Hardware Specification
Processor

: Intel Core 2 Duo.

Speed

2.4GHz.

RAM Capacity

1GB.

Hard Disk Drive

250 GB.

Monitor

LCD.

Key Board

Logitech 104 Key Board.

Printer

Laser printer

Software Specification
Front End

VB.Net2008

Back End

SQL Server 2000

Operating System

Windows XP

ABOUT THE SOFTWARE

VB.NET
The system is developed using Visual Basic. NET, which is a very
popular Microsoft Product developed by Microsoft Corporation. This is one
of the improved languages from basic language. Visual basic. NET
includes a variety of open active controls for user interfaces to design
application form
OVER VIEW OF .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, but internet-distributed, or
executed remotely.

To provide a code execution environment that minimizes software

deployment and versioning conflict.

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

code-execution

environment

that eliminates

the

performance problems of scripted or interpreted environments.

To make the developer experience consist ant across widely varying

types of applications, such as windows-based applications and webbased 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

Common Language Runtime (CLR).

NET framework class library.

Common Language Runtime (CLR).

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 and thread
management 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 principal of the

runtime .Code that targets the runtime isknown as managed code, while
code that dose not target the runtime is known as unmanaged code.

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 explicit both managed and unmanaged features. The .NET framework
not

only

provides

several

runtime

hosts,

but

also

supports

the

development of third-party runtime hosts.

Internet explore is an example of an unmanaged application that runtime

(in the form of a mime type extension).Using internet explorer to host the
runtime enables you to embed managed components or windows from
controls in the HTML document

The Components Of CLR Are:

CTS =>Common Type System.

CLS =>Common Language Specification

CIL =>Common Intermediate Language

JIT =>Just In Time Compiler

VES =>Virtual Execution System

CTS Common Type System

This is the range of types that the .NET runtime understands, and
therefore that .NET application can use. The common type system
supports both object oriented programming like java as well as procedural
languages like c .It deals with two kinds of entities such objects and
values.
CLS-Common Language Specification
This is a subset of the CTS that all .NET languages are expected to
support. The idea is the any program that uses CLS-compliant types can
interoperate with any .NET program written in any language. If a
component written in one language (say c#) is to be used from another
language (say VB.NET) then the component writer must adhere to type
and structures defined by CLS.
CIL-Common Intermediate Language
All compilers complying with CLR must generate an intermediate
language representation called common intermediate language (CIL). The
CIL uses this intermediate language to either generate native code or use
just in compiler (JIT) complication to execute the intermediate code on the
fly.
JIT-Just In Time Compiler
The JIT or just in time compiler is the part of the runtime execution
environment, which is used to convert the intermediate language

contained in the execution file, called assemblies , into native executable

code.
The security policy settings are referred at this to decide if code being
compiled needs to be type safe.
VES-Virtual Execution System
Virtual execution system (VES) is more or less equivalent to the
JVM (Java Virtual Machine).VES loads, links and runs the programs written
for common language infrastructure contained in portable executable (PE)
files.VES fulfill its loader function by using information contained in the
metadata and uses late binding (or linking) to integrate modules compiled
separately, which may even be written in different languages
NET Framework Class Library
The .NET framework library is a collection of reused types that
tightly with the common language runtime (CLR). The class library is
object oriented, providing type from which your own managed code can
derive functionality. Managed codes are intermediate language codes
along with metadata contained in portable executable (PE) files. This not
only makes the .NET framework type easy to use, but also reduces the
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 you r own
collection classes .your collection classes will blend seamlessly with the
classes in the .NET framework.One can use the .NET framework to develop
the following types of application and services.
Console application
Scripted and hosted application
Windows GUI application (windows forms)
VB.NET application
XML web services

Visual Basic .Net

Visual basic .NET preserves VBs general approach to programming
with a SDK development environment and click through forms to get at
the underlying code. The Visual Basic IDE is made up of a number of
components given below

Forms

Toolbox

Tabs

Properties windows

Solution explorer

Output windows

Task list window

Forms
A form is one of the most basic objects in which the application code
and acts as a container for the controls placed on it thus providing a visual
interface. VB.NET initially includes a default form.
Toolbox
The toolbox is an important window, which contains a set of
controls. It contains the controls to create our forms non-graphical
components such as database connections and code fragments that can
be dragged directly from the toolbox into the code window.

Tabs
Different tabs are organized in the toolbox. Some of the tabs are

Data: Contains components that access to data and data sources.

Components:

Contains

various

components

such

as

Reporting,

message queuing etc.

Clipboard ring: Contains a list of the last few items that is copied to
the system clipboard.

General: Empty by default, this is a place for us to store general

controls, components, and code fragments.

Win

forms:

Containing

windows

form

controls

is

automatically

available when windows project is included in the project.

Web forms: Contains server side web form controls that are used to
create web pages.

HTML tab: Contains controls that correspond to the standard HTML

tags.

Properties Window
The properties window appears beneath the solution explorer on the
right-hand of the VS.NET main window. It displays the properties for the
currently selected object in the main window. Pressing key F4 also displays
the properties window for the selected object.
Solution Explorer
Solution explorer window is similar to the project explorer window in
the Bathe solution explorer is a bit more advanced, since it allows us to
construct solutions out of several different projects including those
written in different languages.
Class View
The class view window is somewhat similar to the solution explorer, in
the it provides a view into our solution and project. A view of classes,
methods and properties rather than a view of files are provided by the
class view in the world of object-oriented world of .NET.
Server Explorer
Server explorer is an exciting new feature of VS.NET as it allows us
to explore and access server components in nice graphical environments.

The server explorer lists the data connections and the servers that are
available to the user. It can be used to examine and manipulate servers
and the databases they contain in the server explorer.
Output Window
The output window is similar to the immediate window available in
the previous version of visual basic. The immediate window is used to
view debug output from the application, and to interact with the
environment by entering bits of code or even calling procedures within the
users code.
Task List Window
Task list window is a feature that is used to provide a quick list of all
the current build and syntax errors in our application. The main advantage
of using the task list is that by double-clicking on an error listed in the
window will take us right to the troublesome point in our code.

SQL SERVER 2000

Microsoft SQL Server 2000 is a full-featured relational database
management system (RDBMS) that offers a variety of administrative tools
to ease the burdens of database development, maintenance and
administration.
Enterprise Manager is the main administrative console for SQL
Server installations. It provides you with a graphical "birds-eye" view of all
of the SQL Server installations on our network.
Query Analyzer offers a quick and dirty method for performing
queries against any of our SQL Server databases. It is a great way to
quickly pull information out of a database in response to a user request,
test

queries

before

implementing

them

in

other

applications,

create/modify stored procedures and execute administrative tasks.

SQL Profiler provides a window into the inner workings of your

database. SQL Profiler allows you to capture and replay system "traces"
that log various activities. It is a great tool for optimizing databases with
performance issues or troubleshooting particular problems.
Service Manager is used to control the MS SQL Server (the main
SQL

Server

process),

MSDTC

(Microsoft

Distributed

Transaction

Coordinator) and SQL Server Agent processes. An icon for this service
normally resides in the system tray of machines running SQL Server.

FEATURES OF SQL SERVER 2000

Internet Integration
The SQL Server 2000 database engine includes integrated XML
support. It also has the scalability, availability, and security features
required to operate as the data storage component of the largest
Web sites. The SQL Server 2000 programming model is integrated
with the Windows DNA architecture for developing Web applications.

Scalability and Availability

The same database engine can be used across platforms ranging
from laptop computers running Microsoft Windows 98 through
large, multiprocessor servers running Microsoft Windows 2000 Data
Center Edition. SQL Server 2000 Enterprise Edition supports features
such as federated servers, indexed views, and large memory
support that allow it to scale to the performance levels required by
the largest Web sites.

Enterprise-Level Database Features

The SQL Server 2000 relational database engine supports the
features

required

to

support

demanding

data

processing

environments. The database engine protects data integrity while

minimizing

the

overhead

of

managing

thousands

of

users

concurrently modifying the database. SQL Server 2000 includes a

set of administrative and development tools that improve upon the

process of installing, deploying, managing, and using SQL Server
across several sites.

Data warehousing
SQL Server 2000 includes tools for extracting and analyzing
summary data for online analytical processing. SQL Server also
includes tools for visually designing databases and to analyze the
data.

Chapter V
SYSTEM DESIGN
5.1 DATABASE ANALYSIS
Database design is an important place in designing a system.
During this phase care should be taken to avoid redundancy of
information storing into a database, since it leads to wastage of memory
space.
Normalization Techniques:
Normalization is a process of simplifying the relationship between
data elements in a record. Through normalization a collection of data in a
records structure is replaced by successive record structures that are
simpler and more predictable and therefore more manageable.

First Normal Form

A relation is said to be in first normal form if the values in the

relation are atomic for every attribute in the relation .By this we mean
simply that no attribute value can be a set of values or as it sometimes
expressed, a repeating group.

Second Normal Form

A relation is said to be in second normal form if it is in first normal form

and it should satisfy any one of the following rules.Primary key is a not a
composite primary key.No non-key attribute is fully functionally dependent
on full set of primary key

Third Normal Form

A relation is said to be in third normal form if it is in second normal

form and if their exits no transitive dependencies

Transitive Dependency
If two non-key attributes depends on each other as well as on the

primary key then they are said to be transitively dependent. the above
normalization principles where applied to decompose the data in multiple
tables there by making the data to be maintained in a consistent state.
5.2 DATABASE DESIGN

SIMCARD PURCHASE
FIELD

DATA

NAME
Siname
Sno
Scode
Purdate
Pinno
Price
Offer

TYPE
Text
Integer
Integer
Date/time
Integer
Integer
varchar

WIDTH
20
10
6
8
14
10
10

DESCRIPTION
Simcard Name
Sim Serial Number
Sim puk code
Purchase Date
Sim Pin Number
Simcard price
Offer type

DATACARD SALES
FILED

DATA TYPE

WIDTH

DESCRIPTION

varchar

20

Datacard name

DCno

Integer

20

Datacard Number

DCcode

Integer

DCdate
DCprice

Date/time
Integer

DCoffer

varchar

DCmodel

varchar

NAME
DCname

Datacard Code
8
10

Datacard Sales date

Price
Datacard Offer

10

DATACARD model

RECHARGE CARD
FIELD

DATA

NAME

TYPE

WIDTH

DESCRIPTION

sno

Integer

10

Serial Number

cocode

Integer

Coopen Code

Date/time

redate

Recharge

Coopen

Date
Coopen Serialno

cosno

Integer

16

coprice

Integer

Coopen Price

cooffer

varchar

10

Coopen Offer

MODEM DETAILS
FILED

DATA TYPE

WIDTH

NAME
mcode

Integer

10

DESCRIPTION
Modem Code

msno
mpin
mregdate
mprice
mmodel

Integer
Integer
Date/time
Integer
varchar

20
20
10

Modem S.No
Modem Pin No
Modem Register

20
10

Date
Price
Model

CUSTOMER DETAILS
FILED

DATA TYPE

WIDTH

DESCRIPTION

Integer
varchar
varchar
varchar
Integer
varchar
Date/time

10
15
25
25
10
10

Customer Code
Customer Name
Customer Address
Company Address
Phone No
Email Id
Purchased Date

FILED

DATA TYPE

WIDTH

DESCRIPTION

NAME
Sticode
stitem
sticode
stiname
Item qty
qtyprice

Integer
varchar
Integer
varchar
Integer
Integer

10
10
10
15
10
10

NAME
cuscode
cusname
cusaddr
compaddr
phno
cusemail
pdate

STOCK DETAILS

Stock Code
Stock Item type
Stock item code
Stock item name
Item stock Quantity
Stock quantity price

SALES DETAILS
FILED

DATA TYPE

WIDTH

NAME
Ino
Idate
Cname
Icode
Iname
Isno
Iprice
Icolor
Imodel
off
Ipino

Integer
Date/time
Integer
Integer
Integer
Integer
Integer
varchar
varchar
varchar
Integer

10
15
10
10
10
10
10
15
10
16

DESCRIPTION
Invoice Number
Invoice Date
Customer Name
Item Code
Item Name
Item Serial Number
Item Price
Item Color
Item Model
Offer
Item Pin Number

BILLING DETAILS
FILED

DATA TYPE

WIDTH

NAME
Ino
Idate
Cname
Icode
Iname
simno

Integer
Date/time
Integer
Integer
Integer
Integer

10

simpin

Integer

Isno
Iprice
mpin
Icolor
cusaddr

Integer
Integer
Integer
varchar
varchar

10
10
8
10
25

compaddr

varchar

25

phno
cusemail
Iprice
tax
Itamt

Integer
varchar
Integer
Integer
Integer

10
25
15
10
16

15
10
10
10

DESCRIPTION
Invoice Number
Invoice Date
Customer Name
Item Code
Item Name
SIM No
SIM PIN No
Item Offer
Item Model
Modem PIN No
Item Color
Customer Address
Company Address
Phone No
Email Id
Item Price
TAX
Total Amount

Chapter VI
SYSTEM TESTING
System testing is critical aspect of software quality assurance and
represents the ultimate Review of specification, design and coding. Testing
is a process of executing a program with the intent of finding an error. A
good testing case is that has the probability of finding as yet undiscovered
error. The purpose of the system testing is to identify and correct bugs in
the developed system. Nothing is complete without testing. Testing is vital
to the success of the system.
6.1 SYSTEM TESTING
After each program passes its own test, it is linkage to the other
programs is scrutinized with a program integration test. This ensures that
the program work together as intended. Before the implementation
phase the designed system should be tested with raw data to ensure that
all modules of the system work correctly and satisfactorily. If some bug is
found they can be removed before the implementation phase. The testing
has the four kind of testing that is as follows.
WHITE BOX TESTING
White box testing, sometimes called glass-box testing is a test case
design method that uses the control structure of the procedural design to
derive test cases. Using white box testing methods, the software engineer
can derive test cases.
1. Guarantee that all independent paths within a module have
exercised at least once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational
bounds.
4. Exercise internal data structures to ensure their validity.

BLACK BOX TESTING

Black box testing, also called behavioral testing, focuses on the
functional requirements of the software. That is, black box testing enables
the software engineer to derive sets of input conditions that will fully
exercise all functional requirements for a program. Black box testing is not
an alternative to white box techniques. Rather it is a complementary
approach that is likely to uncover a different class of errors than white box
methods. Black box testing attempts to find errors in the following
categories.
UNIT TESTING
Unit testing is the basic level of testing where individual
components are tested to ensure that they operate correctly. In a properly
designed system, each component should have a precise specification,
and test cases must be defined to check that the component meets
its specification. Unit testing considers each component to be a standalone entity, which does not require other system components to be
present during the testing process. The modules purchase, sales are
individually unit tested using the above approach.
ACCEPTANCE TESTING
Acceptance testing involves planning an execution of a functional
test, performance test and stress test to verify that the implemented
system satisfies the requirement. The acceptance testing is the final stage
of the user the various possibilities of the data are entered and the results
are tested.
VALIDATION TESTING
Software validation is achieved through a series of test that
demonstrates the conformity and requirements. Thus the proposed
system under consideration has to be tested by validation and found to be
working satisfactorily. For example in customer enters phone number field
should contain number otherwise it produces an error message Similarly
in all the forms the fields are validated

6.2 IMPLEMENTATION PLAN

System implementation is loss creative than design but it is a crucial
phase in the system life cycle. It is primarily concerned with ordering of
the items. Implementation is the process of concerning a new system
design into an operational one. Implementation is the stage in the project
where the theoretical design is turned into a working system. The most
crucial stage is achieving a new successful system and in giving
confidence is in getting the approval for the system manager.
The data entry, the various menus and most important reports that
the system is capable of producing are shown to the staff. This is done in
view of any last minute changes that will be necessary in the
formats.When everyone is satisfied, the new system is finally handled
over to the data entry operators. The more complex the system is being
implemented, the more involved will be the systems analysis and design
effect required for the implementation.

Chapter VI
CONCLUSION
The system is more helpful and has advantages over the existing
manual system. Since data are proceed much faster and reports in
required format are quite easily obtained. Any system may also have its
own drawbacks and can be modified further to incorporate the required
changes.
The system deals with the details of the material flow. In future the
system can be implemented to control over flow of cash and labors also.
The details of the staffs of stores department are maintained separately
by administrative personalities. In future if there were any requirement for
adding the details of staff the system is capable of adding them without
changing the database structure.

BIBLIOGRAPHY
REFERENCES
Eilas M.Awad,
Publications (P)

System Analysis And Design, Galgogia

Limited, Second Edition.

Distributed .Net Programming In Vb .Net By Tom

Barnaby
Professional Vb.Net, 2nd Edition By Fred Barwell, Et Al
Roger S Pressman (1997), Software Engineering, Tata
Mcgraw-Hill Publishing Company.
James R Groff And Paul N Weinberg, The Complete
Reference: Sql, Tata Mcgraw-Hill.
Online References:
www.msdn.microsoft.com
www.microsoftdotnet.net
www.developerproject.com