Project Report Introduction

Bike Showroom Management System
INTRODUCTION
Jnana Deepa Vidhyapeedham

1.INTRODUCTION
In today’s information-rich society, every field is computerized.

Each and every process done in a firm is stored in a system for easy access and future
reference. In a bike showroom there will be bike sales and information regarding that
sale such as when it has been sold, to whom, details of customer, about the amount and
details of the bike etc. Also showroom has to record the details of employees working
there.
We can add such details to a database in a system. Thus maintaining

the data can be done easier and chance of inconsistency and redundancy can be
reduced to an extent.
Bike showroom Management System is one among them. The

system is meant to fully automate the process done in the showroom. One of the
important objectives of the system is to fasten and improve the process of managing
the showroom.

PROBLEM
DEFINITION

2.PROBLEM DEFINITION
The objective of this project is to create a Bike Showroom

Management System which helps to manage the details about the bikes available and
also the employees working in that showroom. Most of the showrooms today are
running manually storing data in books and files. As the storage medium are books
there is chance of inconsistency, accessing a particular item is very time consuming
and boring task and the probability of errors during calculations is very high. Due to
these drawbacks of the existing manual system, the need of new computerized system
is inevitable.
Using the features of Visual Basic 6.0, the Showroom Management

System has got highly user friendly interface which makes the dealing with the system
simpler and easier. With the MSSQL Server 2005, we can store and retrieve required
data in efficient manner, so that the precious time of users can be saved, calculations
can be made accurately and thereby make their procedures simple.

SYSTEM STUDY

3. SYSTEM STUDY
System study is the most important phase of the system

development. A master plan detailing the steps to be taken and the outcome expected
are prepared. The initial investigation determines whether the users request has
potential merit. The major steps are defining user requirements, studying the present
system and defining performance expected by candidate system to meet the user
requirements.
3.1 Existing System
A bike showroom has to manage a number of forms regarding

delivery, exchange, registration, insurance etc. At present all the procedures are doing
manually. There are many disadvantages for this system. Data security cannot be
assured, retrieving data is difficult. There is chance of losing the stored details. Also
errors occur. It is a time consuming process.
3.2 Proposed System
To take advantage of the latest technology and to manage the details

stored in the showroom a new system needs to be developed. The new system should
accomplish the following functions:
The system should allow the representative to handle the model,

price, tax varying. The booking of bike, exchange information, registration, loan
details all have to be handled. It should store the customer details, update the price and
taxes. The colours available for a specific bike, its chassis no, engine no etc. also has to
be stored.

Modules
This software has mainly two modules:
Administrator module – in which the administrator can enter the essential details
regarding the available bikes in the showroom their price in showroom and the price in
onroad, tax etc.
User module – in this module the user who manage the system in showroom can enter
the details of customer purchased bike, its details such as chassis no, engine no, colour,
date of purchase, if it is exchanged the detail of exchanging one and the new bike etc.
The administrator module includes the following sub modules:
Bike details
It allows the administrator to enter the bikes available and details such as
colour, chassis no, price etc.
Employee details
It allows the administrator to enter each employee working in the showroom and
their details.
The user module includes the following sub modules:
Bike booking
The system user can enter the details of customer who is booking a bike
Search
The user can search whether the required bike is available or not.
Registration details

The details regarding the registration are stored.
Exchange details
The user enters the details of exchanging the bike.
Loan details
The details of loan such as account no are stored.

SYSTEM ANALYSIS

4. SYSTEM ANALYSIS
It is general term that refers to a structural process for identifying

and solving problems. In a computer based transformation system SDLC is the
structured approach. Analysis implies the process of breaching something down in to
its parts so that the whole may be understood.
The requirement of a new system is analyzed for the bike

showroom PSN AGENCIES PVT. LTD. Situated in palarivattom, Cochin. Showroom
contains bike from the makers INDIA YAMAHA MOTOR PRIVATE LIMITED. The
sale of bikes and regarding details, customer details all have to be store in file.
The objective of this project is to create bike showroom

