Synopsis of Project

NK GAS AGENCY-BOOKING SYSTEM Version1.
1. INTRODUCTION
The project has been designed in order to provide a working overview of the Gas
Agency Booking automation system, through which transactions like customer gas
booking, adding stock and customer account management can be made possible.
The system is used here as a medium to provide the end user(s) with ease of using the
interface, which should be in accordance with the current market trend.
Also, the system is supposed to possess efficient, effective as well as secure

transaction. The data entered should not be visible to other people, who just might
want to use the data for some mischievous purposes.
Before development of the system it has to be seen that how the computerized system
is going to benefit the users (i.e. client) as compared to the manual system, which they
are currently using and how it is going to benefit them more as compared to manual
system.
AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

NK GAS AGENCY-BOOKING SYSTEM Version1.1
2. OBJECTIVE
The objective of this project is to computerize the Gas Agency Booking system, which
currently operates under the manual system. This project would help in handling the
gas agency booking work on computers. Their will be one computer system on which
everyday computer transaction can be done like opening new customer account,
handling transaction, editing old accounts and viewing reports etc.
In this project the sub-objectives, which are part of main objectives, are the following:
1) Editing Customer Accounts: - Employee can open the old customer account and
edit the corresponding personal information in case of any changes.
2) Adding Stock Items: - User can view the stock items in the database in a report
view manner, and can easily add or edit the stock item in the form.
3) Easy reports: - Report like Customer details and Stock details can be viewed on a
click of a mouse.
4) No paper work: - No need of paper work because all the work likes customer
entries and gas booking will do on computer.
5) Fast results: - Since all the information can be assessed on the click of the mouse
so work will be fast.

3. ANALYSIS
We analyzed the whole market according to our project requirements. In our project
we need an excellent database system as a back-end which will enable us to insert,
update, delete, or manipulate the data efficiently.
The front-end should be such that it should make the whole environment user friendly
for gas agency but not at the cost of efficient working.
After a lot of analysis we came to the conclusion that ‘MSSQLServer2000’ will be

best suited for back-end and ‘C#’ will be best suited front-end.
5.1 SYSTEM ANALYSIS

System Requirements
Review & Validation

User Requirement Specifications
Software Requirements
Software Requirements
Review & Validation
Preliminary Design
Review & Validation

Detailed Functional Specifications
Detailed Design Global Implementation Specifications &

Review & Validation Detailed Implementation Specifications
Code and Debugging
Review & Validation Coding & Debugging
Testing
Testing
Review & Validation
Maintenance
Review & Validation Maintenance
Process Engineering of Application Software (Software Development Life cycle)

5.2 IDENTIFICATION OF THE NEED
Since the world is growing for globalization, every organization wants to beat its
competitors and want to grow. Enterprise Resourceful Planning (ERP) is the need of
today’s organization. Survival on manual system is difficult so, that’s why
organization of the corporate world wants to computerize their departments. The
modules should be complete database driven and interactive that should provide the
proper information about the Placement and Training Organization.
Success of a system depends largely on how accurately a problem is defined,

thoroughly investigated and properly carried out to the choice of solution. Analysis is
a phase in which the requirements for the new system are identified. System analysis
is a detailed study of the various operations performed by a system and their
relationship within and outside of the system. The question is: what must be done to
solve the problem? One aspect of analysis is defining the boundaries of the system
and determining whether or not a candidate system should consider other related
system. During analysis data are collected on the available files, decision points and
transactions handled by the parent system. Data flow diagram, interviews, onsite
observations, questionnaires are used as a logical system model and tools to perform
the analysis.
Tasks, which are performed as analyst:

1. Gathered all facts about the present system from the employees.
2. Studied strength and weakness of the current system.
3. Determined “what” must be done to solve the problem.
4. Prepared a functional specifications document.
In order to reduce the time, there is a need for computerized system that cans retrieve
data, insert data, update existing data or delete existing data. These modules are
developed wit the aim of reducing time, reducing manpower, reducing cost so that the
records can be easily maintained. The volume of work and complexity are increasing
year by year. This system reduces complexity and workload.
Preliminary Investigation:
A request to take assistance from information system can be made for many reasons,
but in each case some one in the organization initiate the request. When the request is
made, the first system activity the preliminary investigation begins. This activity has
three parts:
1. Request clarification
2. Feasible Study

3. Request approval
Many requests from employees and users in the organization are not clearly defined.
Therefore, it becomes necessary that project request must be examined and clarified
properly before considering systems investigation.
The feasibility study is carried out by a small group of people who are familiar with
information system techniques, understand the parts of the business or organization
that will be involved or affected by the project, and are skilled in the system analysis
and design process.
Request Approval: It is not necessary that all request projects are desirable or feasible.
Some organizations receive so many projects request from employees that only a few
of them can be purchased. However, those projects that are feasible and desirable
should be put into a schedule. In some cases, development can start immediately,
although usually system staff members are busy on other ongoing projects. When such
situation arises, management decides which projects are more urgent and schedule
them accordingly. After a project request is approved, its cost, priority, completion
time and personal requirements are estimated and used to determine where to add it to
any existing project list. Later on, when the other projects have been completed, the
proposed application development can be initiated.
Analysis is a process of studying a problem and to find the best solution to that
problem. System analysis gives us the target for the design and the implementation.
Analysis is one phase, which is important phase for system development lie cycle.
System development is a problem solving techniques. Analysis involves interviewing
the client and the user. You people and the existing documents about the current mode
of operation are the basic source of information for the analyst.
Analysis is the process of studying a problem to find the best solution to that problem.
System analysis gives us the target for the design and the implementation. Analysis is
one phase of the very important phase of the system development life cycle. System
development is a problem solving techniques. Analyses involve interviewing the client
and the user. These people and the existing document about the current mode of
operation are the basic source of information for the analyst.

6. FEASIABILITY STUDY
Depending on the result of the initial investigation, the survey is expended to a more
detailed feasibility study. A feasibility study is a test of system proposal according to
its work ability impact on the organization, ability to meet user needs, and effective
use of resources. It focuses on three major questions-
1. What are the user’s demonstrable needs and how does candidate system
meets them?
2. What resources available for given candidate system Is the problem worth
solving?
3. What is the likely impact of the candidate system on the organization? How
well does it fit with in the organizations master MIS plan?
Each of these questions must be answered carefully.
The objective of the feasibility study is not to solve the problem but to acquire a sense
of its scope. During the study, the problem definition is crystallized and aspects of the
problem to be included in the system are determined. Consequently cost and benefits
are estimated with greater accuracy of this stage. The result of feasibility study is a
formal proposal. This is simply a report- a formal document detailing the nature and
the scope of proposed solution. The out come of the initial investigation is to be
determining whether in alternative system is feasible.
6.1 TECHNICAL FEASIBILITY

Technical feasibility around the existing computer system (hardware, software, etc)
and what extend it can support the proposed addition. For example if the current
computer is opening at 80% capacity- an arbitrary ceiling – then running another
application could overload the system are require additional hardware. This involves
financial consideration to accommodate enhancements. If the budget is serious
constraints, then the project is not feasible. Regarding any project few technical
feasibility questions must be considered:-
1. Is a project technically feasible?

2. Is it with in the state of art?
3. Can defects to reduce to level matching the application need?
All these questions are study in technical feasibility. Project on the margins of your
experience are not so easy, a team have to spend several month discovering what the
central, difficult to implement requirement of a new application actually are. Do some
of these requirements pose risks that would make the project infeasible? Can these

