IUBAT - International University of Business Agriculture and Technology

REPORT ON:

“Client billing system for ISP(true communication)”

Submitted By:

Group Name: Authentic

Group Member List:

Name ID Program
Mst Jannatul Ara Sumi 13103030 BCSE

Submitted To:

Md. Saidur Rahman

Instructor of Computer Science and

Engineering-IUBAT

Course no: CSC 387

Course name: System Analysis & Design
Dept. of computer science and Engineering
Date of Submission: 07-08-2014

Letter of Transmittal

April 07, 2015

Md. Saidur Rahman

0
Supervisor, CSC387

College of Engineering and Technology (CEAT)

Department of Computer Science & Engineering.

IUBAT- International University of Business Agriculture & Technology

4Embankment Drive Road, Sector-10, Uttara Model Town, Dhaka-1230, Bangladesh.

Subject: Submitting a report on “Client billing system for ISP(true communication”.

Dear Sir,

I have selected Client billing system for ISP(true communication my project of System Analysis
& Design course (CSC 387). I pleased to propose a plan to you for my project. By this project I
can show my efficiency of technical work effectively.

For your kind consideration I inform you that I am trying my best to prepare the project for an
effective web design for a ISP FIRM. I have immense pleasure to have the study on this which is
effective in our practical field as well as our study sector. We also mention there is lacking in
information and some sleep of tongue due to limit of knowledge and time.

After having some problem I have given best effort to the report and I hope you will appreciate
the project report and oblige thereby.

Sincerely

…………………………

Mst Jannatul Ara

ID# 13103030

On behalf of group- Authentic

Abstract

1
This project is the Client billing system for ISP(true communication) . This project is mainly for a ISP
company who manage their work with pen and paper base, and we computerize their all work
system by our software .This project provide them support their day to day work. They can able
to keep a record of their client where will be all detail information about their client, details
about internet packages and its creates in-voice. In-voice calculations are done automatically.
They can update, delete all the information about their client. Once a admin login the system and
resister the client from that time he will be able to conduct this software. This project help the
admin a better interface that make his work easy and comfortable. And this project will be save
his time. Administrative part will control the login part. After that admin can control or monitor
the rest of the system.

2
 Acknowledgement

In the name of ALLAH who is the most merciful and the most graceful.

First of all I sincerely like to thank Md.siddiqulla (Director of True comminication), giving
me the opportunity to complete our project at True communication. We would like to pay my
gratitude to Md.siddiqulla for his support and encouragement during our project period.

We would like to pay my gratitude to my faculty advisor MD. Saidur Rahman, faculty of
Computer Science & Engineering Department, who has given me the opportunity to make such
a report for not only in this semester but also throughout my education life at True
communication by giving his valuable suggestions and advices at any time, at any situation. We
would able to make this report effectively and properly only for his right direction. Beside that it
is also our pleasure to thank again Saidur Rahman to give me an opportunity to submit this
report. For his continuous encouragement and contribution gave our self the grit and
determination needed to able to finish our project and finish it well.

3
 Student Declaration

We are the students of BCSE-Bachelor of Computer Science and Engineering program, under
the College of Engineering and Technology (CEAT), at the IUBAT-International University of
Business Agriculture and Technology and declaring that, this report on the topic of “Client
billing system for ISP(true communication” has only been prepared for the fulfillment of the
course of CSC-387 (System Analysis and Design).

This report is not prepared for any other purposes.

Thanking you.

Student name with ID and Signature:

--------------------------

Mst.Jannatul Ara

ID: 13103030

Letter of authorization

4
Dated 12h August, 2015

Seyda Sadia Islam

ID# 13103043

On behalf of group- Authentic

Program: MSc in CSE

Dear Group Authentic.

I hereby authorize you to develop “Client Billing System” to fulfill the requirement of the project of course

CSE 387 to complete the Degree of Bachelors in Computer Science and Engineering.

I wish you complete this project successfully as the part of completion of the degree of Bachelors in Computer
Science and Engineering.

Md Saidur Rahman

Department of Computer Science & Engineering

Iubat University Business Agriculture & Technology

4,Embarkment drive Road,Sector 10,Uttara. Dhaka-1230

5
 Content Page
1. Introduction Page

1.1. Introduction of Project…………………………………………………10

1.2. Aim of Project………………………………………………………….10

1.3. System Study & Analysis………………………………………………11

1.3.1 System Analysis……………………………………………….11

2. Existing System

2.1. Existing Manual System………………………………………………12

2.2. Process of Existing System……………………………………………12

2.3. Problems with Existing System……………………………………….12

3. Proposed System

3.1. Aim of Proposed System……………………………………………..13

3.1.1. Advantage of the Proposed System………………………..13

3.2. System Feasibility Study…………………………………………….14

4. Proposed System Design

4.1. Introduction of Proposed System…………………………………..16

4.1.1. Logical Design……………………………………………17

4.1.2. Physical Design…………………………………………..17

6
 4.1.3. Design / Specification Activities……………………………17

5. Implementation of Model

5.1. Analysis Modeling & Design Methodologies…………………………18

5.1.1. Database Design……………………………………………..18

5.1.2. Entity Relationship Model…………………………………..19

5.1.3. Identifying Entities…………………………………………..19

5.1.4. Entity Relationship Diagram (Introduction)…………………19

5.1.5. Relationship Cardinality……………………………………..20

5.1.6. Entity Relationship Diagram (Diagram)……………………..22

5.1.7. Database Table Structure……………………………………23

5.2. System Description…………………………………………………….25

5.2.1. Data Flow Diagram (Introduction)…………………………..25

5.2.2. Symbol of DFD……………………………………………….27

5.2.3. DFD of Project………………………………………………..27

5.2.4. Effort Distribution....................................................................31

5.2.5. Task Distribution………………………………………………32

5.2.6. Time Chart for Activities………………………………………33

5.2.7. System Specification…………………………………………..35

5.2.8. Project Cost Estimation…………………………………………35

5.2.8.1. Hardware Costs……………………………………….35

7
 5.2.8.2. Software Costs………………………………………...37

5.2.8.3. Other Costs……………………………………………..38

5.2.9. Cost Benefit Analysis…………………………………………….38

5.3. System Testing………………………………………………………………38

5.3.1. System Testing Introduction……………………………………..39

5.3.2. Test Plan…………………………………………………………..40

6. System Requirements & Using Guideline

6.1. System Requirements …………………………………………………….41

6.1.1. Hardware Requirements…………………………………………..41

6.1.2. Software Requirements……………………………………………41

6.1.3. Using Guideline……………………………………………………..42

6.1.4. Screen Shoot………………………………………………………..43

7. Conclusion & Upcoming Feathers

7.1. Conclusion……………………………………………………………………47

7.2. Upcoming Feathers…………………………………………………………..47

-Bibliography………………………………………………………………………48

8
--Project--

9
Introduction:
1.1. Introduction of Client Billing System:
True Communication Company is the one of the ISP FIRM in Bangladesh. To form a team of
CSE students of ISP FIRM in order to perform different educational and social works. It has
some specific goals.True Communication ISP has increased service package ,facility and the
number of clients in each year but existing manual based system does not provide the efficient
service to handle the client’s record, cannot maintain the supports with their clients, can not
generate bill and faces lots of problems to handle the clients information, collect the bill, handle
the types of complains, their solution, cannot proper handle the reporting part and payment
system. So the initiative has been taken in order to design and develop new computerized system
to maintain and distribute the information to other modules with efficiently. In the term of
development of this project, we are the students of Computer Science and Engineering trying to
develop this Desktop base client billing system for True Communication. Here, We make
contract with the System administer for collecting the project requirement information, We
identified the problems of current manual system through the analysis. We discovered a new
system depends on existing manual system features including with clients billing system reduce
the complexity of the current manual system.The flow of the information will be fully
maintained by the system admin and the authorized person internally after entering the data. That
information will be extensively protected and back up in system. As True Communication will
use this system that’s why there is no possibility to be hacked from internet. Thus We
recommend developing this system as soon as possible with all the functionality.

1.2 Aim of projects:

 To become premier Internet Service Provider by developing state-of-the-art
technology to build a connected Bangladesh
 Achieve customer satisfaction by providing round the clock reliable quality service.
 Try developing good communication and understanding between the clients of True
Communication
 Learn how to provide real community service.

10
1.3. System study and Analysis:
System analysis is a process of gathering and interpreting facts , diagnosing problems and
information to recommend improvement on the system. It is a problem solving activity that
requires intensive communication between the system users and system developers .The mission
of the System study and Analysis is to conduct studies and analyses of an operational and
technological nature, and to promote the exchange and development of methods and tools for
operational analysis as applied to defense problems. The Panel will conduct studies, analysis and
information exchange activities that explore how operational capability can be provided and
enhanced through the exploitation of new technologies, new forms of organization or new
concepts of operation.

1.3.1.System Study:
System analysis or study is an important phase of any system development process. As it is
desktop based client billing system so, after collecting all the required information those
are necessary for design and development. For designing clients billing system form we
have collected previous hard copy of clients list and their billing list form company
administrator. A detailed study of the process must be made by various techniques like
interviews questionnaires etc. The data collected by these sources must be scrutinized to arrive to
a conclusion .The conclusion is understanding of how the system functions. This system is called
the existing system. Now the existing system is subjected to close study and problem areas are
identified. The designer now functions as a problem solver and tries to sort out the difficulties
that the enterprise faces. The solutions are given as proposals . The proposal is then weighted
with the with the existing system analytically and the best one is selected. The proposal is
presented to the user for an endorsement by the user. The proposal is reviewed on user request
and suitable changes are made. This is loop that as soon as the user is satisfied with proposal
.Preliminary study is the process of gathering and interpreting facts, using the information for
further studies on the system. Preliminary study is problem solving activity that requires
intensive communication between the system users and system developers .It does various
feasibility studies. In this studies a rough figure of the system activities can be obtained ,from
which the decisions about the strategies to be followed foe effective system study and analysis
can be taken.

11
Existing System and Proposed System
2.1. Existing Manual System:
True Communication of ISP FIRM did not have any computerized based clients billing system
for distributing, creating and managing the client bill. They would maintain each and every as a
traditionally that’s meant every things was controlled manually for example: they are using the
file folder and different type of bookshelf to store information. They used to write down each
everything manually. To be creating the bill for client of True Communication would have to fill
a manual form. That time we can tells about the complains. After analyzing the existing manual
system we obtain following information.

a. Clients all information form-paper copy.

b. Create bill through manually.

2.2. Process of Existing System:

 Bill generate with manually
 Payment method count manually
 Time costly to collect information from different branches

2.3. Problems with Existing System:

Analyzing the existing system we find out the following problem.

 It is a manual and traditional system. It’s not technological system.

 Lack of security of data.

 Time consuming.

 Needs manual calculation.

 Not user friendly.

 Do not manage properly all the information of the client bill.

12
  Either no reports generating in a current system or they are generated with great
difficulty reports take time to generate in the current system.

 Existing system requires lot of paper work.

 Client of the true communication for ISP do not get the information properly.

 Clients cannot participate as frequently.

 Possibility to lost of information.

Proposed System
3.1. Aim of Proposed System:
The aim of proposed system is to develop a system of improved facilities. The proposed system
can overcome all the limitations of the existing system. The system provides proper security and
reduces the manual work.

3.1.1. Advantage of the Proposed System:

 Handle all the clients’ information and create invoice properly.

 Security of data.
 Reduce manual data entry.
 To get the bill records of the clients easily.
 Available functionality for performing various tasks.
 Easy to provide clients bill information.
 Minimum time consumption.
 The proposed system is user friendly because the retrieval and storing of data is fast
and data is maintained efficiently.
 Reports can be easily generated in a proposed system.

13
3.2. System Feasibility Study:
FEASIBILITY STUDY

Feasibility study is made to see if the project on completion will serve the purpose of the
organization for the amount of work, effort and the time that spend on it. Feasibility study lets
the developer foresee the future of the project and the usefulness. A feasibility study of a system
proposal is according to its workability, which is the impact on the organization, ability to meet
their user needs and effective use of resources. Thus when a new application is proposed it
normally goes through a feasibility study before it is approved for development.

The document provide the feasibility of the project that is being designed and lists various areas
that were considered very carefully during the feasibility study of this project such as Technical,
Economic and Operational feasibilities. The following are its features:

TECHNICAL FEASIBILITY:

The system must be evaluated from the technical point of view first. The assessment of this
feasibility must be based on an outline design of the system requirement in the terms of input,
output, programs and procedures. Having identified an outline system, the investigation must go
on to suggest the type of equipment, required method developing the system, of running the
system once it has been designed.

Technical issues raised during the investigation are:

 Does the existing technology sufficient for the suggested one?

 Can the system expand if developed?

The project should be developed such that the necessary functions and performance are achieved
within the constraints. The project is developed within latest technology. Through the technology
may become obsolete after some period of time, due to the fact that never version of same
software supports older versions, the system may still be used. So there are minimal constraints
involved with this project. The system has been developed using PHP the project is technically
feasible for development.
To develop our project, we need a higher level programming language like PHP. And for
database purpose we need programming compatible database such as My SQL and for reporting

14
purpose we use Data report. To use this system we need a computer with simple configuration.
All the technology which is mention above is ready to use. So my project is technically feasible.

ECONOMIC FEASIBILITY
The developing system must be justified by cost and benefit. So if we develop the system by
investing our resource including time, money and intellectuality then, the effort of Manager and
their staffs will be reduced and accurate. It will also less time consuming. Thus we can call
intangible benefit. Also True Communication FIRM can drive their system with less man power
which will save money of the organization. This is our expected outcome of this system and as it
is possible, it is economically feasible.
Criteria to ensure that effort is concentrated on project, which will give best, return at the
earliest. One of the factors, which affect the development of a new system, is the cost it would
require.

The following are some of the important financial questions asked during preliminary
investigation:

 The costs conduct a full system investigation.

 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.

Since the system is developed as part of project work, there is no manual cost to spend for the
proposed system. Also all the resources are already available, it give an indication of the system
is economically possible for development.

Operational feasibility:
As we are using high level programming language, there are lots of possibilities to make our
system user friendly by using textbox, buttons and so on. Also level programming language has
self-validation process which can make it easier for our user and user can use it easily. As it is
user friendly, user will accept the system and system is operationally feasible.

So operational feasibility addresses concerns about user acceptance, management support, and
the requirements of entities and factors in the organizations external environment. The proposed
system will be desirable within the existing way of tour package management. It will become

15
very easy for the tour operator to operate the system. This system will boost up the performance
of the web site.

BEHAVIORAL FEASIBILITY

This includes the following questions:

 Is there sufficient support for the users?

 Will the proposed system cause harm?

The project would be beneficial because it satisfies the objectives when developed and installed.
All behavioral aspects are considered carefully and conclude that the project is behaviorally
feasible.

Proposed System Design

4.1. Introduction of Proposed System:
Design is the first step into the development phase for any engineered product or system. Design
is a creative process . A good design is the key to effective system. The term “design” is defined
as “the process of applying various techniques and principles for the purpose of defining a
process or a system in sufficient detail to permit its physical realization”. It may be define as a
process of applying various techniques and principles for the purpose of defining a device, a
process or a system in sufficient detail to permit its physical realization. Software design sits at
the technical kernel of the software engineering process and is applied regardless of the
development paradigm that is used. The system design develops the architectural detail required

16
to build a system or product. As in the case of any systematic approach this software too
undergone to best possible design phase fine tuning all efficiency ,performance and accuracy
levels. System design go through two phases of development: logical and physical design.

4.1.1. Logical Design:

The logical flow of a system and define the boundaries of a system . It includes the
following steps:

 Reviews the current physical system- it’s data flows ,file content, volume
frequencies etc.
 Prepares output specifications- that is determines the format, content, and
frequency of reports.
 Prepares output specifications-format, content and most of the input functions .
 Prepares edit ,security and control specifications .
 Specifies the implementation plan.
 Prepares a logical design walk through of the information flow, output, input
controls and implementation plan.
 Reviews benefits ,costs, target dates and system constraints.

4.1.2. Physical Design:

Physical system produces the working systems by define the design specifications that
tell the programmers exactly what the candidate system must do. It includes the following
steps-

 Design the following system.

 Specify input and output media.
 Design the database and specify backup procedures.
 Design physical information flow through the system and a physical design walk
through
 Plan system implementation.
 Determine training, procedures, course and timetable.
Device a test and implementation plan and specify any new hardware/software.
 Update benefits , costs, conversion date and system constraints.

4.1.3. Design / Specification Activities:

 Concept formulation
 Problem understanding
 High level requirements proposals

17
  Feasibility study
 Requirements engineering
 Architectural design

Implementation of Model
5.1. Analysis Modeling & Design Methodologies

At a technical level, software engineering begins with a series of modeling tasks that lead to a
complete specification of requirements and a comprehensive design representation for the
software to be built. Analysis modeling uses a combination of text and diagrammatic forms to
depict requirements for data , function and behavior in a way that is relatively easy to understand
and more important, straightforward to review for correctness, completeness and consistency.
The analysis model is the first technical representation of a system.

There are a few analysis modeling methods but two of those models are widely used. They are
structured analysis and object oriented analysis (OOA).The structured analysis model is used in
this project. Because OOA is used when there are many transformation flows, there is a great
chance of data corruption. As there are few transformation flows and many transaction flows in
this system, structured analysis has been chosen.

Design methodology refers to the development of a system or method for a unique situation.
Today, the term is most often applied to technological fields in reference to web design, software
or information systems design.

Components of Design Methodology

The key to design methodology is finding the best solution for each design situation, whether it
be in industrial design, architecture or technology. Design methodology stresses the use of
brainstorming to encourage innovative ideas and collaborative thinking to work through each
proposed idea and arrive at the best solution. Meeting the needs and wants of the end user is the
most critical concern. Design methodology also employs basic research methods, such as
analysis and testing.

5.1.1. Database Design:

Database design is the process of producing a detailed data model of a database. This
logical data model contains all the needed logical and physical design choices and
physical storage parameters needed to generate a design in a data definition language,
which can then be used to create a database.

18
The data base design has two level processes. In the first step ,user requirements are
gathered together and a data base is designed

5.1.2. Entity Relationship Model:

In software engineering, an entity–relationship model (ER model) is a data model for
describing the data or information aspects of a business domain or its process
requirements, in an abstract way that lends itself to ultimately being implemented in
a database such as a relational database. The main components of ER models
are entities (things) and the relationships that can exist among them.

In ER modeling, the structure for a database is portrayed as a diagram, called an entity-

relationship diagram (or ER diagram), that resembles the graphical breakdown of a
sentence into its grammatical parts. Entities are rendered as points, polygons, circles, or
ovals. Relationships are portrayed as lines connecting the points, polygons, circles, or
ovals. Any ER diagram has an equivalent relational table, and any relational table has an
equivalent ER diagram. ER diagramming is an invaluable aid to engineers in the design,
optimization, and debugging of database programs.

In a logical sense, entities are the equivalent of grammatical nouns, such as employees,
departments, products, or networks. An entity can be defined by means of its properties,
called attributes. Relationships are the equivalent of verbs or associations, such as the act
of purchasing, the act of repairing, being a member of a group, or being a supervisor of a
department. A relationship can be defined according to the number of entities associated
with it, known as the degree.

5.1.3. Identifying Entities:

Identifying the Entity according to the conceptual design.

1. System User

2. Client information

3. Invoice

4. Login time

5.1.4. Entity Relationship Diagram

19
An entity relationship diagram (ERD) shows the relationships of entity sets stored in a
database. An entity in this context is a component of data. In other words, ER diagrams
illustrate the logical structure of databases. At first glance an entity relationship diagram
looks very much like a flowchart. It is the specialized symbols, and the meanings of those
symbols, that make it unique.

Some of the basic term used in ERD in describe below

Entities: which are represented by rectangles. An entity is an object or concept about

which.You want to store information

Relationship: which are represented by diamond shapes, show how two entities share
information in the database.

Attributes: which are represented by ovals. A key attribute is the unique, distinguishing
characteristic of the entity. For example, an employee's social security number might be
the employee's key attribute. 

20
5.1.5. Relationship Cardinality:
Relationship cardinality refers to the number of entity instances involved in the
relationship. The cardinality ratio are

 1:1(One to One)
 1:N(1 to many)
 M:N(Many to many)

Primary key :A primary key is a special relational database table column (or
combination of columns) designated to uniquely identify all table records. 

A primary key’s main features are:

It must contain a unique value for each row of data.

It cannot contain null values.

Foreign key :A foreign key is a column (or columns) that references a column (most
often the primary key) of another table. The purpose of the foreign key is to ensure
referential integrity of the data. In other words, only values that are supposed to appear in
the database are permitted.

21
5.1.6. Entity Relationship Diagram

22
5.1.7. Database Table Structure:
1. System User

2. Client information

23
3. Invoice

24
 4. Login time

5.2. System Description:

To develop client billing system we use some operation listed below-

 Authorized client
 System user
 Register new client
 Create Invoice
 View client list
 View invoice

Authorized client: Client must have connection with the organization .who want to take internet
connection; he/she will come to the organization and give their information to the client manager. He/she
must have to select a package. He/she may fill up a form including all necessary information and submit it
to the client manager. The client manager handover it to the admin or system user.

System user : System user or the administrator has a login name and password. With that name and
password he/she signed into the system.

Register new client: After logging into the system in dashboard there is a module or option named
Register new client. By clicking the module admin can register new client.

View client list: By clicking View client list admin can get the information about client. Here the system
has three more option. More, Edit, Delete. By clicking more admin gets detail info about client. By

25
clicking edit option admin can update the info. If there is any unnecessary client info who is not a client
of the company, admin can delete the clients details by clicking delete option.

Create invoice: In dashboard there is another option named Create invoice . By clicking here admin will
get a option named invoice.By clicking invoice admin can create bill of client. All necessary information
is already there if he click submit the bill will be payed.

View invoice: There is another option named view invoice in dashboard. After clicking it there will have
another option to select month.After selecting month it will show payment success. But if client didn’t
pay bill it will show payment pending.

5.2.1. Data Flow Diagram:

A Data Flow Diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modeling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system, which can later be elaborated.
DFDs can also be used for the visualization of data processing (structured design).

A DFD shows what kind of information will be input to and output from the system,
where the data will come from and go to, and where the data will be stored. It does not
show information about the timing of process or information about whether processes
will operate in sequence or in parallel.

At its simplest, a data flow diagram looks at how data flows through a system. It concerns
things like where the data will come from and go to as well as where it will be stored. But
you won't find information about the processing timing (e.g. whether the processes
happen in sequence or in parallel).

We usually begin with drawing a context diagram, a simple representation of the whole
system. To elaborate further from that, we drill down to a level 1 diagram with additional
information about the major functions of the system. This could continue to evolve to
become a level 2 diagram when further analysis is required. Progression to level 3, 4 and
so on is possible but anything beyond level 3 is not very common.

In DFD,there are four symbols that are given in the diagram:

External Entity

An external entity can represent a human, system or subsystem. It is where certain data comes
from or goes to. It is external to the system we study, in terms of the business process. For this
reason, people used to draw external entities on the edge of a diagram.

26
Process

A process is a business activity or function where the manipulation and transformation of

data takes place. A process can be decomposed to finer level of details, for representing
how data is being processed within the process. 

Data Store

A data store represents the storage of persistent data required and/or produced by the process.
Here are some examples of data stores: membership forms, database table, etc. 

Data Flow
A data flow represents the flow of information, with its direction represented by an arrow
head that shows at the end(s) of flow connector. 

5.2.2. Symbol of DFD:

27
5.2.3. DFD of Client billing system:
Context level diagram:

Level 1 DFD:

28
Level 2 Process 1(login):

29
Level 2 Process 2(client):

Level 2 Process 3(create invoice):

30
Level 2 process 4(view invoice):

5.2.4. Effort Distribution:

31
The software project estimation technique leads to estimates of work units required to complete
the software development. A recommended distribution of effort across the definition and
development phases is referred as the 40-20-40 rule. Forty percent of all effort is allocated to
coding and the remaining forty percent is allocated to back end testing. This rule is used as a
guideline only.

In this project 45% of full software development has been allocated to analysis and design, 52%
has been allocated to coding and the remaining 3% percent is allocated to software testing and
support.

A detailed view of the effort distribution chart is illustrated given below:

32
5.2.5. Task scheduling
Project scheduling is an activity of distributing the estimated efforts within the planned
project duration. There are some basic rules for project scheduling. They are as follows
—

Compartmentalization —The project must be compartmentalized into a number of

manageable activities and tasks.

Interdependency — The interdependency of each compartmentalized activity or task

must be determined. Some tasks must occur in sequence while others can occur in
parallel.

Time allocation — Each task to be scheduled must be allocated some number of work
units.

Effort validation — Every project has a defined number of staff members. But in this
case I myself develop it for the course requirement. However in group project it should
be ensured that no more than the allocated number of people has been scheduled at any
given time.

Defined responsibilities — Every task that is scheduled should be assigned to me to

reach the maximum outcome.
33
Defined outcomes — Every task that is scheduled should have a defined outcome. The
outcome is normally a work product or a part of a work product.

5.2.6. Time Chart for Activities

Total system development is a combination of set of tasks. These set of tasks should be
done sequentially and timely. Project schedule works as the guideline of the supervisor
Md.Saidur Rahman and our group member as system developer. The task chart of this
system is as follows —

34
Function point estimation:

FP count for function F1

Type of component Number of Low Complexity Component Total

component of Average High
External Input 2(8,0,0) 2X2 0X0 0X0 4
External output 3(3,0,0) 3X2 0X0 0X0 6
External Query 11(11,0,0) 11X2 0X0 0X0 22
Internal Logical files 7(7,0,0) 7X2 0X0 0X0 14
External Interface files 2(2,0,0) 2X1 0X0 0X0 2
Total UFP 48

Complexity adjustment value for function F1

System Characteristic Rating

Data communications 1
Distributed data processing 0
Performance 4
Heavily used configuration 0
Transaction rate 2
Online data entry 0
End user efficiency 4
Online update 0
Complex processing 0
Reusability 0
Installation ease 3
Operation ease 2
Multiple sites 0
Facilitate change 0
Total 16
VAF(Total divided by 100) 0.16

FPC = UFP X (0.65 + VAF) = 48 X ( 0.65+0.16 ) = 38.88/4=9.72 man per month

35
5.2.7. System Specification:
System requirements specification A detailed statement of the effects that a system is
required to achieve. A good specification gives a complete statement of what the system
is to do, without making any commitment as to how the system is to do it: it constrains
only the externally observable behavior and omits any design or implementation bias. 

A system requirements specification is normally produced in response to a user

requirements specification or other expression of requirements, and is then used as the
basis for system design. The system requirements specification typically differs from the
expression of requirements in both scope and precision: the latter may cover both the
envisaged system and the environment in which it will operate, but may leave many
broad concepts unrefined. Traditionally, system requirements specifications took the
form of natural-language documents. However, both the need for precision and problems
with the increasing size of specification documents have led to the development of more
formal notations. These are capable of being mathematically manipulated so as to show
that the system as designed and implemented actually meets the specification. This may
be especially important in connection with safety-critical systems.

A system requirements specification may also be used in contract negotiations during and
after the purchase of the system, which must meet the specifications that the contractor
has agreed to accept. This is especially important where the purchaser sets out the
requirements in terms of a range of functions and performance levels that the contractor
commits to supplying and meeting, rather than as an inventory of components (hardware
and software) that the contractor undertakes to supply.

5.2.8. Project Cost Estimation

Total Personal cost=1000 Tk

5.2.8.1. Hardware Costs

Desktop system configuration:

Hardware Accessories cost=26000

Hardware Accessories life=36 months

36
 Hardware Accessories useage=45 days

Hardware Accessories use cost=(26000/1080)*45=1083.33 tk

Total hardware cost:1083.33 Tk

Machine Quantity Parts Quantity Price Deprecation Deprecation Hardware

cost cost

Mother 1 3500 3500tk/108 145.83

Board 0
day*45 day

Processor 1 3000 3000tk/108 125

cor2 due 0
day*45 day

Desktop 2GB RAM 1 1500 1500tk/108 62.5

computer 0
day*45 day

320 GB 1 2500 2500tk/108 104.16

HDD 0
day*45 day 1041

Monitor 1 7000 7000tk/108 291.67

0
day*45 day

DVD 1 1500 1500tk/108 62.5

Writer 0
day*45 day

Keyword, 1 1000 1000tk/108 41.67

Mouse & 0
others day*45 day

Printer Printer 1 5000 5000tk/108 208.3

0
day*45 day

37
Total
1041 tk

5.2.8.2: Software cost:

Total software cost=30,000 tk

5.2.8.3. Other Costs

Total other cost =500 tk

Total Project Cost Estimation:

Cost estimate describe the expense that needs to spend during project
development.

1. Personal Cost = = 500/-

2. Hardware Cost = 4000 = 1083/-
3. Software Cost = 30000/-

Total Cost = 31583/-

5.2.9. Cost Benefit Analysis

Cost-benefit analysis is used to determine the economic feasibility of a project.
The total expected costs are weighed against the total expected benefits. If the
benefits outweigh the costs over a given period of time, the project may be
considered to be financially viable. The costs involved with a software
development project will consist of the initial development cost (the costs
incurred up to the point where the new system becomes operational), and the
operating costs of the system throughout its expected useful lifetime (usually a
period of five years). The expectation is that at some point in the system's
lifetime, the accumulated financial benefits of the system will exceed the cost of

38
 development and the ongoing operating costs. This point in time is usually
referred to as the break-even point.

The benefits of the new system are usually considered to be the tangible financial
benefits engendered by the system. These could be manifested as reduced
operating costs, increased revenue, or a combination of the two. In some cases
there may be one or more less tangible benefits (i.e. benefits that cannot be
measured in financial terms), but such benefits are difficult to assess. Indeed the
accuracy of a cost benefit analysis is dependent on the accuracy with which the
development costs, operational costs and future benefits of the system can be
estimated, and its outcome should always be treated with caution.

Break even Analysis of Client Billing System:

Pay back Period:

39
5.3. System Testing
Implementation is the stage of the project where the theoretical design is turned into a
working system. It can be considered to be the most crucial stage in achieving a
successful new system gaining the users confidence that the new system will work and
will be effective and accurate. It is primarily concerned with user training and
documentation. Conversion usually takes place about the same time the user is being
trained or later. Implementation simply means convening a new system design into
operation, which is the process of converting a new revised system design into an
operational one.

5.3.1. System Testing Introduction

Software Testing is the process of executing software in a controlled manner, in
order to answer the question - Does the software behave as specified?. Software
testing is often used in association with the terms verification and validation.
Validation is the checking or testing of items, includes software, for conformance
and consistency with an associated specification. Software testing is just one kind
of verification, which also uses techniques such as reviews, analysis, inspections,
and walkthroughs. Validation is the process of checking that what has been
specified is what the user actually wanted.

Validation : Are we doing the right job?

Verification : Are we doing the job right?
Software testing should not be confused with debugging. Debugging is the
process of analyzing and localizing bugs when software does not behave as
expected. Although the identification of some bugs will be obvious from playing

40
 with the software, a methodical approach to software testing is a much more
thorough means for identifying bugs. Debugging is therefore an activity which
supports testing, but cannot replace testing.
Other activities which are often associated with software testing are static analysis
and dynamic analysis. Static analysis investigates the source code of software,
looking for problems and gathering metrics without actually executing the code.
Dynamic analysis looks at the behavior of software while it is executing, to
provide information such as execution traces, timing profiles, and test coverage
information.

Testing is a set of activity that can be planned in advanced and conducted

systematically. Testing begins at the module level and work towards the
integration of entire computers based system. Nothing is complete without testing,
as it vital success of the system testing objectives, there are several rules that can
serve as testing objectives. They are
 
Testing is a process of executing a program with the intend of finding an d test
case is one that has high possibility of finding an undiscovered error.A successful
test is one that uncovers an undiscovered error.
 
If a testing is conducted successfully according to the objectives as stated above,
it would uncovered errors in the software also testing demonstrate that the
software function appear to be working according to the specification, that
performance requirement appear to have been met.
 
There are three ways to test program.
 For correctness
 For implementation efficiency
 For computational complexity

Test for correctness are supposed to verify that a program does exactly what it
was designed to do. This is much more difficult than it may at first appear,
especially for large programs.

5.3.2. Test Plan

41
 A test plan implies a series of desired course of action to be followed in
accomplishing various testing methods. The Test Plan acts as a blue print for the
action that is to be followed. The software engineers create a computer program,
its documentation and related data structures. The software developers is always
responsible for testing the individual units of the programs, ensuring that each
performs the function for which it was designed. There is an independent test
group (ITG) which is to remove the inherent problems associated with letting the
builder to test the thing that has been built. The specific objectives of testing
should be stated in measurable terms. So that the mean time to failure, the cost to
find and fix the defects, remaining defect density or frequency of occurrence and
test work-hours per regression test all should be stated within the test plan.

6. System Requirements & Using Guideline

To be used efficiently, all computer software needs certain hardware components or other
software resources to be present on a computer. These prerequisites are known as
(computer) system requirements and are often used as a guideline as opposed to an absolute rule.
Most software defines two sets of system requirements: minimum and recommended. With
increasing demand for higher processing power and resources in newer versions of software,
system requirements tend to increase over time. Industry analysts suggest that this trend plays a
bigger part in driving upgrades to existing computer systems than technological advancements.
A second meaning of the term of System requirements, is a generalization of this first definition,
giving the requirements to be met in the design of a system or sub-system.

6.1. System Requirements

6.1.1. Hardware Requirements
HARDWARE REQUIREMENTS

Processor : X86 Compatible processor with 1.7 GHz Clock speed

RAM : 512 MB or more

42
Hard disk : 10 GB or more

Monitor : VGA/SVGA

Keyboard : 104 Keys

Mouse : 2 buttons/ 3 buttons

6.1.2. Software Requirements

SOFTWARE REQUIREMENTS

Operating System : Windows

Front end : HTML,CSS
Back end : PHP, jQuery, javascript

6.1.3. Using Guideline

Once the system is successfully developed the next important step is to ensure that the
administrators are well trained to handle the system. This is because the success of a
system invariably depends on how they are operated and used. The implementation
depends upon the right people being at the right place at the right time. Education
involves creating the right atmosphere and motivating the user. The administrators are
familiarized with the run procedures of the system, working through the sequence of
activities on an ongoing basis.

Implementation is the state in the project where the theoretical design is turned into a
working system. By this, the users get the confidence that the system will work
effectively. The system can be implemented only after through testing.

The systems personnel check the feasibility of the system. The actual data were inputted
to the system and the working of the system was closely monitored. The master option
was selected from the main menu and the actual data were input through the
corresponding input screens. The data movement was studied and found to be correct
queries option was then selected and this contains various reports Utilities provide
various data needed for inventory was input and the module was test run. Satisfactory

43
 results were obtained. Reports related to these processes were also successfully
generated. Various input screen formats are listed in the appendix.

Implementation walkthroughs ensure that the completed system actually solves the
original problem. This walkthrough occurs just before the system goes into use, and it
should include careful review of all manuals, training materials and system

6.1.4. Screen Shots:

Login interface for Client Billing System:

44
Main interfaces of Client Billing System:

Register new Client interface:

45
View client list interface:

Edit client list Interface:

46
Create invoice option interface:

Create invoice interface:

47
View invoice interface:

7. Conclusion & Upcoming Feathers

48
 7.1. Conclusion
By using “Client billing System for ISP(True communication)”, admin can access
database in order to add, remove and update information by his login information. In this
process admin have to confirm password to access the database and all the features. ISP
companies need an effective and accurate billing system to be able to assure their
revenue. Billing systems process the usage of network equipment that is used during the
service usage into a single Call Detail Record (CDR). The billing process involves
receiving billing records from various networks, determining the billing rates associated
with the billing records, calculating the cost for each billing record, aggregating these
records periodically to generate invoices, sending invoices to the customer, and collecting
payments received from the customer.

7.2. Upcoming Feathers

 Database Security Management:
Still we do not implement any database backup process. Primarily it will done by
manually and in next update I planned to use parallel data storage process.
 Add more feature:
This the new part of software. So we put manually some information. Later some part
will be add and some info will be automatic selected.
 Network facility for authorized agent:
Still only Admin can use this software due to profile security. So it will update network
facility with user profile.

--Bibliography/ References—

49
1. http://www.codeproject.com/Articles/10824/Billing-System-Introduction
2. https://www.wikipedia.org
3. www.w3school.com
4. https://webfiles.uci.edu
5. www.sourcecodester.com
6. www.sourcecodester.com
7. http://www.smartdraw.com
8. www.slideshare.net
9. http://www.encyclopedia.com/doc/1O11-systemrequirementsspcfctn.html
10. http://www.technologyuk.net/computing/sad/cost_benefit_analysis.shtml

50