management software which helps to store the details of bikes in the showroom, details
of customers, employees working etc. The customer can purchase a bike by booking
earlier. It can be giving ready cash or can exchange an existing bike. Customer can also
purchase a bike through loan. All the details including registration, insurance are
stored in the database. The software displays all the available bikes and prices, tax,
insurance amount, details of customers.
4.1 FEASIBILITY STUDY

The development and implementation of a new system is definitely

expensive. It requires system resources, manpower, time and money. So it increases the
necessity of the feasibility study based on the proposed system requirements. During
system analysis, the feasibility study of the proposed system is to be carried out.
The study is done in three phases:
Technical feasibility
Economical feasibility
Operational Feasibility
Technical Feasibility
The assessment of technical feasibility must be based on an outline

design of system requirements in terms of input, output, files, programs, and
procedures. This can be qualified in terms of volume of data, trends, frequency of
updating, cycles of activity etc. in order to give an introduction of technical system.
“Bike showroom management system” satisfies technical feasibility because it need
not require any additional hardware or system configuration for implementation and
execution.
Economical Feasibility

Usually for windows applications the costs involved are fairly

minimal. Even features like search, Reporting, functionality for multiple users etc coast
very minimal amount. So the “Bike showroom management system” satisfies
economical feasibility.
Operational Feasibility
The windows application is a highly programmable

environment that allows mass customization through the immediate deployment of a
large and diverse range of applications, to millions of global users.

4.2 SOFTWARE REQUIREMENT SPECIFICATION
Analysis will be helpful to produce a software requirement

specification (SRS). An SRS contains functional requirements, performance
requirements, forms of input and output, design constraints etc.
Functional requirements include functionality details of every

module. The first module, i.e. Employee module consists of the details of employee
including the salary details. In customer module all the details about customer are
stored, also about the details of bike purchasing and delivery details. Sales module
contains to whom bike sold, date amount etc. the other module is Spare sale module
where the spare parts of the bike stored and sold are stored.
Performance requirements involve the minimum hardware

and software needs. In this project we will have the support of Intel Pentium IV
processor, 100GB hard disk, CD drive, key board and printer. Microsoft Visual Basic
6.0 and SQL server 2005 are the supporting software with the help of Windows XP
operating system. Input and output forms are also considerable. In this we enter the
input through key board and get output through the monitor and printer.
Design constraints identify the various conditions for design.

It includes factors which are affecting the input and output design.

4.3 HARDWARE SPECIFICATIONS
System used : Pentium II
Main Memory : 256 MB RAM
Processor Speed : 1.6 GHz
Operating System : WINDOWS XP
4.4 SOFTWARE SPECIFICATION
Operating System : Windows XP
Front End : VISUAL BASIC 6.0
Back End : MS SQL SERVER 2005
SOFTWARE FEATURES
VISUAL BASIC 6.0

Microsoft Visual Basic is the fastest and easiest way to create

applications for Microsoft Windows. Whether the user is an experienced proffessional
or brand new to Windows programming. Visual Basic provides him with a complete set
of tools to simplify rapid application development.The "Visual" part refers to the
method used to create the Graphical User Interface (GUI). Rather than writing
numerous lines of code to describe the appearance and location of interface elements,
one can simply drag and drop pre-built objects to the screen.
The "Basic" part refers to the BASIC (Beginners All Purpose

Symbolic Instruction Code) language used by more programmers than any other
language in the history of computing. Visual Basic has evolved from the original
BASIC language and now contains several hundred statements, functions and
keywords, many of which relate directly to windows GUI. Beginners can create useful
applications by learning just a few keywords, yet the power of language allows
proffessionals to accomplish everything.
Microsoft Visual Basic is one of the powerful RAD (Rapid

Application Development) tools as it enables the proffessionals as well as the beginner
to develop easily.
Visual Basic is object oriented ( I, e all the activities trigger on

event or the other). Each object has its own event handling procedure. It is enough if
one creates the screen layout and then writes the code that will run in response to
specific events. The new features of Visual Basic 6.0 profoundly concentrates on the
internet development features , ActiveX technologies, enhanced controls, Client/server,
data access etc.

The Visual Basic programming language is not unique to Visual

Basic. The Visual Basic programming system, Application edition included in
Microsoft Excel, Microsoft Access and many other Windows applications use the same
language. The Visual Basic programming systems, scripting edition (VB script) for
internet programming is a sub set of Visual Basic language.
The Visual Basic language is quite powerful if one can imagine a

