Telephone Biller
Telephone Biller
Telephone Biller
on
Telephone bill
ACKNOWLEDGEMENT
This Project is developed in year 2010 to consider the requirement of Telephone
Bill
I thankful to Teaching and Non-Teaching Staff and College who have helped and
Guided me in preparing this project.
I am also thankful to my colleagues to help me to developing this project.
And to all my friends and my guided who has helped me in such a way to finish this
project.
I am also thankful to Wikipedia encyclopedia the internet online library to guide
me to develop the project report.
Yours Faithfully,
Student Name
Pesavariya Seema
Mehta Archana
ABSTRACT
Telephone Bill
AIM OF PROJECT
Project making is a one subject of BCA. The student gets a chance to have
practical knowledge of the software exposure as to gain control over programming
languages. The objective of practical training of BCA levels is to develop among the
students a feeling of software making in order to develop a practical bias in them as
supplement to the theoretical study of the computer application in general.
Such project making plays a dominant role in developing practical view points,
experience and also make them aware about the role situation of the software application.
This project is prepared under my knowledge, guidance given by our professors and
especially Thanks to concerned person, who has helped us to get knowledge on the
project.
PROJECT CATEGORY
This project is a windows bases project.
PROJECT DESCRIPTION
The objective of this project is to maintain the details of Telephone Bill the main
objective of the project is to improve the Administrator efficiency facilitating it to
promptly address any kind of information sought for and to minimize the workload.
Hence this software is used to maintain working detail in the Telephone Bill thus
the user get better response with it.
Hence this software is used to providing good service to the registered
Authorities, thus an unauthorized person cannot access it.
Index
1.
2.
Introduction
Project Summary
Purpose
Scope
3.
4.
5.
6.
7.
Project Planning
System Analysis
Feasibility Study
System Design
Data Dictionary
Implementation and Planning Details
Coding Standards
Testing
Testing Methods
Testing Cases
8.
9.
User Manual
Limitation & Future Enhancement
10.
11.
Screenshot
Limitation
Future Enhancement
Conclusion
References
INTRODUCTION
PROJECT SUMMARY
The Project Telephone Bill is dedicated to the requirement of the Jamnagar.
Telephone Bill Works on the,Telephone Bill, The objective of this project is to maintain
the details of
users needs & what exactly is desired from the software, and what constraints on the
solution are.
TECHNOLOGY USED
1. TC
2. Wikipedia encyclopedia
PROJECT MANAGEMENT
The manager who forgets that software engineering work is an intensely human endeavor
will never have success in project management.
A manager who fails to encourage comprehensive customer communication early in the
evaluation of a project risks building an elegant solution for the wrong problem.
Finally, the manager who pays little attention to the process runs the risks of inserting
competent technical methods & tools into a vacuum.
Project Management has two parts like:
1) Project Planning & Scheduling
2) Risk Management
PROJECT PLANING AND SCHEDULING
The software project management process begins with a set of activities that are
collectively called Project Planning.
The first of this activities is Estimation.. whenever estimates are made, we look into
the future and accept some degree of uncertainty as a matter of course. although
estimating is as much art as it is science, this important activity need not be conducted in
a random manner. Useful techniques for time & effort estimation do exist. And because
estimation lays a foundation for all other project planning activates, and project planning
provides the road map or successful software engineering.
-
RISK MANAGEMENT
Although there has been considerable debate about the proper definition for
software risk,There is general agreement that risk always involves two characteristics
Uncertainty: - The events that characterize the risk may or may not happen.
SYSTEM REQUIREMENT
It Studies the current business system to find out how it works and where improvement
should be made? This study consider both manual and computer methods.
A requirement is a feature that must be included in a new system it may include a way of
capturing or processing data, producing information, controlling a business activities or
supporting management.
CHARACTERISTIC OF SOFTWARE
1) Predetermine objectives
2) Set of Components
3) Set of Process
4) Inter related and Interdependence
5) Sub System
6) Integration
SOFTWARE REQUIREMENTS
Windows 2000/Xp
TC
HARDWARE REQUIREMENTS
Pentium III or Advanced Processor
256 MB RAM
80 GB Hard disk or onwards
Monitor 1366 * 768 resolutions
SYSTEM ANALYSIS
STUDY OF CURRENT SYSTEM.
This is implemented system is total file base system and it is very time consuming
to execute the process of Telephone Bill. it is not more efficient and effective to
implementing in real world.
PROBLEM AND WEAKNESS OF CURRENT SYSTEM
This system require the more man power . so that it consume or man power and
money . it is very slow to work with this systems
A systems analyst is responsible for researching, planning, coordinating and
recommending software and system choices to meet an organization's business
requirements.
Systems analysts may act as liaisons between vendors and the organization they
represent. They may be responsible for developing cost analyses, design considerations,
and implementation time-lines. They may also be responsible for feasibility studies of a
computer system before making recommendations to senior management.
Basically a systems analyst performs the following tasks:
I.
II.
III.
IV.
Perform system testing with sample/live data with the help of testers
V.
Requirements analysis is the first stage in the systems engineering process and software
development process.
FEASIBILITY STUDY
A feasibility study is a preliminary study undertaken to determine and document a
project's viability or the discipline of planning, organizing, and managing resources to
bring about the successful completion of specific project goals and objectives. The term
is also used to describe the preliminary analysis of an existing system to see if it is worth
upgrading all or a part. Also known as feasibility analysis The term is also used to refer to
the resulting document. The results of this study are used to make a decision whether or
not to proceed with the project. If it indeed leads to a project being approved, it will
before the real work of the proposed project starts and be used to ascertain the likelihood
of the project's success. It is an analysis of possible alternative solutions to a problem and
a recommendation on the best alternative. It can decide, for example, whether order
processing can be carried out by a new system more efficiently than the previous one.
If a project is seen to be feasible from the results of the study, the next logical step is to
proceed with it. The research and information uncovered in the feasibility study will
support the detailed planning and reduce the research time.
Feasibility is the determination of whether or not a project is worth doing. The
process followed in making this determination is called a feasibility study. This type of
study determines if a project can and should be taken. Once it has been determine that
project is feasible, the analyst can go ahead and prepare a project specification, which
finalizes project requirements.
In the conduct of the feasibility study, we usually consider seven distinct, but inter-related
types of feasibility. They are:
1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility
4. Technical Feasibility
The Technical needs of the system are as follows:
Facility to communicate data to distant location. Response time under certain conditions.
Ability to process a certain volume of transaction at a particular speed. In examining the
technical feasibility, configuration is given more importance than actual make of
hardware. Here the configuration gives the complete picture about the systems
requirements:
-How many workstations are required?
-How these workstations are interconnected so that they can operate and communicate
smoothly?
What speeds of Input and Output should be achieved.
As the above requirements of the system can be fulfilled easily with the technology
available in the market, therefore the proposed system is technically feasible.
Economical Feasibility
Economic analysis is the most frequently used technique for evaluating the effectiveness
of a proposed system. More commonly known as Cost / Benefit analysis the procedure is
to determine the benefits and savings that are expected from a proposed system and
compare them with the costs. If benefits outweigh costs, a decision is taken to design and
implement the system. Otherwise, further justification or alternative in the proposed
system will have to be made if it is to have a chance of being approved.
Proposed system for Telephone Bill Centre is economically feasible in terms of time and
effort of staff and management. Cost will be incurred at the beginning but the effort and
time saved by the proposed system far outweighs the cost incurred. Since the company is
not already computerized, so initially large amount will be involved but in due course
with the outcome of the system, the cost will be outweighed by the result of the
automated system.
Operational Feasibility
It is mainly related to human company and political aspects. The points to be considered
are:
-What changes will be brought with the system?
-What company structures are distributed?
-What new skills will be required?
Project is not rejected simply because of operational infeasibility but such consideration
is likely to critically affect the nature and scope of the eventual recommendations.
For Telephone Bill apart from other facts as per operational feasibility is concerned we
need to see to it that the system to be developed should be user-friendly so that staff and
other personnels who are not computer literate find it easy to work with. As the office
staff does most of the work, so they might have to be trained.
SYSTEM DESIGN
DATAFLOW DIAGRAM
Authentication module
Administrator Module
Client module
other modules
CODING STANDARD
Access Control:
Accesses Control can be defined as control established to ensure that only administrator
are accessed data with the proper authority. Different types of access control, which are
used in this software, are as follows:
Physical Access:
The best form of access control is the physical access control. Only authorized personal
should be allowed to do specific tasks like booting of the machine, mounting disks,
distributing reports etc.
In this software the database is centralized means all the data is stored at one
place called as server where as number of section (workstation) are attached to it.
Without the server nothing can be done. So, for starting server an authorized person
should be there.
Validations:
Validations of data entered on various input screens are not a security for the system but a
control to ensure that clean data goes into the system. If data is not validated on input,
you will end up with a lot of inconsistent data.
In computer parlance, this is referred to as Garbage In, Garbage Out. If proper
validation is not done, user tends to lose confidence in the system and it eventually boils
down to a new project of clearing up the data. Typical validations done on input screen
are as follows:
Combo input System
Length of data.
Type of data (numeric, integers, alphabetic, alphanumeric)
Discreet values
Cross validation of data across various fields
Data Integrity:
We can have the best of validations in a system but invalid data can always get into the
system due to some recent changes done on the software, which was not tested
comprehensively, or due to corruption. Whatever the cause, it is a very good control
practice to periodically check the integrity of the data on the system. Data Integrity could
be verified by a number of techniques. Some of the used techniques are listed below:
Tallying number of records across various tables in the database.
Tallying critical fields across tables in the database.
Whatever be the technique, periodic validation of data will give us early warning signals
in case something is wrong with database.
security features:
In the Telephone Bill we have set the best security Features to operate the application,
When user logged into the software Application ask for the username & password which
are stored into a database & it will check both username & password condition, If user do
any mistake to entering the username & Password then application will count the wrong
username & password which is entered by user when user logged into application it will
display to the user that how many times the wrong username & password are entered this
system called Hack Detector.
Hack detector not only checking the condition of the username & Password it will
count how many times wrong password binged entered to the application to hack this
application. In every type of threats this application are securable any threats or viruses
cannot delete any important data of this application.
The other new facility is that we also can add new administrator password instead
of change the password the benefit of this feature is that the possibility of hacking is very
less because no one can change the current password we must add new password and the
new user & Password will add by whom who know the administrator secrete Password
only here is a two passwords are sated.
First one the user name & password when u logged into the software and the other
one is that Administrator password to add a new user account which is secrete and only
know by the administrator. If u want to add new user and if u dont know the
administrator password which is a master password u must called the administrator to add
a new account in the application.
In such a way this application is very secure. I have done my try best to developed a
secure application.
If user entered wrong Log in Password then following message box will
displayed: Then if user Entered a Correct Username & password Following will be
shown :
Same in the master password verification if user entered wrong password it will
shown error message& when user entered correct password it will display how many
times other user entered wrong password.
If user entered wrong Username & Password :
Then if user entered a correct Username & Password then :
User can access all the control of administrator like Add, Update, Delete, Edit,
All the menu can accessible by the user.
TESTING
Testing plan
Testing Strategies
Testing Method
Test cases
TESTING METHOD
Software testing methods are traditionally divided into black box testing and
white box testing. These two approaches are used to describe the point of view that a test
engineer takes when designing test cases.
Black Box Testing
Black box testing treats the software as a black box without any knowledge of internal
implementation. Black box testing methods include equivalence partitioning, boundary
value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix,
exploratory testing and specification-based testing.
Specification-based testing
Specification-based testing aims to test the functionality according to the
requirements. Thus, the tester inputs data and only sees the output from the test object.
This level of testing usually requires thorough test cases to be provided to the tester who
then can simply verify that for a given input, the output value (or behavior), is the same
as the expected value specified in the test case. Specification-based testing is necessary
but insufficient to guard against certain risks.
Try different inputs and see if we get the correct output:
Input 1
Input N
Output
Black Box
White Box
Guarantee that all independent paths within a module have been exercised at least once.
Exercise all logical decisions on their true and false sides.
Execute all loops at their boundaries and within their operational bounds.
Exercise internal data structures to ensure their validity.
Unit Testing
Unit testing, also called module or component testing is testing individual software units
independently of the other units in the same system. The programmer does this testing.
Unit testing is recognized as one of the most efficient ways to reduce the density and
proliferation of errors in a software application. Unit testing has been done for each
ITEM of the system. We have followed the following procedure to perform unit testing:
TEST CASES
If user Id and password will be correct then a massage as Welcome to the
Telephone Bill will be displayed in the massage box. All the modules are connected
properly with main menu. This can be displayed on the status bar. Where the entire
module can be shown .Implementing the test plan in the software with data.:There are two methods are used for implementing the test plan.
Testing with the dummy data: - Testing in this way means testing with data which not
original or it is dummy. With this method accuracy of the system can be judged according
to some extents. If the system is running correctly with this data then it can be inferred
that software has been tested successfully.
Testing with Live data: - Testing with live data means testing with original data. This
means that system is tested with data taken from the actual user. This is very accurate as
compared to dummy data. If the system is running correctly with this data then it can be
inferred that software tested successfully.
Customer Section
Edit
Delete
Deleted values
Billing Section
Delete
View
Delete
Billing Details
and visual basic it means that if proposed Screen increases his users it just has to add
more machines and can install client software to new machine to provide Enquiry on one
machine, Registration on other and so on.
Security: - Data is secure. Only the administrators can do backup and restoring
of data type of job by giving login name and password. To operate the program also
administrator has to enter password.
Large Database Supports: - Using oracle as RDBMS means large number of
records can be managed without facing any problem.
BIBLIOGRAPHY
The Bibliography contains references to all the documents that were used to develop the
software.
Books
Programming with ANSI C++
C++ complete reference
Balaguruswami C++
Websites
www.WikiPedia.com
www.google.com