Index Content

 PROJECT PROFILE
 INTRODUCTION
 OBJECTIVE
 PURPOSE
 SDLC
 SYSTEM ANALYSIS
 FEASIBILITY
 SPIRAL MODEL
 REQUIREMENT SPECIFICATION
 HARDWARE/SOFTWARE
 FRONT END
 BACK END
 DESIGN
 DFD
 CONTEXT DIAGRAM
 E-R DIAGRAM
 DATADICTIONARY
 FORMS
 DATA REPORT
 CODING
 TESTING
 IMPLEMENTATION
 FUTURE SCOPE
 CONCLUSION
 BIBLOGRAPHY
 Project Profile
Project Title “BOOK SHOP MANAGEMENT SYSTEM”

Project definition Watch shop management system

provides better way to manage records of
customers. It also reduces paper work
and loss of data is also reduced to a
greater extent.

Developed for Revolution in management

Internal project guide Ms. RADHIKA SAHU

Team Size 1 (individual project)

Developer Laxmi Sori

Hardware configuration Processor :-Intel Core Processor above

Pentium IV

Ram :-512 MB

Hard Disk:- 1 GB

Front end VISUAL BASIC 6.0

Back end MS ACCESS

Operating system WINDOWS 10

 1. INTRODUCTION
Computer technology makes a dramatic break with the past:

Most companies are designed and use their applications that which the
application runs on the user access a maintained manage file or database.

The concept of computerized report has important in the

industry, which needs information to retrieve in the fast and efficient
way.

Objectives of the system

 Increased end-user productivity because of flexible data access.
 Graphical oriented, highly interactive user interface.
 Increased developer productivity through usage of easy to use tools.
 Improved access to information because of computerizing.
 Easier maintenance of application and data.

Every organization has a system generating and monitoring various

kinds of data and report that are very relavant for the smooth functioning
of that organization. Effective decisions are to be taken by the
management based on the current data information which
provides accurate and help the management.

The main aim of this project is to maintain all the records by

computerized the watch showroom. This existing system is a manual
system. so there is a lot of limitation like large number of man
power. On using this project customer could view and purchase the
product directly .It gives computerization helps the supplier to reduce
the paperwork.

Sonata
Sonata is the Value for Money watch brand from Titan Industries Ltd. It
is targeted at consumers seeking durability and value, with a clear
positioning of " No compromise watch". Sonata comes with the backing
of being a Tata product with five clear functional attributes,
Affordability, looks, 1 Year Guarantee, Waterproof (up to 30m water
resistant) and Durability. It is therefore known as " 5 Ghadi ke barabar"
an equivalent for no-compromise watch. It is India's largest selling
watch brand with a sale of over 30 Lakh watches in 2003-04.

Sonata has a wide range of over 400 watches in different traditional

designs for gents and ladies. The range starts from Rs 395 and goes up to
Rs 1250. The exclusive designs are made with best quality material,
undergoing several stringent tests. Primarily, Sonata is known for being
a brand that is strong in gold plated watches, and it also has a very good
collection of steel watches.

Classic

Classic is the renowned brand of horological products in India. The

company was started as a trading house in 1978 and got appointed as
distributor for many leading brands for northern India, graduated to
become the pioneers in manufacturing and marketing a range of fancy
wall and table clocks in 1986. Our's was the first company to give high
priced clocks to the trade.

In 1993 the company saw an opportunity to manufacture and

market Quartz wristwatches and decided to enter this segment with
one goal in mind to give the consumer real value for money.

Classic watches offers an astonishing range of gents and ladies watches

and has become one of the best selling brands in the country because of
the quality, design and most important it's price range of MRP Rs. 395/-
onwards. The watches are gold plated to 3 microns to provide enduring
plating and are fitted with matching genuine leather or metal
straps. Most of the watches are 3 ATM water resistant and are
guaranteed for one year including gold plating.
Recently, the company has introduced a new range named CYBER for
so planned the young and trendy consumer in analogue and
digital watches with alarm, chronograph and multifunction
features, starting at a price point of Rs. 295/- onward

