Call Us011-4166-8088, 90155-96280, 9313565406

Send Sms'PROJHELP' to 93135-65406

Mail Usinfo@projecthelpline.in

SIKKIM MANIPAL UNIVERSITY

PROJECT REPORT

ON

“MTNL BILLING SYSTEM”

Submitted in partial fulfillment of the requirements for qualifying

MSC(IT)

SUBMITTED BY

NAME :

ENROLLMENT NO :

UNDER SUPERVISION OF:

Declaration

I here by declare that the project report entitled “(Title of the Project)”
Submitted in partial fulfillment and requirement for the degree of “(Course Name)” to Sikkim Manipal University, India is my original work and not submitted for the award of any other degree, diploma, fellowship, or any similar title of prizes.

Place :……………………. (Name of Student)

Date :……………………. Reg. No.

Course-Semester

Examiner’s Certificate

This is to certify that project report submitted by “(Name of Student)” entitled “(Name of Project)” is approved and is acceptable in quality and form.

Internal Examiner External Examiner

Name of Examiner
Designation
College / Organization

Ref. No:___________ Date:_____________

Certificate of Guide

This is to certify that project report entitled “(Name of Project)”, Submitted in partial fulfillment and requirement for the degree of “(Course Name)” to Sikkim Manipal University, India by “(Name of the Student)” has worked under my supervision and guidance and that no part of this report has been submitted for the award of any other degree, diploma, fellowship, or any similar titles or prizes and the work has not been published in any journal or magazine.

Certified By-

Name of the Project Guide
Designation
College / Organization

TABLE OF CONTENTS/INDEX WITH PAGE NUMBERING

Acknowledgement 3

Declaration 4

1. Introduction and objectives

1.1 Introduction ………………………………………………………………8
1.2 Objectives of the Project …………………………………………………9
1.3 Drawbacks of current manual system …………………………..…….10
1.4 Project Category ………………………….……………………………..11
1.5 Software Hardware Requirements……………………………..………12

2. System Study
2.1 Preliminary Investigation…………………………………………….….22
2.2 System Development Life Cycle………………………………..……..23
2.3 Feasibility Study…………………………………………..………….…26
2.4 Economic Feasibility……………………………………………………28
2.5 Technical Feasibility……………………………………………….……31
2.6 Operational Feasibility …………………………………………………34
2.7 Feasibility Report………………………………………………………..34

3. System Analysis
3.1 Importance of Computerized MTNL Billing ………………………..…37
3.2 Principles of System Analysis…………………………………………..38

4. System Design
4.1 System Design…………………………………………………………..40
4.2 E-R Diagram …………………………………………………….……….46
4.3 Context Level DFD……………………………………………………….47
4.4 Modules …………….. ……………………………………………………52
4.5 Process Logic……………………………………………………………54
4.6 Tools/ Platform, Hardware and Software Requirement …….……….55
4.7 Scheduling ………………………………………………………………56

5. System Development
5.1 Source Code ……………………………………………………………59
5.2 Code Efficiency ……………………………………………………..…94
5.3 Optimization of Code…………………………………………………..94

6. Testing
6.1 Testing Phases………………………………………………………….96
6.2 Testing Levels ………………………….………..………………………97
6.3 Test Cases ………………………………………………………….…102

7. Post Implementation Maintenance and Review

7.1 System Implementation maintenance and review….…………….110
7.2 Hardware Evaluation Factors………………………………………..111
7.3 Evaluation Factors For Hardware……………………………..…….111
7.4 Evaluation Factors For Software……………………………..…….112
7.5 Conversion and Training……………………………………………..113
7.6 Training Needs …………………………………………………….…114

8. Cost Estimation for the Project…………………………………………115

9. GANTT & PERT CHART…………………………………………………116

10. Security and Validations………………………………………………….119

11. Scope of Future Application…………………………………………….120

12. Conclusion………………………………………………………….……..121

13. Bibliography……………………………………………………………….122

1. INTRODUCTION

This is a Project work undertaken in context of partial fulfillment of the BCA. MTNL has recognized that IT is the key to future business success. IT is being implemented as the backbone for running customer friendly services. Several IT systems and accounting and billing systems are already operational at MTNL.

Existing MTNL billing system had problems right from the beginning. Not only has the billing system worked erratically since, but also following the launch of services the subscribers (not many to begin with) were also not issued bills for months together. All due to some software problems,” the sources noted. The billing system was working slowly and it was not possible to generate automatic disconnection list due to non-payment, complaint details etc. with the result that timely disconnection was not possible. All these factors resulted in heavy outstanding.

Apart from this, many subscribers continued to make heavy calls and then migrate to other mobile operators, leaving heavy outstanding amounts with MTNL. They pointed out the problems in the billing system that continued and these include delayed implementation of roaming module, provisioning of credit control and service interface which continues to throw up sporadic mistakes in billing generation. The present system also does not allow for monitoring of cases with outstanding payments, automatic generation of payment reminders, automatic disconnection and reconnections. With the result, the outstanding dues of MTNL have only mounted.

1.2 OBJECTIVES OF THE PROJECT

This project is designed to achieve the following objectives:

To make the processing of MTNL Billing system easier & faster. Also to generate various types of reports requested by the user of the application. It contains the following features:

The whole system should be menu driven & the main menu should be displayed automatically as soon as the user logon succeeds.

The software must have a user-friendly interface & appealing appearance to ease the work of the end users.

The system should be able:
• To maintain consumers details
• To maintain bills paid by the consumers
• To add complaints, to assign complaints to the engineers and update the status of the complaints.
• To add new installations and connections.
• Update disconnections.

Above all the software system should be able to eliminate all the paper work required in implementation the task of data maintenance, which previously was tedious, time consuming and error prone.

1.3 DRAWBACKS OF CURRENT MANUAL- SYSTEM

 The current manual system has a lot of paper work and it does not deal with exact details.
 To maintain the records of sale and service manually, is a Time-consuming job.
 With the increase in database, it will become a massive job to maintain the database.
 Requires large quantities of file cabinets, which are huge and require quite a bit of space in the office, which can be used for storing records of previous claims.
 Lack of security for the records, anyone disarrange the records of your system.

ESTABLISH THE NEED OF NEW SYSTEM

1. Problem of Reliability: Current system is not reliable. It seems to vary in quality from one month to the next. Sometimes it gives good output, but sometimes the output is worst.

2. Problem of Accuracy: There are too many mistakes in reports.

3. Problem of timeliness: In the current system the reports and output produced is mostly late and in most of the cases it is useless because it is not on time.

4. Problem of Validity: The output and reports mostly contains misleading information. The customer’s information is sometimes not valid.

5. Problem of Economy: The current system is very costly. We have to spend lots of money to keep the system up and going, but still not get the desired results.

6. Problem of Capacity: The current system is suffering from problem of capacity also. The staff for organization is very less and the workload is too much. Few peoples cannot handle all the work.

1.4 PROJECT CATEGORY

Business Application (RDBMS) Expert Systems:

This Project is coupled with material on how to use the various tool, sub sets available in VB.Net and SQL Server. The need of today’s software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications.

These applications give users the power and ease of a GUI with the multi user capabilities of Novell, UNIX or WinNT based RDBMS engines such as SQL Server.

All the important coding techniques used by programmers, in OOPS based coding is brought out in full and in great detail.

1.5 SOFTWARE & HARDWARE REQUIREMENTS

The need of today’s software development is competence in a GUI based front-end tool, which can connect to Relational Database engines. This gives the programmer the opportunity to develop client server based commercial applications.

FRONT END

.NET programming tools are complete programming environments. It allows programmers to build a GUI program using the various on-screen controls such as buttons, text, menus, boxes etc. These controls are placed on a form and then the processing details related with each control are filled in.

In the business world, competitive strategies have become the order of the day to improve quality, cut costs and provide a high response customer service base. Most organizations today need to be market driven and do a lot of value addition to their products and services. This naturally calls for rational decision making, which requires information. Information Technology or IT provides that effective channel to support and implement this strategy. Client/Server is the technology that empowers the desktop, thus setting a trend for the way successful organizations will use technology in the next decade

INTRODUCTIONTO.NET

What is .NET?
• A vision of how information technology will evolve
• A platform that supports the vision
• A business model of software as a service

1. A Vision.
• Web sites will be joined by Web services
• New smart devices will join the PC
• User interfaces will become more adaptable and customizable
• Enabled by Web standards

2. A Platform.
• The .NET Framework
• Visual Studio.NET
• .NET Enterprise Servers
o Database, Messaging, Integration, Commerce, Proxy, Security, Mobility, Orchestration, Content Management
• .NET Building Block Services
o Passport
o .NET My Services (“Appin”)
• Goal: make it incredibility easy to build powerful Web applications and Web services

3. A business model.
• Software as a service
• Subscription-based services
• Application hosting, e.g. bCentral

Interoperability: Web languages and protocols must be compatible with one another independent of hardware and software.

Evolution: The Web must be able to accommodate future technologies. Encourages simplicity, modularity and extensibility.

Decentralization: Facilitates Scalability and Robustness.

Web Services
• A programmable application component accessible via standard Web protocols
• The center of the .NET architecture
• Exposes functionality over the Web
• Built on existing and emerging standards are HTTP, XML, SOAP, UDDI, WSDL.

The .NET Framework

What is the .NET Framework?
• A set of technologies for developing and using components to create:
o Web Forms
o Web Services
o Windows Applications
• Supports the software lifecycle
o Development
o Debugging
o Deployment
o Maintenance

• Application Architectures
o The Different types of Applications may vary from single-tier desktop applications (applications that follow the single-tier architecture) to multi-tier applications (applications that follow the two-, three, or n-tier architecture)
o Single-tier architecture
 A single executable file handles all functions relating to the user, business, and data service layers.
o Two-tier architecture
 Divides an application into the following two components:
 Client
 Server
o Three-tier architecture
 All the three service layers reside separately, either on the same machine or on different machines.
o n-tier architecture
 Uses business objects for handling business rules and data access.
 Has multiple servers handling business services.

The .NET Initiative

• The introduction of the Internet and its rapid growth in the recent past has led to the development of a number of new Technologies.
• One of the most important requirements of such applications is the ability to interchange information across platforms and to benefit from the functionality provided by other applications.
• In the current scenario, although applications serve organization-specific requirements, they are not interoperable. Microsoft has introduced the .NET initiative with the intention of bridging the gap in interoperability between applications.
• The .NET initiative offers a complete suite for developing and deploying applications, which consists of the following:
o NET products: Microsoft has already introduced Visual Studio .NET, which is a tool for developing NET applications by using programming languages such as Visual Basic, C#, and Visual C++.
o NET services: Microsoft is coming up with its own set of Web services, known as My Services. These services are based on the Microsoft Passport Authentication service, the same service that is used in Hotmail.

Explanation of the .NET Framework
• Is a collection of services and classes?
• Exists as a layer between .NET applications and the underlying operating system.
• Encapsulates much of the functionality, such as debugging and security services.
• The following figure depicts the components of the .NET Framework:

The .NET Framework Base Classes or the .NET Class Framework

• Consists of a class library that works with any .NET language, such as Visual Basic .NET and C#.
• Provides classes that can be used in the code to accomplish a range of common programming tasks.
• Comprises
o Namespaces: Namespaces help you to create logical groups of related classes and interfaces that can be used by any language targeting the .NET Framework.
o Assembly: An assembly is a single deployable unit that contains all the information about the implementation of classes, structures, and interfaces.
• The Common Language Runtime
o Provides functionality such as exception handling, security, debugging, and versioning support to any language that targets it.
o Can host a variety of languages and offer a common set of tools across these languages, ensuring interoperability between the codes.

• Provides the following features:
o Automatic memory management
o Standard type system
o Language interoperability
o Platform independence
o Security management
o Type safety

Advantages of the .NET Framework