risks be overcome? The feasibility team ought to negative answers; a reduction is

requirement may be negotiated. To carry architecture and design of the high-risk
requirement to the point at which it can answer these questions.
6.2 ECONOMICAL FEASIBILITY

Economics analysis is the most frequently for evaluating the effectiveness of a
candidate system. More commonly known as cost/benefit analysis, the procedure is
determined benefits and savings. That is expected from a candidate system and
compares them with cost. If benefits out weigh cost and compare then the design is
made to design and implement the system. Otherwise further justification or
alterations in the proposed system will have to be made if it is to have a chance of
being approved. This is an ongoing report that improves in accuracy at each phase of
the system life cycle. Regarding any project few economical feasibility questions must
be considered:-
1. Is it my software is economically feasible?

2. Can development is completed at a cost the software organization, its client,
or the Market can afford?
3. This study is very necessary. We can evaluate economical feasibility of this
Software system that means what is the market value of this system?
If your system is economically feasible then he is use many people and stand in
market in long time.
6.3 OPERATIONAL FEASIBILITY

People are inherently resistant to change, and computers have been facilitating
change. An estimate should be made of how strong a reaction the user staff is likely to
have toward the development of a computerized system. It is common knowledge that
computer installation has something to do with turnover, transfer, retraining and
changes in employee job status. The systems operational feasibility depends on the
system technical feasibility. Which methods we use for developing the system and
what technique we use for developing the system. If the system is operationally
feasible then it is a reliable system and giving the correct result. When client is
working with this software system then all forms and fields are described and its
database is connect in appropriate manner.

Choice of Platform?
In any organization a lot of data is generated as result of day-to-day operations. In the
past , all kind of data – be it business of a company. Since the task was performed
manually, it was time consuming and error prone. With the advent of computer, the
task of maintaining large amount of data has undergoes a sea change. Today computer
system have become so user friendly that even first time users can create their own
application with the help of tools such as MS-Access, Fox-Pro and SQL Server. These
tools are very visual and hence user friendly. They provide a point and click
environment for building applications that can interact with large amount of data.

7. SOFTWARE REQUIREMENT
SPECIFICATION
7.1HARDWARE SPECIFICATION:-
It is recommended that the minimum configuration for clients is as appended
below:-
Suggested Configuration of Windows clients:-
Microprocessor - Pentium-2 class processor, 450 megahertz (MHz)

Ram - 128 MB of RAM
Hard Disk - 2.5 gigabytes (GB) on installation drive, which
Includes 500 MB on system drive.
CD ROM Drive - 52 X CD ROM Drive
7.2SOFTWARE SPECIFICATION:-
Operating System: Windows 2000XP/Windows 2000 NT
RDBMS: Sql Server 2000
Front End: Microsoft Visual Studio.NET
This system was developed under window 2000XP/Windows 2000 NT. It is complete
with all 32-bit versions of windows operating system. Windows is a popular and
largest used operating system in the world because it is easy to understand and
provides an easy interface to users.
Windows 2000XP/Windows 2000 NT Operating System

The main responsibility of an operating system is to manage computer’s resources. All
activities in the system scheduling application programs, waiting files to disk, sending
data across a network and so on should function as seamlessly and transparently as
possible. Windows 98 makes your computer easier to use, with new and enhanced
feature.

Improved Reliability
Window 98 improves computer reliability by introducing new wizards, utilities and
resources that keep your system running smoothly.
Faster Operating System

Windows 98 includes tools that help your computer run faster than Windows 95 with
out adding new hardware. Window 98 includes a suite of programs designed to
optimized you’re web.
Integration
Windows 98 Explorer and Internet Explorer integrate local and Web-based resources
in a single viewer computer’s efficiency, especially when used together. Window 98
makes your computer more entertaining by new hardware. These enhancements
provide you with hours of fun.
Multitasking Concepts
Multitasking in general refers to an operating system’s capability to load and execute
several applications concurrently. A multitasking operating system is consider a robust
and reliable one if it successful shields concurrent applications from each other,
making them believe that they system also shields application from other’s bugs.
To a large extent, multitasking operating system relay on system hardware to

implement these capabilities. Another important aspect of multitasking is process
scheduling. As process are capable of executing only a single stream of instruction at
any given, multitasking would obviously not be possible without the technique of the
context switching. A context switch, triggered by a specific event (such as an interrupt
from a timer circuit or a call by the running application to a specific function),
essentially consist of saving the processor context (instruction pointer, stack pointer,
register contents) of one running program and loading that of another.
In a cooperative multitasking environment, the operating system relies explicitly on
applications to yield control by regularly calling a specific set of operating system
functions. Context switching takes place at well-defined point during the execution of
a program.

8. DESIGN
The most creative and challenging phase of the system life cycle is system design. The
term design describes a final system and the process by which it is developed. It refers
to the technical specifications that will be applied in implementing the candidate
system.
The first step is to determine how the output is to be produced and in what format.
Samples for the output (and input) are also presented.
The second step is input data and master files (data base) have to be designed to meet
the requirements of the proposed output. The operational (processing) phases are
handled through program construction and testing including a list of the programs
needed to meet the system’s objective and complete documentation. Finally, details
related to justification of the system on the user and the organization are documented
and evaluated by management as a step toward implementation. To design the system
we must note the following points:
 To identify the Software Components which satisfy the System Design?

 To design and document the Software Components and their linkage.
In this component the software components and relevant interfaces such as,
interactions with existing internal and external systems, network connections, standard
input an output formats are to be identified.
Identify Relevant Interfaces

 Interaction with existing internal systems.
 Interaction with external systems.
 Network Connections.
 Standard Input Formats
 Standard Output Formats.
Program Specification
Elements of Specifications required are

 How it is being accessed.
 Function called.
 Program Security.
 Field Details.
 Program Functions.

From Analysis
Detailed
Output System Cost
Design Documentation Justification
and
Candidate
design
Input
Design Design
submitted to
management
for approval
File
Design
Processing No
Design Design Abandon project
accepted
Yes
Test
Programs
STEPS IN SYSTEM DESIGN

8.1 STEPS IN SYSTEM DESIGN
Databases and database technology are having a major impact on the growing use of
computers. It is fair to say that databases will play critical role: in almost all areas
where computers are used. Including business, engineering, medicine, law, education
and library, science to name a few. A database is a collection of related data. By data
we mean known facts that can be recorded and that have implicit meaning for
example, consider, the names, telephone numbers and addresses of the people you
know. You may have recorded this data in an indexed address, book, or you may have
stored it on a diskette. Using a personal computer and software such as DBASE IV or
V, PARADOX, MS EXCEL OR MS ACCESS. This is a collection of related data with
an implicit meaning and hence is a database.
A database is a logically coherent of with some inherent meaning.
A database represents some aspects of the real world. Sometimes called the mini-
world or the universe of discourse (UOD). Changes to the mini-world are reflected in
the database.
A database is designed, built and populated with data for the specific people. It has an
intended group of users and some preconceived applications in which the users are
interested.
A database can be of any size and of varying complexity. For example, the list of
names and addresses referred to earlier may consist of only a few hundred records,
each with simple structure. On the other hand the card catalog of a large library may
contain half a million cards stored under different categories by primary author’s last
name, by subject, by book title with each category organized in alphabetic order.
A database may be generated and maintained or by machine. The library card catalog
is an example of a database that may be created and maintained either by a group of
application programs written specially for that task or by a database management
system.
A database management system (DBMS) is a collection of programs that enables
users to create and maintained a database. The DBMS is hence a general-purpose
software system that facilities tile processed of defining, constructing and
manipulating database for various applications. Defining a database involves
specifying the data types, structures and constraints for the data to be stored in the
database. Constructing the database is the process of storing the data itself on some
storage medium that is controlled by the DBMS. Manipulating a database includes
such functions as querying the database to reflect changes in the mini-world, and
generating reports form the data.
With the advent of the graphical operating system like windows, the world of
imputing went through a dramatic change. It opened up a whole new world of
graphics. Interfaces that use graphics came to known so graphical user interface
(GUI). These became very popular because the users could identify with images than