. Organization Profile

Kanagaraj Watch showroom is one of the famous watch showroom in

Avinashi. The showroom was establishing in the year of 1999.It is
located at Avinashi.

It deals with all kinds of alarms, wall clocks and wristwatches.

This watch showroom purchased from company dealers and sold to the
customers. This showroom provides one year guarantee to all the
products the have. All the latest and valuable kinds of alarms,
wallclocks and wristwatches are available they also provide
service to the watches.

The main objectives of this shop are

 Quality Maintenance

 Reasonable Price

 Regular Customer

 New Varieties

 Discount Sale
Kanagaraj Watch showroom runs according to satisfaction of
the customer. It has customer from various places. This showroom
runs with four employees.
PURPOSE
The project titled as “WATCH SHOP MANAGEMENT SYSTEM”
is developed in vb as front end and ms access as back end. The
main aim of the project is to make a complete solution for
watch sales system. ... The watches are purchased from the dealers
SOFTWARE DEVELOPMENT LIFE CYCLE
(SDLC)
The ultimate objective of software engineering is to produce good quality
maintainable software within reasonable time frame and at affordable cost. This is
achievable only if we have matured processes to produce it. For a mature process,
it should be possible to determine in advance how much time, cost and effort will
be required to produce the final product. This can only be done using data from
past experience, which requires that we must measure the software process.
A key component of any software development process is the life cycle model on
which the process is based. Life cycle of the software starts from concept
exploration and ends at the retirement of the software.
The system life cycle is:
The period of time that starts when a software product is conceived and ends when
the product is no longer available for use. The software life cycle typically
includes a requirement phase, design phase, implementation phase, test phase,
installation and check out phase, operation and maintenance phase, and sometimes
retirement phase.
In this project the Spiral Model has been used
REQUIREMENT ANALYSIS &FEASIBILITY
STUDY
When we receive a request for a new software project from the customer, first of
all, we would like to understand the requirements of the project.
Requirement analysis is very important and essential activity. We analyze, refine
the gathered requirements in order to make consistent and unambiguous
requirements.

In spite of understanding the project we would also analyses whether it is feasible

in terms of cost, technical and market. If it is not feasible in any term it will not be
fruitful to develop such a project.
Initially it should also be analyzed whether the requirements for the
project(hardware and software) are affordable or feasible.

So before preceding further to the design issues here we will discuss in some what
detail the requirement analysis and the feasibility study of the project.

REQUIREMENT ANALYSIS
Requirements analysis inand software engineering, encompasses those tasks that
determines the needs or conditions to meet for a new or altered product, taking
account of the possibly conflicting requirements of the various stakeholders, such
as beneficiaries or users.

Requirements analysis is critical to the success of a development project.

Requirements must be documented, actionable, measurable, testable, related to
identified business needs or opportunities, and defined to a level of detail sufficient
for system design. Requirements can be architectural, structural, behavioral,
functional, and non-functional.

Conceptually, requirements analysis includes three types of activity:

 Eliciting requirements: the task of communicating with customers and users

to determine what their requirements are. This is sometimes also called
requirements gathering.
 Analyzing requirements: determining whether the stated requirements are
unclear, incomplete, ambiguous, or contradictory, and then resolving these
issues.
  Recording requirements: Requirements might be documented in various
forms, such as natural-language documents, use cases, user stories, or
process specifications.

FIG 3.1: REQUIREMENT ANALYSIS STEPS

The various steps of the requirement analysis are shown in figure 3.1:

(i) Draw the context diagram:

The context diagram is a simple model that
defines the boundaries and interfaces of the proposed system with the
external world. It identifies the entities outside the proposed system that
interact with the system.

(ii) Development of a prototype:

One effective way to find out what the customer
really wants is to construct a prototype. Prototype helps the client to
 visualize the proposed system and increase the understanding of
requirements.

(iii) Model the requirements:

This process is usually consist of various
graphical representation of the functions data entries external entities and
relationship between them. This will help us to find the incorrect
inconsistent missing requirements.