• Some advantages of the .NET Framework are:
o Consistent programming model
o Multi-platform applications
o Multi-language integration
o Automatic resource management
o Ease of deployment

ADO.NET

• Is a model used by Visual Basic .NET applications to communicate with a database for retrieving, accessing, and updating data?
• Uses a structured process flow to interact with a database.

ADO .NET Data Access
Most applications need data access at one point of time making it a crucial component when working with applications. Data access is making the application interact with a database, where all the data is stored. Different applications have different requirements for database access. VB.NET uses ADO.NET (Active X Data Object) as it’s data access and manipulation protocol, which also enables us to work with data on the Internet. Let’s take a look why ADO.NET came into picture replacing ADO.

Evolution of ADO.NET
The first data access model, DAO (data access model) was created for local databases with the built-in Jet engine which had performance and functionality issues. Next came RDO (Remote Data Object) and ADO (Active Data Object) which were designed for Client Server architectures but soon ADO took over RDO. ADO was a good architecture but as the language changes so is the technology within it. With ADO, all the data is contained in a record set object which had problems when implemented on the network (Internet) and penetrating firewalls. ADO was a connected data access which means that when a connection to the database is established the connection remains open until the application is closed, which raises concerns about database security and network traffic. And also as databases are becoming increasingly important and as they are serving more people a connected data access model makes us think about its use. For example, an application with connected data access may do well when connected to two clients, the same may do poorly when connected to 10 and might be unusable when connected to 100 or more. Also, open database connections use system resources to a maximum extent making the system performance less effective.

Why ADO.NET?

To cope up with some of the problems mentioned above, ADO.NET came into existence. ADO.NET addresses the above mentioned problems by maintaining a disconnected database access model which means that when an application interacts with the database the connection is opened to serve the request of the application and is closed as soon as the request is completed. Likewise if a database is updated, the connection is opened long enough to complete the Update operation and is closed. By keeping connections open for only a minimum period of time ADO.NET conserves system resources and provides maximum security for databases and also has less impact on system performance. Also, ADO.NET when interacting with database uses XML by converting all the data into XML and using it for database related operations making them more efficient.

Features of ADO.NET
• Disconnected data architecture — Applications connect to the database only while retrieving and updating data.
• Data cached in datasets — ADO.NET is based on a disconnected data structure. Therefore, the data is retrieved and stored in datasets.
• Data transfer in XML format — ADO.NET uses XML for transferring information from a database into a dataset and from the dataset to another component.
• Interaction with the database is done through data commands.

ADO.NET Object Model
Key Components of the ADO.NET Model
• Data Provider
o Is used for connecting to a database, retrieving data, and storing the data.
• Is of two types:
o OLE DB data provider
o SQL Server data provider

Components of a Data Provider
• Connection
o Used to establish a connection with a data source
o Some commonly used properties and methods:
 ConnectionString property
 Open()method
 Close()method
 State property
• Data adapter
o Creates a dataset and updates the database.
o Handles data transfer between the database and the dataset through its properties and methods.
o Displays the data through the process of table mapping.
o Are of two types:
 SqlDataAdapter
 OleDbDataAdapter

• Data command

o Is a SQL statement or a stored procedure that is used to retrieve, insert, delete, or modify data from a data source.
o Is an object of the OleDbCommand or SQLCommand class.

• Data reader

o Is used to retrieve data from a data source in a read-only and forward-only mode.
o Stores a single row at a time in the memory.
o Commonly used methods:
 Read()
 Close()
 NextResult()
• Dataset

o Is a disconnected, cached set of records that are retrieved from a database.
o Is present as a DataSet class in the System.Data namespace.
o Has its own object model.

2.1 PRELIMINARY INVESTIGATION

System development, a process consisting of two major steps of system analysis and design, start when management or sometimes system development personnel feel that a new system or an improvement in the existing system is required. The system development life cycle is classically thought of as the set of activities that analysts, designers and users carry out to develop and implement an information system. The system development life cycle consists of the following activities:

 Preliminary investigation
 Determination of system requirements
 Design of system
 Development of software
 System testing
 Implementation, evaluation, and maintenance

A request to take assistance from information system can be made for many reasons, but in each case someone in the organization initiates the request is made, the first system activity the preliminary investigation begins. This activity has three parts:

1) Request clarification
2) Feasibility study
3) Request approval

2.2 SYSTEM DEVELOPMENT LIFE CYCLE

Systems are created to solve problems. One can think of the systems approach as an organized way of dealing with a problem. In this dynamic world, the subject System Analysis and Design (SAD), mainly deals with the software development activities.

DEFINING A SYSTEM

A collection of components that work together to realize some objective forms a system. Basically there are three major components in every system, namely input, processing and output.

In a system the different components are connected with each other and they are interdependent. For example, human body represents a complete natural system. We are also bound by many national systems such as political system, economic system, educational system and so forth. The objective of the system demands that some output is produced as a result of processing the suitable inputs.

SYSTEM LIFE CYCLE

System life cycle is an organizational process of developing and maintaining systems. It helps in establishing a system project plan, because it gives overall list of processes and sub-processes required for developing a system.
System development life cycle means combination of various activities. In other words we can say that various activities put together are referred as system development life cycle. In the System Analysis and Design terminology, the system development life cycle means software development life cycle.

Following are the different phases of software development cycle:

 System study
 Feasibility study
 System analysis
 System design
 Coding
 Testing
 Implementation
 Maintenance

The Different Phases Of Software Development Life Cycle Are Shown Below.

A system analysis is a separation of a substance into parts for study and their implementation and detailed examination. Before designing any system it is important that the nature of the business and the way it currently operates are clearly understood. The detailed examination provides the specific data required during designing in order to ensure that all the client’s requirements are fulfilled. The investigation or the study conducted during the analysis phase is largely based on the feasibility study. Rather it would not be wrong to say that the analysis and feasibility phases overlap. High-level analysis begins during the feasibility study. Though analysis is represented as one phase of the system development life cycle (SDLC), this is not true. Analysis begins with system initialization and continues until its maintenance. Even after successful implementation of the system, analysis may play its role for periodic maintenance and up gradation of the system.

One of the main causes of project failures is inadequate understanding, and one of the main causes of inadequate understanding of the requirements is the poor planning of system analysis. Analysis requires us to recall the objectives of the project and consider following three questions:

 What type of information is required?
 What are the constraints on the investigation?
 What are the potential problems that may make the task more difficult?

2.3 FEASIBILITY STUDY

The basic premise of system analysis is being done here. The primary goal of the system analysis stage is to identify problems and determine how they can be solved with the computer system. In formal SDLC methodologies, the first step in system analysis is feasibility study. A feasibility study is the quick examination of the problems, goals, expected cost of the system. The objective is to determine whether the problem can reasonably solved with a computer system. In some cases, may be there is a better alternative, or perhaps is simply short term annoyance and will gradually disappear. In other cases, the problem may turn out to be more complex than was thought and involves users across the company. Also, some problems may not be solvable with today’s technology. It might be better to wait for better technology. In any case, you need to determine the scope of the project to gain the better idea of cost, benefits, and objectives.

The feasibility study is typically written so that non- programmers can easily understand it. It is used to “sell” the to the upper management and as a starting point for the next step. Additionally it is used as a reference to keep the project on track, and to evaluate the progress of project team. Is the project cost effective or there is a cheaper solution? Will the proposed system improve the operation of the bank; will complicating factors prevent it from achieving its goals? Does the technology exist and does the firm have the staff to make the technology work?

When the proposal is determined to be feasible, the team leaders are appointed and a plan and schedule are created. The schedule contains a detailed listing of what parts of the project are completed at each time. Of course, it extremely difficult to estimate the true cost and completion dates. Nonetheless, the schedule is an important tool to evaluate the status of the project and the progress of the team.
Steps in feasibility Analysis are:

1. Identify deficiency by pinpointing, missing functions, unsatisfactory performance, Excessive cost of operations.

2. Set goals to remove these deficiencies.

3. Goals must be quantified, realizable within the constraints of an organization,broken down into sub goals agreeable to all concerned.

4. Set goals not only to remove deficiencies but also to effectively meet competition. For instance, goals must be based on what competitors do.

2.4 ECONOMIC FEASIBILITY

Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost / benefit analysis; in this procedure we determine the benefits and savings that are expected from a proposed system and compare them with costs. We found the benefits outweigh the costs; we take a decision to design and implement the new proposed system.

During the feasibility phase, broad alternatives solutions are examined. For each alternate solution the cost and benefits have to be examined before designing one of the alternatives.
Broad solutions will consist of:

1. Specifications of information to be made available by the system.
2. Description of what will be done manually and what the computer will do.
3. Specification of new computing equipment needed or specification of expansion of an existing computer.

 COST AND BENEFIT ANALYSIS
Developing an IT application is an investment. Since after developing that application it provided the organization with profits. Profits can be monetary or in the form of an improved working environment. However, it carries risks because in some cases an estimate can be wrong and the project might not actually turn out to be beneficial.

Cost benefit analysis helps to give management a picture of the cost, benefits and risks. It usually involves comparing alternate investments.
Cost benefit determines the benefits and savings that are expected from the system and compares them with the expected cost.

In performing cost and benefit analysis it is important to identify cost and benefits factors. Cost and benefits can be categorized into the following categories:

i. Development cost – Development costs is the cost that are incurred during the development of the system. It is one time investment.
ii. Operating cost – Operating cost are the expenses required for the day¬ to-day running of the system. As, operating cost are wages, supplies and overheads.
iii. Hardware/Software cost – It includes the cost of purchasing or leasing of computes and it’s peripherals. Software costs involves required software cost.
iv. Personnel cost – It is the money spent on the people involved in the development of the system.
v. Facility cost – Expenses that are incurred during the preparation of the physical site where the system will be operational. These can be wiring, flooring, acoustics, lighting, and air-conditioning.
vi. Supply cost – These are variable costs that are very proportionately with the amount of use of paper, ribbons, disks, and others.

 BENEFITS
We can define benefits as
Profit or Benefit = Income – Cost
Benefits can be accrued by:
Increasing income or
Decreasing costs or
Both

ITEM COST (Rs.)
Computer 40,000 (depend upon the configuration)
Laser Printer 7,000
VB.NET
SQL Server
Scanner 4,000
Project cost
Total 4,000 (approx.)
55,000

We should know that we need a person who can work with these software’s and so his training will cost around Rs 4,000. Here we see that the total price to get one computer up and running with the database management system is close to Rs.50, 000 as we don’t really need a very high performance computer as this project is entirely text based and requires only minimal processor speeds for computing. If the developer wants to have around 2 computers then we have the total costs being:
55,000*2 = Rs.1, 10,000

This would mean that the this project would need around 1 lakh to run my system successfully and resourcefully. MTNL billing authorities are planning to reduce the staff , suppose if they remove one employee. Salary of on employee being around Rs.5,000. In one year annual salary of employee is equal to Rs. 60,000 and salary to three bill receiver and consumer is Rs. l, 80,000 for one year .From this analysis it can be seen that whatever money the MTNL billing system will invest on making their system a computerized system will be recovered and half years of time (approx.). This analysis shows that how management is benefited by computerized system.
BENEFITS:
1) Fast and easy access to all MTNL BILLING related procedures and functions.
2) No need for large storage spaces sized of rooms for storing the cabinets because all the information about the members and other details is saved in the computer’s hard disks.
3) High level of security and authentication of each and every user.
4) Less need for personnel, thus, no monthly salaries, this leads to no extra funds.
5) Reliability is increased, as backups of files, and records can be made and saved in various different locations and information will be highly secure, unlike in file cabinets where entries can easily be ripped or tampered with by users.
6) The reception/front office will look much more neater and cleaner the environment they need, as there Won’t be any cupboards or drawers which make the MTNL Billing overcrowded.
7) There will be no longer the need for all the paper work required to make timely reports lists or other lists as the program generates then at anytime at a very quick pace.
2.5 TECHNICAL FEASIBILITY
Today, very little is technically impossible. Consequently, technical feasibility looks at what is practical and reasonable. Technical feasibility addresses three major issues:
1. Is the proposed technology or solution practical?
2. Do we currently possess the necessary technology?
3. Do we possess the necessary technical expertise, and is the schedule reasonable?