programming task, it can probably be accomplished using Visual Basic. All these basic
commands and functions are available and it is possible to call Windows API
functions, if you need to extend the language.
MS SQL SERVER 2005

SQL Server 2005 (codenamed Yukon), released in October

2005, is the successor to SQL Server 2000. It included native support for
managing XML data, in addition to relational data. For this purpose, it defined an
xml data type that could be used either as a data type in database columns or as
literals in queries. XML columns can be associated with XSD schemas; XML data
being stored is verified against the schema. XML is converted to an internal
binary data type before being stored in the database. Specialized indexing
methods were made available for XML data. XML data is queried using XQuery;
Common Language Runtime (CLR) integration was a main features with this
edition, enabling one to write SQL code as Managed Code by the CLR. SQL
Server 2005 added some extensions to the T-SQL language to allow embedding
XQuery queries in T-SQL. In addition, it also defines a new extension to XQuery,
called XML DML that allows query-based modifications to XML data. SQL
Server 2005 also allows a database server to be exposed over web services using
TDS packets encapsulated within SOAP (protocol) requests. When the data is
accessed over web services, results are returned as XML
For relational data, T-SQL has been augmented with error

handling features (try/catch) and support for recursive queries with CTEs
(Common Table Expressions). SQL Server 2005 has also been enhanced with new
indexing algorithms, syntax and better error recovery systems. Data pages are
check summed for better error resiliency, and optimistic concurrency support has
been added for better performance. Permissions and access control have been
made more granular and the query processor handles concurrent execution of
queries in a more efficient way. Partitions on tables and indexes are supported
natively, so scaling out a database onto a cluster is easier. SQL CLR was
introduced with SQL Server 2005 to let it integrate with the .NET Framework.
SQL Server 2005 introduced "MARS" (Multiple Active Results

Sets), a method of allowing usage of database connections for multiple purposes.

SQL Server 2005 introduced DMVs (Dynamic Management

Views), which are specialized views and functions that return server state
information that can be used to monitor the health of a server instance, diagnose
problems, and tune performance.
SQL Server 2005 introduced Database Mirroring, but it was not

fully supported until the first Service Pack release (SP1). In the initial release
(RTM) of SQL Server 2005, database mirroring was available, but unsupported.
In order to implement database mirroring in the RTM version, you had to apply
trace flag 1400 at startup. Database mirroring is a high availability option that
provides redundancy and failover capabilities at the database level. Failover can
be performed manually or can be configured for automatic failover. Automatic
failover requires a witness partner and an operating mode of synchronous (also
known as high-safety or full safety).

SYSTEM DESIGN
5. SYSTEM DESIGN

Design is the first step in the development phase for any

engineered product or system. Design is a creative process; a good design is the key to
effective system. The term “Design” is defined as “The process of applying various
techniques and principles for the purpose of defining a process or a system in sufficient
detail to permit its physical realization”. It may be defined as the process of applying
various techniques and principles for the purpose of defining a device, a process or a
system in sufficient detail to permit its physical realization. Software design sits at the
technical kernel of the software engineering process and is applied regardless of the
development paradigm that is used. For a project management point of view, software
design is conducted in two steps. Preliminary design is concerned with the
transformation of requirements in to data and software architecture. Detail design
focuses on refinement to the architectural representation that lead to detail algorithm
data structure and representation of software.
In system design high-end decisions are taken regarding the

basic system architecture, platforms and tools to be used the system design transforms
a logical representation of what a given system is required to be in the physical
specification. A design starts with the system requirement specification and converts it
to a physical reality during the development. Important design factors such as
reliability response time, throughput of the system maintainability, expandability etc
should be taken into account.
5.1 INPUT DESIGN

Input screen has to be designed so simple that the user can enter
data easily. The input design involves determining what are the inputs , how the data
should be performed, how to validate data, how to minimize data entry and how to
provide a multiuser facility. In accurate input, data are the most common cause of
errors in data processing. Errors entered by data entry operators can be controlled by
input design. Input design is the process of converting user-originated inputs to a
computer-based format. Input data are collected and organized into groups of similar
data. Once identified, appropriate input media are selected for processing.
Enough messages and dialogue boxes are provided while