(iv) Finalize the requirements:

After modeling the requirements now we finalize
the analyzed requirements and next step is to document these
requirements

FEASIBILITY STUDY
A feasibility study is conducted to select the best system that meets performance
requirement. This entails an identification description, an evaluation of candidate
system and the selection of best system for the job. The system required
performance is defined by a statement of constraints, the identification of specific
system objective and a description of outputs.
The key consideration in feasibility analysis are:
1. Economic Feasibility
2. Technical Feasibility
3. Operational Feasibility

Economical Feasibility:-
It looks at the financial aspect of the project. It determines whether the
management has enough resources and budget to invest in the proposed system and
the estimated time for the recovery of cost incurred. It also determines whether it
is worth while to invest the money in the proposed project. Economic feasibility is
determines by the means of cost benefit analysis. The proposed system is
economically feasible because the cost involved in purchasing the hardware and
the software are within approachable. The personal cost like salaries of employees
hired are also nominal, because working in this system need not required a highly
qualified professional. The operating-environment costs are marginal. The less
time involved also helped in its economical feasibility
Technical Feasibility :-
It is a measure of the practically of specific technical solution and the availability
of technical resources and expertise.

 The proposed system uses VISUAL BASIC 6.0as front-end and MS

ACCESS as back-end tool.
 MS ACCESS is a popular tool used to design and develop database objects
such as table views, indexes.
 The above tools are readily available, easy to work with and widely used for
developing commercial application.

Operational Feasibility:-
The system will be used if it is developed well then be resistance for users that
undetermined:
 No major training and new skills are required as it is based on SPIRAL
model.
 It will help in the time saving and fast processing and dispersal of user
request and application.
 New product will provide all the benefits of present system with better
performance.
 User involvement in the building of present system is sought to keep in mind
the user specific requirement and needs.
 User will have control over there own information. Important information
such as pay slip can be generated at the click of a button.
 Faster and systematic processing of user application approval, allocation of
IDs payments, etc. used had greater chances of error due to wrong
information entered mistake.
SUMMARY
Here we have dealt with the requirement analysis and the feasibility study which
gives the better understanding of the project.
Requirement analysis determines the needs to be fulfilled and what the prepared
document should do after completion. For the better understanding of the
requirements we will draw the context diagram then build a prototype, analyze the
requirements and lastly finalize them.

In feasibility we analyze the feasibility of the project in terms of economic

feasibility, technical feasibility and operational feasibility.

Spiral Model:
The problem with traditional software process models is that they do not deal
sufficiently with the uncertainty, which is inherent to software project. Important
software projects have failed because project risks were neglected and nobody was
prepared when something unforeseen happened. Barry Boehm recognized this and
tried to incorporate the “Project Risk” factor into a life cycle mode. The result is
the spiral model, which was presented in 1986 [BOEH86].
The radial dimension of the model represents the cumulative costs. Each path
around the spiral is indicative of increased costs. The angular dimension
represents the progress made in completing each cycle. Each loop of the spiral
from X-axis clockwise through 360 degree represents one phase. One phase is
split roughly into four sectors of major activities:
 Planning: Determination of objectives, alternatives and constraints.
 Risk analysis: analyze alternatives and attempts to identify and resolve the
risks involved.
 Development: Product development and testing product.
 Assessment: Customer evaluation.
An important feature of the spiral model is that each phase is completed with a
review by the people concerned with the project designers and programmers. This
review consists of a review of all the products developed up to that point and
includes the plans for the next cycle. These plans may include a partition of the
product in smaller portions for development or components that are implemented
by individual groups or persons, if the plan for the development fails, then the
spiral is terminated. Otherwise with the initiation of new or modified software.
The advantage of this model is the wide range of option to accommodate the good
features of other life cycle models. It become equivalent to another life cycle
model in appropriate situations. It also incorporates software quality objectives
into software development. The risk analysis and validation steps eliminates errors
in the early phases of development.
The spiral model has some difficulties that need to be resolved before it can be a
universally applied life cycle model. These difficulties include lack of explicit
process guidance in determining objectives, constraints, alternatives; relying on
risk assessment expertise; and providing more flexibility than required for many
applications.