words. Mention tile word print to a person and it invokes the image of a printer. The
primary requirements for an interface are that it is easy to use. We must be able react
intuitively to an interface presented to us. This is possible if the interface presented is
such that is it emulates real life.
8.2 DATA FLOW DIAGRAM

DTDDADAA
Data Flow Diagramming is a means of representing a system at any level of detail
with a graphic network of symbols showing data flows, data stores, data processes,
and data sources/destination.
The data flow diagram is analogous to a road map. It is a network model of all
possibilities with different detail shown on different hierarchical levels. This processes
of representing different details level is called “leveling” or “partitioning” by some
data flow diagram advocates. Like a road map, there is no start point or stop point, no
time or timing, or steps to get somewhere. We just know that the data path must exist
because at some point it will be needed. A road map shows all existing or planned
roads because the road is needed.
Details that is not shown on the different levels of the data flow diagram such as
volumes, timing, frequency, etc. is shown on supplementary diagrams or in the data
dictionary. For example, data store contents may be shown in the data dictionary.
Data Flow Diagram (DFD) uses a number of symbols to represent the systems. Data
Flow Diagram also known as ‘Bubble Chart’ is used to clarify system requirements
and identifying the major transformations that will become programs in system
design. So it is the starting point of the design phase that functionally decomposes the
requirements specifications down to the level of details.
Symbols of DFD
The various symbols used for DFD are:
 Square
A square defines a source (originator) or destination of system data.
 Arrow
An arrow identifies data flow-data in motion. It is a pipeline through which

information flows.

 Circle
A circle or a bubble represents is a process that transforms incoming data flow into
outgoing data flow. Circle basically represents a process.
 Open Rectangle
An open Rectangle is data store-data at rest, or temporary repository of data. Open

rectangle basically denotes data storage.
Information Flow of Data for Testing
Software Test Results Evaluatio

Configuration n
Testing Error
Rate Debu
Data g
Expected
Test Configuration
Results
Reliabilit
y
Model
Correction
Predicted Reliabilit y
Information Flow of Data Testing

AGENCY
LEVEL: 1
Required for Booking

Agency
Customer
Check
Last
Release
Release Stock
Availability Booking
Process
Stock

LEVEL: 2
Customer Release Release
If Stock
less Than Update
Minimum Stock
Stock

A
Order Stock
Stock
Level
Company Y
Make
Order
LEVEL: 3
Samples Forms
Login Form
This is the Login Form from which the trainees and the authorized person of the
company should enter their name and password to use the system called “Placement
Providing System”. It is for the authorization of the system

Main Form
This is the main form which comes after when the user or the authorized person enters
their names and password and then press the login Button on the Login Form. If the
authorized person of the company enters their name and password and he is
authorized for that system then all the menus of the main form are enabling.

New Connection Form
This screen comes when the new Connection is issue to customer. User Fill the
Information in the form as per the Form and Connection No. is self generated. After
fill all the required information, we submit it and entry is updated in record.
Connection No. is unique field.
Customer Demand Form

In this the information of customer is enter & store, when customer demand for
cylinder.

Customer detail Form
This form is used to view all the detail of the Customer. User can also see the detail
according to the commercial and domestic Connections. This form is used to view all
the detail of the Customer according to the Connection date, Customer name and
Connection No and update the record according to the requirements only Connection
No. is not updateable.

Stock detail
Stock form is used for Inventory management. it use to know the present stock of both
commercial and domestic LPG cylinders. It also generate message when available
stock go under the minimum stock level.
Transaction Form

Transaction form is used for booking and release of LPG. It also check the last release
date, it is must that the difference between present date and last release should be 21
days.
Customer _ List Report

This report shows the record of all customers associated with NK GAS AGENCY.
Stock Report

This report shows all the information about the stock of cylinders.
Designer Form

This form represents the name of the developer of computer rise Booking System.
9. CODING
9. CODING
Login Form
using System;
using System.Drawing;
using System.Collections;
using System.ComponentModel;
using System.Windows.Forms;
using System.Data;
using System.Data.SqlClient;
using Microsoft.VisualBasic;
Public class Form1 : System.Windows.Forms.Form
{
DataSet ds;
int count=0;
Form2 f2;
private System.Windows.Forms.TextBox textBox1;
private System.Windows.Forms.TextBox textBox2;
private System.Windows.Forms.Label label1;
private System.Windows.Forms.Button button1;
private System.Windows.Forms.Button button2;
private System.Windows.Forms.ProgressBar progressBar1;
private System.Windows.Forms.Timer timer1;
private System.ComponentModel.IContainer components;
static void Main()

{
Application. Run (new Form1());
}
private void Form1_Load(object sender, System.EventArgs e)
{
SqlConnection con=new SqlConnection("server=.;uid=sa;database=gasagency");
SqlDataAdapter sd=new SqlDataAdapter("select * from login",con);
Ds=new Dataset();
sd.Fill(ds,"login");
progressBar1.Visible=false;
textBox2.PasswordChar='*';
this.Text="LOGIN TO NK GAS AGENCY";
progressBar1.Minimum=0;
progressBar1.Maximum=120;
}
private void Form1_Closing(object sender, System.ComponentModel.CancelEventArgs
e)
{
Application.Exit();
}
private void button1_Click(object sender, System.EventArgs e)

{
Data Table dt=ds.Tables[0];
for each(DataRow dr in dt.Rows){
if(dr[0].ToString()==textBox1.Text.Trim())
String () ==textBox2.Text.Trim ())
{i=1;
progressBar1.Visible=true;

label3.Text="Now Loading.....”
timer1.Start ();
}
Else
{i=1;
MessageBox.Show("invalid password");
textBox2.Focus();
textBox2.Clear();
count++;
}
}
}
if(i!=1)
{
if(textBox1.Text.Length==0)
{
MessageBox.Show("enter a user name");
textBox1.Focus();
}
else
{
MessageBox.Show("Invalid User, User Does not exist");
count++;
textBox1.Focus();
textBox1.Clear();
textBox2.Clear();
}
}
if(count==3)
{button1.Enabled=false;}
{
Application.Exit();
}
private void textBox2_KeyDown(object sender,System.Windows.Forms.KeyEventArgs e)
{
if(e.KeyCode==Keys.Enter)
{button1_Click(sender,e);
}}
private void timer1_Tick(object sender, System.EventArgs e)
{ button2.Enabled=false;
progressBar1.Value+=10;
if (progressBar1.Value==120)
{
timer1.Stop();
this.Visible=false;
f2.Show();
}}
Main Form
public class Form2 : System.Windows.Forms.Form

