Book Shop Project
Book Shop Project
Book Shop Project
Punjab Technical University (PTU) was established in the Year 1997 under the
Punjab Technical University Act, 1996(Punjab Act No. 1 of 1997) to provide for
the establishment and incorporation of a University for the advancement of
technical education and developement thereof in the State of Punjab and for
matters connected therewith. In pursuance of this Act, the University started its
journey with 09 engineering colleges and few management colleges affiliated to it.
Since then, the University has come a long way and during this Academic Session
2013-14, the University has affiliated 100+ engineering Colleges, 139
Management and Computer Application courses, 37 institutions imparting
Pharmacy education, 11 colleges imparting Hotel Management education, 06
Colleges providing Architecture Education and 21 Regional Centre for M.Tech and
Ph.D in different branches of Engineering and Management and 01 Regional
Centre for M.Pharmacy. More then 2014 Learning Centers of PTU are providing
professional education through Distance Learning all over the Country and abroad.
All the time of the University , the students were doing their engineering courses
from the University of other states. PTU achived that height & glory because of
which it became sucessfull in winning the faith of the students. At present, after 15
year of its existance, PTU is providing education to approximately 5 lac students in
the fields of Engineering, Management, Architecture and Pharmacy. This number
includeds 50 percent students form the states other than Punjab.
We, at Punjab Technical University, are propelled by the vision and wisdom of our
leaders and are continously striving to discharge our duties for the overall
improvement of quality of education and to make sure that the courses we offer
remain relevant to our society and usefull to our students in the globalized work
environment.
1
PROFILE OF PROBLEM
Existing System is not very efficient language and time consuming. It is not very
easy to understand. So there are some problem and drawback in the existing
System which is given below:-
NonSharing: - The different users in the shop cannot share the data
simultaneously.
2
Security: - Less security of the current system.
Lot of Paper Work: - It adds the volume of paper and file work.
3
EXISTING SYSTEM
In the previous days, the whole working is done in a Medical Store using manual
ways. But due to the change in technology and time, every person needs an easy
and efficient way for doing work. The employees having face various problems
with the existing system i.e. Totally Paperwork
There is not a proper bridge between the employees of the shop as well as
between the customer and staff that why each and every notice or information need
lot of time along with lot of expense to transferred. The existing techniques are
Telephone, Letters, Notice, Fax etc. Another way was that the persons have to talk
face to face by meeting to each other. It is time consuming because for this, it
becomes necessary that both persons have time to meet and talk to each other for
sharing information or better communication. Sometimes it becomes difficult task.
If any person wants to gain information about any department then all the
ways are quite expensive along with time consuming. Sometimes the message
becomes late to be received due to manual ways. All the records as well as
information about any matter will be registered properly into the registers. That
task was quite hard, because it is not an easy task to manage the information for
longer time without redundancy. There was not any way to send common message
to whole organization with different department at a time. It was impossible. There
was a lot of work load on the employee. The existing system was that all the
persons do their work personally without the help of any software package. So
sometimes transfer of information needs expensive stationary. The maintenance is
also very difficult.
4
Some pitfalls of existing system is given below:
Huge paperwork
Time Consuming
Data Redundancy
Data Inconsistency
Security Problem
Reduced Speed
Low Performance
5
PROBLEM ANALYSIS
The basis aim of problem analysis is to obtain a clear understanding of the needs of
customers and the users, what exactly is desired from the software. Analysis leads
to the actual specification. In this section we will focus on the analysis.
Specification is discussed in the next section. People performing the analysis are
also responsible for specification the requirements.
Analysis involves interviewing the customer and end user. These people and the
existing documents about the current mode of operation are the basic source of
information for the analysts. The purpose of Book Shop Management systems is to
make more productive use for manage the Vehicles. Generally the main component
of such a system is a suite of Book Shop Management software that handles access
control and system security. Book Shop management software enables shop owner
to perform tasks more effectively and efficiently, gathers usage data to produce
reports that can be used to inform planning decisions, manages software best
access for users, and provides security by keeping dealer detail. Access control
may include access to getting information about Management of Books. Reports
may contain information subject to dealer detail.
We have create a Software to solve problem to save record about all customer
Vehicles we have decide to create following form in our project:-
Add Employee:- In this form when a new Employee add in this form.
6
Employee Detail: - This form are show the detail of employees
Add Books to stock: - These form are used to add books in books stock.
Find and update - When an any book is add in stock with wrong
information then we can find it and update it with right information.
Find and Delete:-This form can be used to delete any book from the
stock.
7
INFORMAL APPROACH
The informal approach to analysis is one where no defined methodology is used
like in any approach; the information about the music System is obtained by
interaction with the client, end user, questionnaire, study of existing documents,
brainstorming etc. in this approach no formal model is built of the System. The
problem and the System model are essential built in the minds of the analysts and
are directly translated from the minds of the analysts to the SRS.
Frequently, in such an approach, The analyst will have a series of meeting with the
clients and end user will explain to the analyst about their environment and their
needs as they perceive them any documents describing the work or the
organization may be given, along with outputs of the existing methods of
performing the task. In these early meeting, the analyst is basically the listener,
absorbing the information provided. Once the analyst understand the system to
some extent, the some extent, next few meeting to seek clarifications of the parts
he does not understand. Then in the final meeting, the analyst essentially explain to
the client what he understand the system should do and uses the meetings as a
means of verifying if what he proposes the system should do is indeed consistent
with the objective of the client. An initial draft of the SRS may be used in the final
meetings.
8
STRUCTURED ANALYSIS
9
PRODUCT DEFINITION
Regarding this goal aspect of our course, we tried to find some good problems,
which we could develop with much effort so that we could gain, as much from our
course that may be milestone in our future professional life. In developing the
system we came in contact with many persons related with this field. This
experience which we have acquired while developing this system will prove to be a
backbone in our future life.
Using this software we can process order easily. Quick decision is taken using
reports which are being generated with the help of this software. It also maintains
records for inventory.
10
FEASIBILITY ANALYSIS
1. What are the user's demonstrable needs and how does a candidate
system meet them?
11
THERE ARE MAJOR CHARACTERSTICS:-
1. Economic feasibility
2. Technical feasibility
3. Behavioral feasibility
ECONOMIC FEASIBILITY:
Economic analysis is the most frequently used method for evaluating the
effectiveness of a candidate system. A procedure of cost/benefit analysis is
applied to determine the savings and benefits that are expected from the
candidate system and then compare them with the costs. If benefits outweigh
the costs, then the decision is made to design, and implement the system.
Otherwise, further justification or alterations in the propose system will have
to be made if it is to have a chance of being approved. This is an ongoing
effort that improves in accuracy at each phase of the system life cycle.
SOCIAL FEASIBILITY:
12
conducting business. When we explained our system to users, they gave a
good response.
BEHAVIORAL FEASIBILITY:
Points that the user staff raised against the new system: -
3. Change in job status, and may be demotion if found not qualified for the job.
6. Difficult and time consuming requires if system failure occurs during the
working hours.
7. Loss of time and working hours if the system is not repaired on the time.
The user staff that had to directly work on the new system gave all the
limitation or the apprehensions that are listed above .they feared that the new
system would result in the demotions or they will be out of their jobs. They
may not be computer literate they said that in order to retain their jobs they
13
would have to undertake computer training at the private institute. Which is
very expensive and difficult at their personal cost?
TECHNICAL FEASIBILITY:
As the user know that the existing system that is in the use at the users
work place at the manual. All the operations that are being done on the data
are manual. This system is working well but it resulting in huge loss. All the
14
time loss and money lost can be put to various other uses, if all the time lost
can be recovered. The new system can be designed in such a way that it
retains the basic structure of the users manual system that is in use at the
moment, because then it would not be the difficult for the user and user staff
to acquaint them with the new system.
The major and basic advantages of the new system that it would be greatly
reduce the load on the employees of Agency. They would be able to do same
amount of work in less amount of time. The new system should be design in
such a way that is able to hold a large amount of data. The transfer of the
data from one place to other place would be quite easy. The new system
would be very interactive in nature as compared to the existing one.
15
PROJECT PLAN
The project goal is to remove the deficiencies of the present system such as:- In
accuracy, instance in availability and in adequacy of the information as its being
excessively costly in terms of time, money and man power and unsatisfactory
provision of information. Computerized reports are quicker and cheaper than
current manual of preparations. The goal is this project is to design and implements
the proposed solution that is developed and integrated computerized system that
would generate speedy. Accurate and adequate reports at the time of need, so my
project is based on Book Shop Management.
Planning may be the most important management activity. Without a proper plan,
no real monitoring or controlling of the project is possible. The basic goal of
planning is to look into the future, identify the activities that need to be done to
complete the project successfully, and plan the scheduling and resource allocation
for these activities. The input to the planning activity is the requirements
specification. The output of this phase is the project plan:-
1) Cost estimation
2) Schedule and milestones
3) Personnel plan
4) Software quality assurance plans
5) Configuration management plans
6) Project monitoring plans
7) Risk management
16
SOFTWARE REQUIREMENT ANALYSIS:-
DEFINITION OF REQUIREMENT:-
Requirements of the proposed are the capabilities that the system, which is yet to
be developed, should have. The requirements phase translates the ideas in the mind
of the clients (the input), into a formal document (the output of the requirements
phase).Thus, the output of the phase is a set of formally specified requirements.
Generally, the SRS is a document that completely describes what the proposed
software should do without describing how the software will do it.
17
REQUIREMENTS COVER: -
1. General Description
2. Specific requirements
General Description
Describe the general factors that affect the product and its requirements. This
section does not state specific requirements. Instead, it provides a background for
those requirements, which are defined in previous section, and makes them easier
to understand. In a sense, this section tells the requirements in plain English for the
consumption of the customer. For eg:-
Specific requirements
A computer with latest technology.
Visual basic software.
Printer for reports printing.
Periodic care of hardware.
18
Air conditioned room for well working of pc.
It also requires ms-access as back-end.
System requirement
19
DATABASE DESIGN
20
Identify the relationship between the objects.
Main motive in the database design is to manage the share ability of database.
Good database design must be satisfied current and future application needed for
organization. Create to unanticipated user requirement are expandable to modify.
21
Database Design (Tables in MS-Access)
Login Table
Employee Table
22
Billing Table
23
Form Design
Sign Up Form
24
Log In Form
25
Add Employee
26
Employee Detail
27
Remove Employee
28
Add Books
30
31
Billing
Change Password
32
Delete User
33
MDI Form
34
TESTING
Introduction
35
Software testing is a process which is used to identify the correctness,
completeness and quality of software. IEEE defines testing as the process of
exercising or evaluating a system by manual or automated means to verify
that it satisfy specified requirements or to identify differences between
expected and actual results.
Software testing is often used in association with terms Verification and
Validation. Various advantages associated with testing are listed below:-
Types of Testing:-
Functional Testing
Structural Testing
Functional Testing
Functional testing is also called black box testing, because we see the
Program as a black box that is, we ignore how it is being written
In contrast to structural or white-box testing, where the program is the base.
36
Tests based on spec
Test covers as much specified behavior as possible
Functional testing checks the functional requirements and examines the input and
output data of requirements. The functionality is determined by observing the
outputs to corresponding inputs.
Why Functional testing?
Events
Output
Inputs
Structural Testing
37
perspective of the system, as well as programming skills, are used to design test
cases. The tester chooses inputs to exercise paths through the code and determine
the appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-
circuit testing (ICT).
While white-box testing can be applied at the unit, integration and system levels of
the software testing process, it is usually done at the unit level. It can test paths
within a unit, paths between units during integration, and between subsystems
during a systemlevel test. Though this method of test design can uncover many
errors or problems, it might not detect unimplemented parts of the specification or
missing requirements.
Branch testing
Path testing
Statement Coverage
Decision Coverage
IMPLEMENTATION
Implementation of Project
38
Implementation is the stage where all the planned activities are put into action.
Before the implementation of a project, the implementers should identify their
strength and weaknesses (internal forces), opportunities and threats (external
forces).
The strength and opportunities are positive forces that should be exploited to
efficiently implement a project. The weaknesses and threats are hindrances that can
hamper project implementation. The implementers should ensure that they devise
means.
Monitoring is important at this implementation phase to ensure that the project is
implemented as per the schedule. This is a continuous process that should be put in
As such; the monitoring activities should appear on the work plan and should
involve all stake holders. If activities are not going on well, arrangements should
be made to identify the problem so that they can be corrected.
Monitoring is also important to ensure that activities are implemented as planned.
This helps the implementers to measure how well they are achieving their targets.
This is based on the understanding that the process through which a project is
implemented has a lot of effect on its use, operation and maintenance.
Post-Implementation of Project
39
Within six months to one year after an initial software implementation project is
complete, there is always a need for a second project to address opportunities with
the original implementation. Always is a pretty strong word, but so far in my career
and the careers of many of my closest peers, this is always true.
SOFTWARE MAINTENANCE
40
Software maintenance in software engineering is the modification of a software
product after delivery to correct faults, to improve performance or other attributes.
[1]
The key software maintenance issues are both managerial and technical. Key
management issues are: alignment with customer priorities, staffing, which
organization does maintenance, estimating costs. Key technical issues are: limited
understanding, impact analysis, testing, and maintainability measurement.
41
PROJECT LEGACY
42
Current Status of Project
Now this time project of Book Shop Management is complete. Trough this project
user can do much work in easy way. In this project there is separate login for
admin and normal user. According to this there access is also limited. Project can
able for sale and purchase of medicines through this project. It keeps record of
each sale and purchase. It also able to keep records of stock and our suppliers.
Admin can easily generate bill through this system. Reports of medicine sale,
purchase and dealer detail can be easily generated by this system. Easy to check
the available stock. User can update information of stock, dealer and login details
with the help of this project.
USER MANUAL
43
How to Login:-
When user starts the Book Shop Management System first he needs to be login in
the software. For login click on the logins menu and then select login option.A
login window then open fill your user name and password in given fields and then
click on login button. This way you can login.
44
For checking the reports regarding add books detail then select reports option and
select any report you want to see.
Source Code
45
Sign Up Form-
s = Text2.Text
s1 = Text3.Text
If (s <> s1) Then
MsgBox "retry"
Text2.Text = ""
Text3.Text = ""
Text2.SetFocus
Else
rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs.Update
MsgBox "inserted"
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
End If
End Sub
End Sub
Log In Form-
46
Dim cn As New ADODB.Connection
MDIForm1.employee = True
MDIForm1.books = True
MDIForm1.billing = True
MDIForm1.security = True
MDIForm1.rep = True
Me.Hide
a = "1"
End If
rs.MoveNext
Loop
If a = "0" Then
MsgBox "Envaild Username and Pssword", vbOKCancel, "ERROR"
End If
Text1.Text = ""
End Sub
47
While Not rs.EOF
Combo1.AddItem rs(0)
rs.MoveNext
Wend
End Sub
Add Books
48
Option Explicit
Dim con As ADODB.Connection
Dim rs As ADODB.Recordset
End Sub
End Sub
49
Option Explicit
Dim cn As ADODB.Connection
Dim rs As ADODB.Recordset
Private Sub Command1_Click()
End Sub
End Sub
End If
End Sub
50
Private Sub Command5_Click()
rs.MoveNext
If rs.EOF = True Then
MsgBox "last record"
rs.MoveLast
Else
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
End If
End Sub
End Sub
End Sub
51
Private Sub Command9_Click()
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs(6) = Text7.Text
rs.Update
MsgBox "records updated "
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
Text7.Text = " "
End Sub
52
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub Command1_Click()
rs.MoveFirst
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
End Sub
53
rs.MoveLast
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
Text5.Text = rs(4)
Text6.Text = rs(5)
Text7.Text = rs(6)
End Sub
Private Sub Command5_Click()
rs.Delete
MsgBox "Record is deleted"
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
End Sub
54
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
rs.AddNew
rs(0) = Text1.Text
rs(1) = Text2.Text
rs(2) = Text3.Text
rs(3) = Text4.Text
rs(4) = Text5.Text
rs(5) = Text6.Text
rs.Update
MsgBox "Records are Saved"
Text1.Text = " "
Text2.Text = " "
Text3.Text = " "
Text4.Text = " "
Text5.Text = " "
Text6.Text = " "
rs.MoveNext
End If
End Sub
End Sub
Employee Detail
55
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
rs.MoveFirst
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(3)
56
Text5.Text = rs(4)
Text6.Text = rs(5)
End Sub
End Sub
57
Delete Employee
End Sub
End Sub
End Sub
58
MsgBox "last record"
rs.MoveLast
Else
Text1.Text = rs(0)
Text2.Text = rs(1)
Text3.Text = rs(2)
Text4.Text = rs(4)
Text5.Text = rs(5)
End If
End Sub
End If
End Sub
End Sub
Change Password
59
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
End Sub
60
rs.Open "Sign11", cn, adOpenDynamic, adLockOptimistic, adCmdTable
While Not rs.EOF
Combo1.AddItem rs(0)
rs.MoveNext
Wend
rs.Close
End Sub
Delete User
61
Dim cn As New ADODB.Connection
Dim rs As New ADODB.Recordset
Private Sub Command1_Click()
rs.Open
If (Combo1.Text = "") Then
MsgBox "select user"
rs.Close
Else
rs.MoveFirst
rs.Find "username='" & Combo1.List(Combo1.ListIndex) & "'"
rs.Delete
rs.Update
MsgBox " deleted"
rs.Close
End If
End Sub
62
Billing
Option Explicit
Dim cn As ADODB.Connection
Dim rs As ADODB.Recordset
Dim rs1 As ADODB.Recordset
Dim bno As Integer
End Sub
Dim up As Integer
up = Val(Text6.Text) - Val(Text12.Text)
rs(1) = up
Text6.Text = up
rs.Update
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
63
Text5.Text = ""
Text6.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""
Text12.Text = ""
Text13.Text = ""
End Sub
DataEnvironment1.Command1 (i)
DataReport1.Show
End Sub
64
rs.MoveFirst
'Text14.Text = Date
End Sub
MDI Form-
65
Private Sub addbooks_Click()
Form6.Show
End Sub
66
MDIForm1.employee = False
MDIForm1.books = False
MDIForm1.billing = False
MDIForm1.security = False
MDIForm1.rep = False
End Sub
End Sub
67
DATA REPORTS-
Report1-
68
Report2-
69
Report3-
70
Data report- 4
BIBLIOGRAPHY
71
www.google.com
www.encyclopedia.com
www.wikipedia.com
www.booksmanagementreport.com
72