Is the Proposed Technology or Solution Practical?

The technology for any defined solution is normally available. The question whether that technology is mature enough to be easily applied to our problems. Some firms like to use state-of-the-are technology, but most firms prefer to use mature and proven technology. A mature technology has a larger customer base for obtaining advice concerning problems and improvements.
Do We Currently Possess the Necessary Technology?

Assuming the solution’s required technology is practical, we must next ask ourselves, is the technology available in our information systems shop? If the technology is available, we must ask if we have the capacity. For instance, will our current printer be able to handle the new reports and forms required of a new system?
If the answer to any of these questions is no, then we must ask ourselves, Can we get this technology? The technology may be practical and available, and, yes, we need it. But we simply may not be able to afford it at this time. Although this argument borders on economic feasibility, it is truly technical feasibility. If we can’t afford the technology, then the alternative that requires the technology is not practical and is technically infeasible!
Do We Possess the Necessary Technical Expertise, and Is the Schedule Reasonable?
This consideration of technical feasibility is often forgotten during feasibility analysis. We may have the technology, but that doesn’t mean we have the skills required to properly apply that technology. For instance, we may have a database management systems (DBMS). However, the analysis and programmers available for the project may not know that DBMS well enough to properly apply it. True, all information systems professionals can learn new technologies. However, that learning curve will impact the technical feasibility of the project; specifically, it will impact the schedule.
As mentioned earlier, the current operational state of MTNL billing is very primitive as all bulling is done on hand written database. These files are then placed in drawers or cabinets and tagged in a sorted order. The MTNL billing ontains over a large number of drawers and cabinets. Each cabinet takes a large space. Other than this it uses many kind of papers to calculate and maintain different account works. Since there has been no use of computer in the MTNL billing so far, for storage of data, there is no currently used software.
The software & hardware to run my project, and is it’s usage is given in the table below:

TOOLS/PLATFORMS, HARDWARE & SOFTWARE REQUIREMENTS

HARDWARE:

Processor : Pentium 2.4 GHz or above
Memory : 256 MB RAM or above
Cache Memory : 128 KB or above
Hard Disk : 3 GB or above [at least 3 MB free space required]
Floppy Disk : 3.5” with 1.44 MB capacity
[at least one drive labeled A: required]

SOFTWARE:

Operating System : Windows 95/98, Win NT, Win 2000.
Font-End Tool : VISUAL BASIC .NET
Back End Tool : SQL SERVER

2.6 OPERATIONAL FEASIBILITY

It is mainly related to human organizational and political aspects. The points to be considered are:

o What changes will be brought with the system?
o What organizational structures are disturbed?
o What new skills will be required? Do the existing staff members have these skills?
o If not, can they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such considerations are likely to critically affect the nature and scope of the eventual recommendations.

For operational feasibility study we appointed a small group of people who are familiar with information system techniques, who understand the parts of the business that are relevant to the project and are skilled in system analysis and design process.

2.7 FEASIBILITY REPORT

All projects are feasible-given unlimited resources and infinite time. Unfortunately, the development of a computer-based system or product is more likely plagued by a scarcity of resources and difficult delivery dates. It is both necessary and prudent to evaluate the feasibility of the project at the earliest possible time.

Feasibility and risk analysis are related in many ways. If the project risk is great, the feasibility of producing quality software is reduced. During product engineering however we concentrate our attention on four primary areas of interest:

Economic feasibility: An evaluation of development cost weighed against the ultimate income or benefit derived from the developed system or product.
Technical feasibility: A study of function, performance, and constraints that may affect the ability to achieve an acceptable system.
Legal feasibility: A determination of any infringement, violation or the liability that could result from the development of the system.
Alternatives: An evaluation of alternative approaches to the development of the system or product.

3.1 IMPORTANCE OF COMPUTERIZED

MTNL BILLING

There are several attributes in which the computer based information works. Broadly the working of computer system is divided into two main groups:

• Transaction System
• Decision Support System

Transaction System:

A transaction is a record of some well-defined single and usually small occurrence in a system. Transactions are input into the computer to update the database files. It checks the entering data for its accuracy. This means that numeric data appears in numeric field and character data in character field. Once all the checks are made, transaction is used to update the database. Transaction can be inputted in on-line mode or batch mode. In on-line mode, transactions are entered and updated into the database almost instantaneously. In batch mode, transactions are collected into batches, which may be held for a while and inputted later.

Decision Support System:

It assists the user to make analytical decision. It shows the various data in organized way called analysis. This analysis can be made to syrdy preferences and help in making decisions.

Computer system works out best with record maintenance. It will tell you which customer would get how much pending/reports statements. It will also help to search the information about a particular person by simply entering his telephone number. User can store information as per requirement, which can be used for comparison with other reports.

3.2 PRINCIPLES OF SYSTEM ANALYSIS

Principles:
1. Understand the problem before you begin to create the analysis model.
2. Develop prototypes that enable a user to understand how human machine interaction will occur.
3. Record the origin of and the reason for every requirement.
4. Use multiple views of requirements like building data, function and behavioral models.
5. Work to eliminate ambiguity.

A Complete Structure:

The limited time and resources have restricted us to incorporate, in this project, only the main activities that are performed in news sites, but utmost care has been taken to make the system efficient and user friendly.

For the optimum use of practical time it is necessary that every session is planned. Planning of this project will include the following things:

• Topic Understanding.
• Modular Break – Up of the System.
• Processor Logic for Each Module.
• Database Requirements.

Topic Understanding:

It is vital that the field of application as introduced in the project may be totally a new field. So as soon as the project was allocated to me, I carefully went through the project to identify the requirements of the project.

Modular Break –Up of the System:

 Identify The Various Modules In The System.
 List Them In The Right Hierarchy.
 Identify Their Priority Of Development
 Description Of The Modules:

4.1 SYSTEM DESIGN
The design document that we will develop during this phase is the blueprint of the software. It describes how the solution to the customer problem is to be built. Since solution to complex problems isn’t usually found in the first try, iterations are most likely required. This is true for software design as well. For this reason, any design strategy, design method, or design language must be flexible and must easily accommodate changes due to iterations in the design. Any technique or design needs to support and guide the partitioning process in such a way that the resulting sub-problems are as independent as possible from each other and can be combined easily for the solution to the overall problem. Sub-problem independence and easy combination of their solutions reduces the complexity of the problem. This is the objective of the partitioning process. Partitioning or decomposition during design involves three types of decisions: –
Define the boundaries along which to break;
Determine into how money pieces to break; and
Identify the proper level of detail when design should stop and implementation should start.

Basic design principles that enable the software engineer to navigate the design process suggest a set of principles for software design, which have been adapted and extended in the following list:

Free from the suffer from “tunnel vision.” A good designer should consider alternative approaches, judging each based on the requirements of the problem, the resources available to do the job.
The design should be traceable to the analysis model. Because a single element of the design model often traces to multiple requirements, it is necessary to have a means for tracking how requirements have been satisfied by the design model.

The design should not repeat the same thing. Systems are constructed using a set of design patterns, many of which have likely been encountered before. These patterns should always be chosen as an alternative to reinvention. Time is short and resources are limited! Design time should be invested in representing truly new ideas and integrating those patterns that already exist.

The design should “minimize the intellectual distance” between the software and the problem as it exists in the real world. That is, the structure of the software design should (whenever possible) mimic the structure of the problem domain.

The design should exhibit uniformity and integration. A design is uniform if it appears that one person developed the entire thing. Rules of style and format should be defined for a design team before design work begins. A design is integrated if care is taken in defining interfaces between design components.

The design activity begins when the requirements document for the software to be developed is available. This may be the SRS for the complete system, as is the case if the waterfall model is being followed or the requirements for the next “iteration” if the iterative enhancement is being followed or the requirements for the prototype if the prototyping is being followed. While the requirements specification activity is entirely in the problem domain, design is the first step in moving from the problem domain toward the solution domain. Design is essentially the bridge between requirements specification and the final solution for satisfying the requirements.

The design of a system is essentially a blueprint or a plan for a solution for the system. We consider a system to be a set of components with clearly defined behavior that interacts with each other in a fixed defined manner to produce some behavior or services for its environment. A component of a system can be considered a system, with its own components. In a software system, a component is a software module.

The design process for software systems, often, has two levels. At the first level, the focus is on deciding which modules are needed for the system, the specifications of these modules, and how the modules should be interconnected. This is what is called the system design or top-level design. In the second level, the internal design of the modules, or how the specifications of the module can be satisfied, is decided. This design level is often called detailed design or logic design. Detailed design essentially expands the system design to contain a more detailed description of the processing logic and data structures so that the design is sufficiently complete for coding.

Because the detailed design is an extension of system design, the system design controls the major structural characteristics of the system. The system design has a major impact on the testability and modifiability of a system, and it impacts its efficiency. Much of the design effort for designing software is spent creating the system design.

The input to the design phase is the specifications for the system to be designed. Hence, reasonable entry criteria can be that the specifications are stable and have been approved, hoping that the approval mechanism will ensure that the specifications are complete, consistent, unambiguous, etc. The output of the top-level design phase is the architectural design or the system design for the software system to be built. This can be produced with or without using a design methodology. Reasonable exit criteria for the phase could be that the design has been verified against the input specifications and has been evaluated and approved for quality.

A design can be object-oriented or function-oriented. In function-oriented design, the design consists of module definitions, with each module supporting a functional abstraction. In object-oriented design, the modules in the design represent data abstraction (these abstractions are discussed in more detail later). In the function-oriented methods for design and describe one particular methodology the structured design methodology in some detail. In a function- oriented design approach, a system is viewed as a transformation function, transforming the inputs to the desired outputs. The purpose of the design phase is to specify the components for this transformation function, so that each component is also a transformation function. Hence, the basic output of the system design phase, when a function oriented design approach is being followed, is the definition of all the major data structures in the system, all the major modules of the system, and how the modules interact with each other.

Once the designer is satisfied with the design he has produced, the design is to be precisely specified in the form of a document. To specify the design, specification languages are used. Producing the design specification is the ultimate objective of the design phase. The purpose of this design document is quite different from that of the design notation. Whereas a design represented using the design notation is largely to be used by the designer, a design specification has to be so precise and complete that it can be used as a basis of further development by other programmers. Generally, design specification uses textual structures, with design notation helping in understanding

DATA MODELING

Introduction to data dictionary:
Data dictionaries are an integral component of structured analysis, since data flow diagrams by themselves do not fully describe the subject of the investigation . The data flow diagrams provide the additional details about the project/system.

Data Dictionary (Definition):
A data dictionary is a catalog- a repository- of the elements in a system. These elements center on the data and the way they are structured to meet user requirements and organization needs. A data dictionary consists of a list of all the elements composing the data flowing through a system. The major elements are data flows , data stores , and processes. The data dictionary stores details and descriptions of these elements.

1. Login Table: To store Admin login details

User ID Type Primary Key Description
Username Char(30) Not null User ID
Password Char(30) Not null Password
E mail Char(70) Not null Email

2. Consumer Table: consumer table stores the details of the consumer

User ID Type Primary Key Description
Cons_no Number(15) Primary key Consumer No
Cons_name Char(70) Not null Consumer Name
Cons_add Char(70) Not null Consumer address
Cons_city Char(50) Not null City, State
pin number Not null pincode
Contact_no Number(10) Not null Contact no
Email Char(70) Not null Email
Date_of_Reg Date Not null Date of Registration
Tariff_Plan Char(50) Not null Tariff plan
Category Char(50) Not null Category of the consumer
Reg_Charges number Not null Registration charges
Telephone_no number Not null Contact Number