{
Form3 f3;
public static int count=0;
NewCon f4;
public static int i=0;
Form4 f5;
Form5 f6;
cust_details cc;
public static int k=0;
public static int m=0;
public static int q=0;
public static int p=0;
Cust_ListReport rep;
Stock_Report sr;
public static int w=0;
TransactionDetails td;
public static int t=0;
}
rivate void Form2_Load(object sender, System.EventArgs e)
{
this.WindowState=System.Windows.Forms.FormWindowState.Maximized;}
e)
{
DialogResult res=MessageBox.Show("Do You Really Want To Quit The
Application","QUIT NK GAS
AGENCY",MessageBoxButtons.OKCancel,MessageBoxIcon.Warning);
if(res==DialogResult.OK)
{
Application.Exit();
}
if(res==DialogResult.Cancel)
{
e.Cancel=true;
}
}
private void menuItem5_Click(object sender, System.EventArgs e)

{
Form f=this.ActiveMdiChild;
if(f!=null)
{
f.Close();
}
if(count==0)
{
f3=new Form3();
f3.MdiParent=this;
f3.Show ();
count=1;
}
else
{
if(f3.Visible==true)
{
count=1;
}
else
{
f3.Show();

count=1;
}
}
}
{
Form f=this.ActiveMdiChild;//this property determines whether any active form is
MdiChild form or not
if(f!=null)
{
f.Close();
}
else
{
MessageBox.Show("Cannot Close The Main Form");
}
}
{
Application.Exit();
}
{
if(f!=null)
{
f.Close();
}
if(i==0)
{
f4=new NewCon();
f4.MdiParent=this;
f4.Show();
i=1;
}
else
{
{ i=1;
}
else
{
f4.Show();
i=1;
}
}
}
{
if(f!=null)
{
f.Close();
}
if(q==0)
{
cc=new cust_details();
cc.MdiParent=this;
cc.Show();
q=1;

}
else
{
if(cc.Visible==true)
{
q=1;
}
else
{
cc.Show();
q=1;
}
}
}
{
if(f!=null)
{
f.Close();
}
if(m==0)
{
f6=new Form5();
f6.MdiParent=this;
f6.Show();
m=1;
}
else
{
{
m=1;
}
else
{
f6.Show();
m=1;
}
}
}
{
if(f!=null)
{
f.Close();
}
if(p==0)
{
rep=new Cust_ListReport();
rep.MdiParent=this;
rep.Show();
p=1;
}
else
{
if(rep.Visible==true)
{
p=1;

}
else
{
rep.Show();
p=1;
}
}
}
{
if(f!=null)
{
f.Close();
}
if(k==0)
{
f5=new Form4();
f5.MdiParent=this;
f5.Show();
k=1;
}
else
{
{
k=1;
}
else
{
f5.Show();
k=1;
}
}
}
{
if(f!=null)
{
f.Close();
}
if(w==0)
{
sr=new Stock_Report();
sr.MdiParent=this;
sr.Show();
w=1;
}
else
{
if(sr.Visible==true)
{
w=1;
}
else
{
sr.Show();
w=1;
}

}
}
{
if(f!=null)
{
f.Close();
}
if(t==0)
{
td=new TransactionDetails();
td.MdiParent=this;
td.Show();
t=1;
}
else
{
if(td.Visible==true)
{
t=1;
}
else
{
td.Show();
t=1;
}
}
}
}
}
Form 3

{
this.MaximizeBox=false;
this.MinimizeBox=false;
this.Text="About";
}
private void Form3_DoubleClick(object sender, System.EventArgs e)
{
this.Close();
}
e)
{
Form2.count=0;
}
Customer Demand Form (4)

{
SqlConnection con;
SqlDataAdapter sd;
DataSet ds;
DataTable dt;
SqlDataAdapter sd1;
DataSet ds1;
DataTable dt1;
int sum=0;
SqlDataAdapter sd2;
DataSet ds2;
DataTable dt2;
}
private void Form4_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
Form2.k=0;
}
private void radioButton1_CheckedChanged(object sender, System.EventArgs e)
{
if(radioButton1.Checked==true)
{
groupBox3.Visible=false;
}
}
{
{
groupBox3.Visible=true;
groupBox3.Location=new System.Drawing.Point(272,112);
groupBox3.Size=new System.Drawing.Size(208,128);

}
}
{
{
}
}
{
radioButton1.Checked=true;
textBox3.ReadOnly=true;
comboBox2.Enabled=false;
con=new SqlConnection("server=.;uid=sa;database=gasagency");
sd=new SqlDataAdapter("select * from cust_info",con);
ds=new DataSet();
sd.Fill(ds,"cust_info");
sd.FillSchema(ds,SchemaType.Mapped,"cust_info");
dt=ds.Tables[0];
foreach(DataRow dr in dt.Rows)
{
comboBox1.Items.Add(dr[1].ToString());
}
textBox1.Text=DateTime.Now.ToShortDateString();
textBox5.Text="1";
sd1=new SqlDataAdapter("select * from stock_det",con);
ds1=new DataSet();
sd1.Fill(ds1,"stock_det");
sd1.FillSchema(ds1,SchemaType.Mapped,"stock_det");
dt1=ds1.Tables[0];
foreach(DataRow dr1 in dt1.Rows)
{
comboBox2.Items.Add(dr1[0].ToString());
sum+=Convert.ToInt32(dr1[5].ToString());
}
textBox7.Text=sum.ToString ();
sd2=new SqlDataAdapter ("select * from cust_trans",con);
ds2=new Dataset ();

sd2.Fill (ds2,"cust_trans");
sd2.FillSchema (ds2, SchemaType.Mapped,"cust_trans");

dt2=ds2.Tables [0];
int ma=dt2.Rows.Count;
If (ma==0)
{
textBox3.Text="1";
}
else
{
DataRow dr4=dt2.Rows[ma-1];
int z=1+Convert.ToInt32(dr4[1].ToString());
textBox3.Text=z.ToString();
}

{
this.Close();
}

{comboBox2.Enabled=true;
try
{
string str=comboBox1.SelectedItem.ToString();
DataRow dm=dt.Rows.Find(str);
textBox2.Text=dm[2].ToString();
textBox4.Text=dm[5].ToString();
button1.Enabled=false;
}
catch(Exception ef)
{
MessageBox.Show("No Customer ID Selected");
}
}

{
try
{
SqlCommandBuilder cmd1=new SqlCommandBuilder(sd2);
DataRow d5=dt2.NewRow();
d5[0]=Convert.ToDateTime(textBox1.Text);
d5[1]=textBox3.Text;
d5[2]=comboBox1.SelectedItem.ToString();
{
d5[5]="cash";
d5[6]="";
d5[7]=" ";
d5[8]=" ";
dt2.Rows.Add(d5);
sd2.Update(ds2,"cust_trans");
MessageBox.Show("Transaction completed sucessfully");
this.Close();
}
{

d5[5]="cheque";
if((textBox8.Text.Length!=0)&&(textBox9.Text.Length!=0))
{
d5[8]=dateTimePicker1.Value.ToShortDateString();
dt2.Rows.Add(d5);
this.Close();
}
}
{
d5[5]="Credit Card";
{
d5[8]=dateTimePicker2.Value.ToShortDateString();
dt2.Rows.Add(d5);
this.Close();
}
}
SqlCommandBuilder cmd2=new SqlCommandBuilder(sd1);
string abc=comboBox2.SelectedItem.ToString();
DataRow d6=dt1.Rows.Find(abc);
int z=Convert.ToInt32(d6[5].ToString());
int p=z-1;
d6[5]=p.ToString();
sd1.Update(ds1,"stock_det");
}
catch(Exception ss)
{
MessageBox.Show(ss.Message);
}
}
private void comboBox2_SelectedIndexChanged(object sender, System.EventArgs e)
{
DataRow dr2=dt1.Rows.Find(str);
textBox6.Text=dr2[3].ToString();
}
private void textBox10_KeyPress(object sender, System.Windows.Forms.KeyPressEventArgs e)

{
int c=Convert.ToInt32(Microsoft.VisualBasic.Strings.Asc(e.KeyChar));
if((c==32)||(c==46)||(c==8)||(c>=48 && c<=57))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
Private void textBox8_KeyPress(object sender, System.Windows.Forms.KeyPressEventArgs e)

{
if((c==32)||(c==46)||(c==8)||(c>=48 && c<=57))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c==32)||(c==46)||(c==8)||(c>=65 && c<=90)||(c>=97 && c<=122))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c==32)||(c==46)||(c==8)||(c>=65 && c<=90)||(c>=97 && c<=122))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
}
}
Stock Details Form(5)