design screen, which does guide user at the time of any errors, or at time of entry. This
feature provides a user-friendly interface to native users. It can be emphasized that
input deigns of ACS system is so designed that it ensures easy and error free data entry
mechanism. Once one is sure of input data the output formatting becomes a routine
work.
5.2 OUTPUT DESIGN
A quality output is one, which meets the requirements of the

end user and presents the information clearly. In any systems results of processing are
communicated to the user and to other systems through outputs. In the output design it
is determined how the information is to be displayed for immediate need and also the
hard copy output. It is the most important and direct source information to the user.
Efficient and intelligent output design improves the system’s relationship the user and
helps in decision making.

The objective of the output Design is to convey the

information of all the past activities, current status and to emphasize important events.
The output generally refers to the results and information that is generated from the
system. Outputs from computers are required primarily to communicate the results of
processing to the users. They are also used to provide a permanent copy of these
results for later consultation.
5.3 DATABASE DESIGN
The data in the system has to be stored and retrieved from database.
Designing the database is a part of system design. Data elements and data structures to
be stored have been identified at analysis phase. They are structured and put together to
design the data storage and retrieval system.
A database is a collection of interrelated data stored with minimum

redundancy to serve many users quickly and efficiently. The general objective is to
make database access easy, quick, inexpensive and flexible for the user. Relationships
are established between the data items and unnecessary data items are removed.
Normalization is done to get an internal consistency of data and to have minimum
redundancy and maximum stability. This ensures minimizing data storage required,
minimizing changes of data inconsistencies and optimizing for update times. The SQL
Server database has been chosen foe developing the relevant databases.

Tables
1.Login
Fields Data type Size Constraint
User name nvarchar 20 Primary key
Password nvarchar 20
2.Employee
Emp id nvarchar 50 Primary key
Ename nvarchar 50
Desig nvarchar 25
Address nvarchar 500
Phno number 10
Date of birth date time 10
Email nvarchar 25
Date of join date time
Basic numeric 10
Net salary number 10

3. Customer
Cust id nvarchar 10 Primary key
Cust name nvarchar 20
Address nvarchar 500
Phno number 10
Email nvarchar 15
4. Enquiry
Enq id nvarchar 10 Primary key
Cust id nvarchar 10 Foreign key
Description nvarchar 100
Status nvarchar 50
Next call date date time

5.Booking
Booking id nvarchar 10 Primary key
Cust id nvarchar 10 Forign key
Bike model nvarchar 10
Booking date date time
Advance number 10 check
Expect delivary date date time
Color nvarchar 10

6. Sales
Sales id nvarchar 10 Primary key
Booking id nvarchar 10 Forign key
Showroom price number 10
On road price number 10
Road tax fee number 10
Insurance fee number 10
Registration fee number 10
Chasis no nvarchar 10
Engine no nvarchar 10
Balance Amt number 10
Sales date date time

7. Spare sale
Spare sale id nvarchar 10 Primary key
Spare id nvarchar 10 Foreign key
Cust id nvarchar 10 Foreign key
Sale date date time 10
Quantity number 10
Total number 10
Service number number 10 Primary key
Cust id nvarchar 10
Bike model nvarchar 10
Service type nvarchar 10
Kilometer number 10
Date date time
100
Service details nvarchar
15
Purchase branch nvarchar
name 15
number
Total charge 9
numeric
Reg no

8.Service

5.4 E-R Diagram

designa Addres
Date of
empna tion s
Join
me
Basic
Salary
empid
Bookin
g date Net
advanc Salary
Addres Phone e Employee
s Number Bike
name
custid mode
CustId
Exept
Bookin
Email delivary
g id
date
For For
Customer Booking For
Booking Booking
Enquiry
Enquiry
Spare
Enq Id
Sale Id Spare
Sale id
Spares
Spare
User id Next
id
call
Cus Id date
Spare Status
For For sale
name Sale
Service Spare Sales descrip
date
Bike tion
model
Quantit
Bookin
y Showroo
g Id
Spare m Price
quantit Road
Total
y Tax Fee
Sale iD
For
Servicing
OnRoa
For Sales d Price
Servicing
Service Engine
no
Service Total
SaleDat
No charge
Chasys e
No
Cus Id kilomet
Byke Service er
model Type

