Académique Documents
Professionnel Documents
Culture Documents
1
OBJECTIVES AND SCOPE OF PROJECT
Objective:-
The main objective of the project is to help the project is to help the ongoing
user help to attain an easy way to navigate the customer’s details and solve
the customer’s problems.
It is basically a very instant processing system by which customer can get
the book in the right condition.
The manager of the book store also finds it sufficient enough to view the
details of the sales, servicing and well organized way to employ the staff that
are included in the book store staff.
Scope:-
2
THEORETICAL BACKGROUND OF PROJECT:-
3
DEFINATION OF PROBLEM
3. Problem of timeliness: In the current system the reports and output produced is
mostly late and in most of the cases it is useless because it is not on time.
5. Problem of Economy: The current system is very costly. We have to spend lots
of money to keep the system up and going, but still not get the desired results.
4
SYSTEM ANALYSIS AND DESIGN
SYSTEM ANALYSIS
Existing system
5
Limitation in Existing system
Proposed system
6
SOFTWARE DESIGN
Design considerations
There are many aspects to consider in the design of a piece of software. The
importance of each should reflect the goals the software is trying to achieve. Some
of these aspects are:
Compatibility -The software is able to operate with other products that are
designed for interoperability with another product. For example, a piece of
software may be backward-compatible with an older version of itself.
Extensibility – New capabilities can be added to the software without major
changes to the underlying architecture.
Fault-tolerance –The software is resistant to and able to recover from
component failure.
Maintainability –The software can be restored to a specified condition
within a specified period of time. For example, antivirus software may
include the ability to periodically receive virus definition updates in order to
maintain the software’s effectiveness.
Modularity – The resulting software comprises well defined, independent
components. That leads to better maintainability. The components could be
then implemented and tested in isolation before being integrated to form a
desired software system. This allows division of work in a software
development project.
Packaging- Printed material such as the box and manuals should match the
style designated for the target market and should enhance usability. All
compatibility information should be visible on the outside of the package.
All components required for use should be included in the package or
specified as a requirement on the outside of the package.
Reliability- The software is able to perform a required function under stated
conditions for a specified period of time.
Reusability- The modular components designed should capture the essence
of the functionality expected out of them and no more or less. This single-
minded purpose renders the components reusable wherever there are similar
needs in other designs.
7
Robustness- The software is able to operate under stress or tolerate
unpredictable or invalid input. For example, it can be designed with
resilience to low memory conditions.
Security- The software is able to withstand hostile acts and influences.
Usability- The software user interface must be intuitive (and often
aesthetically pleasing) to its target user/audience. In many cases, online help
should be included and also carefully designed.
Modeling language:-
8
Purpose: The main purpose for preparing this document is to give a general
insight into the analysis and requirements of the existing system or situation and
for determining the operating characteristics of the system.
Scope: This document plays a vital role in the development life cycle (SDLC) as it
describes the complete requirement of the system. It is meant for use by the
developers and will be the basic during testing phase. Any changes made to the
requirement in the future will have to go through formal change approval process.
Functional Requirements:
OUTPUT DESIGN
Output Definition
9
INPUT DESIGN
Input design is a part of overall system design. The main objective during the input
designing is as given below:
To produce a cost-effective method of input.
To achieve the highest possible level of accuracy.
To ensure that the input is acceptable and understood by the
user.
INPUT STAGES:
Data recording
Data transcription
Data conversion
Data verification
Data control
Data transmission
Data validation
Data correction
INPUT TYPES:
Controlled Redundancy
Data independence
Accurate and integrating
More information at low cost
Recovery from failure
Privacy and security
Performance
Ease of learning and use
Performance requirements:
The requirement specification for any system can be broadly stated as given
below:
The requirement specification for any system can be broadly stated as given below:
11
The system should be accurate
The system should be better then the existing system
The existing system is completely dependent on the staff to perform all the
duties.
12
DETAILS OF HARDWARE AND SOFTWARE REQUIREMENT
1. SOFTWARE
2. HARDWARE
13
SYSTEM TESTING
Testing: - According to IEEE,” testing means the process of analyzing an s/w item
to detect the difference between existing and required condition and to evaluate the
feature of the s/w item”.
White Box Testing: - In this testing technique the internal structure of s/w
component in tested. White box testing is also known as glass box testing. It is test
case, design method that uses the control structure of the procedural design test
cases.
Black Box Testing: - In black box testing, the structure of the program is not
considered. Text case is decided on the basis of requirement or specification of the
program or modeling and the internals of the modules or the program are not
considered for selection of cases.
14
DATA FLOW DIAGRAM (DFD)
15
Data Flow Diagram:-
The project dictionary contains an entry for each DFD developed during
analysis. Thus there is a context diagram. A top level DFD and detailed diagrams
for all top level functions and their components. Each DFD has a unique number
and can be reference by that number.
DFD is a graphics representation of system that shows data flow to, frame
and within the system, processing functions that change data in some manner and
the storage this data.
DFD are nothing but more than network of a related system functions
(processing of data) that indicate from where information (data) is received
(inputs) and to where it is send (outputs). It is also called as bubble charges.
DFD’s are more detailed than content diagram. DFD’s are used to despite
specifics data flows (movement of inform) from both the physical view point (How
it is dine) and the logical view point (what is done).
DFD use a number of symbols to represent system. Most data flow
modeling methods use four kinds of symbols these symbols are used to represent
four kinds of system components.
1-processes
2-data stores
3-data flows
4-external entities
16
0 LEVEL DFD:-
PROVISION STORE
MANAGEMENT
CUSTOMER INFORMATION
17
1 LEVEL DATA FLOW DIAGRAM:-
LOGIN
PROVISION STORE
MANAGEMENT
MDI FORM
DATABASE DATABASE
DATABASE DATABASE
18
ENTITY RELATIONSHIP DIAGRAM (E-R DIAGRAM
CUSTOMER
NAME ADDRESS
BILL NO. BILL NO. DATE
DATE
S.NO
TOTAL S.NO
QTY AMOUNT QTY
RATE PARTICULER
PARTICULER
AMOUNT PRODUCT
ADDRESS
DATE
DELEAR NAME
S.NO.
TOTAL
MOBILE NO.
AMOUNT
ADDRESS
PARTICULER
QTY AMOUNT
RATE
19
DATABASE DESIGN
20
SALE TABLE
21
PURCHASE TABLE
22
STOCK TABLE
23
CUSTOMER INFORMATION TABLE
24
INPUT/OUTPUT SCREEN
25
LOGIN FORM
26
SPLASH FORM
MDI FORM
27
28
SALES FORM
29
PURCHASE FORM
30
STOCK FORM
31
CUSTOMER INFO FORM
32
CODING
LOGIN FORM
33
Private Sub Command1_Click()
If Text1.Text = "ishwar" And Text2.Text = "2019" Then
Unload Me
Form2.Show
Else
MsgBox "Invalid password try again!"
Text1.Text = " "
Text2.Text = " "
Text1.SetFocus
End If
End Sub
SPLASH FORM
34
MDI FORM
35
SALE FORM
36
Private Sub Command3_Click()
rs!billno = Text1.Text
rs!customername = Text2.Text
rs!address = Text3.Text
rs!Date = Text4.Text
rs!sno = Text5.Text
rs!particuler = Text6.Text
rs!qty = Text7.Text
rs!Rate = Text8.Text
rs!amount = Text9.Text
rs!totalamount = Text10.Text
End Sub
37
MsgBox "record not found"
End If
End Sub
38
Text2.Text = rs!customername
Text3.Text = rs!address
Text4.Text = rs!Date
Text5.Text = rs!sno
Text6.Text = rs!particuler
Text7.Text = rs!qty
Text8.Text = rs!Rate
Text9.Text = rs!amount
Text10.Text = rs!totalamount
End Sub
PURCHASE FORM
Dim cm As New Connection
Dim rs As New Recordset
Dim rs1 As New Recordset
39
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(6) = Text7.Text
rs(7) = Text8.Text
rs(8) = Text9.Text
rs(9) = Text10.Text
rs(10) = tetx11.Text
End Sub
STOCK FORM
Dim cm As New Connection
42
Dim rs As New Recordset
Dim rs1 As New Recordset
45
Dim rs1 As New Recordset
47
Private Sub Command9_Click()
rs.MoveNext
If rs.EOF Then
rs.MoveFirst
End If
showdata
End Sub
48
DATA REPORT
SALE REPORT
49
50
PURCHASE REPORT
51
STOCK REPORT
52
CUSTOMER INFO REPORT
53
SALE PRINT REPORT
54
55
PURCHASE PRINT REPORT
56
STOCK PRINT REPORT
57
CUSTOMER INFO PRINT REPORT
58
CONCLUSION
59
REFERENCES
The references contains reference to all the documents that were referred for the
creation and completion of the project. It contains the Names of the referred
software engineering documents, visual basic technical and stadards.
61