SUMMARY
 This deal with developing a good quality software with affordable time and
reasonable cost.
 We have to take a mature process to determine time and cost required to
produce the project.
 Software development life cycle is the key component of any
software development process. This encomprises a requirement phase,
design phase, implementation phase, test phase, installation and check out
phase, operation and maintenance phase and sometimes retirement phase.
 Here Spiral Model has been used because it includes the Risk
Management along with other phases used with other traditional
software.
 Each phase of Spiral model consists of Planning, Risk analysis,
Development, Assessment sectors.
 The problem with this model includes lack of explicit process guidance in
determining objectives, constraints, relying on risk management expertise.
 REQUIREMENT SPECIFICATION
HARDWARE: - Processor (Intel core processor above Pentium IV)
RAM (512 MB)
HARD DISK (1GB)

SOFTWARE: - WINDOWS 10

FRONT END: - VISUAL BASIC 6.0

BACK END: - MS ACCESS

 FRONT END

WHAT IS VISUAL BASIC 6.0?

Visual Basic is a generation event and integrated development environment
(IDE) from Microsoft for its COM programming model first released in 1991 and
declared legacy in 2008. Microsoft intended Visual Basic to be relatively easy to
learn and use. Visual Basic was derived from BASIC and enables the rapid
application development (RAD) of graphical user interface (GUI) applications,
access to databases using Data Access Objects,, Remote Data Objects, or ActiveX
Data Objects, and creation of ActiveX controls and objects.

The final release was version 6 in 1998 (now known simply as Visual Basic). On
April 8, 2008 Microsoft stopped supporting Visual Basic 6.0 IDE. The Microsoft
Visual Basic team still maintains compatibility for Visual Basic 6.0 applications on
Windows Vista, Windows Server 2008 including R2, Windows 7, Windows 8,
Windows 8.1, Windows Server 2012 and Windows 10 through its "It Just Works"
program. In 2014 there were tens of thousands of developers who still prefer
Visual Basic 6.0 over Visual Basic .NET. In 2014 some developers lobbied for a
new version of Visual Basic 6.0. A dialect of Visual Basic, Visual Basic for
Applications (VBA), is used as a macro or scripting language within several
Microsoft applications, including Microsoft Office.
 BACK-END

WHAT IS MS- ACCESS?

Microsoft Access is a DBMS (also known as Database Management System)

from Microsoft that combines the relational Microsoft with a graphical user
interface and software-development tools. It is a member of the Microsoft Office
suite of applications, included in the Professional and higher editions or sold
separately.

Microsoft Access stores data in its own format based on the Access Jet Database
Engine. It can also import or link directly to data stored in other applications and
databases.

Software developers and data architects can use Microsoft Access to develop
application software, and "power users" can use it to build software applications.
The Microsoft® Access Database is made up of 7 major components:
 Tables
 Relationships
 Queries
 Forms
 Reports
 Macros
SYSTEM DESIGN :
After gathering the requirements and determining that the proposed system is
technically feasible, we will move further towards the designing issues. Here the
main goal is to transform the requirements specification into a structure that is
suitable for implementation in some programming language. Here we determine
the individual’s constraints to be used further as per requirements. These
constraints are than mapped into Data Flow diagrams (DFD) & Entity Relationship
Diagram(ER-Diagram).
Data Flow Diagram:-
A data-flow diagram (DFD) is a graphical representation of the "flow" of data
through an information system. DFDs can also be used for the visualization of data
processing (structured design).
Data flow diagrams (DFDs) are the method of choice over technical descriptions
for three principal reasons.

(1) DFDs are easier to understand by technical and nontechnical audiences.

(2) DFDs can provide a high level system overview, complete
with boundaries and connections to other systems.
(3) DFDs can provide a detailed representation of system components.

DFDs help system designers and others during initial analysis stages visualize a
current system or one that may be necessary to meet new requirements. Systems
analysts prefer working with DFDs, particularly when they require a clear
understanding of the boundary between existing systems and postulated systems.
DFDs represent the following:

1. External devices sending and receiving data

2. Processes that change that data
3. Data flows themselves
4. Data storage locations

0 Level DFD: A level 0 DFD, also called a fundamental system model or

context diagram represents the entire software element as a single bubble with
input and output data indicated by incoming and outgoing arrows, respectively.

 A data flow diagram shows the logical flows of data through a

transaction processing system of an organization.
  They are primarily used in the systems development process as a tool
for analyzing an existing system.

1 Level DFD: This level of DFD provides more detailed structure. It provides a
detailed view of requirements and flow of data from 1 bubble to another.

Data Flow:-
 Data move in specific direction from an origin to a destination in the form
of a document.

Process:-
 Procedures or devices that use or transform data.

Source or Destination of Data:-

 Source or Destination of data, which may be people, organization or other
entities, interact with the system but are outside its boundary.

Data Store:-

 A Data Store referenced by a process in the system.

Context Diagram

O-LEVEL :-

Watch shop
USER
& management DATABASE
system

ENTITY RELATIONSHIP DIAGRAM:-

The entity relationship model is a high level data model. It is based on

a perception of a real world that consists of a collection of basic objects, called
entities, and of relationship among these objects. It was developed to facilitate
database design by allowing specification of an enterprise schema, which represent
the overall logical structure of a database.

Entities-relationship analysis uses three major abstractions to

describe data.
1) Entity: An entity is an object that has its existence in the real world. It includes
all those “things” about which data is collected. An entity may be a tangible object
such as a student, a place or a part. It may also be non-tangible such as an event, a
job title or a customer account. For example, if we say that a customer buys goods,
it means customer and goods are entities.
 Diagrammatically, entities are represented in rectangles

2) Attributes: Attributes are units that describe the characteristics or properties of

entities. In a database, entities are represented by tables and attributes by columns.
For example, a customer entity might have numerous attributes such as code, name
and addresses. Similarly, the goods entity may have attributes like code and price.
They are drawn in elliptical shapes along with the entity rectangles.

3) Relationship:- Relationships illustrate how two entities share information

in the database structure.

 The diagram documents the entities and relationship involved in the

employee information and payroll system.

 It depicts the fundamental relations like recording personnel information,

paying salary and getting a loan.

 The E-R Diagram for a Employee Payroll system can

An Entity Set: It is a set of entities of the same type that share the same properties,
or attributes. The set of all persons who are customers at a given bank, example,
can be defined as the entity set customer.
ER ENTITY RELATIONSHIP DIAGRAM OF WATCH STORE MANAGEMENT SYSTEM
DATABASE:-

Data base is used to store the relevant information of the individuals. A database is
a collection of rows and columns in which rows indicates the tuple and column
indicates the domain of table.
In database management system, a file that defines the basic organization of
a database A data dictionary contains a list of all files in the database, the number
of records in each file, and the names and types of each fields. Most database
management systems keep the data dictionary hidden from users to prevent them
from accidentally destroying its contents.
Data Dictionary
A metadata or data dictionary is the data about the data .It is the self-
describing nature of the database that provides program-data independence.
It is also called as the SYSTEM CATALOG. It holds the following
information about each data element in the databases, it normally include :

 Name
 Type
 Range of values
 Source
 Access authorization
 Indicates which application programs use the data so that, when a
change in a data structure is contemplated , a list of the affected
programs can be generated.

Data dictionary is used to actually control the database operation,

data integrity and accuracy. Metadata is used by developers to
develop the programs, queries, controls and procedures to manage the
data. Metadata is available to database administrators (DBAs),
designers and authorized user as on-line system documentation. This
improves the control of database administrator (DBAs) over the
information system and the user’s understanding and use of the
system. There are two types of data dictionary:-
 ACTIVE
 PASSIVE
DATA REPORT