{

SqlConnection con;
SqlDataAdapter sd;
DataSet ds;
DataTable dt;
Form6 f7;
int sum=0;
editstock ed;
int z=0;
int p=0;
int a=0;
}
e)
{
Form2.m=0;
}
{
datafill();
sd=new SqlDataAdapter("select * from stock_det",con);
ds=new DataSet();
sd.Fill(ds,"stock_det");
dt=ds.Tables[0];
foreach(DataRow dr1 in dt.Rows)
{
sum+=Convert.ToInt32(dr1[5].ToString());
z+=Convert.ToInt32(dr1[3].ToString());
}
textBox1.Text=sum.ToString();
}
private void datafill()
{
ds=new DataSet();
dt=ds.Tables[0];
dataGrid1.DataSource=dt;
dataGrid1.Refresh();
}
{
f7=new Form6();
f7.myeve+=new mydel(datafill);
f7.Show();
}
{
this.Close();
Form2.m=0;
}
{
ed=new editstock();
ed.myeve1+=new mydel2(datafill);
for(int i=0;i<dt.Rows.Count;i++)
{
bool bin=dataGrid1.IsSelected(i);
if(bin==true)

{
DataRow dr=dt.Rows[i];
ed.dateTimePicker1.Value=Convert.ToDateTime(dr[1].ToString());
ed.textBox1.Text=dr[2].ToString();
ed.Show();
}
}
}
}
}
ADD NEW STOCK FORM(6)

namespace gasagencyproj
{
public delegate void mydel();
{
public event mydel myeve;
SqlConnection con;
SqlDataAdapter sd;
DataSet ds;
DataTable dt;
int z;
}
{
this.Close();
}
{
ds=new DataSet();
dt=ds.Tables[0];
int s=dt.Rows.Count;
if(s>0)
{
DataRow dr=dt.Rows[s-1];
int d=1+Convert.ToInt32(dr[0].ToString());
textBox1.Text=d.ToString();
}
else
{
textBox1.Text="1";
}
}
{
try
{
SqlCommandBuilder cmd=new SqlCommandBuilder(sd);
DataRow dr1=dt.NewRow();

dr1[0]=textBox1.Text;
dt.Rows.Add(dr1);
sd.Update(ds,"stock_det");
MessageBox.Show("new stock successfully added");
ActiveForm.Close();
myeve();
}
catch(Exception g)
{
MessageBox.Show(g.Message);
}
}
private void textBox4_KeyUp(object sender, System.Windows.Forms.KeyEventArgs e)
{
int a=Convert.ToInt32(textBox3.Text);
int b=Convert.ToInt32(textBox4.Text);
int p=a*b;
textBox5.Text=p.ToString();
}}}
NEW CONNECTION FORM(NEW Con)

public class NewCon : System.Windows.Forms.Form
{
SqlConnection con;
SqlDataAdapter sd;
DataSet ds;
DataTable dt;
}
private void NewCon_Load(object sender, System.EventArgs e)
{
ds=new DataSet();
dt=ds.Tables[0];
int c=dt.Rows.Count;
if(c>0)
{
DataRow dr=dt.Rows[c-1];
int d=1+Convert.ToInt32(dr[1].ToString());
textBox2.Text=d.ToString();
}
else
{
textBox2.Text="101";
}
comboBox1.SelectedItem=comboBox1.Items[0];
comboBox2.SelectedItem=comboBox2.Items[0];
radioButton1.Checked=true;
textBox3.MaxLength=25;

textBox3.Clear();
}
{
{
}
}
{
this.Close();
}
{
{
this.groupBox3.Location = new System.Drawing.Point(248, 64);
}
}
{
{
}
}
private void NewCon_Closing(object sender, System.ComponentModel.CancelEventArgs
e)
{
Form2.i=0;
}
private void textBox3_KeyPress(object sender,
System.Windows.Forms.KeyPressEventArgs e)
{
if((c>=65 && c<=90)||(c>=97 && c<=122)||(c==32)||(c==46)||(c==8))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{

if((c==32)||(c==46)||(c==8)||(c>=48 && c<=57)||(c>=65 && c<=90)||
(c>=97)&&(c<=122))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c==32)||(c==46)||(c==8)||(c>=48 && c<=57))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c==32)||(c==46)||(c==8)||(c>=65 && c<=90)||(c>=97 && c<=122))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c==32)||(c==46)||(c==8)||(c>=48 && c<=57))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c==32)||(c==46)||(c==8)||(c>=65 && c<=90)||(c>=97 && c<=122))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}

{
{
errorProvider1.SetIconAlignment(textBox3,ErrorIconAlignment.BottomLeft);
errorProvider1.SetError(textBox3,"the name field cannot be left blank");
textBox3.Focus();
}
else
{
errorProvider1.Dispose();
}
int f=Convert.ToInt32(dateTimePicker1.Value.Year);
int z=Convert.ToInt32(DateTime.Now.Year);
int p=z-f;
if(p<18)
{
errorProvider2.SetIconAlignment(dateTimePicker1,ErrorIconAlignment.MiddleRight);
errorProvider2.SetError(dateTimePicker1,"Age cannot be less than 18 years");
}
else
{
}
{
errorProvider3.SetError(textBox4,"the address field cannot be left blank");
}
else
{
}
if((textBox5.Text.Length==0)||(textBox5.Text.Length<10))
{
errorProvider4.SetIconAlignment(textBox5,ErrorIconAlignment.MiddleRight);
errorProvider4.SetError(textBox5,"the phone number must not be 0 and cannot be
less than 10 digits");
}
else
{
}
{
errorProvider5.SetIconAlignment(textBox6,ErrorIconAlignment.MiddleRight);
errorProvider5.SetError(textBox6,"the certificate number cannot be left blank");
}
else
{
}
{
{
errorProvider6.SetError(textBox12,"the card number cannot be left blank");
}
else
{

}
{
errorProvider7.SetError(textBox13,"Bank name cannot be left blank");
}
else
{
}
}
{
{
errorProvider8.SetError(textBox10,"the cheque number cannot be left blank");
}
else
{
}
{
errorProvider9.SetError(textBox11,"the bank name cannot be left blank");
}
else
{
}
}
if((textBox3.Text.Length>0)&&(p>18)&&(textBox4.Text.Length>0)&&(textBox5.Text.Le
ngth==10)&&(textBox6.Text.Length!=0))
{
SqlCommandBuilder cmd=new SqlCommandBuilder(sd);
DataRow dr1=dt.NewRow();
dr1[3]=comboBox1.SelectedItem;
dr1[4]=dateTimePicker1.Text.ToString();
dr1[7]=comboBox2.SelectedItem;
{
dr1[10]="cash";
dr1[11]=" ";
dr1[12]=" ";
dr1[13]=" ";
dt.Rows.Add(dr1);
sd.Update(ds,"cust_info");
MessageBox.Show("new customer sucessfully added");
this.Close();
}

{
dr1[10]="cheque";
{
dt.Rows.Add(dr1);
this.Close();
}
}
{
dr1[10]="Credit Card";
{
dt.Rows.Add(dr1);
this.Close();
}
}
}
}
{
if(e.KeyChar>='0' && e.KeyChar<='9')
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
}
}
Stock Report Form
public class Stock_Report : System.Windows.Forms.Form