Context Level Diagram (Level 0)
5.5 Data Flow Diagram
Employee Details,Customer
care,sales,Service,authentication Sales,costomer care, Service
Administrator Bike Showroom Employee

Management System
Employee Details,Customer Sales,costomer care, Service
care,sales,Service,
authenticated

Level 1
Employee
id
Emp
Employee Settings
ing ils
ag
m an deta ils
r e deta
Fo loye loyee
p Emp
Em
id
st
For booking, Cu
enquiring,follow up Customer
Customer Care
Administrator
ils
deta
mer
Custo
s id
Sale
Sales
Sales
Sales details
Service number
Service
sales
Service Details

Cust id
Customer
Level 1.1
Customer Details
Customer care Booking id
Booking
Booking details
Enquiry
User
Sales id
Sales
Sales Details Sales
Spare Sales
id
Spare Sales
Spare Sales
details
Service
number
Service Service
Service Details

SYSTEM TESTING


6. SYSTEM TESTING
System testing is a stage of implementation, which is aimed at

ensuring that the system works accurately and efficiently before live operation
commences. Testing is the process of executing the program with the intent of finding
errors and missing operations and also a complete verification to determine whether
the objectives are met and the user requirements are satisfied. The ultimate aim is
quality assurance. Tests are carried out and the results are compared with the expected
document. In the case of erroneous results, debugging is done. Using detailed testing
strategies a test plan is carried out on each module.
The various tests performed in system are unit testing, integration

testing, validation testing and system testing.
UNIT TESTING
Unit testing focuses verification effort on smallest unit of software

design module. Here there are two namely, client system and estimation. In unit
testing,
Module interface is tested to ensure that information properly flows

into and put of the program under test.
Local data structures are examined to ensure that data stored

temporarily maintains its integrity during all steps in algorithm execution.
Boundary condition is tested to ensure that the module operates at

boundaries established to limit or restrict processing.

All independent paths through the control structures are executed to

ensure that all statements in the module have been executed at least once.
Error handling paths are also tested.
Unit testing focuses verification effort on the smallest unit of

software design, the module. Here, the module interfaces, local data structures,
boundary conditions, and all independent paths and last but not least, all the error
handling paths were verified by inputting false data. Tests of data flow across each
module interface of this software were done before any other test was initiated.
INTEGRATION TESTING
Integration testing is a systematic technique for constructing the

program structure while at the same time conducting tests to uncover errors associated
with interfacing. Unit tested module were taken and a single program structure was
built that has been dictated by the design. Incremental integration has adopted here.
The entire software was developed and tested in small segments, where errors were
easy to locate and rectify. Programs builds were constructed corresponding to the
successful testing of user integration, data manipulation analysis, and the display
processing and database management. These tests can be performed:
Top down integration
Bottom up integration
VALIDATION TESTING
Validation testing is done to ensure complete assembly of the error-

free software. Validation can be termed successful only if it functions in manner
reasonably expected by the customer.

Under validation is alpha and beta testing. Alpha testing is where

the end user tests the system rather than the developer, but in a controlled environment.
The software is used on a natural setting with the developer

monitoring the user using the system. The developer records the errors and usage
problems encountered by the user. The sales person conducts beta testing at one more
sites. The developer is not present during these tests.
Hence, beta test can be said as the live application of the software
on an environment that cannot be controlled by the developer. The sales person takes
down the problems encountered during beta testing and reports these to the developer
at regular intervals. The developer makes suitable modifications to the software
henceforth.
SYSTEM TESTING
System testing is actually a series of different tests whose primary

purpose to fully exercise the computer based system. Each test works to verify that all
system elements have been properly integrated. Types of system tests are:
1. Recovery Testing
2. Security Testing
3. Stress Testing
4. Performance Testing

ACCEPTANCE TESTING
Undertaken in this project, an acceptance test has the

objective of selling the user on the validity and reliability of the system it verifies that
the system procedures operate to system specification and the integrity of vital data is
maintained. I tested the system with a large collection of records. The system is found
to be user friendly and efficiently. All the above testing was successfully done.