3. Bill Table: to store bill details
User ID Type Primary Key Description
Bill_no Number(15) Primary key Bill no
Telephone_no Number(10) Not null Telephone No
Bill_No Date Not null Bill Date
Due_date Date Not null Due date
Amt_after_due Date Not null Amount after due date
Previous_read Number Not null Previous meter reading
Pre_read_date Date Not null Previous meter reading date
Curr_read Number Not null Current meter reading
Curr_read_date Date Not null Current reading date
Metere_call Number Not null Metere calls
Free_call Number Not null Free calls
Net_calls_chargeable Number Not null Net calls chargeable
Call_charges Number Not null Call charges
Monthly_service Number Not null Monthly service charges
Service_tax Number Not null Service tax
Other_debits Number Not null Other debits
Other_credits Number Not null Other credits
Amt_paid Number Not null Amount paid
Call_rate Number Not null Call rate
status Number Not null Status of the payment

4. Transaction Table: To store details of the all the bills paid by the consumers through any mode of payment.
User ID Type Primary Key Description
Transaction Id Number Primary Key Transaction Id
Bill_no Number Not null Bill No
Telephone_no Number Not null Telephone No
Consumer_no Number Not null Consumer No
Bill_date Date Not null Bill Date
Payment_date Date Not null payment Date
Amount_paid Number Not null Amount Paid
Mode_of_payment Char(50) Not null Mode of payment
Bank Char(70) Not null Bank name
Description Char(200) Not null Description

5. Complaint Details: To store details of the complaints raised by the consumers and solved by the departments.
User ID Type Primary Key Description
Complaint_no Char(30) Primary key Complaint No
Complaint_details Date Not null Complaint Date
Attend_by Date Not null Attended by
Solved_by Date Not null Solved by
Complaint_desc Char(250) Not null Complaint description

6. Emp Details: To store details of the employees of all departments
User ID Type Primary Key Description
Emp_id Char(30) Primary key Employee Id
Emp_name Char(30) Not null Employee Name
Address Char(70) Not null Address
Contact_no Number Not null Contact No
Designation Char(50) Not null Designation
Department Char(50) Not null Department
Salary Number Not null Salary
Date_of_join Date Not null Date of joining
Qualification Char(50) Not null Qualification
expert Char(50) Not null Expertisation

ER-Diagram

CONTEXT LEVEL DFD
Context Level DFD
for MTNL Billing system

Complaints

Managing

Consumer Details
Employee

Details

Ist Level DFD for MTNL Booking

Ist Level DFD for New Connection

IInd Level DFD for Cancellation of Installation

Ist level DFD for Complaint

4.4 MODULES

Different modules that makeup these systems are briefly described below:

• ADMIN AUTHENTUCATION
• MANAGING CONSUMER DETAILS
• CONSUMPTION & TRANSACTION
• BILL GENERATION
• COMPLAINTS
• EMPLOYEE DETAILS
• DISCONNECTIONS

ADMIN AUTHENTICATION

In this module, admin enters a password and the software checks its validity. If the password is valid then option is given to change the password, otherwise “Invalid User/Password” message is displayed. Admin is the main user of the project .
• He can create sub users to operate the software.
• He provides user id and password to sub admin users according to the authentications.
• Admin can generate reports

MANAGING CONSUMERS DETAILS

This is used to add a new consumer details, delete consumer ’s details and view consumer’s details. In that screen, the automatic item is created.
In this module, whenever a new entity is required to be added the corresponding forms are opened and the database is manipulated to check whether the data is already existing or not. If it already exists, then it prompts that “Entry already existing” and if not than the data is entered with the various validation checks.It maintains all information regarding consumer:
Consumer ID
Consumer Name
Residential Details
Tarrif Plan
Category
Telephone No.
Registration Charges

BILL & TRANSACTION MODULE.

In this module, Admin sub user add details of the bills paid by the consumers and update their balances and dues. This can be done by the meter reading details given in the bill. These reading are stored in the database.

COMPLAINTS

This module maintains complaints details. If complaints are not handled timely it can result in the disconnections and bad reputation of MTNL. Complaints details are also stored in the database. After that they are assigned to the employees and engineers.

EMPLOYEES MODULE

This module maintains employees details. It maintains the database of all the employee of all departments.

MODIFYING/UPDATING EXISTING ENTITIES

In this module, whenever an existing entity is required to be modified the corresponding forms are opened and the database is manipulated and the data is fetched. Now the user can made the required changes and then accordingly, he updates the data. Again, the checks are followed in case there is any invalid entry. For example if some complaints are solved by the MTNL department, then its status should be updated.

VALIDATION OF DATA ENTERED BY THE USER & ERROR HANDLING

In this module, the validity of data entered by the user during the various business processes is checked through various validation checks. For example, there should not be any characters entered in the numeric fields, likewise if there is any error occurs than it should handle that particular error and give the required messages.

REPORT GENERATION

In this module reports are generated for the following entities:
a) Consumers report
b) Employees Details
c) Bills Details
d) Transactions Report

4.5 PROCESS LOGIC FOR EACH MODULE:
Process Logic of Module is a tool that may be useful in planning and evaluating projects. Our logic model contains four components with Inputs-Outputs-Outcomes being central to the built in response to the model:
• Situation: The context and need that gives rise to a project or initiative; logic modules are built in response to an existing situation.
• Inputs: The resources, contributions, and investments that are made in response to the situation. Inputs lead to Outputs.
• Outputs: The activities, products, methods, and services that reach people and users. Outputs lead to outcomes.
• Outcomes: The results and benefits for individuals, groups, agencies, communities and/or systems.

4.6 TOOLS / PLATFORM, HARDWARE AND SOFTWARE REQUIREMENT SPECIFICATION

HARDWARE

Processor : Pentium 2.4 GHz or above

Memory : 256 MB RAM or above

Cache Memory : 128 KB or above

Hard Disk : 3 GB or above [at least 3 MB free space required]

Floppy Disk Drive : 3.5” [At least one drive labeled a: required]

Printer : Dot Matrix / DeskJet connected to LPT port

SOFTWARE

Operating System : Windows XP (Professional).

Font-End Tool : VB .NET

Back-End : SQL SERVER 2000

4.7 SCHEDULING

Scheduling of a software project does not differ greatly from scheduling of any multi- task engineering effort. Therefore, generalized project scheduling tools and techniques can be applied with little modification to software projects.

Program evaluation and review technique (PERT) and critical path method (CPM) are two project scheduling methods that can be applied to software development. Both techniques are driven by information already developed in earlier project planning activities.

Estimates of Effort

 A decomposition of the product function.
 The selection of the appropriate process model and task set.
 Decomposition of tasks.
Interdependencies among tasks may be defined using a task network. Tasks, sometimes called the project Work Breakdown Structure (WBS) are defined for the product as a whole or for individual functions.

Both PERT and CPM provide quantitative tools that allow the software planner to (1) determine the critical path-the chain of tasks that determines the duration of the project; (2) establish “most likely” time estimates for individual tasks by applying statistical models; and (3) calculate “boundary times” that define a time window” for a particular task.

Boundary time calculations can be very useful in software project scheduling. Slippage in the design of one function, for example, can retard further development of other functions. It describes important boundary times that may be discerned from a PERT or CPM network: (I) the earliest time that a task can begin when preceding tasks are completed in the shortest possible time, (2) the latest time for task initiation before the minimum project completion time is delayed, (3) the earliest finish-the sum of the earliest start and the task duration, (4) the latest finish- the latest start time added to task duration, and (5) the total float-the amount of surplus time or leeway allowed in scheduling tasks so that the network critical path maintained on schedule. Boundary time calculations lead to a determination of critical path and provide the manager with a quantitative method for evaluating progress as tasks are completed.

Both PERT and CPM have been implemented in a wide variety of automated tools that are available for the personal computer. Such tools are easy to use and take the scheduling methods described previously available to every software project manager.

5.1 COMPLETE PROJECT CODING

Public Class process

Private Sub process_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
ProgressBar1.Minimum = 0
Dim i As Integer
For i = 0 To 100
System.Threading.Thread.Sleep(100)
ProgressBar1.Value = i

Next
Dim a As New Form1
a.Show()
Me.Hide()

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient

Public Class Login

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click

Dim con As New SqlConnection
Dim cmd As New SqlCommand
Dim da As New SqlDataAdapter
Dim ds As New DataTable
If (TextBox1.Text = “” Or TextBox2.Text = “” Or TextBox3.Text = “”) Then
MsgBox(“sorry fill properly this textbox”)
Else

con = New SqlConnection(“Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”)

cmd = New SqlCommand(“select *from login where user_name=@user_name and password=@password and email_id=@email_id”, con)

Dim a, b, c As New SqlParameter

a = New SqlParameter(“@user_name”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cmd.Parameters.Add(a)

b = New SqlParameter(“@password”, SqlDbType.VarChar)
b.Value = TextBox2.Text
cmd.Parameters.Add(b)

c = New SqlParameter(“@email_id”, SqlDbType.VarChar)
c.Value = TextBox3.Text
cmd.Parameters.Add(c)
da = New SqlDataAdapter()
da.SelectCommand = cmd
ds = New DataTable()
da.Fill(ds)
If ds.Rows.Count = 0 Then
MsgBox(“invalid try again”)

Else

Dim aa As New MDIParent1
aa.Show()
Me.Hide()
End If

End If

End Sub

Private Sub Login_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub Label3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)

End Sub