{
private CrystalDecisions.Windows.Forms.CrystalReportViewer crystalReportViewer1;
}
private void Stock_Report_Load(object sender, System.EventArgs e)
{
CrystalReport3 r3=new CrystalReport3();
crystalReportViewer1.ReportSource=r3;
}
private void Stock_Report_Closing(object sender, System.ComponentModel.CancelEventArgs e)

{
Form2.w=0;
}
}
}

TRANSACTION DETAILS FORM
public class TransactionDetails : System.Windows.Forms.Form

{
SqlConnection con;
SqlDataAdapter sd;
DataSet ds;
DataTable dt;
int u=1;
}
private void TransactionDetails_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
Form2.t=0;
}
{
u=1;
listView1.Items.Clear();
int c=Convert.ToInt32(dateTimePicker1.Value.Day);
int a=Convert.ToInt32(dateTimePicker1.Value.Month);
int b=Convert.ToInt32(dateTimePicker1.Value.Year);
int d=Convert.ToInt32(dateTimePicker2.Value.Day);
int g=Convert.ToInt32(dateTimePicker2.Value.Month);
int f=Convert.ToInt32(dateTimePicker2.Value.Year);
if((c==d)||(c<d)||(c>d))
{
if((a==g)||(a<g)||(a>g))
{
if((b==f)||(b<f))
{
if((a>g)||(c>d))
{
MessageBox.Show("From Date cannot be greater than To Date");
}
else
{
for(int i=0;i<dt.Rows.Count;i++)
{
DataRow dr=dt.Rows[i];
DateTime tim=Convert.ToDateTime(dr[0].ToString());
int j=tim.Day;
int k=tim.Month;
int l=tim.Year;
if((j<=c && j<=d)||(j>c && j<=d)||(j>d))
{
if((k<=a && k<=g)||(k>a && k<=g)||(k>g))
{
if((l<=b && l<=f)||(l>b && l<=f))
{
groupBox1.Text="Following Is The List Of Transactions That Has Taken Place";
listView1.Items.Add(u.ToString());
string str=dr[0].ToString();
string abc=str.Substring(0,9);
listView1.Items[i].SubItems.Add(abc);
listView1.Items[i].SubItems.Add(dr[1].ToString());

u++;
}
else
{
groupBox1.Text="No Records Found For The Given Date";
}
}
}
}
}
}
else
{
MessageBox.Show("From Date Cannot Be Greater Than To Date");
}
}
else
{
}
}
else
{
}
}
{
this.Close();
}
private void TransactionDetails_Load(object sender, System.EventArgs e)
{
sd=new SqlDataAdapter("select * from cust_trans",con);
ds=new DataSet();
sd.Fill(ds,"cust_trans");
dt=ds.Tables[0];
listView1.View=View.Details;
listView1.GridLines=true;
listView1.Columns.Add("NO",50,HorizontalAlignment.Left);
listView1.Columns.Add("Trans_Date",100,HorizontalAlignment.Center);
listView1.Columns.Add("Trans_ID",90,HorizontalAlignment.Center);
listView1.Columns.Add("Cust_ID",90,HorizontalAlignment.Center);
listView1.Columns.Add("Pay_Mode",90,HorizontalAlignment.Center);
listView1.Columns.Add("Amount",90,HorizontalAlignment.Center);
}
}
}
CUSTOMER DETAILS FORM

public class cust_details : System.Windows.Forms.Form
{
SqlConnection con;
SqlDataAdapter sd;

DataSet ds;
DataTable dt;
Edit_Cust cust;
}
private void cust_details_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
Form2.q=0;
}
private void cust_details_Load(object sender, System.EventArgs e)
{
ds=new DataSet();
sd.FillSchema(ds,SchemaType.Mapped,"cust_info");
dt=ds.Tables[0];
foreach(DataRow dm in dt.Rows)
{
comboBox1.Items.Add(dm[1].ToString());
}
textBox10.Visible=false;
label14.Visible=false;
button3.Enabled=false;
}
{
try
{
DataRow dr=dt.Rows.Find(str);
textBox1.Text=dr[2].ToString();
string ms=dr[4].ToString();
string cd=ms.Substring(0,9);
textBox4.Text=cd;
if(textBox8.Text=="cash")
{

}
if(textBox8.Text=="Credit Card")
{
textBox10.Visible=true;
label14.Visible=true;
label14.Text="Card_No";
label16.Text="Valid_Upto";
}
if(textBox8.Text=="cheque")
{
label14.Text="Ch.No";
label16.Text="Date_of_issue";
}
button3.Enabled=true;
}
catch(Exception b)
{
MessageBox.Show("no customer id selected");
}
}
{
this.Close();
Form2.q=0;
}
{
DataRow dm=dt.Rows.Find(str);
cust=new Edit_Cust();
cust.MdiParent=this.MdiParent;
cust.textBox1.Text=dm[1].ToString();
string abc=dm[0].ToString();
string s=abc.Substring(0,9);
cust.textBox7.Text=s;
cust.comboBox2.Items.Add("Male");
cust.comboBox2.Items.Add("female");

cust.comboBox2.SelectedItem=dm[3].ToString();
cust.comboBox1.Items.Add("Ration Card");
cust.comboBox1.Items.Add("Electricity bill");
cust.comboBox1.Items.Add("Telephone Bill");
cust.comboBox1.SelectedItem=dm[7].ToString();
cust.dateTimePicker1.Value=Convert.ToDateTime(dm[4].ToString());
this.Close();
cust.Show();
}
}
}
CUSTOMER LIST REPORT FORM

public class Cust_ListReport : System.Windows.Forms.Form
{
private CrystalDecisions.Windows.Forms.CrystalReportViewer crystalReportViewer1;
}
private void Cust_ListReport_Closing(object sender, System.ComponentModel.CancelEventArgs e)
{
Form2.p=0;
}
private void Cust_ListReport_Load(object sender, System.EventArgs e)
{
CrystalReport1 re=new CrystalReport1();
crystalReportViewer1.ReportSource=re;
this.Size=this.MdiParent.Size;
this.WindowState=System.Windows.Forms.FormWindowState.Maximized;
}
EDIT CUSTOMER FORM