SYSTEM
IMPLEMENTATION

7. SYSTEM IMPLEMENTATION
Implementation is one of the most important tasks of the project.

Implementation is the phase in which one has to be cautious, because all the efforts
undertaken during the project will be fruitful only if the software is properly
implemented according to the plans made. The implementation phase is creative than
system design. It is primarily concerned with user training, site preparation and file
conversion.
When the managers system is linked to terminals on remote sites, the

telecommunication network and tests of the network along with the system are also
included under implementation.Depending upon the nature of the system, extensive
user training may be required. Programming itself is a design work. The initial
parameters of the management information system should be modified as a result of
programming efforts; programming provides a reality test for the assumptions made by
the analyst. System testing check the readability and accuracy of the system access
and retrieve and update data from the new files. Once the program becomes available,
the test data are read into the computer and processed. In most conventions parallel
run was conducted to establish the efficiency of the system.
The most critical stage in achieving a successful new system is giving the
confidence that the new system will work and be effective. The system can be
implemented only after thorough testing is done and if it is found to be working
according to the specification. This method also offers the greatest security since the
old system can take over if the errors are found or inability to handle certain type of
transactions while using the system.


SYSTEM
MAINTENANCE

8. SYSTEM MAINTENANCE
Software maintenance is the process of modifying a

software system or components after its delivery in order to correct faults, improve the
performance and other attributes, or to adapt to a change environment. Maintenance
covers a wide range of activities including correcting the coding and design errors,
updating the documentation and test data, and upgrading the user support. There is an
aging process that calls for periodic maintenance or hardware and software.
Maintenance is always necessary to keep the software usable and useful. Hardware
also requires periodic maintenance to keep the system into its standards. Software
maintenance activities can be classified in to three:
Corrective maintenance
Adaptive maintenance
Perfective maintenance
Corrective maintenance removes software faults. Perfective

maintenance improves the system without changing its functionality. The objective of
perfective maintenance should be to prevent failures and optimize the software.

Adaptive maintenance modifies the software to keep it up

to date with its operative environment. It may be needed because of changes in the
user requirements, changes in target platform, or changes in external interfaces. Minor
adaptive changes should be handled by normal maintenance process. Major
adaptiveness should be carried out as, a separate development process.
8.1 Future Enhancement
The requirement of the company is bound to change as and

when new changes are made within the organization. This system has been designed in
such a way that any further enhancement can be incorporated with the existing system.
Any changes to the showroom management can be implemented to the system. This
system has been developed using VB, Therefore any further enhancement will surely
add to the feasibility and usefulness of the system for the organization as a whole in the
future.



CONCLUSION
9. CONCLUSION
The project Showroom Management System has been developed to

overcome the problem faced in the present system. The developed package was found
to work out the operation effectively. The objectives such as reducing inconsistency,
limiting redundancy, accessing data within less time of the system have been achieved.
A consistent and efficient system has been successfully

developed, implemented and tested. The system has been developed using VB 6.0
under Windows XP. The system is very flexible and user friendly. So further changes
can be incorporated into these systems easily. Adequate documentation provides for
maintenance and future enhancement.


APPEDNIX

10. APPENDIX
SREEN SHOTS







10.2 SAMPLE SOURCE CODE
For Form Load
Private Sub Form_Load()
connection
conn.Open sConnString
Set cmd.ActiveConnection = conn

cmd.CommandText = "SELECT Empid FROM Employee"
cmd.CommandType = adCmdText
Set rs = cmd.Execute
Do While Not rs.EOF
For iCtr = 0 To rs.Fields.Count - 1
cmbEmployeeid.AddItem (rs.Fields(0).Value)
Next
rs.MoveNext
Loop
Set rs = Nothing
Set cmd = Nothing
conn.Close
Set conn = Nothing
End Sub
For inserting
Private Sub cmdinsert_Click()
connection

cmd.CommandText = "insert into Employee values('" & cmbEmployeeid.Text & "','"

