Telephone Billing System

Final Project Report Submitted to Rajiv Gandhi Prodhyogiki Vishwavidhyalaya, Bhopal Towards partial fulfillment for the Degree of Bachelor of Engineering in Computer Science 2010-2011 GUIDED BY: SUBMITTED BY:
Mr. Neeraj paliwal khare(0853cs071008) Pranjali Pateriya(0853cs071035) Aparna

Department of Computer Science & Engineering Oriental Institute Of Science And Technology, Indore

Rajiv Gandhi Prodhyogiki Vishvavidhyalaya, Bhopal

TABLE OF CONTENTS

1. Abstract 2. Objective Of the Project 3. Requirements 4. Technical details of the project 5. planning 6. Design 7. Testing 8. Conclusion

Abstract

Our purpose is to facilitate the telephone office with a telephone billing system software which will help to contain the whole information regarding the customer under a single web site. We are providing system application, by using which the administrator will be able to easily manage and control the data. This software is a telephone billing system regarding telephone office, all the managing information of customer and facilities are provided in it. It is a system application, in which operator and administrator will be able to manage the data. Customer will only have privilege to retrieve or check the data, they will not be able to modify or change the data without having authority.

Objective
To facilitate the telephone office with a telephone billing system software which will help to contain the whole information regarding the customer under a single web site. We are providing system application, by using which the administrator will be able to easily manage and control the data.

Requirements

SOFTWARE REQUIREMENT:The Software Requirement Specification is one of the critical documents since it identifies the aims and goals of the project. This is important to the success of the project since it clearly outlines what the development team must achieve in order to classify the project to be complete. A strict definition of this type also enables the project team to outline the necessary means to achieve these goals. If this step is not carried out correctly the project can encounter delays caused by changes to the requirements brought about by developers and customers, thus altering the project schedule.

To implement this project following software are necessary. Java Server Page HTML Editor MS ACCESS Local server Tomcat.

Functional Requirements (Product Functions)For USERRegistration, Login, Forget Password, View Profile, Update Profile, Add Education Qualification, Change

Password, Log out, Delete Account, Submit/Update Account.

For AdministratorLogin, Change Password, update,Block/Unblock/Delete USER Accounts, and Log out. Operating Environment Server Side- Operating system (Microsoft Windows XP) -Server Apache Tomcat engine(5.5.1) -JDK 1.5, SDK1.3(J2EE) -DataBase Management System Oracle 9i

Client Side- Browser- Internet Explorer 6 or any browser

Design and Implementation Constraints Language Requirements - HTML (Hyper Text Markup Language)

- J2EE1.3(JAVA 2 Enterprise Edition) -J2SE1.5(JAVA 2 Standard Edition) - SQL (Structured Query Language) - Java Script

Development Requirements - Microsoft Front Page 2000(HTML pages) - JDK1.5 (Java Development Kit) - Net Beans IDE5.5 (Integrated Development Envioronment) - DBMS (Database Management System)

Communication ProtocolHTTP (Hyper Text Transfer Protocol) stateless protocol based on client server connection 3.1 Hardware RequirementsOperating EnvironmentServer Sidearchitecture and TCP/IP

Memory- 256 MB of RAM, 20 GB hard disk Processor - Intel/AMD or any equivalent processor supporting Microsoft Windows XP.

Design and Implementation Constraints Memory 256 MB of RAM, 20 GB hard disk Processor - Intel/AMD or any equivalent processor supporting Microsoft Windows XP.

3.1.3 Hardware InterfacesNIC (Network Interface Card), LAN cables, hubs, switches or routers for maintaining computer network as per requirement.

Technologies

- HTML (Hyper Text Markup Language) - J2EE (Java Platform, Enterprises Edition) 1. Servlet 2. JSP 3. Java Beans

4. Java mail - RDBS (Relational Database Management System) Oracle 10g - SQL (Structured Query Language for RDBMS)

Planning
-

We decide to make different module (functions) to solve particular problem due to this the main goal of project would be easily achieved.

- We want to add some additional feature rather than previous website. - We decice the user friendly processes.

Design

Overall Description
Use-Case Model Survey Architecture Diagram And Database Design

Use-Case Model Survey

Identification Entities

1. Administrator: It is the name of main authority of the system that can control overall system. 2. Operator: Operator is operating the system, maintain records and give the information about services to customers. 3. Customer: Customer is the user who uses service of the system. 4. Registration Form: It is a form which is filled by new customer for taking connection of service. 5. Bill: Bill is giving the whole information about using service which contain amount of calls and other services.

Identification task
1. Registration:It can be done by administrator and perform by new customers. 2. Pay Bill:Paying bill by customer who is using service. 3. Dialing:Dialing is done by the customer when they have wanted to communicate to another person or customer. 4. Complain:Doing complain by customer if he has any problem in service. 5. Information:To give any type of information to the customer is given by operator. 6. Maintain Records:-

This task is done by operator to maintain all records of the customer.

SOFTWARE PROCESS MODEL

The application of systematic, disciplined, quantifiable approach applied of to the development, that is, the operation application and of maintenance software;

engineering to software along with the study of approaches involved in the same is called Software Engineering. Software engineering is a layered approach towards software development. The foundation for the software engineering is the process layer. The process layer holds the entire software paradigm and all the other methods that hold the software together. To solve the various problems involved and identified with an associated software development process, various models have often referred to as software engineering paradigm .

- How to Choose a Software Engineering Paradigm:

The process model for the software engineering is chosen based upon the nature of the project and

application, the method and tools to be used and the control and the deliverable that are required. In analysis phase of our project we analyze that the Waterfall Model will suitable to develop our project.

Incremental Model:

Conclusion

So, our points of conclusion will give us the proper knowledge of our project. Main points are following as: Our project is the kind of Internet world, so it will help to launch our view and make international connection. Mostly customer wants all facility at one place and very fast. Thats why we try to provide all customers needed facility. It needs 2 or more computers. It also needs internet connections.