public class Edit_Cust : System.Windows.Forms.Form
{
SqlConnection con;
}
private void Edit_Cust_Load(object sender, System.EventArgs e)
{
errorProvider1.BlinkStyle=ErrorBlinkStyle.AlwaysBlink;
}
{
if((c>=65 && c<=90)||(c>=97 && c<=122)||(c==32)||(c==8)||(c==46))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{

if((c>=65 && c<=90)||(c>=97 && c<=122)||(c>=48 && c<=57)||(c==32)||(c==8)||
(c==46))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c>=48 && c<=57)||(c==32)||(c==46)||(c==8))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
if((c>=65 && c<=90)||(c>=97 && c<=122)||(c>=48 && c<=57)||(c==32)||(c==8)||
(c==46))
{
e.Handled=false;
}
else
{
e.Handled=true;
}
}
{
int a=Convert.ToInt32(dateTimePicker1.Value.Year);
int b=Convert.ToInt32(DateTime.Now.Year);
int q=b-a;
if(q<18)
{
errorProvider1.SetIconAlignment(dateTimePicker1,ErrorIconAlignment.BottomLeft);
errorProvider1.SetError(dateTimePicker1,"The age cannot be less than 18 years");
}
else
{
SqlCommand cmd=new SqlCommand("update cust_info set
cust_name=@name,cust_sex=@sex,cust_address=@address,cust_dob=@dob,cust_phone=@phone,cust_certificate=@c
ertificate,cert_number=@number where cust_id='"+textBox1.Text+"'",con);
cmd.Parameters.Add("@name",textBox6.Text);
cmd.Parameters.Add("@sex",comboBox2.SelectedItem.ToString());
cmd.Parameters.Add("@address",textBox2.Text);
cmd.Parameters.Add("@dob",dateTimePicker1.Value.ToShortDateString());
cmd.Parameters.Add("@phone",textBox5.Text);
cmd.Parameters.Add("@certificate",comboBox1.SelectedItem.ToString());
cmd.Parameters.Add("@number",textBox4.Text);
con.Open();
cmd.ExecuteNonQuery();
con.Close();

MessageBox.Show("Customer record sucessfully updated");
this.Close();
}
}
{
this.Close();
}
}
}
EDIT STOCK FORM