& txtEmployeename.Text & "','" & cmbDepartment.Text & "','" & rtxtDescription.Text
& "','" & rtxtAddress.Text & "','" & txtPhonenumber.Text & "','" &
dtpDateofbirth.Value & "','" & txtemail.Text & "')"
cmd.Execute
MsgBox ("inserted")
End Sub
Selecting from appropriate id
Private Sub cmbEmployeeid_Click()
connection
cmd.CommandText = "SELECT
Empname,Department,Description,Address,Phno,dob,email FROM Employee where
Empid='" & cmbEmployeeid.Text & "'"
Set rs = cmd.Execute

Do While Not rs.EOF
For iCtr = 0 To rs.Fields.Count - 1
txtEmployeename.Text = rs.Fields(0).Value
cmbDepartment.Text = rs.Fields(1).Value
rtxtDescription.Text = rs.Fields(2).Value
rtxtAddress.Text = rs.Fields(3).Value
txtPhonenumber.Text = rs.Fields(4).Value
dtpDateofbirth.Value = rs.Fields(5).Value
txtemail.Text = rs.Fields(6).Value
Next
rs.MoveNext
Loop
Set rs = Nothing
Set cmd = Nothing
conn.Close
Set conn = Nothing
End Sub

For deleting:
Private Sub cmdDelete_Click()
connection
cmd.CommandText = "delete Employee where Empid='" & cmbEmployeeid.Text &

"'"
cmd.Execute
MsgBox ("Deleted")
End Sub

BIBILOGRAPHY

11. BIBILOGRAPHY
BOOKS
System Analysis and Design : Elias.M.Award
Guide to Visual Basic 6.0 : Peter Norton
Database System Concepts : Abraham Silberschatz
Henery.F.Korth
Sudarshan

Project Report Introduction

Uploaded by

Copyright:

Available Formats

You might also like

Project Report Introduction

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Project Report Introduction

Uploaded by

Copyright:

Available Formats

Bike Showroom Management System

Jnana Deepa Vidhyapeedham

In today’s information-rich society, every field is computerized.

We can add such details to a database in a system. Thus maintaining

Bike showroom Management System is one among them. The

Jnana Deepa Vidhyapeedham

Jnana Deepa Vidhyapeedham

The objective of this project is to create a Bike Showroom

Using the features of Visual Basic 6.0, the Showroom Management

Jnana Deepa Vidhyapeedham

Jnana Deepa Vidhyapeedham

System study is the most important phase of the system

3.1 Existing System

A bike showroom has to manage a number of forms regarding

3.2 Proposed System

To take advantage of the latest technology and to manage the details

The system should allow the representative to handle the model,

Jnana Deepa Vidhyapeedham

This software has mainly two modules:

The administrator module includes the following sub modules:

The user module includes the following sub modules:

Jnana Deepa Vidhyapeedham

The details regarding the registration are stored.

The user enters the details of exchanging the bike.

The details of loan such as account no are stored.

Jnana Deepa Vidhyapeedham

Jnana Deepa Vidhyapeedham

It is general term that refers to a structural process for identifying

The requirement of a new system is analyzed for the bike

The objective of this project is to create bike showroom

4.1 FEASIBILITY STUDY

Jnana Deepa Vidhyapeedham

The development and implementation of a new system is definitely

The study is done in three phases:

The assessment of technical feasibility must be based on an outline

Jnana Deepa Vidhyapeedham

Usually for windows applications the costs involved are fairly

The windows application is a highly programmable

Jnana Deepa Vidhyapeedham

4.2 SOFTWARE REQUIREMENT SPECIFICATION

Analysis will be helpful to produce a software requirement

Functional requirements include functionality details of every

Performance requirements involve the minimum hardware

Design constraints identify the various conditions for design.

Jnana Deepa Vidhyapeedham

4.3 HARDWARE SPECIFICATIONS

System used : Pentium II

Main Memory : 256 MB RAM

Processor Speed : 1.6 GHz

Operating System : WINDOWS XP

4.4 SOFTWARE SPECIFICATION

Operating System : Windows XP

Front End : VISUAL BASIC 6.0

Back End : MS SQL SERVER 2005

VISUAL BASIC 6.0

Jnana Deepa Vidhyapeedham

Microsoft Visual Basic is the fastest and easiest way to create

The "Basic" part refers to the BASIC (Beginners All Purpose