Professional Documents
Culture Documents
(Autonomous)
CERTIFICATE
Date:
Finally, we would like thank each and everyone who was directly or
Indirectly involved with this project report.
Index
1. Introduction
o Company Profile
o Introduction to system
o Scope of the system
o Proposed System
2. Analysis
o Fact Finding Technique
o Feasibility Study
o Hardware & Software Requirement
3. System Design
o E-R Diagram
o Context Level Diagram
o Data Flow Diagram
o File Design
o Data Dictionary
4. Form Design (with input values)
5. Reports
6. Advantages & Limitations
7. Future Enhancement
8. Bibliography
1. Introduction
1. INTRODUCTION
● Introduction to System
● Scope of the System
● Proposed System
Introduction to System
● Customer will get category wise information about each vintage item and
all other details related to vintage item.
● This system also maintains all the details of the customer and the product
sold. Maintains all the details of the seller also.
● System handles all the bill & payment process. It maintains details of the
complaint and query given by customers.
• To make the information available to admin and employee, in just few click.
• To have a centralized control over the records of staff, customers and monitor
changes in these records
● Customer will get category wise information about each vintage item and
all other details related to vintage item.
● This system also maintains all the details of the customer and the product
sold.
● Questionnaires
● Interviews.
● Record Reviews.
● Observation
1) Questionnaires
This method is used to gather information about various issues of system from
large number of persons. It is useful to determine the overall opinion before
giving any specific direction to the system project.
2) Interview Techniques
This technique is used to gather information from top people of “Vintage Shop
Management System”. Questions were asked regarding the manual procedure
of the system. By using Interview techniques I came to know that what
exactly their requirements are? How they carry out manual procedures? What
are the major inputs and outputs to the system?
3) Record Searching
This technique helped me to know that how do they store data in their file?
Which transactions affect which types of files? What type of updates they
perform? Study of already available documents is the fastest and independent
way of gathering fact and information based on which further processes can
be welled structured.
4) Observations
This technique helped me to know the actual flow of the documents; the
persons involved in the procedures, what steps they follow. I also came to
know about the pros and cons of their manual system.
FEASIBILITY STUDY
The aims of a Feasibility study are to find out whether the system is worth
implementing and if it can be implemented, given the existing budgets and schedule
.The input to the feasibility study is a set of preliminary requirements, an outline
description of the system and how the system is intended to support business
processes.
As a part of preliminary investigation the feasibility study was carried out. The
proposed system was viewed from three aspects.
1) Social Feasibility:-
Although generally there is always resistance, initially to any change in the system,
the system is aimed at relieving the work load of the end users. The system has been
developed keeping the customer, their work culture and their previous habits in their
mind.
The system is going to help the end users to perform the maintenance of the records
and report generation with the least possible errors. Moreover the system is very
user friendly. Thus, there is no reason for the project to be socially unfeasible.
2) Operational Feasibility:-
Proposed system has been developed keeping the point of view of existing
employees. The “VINTAGE SHOP MANAGEMENT SYSTEM” already has the
staff with the required technical knowledge to operate the system.
So, the need to recruit, select and train new employees to operate the system is not
really felt. The system being highly graphically interactive, the need of highly
trained technical staff is not required. Thus the system is operationally feasible.
3) Technical Feasibility:-
The proposed system will be built using Microsoft VB 6.0 as frontend and
Microsoft Access 98 as backend which fits in the hardware configuration specified
by the organization. Thus, new system will not be cost bearing for the organization.
4) Economic Feasibility:-
Keeping in view all the other parts of feasibility, it automatically reflects the system
also seems to be economically feasible. It will reduce the organization’s hardware
and software expenses to some extent.
Hardware & Software Requirement
HARDWARE REQUIREMENTS:
SOFTWARE REQUIREMENT:
ADMIN:
BUYER:
Field Name Data type Constraints Description
b_id NUMBER Primary Key BUYER ID
b_name TEXT NOT NULL BUYER NAME
b_phno TEXT NOT NULL BUYER PHONE NUMBER
b_email TEXT NOT NULL BUYER EMAIL-ID
b_addr TEXT NOT NULL BUYER ADDRESS
BUYER RECEIPT:
Field Name Data type Constraints Description
b_id NUMBER Primary Key BUYER RECEIPT ID
buyer_id NUMBER Foreign key BUYER ID
sub_total NUMBER NOT NULL TOTAL AMT TO BE PAID
date_of_issued Date/Time NOT NULL DATE OF INVOICE CREATION
CART:
Field Name Data type Constraints Description
cart_item_id NUMBER Primary Key CART ITEM ID
c_item_name TEXT NOT NULL CART ITEM NAME
c_item_price NUMBER NOT NULL CART ITEM PRICE
EMPLOYEE:
FEEDBACK:
Field Name Data type Constraints Description
f_id AutoNumber Primary Key FEEDBACK ID
f_desc TEXT NOT NULL FEEDBACK DESCRIPTION
b_id NUMBER NOT NULL BUYER ID (FEEDBACK)
bname TEXT NOT NULL BUYER NAME( FEEDBACK)
ITEMS:
Field Name Data type Constraints Description
item_id NUMBER Primary Key ITEM ID
item_name TEXT NOT NULL ITEM NAME
item_detail MEMO NOT NULL ITEM DESCRIPTION
item_price NUMBER NOT NULL ITEM PRICE
item_catergory TEXT NOT NULL ITEM CATEGORY
item_date Date/Time NOT NULL ITEM PURCHASED DATE
SELLER:
Field Name Data type Constraints Description
s_id NUMBER Primary Key SELLER ID
s_name TEXT NOT NULL SELLER NAME
s_phno TEXT NOT NULL SELLER PHONE NUMBER
s_email TEXT NOT NULL SELLER EMAIL-ID
s_addr TEXT NOT NULL SELLER ADDRESS
SELLER RECEIPT:
Field Name Data type Constraints Description
sr_id NUMBER Primary Key SELLER RECEIPT ID
seller_id NUMBER Foreign key SELLER ID
item_id NUMBER Foreign key ITEM ID
date_issued Date/Time NOT NULL DATE OF INVOICE CREATION
4. FORM DESIGN
(WITH INPUT VALUES)
1.)ADMIN LOGIN FORM:
4) REGISTRATION FORM:
5) EMPLOYEE SEARCH FORM:
ADVANTAGES
LIMITATIONS
FUTURE ENHANCEMENTS
8) Bibliography
REFERENCE BOOKS:-
● Software Engineering by Dr.D.D Balasaraf and Umakant
S.Shrisshetti.
● Database Management System by Ms.Kavita Khobragade and
Mrs.Manisha Bharambe.
● Visual Basic 6.0 Programming Black book by Steven Holzner.
WEB SITES:-
● https://www.vbforums.com/forumdisplay.php?1-Visual-Basic-
6-a nd-Earlier
● http://stackoverflow.com/
● www.codeguru.com
● https://www.codeproject.com\