namespace gasagencyproj
{
public delegate void mydel2();
public class editstock : System.Windows.Forms.Form
{
SqlConnection con;
public event mydel2 myeve1;
}
private void editstock_Load(object sender, System.EventArgs e)
{
}
{
this.Close();
}
{
SqlCommand cmd=new SqlCommand("update stock_det set
stock_date=@da,no_of_item=@item,item_price=@price,tot_amount=@amount where
stock_id=@stock",con);
cmd.Parameters.Add("@stock",textBox4.Text);
cmd.Parameters.Add("@da",dateTimePicker1.Value.ToShortDateString());
cmd.Parameters.Add("@item",textBox1.Text);
cmd.Parameters.Add("@price",textBox2.Text);
cmd.Parameters.Add("@amount",textBox3.Text);
con.Open();
cmd.ExecuteNonQuery();
con.Close();
MessageBox.Show("stock sucessfully updated");
ActiveForm.Close();
myeve1();
}
Private void textBox2_KeyDown(object sender, System.Windows.Forms.KeyEventArgs e)
{
if(e.KeyCode==Keys.Enter)
{
int c=Convert.ToInt32(textBox1.Text);
int d=Convert.ToInt32(textBox2.Text);
int z=c*d;
textBox3.Text=z.ToString();
}
}

10. VALIDATION CHECKS

System validation checks the quality of the software in both simulated and live
environments. First the software goes through a phase (often referred as alpha testing)

in which error and failures based on simulated user requirements are verified and
studied. The modified software is then subjected to phase (called beta testing) in the
actual user site or a live environment. The system is use regularly with live
transaction. After a schedule time, failures and errors are documented and final
correction and enhancements are made before the package is released for use.
Validation refers to a different set of activities that ensure that the software that has
been built is traceable to customer requirement. Validation is probably the most
important and ironically, the most often neglected section of the software requirement
specification. How do we recognize a successful implementation? What classes of
tests must be conducted to validate function, performance and constraints? We
neglected the section, because completing it demands a thorough understanding of
software requirements – something that we often do not have at this stage. Yet,
specification of validation criteria acts as an implicit review of all other requirements.
It is essential that time and attention is given in this section. At the culminating of
integration testing, software is completely assembled at a package, interfacing error
have been uncovered and corrected, and a final series of software test – validation
testing may begin.

11. TESTING
11.1TESTING
Testing plays a critical role in quality assurance of the software. Testing is a dynamic
method for verification and validation. With the help of testing we observe the failure
of the system in terms of logical and runtime errors. The testing process can deduce
the presence of fault in the system; however, separate activities have to be performed
to identify the faults.
As the goal of testing is to detect any errors in the programs, different flavor of testing
are often used. Unit testing are used to test module or a small collection of modules
and the focus is on detecting coding errors in modules. During integration testing
modules are combined into sub-system, which are then tested. The goal here is to test
the system design. In system testing and acceptance testing, the entire system is tested.
The goal here is to test the fulfillment of the requirement. Structural testing can be
used for unit testing while at higher level mostly functional testing is used.
The objective for test case design is to derive asset of test that has the highest
likelihood for uncovering errors in the software. To accomplish this objective, two
different categories of test case design techniques are used. White-box testing and
black-box testing.
White-box test focuses on the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to
ensure that all statement in the program control structure. Test cases are derived to
ensure that all statement in the program has been executed at least once during testing
and that all logical conditions have been exercised. Basis path testing, a white box
technique, makes use of program graphs (or graph matrices) to derive the set of
linearly independent test that will ensure coverage. Condition and data flow testing
further exercising degrees of complexity.
Black-box test are designed to uncover errors functional requirement without regard to
the internal workings of a program. Black-box testing techniques focus on the
information domain of the software, deriving test cases by partitioning the input and
output domain of a program in manner that provides through test coverage. The black-
box test is used to demonstrate that software functions are operational, that input is
properly produced, and that the intergrity of external information are maintained. A
black-box test examines some fundamental aspect of a system with little or no regard
for the integral logical structure of the software.

Graph based testing methods explore the relationship between and behavior of
program objects. Equivalence partitioning divides the input classes of data are likely
to exercise specific software function. Boundary values analysis probes the program’s
ability to handle data at the limits of acceptability.
Specialized testing methods encompass broad arrays of software capabilities and

application areas. Graphical user interface, client/server architectures documentation
and help facilities, and real-time systems each require specialized guidelines and
techniques for software testing.
Test Information Flow
Evaluatio
Software n
Configuration
Test Results
Errors
Error
Testing Rate Data
Expected Results
Debug
Reliability
Test Configuration Model
Predicated Reliability Correction
A strategy for software testing may also be viewed in the context of the spiral. Unit
testing begins at the vortex of the spiral and, concentrates on each unit, component of
the software as implemented in source code. Testing progresses moving outward along
the spiral to integration testing, where the focus is on designed the construction of the
software architecture. Taking another turn outward on spiral, we encounter validation
testing, where requirements established as part of software requirements analysis are
validated against the software that has been constructed. Finally, we

arrive at system testing, where the software and other system elements are tested as a
whole. To test computer software, we spiral out along stream lines that broaden the
scope of testing with each turn.
Considering the process from a procedural point of view, testing within the context of
software engineering is actually a series of four steps that are implemented
sequentially. The steps are shown in Figure. Initially, tests focus on each component
individually, ensuring that it functions properly as unit. Hence, the name unit testing.
Unit testing makes heavy use of white-box testing techniques, exercising specific
paths in module’s control structure to ensure complete coverage and maximum error
detection.
System Testing
Validation Testing
Integration Testing
Unit Testing
h Code
Design
System Engineering
Nest, components must be assembled or integrated to form the complete software

package. Integration testing addresses the issues associated with the dual problems of
verification and program construction. Black-box case design techniques are the most
prevalent during integration, although a limited amount of white-box testing may be
used to ensure coverage of major control paths. After the software has been integrated
(constructed), a set of high-order tests conducted. Validation criteria (established
during requirements analysis) must be tested. Validation testing provides final
assurance that software meets all functional, behavioral, and performance
requirements. Black-box testing techniques are used exclusively during validation.

Software
Configuration Test Results
Evaluatio
n
Errors
Error
Rate Data
Testing
Expected Results Debug
Reliability
Model
Test Configuration
Correction
Predicated Reliability

12. IMPLEMENTATION
Implementation is the process of having systems personnel check out and put new
equipment into use, train users, install the new application and construct any files of
data needed to use it. This phase is less creative than system design. Depending on the
size of the organization that will be involved in using the application and the risk
involved in its use, systems developers may choose to test the operation in only one
area of the firm with only one or two persons. Sometimes, they will run both old and
new system in parallel way to com-pare the results. In still other situations, system
developers stop using the old system one day and start using the new one the next.

13. SECURITY MEASURES TAKEN

In security measure taken we have discussed what security measures we should apply
on “NK GAS AGENCY”. What kind of security measures should be applied for the
security of databases and how we manage it?
Although there are many measures of software quality, correctness, maintenance,
integrity, and usability provide useful indicators for the project team.
Software integrity has become increasingly important in the age of hackers and
firewalls. The attributes measure a system ability to stand with attacks to its security.
Attacks can be made on all three components of software:
• Program
• Data
• Document
To measures integrity we must be defined two additional attributes:
• Threat
• Security
Threat is the probability that an attack of a specific type will occurs with in a given
time. Security is the probability that the attack of a specific type will be repelled.
To tackle with some of the problems mentioned above we will develop a user
authentication module that uniquely identifies the Administrator, valid or invalid
users.

14. COST ESTIMATION

Software cost and effort estimation will never be an exact science. To many variables-
Human, Technical, environmental, Political can affect the ultimate cost of software
and effort applied to develop it. However, software project estimation can be
transformed from a black art to a series of systemic steps that provides estimates with
acceptable risk.
To achieve reliable cost and effort estimates, a number of options arise:
 We can achieve 100% accurate estimates after the project is complete.
 Base estimates on similar projects that have already been completed.
 Use relatively simple decomposition techniques to generate project cost and

efforts and
 Use one or more empirical models for software cost and effort estimation.
The first option is that the cost estimates must be provided “up front”. However, we
should recognize that the longer we wait. The second option can work reasonably
well, if the current project is quite similar to past efforts and other project influences.
The remaining options are viable approaches to software project estimation. Ideally,
the techniques noted for each option should be applied in tandem.
Each of the viable software cost estimation option is only as good as the historical
data used to seed the estimate.

15. FUTURE SCOPE

Despite a lot of support and services are being provided by the software, it may have
the some limitations which can be overcome by adopting the following measures such
as:
• Can provide record based security.
• Can have better record traversal mechanism.
• Can provide backup for records.
• Can provide different rights to different users.
Some of the improvements that have been predicted in future are as follows:
1. Create a Asp page in which an agency administrator can enter a month and year.
System will display the sales data based on the month and year entered by the
administrator of agency.
2. Create a monthly report providing the details about the status of items in the
agency. The report should be displayed in the following format:
NK Gas Agency
Booking Details for the Month- Year-----
Card No Cylinder Description Quantity on Hand
3. Create a daily report providing the details of the transactions for each day in the
OBS. The report should be displayed in the following format:
NK Gas Agency
Transaction Details
Card No Tran no Transaction Quantity Amount

Date

4. Create a report that will be given as a bill to the customer after the customer
purchases the required items. The report should be displayed in the following
format:
NK Gas Agency
Faridabad, India
Date: --/--/--
Customer Number:
Customer Name:
Card-No Cylinder Description Quantity Amount
Total Amount:

16. BIBLIOGRAPHY
S.NO TITLE AUTHOR
1. VB.NET on the Edge Rick Leinecker.
2. Programming Microsoft Visual Basic.Net (Microsoft Press) Francesco Balena.
3. Introducing .NET WROX publications
4. Upgrading Microsoft Visual Basic .NET (Microsoft Press) John Smiley.

Authors: Ed Robinson, Ian Oliver and Michael Bond. Learn
to Program with Visual Basic .NET (Osborne McGrew-Hill),
5. Internet Explorer http://www.vbnetdesign.com
6. Internet Explorer http://www.google.com
7. Internet Explorer http://www.microsoft.com/v

b.net
8. Internet Explorer http://www.databasejournal.com

Synopsis of Project

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Synopsis of Project

Transféré par

Droits d'auteur :

Formats disponibles

NK GAS AGENCY-BOOKING SYSTEM Version1.

Also, the system is supposed to possess efficient, effective as well as secure

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

After a lot of analysis we came to the conclusion that ‘MSSQLServer2000’ will be

5.1 SYSTEM ANALYSIS

Review & Validation

Review & Validation

Detailed Design Global Implementation Specifications &

Code and Debugging

Review & Validation Coding & Debugging

Review & Validation Maintenance

Process Engineering of Application Software (Software Development Life cycle)

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Success of a system depends largely on how accurately a problem is defined,

Tasks, which are performed as analyst:

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Each of these questions must be answered carefully.

6.1 TECHNICAL FEASIBILITY

1. Is a project technically feasible?

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

risks be overcome? The feasibility team ought to negative answers; a reduction is

6.2 ECONOMICAL FEASIBILITY

1. Is it my software is economically feasible?

6.3 OPERATIONAL FEASIBILITY

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Suggested Configuration of Windows clients:-

Microprocessor - Pentium-2 class processor, 450 megahertz (MHz)

Windows 2000XP/Windows 2000 NT Operating System

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Faster Operating System

To a large extent, multitasking operating system relay on system hardware to

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

 To identify the Software Components which satisfy the System Design?

Identify Relevant Interfaces

Elements of Specifications required are

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

STEPS IN SYSTEM DESIGN

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

8.2 DATA FLOW DIAGRAM

A square defines a source (originator) or destination of system data.

An arrow identifies data flow-data in motion. It is a pipeline through which

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

An open Rectangle is data store-data at rest, or temporary repository of data. Open

Information Flow of Data for Testing

Software Test Results Evaluatio

Information Flow of Data Testing

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Required for Booking

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Customer Release Release

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Customer Demand Form

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

AL-FALAH SCHOOL OF ENGINEERING & TECHNOLOGY,FARIDABAD

Customer _ List Report