Escolar Documentos
Profissional Documentos
Cultura Documentos
_______________________________________________Page No. 1
Government Polytechnic
_______________________________________________Page No. 2
Supervisor Certificate
This Is To Certify That Mr./Ms. ______________ ______________ Of I.T (Seat No. ____) Has Worked On Project. Entitled ___________________________, From __________ To __________ . This (S-506) Is InHouse Project Of Three Credits. He/She. Was Regular In His/Her Work And Devoted Around 100 Hours For The Project Including Analysis And Design. He/She Has Completed The Project Satisfactory.
Date: Head/Coordinator.
Supervisor.
_______________________________________________Page No. 3
Acknowledgement
Project work is an assignment where by the candidates coming out of the academic field exposure to the person, who are on the job. Therefore it affords an opportunity of leaving from others experience. We are extremely thankful to dr. H.s patel, principal of government polytechnic, who allowed me to work on the project. We are extremely thankful to mr. Indravadan , the owner of the krishana coporation for providing us information and details of the shop. We express sincere thanks to our h.o.d mr. Parvez faruki for inspiring me to take up the direction and also rendering her precious help and guides. Without her co-operation and direction, it would have been difficult for me to compicate this dissection. We sincerely express our deep source of gratitude to our project guide miss.jigna gandhi who has been immense help to us supporting and guiding us throughout the project work. I would like to take this opportunity to thanks my counselor mr. Utpal dholakia and other faculty member for their consultant inspiration. Last but not list my heartily thanks to my friends and all lab staff . i would once again like to express my heartiest to all who helps me directly or indirectly throughout this project work.
_______________________________________________Page No. 4
Project Profile
Project Title Oraganization Project Guide Submittted By Front-End Back-End Documentation Submited To : : : :
Gas Agency System Krishna Corporation
: : : :
_______________________________________________Page No. 5
_______________________________________________Page No. 6
_______________________________________________Page No. 7
_______________________________________________Page No. 8
Hardware Requirement
Compaq Keyboard Compaq Monitor Compaq Mouse Pentium Processor 64 Mb Ram 4 GB Hard Disk
Software Requirement
Front End Tool Back End Tool Visual Basic 6.0 Microsoft Access
_______________________________________________Page No. 9
Tools Information
Visual Basic 6.0 (Front End Tool)
VB is a program language and development that allows you to create programs that run under windows operating system. It enable you to develop many different type of application. It is a programming language used to create windows base application. It makes it very easy to get the user interface of the application and running it. It is very easy and it provides a very friendly environment while programming in vb. It provides a vital link to graphics environment and allows you to develop application base on stander windows features. Dialogue box, command buttons, pulls down menus, scroll bars and selection lists etc. It also allows crating robust application that fully make use of the graphics, user interface. By connect with access can be run and terminated through vb 6.0.
_______________________________________________Page No. 10
An application is made up forms, controls, modules. Forms are windows on which you built user interface. Controls are building of user interface control also called active x control and command button that you used to display information to the user, gather information from the user, and respond to the user action. Procedures are small routing you write that are callable from anywhere in your application into small components that can be called in many times. Events in a very important in any windows programming language. An event is something that occurs in response to a user interaction with keyboard or mouse. Events are those messages that the operating system sends to the applications. Forms i. Properties ii. Property Procedures. iii. Event Handless. iv. Other Procedure Controls i. Property ii. Event Handles iii. Methods
_______________________________________________Page No. 11
_______________________________________________Page No. 12
System Study
Feasibility Study: To check whether the system once created will be feasible or not. A feasibility study is undertaken to determine the possibility all probability of either improving the existing system or developing a completely new system. Technical Feasibility: To technical feasibility, it is checked that if the work for the project can be done with present equipments, software and available personnel.
_______________________________________________Page No. 13
Cost Estimation
The category of the system is organic for this a = 3.2 and b = 1.05 are constant. The size of the system is 2.5 kdl (thousand of delivered line of code). Initial cost estimation ei = a * (size)b = 3.2 * (2.5)1.05 = 8.375 Eaf is effort adjustment factor. Reliability is high 1.15 Database size is normal 1.00 Complexity is very low 0.70 Programmer experience is very low 1.29 Programmer capacity is normal 1.00 Language experience is low 1.07 Analyst catalyst is normal 1.00 Eaf = 1.15 * 1.00 * 0.70 * 1.29 * 1.00 * 1.07 * 1.00 =1.11 Final cost = ei * eaf = 8.375 * 1.11 = 9.30 pm
_______________________________________________Page No. 14
_______________________________________________Page No. 15
Existing System
Introduction
The krishna corporation does not own any existing computerized system currently, but are willing to convert their manual system into computerized system. They do all their transactions annually through record books.
Existing system
In manual system, to add a new customer they have to add records in register. Suppose customer leave the town or city, so their records should be deleted. They delete their records from master register, which is difficult. If a customer wants to change his or her address, it is difficult to update or change his or her profile into register. In manual system it is difficult to maintain the stock. When a customer comes for cylinder refills they have to first check their validity. Then they will book his refill in the register, which is very time consuming. In manual system they have to daily update the stock register. Difficulty to see how much cylinder customer, company or company itself has. Existing system is manual system rather than computerized.
_______________________________________________Page No. 16
In existing system they are using different types of registers for different purpose.
Work distribution cant be made easily. To check customers history is difficult. Probabilities of errors in calculation of bills, stock management
etc.
_______________________________________________Page No. 17
This system involves When a customer request for a gas refills, first check for his validations, prepare bills and handle those bills to particular deliveryman for delivery. This system maintains customers all type of records.
It handle customers all requests for booking, gas refills and to provide them in time.
_______________________________________________Page No. 18
History checking easily done. Accurate work. Fewer people required. To make the security high. Daily transactions are easily handled. Fast transactions. Work distribution is easily done. Generation of different kinds of reports. Reduction in redundancy. Easily find that how many no. Of cylinder company has. Easily find that how many cylinders are empty. Easily find stock reports. Gives fixed rate of the customer.
_______________________________________________Page No. 19
_______________________________________________Page No. 20
Maintaining customer information. Maintaining stock information. Maintaining cylinder refills information. Delivery of refills information. Preparation of reports. Handle the fix rate of the customer.
_______________________________________________Page No. 21
Requirement Analysis
As we have decided to develop a new system now it is a time to determine the new requirement for the new system. As the user is the most important part of any system it is required to find the users requirement to develop a user friendly system rather than having develop a developer friendly system. the outputs required by the user that must be included into the proposed system are as follows. The work for he particular user must be personalized. The customer information must be entered on such a way that it is easier for user to understand. Daily reports and monthly reports are printed. Bills are printed as in required order. The user must be provided ease if he wants to switch from one application to other at a time.
_______________________________________________Page No. 22
Interviews
Record review Interviews User interview were conducted to determine the qualitative information. These interview, which were unstructured interview provide opportunity to gathered information from respondents who are involve in the process for a long time. These interview provide information such as Activities involved in process o given system. Limitation of existing manual system. Type and frequency of reports.
Record review To gather details about the system, many kinds of reports were reviewed. This study covered Standard operating procedure. Reports generated by existing manual system. Input /output of the system.
_______________________________________________Page No. 23
_______________________________________________Page No. 24
_______________________________________________Page No. 25
Data Dictionary
Data dictionary is a store of information about the data in database. The dictionary defines the name, description, source of data, users of data, and keywords in data, formula to derive the data specification and such other details. Data dictionary brings common understanding of the data in the organization RDBMS provides software to create the dictionary. Use of data dictionary enforces the standards of processing, usages application and documentation in the organization. Data dictionaries are an integral component of structured analysis, since data flow diagram by themselves do not fully describe the information about the system. The data dictionary provides additional information about the system. Description of all data used in the system is given in a data dictionary.
_______________________________________________Page No. 26
Data Dictionary
The files used for this project are Customer_master Customer_rate Cylinder_master Recived_master Trans_master Type_master
Valid(0,1,2)
_______________________________________________Page No. 27
Not null
_______________________________________________Page No. 28
Sr.No . 1 2 Fields
Cylinder_Type Cylinder_Type_Name
_______________________________________________Page No. 29
HIERARCHY CHART
GAS AGENCY SYSTEM
DELIEVER Y TO CUSTOMER
STOCK MAINTAI N
DELIVER Y TO COMPAN Y
_______________________________________________Page No. 30
CYLINDER_MA R
CYLINDER_MA ER
DELIVERY INFORMATION
CUSTOMER
ACKNOWLEDGEMENT
_______________________________________________Page No. 31
CONTEXT DIAGRAM
DIAGRAM DIAGRAM
CUSTOMER
REQUEST FOR FULL CYLINDER
ACKNOWLEDGE
GAS AGEN CY
COMPANY
_______________________________________________Page No. 32
0 LEVEL DFD
REQUEST FOR CYLINDER CHALLAN INFO
CUSTOMER
ACKNOWLEDGE
CHALLAN _MASTER
to cust
CYLINDER_MASTER
RECEIVED INFO
RECEIVED_MASTER
ACKNOWLEDGEMENT
CHALLAN INFO
CHALLAN_MASTER
STOCK INFO
CHALLAN _MASTER
CHALLAN INFO
TRANS_MASTER
CYLIN INFO
CYLINDER_MASTER
GIVEN EMPTY CYLINDER
CYLINDER_MASTER
5.0 full cylin recieve d ACKNOWLEDGEMENT GIVE FULL CYLIN
CYLIN INFO
COMPANY
ACKNOWLEDGEMENT
RECEIVED_MASTER
RECEIVED INFO
_______________________________________________Page No. 33
CUSTOMER
ACKNOWLEDGE
CYLINDER INFO
CYLINDER_MASTER
CYLINDER_MASTER
CUSTOMER
_______________________________________________Page No. 34
customer
CYLINDER INFO
CYLINDER_MASTER
DELIVERY INFORMATION 2.3 MADE CHALLAN FOR THE CUSTOME R CHALLAN GIVEN TO CUSTOMER CUSTOMER ACKNOWLEDGEMENT
_______________________________________________Page No. 35
ACKNOWLEDGEMENT
CUSTOMER
DELIEVERY EMPTY CYLINDER INFO
TRANS_MASTER
CYLINDER_MASTER
ACKNOWLEDGE
_______________________________________________Page No. 36
COMPANY
FULL CYLINDER INFORMATION 5.2 ADD NO INFO FULL LIST CYLINDER INFO CYLINDER_MASTER
_______________________________________________Page No. 37
_______________________________________________Page No. 38
_______________________________________________Page No. 39
_______________________________________________Page No. 40
_______________________________________________Page No. 41
_______________________________________________Page No. 42
_______________________________________________Page No. 43
_______________________________________________Page No. 44
_______________________________________________Page No. 45
_______________________________________________Page No. 46
_______________________________________________Page No. 47
_______________________________________________Page No. 48
_______________________________________________Page No. 49
_______________________________________________Page No. 50
_______________________________________________Page No. 51
_______________________________________________Page No. 52
_______________________________________________Page No. 53
_______________________________________________Page No. 54