Private Sub GroupBox1_Enter(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles GroupBox1.Enter

End Sub

Private Sub ToolTip1_Popup(ByVal sender As System.Object, ByVal e As System.Windows.Forms.PopupEventArgs)

End Sub

Private Sub TextBox1_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TextBox1.TextChanged

End Sub

Private Sub TextBox2_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TextBox2.TextChanged

End Sub
End Class

Imports System.Windows.Forms

Public Class MDIParent1

Private m_ChildFormNumber As Integer

Private Sub DatabaseToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles DatabaseToolStripMenuItem.Click

End Sub

Private Sub ComplaintDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ComplaintDetailsToolStripMenuItem.Click
Dim a As New Complaint_insert
a.MdiParent = Me
a.Show()
End Sub

Private Sub EmpDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles EmpDetailsToolStripMenuItem.Click
Dim a As New emp_insert
a.MdiParent = Me
a.Show()

End Sub

Private Sub TransactionDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TransactionDetailsToolStripMenuItem.Click
Dim a As New transaction_insert
a.MdiParent = Me
a.Show()
End Sub

Private Sub ConsumerDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ConsumerDetailsToolStripMenuItem.Click
Dim a As New consumer_insert
a.MdiParent = Me
a.Show()
End Sub

Private Sub BillDetailsToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BillDetailsToolStripMenuItem.Click
Dim a As New Billl_insert

a.MdiParent = Me
a.Show()
End Sub

Private Sub EmpSearchToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles EmpSearchToolStripMenuItem.Click
Dim a As New Emp_search
a.MdiParent = Me
a.Show()
End Sub

Private Sub TransationSearchToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TransationSearchToolStripMenuItem.Click
Dim a As New Transaction_Search
a.MdiParent = Me
a.Show()
End Sub

Private Sub MDIParent1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub ComplaintToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ComplaintToolStripMenuItem.Click
Dim a As New Complaint_edit
a.MdiParent = Me
a.Show()
End Sub

Private Sub ConsumerToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ConsumerToolStripMenuItem.Click
Dim a As New Consumer_edit
a.MdiParent = Me
a.Show()
End Sub

Private Sub BillToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BillToolStripMenuItem.Click
Dim a As New Bill_edit
a.MdiParent = Me
a.Show()
End Sub

Private Sub EmployeesToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles EmployeesToolStripMenuItem.Click
Dim a As New emp_edit
a.MdiParent = Me
a.Show()
End Sub

Private Sub TToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TToolStripMenuItem.Click
Dim a As New Transaction_edit
a.MdiParent = Me
a.Show()
End Sub

Private Sub ComplaintSearchToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ComplaintSearchToolStripMenuItem.Click
Dim a As New Complaint_search
a.MdiParent = Me
a.Show()
End Sub

Private Sub ConsumerSearchToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ConsumerSearchToolStripMenuItem.Click
Dim a As New Consumer_search
a.MdiParent = Me
a.Show()
End Sub

Private Sub BillSearchToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BillSearchToolStripMenuItem.Click
Dim a As New Bill_search
a.MdiParent = Me
a.Show()
End Sub

Private Sub BillToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles BillToolStripMenuItem1.Click
Dim a As New Bill_Report
a.MdiParent = Me
a.Show()
End Sub

Private Sub ConsumerToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ConsumerToolStripMenuItem1.Click
Dim a As New consumer_report2
a.MdiParent = Me
a.Show()

End Sub

Private Sub ComplaintToolStripMenuItem1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ComplaintToolStripMenuItem1.Click
Dim a As New Complaint_Report
a.MdiParent = Me
a.Show()
End Sub

Private Sub TransactionToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TransactionToolStripMenuItem.Click
Dim a As New Transaction_Report
a.MdiParent = Me
a.Show()
End Sub

Private Sub EmployeeToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles EmployeeToolStripMenuItem.Click
Dim a As New Employee_Report
a.MdiParent = Me
a.Show()
End Sub

Private Sub ExitToolStripMenuItem_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles ExitToolStripMenuItem.Click
End
End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class emp_insert
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL billing system ;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
If (TextBox1.Text = “”) Then
MsgBox(” Employee id is compulsary to enter “)

Else

con.Open()
cm = New SqlCommand(“insert into emp_Details values (‘” & TextBox1.Text & “‘,'” & TextBox2.Text & “‘,'” & TextBox3.Text & “‘,'” & TextBox4.Text & “‘,'” & TextBox5.Text & “‘,'” & TextBox6.Text & “‘,'” & TextBox7.Text & “‘,'” & TextBox8.Text & “‘,'” & TextBox9.Text & “‘,'” & TextBox10.Text & “‘)”, con)
cm.ExecuteNonQuery()
MsgBox(” Record inserted “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox1.Focus()
con.Close()
End If
End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class transaction_insert
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
If (TextBox1.Text = “”) Then
MsgBox(“Trasaction id is compulsary to enter”)

Else
con.Open()
cm = New SqlCommand(“insert into transaction_details values (‘” & TextBox1.Text & “‘,'” & TextBox2.Text & “‘,'” & TextBox3.Text & “‘,'” & TextBox4.Text & “‘,'” & TextBox5.Text & “‘,'” & TextBox6.Text & “‘,'” & TextBox7.Text & “‘,'” & TextBox8.Text & “‘,'” & TextBox9.Text & “‘,'” & TextBox10.Text & “‘)”, con)
cm.ExecuteNonQuery()

MsgBox(” Record inserted “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox1.Focus()
con.Close()
End If

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Complaint_insert
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Private Sub Complaint_insert_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
If (TextBox1.Text = “”) Then
MsgBox(” Complaint no is compulsary to enter “)

Else
con.Open()
cm = New SqlCommand(“insert into Complaint_Details values (‘” & TextBox1.Text & “‘,'” & TextBox2.Text & “‘,'” & TextBox3.Text & “‘,'” & TextBox4.Text & “‘,'” & TextBox5.Text & “‘)”, con)
cm.ExecuteNonQuery()
MsgBox(” Record inserted “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox1.Focus()
con.Close()
End If

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class consumer_insert
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
If (TextBox1.Text = “”) Then
MsgBox(” Consumer no is compulsary to enter “)

Else
con.Open()
cm = New SqlCommand(“insert into consumer_table values (‘” & TextBox1.Text & “‘,'” & TextBox2.Text & “‘,'” & TextBox3.Text & “‘,'” & TextBox4.Text & “‘,'” & TextBox5.Text & “‘,'” & TextBox6.Text & “‘,'” & TextBox7.Text & “‘,'” & TextBox8.Text & “‘,'” & TextBox9.Text & “‘,'” & TextBox10.Text & “‘,'” & TextBox11.Text & “‘,'” & TextBox12.Text & “‘)”, con)
cm.ExecuteNonQuery()
MsgBox(” Record inserted “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox11.Text = “”
TextBox12.Text = “”
TextBox1.Focus()
con.Close()
End If

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Billl_insert
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Private Sub Billl_insert_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “DServer=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
If (TextBox1.Text = “”) Then

MsgBox(” Bill no is compulsary to enter “)
Else

con.Open()
cm = New SqlCommand(“insert into Bill_Table values (‘” & TextBox1.Text & “‘,'” & TextBox2.Text & “‘,'” & TextBox3.Text & “‘,'” & TextBox4.Text & “‘,'” & TextBox5.Text & “‘,'” & TextBox6.Text & “‘,'” & TextBox7.Text & “‘,'” & TextBox8.Text & “‘,'” & TextBox9.Text & “‘,'” & TextBox10.Text & “‘,'” & TextBox11.Text & “‘,'” & TextBox12.Text & “‘,'” & TextBox13.Text & “‘,'” & TextBox14.Text & “‘,'” & TextBox15.Text & “‘,'” & TextBox16.Text & “‘,'” & TextBox17.Text & “‘,'” & TextBox18.Text & “‘,'” & TextBox19.Text & “‘)”, con)
cm.ExecuteNonQuery()
MsgBox(” Record inserted “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox11.Text = “”
TextBox12.Text = “”
TextBox13.Text = “”
TextBox14.Text = “”
TextBox15.Text = “”
TextBox16.Text = “”
TextBox17.Text = “”
TextBox18.Text = “”
TextBox19.Text = “”
TextBox20.Text = “”
TextBox1.Focus()
con.Close()
End If

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Emp_search

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

cm = New SqlCommand(“select *from Emp_Details where Emp_id=@Emp_id”, con)
Dim a As New SqlParameter
a = New SqlParameter(“@Emp_id”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cm.Parameters.Add(a)
data = New SqlDataAdapter
data.SelectCommand = cm
dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
DataGridView1.DataSource = dt

End If
End Sub

Private Sub Emp_search_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Transaction_Search

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

cm = New SqlCommand(“select *from Transaction_Details where Transaction_id=@Transaction_id”, con)
Dim a As New SqlParameter
a = New SqlParameter(“@Transaction_id”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cm.Parameters.Add(a)
data = New SqlDataAdapter
data.SelectCommand = cm
dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
DataGridView1.DataSource = dt

End If
End Sub

Private Sub Transaction_Search_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Complaint_search

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

cm = New SqlCommand(“select *from Complaint_details where complaint_no=@complaint_no”, con)
Dim a As New SqlParameter
a = New SqlParameter(“@Complaint_no”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cm.Parameters.Add(a)
data = New SqlDataAdapter
data.SelectCommand = cm
dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
DataGridView1.DataSource = dt
End If
End Sub

Private Sub Complaint_search_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Consumer_search

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

cm = New SqlCommand(“select *from Consumer_table where cons_no=@cons_no”, con)
Dim a As New SqlParameter
a = New SqlParameter(“@cons_no”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cm.Parameters.Add(a)
data = New SqlDataAdapter
data.SelectCommand = cm
dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
DataGridView1.DataSource = dt

End If
End Sub

Private Sub TextBox1_TextChanged(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TextBox1.TextChanged

End Sub

Private Sub consumersearch_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Bill_search

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

cm = New SqlCommand(“select *from Bill_Table where Bill_no=@Bill_no”, con)
Dim a As New SqlParameter
a = New SqlParameter(“@Bill_no”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cm.Parameters.Add(a)
data = New SqlDataAdapter
data.SelectCommand = cm
dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
DataGridView1.DataSource = dt

End If
End Sub

Private Sub TextBox1_MouseLeave(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TextBox1.MouseLeave

End Sub

Private Sub Bill_search_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient

Public Class emp_edit
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL billing system ;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
con.Open()
cm = New SqlCommand(“update Emp_Details set Emp_name = ‘” & TextBox2.Text & “‘, Address = ‘” & TextBox3.Text & “‘, Contact_no = ‘” & TextBox4.Text & “‘, Designation = ‘” & TextBox5.Text & “‘, Department = ‘” & TextBox6.Text & “‘,Salary = ‘” & TextBox7.Text & “‘, Date_of_join = ‘” & TextBox8.Text & “‘, Qualification = ‘” & TextBox9.Text & “‘, Expert = ‘” & TextBox10.Text & “‘ where Emp_id = ‘” & TextBox11.Text & “‘”, con)
cm.ExecuteNonQuery()
MsgBox(” Record updated “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox1.Focus()
con.Close()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
data = New SqlDataAdapter(“select * from Emp_details where emp_id='” & TextBox11.Text & “‘”, con)

dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
TextBox1.Text = dt.Rows(0)(0).ToString()
TextBox2.Text = dt.Rows(0)(1).ToString()
TextBox3.Text = dt.Rows(0)(2).ToString()
TextBox4.Text = dt.Rows(0)(3).ToString()
TextBox5.Text = dt.Rows(0)(4).ToString()
TextBox6.Text = dt.Rows(0)(5).ToString()
TextBox7.Text = dt.Rows(0)(6).ToString()
TextBox8.Text = dt.Rows(0)(7).ToString()
TextBox9.Text = dt.Rows(0)(8).ToString()
TextBox10.Text = dt.Rows(0)(9).ToString()
End If

End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click
cm = New SqlCommand(“delete from emp_details where emp_id ='” & TextBox11.Text & “‘”, con)
con.Open()
cm.ExecuteNonQuery()
con.Close()
MsgBox(“your data has been sucessfully deleted”)

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Transaction_edit
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL billing system ;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click

con.Open()
cm = New SqlCommand(“update Transaction_Details set Bill_no = ‘” & TextBox2.Text & “‘, Telephone_no = ‘” & TextBox3.Text & “‘, Consumer_no = ‘” & TextBox4.Text & “‘, bill_date = ‘” & TextBox5.Text & “‘, payment_date = ‘” & TextBox6.Text & “‘, Amount_paid = ‘” & TextBox7.Text & “‘, mode_of_payment = ‘” & TextBox8.Text & “‘, bank = ‘” & TextBox9.Text & “‘, description = ‘” & TextBox10.Text & “‘ where Transaction_id= ‘” & TextBox11.Text & “‘”, con)
cm.ExecuteNonQuery()
MsgBox(” Record updated “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox1.Focus()
con.Close()

End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click
data = New SqlDataAdapter(“select * from Transaction_details where Transaction_id='” & TextBox11.Text & “‘”, con)

dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
TextBox1.Text = dt.Rows(0)(0).ToString()
TextBox2.Text = dt.Rows(0)(1).ToString()
TextBox3.Text = dt.Rows(0)(2).ToString()
TextBox4.Text = dt.Rows(0)(3).ToString()
TextBox5.Text = dt.Rows(0)(4).ToString()
TextBox6.Text = dt.Rows(0)(5).ToString()
TextBox7.Text = dt.Rows(0)(6).ToString()
TextBox8.Text = dt.Rows(0)(7).ToString()
TextBox9.Text = dt.Rows(0)(8).ToString()
TextBox10.Text = dt.Rows(0)(9).ToString()

End If
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
cm = New SqlCommand(“delete from transaction_details where transaction_id ='” & TextBox11.Text & “‘”, con)
con.Open()
cm.ExecuteNonQuery()
con.Close()
MsgBox(“your data has been sucessfully deleted”)

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Complaint_edit
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
Private Sub Complaint_edit_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL billing system ;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
con.Open()

cm = New SqlCommand(“update Complaint_Details set complaint_no = ‘” & TextBox2.Text & “‘, Attend_by = ‘” & TextBox3.Text & “‘, Solved_by = ‘” & TextBox4.Text & “‘, complaint_desc = ‘” & TextBox5.Text & “‘ where complaint_no='” & TextBox6.Text & “‘”, con)
cm.ExecuteNonQuery()
MsgBox(” Record updated “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox1.Focus()
con.Close()
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click
cm = New SqlCommand(“delete from Complaint_Details where complaint_no ='” & TextBox6.Text & “‘”, con)
con.Open()
cm.ExecuteNonQuery()
con.Close()
MsgBox(“your data has been sucessfully deleted”)

End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

cm = New SqlCommand(“select *from Complaint_Details where complaint_no= ‘” & TextBox6.Text & “‘”, con)
Dim a As New SqlParameter
a = New SqlParameter(“@complaint_no”, SqlDbType.VarChar)
a.Value = TextBox1.Text
cm.Parameters.Add(a)
data = New SqlDataAdapter
data.SelectCommand = cm
dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)

Else
TextBox1.Text = dt.Rows(0)(0).ToString()
TextBox2.Text = dt.Rows(0)(1).ToString()
TextBox3.Text = dt.Rows(0)(2).ToString()
TextBox4.Text = dt.Rows(0)(3).ToString()
TextBox5.Text = dt.Rows(0)(4).ToString()

End If

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Consumer_edit
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter

Private Sub Consumer_edit_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL billing system ;Integrated Security=True”
End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
con.Open()

cm = New SqlCommand(“update consumer_table set cons_name = ‘” & TextBox2.Text & “‘, cons_add = ‘” & TextBox3.Text & “‘, cons_city = ‘” & TextBox4.Text & “‘, pin = ‘” & TextBox5.Text & “‘, contact_no = ‘” & TextBox6.Text & “‘,Email = ‘” & TextBox7.Text & “‘,Date_of_reg = ‘” & TextBox8.Text & “‘, traiff_plan = ‘” & TextBox9.Text & “‘, category = ‘” & TextBox10.Text & “‘, reg_charges = ‘” & TextBox11.Text & “‘, telephone_no = ‘” & TextBox12.Text & “‘ where cons_no = ‘” & TextBox13.Text & “‘”, con)
cm.ExecuteNonQuery()
MsgBox(” Record updated “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox11.Text = “”
TextBox12.Text = “”
TextBox1.Focus()
con.Close()
End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
data = New SqlDataAdapter(“select * from Consumer_table where Cons_no='” & TextBox13.Text & “‘”, con)

dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
TextBox1.Text = dt.Rows(0)(0).ToString()
TextBox2.Text = dt.Rows(0)(1).ToString()
TextBox3.Text = dt.Rows(0)(2).ToString()
TextBox4.Text = dt.Rows(0)(3).ToString()
TextBox5.Text = dt.Rows(0)(4).ToString()
TextBox6.Text = dt.Rows(0)(5).ToString()
TextBox7.Text = dt.Rows(0)(6).ToString()
TextBox8.Text = dt.Rows(0)(7).ToString()
TextBox9.Text = dt.Rows(0)(8).ToString()
TextBox10.Text = dt.Rows(0)(9).ToString()
TextBox11.Text = dt.Rows(0)(10).ToString()
TextBox12.Text = dt.Rows(0)(11).ToString()

End If
End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click
cm = New SqlCommand(“delete from consumer_table where cons_no ='” & TextBox13.Text & “‘”, con)
con.Open()
cm.ExecuteNonQuery()
con.Close()
MsgBox(“your data has been sucessfully deleted”)

End Sub

Private Sub TextBox13_MouseHover(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles TextBox13.MouseHover

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Bill_edit
Dim con As New SqlConnection
Dim cm As New SqlCommand
Dim dt As New DataTable
Dim data As New SqlDataAdapter
Private Sub Bill_edit_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
con.ConnectionString = “Server=.\sqlexpress;Initial Catalog=MTNL Billing System;Integrated Security=True”

End Sub

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
con.Open()

cm = New SqlCommand(“update Bill_table set Telephone_no = ‘” & TextBox2.Text & “‘, due_date = ‘” & TextBox3.Text & “‘, Amt_after_due = ‘” & TextBox4.Text & “‘, Previous_read = ‘” & TextBox5.Text & “‘, pre_read_date = ‘” & TextBox6.Text & “‘,Curr_read = ‘” & TextBox7.Text & “‘, Curr_read_date = ‘” & TextBox8.Text & “‘, Meter_call = ‘” & TextBox9.Text & “‘, free_call = ‘” & TextBox10.Text & “‘, Net_Calls_chargeable = ‘” & TextBox11.Text & “‘, Call_charges = ‘” & TextBox12.Text & “‘,Monthly_service='” & TextBox13.Text & “‘,Service_tax='” & TextBox14.Text & “‘,Other_debits='” & TextBox15.Text & “‘,Other_credits='” & TextBox16.Text & “‘,Amt_paid='” & TextBox17.Text & “‘,Call_rate='” & TextBox18.Text & “‘,Status='” & TextBox19.Text & “‘ where bill_no = ‘” & TextBox1.Text & “‘”, con)
cm.ExecuteNonQuery()
MsgBox(” Record updated “)
TextBox1.Text = “”
TextBox2.Text = “”
TextBox3.Text = “”
TextBox4.Text = “”
TextBox5.Text = “”
TextBox6.Text = “”
TextBox7.Text = “”
TextBox8.Text = “”
TextBox9.Text = “”
TextBox10.Text = “”
TextBox11.Text = “”
TextBox12.Text = “”
TextBox13.Text = “”
TextBox14.Text = “”
TextBox15.Text = “”
TextBox16.Text = “”
TextBox17.Text = “”
TextBox18.Text = “”
TextBox19.Text = “”

TextBox1.Focus()
con.Close()

End Sub

Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button3.Click
cm = New SqlCommand(“delete from Bill_Table where Bill_no ='” & TextBox21.Text & “‘”, con)
con.Open()
cm.ExecuteNonQuery()
con.Close()
MsgBox(“your data has been sucessfully deleted”)

End Sub

Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button2.Click
data = New SqlDataAdapter(“select * from Bill_table where bill_no='” & TextBox21.Text & “‘”, con)

dt = New DataTable
data.Fill(dt)
If (dt.Rows.Count = 0) Then
MsgBox(“Sorry Not Found”)
Else
TextBox1.Text = dt.Rows(0)(0).ToString()
TextBox2.Text = dt.Rows(0)(1).ToString()
TextBox3.Text = dt.Rows(0)(2).ToString()
TextBox4.Text = dt.Rows(0)(3).ToString()
TextBox5.Text = dt.Rows(0)(4).ToString()
TextBox6.Text = dt.Rows(0)(5).ToString()
TextBox7.Text = dt.Rows(0)(6).ToString()
TextBox8.Text = dt.Rows(0)(7).ToString()
TextBox9.Text = dt.Rows(0)(8).ToString()
TextBox10.Text = dt.Rows(0)(9).ToString()
TextBox11.Text = dt.Rows(0)(10).ToString()
TextBox12.Text = dt.Rows(0)(11).ToString()
TextBox13.Text = dt.Rows(0)(12).ToString()
TextBox14.Text = dt.Rows(0)(13).ToString()
TextBox15.Text = dt.Rows(0)(14).ToString()
TextBox16.Text = dt.Rows(0)(15).ToString()
TextBox17.Text = dt.Rows(0)(16).ToString()
TextBox18.Text = dt.Rows(0)(17).ToString()
TextBox19.Text = dt.Rows(0)(18).ToString()
End If
End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Employee_Report
Dim con As New SqlConnection
Dim da As New SqlDataAdapter
Private Sub CrystalReportViewer1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CrystalReportViewer1.Load
con = New SqlConnection(“Server=.\sqlexpress;Initial Catalog= MTNL Billing System;Integrated Security=True”)

da = New SqlDataAdapter(“select *from Emp_details”, con)
Dim ds = New DataSet()
da.Fill(ds)
Dim cr = New CrystalReport10
cr.SetDataSource(ds)
CrystalReportViewer1.ReportSource = cr
End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Transaction_Report
Dim con As New SqlConnection
Dim da As New SqlDataAdapter
Private Sub CrystalReportViewer1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CrystalReportViewer1.Load

con = New SqlConnection(“Server=.\sqlexpress;Initial Catalog= MTNL Billing System;Integrated Security=True”)

da = New SqlDataAdapter(“select *from transaction_details”, con)
Dim ds = New DataSet()
da.Fill(ds)
Dim cr = New CrystalReport11
cr.SetDataSource(ds)
CrystalReportViewer1.ReportSource = cr

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class Complaint_Report
Dim con As New SqlConnection
Dim da As New SqlDataAdapter
Private Sub CrystalReportViewer1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CrystalReportViewer1.Load
con = New SqlConnection(“Server=.\sqlexpress;Initial Catalog= MTNL Billing System;Integrated Security=True”)

da = New SqlDataAdapter(“select *from Complaint_details”, con)
Dim ds = New DataSet()
da.Fill(ds)
Dim cr = New CrystalReport8
cr.SetDataSource(ds)
CrystalReportViewer1.ReportSource = cr
End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient
Public Class consumer_report2

Private Sub CrystalReportViewer1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CrystalReportViewer1.Load
Dim con As New SqlConnection
Dim da As New SqlDataAdapter

con = New SqlConnection(“Server=.\sqlexpress;Initial Catalog= MTNL Billing System;Integrated Security=True”)

da = New SqlDataAdapter(“select *from Consumer_table”, con)
Dim ds = New DataSet()
da.Fill(ds)
Dim cr = New CrystalReport9
cr.SetDataSource(ds)
CrystalReportViewer1.ReportSource = cr

End Sub
End Class

Imports System.Data
Imports System.Data.SqlClient

Public Class Bill_Report
Dim con As New SqlConnection
Dim da As New SqlDataAdapter
Private Sub REPORT_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load

End Sub

Private Sub CrystalReportViewer1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles CrystalReportViewer1.Load

con = New SqlConnection(“Server=.\sqlexpress;Initial Catalog= MTNL Billing System;Integrated Security=True”)

da = New SqlDataAdapter(“select *from Bill_table”, con)
Dim ds = New DataSet()
da.Fill(ds)
Dim cr = New CrystalReport7
cr.SetDataSource(ds)
CrystalReportViewer1.ReportSource = cr

End Sub
End Class

5.2 CODE EFFICIENCY

Reviewing of Code efficiency for a module is carried out after the module is successfully compiled and all the syntax errors eliminated. Code efficiency review is extremely cost-effective strategies for reduction in coding errors in order to produce high quality code. Normally, two types of efficiency are carried out on the code of a module – code optimization and code inspection. The procedure and final objective of these two efficiency techniques are very different as discussed below.

5.3 OPTIMIZATION OF CODE

Code optimization is an informal code analysis technique. In this technique, after a module has been coded, it is successfully compiled and all syntax errors are eliminated. Some members of the development team are given the code a few days before the optimization meeting to read and understand the code. Each member selects some test cases and simulates execution of the code by hand (i.e. trace execution through each statement and function execution). The main objectives of the optimization are to discover the algorithmic and logical errors in the code. The members note down their findings to discuss these in a optimization meeting where the coder of the module is also present.

Even though a code optimization is an informal analysis technique, several guidelines have evolved over the years for making this naïve technique more effective and useful. Of course, these guidelines are based on personal experience, common sense, and several subjective factors. Therefore are based on personal experience, common sense, and several subjective factors. Therefore, guidelines should be considered as examples rather than as rules to be applied dogmatically. Some of these guidelines are the following:

The team performing the code optimization should not be either too big or too small. Ideally, it should consist of three to seven members.

6.1 TESTING PHASE

One of the purposes of the testing is to validate and verify the system. Verification means checking the system to ensure that it is doing what the function is supposed to do and Validation means checking to ensure that system is doing what the user wants it to do.

No program or system design is perfect; communication between the user and the designer is not always complete or clear, and time is usually short. The result is errors and more errors. Theoretically, a newly designed system should have all the pieces in working order, but in reality, each piece works independently. Now is the time to put all the pieces into one system and test it to determine whether it meets the user’s requirements. This is the best chance to detect and correct errors before the system is implemented. The purpose of system testing is to consider all the likely variations to which it will be subjected and then push the system to its limits. If we implement the system without proper testing then it might cause the problems.

1. Communication between the user and the designer.
2. The programmer’s ability to generate a code that reflects exactly the system specification.
3. The time frame for the design.

Theoretically, a new designed system should have all the pieces in working order, but in reality, each piece works independently. Now is the time to put all the pieces into one system and test it to determine whether it meets the requirements of the user.

The process of system testing and the steps taken to validate and prepare a system for final implementation are:

6.2 LEVELS OF TESTING
The different types of testing are as follows:

1. UNIT TESTING:
This is the smallest testable unit of a computer system and is normally tested using the white box testing. The author of the programs usually carries out unit tests.

2. INTEGRATION TESTING:

In integration testing, the different units of the system are integrated together to form the complete system and this type of testing checks the system as whole to ensure that it is doing what is supposed to do. The testing of an integrated system can be carried out top-down, bottom-up, or big-bang. In this type of testing, some parts will be tested with white box testing and some with black box testing techniques. This type of testing plays very important role in increasing the systems productivity. We have checked our system by using the integration testing techniques.

3. SYSTEM TESTING:
A part from testing the system to validate the functionality of software against the requirements, it is also necessary to test the non-functional aspect of the system. Some examples of non-functional tools include tests to check performance, data security, usability/user friendliness, volume, load/stress that we have used in our project to test the various modules.

System testing consists of the following steps:

1. Program(s) testing.
2. String testing.
3. System testing.
4. System documentation.
5. User acceptance testing.

4. FIELD TESTING:
This is a special type of testing that may be very important in some projects. Here the system is tested in the actual operational surroundings. The interfaces with other systems and the real world are checked. This type of testing is very rarely used. So far our project is concerned; we haven’t tested our project using the field testing.

5. ACCEPTANCE TESTING:
After the developer has completed all rounds of testing and he is satisfied with the system, then the user takes over and re-tests the system from his point of view to judge whether it is acceptable according to some previously identified criteria. This is almost always a tricky situation in the project because of the inherent conflict between the developer and the user. In this project, it is the job of the bookstores to check the system that whether the made system fulfills the goals or not.

5.2 Debugging and Code improvement

Testing is vital to the success of the system. System testing makes a logical assumption that if all the parts of the system are correct, the goal will be successfully achieved. Inadequate testing results in two types of problems:

1. The time lag between the cause and the appearance of the problem.
2. The effect of system errors on the files and records within the system.

ACTIVITY NETWORK FOR SYSTEM TESTING

The test plan entails the following activities:
1. Prepare test plan.
2. Specify conditions for user acceptance testing.
3. Prepare test data for program testing.
4. Prepare test data for transaction path testing.
5. Plan user training.
6. Compile/assemble programs.
7. Prepare job performance aids.
8. Prepare operational documents.

PREPARE TEST : A workable test plan must be prepared in accordance with established design specifications. It includes the following items:
• Outputs expected from the system.
• Criteria for evaluating outputs.
• A volume of test data.
• Procedure for using test data.
• Personnel and training requirements.

SPECIFY CONDITIONS FOR USER ACCEPTANCE TESTING
Planning for user acceptance testing calls for the analyst and the user to agree on conditions for the test.
PREPARE TEST DATA FOR PROGRAM TESTING
As each program is coded, test data are prepared and documented to ensure that all aspects of the program are properly tested.

PREPARE TEST DATA FOR TRANSACTION PATH TESTING
This activity develops the data required for testing every condition and transactions to be introduced into the system. The path of each transaction from origin to destination is carefully tested reliable results.

PLAN USER TRAINING
User training is designed to prepare the user for testing and converting the system. User involvement and training take place parallel with programming for three reasons:
• The system group has time available to spend on training while the programs are being written.
• Initiating a user-training program gives the systems group a clearer image of the user’s interest in the new system.
• A trained user participates more effectively in system testing.

The training plan is followed by preparation of the user training manual and other text materials.
COMPILE / ASSEMBLE PROGRAMS
All programs have to be compiled / assembled for testing.

PREPARE JOB PERFORMANCE AIDS
In this activity the materials to be used by personnel to run the system are specified and scheduled. This includes a display of materials.

PREPARE OPERATIONAL DOCUMENTS
During the test plan stage, all operational documents are finalized including copies of the operational formats required by the candidate system.

SYSTEMS TESTING
The computer department to ensure that the system functions as specified does this testing. This testing is important to ensure that a working system is handed over to the user for acceptance testing.

ACCEPTANCE TESTING
The user to ensure that the system functions, as the user actually wanted performs this testing. With prototyping techniques, this stage becomes very much a formality to check the accuracy and completeness of processing. The screen layouts and output should already have been tested during the prototyping phase.
An error in the program code can remain undetected indefinitely. To prevent this from happening the code was tested at various levels. To successfully test a system, each condition, and combinations of conditions had to be tested. Each program was tested and linked to other programs. This unit of program is tested and linked to other units and so on until the complete system has been tested.
The purpose of testing is to ensure that each program is fully tested. To do so a test plan had to be created. The test plan consists of a number of test runs such as the valid paths through the code, and the exception and error handling paths. For each test run there is a list of conditions tested, the test data used and the result expected. The test plan was then reviewed to check that each path through the code is tested correctly. It is the responsibility of the programmer to collect the data that will produce the required test condition.

6.3 TEST CASES

TEST DATA Specifications for MTNL Billing System user form1
Test Date Programmer User Name: MTNL Billing System
Tested By: Project ID: 11107680

User name
the fields are required.Can enter only letters, spaces, hyphens, and apostrophes. No numeric & special characters are allowed( Length upto 32 characters)

Password The fields are required.Can enter only numeric ( Length upto 8 digit )

Consumer No the fields are required.Can enter only letters, spaces, hyphens, and apostrophes. No numeric & special characters are allowed( Length upto 132 characters)

Consumer name only 8 or 10 digit You may use numbers

Contact No. the fields are required.Can enter only letters, spaces, allowed( Length upto 80 characters)

Bill No. Use 4 to 32 characters and start with a letter. You may use letters, numbers, underscores, and one dot(.)
Call Charges
Payment Date
Amount Paid

Positive Test cases for registration form

T.C ID PRE-CONDITION T.C Email id T.C DATA EXPECTED ACTUAL RESULT
1 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Akhila Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. User Name are required. Ok Pass
2 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field baljeet singh Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. User Name are required. Ok Pass
3 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Subhash Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. User Name are required. Ok Pass
4 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Jai prakash Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.User Name are required. Ok Pass
5 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Rahul Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.User Name are required. Ok Pass

6 User should be on https://MTNL Billing System/registration?And is on Password Field Check the functionality of Password option 2468 The fields are required.Can enter only numeric ( Length upto 8 digit ) Ok Pass

7 User should be on https://MTNL Billing System/registration?And is on Consumer No. Field Check the functionality of Consumer No field Jaiprakash@yahoo.com
Will accept only letters, spaces, hyphens, and apostrophes.Length upto 132 characters. User Name are required. Ok Pass
8 User should be on https://MTNL Billing System/registration?And is on Consumer No. Field Check the functionality of Consumer No field baljeetsingh111@yahoo.com
Will accept only letters, spaces, hyphens, and apostrophes.Length upto 132 characters. User Name are required. Ok Pass
9 User should be on https://MTNL Billing System/registration?And is on Consumer No. Field Check the functionality of Consumer No field subhash@yahoo.com
Will accept only letters, spaces, hyphens, and apostrophes.Length upto 132 characters. User Name are required. Ok Pass

10 User should be on https://MTNL Billing System/registration?And is on Consumer Name Field Check the functionality of Consumer field Patel nagar Will accept only numeric upto 8 digit . User ID is required Ok Pass
11 User should be on https://MTNL Billing System/registration?And is on Consumer Name Field Check the functionality of Consumer Name field tilak nagar Will accept only numeric upto 8 digit . User Id are required Ok Pass

12 User should be on https://MTNL Billing System/registration?And is on Contact no Field Check the functionality of Contact No. field 9856278314 Will accept only letters, spaces.Length upto 80 characters. User Name are required. Ok Pass
13 User should be on https://MTNL Billing System/registration?And is on Contact no Field Check the functionality of Contact No. field Kanpur delta Will accept only letters, spaces.Length upto 80 characters. User Name are required. Ok Pass

14 User should be on https://MTNL Billing System/registration?And is on Bill No Field Check the functionality of Bill No option Mumbai Will accept only letters, numbers, underscores, and one dot (.) Ok pass
15 User should be on https://MTNL Billing System/registration?And is on Bill No Field Check the functionality of Bill No option Delhi Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
16 User should be on https://MTNL Billing System/registration?And is on Bill No Field Check the functionality of Bill No option Punjab Will accept only letters, numbers, underscores, and one dot (.) Ok Pass

User should be on https://MTNL Billing System/registration?And is on Call Charges Field Check the functionality of Call Charges option kerala Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
User should be on https://MTNL Billing System/registration?And is on Call Charges Field Check the functionality of Call charges option Patna Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
User should be on https://MTNL Billing System/registration?And is on Call Charges Field Check the functionality of Call Charges option mumbai Will accept only letters, numbers, underscores, and one dot (.) Ok Pass

User should be on https://MTNL Billing System/registration?And is on Payment Date Field Check the functionality of Payment Date option 2/3/2012 Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
User should be on https://MTNL Billing System/registration?And is on Payment Date Field Check the functionality of Payment Date option 5/6/2012 Will accept only letters, numbers, underscores, and one dot (.) Ok Pass

User should be on https://MTNL Billing System/registration?And is on Amount Paid Field Check the functionality of Amount Paid option 4000/- Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
User should be on https://MTNL Billing System/registration?And is on Amount Paid Field Check the functionality of Amount Paid option 20000/- Will accept only letters, numbers, underscores, and one dot (.) Ok Pass
17 User should be on https://MTNL Billing System/registration?And is on Amount Paid Field Check the functionality of Amount Paid option 6000/- Will accept only letters, numbers, underscores, and one dot (.) Ok Pass

Negative Test cases for registration form

T.C ID PRE-CONDITION T.C Email id T.C DATA EXPECTED ACTUAL RESULT
1 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Akhila Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. User Name are required. Invalid Fail
2 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field baljeet singh Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. User Name are required. Invalid Fail
3 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Subhash Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters.User Name are required. Invalid Fail
4 User should be on https://MTNL Billing System/registration? And is on User Name Field Check the functionality of User Name field Jai prakash Will accept only letters, spaces, hyphens, and apostrophes.Length upto 32 characters. User Name are required. Invalid Fail

5 User should be on https://MTNL Billing System/registration?And is on Password Field Check the functionality of Password option 2468 The fields are required.Can enter only numeric ( Length upto 8 digit ) Invalid Fail

6 User should be on https://MTNL Billing System/registration?And is on Consumer No Field Check the functionality of Consumer No field Jaiprakash@yahoo.com
Will accept only letters, spaces, hyphens, and apostrophes.Length upto 132 characters. User Name are required. Invalid Fail
7 User should be on https://MTNL Billing System/registration?And is on Consumer No Field Check the functionality of Consumer No field baljeetsingh111@yahoo.com
Will accept only letters, spaces, hyphens, and apostrophes.Length upto 132 characters. User Name are required. Invalid Fail

8 User should be on https://MTNL Billing System/registration?And is on Consumer Name Field Check the functionality of Consumer Name Field Patel nagar Will accept only numeric upto 8 digit . Customer ID are required Invalid Fail
9 User should be on https://MTNL Billing System/registration?And is on Consumer Name Field Check the functionality of Consumer Name Field tilak nagar Will accept only numeric upto 8 digit . Customer ID are required Invalid Fail

10 User should be on https://MTNL Billing System/registration?And is on Contact no Field Check the functionality of Contact No. field 9856278314
Will accept only letters, spaces.Length upto 80 characters. User Name are required. Invalid Fail
11 User should be on https://MTNL Billing System/registration?And is on Contact no Field Check the functionality of Contact No. field 956019916 Will accept only letters, spaces.Length upto 80 characters. User Name are required. Invalid Fail

12 User should be on https://MTNL Billing System/registration?And is on Bill No Field Check the functionality of Bill No option Mumbai Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
13 User should be on https://MTNL Billing System/registration?And is on Bill No Field Check the functionality of Bill No option Delhi Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail

User should be on https://MTNL Billing System/registration?And is on Call Charges Field Check the functionality of State option Maharastra Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
User should be on https://MTNL Billing System/registration?And is on Call Charges Field Check the functionality of Call Charges option Delhi Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
User should be on https://MTNL Billing System/registration?And is on Call Charges Field Check the functionality of Call Charges option Punjab Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail

User should be on https://MTNL Billing System/registration?And is on Payment Date Field Check the functionality of Payment Date option 2/3/2012 Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
User should be on https://MTNL Billing System/registration?And is on Payment Date Field Check the functionality of Payment Date option 5/6/2012 Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail

User should be on https://MTNL Billing System/registration?And is on Amount Paid Field Check the functionality of Amount Paid option 4000/- Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail
14 User should be on https://MTNL Billing System/registration?And is on Amount Paid Field Check the functionality of Amount Paid option 20000/- Will accept only letters, numbers, underscores, and one dot (.) .The ID must be available. Invalid Fail

7.1 SYSTEM IMPLEMENTATION MAINTENANCE AND REVIEW

As we know, creating software is one thing and the implementation of the created software is another. The process of implementing software is much difficult as compared to the task of creating the project. First we have to implement the software on a small scale for removing the bugs and other errors in the project and after removing them we can implement the software on a large scale.
Before we think in terms of implementing the Software on a large basis, we must consider the Hardware requirements.
Whenever we develop software or project a certain hardware and software is being used by the programmer for developing the project. The hardware and software to be used by the programmer for developing the project should be such that it would result in the development of a project, which would satisfy all the basic needs for which the project has been created by the programmer. The Hardware should be such that cost constraints of the Client should also be taken into account without affecting the performance.

7.2 HARDWARE EVALUATION FACTORS

When we evaluate computer hardware, we should first investigate specific physical and performance characteristics for each hardware component to be acquired. These specific questions must be answered concerning many important factors. These hardware evaluation factors questions are summarized in the below figure.
Notice that there is much more to evaluating hardware than determining the fastest and cheapest computing device. For e.g. the question of possible obsolescence must be addressed by making a technology evaluation. The factor of ergonomics is also very important. Ergonomics is the science and technology that tries to ensure that computers and other technologies are “user-friendly”, that is safe, comfortable and easy to use. Connectivity is another important evaluation factor, since so many computer systems are now interconnected within wide area or local area telecommunications networks.

7.3 Evaluation Factors for Hardware
1) Performance
2) Cost
3) Reliability
4) Availability
5) Compatibility
6) Modularity
7) Technology
8) Ergonomics
9) Connectivity
10) Environmental requirements
11) Software
12) Support

7.4 EVALUATION FACTORS FOR SOFTWAE

Software can be evaluated according to many factors similar to the hardware evaluation. Thus the factors of performance, cost, reliability, compatibility, modularity, technology, ergonomics, and support should be used to evaluate proposed software acquisitions. In addition, however, the software evaluation factors are summarized in below figure. For e.g. some software packages require too much memory capacity and are notoriously slow, hard to use, or poorly documented. They are not a good selection for most end users, even if offered at attractive prices.

Software evaluation factors
1. EFFICIENCY: is the software a well-written system of computer instructions that does not use much memory capacity or CPU time?
2. FLEXIBILITY: can it handle its processing assignments easily without major modifications?
3. SECURITY: does it provide control procedures for errors, malfunctions and improper use?
4. LANGUAGE: do our computer programmers and users write it in a programming language that is used?
5. DOCUMENTATION: is the s/w well documented? Does it include helpful user instructions?
6. HARDWARE: does existing hardware have the features required to best use this software?
7. Other characteristics of hardware such as its performance, what about the cost, how much is reliable and etc.

7.5 CONVERSION AND TRAINING

An important aspect of is to make sure that the new design is implemented to establish standards. The term implementation has different meanings, ranging form the conversion of a basic application to a complete replacement of a computer system. Implementation is used here to mean the process of converting a new or revise system into an operational one. Conversion is one aspect of implementation. Conversion means changing form one system to another. The objective is to put the tested system into operation while holding costs, risks, and personnel irritation to a minimum. It involves creating computer-compatible files, training the operation staff, and installing terminal and hardware. A critical aspect of conversion is not disrupting the functioning of the organization.

When a new system is used over and old, existing and running one, there are always compatibility errors. These errors are caused because of the lack of equipment or personnel to work the new system. Running any specified system at an organization does require some or other hardware or, in this case, software requirement as well.

Conversion is one aspect of implementation review & software maintenance.

There are three types of implementation:

1. Implementation of a computer system to replace a manual system. The problems encountered are converting files, training users, creating accurate files and verifying printouts for integrity.
2. Implementation of a new computer system to replace an existing one. This is usually a difficult conversion. If not properly planned there can be many problems. Some large computer systems have taken as long as year to convert.
3. Implementation of a modified application to replace an existing one, using the same computer. This type of conversion is relatively easy to handle, provided there are no major changes in the files.

7.6 TRAINING NEEDS

Training needs refer to the gaining of knowledge required for running the system.

First of all the system is a computer based system therefore the person should have good knowledge about computer and its working.
He should know how to use software’s on the computer.

For a better usage and working of the software the organization should appoint a person who has good knowledge of all the required software. The organization gets a person trained through different institutes present in the market. The training should be as per the above requirements.

8. COST ESTIMATION OF THE PROJECT

Cost in a project is due to the requirements for software, hardware, and human resources. Hardware resources are computer time, terminal time and memory required for the project. Software resources include the tools and compilers needed during development. The bulk of cost of software development is due to human resources needed. Cost estimates are determined in terms of person-months (PM).

Total No. Of Persons Involved In This Project:

1. Administrator

2. Senior Programmer

3. Junior Programmers

4. On line Users.

Since this Project will complete in 4 months

COST ESTIMATE: (Salary of Project Manager + Salary of Senior Programmer + 2 * Salary of Junior Programmer) * 2

9. GANTT & PERT CHART

GANT CHART

Gantt charts mainly used to allocate resources to activities. The resources allocated to activities include staff, hardware, and software. Gantt charts (named after its developer Henry Gantt) are useful for resource planning. A Gantt chart is special type of bar chart where each bar represents an activity. The bars are drawn along a timeline. The length of each bar is proportional to the duration of the time planned for the corresponding activity.
Gantt chart is a project scheduling technique. Progress can be represented easily in a Gantt chart, by coloring each milestone when completed. The project will start in the month of June and end after 4 months at the end of September.

System Design

Detailed Design

Coding

Unit Testing

Test Plan

Testing

Jun . Jul. Aug. Sep.

Pert Chart

PERT (Project Evaluation and Review Technique) charts consist of a network of boxes and arrows. The boxes represent activities and the arrows represent task dependencies.

PERT chart represents the statistical variations in the project estimates assuming a normal distribution. Thus in a PERT chart instead of making a single estimate for each task, pessimistic, likely, and optimistic estimates are also made. The boxes of PERT charts are usually annotated with the pessimistic, likely, and optimistic estimates for every task. Since all possible completion times between the minimum and maximum durations for every task have to be considered, there are many critical paths, depending on the permutations of the estimates for each task. This makes critical path analysis in PERT charts very complex. A critical path in a PERT chart is shown by using thicker arrows. The PERT chart representation of the Mtnl Billing problem of Figure A. is shown in Figure B.

Task ES EF LS LF ST
Specification Part 0 15 0 15 0
Design Database Part 15 60 15 60 0
Design GUI Part 15 45 90 120 75
Code Database Part 60 165 60 165 0
Code GUI Part 45 90 120 165 75
Integrate and Test 165 285 165 285 0
Write User Manual 15 75 225 285 210

Figure A : Different Tasks for the MTNL Billing system shown in above table.

FIGURE B: PERT chart representation of the MTNL BILLING SYSTEM.

PERT charts are a more sophisticated form of activity chart. In activity diagrams only the estimated task durations are represented. Since the actual durations might vary from the estimated durations, the utility of the activity diagrams is limited.

10. SECURITY AND VALIDATION CHECKS

In this project we have used following validation checks.

 While entering the data into the form it will check for the name of the client is properly filled & it should not be null.

 Whenever we enter the data for the new customer, company, or user will automatically check the details from the database tables and also generate the connection number automatically.

 Similarly in the complaint table complaint number will generate automatically.

 Entered text / number should not exceed the limit (width).

 Almost for all fields we have used the validation for example if name of the fields requires the text type of data then it will check for the string and if the data is numeric then it will check if the number entered is proper numeric or not.

11. FUTURE SCOPE AND FURTHER ENCHANCEMENT OF THE PROJECT

This project will be developed for the users (employees) to get information about the bills, complaints, connection. Utmost care and back-up procedures must be established to ensure 100% successful implementation of the MTNL BILLING. In case of system failure, the organization should be in a position to process the transaction with another organization or if the worst comes to the worst, it should be in a position to complete it manually.
The decision to automate generally depends on the needs to have accurate, consistent and timely data in a variety of reporting formats. But the most important factor that should be considered is –

 Be sure to take future growth into consideration and evaluate whether the software package could be modified if the organization expands in the future or you need to revise the system.

 The next generation of Windows-based computerized systems would be changing the way owners and management think about running their businesses. It would a powerful tool that gives them more ways to get their financial Information so that they can better manage and grow their business.

 The next generation of systems would take advantage of the latest technologies, including Microsoft Windows XP and Sql Server to offer access and integrate with all aspects of a business. Keeping this in view we could develop systems that would work efficiently and integrate seamlessly in virtually any industry setting, even up to mid-sized corporations and divisions of larger organizations.

 Consider another setting, where the users are not comfortable on computers, for such users we can develop systems where the users can have their own personalized menu setup in the accounting software so that they no longer have to search around to find what they need.

 Now consider the Internet. This wide open information exchange network comes with many benefits for businesses, including breaking down physical barriers as to where he/she can consult to the companies.

 Adding other capabilities can be added time to time. These are
• Application may be installed client server.
• Application can upgraded according to Employees Requirements with little changes made
• Application may be transferred to latest RDMBS like Sql Server with little changes in current code. Use for Security purpose

NOTE: In a nutshell we have a lot of scope to further enhance the futures and functionalities of the proposed Solution.

12. CONCLUSION

It has been developed in MTNL BILLING SYSTEM, keeping in mind the specifications of the system. For designing the system we have used simple data flow diagrams.

Overall the project teaches us the essential skills like:
 Using system analysis and design techniques like data flow diagram in designing the system.
 Understanding the database handling and query processing using SQL Server.

13. BIBLIOGRAPHY

 Visual Basic.NET 2008 Jamew Foxall
 Fundamentals Of Software Engineering Rajib Mall
 Software Engineering K.K.Aggarwal & Yogesh Singh
 Visual Basic.NET Projects Tony Martin,Dominic Selly
 Visual Basic.Net Professional Projects Kuljit Kaur,Pooja Bembey

Leave a Reply