Report data can come from multiple sources of data in your organization. Your
first step in designing a report is to create data sources and datasets that represent
the underlying report data. Each data source includes data connection information.
Each dataset includes a query command that defines the set of fields to use as data
from a data source. To visualize data from each dataset, add a data region, such as
a table, matrix, chart, or map. When the report is processed, the queries run on the
data source, and each data region expands as needed to display the query results for
the dataset.

Terms
 Data connection. Also known as a data source. A data connection includes
a name and connection properties that are dependent on the connection type.
By design, a data connection does not include credentials. A data connection
does not specify which data to retrieve from the external data source. To do
that, you specify a query when you create a dataset.
 Data source definition. A file that contains the XML representation of a
report data source. When a report is published, its data sources are saved on
the report server or SharePoint site as data source definitions, independently
from the report definition. For example, a report server administrator might
update the connection string or credentials. On a native report server, the file
type is .rds. On a SharePoint site, the file type is .rsds.
 Connection string. A connection string is a string version of the connection
properties that are needed to connect to a data source. Connection properties
differ based on data connection type. For examples, see Data Connections,
Data Sources, and Connection Strings in Report Builder.
 Shared data source. A data source that is available on a report server or
SharePoint site to be used by multiple reports.
 Embedded data source. Also known as a report-specific data source. A
data source that is defined in a report and used only by that report.
FORMS
LOGIN FORM
PROGRESS BAR
WELCOME FORM
MDI FORM
WATCH DETAIL
CUSTOMER DETAIL
EMPLOYEE DETAIL
SALES DETAIL
PURCHASE DETAIL
STOCK DETAIL
BILL DETAIL
CONTACT US
EXIT FORM
DATA REPORT
WATCH DETAIL
CUSTOMER DETAIL
SALES DETAIL
EMPLOYEE DETAIL
PURCHASE DETAIL
STOCK DETAIL
BILLS DETAIL
CONTACT US
CODING
LOGIN FORM
Private Sub Command1_Click()
If Text1.Text = "LAXMI" Or Text1.Text = "laxmi" Then
If Text2.Text = 12345 Then
Form2.Show
Me.Hide
Else
MsgBox "WRONG PASWARD", vbInformation, "massage"
End If
Else
MsgBox "WRONG USERNAME", vbInformation, "massage"
End If
Private Sub Command2_Click()
Text1.Text = " "
Text2.Text = " "
End Sub End Sub
Private Sub Command3_Click()
End
End Su
WELCOME FORM
Private Sub Timer1_Timer()
PB1.Value = PB1.Value + 1
If PB1.Value >= 40 And PB1.Value <= 60 Then
Label1.Caption = " Project is loading......" & PB1.Value & "%"
ElseIf PB1.Value >= 80 And PB1.Value < 100 Then
Label1.Caption = "Database is connecting....." & PB1.Value &
"%"
ElseIf PB1.Value >= 100 Then
Form3.Show
Unload Me
Else
Label1.Caption = PB1.Value & "%"
End If
End Sub
MDI FORMS
Private Sub b_Click(Index As Integer)
Form5.Show
End Sub

Private Sub bi_Click()

Datareort7.Show
End Sub

Private Sub c_Click(Index As Integer)

Form6.Show
End Sub

Private Sub cd_Click()

DataReport2.Show
End Sub
Private Sub co_Click()
DataReport9.Show
End Sub

Private Sub d_Click(Index As Integer)

Form7.Show
End Sub

Private Sub e_Click(Index As Integer)

Form8.Show
End Sub

Private Sub em_Click()

DataReport3.Show
End Sub

Private Sub f_Click(Index As Integer)

Forms9.Show
End Sub
Private Sub g_Click(Index As Integer)
Form10.Show
End Sub

Private Sub h_Click(Index As Integer)

Form11.Show
End Sub

Private Sub j_Click(Index As Integer)

Form13.Show
End Sub

Private Sub pu_Click()

DataReport5.Show
End Sub

Private Sub r_Click(Index As Integer)

End Sub
Private Sub sa_Click
()
DataReport4.Show
End Sub

WATCH DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub
Private Sub Command4_Click ()
Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub

CUSTOMER DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub

EMPLYEE DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub
Private Sub Command3_Click ()
Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub

SALES DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub

PURCHASE DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub
Private Sub Command2_Click ()
Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub

STOCK DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub
BILLS DETAIL
Private Sub Command1_Click ()
Adodc1.Recordset.AddNew
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub

Private Sub Command5_Click ()

MDIForm1.Show
End Sub

CONTACT US
Private Sub Command5_Click ()
MDIForm1.Show
End Sub

Private Sub Command2_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command3_Click ()

Adodc1.Recordset.Update
End Sub

Private Sub Command4_Click ()

Adodc1.Recordset.Delete
End Sub
Private Sub Command5_Click ()
MDIForm1.Show
End Sub

EXIT FORM
Private Sub Text1_Change ()
End
End Sub
 TESTING

Importance of software Testing

The importance of software testing and its impact on software cannot be
underestimated. Software testing is a fundamental component of software quality
assurance and represents a review of specification, design and coding. The greater
visibility of software system and the code associated with software failure are
motivating factors for planning, through testing. It is not uncommon for a software
organization to spent 40% of its efforts on testing.
Software Testing Fundamentals
During testing the software engineering produces a series of test cases that are used
to “rip apart” the software they have produced. Testing is the one step in the
software process that can be seen by the developer as destructive instead of
constructive. Software engineers are typically constructive people and testing
requires them to overcome preconceived concepts of correctness and deal with
conflicts when errors are identified.
System Testing
System testing is the expensive and time-consuming process. There are two
strategies for testing software that we use for testing our system: Code Testing and
Specification Testing. In Code testing, we developed those cases to execute every
instructions and path in the program. In specification testing, we examined the
program specification and then wrote test data to determine how the program
operates under specified condition..
Client Acceptance
Needs Testing

Requirements System
Testing

Design Integration
Testing

Code UnitTesting
 We have tested each module separately i.e. have completed unit testing first
and system testing was done after combining /linking all different Modules with
different menus and thorough testing was done. Testing is a very important part
of SDLC and takes approximately 50%of the time.

Once the system is a live one, Maintenance phase is important. Service after
sale is a must and users/ clients must be helped after the system is implemented.
If he/she faces any problem in using the system, one or two trained persons
from developer’s side can be deputed at the client’s site, so as to avoid any
problem and if any problem occurs immediate solution may be provided.

OVERVIEW OF TESTING
Testing: Testing involves executing the program (or part of it) using sample
data and inferring from the output whether the software performs correctly or
not. This can be done either during module development (unit testing) or when
several modules are combined (system testing).

Defect Testing: Defect testing is testing for situation where the program does
not meet its fictional specification. Performance testing tests a system's
performance or reliability under realistic loads. This may go some way to
ensuring that the program meets its non-functional requirements.

Debugging: Debugging is a cycle of detection, location, repair and test.

Debugging is a hypothesis testing process. When a bug is detected, the tester
must form a hypothesis about the cause and location of the bug. Further
examination of the execution of the program (possible including many returns
of it) will usually take place to confirm the hypothesis. If the hypothesis is
demonstrated to be incorrect, a new hypothesis must be formed. Debugging
tools that show the state of the program are useful for this, but inserting print
statements is often the only approach. Experienced debuggers use their
knowledge of common and/or obscure bugs to facilitate the hypothesis testing
process. After fixing a bug, the system must be reset to ensure that the fix has
worked and that no other bugs have been introduced. This is called regression
testing. In principle, all tests should be performed again but this is often too
expensive to do.
 TEST PLANNING:
Testing needs to be planned to be cost and time effective. Planning is setting out
standards for tests. Test plans set out the context in which individual engineers
can place their own work. Typical test plan contains
Overview of testing process
>Requirements trace ability (to ensure that all requirements are tested)
>List of item to be tested
>Schedule
>Recording procedures so that test results can be audited
>Hardware and software requirement.
Black Box Testing
Black box testing relates to the tests that are performed at the software interface.
Although they are designed identify errors, black box tests are used to demonstrate
that software function are operational; that inputs are correctly accepted and the
output is correctly produced. A black box test considers elements of the system
with little interest in the internal logical arrangement of the software. White box
testing of the testing involve closer examination of procedural detail. Logical paths
through the software are considered by providing test cases that exercise particular
sets of conditions and / or loops. The status of the system can be identified at
diverse points to establish if the expected status matches the actual status.
Black box testing tries to find errors in the following categories:
1. Incorrect or missing functions,
2. Interface errors,
3. Errors in data structures or external database access,
4. Performance errors, and
5. Initialization and termination errors.
White Box Testing
White box testing is a test case design approach that Users the control architecture
of the procedural design to produce test cases. Using white box test approaches, the
software engineering can produce test cases

1. Guarantee that all independent paths in a module have been exercised at

least once.

2. Exercise all logical decisions.

3. Execute all loops at their boundaries and in their operational bounds.

Exercise internal data structures to maintain their validity.
 TESTING PROCESS
Best testing process is to test each subsystem separately, as we have done in my
project. Best done during implementation. Best done after small sub-steps of the
implementation rather than large chunks. Once each lowest level unit has been
tested, units are combined with related units and retested in combination. This
proceeds hierarchically bottom-up until the entire system is tested as a whole.
Typical levels of testing:

> Unit -procedure, function, method

> Module -package, abstract data type, class

Sub-system - collection of related modules, cluster of classes, method-message

paths

> Acceptance testing - whole system with real data (involve customer, user,
etc)Alpha testing is acceptance testing with a single client (common for bespoke
systems).

Beta testing involves distributing system to potential customers to use and provide
feedback. In, this project, Beta testing has been followed. This exposes system to
situations and errors that might not be anticipated by us.
SYSTEM IMPLEMENTATION

Implementation denotes the process of converting a new or a

revised
System design in to an operational one. There are three types of
implementation.Implementation of a computer system to replace a manual
system.

•Implementation of a new computer system to replace an existing one

•Implementation of a modified application to replace an existing one

In this project impose the first method is imposed where one can replace
a manual system with that of a computerized one. This system is found to be
satisfactory running under the real environment. The system is tested for
its functionality and appreciated for its efficiency,flexibility, and accuracy
and user friendliness.

The system has been tested with sample data and adequate corrections
were made as per user requirements. The user has very little chances of making
data entry errors. Since enough validation checks and validation error messages
are provided in the system. The end user even with minimum amount of
computer knowledge will be able to key in the data and understand the error
messages. All reports have been found satisfy their requirements.
SCOPE FOR FUTURE ENHANCEMENT

This system is very flexible so the maintenance and future

enhancements based on the changing environment and requirements can be
incorporate easily. Any changes that are likely cause system failures are
presented with security measures.

In order to make modifications effectively, there should be good

communication between customer and the organization. Thus valuable
suggestion supplied can be included in the system .Since Visual Basic
and Access are flexible tools, we can easily incorporate any modular program
into the application. Thus even after the development phase, design and
development of new application and their integration with the existing one
can be carried out with least effort.

Addition reports can be added with the system to show the growth of
the particular field or for the whole company.
CONCLUSION

This project entitled Watch Shop Management System mainly contributes to

provide information about the activities of a Show Room. This project
provides easy retrieval of information about the Products available. The
system helps the user to change his/her requirements in future. Thus it
enables us to carry out the process in an effective way. This system also provides
a user-friendly operating environment and also provides the platform to serve the
needs of emerging information technology trends and needs.
BIBLIOGRAPHY

Books Referred

•Curtis L. Smith, Database Programming with Visual Basic 6.0, Sam’s Publication,
1998, I edition

•Gary cornell, Visual Basic 6.0 from the ground up, TATA MCGRAW Hill
Publication, 1991, I edition.

•Ron Mansfield, Working with Access, TATA McGraw Hill Publication, 1997 I
edition Websites Referred

www.titanworld.com/
www.britishwatchcompany.com/
www.rado.com/en/watch-shop.html
www.thelittlewatchshop.com/