elecrtricity bill management system, Assignments of Database Management Systems (DBMS)

Download elecrtricity bill management system and more Assignments Database Management Systems (DBMS) in PDF only on Docsity!

Report of Electricity Billing System

Introduction of the Project Electricity Billing System:

The "Electricity Billing System" has been developed to override the problems prevailing in the practicing manual system. This software is supported to eliminate and in some cases reduce the hardships faced by this existing system. Moreover this system is designed for the particular need of the company to carry out operations in a smooth and effective manner. The application is reduced as much as possible to avoid errors while entering the data. It also provides error message while entering invalid data. No formal knowledge is needed for the user to use this system. Thus by this all it proves it is user-friendly. Electricity Billing System , as described above, can lead to error free, secure, reliable and fast management system. It can assist the user to concentrate on their other activities rather to concentrate on the record keeping. Thus it will help organization in better utilization of resources. Every organization, whether big or small, has challenges to overcome and managing the information of Bill, Customer, Electricity, Bill Receipt, Payment. Every Electricity Billing System has different Customer needs, therefore we design exclusive employee management systems that are adapted to your managerial requirements. This is designed to assist in strategic planning, and will help you ensure that your organization is equipped with the right level of information and details for your future goals. Also, for those busy executive who are always on the go, our systems come with remote access features, which will allow you to manage your workforce anytime, at all times. These systems will ultimately allow you to better manage resources.

Objective of Project on Electricity Billing System:

The main objective of the Project on Electricity Billing System is to manage the details of Customer, Bill, Connection, Electricity, Payment. It manages all the information about Customer, Bill Receipt, Payment, Customer. The project is totally built at administrative end and thus only the administrator is guaranteed the access. The purpose of the project is to build an application program to reduce the manual work for managing the Customer, Bill, Bill Receipt, Connection. It tracks all the details about the Connection, Electricity, Payment. Functionalities provided by Electricity Billing System are as follows:  Provides the searching facilities based on various factors. Such as Customer, Connection, Electricity, Payment  Electricity Billing System also manage the Bill Receipt details online for Electricity details, Payment details, Customer.  It tracks all the information of Bill, Bill Receipt, Electricity etc  Manage the information of Bill  Shows the information and description of the Customer, Connection  To increase efficiency of managing the Customer, Bill  It deals with monitoring the information and transactions of Electricity.  Manage the information of Customer  Editing, adding and updating of Records is improved which results in proper resource management of Customer data.  Manage the information of Electricity  Integration of all records of Payment.

Scope of the project Electricity Billing System

It may help collecting perfect management in details. In a very short time, the collection will be obvious, simple and sensible. It will help a person to know the management of passed year perfectly and vividly. It also helps in current all works relative to Electricity Billing System. It will be also reduced the cost of collecting the management & collection procedure will go on smoothly. Our project aims at Business process automation, i.e. we have tried to computerize various processes of Electricity Billing System.  In computer system the person has to fill the various forms & number of copies of the forms can be easily generated at a time.  In computer system, it is not necessary to create the manifest but we can directly print it, which saves our time.  To assist the staff in capturing the effort spent on their respective working areas.  To utilize resources in an efficient manner by increasing their productivity through automation.  The system generates types of information that can be used for various purposes.  It satisfy the user requirement  Be easy to understand by the user and operator  Be easy to operate  Have a good user interface  Be expandable  Delivered on schedule within the budget.

Input Data and Validation of Project on Electricity Billing System

 All the fields such as Customer, Connection, Payment are validated and does not take invalid values  Each form for Customer, Bill, Bill Receipt can not accept blank value fields  Avoiding errors in data  Controlling amount of input  Integration of all the modules/forms in the system.  Preparation of the test cases.  Preparation of the possible test data with all the validation checks.  Actual testing done manually.  Recording of all the reproduced errors.  Modifications done for the errors found during testing.  Prepared the test result scripts after rectification of the errors.  Functionality of the entire module/forms.  Validations for user input.  Checking of the Coding standards to be maintained during coding.  Testing the module with all the possible test data.  Testing of the functionality involving all type of calculations etc.  Commenting standard in the source files. The software quality plan we will use the following SQA Strategy:  In the first step, we will select the test factors and rank them. The selected test factors such as reliability, maintainability, portability or etc, will be placed in the matrix according to their ranks.  The second step is for identifying the phases of the development process. The phase should be recorded in the matrix.  The third step is that identifying the business risks of the software deliverables. The risks will be ranked into three ranks such as high, medium and low.

Features of the project Electricity Billing System:

 Product and Component based  Creating & Changing Issues at ease  Query Issue List to any depth  Reporting & Charting in more comprehensive way  User Accounts to control the access and maintain security  Simple Status & Resolutions  Multi-level Priorities & Severities.  Targets & Milestones for guiding the programmers  Attachments & Additional Comments for more information  Robust database back-end  Various level of reports available with a lot of filter criteria’s  It contain better storage capacity.  Accuracy in work.  Easy & fast retrieval of information.  Well designed reports.  Decrease the load of the person involve in existing manual system.  Access of any information individually.  Work becomes very speedy.  Easy to update information

Identification of need:

The old manual system was suffering from a series of drawbacks. Since whole of the system was to be maintained with hands the process of keeping, maintaining and retrieving the information was very tedious and lengthy. The records were never used to be in a systematic order. there used to be lots of difficulties in associating any particular transaction with a particular context. If any information was to be found it was required to go through the different registers, documents there would never exist anything like report generation. There would always be unnecessary consumption of time while entering records and retrieving records. One more problem was that it was very difficult to find errors while entering the records. Once the records were entered it was very difficult to update these records. The reason behind it is that there is lot of information to be maintained and have to be kept in mind while running the business .For this reason we have provided features Present system is partially automated (computerized), actually existing system is quite laborious as one has to enter same information at three different places. Following points should be well considered:  Documents and reports that must be provided by the new system: there can also be few reports, which can help management in decision-making and cost controlling, but since these reports do not get required attention, such kind of reports and information were also identified and given required attention.  Details of the information needed for each document and report.  The required frequency and distribution for each document.  Probable sources of information for each document and report.  With the implementation of computerized system, the task of keeping records in an organized manner will be solved. The greatest of all is the retrieval of information, which will be at the click of the mouse. So the proposed system helps in saving the time in different operations and making information flow easy giving valuable reports.

Feasibility Study:

After doing the project Electricity Billing System, study and analyzing all the existing or required functionalities of the system, the next task is to do the feasibility study for the project. All projects are feasible - given unlimited resources and infinite time. Feasibility study includes consideration of all the possible ways to provide a solution to the given problem. The proposed solution should satisfy all the user requirements and should be flexible enough so that future changes can be easily done based on the future upcoming requirements. A. Economical Feasibility This is a very important aspect to be considered while developing a project. We decided the technology based on minimum possible cost factor.  All hardware and software cost has to be borne by the organization.  Overall we have estimated that the benefits the organization is going to receive from the proposed system will surely overcome the initial costs and the later on running cost for system. B. Technical Feasibility This included the study of function, performance and constraints that may affect the ability to achieve an acceptable system. For this feasibility study, we studied complete functionality to be provided in the system, as described in the System Requirement Specification (SRS), and checked if everything was possible using different type of frontend and backend plaformst. C. Operational Feasibility No doubt the proposed system is fully GUI based that is very user friendly and all inputs to be taken all self-explanatory even to a layman. Besides, a proper training has been conducted to let know the essence of the system to the users so that they feel comfortable with new system. As far our study is concerned the clients are comfortable and happy as the system has cut down their loads and doing.

User Interface Design

User Interface Design is concerned with the dialogue between a user and the computer. It is concerned with everything from starting the system or logging into the system to the eventually presentation of desired inputs and outputs. The overall flow of screens and messages is called a dialogue. The following steps are various guidelines for User Interface Design:

1. The system user should always be aware of what to do next. 2. The screen should be formatted so that various types of information, instructions and messages always appear in the same general display area. 3. Message, instructions or information should be displayed long enough to allow the system user to read them. 4. Use display attributes sparingly. 5. Default values for fields and answers to be entered by the user should be specified. 6. A user should not be allowed to proceed without correcting an error. 7. The system user should never get an operating system message or fatal error.

Preliminary Product Description:

The first step in the system development life cycle is the preliminary investigation to determine the feasibility of the system. The purpose of the preliminary investigation is to evaluate project requests. It is not a design study nor does it include the collection of details to describe the business system in all respect. Rather, it is the collecting of information that helps committee members to evaluate the merits of the project request and make an informed judgment about the feasibility of the proposed project. Analysts working on the preliminary investigation should accomplish the following objectives:  Clarify and understand the project request  Determine the size of the project.  Assess costs and benefits of alternative approaches.  Determine the technical and operational feasibility of alternative approaches.  Report the findings to management, with recommendations outlining the acceptance or rejection of the proposal.  Benefit to Organization The organization will obviously be able to gain benefits such as savings in operating cost, reduction in paperwork, better utilization of human resources and more presentable image increasing goodwill.  The Initial Cost The initial cost of setting up the system will include the cost of hardware software (OS, add-on software, utilities) & labour (setup & maintenance). The same has to bear by the organization.

Project Category

Relational Database Management System (RDBMS) : This is an RDBMS based project which is currently using MySQL for all the transaction statements. MySQL is an opensource RDBMS System. Brief Introduction about RDBSM : A relational database management system (RDBMS) is a database management system (DBMS) that is based on the relational model as invented by E. F. Codd, of IBM's San Jose Research Laboratory. Many popular databases currently in use are based on the relational database model. RDBMSs have become a predominant choice for the storage of information in new databases used for financial records, manufacturing and logistical information, personnel data, and much more since the 1980s. Relational databases have often replaced legacy hierarchical databases and network databases because they are easier to understand and use. However, relational databases have been challenged by object databases, which were introduced in an attempt to address the object-relational impedance mismatch in relational database, and XML databases.

Implementation Methodology:

Model View Controller or MVC as it is popularly called, is a software design pattern for developing web applications. A Model View Controller pattern is made up of the following three parts:  Model - The lowest level of the pattern which is responsible for maintaining data.  View - This is responsible for displaying all or a portion of the data to the user.  Controller - Software Code that controls the interactions between the Model and View. MVC is popular as it isolates the application logic from the user interface layer and supports separation of concerns. Here the Controller receives all requests for the application and then works with the Model to prepare any data needed by the View. The View then uses the data prepared by the Controller to generate a final presentable response. The MVC abstraction can be graphically represented as follows. MVC (Model View Controller Flow) Diagram DATA FLOW DIAGRAMS

o Duration  Resource Allocation o Hardware o Software o Previous relevant project information o Digital Library  Risk Management o Risk avoidance o Risk detection

Project Scheduling: An elementary Gantt chart or Timeline chart for the development plan is given below. The plan explains the tasks versus the time (in weeks) they will take to complete. January February March Requirement Gathering Analysis Design Coding Testing Implement W1 W2 W3 W4 W1 W2 W3 W4 W1 W2 W3 W W i‘ s are weeks of the months, for i =1, 2, 3, 4