Escolar Documentos
Profissional Documentos
Cultura Documentos
AFFILIATED TO
UNIVERSITY OF MUMBAI
A
PROJECT REPORT
ON
“GAS DISTRIBUTION SYSTEM”
SUBMITTED BY
Miss. Madhavi Ananda Pawale
(SEAT NO. 870)
IN
ACADEMIC YEAR 2010-2011
WELCOME
TO
OF
HP GAS DISTRIBUTION,KHED
BY
(T.Y.BSc.I.T.)
1. Introduction (Synopsis)
5. Screens
7. Conclusion
9. Bibliography
1.1 Application details: By clicking this label user can view various information
about the Applicants. Such as Applicant number, Applicant name, Applicant Address
etc.
1.2 Customer details: By clicking this label user can view various information
about the Customer such as Customer number, Customer name, Customer Address etc.
1.3 Transaction details: By clicking this label user can view various information
about the transaction such as driver Date of Booking, Date of Delivery, Number of
Cylinders etc.
1.4 New Booking details: By clicking this label user can view various information
about the Booking such as Booking Number, No. of Cylinders Booked, Date of Supply,
Due Date etc.
1.5 Stock details: By clicking this label user can view various information about the
Stock such as Stock Details details.
Problem overview
In this mechanical world, time seems to be a precious thing. Keeping time as a vital
factor that transportation has been developed, it implements the storage and retrieval
system of day-to-day activities which involves daily Booking report, monthly report on
Booking of the customers, and enquires which enables us to provide efficient and
accurate methods of organizing and accessing different types of information.
Keeping the various records about Customers and their booking also for their
Booking details, for booking information is very big field. There are many Customer
and many booking and booking for that customers in the booking system. So to keep all
this information manually is quite hard difficult to handle. Because a businessman is
also one person who cannot handle all this records and hence cannot satisfy the
demands. Many times we need to delete some records and also want to access many
records more quickly.
But only one person cannot handle all this operations because this record contains
very large information which is beyond the limit of the one person. So this process gets
delay and lead to error prone. Also it becomes time consuming. So there is a need to
solve this problem or to overcome this problem.
The “HP Gas Distribution System, Khed” project solves this problem. This project’s
home page contains the Labels of different information such as Application details,
Normally, we enter VISUAL BASIC on one line. Meaning that end of the physical
line indicated the end of the statement. Thus we can think of the line as an usual
implicit end-of-statement marker. This stand in contrast with usage in more highly
structured languages.
Our finished applications are a true exe file that uses a run time DYNAMIC LINK
LIBRARY (DLL) that we can freely distribute.
LEARNING EDITIONS:
The VISUAL BASIC learning edition allows the programmers to easily create
powerful applications for Microsoft Windows 98 and Windows NT. It includes all
intrinsic controls, plus grid, tab and data bound controls.
PROFESSONAL EDITION:
The VISUAL BASIC professional edition provides the computer professional with
full featured set of tools for developing solutions for others it includes all the features of
learning editions, plus edition ACTIVEX controls, including all internet controls, and
the Crystal Report Writer.
ENTERPRISE EDITION:
The VISUAL BASIC enterprise edition allows professional to create robust
distributed applications in a term setting. It includes all the features of the professional
edition, plus the AUTOMATION MANAGER, COMPONENT MANAGER,
DATABASE MANAGEMENT TOOLS, MICROSOFT VISUAL SOURCE safe
project-oriented version control system and more…
Ms-Access
Ms-Access is a relational database Management System. It is used to store data. We
can create tables. Add records in it and retrieve data whenever we want to see. We have
created relationship between all tables.
HARDDISK : 180 GB
SOFTWARE ENVIRONMENT
SYSTEM DEFINATION
After detailed system study by conducting interviews, referring manuals, reports and
observations it is found that the existing system has some minor drawbacks. They are as
follows:
No proper system maintenance
Minor modifications are needed in the documents
No proper formats of reports
EXISTING SYSTEM
This project maintains the following modules:
Applicants Details
Customers Details
Stock Details
Delivery Details
New Booking Details
Transaction Details
Stock Updation Details
REPORTS:
SYSTEM DESIGN
The entire system design can be divided into 3 different parts which includes:
• File Design
• Input Design
• Output Design
FILE DESIGN:
The design base files are the most important of the system. The performance of the
system depends on how the system is design. It has been given at most attention to
reduce the size of files and redundancy. At the same time all the files are design to
incorporate all relevant information regarding each entities. A single database with
information about all the entities will make the system more complicated. The functions
and structure of each of the database files are given below.
1. APPLICANTS
2. CUSTOMERS
This file is used to store the Customer’s Number, Customers’ Name, Customers
Address, Customers Contact Number etc.
3. TRANSACTION
This file is use to store the details of Date of Booking, Date of Delivery, No. of
Cylinders, Amount etc.
4. DELIVERY
This file is used to store the No. of Cylinders, Date of Delivery, Transportation Name,
Consignment Name etc.
5. NEW BOOKING
This file is used to store the Booking Number, Due Date, Receipt Number, Cylinders
Supplied, Date of Supply etc.
6. STOCK
This file is used to store the Transaction Number, Date, No. of Cylinders Arrived, and
Serial Number From, Serial Number To etc.
7. STOCK UPDATION
This file is used to store the Total Balance Stock, Current Balance Stock,Total
Cylinders Supplied. Date etc.
REPORTS:
• APPLICANTS REPORT
• CUSTOMERS REPORT
• DELIVERY REPORT
• STOCK REPORT
• TRANSACTION REPORT
USER’S SCREEN
REPORTS EXIT
APPLICANT
APPLICANT APPLICANT
DETAILS
DETAILS REPORT
CUSTOMER CUSTOMER
DETAILS REPORT
STOCK STOCK
DETAILS REPORT
DELIVERY DELIVERY
DETAILS REPORT
TRANSACTION TRANSACTION
DETAILS REPORT
In a software development project, errors can be injected at any stage during the
development. Testing performs a very critical role for quality and for ensuring the
reliability of software. During testing, the program to be tested is executed with set of
test cases, and the output of the program for the test cases is evaluated to determine if
the program is performing as it is expected to. Due to its approach, dynamic testing can
only ascertain the presence of error in the program; the exact nature of the error is not
usually decided by testing. Testing forms the first step in determining the errors in the
program. Clearly the success of testing in revealing errors in programs depends
critically on the test cases.
Testing is usually relied upon to detect the faults that occur during any phase of the
software development cycle, in addition to the faults that introduced during the coding
phase itself. For this, different levels of testing are used which perform different tasks
and aim to test different aspects of the system. The basic levels of testing are unit
testing, integration testing, system and acceptance testing. The different levels of testing
attempt to detect different types of faults.
Test Plan:
A Test plan is a general document for the entire project, which defines the scope
approach to be taken, and the schedule of testing, as well as identifying the test items
for the entire testing process and the personnel responsible for the different activities of
testing commences and can be done in parallel with the coding and design phases, the
inputs for the test plan are:
Requirements Document
The project plan is needed to make sure that the test is consistent with overall plan for
the project and the testing schedule matches that of the project plan the requirements
document and the design document are the basic document Used for selecting the test
unit and deciding the approaches to be employed during testing .A test plan should
contain the Following:
Test unit specification
Features to be Tested
Test Deliverables
Schedule
Test unit
It is a set of one or more modules together with associated data which are the forms a
single computer program and which are the object of testing. It can occur at any level
and can contain from a single module to the entire system. This is carried out at every
stage of the project i.e., after completion of every module.
Features to be tested:
Include all software Features and combinations of features and combination of
features to be tested. It includes functionality, performance, design constraints and
attributes.
Testing deliverables should be specified in the test plan, before the actual testing
begins. Deliverables could be a list of test cases that were used detailed results of
testing, test summary report, test log and data about the code coverage.
Schedule:
Specifies the amount of time and effort to be spent on different activities of testing
and testing of different units have been identified.
UNIT TESTING
Unit testing is a dynamic method for verification, where the programs is actually
compiled and executed .It is one of the most widely used method, and the coding phase
is sometimes called “coding and unit testing phase”, as in other forms of testing, unit
testing involves executing the code with some test cases and then evaluating the results.
The goal of unit testing is to test modules or ”units” and not the entire software
system. The programmer himself most often does unit testing, the programmer, after
finishing the coding of a module, test it with some data. The tested module is then
delivered for system integration and further testing there are 4 categories of tests that a
programmer will typically perform on a program unit
Functional tests:
Performance tests:
Stress tests:
Stress tests are designed to overload a system in various ways. Structural tests are
concerned with examining internal process logic of software system.
Integration tests:
After the unit testing the modules is gradually integrated into subsystem, which are
then integrated them to eventually form the entire system. During integration of
modules Integration testing is performed .The goal of this testing is to detect design
errors, while focusing on testing the interconnection between modules.
System Testing:
After the system is put together, system testing is performed. here the system is tested
against the system requirements to see if all the requirements are met and the system
performs as specified by requirements. The entire software is tested and the goal is to
see if the software meets the requirements
Alpha-beta Testing:
A customer does the alpha test at the developer site .the software is used in a natural
setting with the developer and usage problems.
The beta testing is conducted at one or more customer areas of the end of software.
The problems are recorded and updated.
Conditional testing is a test case design method that exercises the logical condition in
a program module. The possible types of components in a condition include a Boolean
operator, Boolean variable, pair of Boolean parenthesis relational operator or an
arithmetic operator.
Data flow testing method selects test path of program according to the location of
definition and uses of variables in the program .they are useful for selecting test. They
are useful for selecting test paths of a program containing nested if and loop statements.
Loop Testing:
Loops are the cornerstone for the vast majority of all algorithm implemented in
software loop testing is a white box technique that focuses exclusively on validity of
loop construct.
Black box testing method focuses on the functional requirements of the software.
Black box testing method attempts to find in the following categories.
- EVEN GELOS
PETROUTSOS
- MICROSOFT CORPORATION
- STEVEN HOLZNER