Sample Report

Real Time Billing System Monitoring Tool
1. Introduction
1.1 General Information
The mail goal of this project is to monitor the Real Time Billing
System. The project is used to monitor the different units like
Service Logic Unit (SLU), Service Data Point (SDP) and Signaling
Gateway Unit (SGU) in the Real Time Billing System (RTBS). The
application provides information about all the machines in a
Graphical User Interface in an efficient and easy way.
The user does not need to perform multiple login to the
different machine in the Real Time Billing System to check their
status. All the information is presented in the single window of the
application.
The application has four modules
 System monitor
 Statistics
 Alarm Monitor
 Settings
1.1.1 SYSTEM MONITOR
This module is used to fetch information about different
machines, SDP, SLU, and SGU and to find out their information like
disk usage, processes running, memory utilization, disk capacity etc.
Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 1

We log onto a machine called TRM (TRilogue Manager) from
which a file named hosts is fetched into local machine using FTP
that contains all the information about the different SDP, SLU and
SGU machines available.
TRilogue Manager (TRM) holds the BIP (Billing interface
Package) that Provides Comprehensive, configured billing
information to the remote Station. It is Integrated Alarm Package
(IAP) that monitors the SN platform, Host Interface for Administration
(HIA) is a software package for external host provisioning of the
subscriber database
Service Logic Unit (SLU) is the RTBS controller entity that
contains the service logic of the RTBS .It Interfaces with the SGU,
the IVRU, the SDP, and the CCS in order to manage access and use
the resources of these components.
Service Data Point (SDP) is a powerful database server system
for the Comverse line of IN value added services. It uses advanced
technology to deliver the best possible mass data server for IN
services. Provides high capacity storage and works in Load Sharing
Mode.
Signaling Gateway Unit (SGU) is internal components of
signaling and messaging. It Interfaces between IN to the signaling
links of the telephone network. It is responsible for processing SS7
specifically for INAP, CAMEL, and WIN and works in Load Sharing
Mode.

After fetching the IP addresses and names of different
machines using file handling, TELNET is used to run different
commands in the remote machine.
1.1.2 STATISTICS
This Module is design to show BHCA (Busy Hour Call

Attempts). In telecommunication, busy hour call attempts (BHCA) is
a teletraffic engineering measurement used to evaluate and plan
capacity for telephone network. BHCA is the number of telephone
calls attempted at the busiest hour of the day (peak hour), and the
higher the BHCA, the higher the stress on the network processors.
BHCA is usually used when planning telephoning switching

capacities and frequently goes side by side with the Erlang unit
capacity calculation. As an example, a telephone exchange with a
capacity of one million BHCA is estimated to handle 250,000
subscribers. The overall calculation is more complex however, and
involves accounting for available circuits, desired blocking rates,
and Erlang capacity allocated to each subscriber.
1.1.3 ALRAM MONITOR
This module contains three sub modules, they are
 Table Space
 Data Files

 Invalid Objects
1.1.3.1 Table Space:
A table space is a logical storage unit within an Oracle

database. It is logical because a table space is not visible in the file
system of the machine on which the database resides. A table space,
in turn, consists of at least one data file which, in turn, are
physically located in the file system of the server. Between, a data
file belongs to exactly one table space.
Each table, index and so on that is stored in an Oracle

database belongs to a table space. The table space builds the bridge
between the Oracle database and the file system in which the table's
or index' data is stored.
In Table Space module it shows the Table Spaces and

corresponding Usage space in terms of percentage. Will get this
information by doing the below mentioned steps.
1.1.3.2 Data Files:
A table space in an Oracle database consists of one or more

physical data files. A data file can be associated with only one table
space and only one database. Oracle creates a data file for a table
space by allocating the specified amount of disk space plus the
overhead required for the file header. When a data file is created,
the operating system under which Oracle runs is responsible for
clearing old information and authorizations from a file before
allocating it to Oracle. If the file is large, this process can take a
significant amount of time. The first table space in any database is
always the SYSTEM table space, so Oracle automatically allocates
the first data files of any database for the SYSTEM table space
during database creation.

In this module we have to display the data files of each table

spaces. All this information will be stored in the dba_data_files table
in the oracle data base.
1.1.3.3 Invalid Objects:
Some types of schema objects reference other objects. For

example, a view contains a query that references tables or other
views, and a PL/SQL subprogram might invoke other subprograms
and might use static SQL to reference tables or views. An object that
references another object is called a dependent object, and an
object being referenced is a referenced object . These references
are established at compile time, and if the compiler cannot resolve
them, the dependent object being compiled is marked invalid.
Oracle Database provides an automatic mechanism to ensure

that a dependent object is always up to date with respect to its
referenced objects. When a dependent object is created, the
database tracks dependencies between the dependent object and its
referenced objects. When a referenced object is changed in a way
that might affect a dependent object, the dependent object is marked
invalid. An invalid dependent object must be recompiled against the
new definition of a referenced object before the dependent object
can be used. Recompilation occurs automatically when the invalid
dependent object is referenced.
It is important to be aware of changes that can invalidate

schema objects, because invalidation affects applications running on
the database. This section describes how objects become invalid,
how you can identify invalid objects, and how you can validate
invalid objects.
In a typical running application, you would not expect to see

views or stored procedures become invalid, because applications
typically do not change table structures or change view or stored
procedure definitions during normal execution. Changes to tables,
views, or PL/SQL units typically occur when an application is

patched or upgraded using a patch script or ad-hoc DDL statements.

Dependent objects might be left invalid after a patch has been
applied to change a set of referenced objects.
1.1.4 SETTINGS
This module contains 2 sub modules, they are
 Admin Login
 Admin Operations
1.1.4.1 Admin Login:
In this module the admin can use the Admin Operations module
by entering the username and password. If username and password
is matches then the Admin can make the operations. The username
and password will be saved in the text file. The text file which
contains username and password is stored in the local machine.
1.1.4.2 Admin Operations:
This module is having 4 sections.
 TRM
 SDP
 SLU
 SGU
1.1.4.2.1 TRM:
In this section the admin can change the TRM IP address,

username and password. The TRM IP is used to get the host file.
This contains the information of SLU, SDP and SGU. All this
information is used in the System Monitor module.

The TRM details are stored in a text file, which contains TRM
IP, username and password. The text file will be in the local
machine.
1.1.4.2.2 SDP:
In this section we can add commands and we can delete
commands. These commands will be saved in a text file. The text file
is stored in the local machine. It contains command description and
command. These details will be used in System Monitor module.
1.1.4.2.3 SLU:
In this section we can add and delete commands. These
commands will be saved in a text file. The text file is stored in the
local machine. It contains command description and command.
These details will be used in System Monitor module.
1.1.4.2.4 SGU:
In this module we can add commands and we can delete

1.2 Statement of the Problem
In existing system the auditing team will take care of
monitoring the Real Time Billing System. The auditing team needs to
login each and every machine in the RTBS like, SLU, SDP and SGU.
They have to take care of each machine with proper health check
commands. The commands are ps -ef, df –k, du –h, etc. For
checking the BHCA in existing system the auditing team has to login
to SDP machine and get the details of calls from call_hist table and
they have to represent in a graphical manner of call flow using MS-
Excel. For checking the disk spaces used by Data Files, Table Space
and Valid and Invalid object the auditing team needs to login in to
the corresponding SDP and retrieve the information to take care of
disk.
The proposed system is Real Time Billing System Monitoring
Tool. It gives the features that the earlier was lack off like, the user
no need to login each machine and no need to remember the IP
address of each machine and the health checking commands.
For BHCA the proposed system will automatically displays the
call flow in graphical manner so that user can easily make a plan for
up gradation the system.

The proposed system will also take care of disc space
utilization by giving the information like, Table Space, Data Files and
Valid and Invalid objects in a GUI based table format.
To implement the new system, we have set the goals and
objectives as explained in 1.3.
1.3 Objective of the Study
1.3.1 Goal:
The main goal of the Real Time Billing System Monitoring Tool
is to monitor the RTBS which helps the health check of the system.
1.3.2 Objectives:
The following objectives are set to achieve the
above said goal of this system
 The main objective of the project is to get the features that the
earlier was lack off like, the user no need to login each machine
and no need to remember the IP address of each machine and
the health checking commands.

 For BHCA the objective is to display the call flow in graphical

manner so that user can easily make a plan for up gradation the
system.
 The system is to take care of disc space utilization by giving

the information like, Table Space, Data Files and Valid and
Invalid objects in a GUI based table format.
1.4 Methodology
The RTBS Monitoring Tool adopts incremental software development

methodology. The methodology builds the model using the following steps:
Design, Implementation and testing. Each requirement is identified, designed,
implemented & tested during every iteration. The product is developed is
complete when it satisfies all of its requirements.

Fig 1.4.1: Incremental life cycle model
1.4.1 Why ILM is used for RTBS?
This model is very useful to get the information (System IP and System
Name) of each system in the RTBS from the TRM machine in quickly and early
during the software life cycle. This model is more flexible – the requirement gets
modified with the different machines except SLU, SDP and SGU. Easier to test
and debug during a smaller iteration like timer, configuration reader. Easier to
manage risk because risky pieces are identified and handled during its iteration,
The product is decomposed into a number of components, each of which

are designed and built separately (termed as builds). Each component is
delivered to the client when it is complete. This allows partial utilization of product
and avoids a long development time. It also creates a large initial capital outlay
with the subsequent long wait avoided. This model of development also helps
ease the traumatic effect of introducing completely new system all at once. The
main reason for which the system is chosen are because the testing is done at
every stage and the model helps to find problems earlier on which it can cost
business less than if it was found later on.
Since every system has its own draw backs, the draw backs which were
faced are each phase of an iteration is rigid and do not overlap each other and
problems may arise pertaining to system architecture because not all
requirements are gathered up front for the entire software life cycle.

1.5 Scope of Study
The scope of the study is to monitor the different machines in
the Real Time Billing System. This project is also used to calculate
the BHCA (Busy Hour Call Attempts) in a graphical manner so that
the user can easily come to know the details of call history per hour
in a day and this tool is also gives the information of Tablespace
usage in percentage, Datafiles present in a Tablespace and invalid
objects present in the system.
The application guides the user of the application with a help
file. It replaces the auditing team in Real Time Billing System.
1.5.1 Limitations of the Study:
 The System will not support the commands like top –S.
 The System will not monitor all the system in the Real Time
Billing System.
 If the database is locked due to some reason the system will
not get the information of Call Flow details and Alarm
Monitor details
1.5.2 Organization of the report:

The Report has been organized in to 10 chapters. The introduction chapter

highlights general information relevant to the system, problem statement,
objectives and methodology adopted. Contents of remaining chapters are given
below.
Chapter 2: Literature survey: This chapter discusses the survey Release

Management software and motivation for developing the Release Management
Dashboard.
Chapter 3: System Requirement specification: This chapter will present

functional, non-functional requirements, system requirement of release
Management Dashboard.
Chapter 4: System analysis: This chapter explains in detail about

existing system, need for the system, feasibility study, use case analysis,
sequential models of Release Management Dashboard.
Chapter 5: System Design: This chapter discusses the overall

architectural design of the Release Management Dashboard.
Chapter 6: Detailed Design: This chapter presents the table used in the
Release Management Dashboard.
Chapter 7: Implementation: This chapter gives the coding conventions

and sample code of Release Management Dashboard.
Chapter 8: Testing: This chapter explains various testing techniques

adopted to test the Release Management Dashboard.
Chapter 9: Results: This chapter contains the screen shots of various

modules of Release Management Dashboard.
Chapter 10: Conclusion and Future Enhancement: This chapter

summarizes the Release Management Dashboard and the modules which can be
implemented in future in the Release Management Dashboard.

2. Literature Survey
The objective of this section is to give an overview of the
current state of conceptual knowledge on integration for application
and technology used to develop this tool. The study has focused on
knowledge, ideas, and tools which have been established and used
for developing an application.
2.1 RTBS Architecture:

The below diagram represents the architecture of Real Time
Billing system [6].
Fig 2.1.1: Architecture of Real Time Billing System

2.1.1 RTBS is composed of the following components:
 Service Logic Unit (SLU)

 TRILOGUE Manager (TRM)
 Signaling Gateway Unit (SGU)
 Service Data Point (SDP)
 Multimedia Unit (MMU)
 Massaging and Storage Unit (MSU)
 Call Control Server (CCS)
 High Speed Backbone Network (HSBN)
 Administrative Local Area Network (Admin LAN)
 Service Administration Workstation (SAW)
 Customer Care Web Server (CCWS)
2.1.1.1 Service Logic Unit (SLU):

 It is the RTBS controller entity that contains the service logic of the RTBS.
 Interfaces with the SGU, the IVRU, the SDP, and the CCS in order to
manage access and use the resources of these components [6].
2.1.1.2 TRILOGUE Manager (TRM):

The TRM holds the
 BIP (Billing interface Package) that Provides comprehensive, configured
billing information to the remote station.
 Integrated Alarm Package (IAP) that monitors the SN platform.
 Host Interface for Administration (HIA) is a software package for external
host provisioning of the subscriber database.
2.1.1.3 Signaling Gateway Unit (SGU):
 Internal components of signaling and messaging

 Interfaces between IN to the signaling links of the telephone network
 Responsible for processing SS7 specifically for INAP, CAMEL and WIN

 Working in Load Sharing Mode
2.1.1.4 Service Data Point (SDP):
 Powerful database server system for the Comverse line of IN value added
services.
 Uses advanced technology to deliver the best possible mass data server
for IN services.
 Provides high capacity storage.
 Working in Load Sharing Mode.
2.1.1.5 Interactive Voice Response Unit:
(IVRU) = MMU + MSU
 Sub-system that provides the voice resources for any calls which require
them.
 Provide the capabilities to Play voice announcements and Collect
DTMF digits
 Operates under full SLU control, according to the service logic
2.1.1.6 Call Control Server (CCS):
 ISUP SS7 signaling interfaces to the Network

 Provides all call setup and tear-down control for all the telephony circuits,
2.1.1.7 High Speed Backbone Network (HSBN):
 Ethernet network connecting all other units

 Provides high speed connectivity between system components for mission
critical data
 Built around a segmented switching Ethernet hub

2.1.1.8 Administrative Local Area Network (Admin LAN):
 Used to transfer administrative data and commands via TCP/IP

 Implemented on the same switching hub used for the HSBN, but is totally
isolated from the HSBN
2.1.1.9 Service Administration Workstation (SAW):
 Used for Database Provisioning

 Directly accesses the SDP database
 Could be installed on any PC
2.1.1.10 Customer Care Web Server (CCWS)
Web-based Customer Care and HIA replacement committed to customers [7]

 Support Customer Care
 Separate CC Screens from SAW
 Modern SOAP interface to replace telnet-based HIA
 English, Spanish, and Portuguese clients
2.2 TECHNOLOGY DETAILS
Platform : Java
User Interface : Java Swings
Integrated Development Environment : Net Beans
Database : Oracle
2.2.1 Java
Java (with a capital J) is a high-level, third generation
programming language, like C, FORTRAN, Smalltalk, Perl, and many
others. Compared to other programming languages, Java is most
similar to C. However although Java shares much of C's syntax, it is
not C. Knowing how to program in C or, better yet, C++, will certainly
help you to learn Java more quickly, but you don't need to know C to
learn Java. Unlike C++ Java is not a superset of C. A Java compiler

won't compile C code, and most large C programs need to be
changed substantially before they can become Java programs [1].
2.2.2 Java Swings
Swing is probably the most advanced toolkit on this planet [3].
It has a rich set of widgets. From basic widgets like Buttons, Labels,
Scrollbars to advanced widgets like Trees and Tables. Swing is
written in 100% java. Swing is a part of JFC, Java Foundation
Classes. It is a collection of packages for creating full featured
desktop applications. Swing is part of the Java Foundation Classes
(JFC). The JFC also include other features important to a GUI
program, such as the ability to add rich graphics functionality and
the ability to create a program that can work in different languages
and by users with different input devices.
2.2.3 NetBeans IDE
The NetBeans IDE is open source and is written in the Java
programming language. It provides the services common to creating
desktop applications such as window and menu management,
settings storage and is also the first IDE to fully support JDK 5.0
features. The NetBeans platform and IDE are free for commercial
and non-commercial use, and they are supported by Sun
Microsystems. It can be downloaded from http://www.netbeans.org
2.2.4 ORACLE
The Oracle Database (commonly referred to as Oracle
RDBMS or simply as Oracle) is an object-relational database

management system (ORDBMS) produced and marketed by Oracle
Corporation. Larry Ellison and his friends and former co-workers Bob
Miner and Ed Oates started the consultancy Software Development
Laboratories (SDL) in 1977. SDL developed the original version of
the Oracle software. The name Oracle comes from the code-name of
a CIA-funded project Ellison had worked on while previously
employed by Ampex.
Oracle runs on virtually all platforms, including Linux, Unix,
and Windows. It is fully multi-threaded using kernel threads, and
provides application program interfaces (APIs) for many
programming languages, including C, C++, Eiffel, Java, Perl, PHP,
and Python.

3. System Requirement Specification
3.1 Functional Requirements
Functional Requirement defines a function of a software system and how the system
must behave when presented with specific inputs or conditions. These may include calculations,
data manipulation and processing and other specific functionality.
Requirement Tag Requirement Description Criticality
An application that monitors
RTBS-Req different machines of RTB

High
System needs to be developed.
User should be able to access
RTBS-Req the health of all the available

High
systems in one single window.
The application must have a
RTBS-Req Login window to prevent non High
Admin user to use it.

Administrators must be able to
change the Login details that
RTBS-Req include changing username, High
password, updating TRM ip
address.
Administrator should be able to
RTBS-Req add and delete the commands to High
run.
The application should allow non
RTBS-Req Admin users to fetch the High
information using preset inputs.
User management Creation,
RTBS-Req change password, creating user Medium
levels
There should be the provision to
RTBS-Req export the fetched information in Medium
excel sheet
Table 3.1.1 Functional Requirements
3.2 Non - Functional Requirements
Non – Functional Requirements are the requirements that are
not directly concerned with the specific functions delivered by the
system. They may relate to emergent system properties such as
reliability, response time and store occupancy. They may define
constraints on the system such as the capabilities of I/O devices and
the data representation used in the System interface.

Non-Functional Requirements specify or constrain the
emergent properties of the system. They may specify system
performance, security, availability, and other emergent properties.
Non-Functional Requirements arise through user needs,
because of budget constraints, because of the need of the
interoperability with other hardware and software systems, or
because of external factors such as safety regulations or privacy
legislation.
Requirement Tag Requirement Description Criticality
Accuracy: The application must
provide latest health information to

RTBS-Req High
the user which is fetched during the
time of login.
Usability: The application should
be user friendly, it should be more

RTBS-Req High
efficient to learn and it should
satisfy the user requirements.
RTBS-Req Maintainability: The installation High
and operation manual of this system

will be provided to the specific user.
Modifiability: The application must
be structured to support later
expected modification. Design of
this product is done in such a way
RTBS-Req that later if user wants some Medium
modifications these can be done
very easily. Due to change in
working environment, requirements
of user can also be changed.
Reliability. The software developed
should be highly reliable. The
unexpected error conditions are to

RTBS-Req High
be handled properly and displayed
to the user in understandable
manner
Efficiency: The amount of
computing resources and time
RTBS-Req required by the application to Medium
perform any function must be
optimum.
RTBS-Req Flexibility : The application should Medium
be flexible such that modification
can be done very easily without
much effort. The application must
be able to withstand the

modifications and work in the
changed environment.
Security: The application should be
RTBS-Req secure enough to allow only High
authorized user to use it.
The information provided to the
RTBS-Req user must me in a GUI format and Medium
easily understandable.
Table 3.1.1 Non - Functional Requirements
3.3 Hardware and Software Requirements
Before installing the software one needs to make sure that your computer
meets the following requirements as suggested by Microsoft:
Minimum Requirements Recommended:
3.3.1 Hardware Requirements:
 Processor 500 MHz or more than 500 MHz
 Memory 256 or higher

 Hard Disk 1.5 GB of available space
 Video Resolution of 1024 X 768 or higher
3.3.2 Software Requirements:
Tools : Net Beans
Languages : Java Swings
Operating system : Windows XP
4. System Analysis
System Analysis is an activity that encompasses most of the tasks that are
called software system engineering. Analysis is a detailed study of the various
operations performed by a system. Once analysis is completed, the analyst has
firm understanding of what is to be done.
In other words, it is a reduction of an entire system by studying the various

operations performed and their relationships within the system; an examination of

business activity, with a view to identify problem areas and recommending

alternative solution.
The objectives of the system analysis are
 Identifying the need.

 Evaluating feasibility study.
 Identifying hardware and software requirements.
 Allocating functions to hardware and software.
 Create a system definition.
System development can generally be thought of having two major

components: systems analysis and systems design. In System Analysis more
emphasis is given to understanding the details of an existing system or a
proposed one and then deciding whether the proposed system is desirable or not
and whether the existing system needs improvements. Thus, system analysis is
the process of investigating a system, identifying problems, and using the
information to recommend improvements to the system.
Systems analysts are the architects, as well as the project leaders, of an

information system. It is their job to develop solutions to users' problems,
determine the technical and operational feasibility of their solutions, as well as
estimate the costs to develop and implement them
4.1 Existing System
In existing system the auditing team will take care of
monitoring the Real Time Billing System. The auditing team needs to
login each and every system in the RTBS like, SLU, SDP and SGU.
They have to take care of each machine with proper health check
commands. The commands are ps -ef, df –k, du –h, etc.

For checking the BHCA in existing system the auditing team
has to login to SDP machine and get the details of calls from
call_hist table and they have to represent in a graphical manner of
call flow using MS-Excel.
For checking the disk spaces used by Data Files, Table Space
and Valid and Invalid object the auditing team needs to login in to
the corresponding SDP and retrieve the information to take care of
disk.
4.2 Limitations of Existing System
The user should know the each system IP address, username
and password. The existing system is very time consuming since
each time user has to login to the different machines and user
should know the commands for health check.
4.3 Proposed System
The proposed system is Real Time Billing System Monitoring
Tool. It gives the features that the earlier was lack off like, the user
no need to login each machine and no need to remember the IP
address of each machine and the health checking commands.
For BHCA the proposed system will automatically displays the
call flow in graphical manner so that user can easily make a plan for
up gradation the system.

The proposed system will also take care of disc space utilization by
giving the information like, Table Space, Data Files and Valid and
Invalid objects in a GUI based table format.
4.4 Feasibility Study
The purpose of this document is to describe the various
studies that were carried out to validate the feasibility of this module
or system.
Feasibilities are.
 Economic Feasibility
 Technical Feasibility
 Behavioral Feasibility
 Schedule feasibility
4.4.1 Economic Feasibility
Economic justification is the bottom line consideration for most
of the systems. But in general, this is the most frequently used
method for evaluating the effectiveness of the system. It mainly
depends on the cost/benefit analysis. It is found that due to the free
availability of the required software with the already existing
hardware resources, the project is feasible economically.
In our case we mainly focus on open source tools like Net
Beans IDE, open source environment which provides by java
programming Language and which is platform independent.

4.4.2 Technical Feasibility
The technical feasibility is one of the main parameters on
which the feasibility of the project is decided.
It is found that hardware requirements are easily satisfied, as
the requirements are small. The software requirements are met. The
skill set required developing the project modules are with knowledge
of
 Java
 Oracle 8i
4.4.3 Behavioral Feasibility
In this feasibility considering the vendor whether they are
accepting the new system or not. Generally people resist changes.
According to the conducted survey the vendor are eager to use
the system such that at any point of time the user should be able to
use the application.
4.4.4 Schedule Feasibility
It is a measure of how reasonable the project timetable is. If a
project is completed after taking too much time then it may be fail.
The study estimating how long the system will take to develop, and
weather it can be completed in a given time period.
In our case, we made a weekly plane to review our project
progress. For each module we set a time according to module

requirements and keenly focus to complete the module in set time
period.
4.5 Use Case Analysis
A use case analysis is the most common technique used to identify the
requirements of a system (normally associated with software/process design) and
the information used to both define processes used and classes (which are a
collection of actors and processes) which will be used both in the use case
diagram and the overall use case in the development or redesign of a software
system or program. The use case analysis is the foundation upon which the
system will be built.
An object-oriented method for designing information systems by breaking

down requirements into user functions. Each use case is a transaction or
sequence of events performed by the user. Use cases are studied to determine
what objects are required to accomplish them and how they interact with other
objects.
A use case diagram in the Unified Modeling Language (UML) is a type of

behavioral diagram defined by and created from a Use-case analysis. Its purpose
is to present a graphical overview of the functionality provided by a system in
terms of actors, their goals (represented as use cases), and any dependencies
between those use cases.
The main purpose of a use case diagram is to show what system functions
are performed for which actor. Roles of the actors in the system can be depicted.

4.5.1 SEQUENCE MODELS
A sequence models in Unified Modeling Language (UML) is a

kind of interaction diagram that shows how processes operate with
one another and in what order.
A sequence diagram shows, as parallel vertical lines ( lifelines),

different processes or objects that live simultaneously, and, as
horizontal arrows, the messages exchanged between them, in the
order in which they occur. This allows the specification of simple
runtime scenarios in a graphical manner.
Use case 1
Fig 4.5.1: System monitoring use case model

Sequence diagram 1
Fig 4.5.2: System monitoring sequence diagram

Actor: RTBS User
Preconditions: The system must be configured and the entire

machine is running properly.
Outcome: Health check of machines will be displayed in GUI.
Alternate Scenario: If the user info is incorrect, then login to the

machine is denied.
 The user will login by using the user name and password
specified in Configuration application.
 The user sends requests to the proper machines and the

request is executed on that machine.
 The executed command is displayed back to the user view port

which is a GUI.
Use Case 2:
Fig 4.5.3: statistics use case model

Sequence diagram 2

Fig 4.5.4: statistics sequence diagram
Actor: RTBS User
Preconditions: The system must be configured and the database is

unlocked.
Outcome: Stats of five tables are displayed in graphs.

machine is denied, and if the database is lock then graph will not
display in GUI for this we need to manually unlock it.

 The user sends query to the proper machines and the query is
executed on that machine.
 The executed query is displayed back to the user view port as

a Graph.
Use Case 3
Fig 4.5.5: Alarm monitoring use case model

Sequence Diagram 3
Fig 4.5.6: Alarm monitoring sequence diagram
Actor: RTBS User
Preconditions: The system must be configured and the database is

unlocked.
Outcome: Stats of different tables are displayed in GUI as a tabular

form.

machine is denied, and if the database is lock then data will not
display in GUI for this we need to manually unlock it.

 The user sends query to the proper machines and the query is
executed on that machine.
 The executed query is display back to user GUI in tabular

form.
Use Case 4
Fig 4.5.7: Administrator use case model

Sequence Diagram 4
Fig 4.5.8: Administrator sequence diagram
Actor: RTBS User
Preconditions: The system must be configured.
Outcome: Administrator are able to change password, inserts new

command, delete commands.
Alternate Scenario: If the Administrator info is incorrect, then login

to the machine is denied, And in case of changing password if

Administrator provide wrong password then Administrator is not able

t o change password.
 ∙The Administrator will login by using the administrator name

and password specified in Configuration application.
 The administrator sends details like for changing password he

provides old password and new password and again retype
new password.
 The details are stored in local database like notepad.
5. System Design
Systems design is the process or art of defining the architecture,

components, modules, interfaces, and data for a system to satisfy specified
requirements. One could see it as the application of systems theory to product
development. There is some overlap with the disciplines of systems analysis,
systems architecture and systems engineering.
5.1 System Architecture

Fig 5.1.1: Real Time Billing System Architecture
5.1.1 RTBS is composed of the following components:
 Service Logic Unit (SLU)

 TRILOGUE Manager (TRM)
 Signaling Gateway Unit (SGU)
 Service Data Point (SDP)
 Multimedia Unit (MMU)
 Massaging and Storage Unit (MSU)
 Call Control Server (CCS)
 High Speed Backbone Network (HSBN)
 Administrative Local Area Network (Admin LAN)
 Service Administration Workstation (SAW)
 Customer Care Web Server (CCWS)
5.1.1.1 Service Logic Unit (SLU):

 It is the RTBS controller entity that contains the service logic of the RTBS.

 Interfaces with the SGU, the IVRU, the SDP, and the CCS in order to
manage access and use the resources of these components.
5.1.1.2 TRILOGUE Manager (TRM):

The TRM holds the
 BIP (Billing interface Package) that Provides comprehensive, configured
billing information to the remote station.
 Integrated Alarm Package (IAP) that monitors the SN platform.
 Host Interface for Administration (HIA) is a software package for external
host provisioning of the subscriber database.
5.1.1.3 Signaling Gateway Unit (SGU):
 Internal components of signaling and messaging

 Interfaces between IN to the signaling links of the telephone network
 Responsible for processing SS7 specifically for INAP, CAMEL and WIN
5.1.1.4 Service Data Point (SDP):
 Powerful database server system for the Comverse line of IN value added
services.
 Uses advanced technology to deliver the best possible mass data server
for IN services.
 Provides high capacity storage.
 Working in Load Sharing Mode.
5.2 Modules Details
The application has four modules
 System monitor
 Statistics

 Alarm Monitor
 Settings
5.2.1 SYSTEM MONITOR
This module is used to fetch information about different
machines, SDP, SLU, and SGU and to find out their information like
disk usage, processes running, memory utilization, disk capacity etc.
5.2.1.1 What is TRM machine?
TRilogue Manager (TRM) holds the BIP (Billing interface
Package) that Provides Comprehensive, configured billing
information to the remote Station. It is Integrated Alarm Package
(IAP) that monitors the SN platform, Host Interface for Administration
(HIA) is a software package for external host provisioning of the
subscriber database
5.2.1.2 What is SLU?
Service Logic Unit (SLU) is the RTBS controller entity that
contains the service logic of the RTBS .It Interfaces with the SGU,
the IVRU, the SDP, and the CCS in order to manage access and use
the resources of these components.

5.2.1.3 What is SDP?
Service Data Point (SDP) is a powerful database server system
for the Comverse line of IN value added services. It uses advanced
technology to deliver the best possible mass data server for IN
services. Provides high capacity storage and works in Load Sharing
Mode.
5.2.1.4 What is SGU?
Signaling Gateway Unit (SGU) is internal components of
signaling and messaging. It Interfaces between IN to the signaling
links of the telephone network. It is responsible for processing SS7
specifically for INAP, CAMEL, and WIN and works in Load Sharing
Mode.
After fetching the IP addresses and names of different
machines using file handling, TELNET is used to run different
commands in the remote machine.
5.2.2 STATISTICS

BHCA is usually used when planning telephoning switching

capacities and frequently goes side by side with the Erlang unit
capacity calculation. As an example, a telephone exchange with a
capacity of one million BHCA is estimated to handle 250,000

subscribers. The overall calculation is more complex however, and

involves accounting for available circuits, desired blocking rates,
and Erlang capacity allocated to each subscriber.
This Module Fetches data from the below tables,
1. CALL_HISTORY_MAIN_A
2. RECHARGE_HISTORY_MAIN_A
3. PS_TRANSACION_MAIN_A
4. OSA_MAIN_A
5. MTR_MAIN_A
The fetched data from the database will be represented in

terms of graph.
Table CALL_HISTORY_MAIN_A
From this table we fetch the number of calls/hour in a day.
Query: select count(*) from call_history_main_a group by

to_char(start_call_date_time,'hh24')
Table RECHARGE_HISTORY_MAIN_A
From this table we fetch the number of Recharge/hour in a day
Query: select count(*) from Recharge_history_main_a group

by to_char(recharge_date_time,'hh24')
Table PS_TRANSACION_MAIN_A
From this table we fetche the number of Payment/hour in a

day.
Query: select count(*) from Ps_Transaction _main_a group by

to_char(recharge_date_time,'hh24')

Table OSA_MAIN_A
From this table we fetch the number of OSA data /hour in a day
data.
Query: select count(*) from Osa_History _main_a group by

to_char(Start_Call_date_time,'hh24')
Table MTR_MAIN_A
From this table we fetch the number of mod_date/hour in a day

data .
Query: select count(*) from mtr _main_a group by

to_char(mod_date,'hh24')
5.2.3 ALRAM MONITOR
 Table Space
 Data Files
 Invalid Objects
5.2.3.1 Table Space:

Each table, index and so on that is stored in an Oracle

database belongs to a table space. The table space builds the bridge
between the Oracle database and the file system in which the table's
or index' data is stored.

In Table Space module it shows the Table Spaces and

corresponding Usage space in terms of percentage. Will get this
information by doing the below mentioned steps.
5.2.3.2 Data Files:

physical data files. A data file can be associated with only one table
space and only one database. Oracle creates a data file for a table
space by allocating the specified amount of disk space plus the
significant amount of time. The first table space in any database is
always the SYSTEM table space, so Oracle automatically allocates
the first data files of any database for the SYSTEM table space
during database creation.
In this module we have to display the data files of each table

spaces. All this information will be stored in the dba_data_files table
in the oracle data base.
5.2.3.3 Invalid Objects:
5.2.3.3.1 About Object Dependencies and Object
Invalidation:

them, the dependent object being compiled is marked invalid.

Oracle Database provides an automatic mechanism to ensure

that a dependent object is always up to date with respect to its
referenced objects. When a dependent object is created, the
database tracks dependencies between the dependent object and its
referenced objects. When a referenced object is changed in a way
that might affect a dependent object, the dependent object is marked
invalid. An invalid dependent object must be recompiled against the
new definition of a referenced object before the dependent object
can be used. Recompilation occurs automatically when the invalid
dependent object is referenced.
It is important to be aware of changes that can invalidate

schema objects, because invalidation affects applications running on
the database. This section describes how objects become invalid,
how you can identify invalid objects, and how you can validate
invalid objects.
5.2.3.3.2 Object Invalidation:
In a typical running application, you would not expect to see

views or stored procedures become invalid, because applications
typically do not change table structures or change view or stored
procedure definitions during normal execution. Changes to tables,
views, or PL/SQL units typically occur when an application is
patched or upgraded using a patch script or ad-hoc DDL statements.
Dependent objects might be left invalid after a patch has been
applied to change a set of referenced objects.
Use the following query to display the set of invalid objects in

the database:
SELECT object_name, object_type FROM dba_objects WHERE

status = 'INVALID';
This module gets the information of invalid objects which are

present. That means it shows the invalid Object Name and Object
Type.

All this information will be stored in all_objects table in the

oracle data base. By using this table we can get the invalid objects
by mentioning the condition as status=’INVALID’ .
5.2.4 SETTINGS
This module contains 2 sub modules, they are
 Admin Login
5.2.4.1 Admin Login:
is matches then the Admin can make the operations. The username
and password will be saved in the text file. The text file which
contains username and password is stored in the local machine.
5.2.4.2 Admin Operations:
 TRM
 SDP
 SLU
 SGU
5.2.4.2.1 TRM:

information is used in the System Monitor module.

The TRM details are stored in a text file, which contains TRM
IP, username and password. The text file will be in the local
machine.
5.2.4.2.2 SDP:
In this section we can add commands and we can delete
5.2.4.2.3 SLU:
In this section we can add and delete commands. These
These details will be used in System Monitor module.
5.2.4.2.4 SGU:

5.3 User Interface Design
The User interface is designed in Java Swings.
Priority to the user is given in designing the interface such that

he/she may have easy interaction with the application.
When a user starts the application, it redirects him to system

monitor where he /she can check the status of available machines by
running the preset commands.
User can also check the statistics of BHCA by clicking

statistics tab on the window and also he/she can check the
tablespace usage, datafiles, and invalid objects by clicking on the
alarm monitor tab.
In system monitor user is presented with three buttons SLU,

SGU, SDP. By clicking each button user can find the available
machine and run the preset commands on each machine to get its
information in the interface.
In statistics we can view CALL, RECHARGE, PAYEMENT, MTR,

OSA information in a graphical manner.
In Alarm Monitor section user can view the tablespace usage,

datafiles, and invalid objects by clicking Tablespace, datafiles, and
invalid objects tabs respectively.
If the user is not an administrator, he will have access only to
the machines and their information preset by the administrator. But
an administrator can Login to the application by using Admin Login
window. He/She can change the TRM ip, username, password in
TRM section after successfully logging in to the system. An
administrator can also add or delete SDP, SGU, and SLU commands
according to the needs.

5.4 ACTIVITY DIAGRAM
Activity diagrams represent the business and operational

workflows of a system. An Activity diagram is a dynamic diagram that
shows the activity and the event that causes the object to be in the
particular state.
The purpose of activity model is to abstract the workflow

behind the system being designed. Activity Diagrams are also useful
for analyzing a use case by describing what actions need to take
place and when they should occur; describing a complicated
sequential algorithm; and modeling applications with parallel
processes.

ACTIVITY DIAGRAM 1
Run Configuration
application
Enter default values
Validate input
values
Store the default

values in database
Fig 5.4.1: Activity Diagram for configuration application
 The User of the application has to run the configuration

application first.
 Here the user will provide some default values depending on

his requirements.

 These values will be stores in the database.
These values will be used in the main application to Login into the
System.
ACTIVITY DIAGRAM 2
Fig 5.4.2: System monitoring activity diagram

provided in the configuration application.
 The entered values are checked, if they are valid then only the
user can proceed.
 The user can modify the default values from configuration

application to the desired values.
 Then user sends the command to execute. If command is valid

then results will be displayed back to user, if not it gives an
error message.
6. Detail Design
As a core engineering process, detailed design transforms

concept alternatives, preliminary physical architectures, design
specifications, and technical requirements into final, cross-
disciplinary design definitions. These designs are further refined and
all accompanying documentation required for manufacturing is
completed in order for timely delivery to the customer of a fully
defined, complete product.
System design is a modeling process. It can be defined as a

transaction from user ’s view to programmer ’s or the database
person’s view. The term design is used in two ways. Used as noun; it
represents the result of the design process.
It is the first level design. In this level the focus is made on

modules. This level describes which modules are used how these
are interconnected. The system can be designed using Use Case
diagrams (Unified Modeling Language).
6.1 INPUT DESIGN

Input design is a part of overall system design. The main

objective during the input designs the input designs is given bellow.
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy
 To ensure that the input is acceptable and understood by the

user.
6.2 ARCHITECTURAL DESIGN
Large Systems are always decomposed into Sub-Systems that

provide some related set of services. The process of identifying
these Sub-Systems and establishing a framework for Sub-System
Control and Communication is called Architectural Design may be
based on a particular Architectural Model or Style.
Fig 6.2.1: Two – tier architecture

Fig 6.2.2: Database Design
6.2.1 Presentation layer
This layer is the front-end that handles presentation and

validation. Thus all user interfaces will be available through this
layer, which are developed in Java Swings.
6.2.2 Component layer
This layer has Web Server which processes required from

multiple user and respond back to the browser. It maintains a
repository of Java server Page. This layer interacts with the
application and database layer for operations.
It contains all the component of the presentation layer such as

image (LOGO).jpg, etc.) In image folder and style in cascading style
sheet folder.
6.2.3 Application layer (Business rules/ Logic)

This layer hosts the business rules/logic. This layer handles

load balancing, database connection polling and transaction
distribution. This is done using JDBC type 3 driver in our application.
6.2.4 Database layer
This layer will store data manage data integrity. Adding

additional processors, memory and I/O controller can scale up this
layer.
This is done using all java classes in our application such that
table named classes with their corresponding details columns as
attribute in the class help to fetch and load corresponding details as
and when required which reduce the money and time complexity
simultaneously.
7. Implementation
To completely implement the system we have followed the following steps,

namely, planning, hardware and software acquisition, implementing the code,
testing every possible generated code, demo to the user and output design.
Planning: Initially a primary implementation plan is prepared to schedule

and manage many different activities that must be completed for a
successful system implementation.

Hardware and Software acquisition: The software’s required for the

project is acquired for the implementation of the system.
Implementing the code: This includes implementing the code for

different modules. This needs connecting the back end to the front end.
Here the different code required for different modules is implemented and
the database connection string is changed accordingly.
Testing every possible generated code: In this every possible

generated code is tested for correctness by entering the data. A search is
made for any errors, and if found steps are taken to eliminate them.
Demo to the user: The end user is given a demonstration of the new
system and the feedback is taken from them, and suggestions from them
are considered for further improvements.
Output Design: Computer output is the most important and direct source
of information to the user. Efficient, intelligible, output design should
improve the systems relationships with the user. Here the output design is
made in the form of forms, which is generated based on the user inputs
and the user interaction.
7.1 Development of the System
The following are tools to be installed for developing and deploying the
application.
 Any java development environment.

 Latest version of java compiler.
 Real Time Billing System TRM IP address.
7.2 Coding Conventions:
Code conventions are important to programmers for a number of reasons:

 80% of the lifetime cost of a piece of software goes to maintenance.
 Hardly any software is maintained for its whole life by the original author.

 Code conventions improve the readability of the software, allowing

engineers to understand new code more quickly and thoroughly.
 If you ship your source code as a product, you need to make sure it is as
well packaged and clean as any other product you create.
7.2.1 File Names

This section lists commonly used file suffixes and names.
7.2.2 File Suffix
JavaSoft uses the following file suffixes:
File Type Suffix

Java source .java
Java bytecode .class
7.2.3 Common File Names

Frequently used file names include:
File Name Use

The preferred name for makefiles.
GNUmakefil We use gnumake to build our
e software.
The preferred name for the file that

README summarizes the contents of a
particular directory
7.2.4 File Organization
 A file consists of sections that should be separated by blank lines and an

optional comment identifying each section.
 Files longer than 2000 lines are cumbersome and should be avoided.

7.2.5 Java Source Files

Each Java source file contains a single public class or interface. When
private classes and interfaces are associated with a public class, you can put
them in the same source file as the public class. The public class should be the
first class or interface in the file.
7.3 Sample Code:
//Automated Telnet Client class is used to run the command and get the
out put of that command in a text file to the local machine.
public class AutomatedTelnetClient
public TelnetClient telnet = new TelnetClient();
public InputStream in;
public PrintStream out;
public String prompt = ">";
public AutomatedTelnetClient(String server, String user, String pass)
try
// Connect to the specified server
telnet.connect(server, 23);
// Get input and output stream references
in = telnet.getInputStream();
out = new PrintStream(telnet.getOutputStream());
// Log the user on
readUntil("login: ");
write(user);

Thread.currentThread().sleep(500);
write(pass);
// Advance to a prompt
//readUntil( prompt + " ");
catch (Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF,
"Incorrect Login Details or Unable to connect to machine", "Connect",
JOptionPane.ERROR_MESSAGE);
public void disp()
File f = new File("D:\\java\\output.txt");
BufferedReader freader = null;
try
freader = new BufferedReader(new FileReader(f));
catch (FileNotFoundException ex)
//Logger.getLogger(AuditView.class.getName()).log(Level.SEVERE, null,
ex);
String s;
try
while ((s = freader.readLine()) != null)

TA.append(s);
TA.append("\n");
catch (IOException ex)
//Logger.getLogger(AuditView.class.getName()).log(Level.SEVERE, null,
ex);
public String readUntil(String pattern)
try
char lastChar = pattern.charAt(pattern.length() - 1);
StringBuffer sb = new StringBuffer();
boolean found = false;
char ch = (char) in.read();
while (true)
sb.append(ch);
if (ch == lastChar)
if (sb.toString().endsWith(pattern))
return sb.toString();
ch = (char) in.read();

catch (Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF, "
Incorrect Login Details2", "Connect", JOptionPane.ERROR_MESSAGE);
return null;
public String readUntil1(String pattern)
try
char lastChar = pattern.charAt(pattern.length() - 1);
StringBuffer sb = new StringBuffer();
boolean found = false;
char ch = (char) in.read();
FileOutputStream f=new
FileOutputStream("D:/java/output.txt");
while (true)
f.write(ch);
sb.append(ch);
if (ch == lastChar)
if (sb.toString().endsWith(pattern))
return sb.toString();

ch = (char) in.read();
catch (Exception e)
return null;
public void write(String value)
try
out.println(value);
out.flush();
//System.out.println(value);//Thread.currentThread().sleep(
11000);
catch (Exception e)
public String sendCommand(String command)
try

write(command);
return readUntil1( prompt + " " );
catch (Exception e)
return null;
public void disconnect()
try
telnet.disconnect();
catch (Exception e)
8. Testing
Testing is a process of executing a program with the intent of

finding an error. Software testing is the execution of program to find
its faults. The testing process focuses on the logical internals of the

software, ensuring that all statements have been testing and on the
functional externals, that is conducting test to uncover error and
ensure that defined input will produce actual results agreed with
required results.
8.1 TEST STRATEGIES
8.1.1 UNIT TESTING:
Unit testing is the first level of testing. In this, different

modules are tested against the specifications produced during
design for the modules. Unit testing is essentially for verification of
the code produced during the coding phase. It is done by the
programmer of module.
In RTB System we have five modules.
 SETTINGS
 SYSTEM MONITOR
 STATISTICS
 ALARM MONITOR
 HELP FILE
8.1.1.1 SETTINGS
The SETTINGS module contains 2 sub modules, they are
 Admin Login
8.1.1.1.1 Admin Login:

is matches then the Admin can make the operations. Here we try
entering the correct username and password to check whether it is
correctly logging in and also provide incorrect values to check
whether the module is barring the user from entering into
application.
8.1.1.1.2 Admin Operations:
 TRM
 SDP
 SLU
 SGU
8.1.1.1.2.1 TRM:

information is used in the System Monitor module .Here we try and
change IP address username and password and check in the local
file for the desired changes.
8.1.1.1.2.2 SDP:

command. Here we add commands and check whether local machine
is able to store it or not. And when we delete it, we check from the
local file that whether it has deleted the command from the file or
not.
8.1.1.1.2.3 SLU:

In this module we can add and delete commands. These

These details will be used in System Monitor module. . Here we add
commands and check whether local machine is able to store it or
not. And when we delete it, we check from the local file that whether
it has deleted the command from the file or not.
8.1.1.1.2.4 SGU:

Here we add commands and check whether local machine is able to
store it or not. And when we delete it, we check from the local file
that whether it has deleted the command from the file or not.
8.1.1.2 SYSTEM MONITOR
The SYSTEM MONITOR module is used to fetch information

about different machines, SDP, SLU, and SGU and to find out their
information like disk usage, processes running, memory utilization,
disk capacity etc.

We check whether the module can correctly log into a TRM

machine by providing different valid TRM ip and password by editing
local file containing TRM details.
Again we provide incorrect login details and see whether it works as

per the expectations.

We edit the local file containing SDP, SLU, SGU commands

and try to run different commands and check for the desired results.
We try to put incorrect commands and check for the error it

generates.
We try to edit the local hosts providing numerous machine ips

and their names and check whether all the SDP, SLU, and SGU ips
and names are being fetched or not.
8.1.1.3 STATISTICS

This module fetches the information from all the SDPs present
in the RTB System.
We try to lock a particular SDP to check whether it is able to

fetch the information.
We unlock it and check the information again. The fetched

information is compared by manually logging in to the SDP and
check the database table.
8.1.1.4 ALARM MONITORING
 Table Space

 Data Files
 Invalid Objects
8.1.1.4.1 Table Space:

This module finds the percentage usage of each tablespace

present in a system.
Here we fetch the tablespace information in the application

GUI. Again we login into the SDP and fetch the same information by
manually. Upon comparing if the two information matches then the
test is successful and the module is correct else not.
8.1.1.4.2 Data Files:

physical data files. A data file can be associated with only one
tablespace and only one database. Oracle creates a data file for a
tablespace by allocating the specified amount of disk space plus the
significant amount of time.
This module finds the datafiles inside a tablespace and

displays in a GUI format.
We manually enter into a system and create a datafile inside a

tablespace, then the module is run to check whether the datafile is
listed or not.

8.1.1.4.3 Invalid Objects:

them, the dependent object being compiled is marked invalid. This
module checks the number of invalid objects present in a particular
system.
Again we manually convert some objects as invalid and run the

module to check whether the created invalid objects are listed or
not.
8.1.1.5 HELP FILE
This module guides user whenever they face some problem in

understanding of the application working.
We test this module by checking whether it describes each and

every aspect of the application or not and whether or not the
application is providing the detailed information of a particular
module.
For e.g. if we click SDP on the file it should give a brief

description of SDP and describe what SDP button inside SYSTEM
MONITOR module will do on clicking it.
8.1.2 INTEGRATING TESTING
Integration testing takes place when modules or sub system

are integrated to create larger systems. After testing each of the
individual components using various testing strategies we bring
together all these components and conduct integration testing.

Integration testing is a systematic technique for constructing

the program structure while at the same time conducting test to
uncover errors associated with interfacing. This testing is done using
the bottom-up approach to integrate the software components of the
software system into functioning whole.
In RTB System we enter into the application by providing the

login details and add some commands for different systems SDP,
SGU and SGU.
We check inside SYSTEM MONITOR module whether these

commands are listed or not and try to run it.
We change the TRM ip in the SETTINGS module to login into

different TRM machine and check whether the application is
providing correct statistics of the SDP machines inside
STATISTICTS module.
We check whether the tablespace information are correctly

fetched by the application by providing new TRM ip in the SETTINGS
module.
All the modules are successfully integrated and tested to

complete the system testing of RTB System Monitoring Tool.
8.1.3 SYSTEM TESTING
System testing was done by with reference to SRS and Defects

that Crept in the system has been found defect free and is working
well. System testing is concerned with interfaces; design Logic,
Control flow recovery, Procedures throughput, capacity and timing
characteristics.
The purpose of this phase is to demonstrate that the software

developed satisfies requirements in the system design in project
requirement document. In RTB System Monitoring Tool application,
this phase includes system/integration testing to test the system
level functionality, security, performance, usability and integration of
the different modules.

8.1.4 ACCEPTANCE TESTING
Testing conducted to enable a user/customer to determine

whether to accept a software product. Normally performed to
validate the software meets a set of agreed acceptance criteria.
Acceptance testing allows users to ensure that the system

meets requirements. Acceptance testing acts as a final verification of
the project function and proper functioning of the system.
8.2 TEST CASES
Test Status
Expected Actual
case Test Cases Input Data
Results Results (Yes/No)
No.
The control The control

Verify the
Username should come came to
username
1 and to Admin Admin Yes
and
password Operations Operations
password
window window
Login as An error
Error
User with message is
Verify User message
incorrect displayed and
2 Name and displayed, Yes
user name login page is
password login page
and available
available
password again
IP, The new ip,

username, username, and
Change The Login
old password are
3 TRM Login details are Yes
password, listed in local
Details listed
new TRM login
password. details file.
4 Add SDP New The New Yes

commands command commands commands
must be shown

in SYSTEM
MONITOR
module on
clicking the are present
SDP button
under different
SDP machines
The
commands
must be shown
in SYSTEM
New
Add SLU New MONITOR
5 commands Yes
commands command module on
are present
clicking the
SLU button
under different
SLU machines
The
commands
must be shown
in SYSTEM
New
Add SGU New MONITOR
6 commands Yes
commands command module on
are present
clicking the
SGU button
under different
SGU machines
7 Delete SDP Selected The cmd’s New Yes

commands command must not be commands
from the shown in not present
dropdown SYSTEM
menu MONITOR
module on
clicking the
SDP button
under different

SDP machines
The
commands
must not be
Selected shown in
command SYSTEM New
8 Delete SLU
from the MONITOR commands Yes
commands
dropdown module on not present
menu clicking the
SLU button
under different
SLU machines
The
commands
must not be
Selected shown in
Delete command SYSTEM New
9 SGU from the MONITOR commands Yes
commands dropdown module on not present
menu clicking the
SGU button
under different
SGU machines
Mouse
click on
the SLU
button All SLU
List all SLU
10 present in machines Listed Yes
machines
the listed in menu
SYSTEM
MONITOR
module
11 List all Mouse All SDP Listed Yes

SDP click on machines
machines the SDP listed in menu
button

present in
the
SYSTEM
MONITOR
module
Mouse
click on
the SGU
List all button All SGU
12 SGU present in machines Listed Yes
machines the listed in menu
SYSTEM
MONITOR
module
Mouse
Fetch click on Statistics
statistics statistics Fetched in Statistics
13 Yes
for listed tab and GUI window in Fetched
SDPs particular Graph
SDP tab.
The
Check for
Drop a tablespace
14 Tablespace Not listed Yes
tablespace must not be
usage
listed
Check for
The datafile
datafiles Drop a
15 must not be Not listed Yes
under datafile
listed
tablespace
Manually
Check for
make an That object
16 invalid Listed Yes
object as must be listed
objects
invalid
17 Testing Search the Help file Description Yes

help file help file should provide provided
for Admin the Admin

Login Login
operation description
Table 8.2.1: Test Cases
8.3 QUALITY ASSURANCE
Documentation and the changes made to it:
A measurement Quality assurance consists of the auditing and

reporting functions of the management. The goal of the quality
assurance is to providing management with the data necessary to be
informed about product quality, thereby gaining insight and confined
that produce quality in meeting his goal. This is in ‘Umbrella Activity’
that is applied throughout the engineering process.
Software quality encompasses
 Analysis, design, coding and testing methods and tools
 Formal technical reviews that are applied during each software

engineering
 Multi tired testing strategies
 Control of software and reporting mechanism
 Procedure to ensure compliance with the software development

standards
Quality Factors
The factors that affect the quality can be categorized into two
groups.
 Factors that can be directly measured.
 Factors that can be indirectly measured.

These factors force on three important aspect of software

product.
 Its operational characteristic
 Its ability to undergo changes
 Its adaptability to new environment
Checking the reports generated by the system validates the

qualities of the output. Since only one form of output is coming out
of the user knowledge, and that is also in report form, the validating
of the report is the only way to know the quality of the system.
By giving the samples possible values to the system, and by

analyzing the reports the quality of the report generation keeps high
quality of each filtering techniques. The quality of the interface and
the techniques provided for the engineers in the tool also keeps a
good quality. The satisfaction of the engineers shows that the quality
of the tools high for the acceptance of the system for their use.
9. Results
9.1 SCREEN SHOTS

Fig 10.1.1: Screen Shot for System Monitor
In the above screen shot it displays all the health check

commands description for each SDP machines in the RTBS.

Fig 10.1.2: Screen Shot for System Monitor Output
The above screen shot shows the output of df –k command for

sdp1.

Fig 10.1.3: Screen Shot for Statistics Module Graph Display
In this it shows BHCA (Busy Hour Call Attempts) for CALL,

RECHARGE, PAYMENT, MTR and OSA.

Fig 10.1.4: Screen Shot for Statistic Module CALL’s Graph
It shows graph of calls made in a particular day.

Fig 10.1.5: Screen Shot for Alarm Monitor Module
The above screen shot shows the usage of TableSpace of

oracle database.

Fig 10.1.6: Screen Shot for Alarm Monitor Module Datafiles
It shows the Datafiles path for each Table Space in the oracle
data base.

Fig 10.1.7: Screen Shot for Alarm Monitor Invalid Objects
It shows the Invalid Objects present in the oracle database in a

GUI based Table format.

Fig 10.1.8: Screen Shot for Admin Operations
It displays the TRM machine login details and the admin can
change the login details of TRM machine.

Fig 10.1.9: Screen Shot for Add a Command
The above screen shot shows the admin can add a new
command to the tool for monitoring purpose.

Fig 10.1.10: Screen shot for delete a Command
The admin can delete an existing command which is used for

monitoring purpose using the below page.

10. Conclusion & Future Enhancement
10.1 Conclusion:
“RTB System Monitoring Tool ” is a desktop application, which

helps in monitoring the system health check. All the machines in a
RTB System can be monitored using this application. It is very user
friendly and easy to use. It provides simple functions to the user and
also provides help files if a user is finding it difficult to use. This
application eliminates multiple login to different machines and
displays the information about the remote machines in a single
window which is graphically rich.
10.2 Future Enhancement
 Need to monitor alarms in real time basis from every RTB units
(alarms will be visible for every 5 mins and get cleared if it not
present in the system)
 Capturing the system process and session consumption in SDP

and finding the locked session and highly memory utilized
process in SDP.
 Checking the Distributed file system alarms and Events (DFfile

system) from SLU, SGU and CCS where OMNI is running.
 Getting the statistics of Call registered/Abandoned/rejected in

SLU and SGU.
 Checking the batch process status and progress of each

individual batch process in SDP.

11. Annexure B
11.1 Sample Code:
// gethostfile method is used to get the \etc\host file from TRM
machine.
public void gethostfile()
try
File f = new File("D:\\java\\trmlogindetails.txt");
BufferedReader freader = new BufferedReader(new FileReader(f));
String s;
String[] st1=s.split("\t");
if(st1.length>=2)
String ip1=st1[0];
String username1=st1[1];
String password1=st1[2];
StringBuffer sb = new StringBuffer( "ftp://" );

if (username1 != null && password1 != null)
sb.append( username1 );
sb.append( ':' );
sb.append( password1 );
sb.append( '@' );
sb.append( ip1 );
sb.append( '/' );
sb.append( "/../../etc/hosts");
try
URL u=new URL(sb.toString());
URLConnection uc=u.openConnection();
BufferedReader br=new BufferedReader(new

InputStreamReader(uc.getInputStream()));
int line;
FileOutputStream f1=new FileOutputStream("D:java/hosts.txt");
while((line=br.read())!=-1)
f1.write((char)line);
br.close();
slu.setVisible(true);
sdp.setVisible(true);
sgu.setVisible(true);
catch(Exception e)

JOptionPane.showMessageDialog(SYS_MONITOR_IF, "Incorrect
Login Details", "Connect", JOptionPane.ERROR_MESSAGE);
slu.setVisible(false);
sdp.setVisible(false);
sgu.setVisible(false);
catch(Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF, "Incorrect Login Details

of TRM", "Connect", JOptionPane.ERROR_MESSAGE);
//Create menu item for each machine.
class HorizontalMenu1 extends JMenu
HorizontalMenu1(final String title)
super(title);
int c1=0,i=0;
JPopupMenu pm = getPopupMenu();
JMenuItem[] mi2=new JMenuItem[1000];
String st=title.substring(0,3);
if(st.equals("slu"))
try

File f = new File("D:\\java\\slucommands.txt");
String s;
c1=0;
if(st1.length>=2)
st4[c1]=st1[0];
c1++;
freader.close();
catch(Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF, "SLU
Command file not Found", "Menu", JOptionPane.ERROR_MESSAGE);
for(i=0;i<c1;i++)
mi2[i]=new JMenuItem(st4[i]);
mi2[i].setFont(new Font("Tahoma", Font.BOLD, 14));
pm.add(mi2[i]);
if(st.equals("sdp"))

try
File f = new File("D:\\java\\sdpcommands.txt");
String s;
c1=0;
if(st1.length>=2)
st4[c1]=st1[0];
c1++;
freader.close();
catch(Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF, "SDP
for(i=0;i<c1;i++)
pm.add(mi2[i]);

if(st.equals("sgu"))
try
File f = new File("D:\\java\\sgucommands.txt");
String s;
c1=0;
if(st1.length>=2)
st4[c1]=st1[0];
c1++;
freader.close();
catch(Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF, "SGU
for(i=0;i<c1;i++)

pm.add(mi2[i]);
for(i1=0;i1<c1;i1++)
mi2[i1].addActionListener(new ActionListener()
public void actionPerformed(ActionEvent e)
String server=null;
String user="",pass="";
String st2=title.substring(0,3);
String getcmd="";
int i;
if(st2.equals("slu"))
for(i=0;i<count;i++)
if(sluname[i].equals(title))
server=sluip[i];
user="sncpuser";
pass="sncpuser";
try
File f = new File("D:\\java\\slucommands.txt");

BufferedReader freader = new BufferedReader(new

FileReader(f));
String s;
if(st1.length>=2)
if(st1[0].equals(e.getActionCommand()))
getcmd=st1[1];
freader.close();
catch(Exception e1)
"SLU Command file not Found", "Menu", JOptionPane.ERROR_MESSAGE);
break;
if(st2.equals("sdp"))

if(sdpname[i].equals(title))
server=sdpip[i];
user="oracle8";
pass="oracle8";
try
File f = new File("D:\\java\\sdpcommands.txt");

FileReader(f));
String s;
if(st1.length>=2)
getcmd=st1[1];
freader.close();
catch(Exception e1)
"Sdp Command file not Found", "Menu", JOptionPane.ERROR_MESSAGE);

break;
if(st2.equals("sgu"))
if(sguname[i].equals(title))
server=sguip[i];
user="sguuser";
pass="sguuser";
try
File f = new File("D:\\java\\sgucommands.txt");

FileReader(f));
String s;
if(st1.length>=2)
getcmd=st1[1];
freader.close();
catch(Exception e1)
"SGU Command file not Found", "Menu", JOptionPane.ERROR_MESSAGE);
break;
displayoutput(server,getcmd,user,pass);
TA.setVisible(true);
});
pm.setLayout(new BoxLayout(pm, BoxLayout.PAGE_AXIS));
pm.setFont(new Font("Tahoma", Font.BOLD, 14));
public Dimension getMinimumSize()
return getPreferredSize();
public Dimension getMaximumSize()
return getPreferredSize();
public void setPopupMenuVisible(boolean b)
boolean isVisible = isPopupMenuVisible();
if (b != isVisible)
if ((b==true) && isShowing())
int x = 0;
int y = 0;
Container parent = getParent();
if (parent instanceof JPopupMenu)
x = 0;
y = getHeight();
else
x = getWidth();
y = 0;
getPopupMenu().show(this, x, y);
else
getPopupMenu().setVisible(false);
public void createMenuBarslu()
MB1.removeAll();
MB1.setLayout(new BoxLayout(MB1, BoxLayout.PAGE_AXIS));
for(int i=0;i<count;i++)
MB1.add(createMenu(sluname[i]));
MB1.setBorder(BorderFactory.createMatteBorder(0,0,0,0,Color.BLACK));
public void createMenuBarsdp()
MB2.removeAll();
MB2.add(createMenu(sdpname[i]));
public void createMenuBarsgu()
MB3.removeAll();
MB3.add(createMenu(sguname[i]));
public JMenu createMenu(final String title)
JMenu m = new HorizontalMenu1(title);
m.setLayout(new BoxLayout(m, BoxLayout.PAGE_AXIS));
m.setFont(new Font("Tahoma", Font.BOLD, 18));
return m;
// the method calcountandgetslu() is used to get the information of all the

slu’s present in the RTBS.
public void calcountandgetslu()
try
count=0;
File f = new File("D:\\java\\hosts.txt");
String str;
int i,j;
while ((str = freader.readLine()) != null)
char ip1[]=str.toCharArray();
char slu1[]=str.toCharArray();
if(!str.startsWith("#"))
i=str.indexOf("slu");
if(i!=-1)
j=0;int a=0,b=0;
char ipc[]=new char[20];
char sluc[]=new char[20];
while(ip1[j]!=' '&& ip1[j]!='\t')
ipc[a++]=ip1[j];
j++;
String chk=new String (ipc);
sluip[count]=chk.trim();
while(i<str.length() && slu1[i]!=' ')
sluc[b++]=slu1[i];
i++;
String chk1=new String(sluc);
sluname[count]=chk1.trim();
count++;
catch(Exception e)
JOptionPane.showMessageDialog(SYS_MONITOR_IF, "Hosts File Not

Found", "Error", JOptionPane.ERROR_MESSAGE);
IF1.setVisible(false);
\\ getDatafromSDP() method is used to get the call details from SDP
machine.
public void getDatafromSDP()
try
Connection con=null;
Class.forName("oracle.jdbc.driver.OracleDriver");
try
con=DriverManager.getConnection("jdbc:oracle:thin:@10.150.12.201:1521:sdpa","pps_o
wner","comverse");
catch(Exception e)
{}
if(con==null)
try
con=DriverManager.getConnection("jdbc:oracle:thin:@10.150.12.2011:1521:sdpb","pps_
owner","comverse");
catch(Exception e)
{}
Statement st=con.createStatement();
ResultSet rs=st.executeQuery("select count(*) from

call_history_main_a group by to_char(start_call_date_time,'hh24')");
int j=0;
while(rs.next())
int i=rs.getInt(1);
Cdata[j++]=i;
rs=st.executeQuery("select count(*) from

recharge_history_main_a group by to_char(recharge_date_time,'hh24')");
j=0;
while(rs.next())
int i=rs.getInt(1);
Rdata[j++]=i;

ps_transaction_main_a group by to_char(date_time,'hh24')");
j=0;
while(rs.next())
int i=rs.getInt(1);
Pdata[j++]=i;
rs=st.executeQuery("select count(*) from mtr_main_a

group by to_char(mod_date,'hh24')");
j=0;
while(rs.next())
int i=rs.getInt(1);
Mdata[j++]=i;

osa_history_main_a group by to_char(start_call_date_time,'hh24')");
j=0;
while(rs.next())
int i=rs.getInt(1);
Odata[j++]=i;
con.close();
catch(Exception e)
JOptionPane.showMessageDialog(ALL, "Please Unlock the SDP",

"Error", JOptionPane.ERROR_MESSAGE);
\\ the class CallsData is used to draw graph of call details
public class CallsData extends JPanel
protected void paintComponent(Graphics g)
//super.paintComponent(g);
Graphics2D g2 = (Graphics2D)g;
g2.setRenderingHint(RenderingHints.KEY_ANTIALIASING,RenderingHints.VALUE_ANT
IALIAS_ON);
int w = getWidth();
int h = getHeight();
// Draw ordinate.
g2.draw(new Line2D.Double(PAD+PAD, PAD+PAD, PAD+PAD, h-

(PAD+PAD)));
// Draw abcissa.
g2.draw(new Line2D.Double(PAD+PAD, h-(PAD+PAD), w-(PAD+PAD), h-

(PAD+PAD)));
// Draw labels.
Font font = g2.getFont();
FontRenderContext frc = g2.getFontRenderContext();
LineMetrics lm = font.getLineMetrics("0", frc);
float sh = lm.getAscent() + lm.getDescent();
// Ordinate label.
String s = "CALLS";
float sy = PAD + ((h - 2*PAD) - s.length()*sh)/2 + lm.getAscent();
for(int i = 0; i < s.length(); i++)
String letter = String.valueOf(s.charAt(i));
float sw = (float)font.getStringBounds(letter, frc).getWidth();
float sx = (PAD - sw)/2;
g2.drawString(letter, sx, sy);
sy += sh;
// Abcissa label.
s = "HOURS";
sy = h - PAD + (PAD - sh)/2 + lm.getAscent();
float sw = (float)font.getStringBounds(s, frc).getWidth();
float sx = (w - sw)/2;
g2.drawString(s, sx, sy);
// Draw lines.
float xInc = (float)(w - 2*(PAD+PAD))/(Cdata.length-1);
float scale = (float)(h - 2*(PAD+PAD))/getMax();
g2.setPaint(Color.green.darker());
for(int i = 0; i < Cdata.length-2; i++)
double x1 = PAD+PAD + i*xInc;
double y1 = h - (PAD+PAD) - scale*Cdata[i];
double x2 = PAD+PAD + (i+1)*xInc;
double y2 = h - (PAD+PAD) - scale*Cdata[i+1];
g2.draw(new Line2D.Double(x1, y1, x2, y2));
// Mark data points.
g2.setPaint(Color.red);
String s1;
for(int i = 0; i < Cdata.length-1; i++)
float x = PAD+PAD + i*xInc;
float y = h - (PAD+PAD) - scale*Cdata[i];
g2.fill(new Ellipse2D.Double(x-2, y-2, 4, 4));
if(g1==1)
s1=String.valueOf(Cdata[i]);
g2.drawString(s1, x-2, y-2);
if(g1==1)
for(int i = 0; i < 24; i++)
float x = PAD+PAD + i*xInc;
s1=String.valueOf(data1[i]);
g2.drawString(s1, x-2, h-(PAD+5));
int m=getMax();
int n=m/10;
s1=String.valueOf(00);
//g2.drawString(s1, 15, h-PAD);
int y1=(h-(PAD+PAD))/10;
int y2=h-(PAD);
for(int i=n;i<m-10;i=i+n)
s1=String.valueOf(i);
g2.drawString(s1, 15, y2=y2-y1);
s1=String.valueOf(m);
g2.drawString(s1, 15, 24+24);
private int getMax()
int max = -Integer.MAX_VALUE;
for(int i = 0; i < Cdata.length; i++)
if(Cdata[i] > max)
max = Cdata[i];
return max;
\\ the below code is used to display the alarm monitor module functions
public class JT1 extends JFrame
Object headerval[]={"TabelSpace","Used (%)"};
Object data[][]=new Object[100][100];
public void getvalueofTabelSpace()
try
try
con=DriverManager.getConnection("jdbc:oracle:thin:@10.150.12.120:1521:sdpa","sys","
sys518");
catch(Exception e)
{}
if(con==null)
try
con=DriverManager.getConnection("jdbc:oracle:thin:@10.150.12.2011:1521:sdpb","sys",
"sys518");
catch(Exception e)
{}
ResultSet rs=st.executeQuery("select
a.TABLESPACE_NAME,a.BYTES bytes_used,b.BYTES
bytes_free,b.largest,round(((a.BYTES-b.BYTES)/a.BYTES)*100,2) percent_used from
(select TABLESPACE_NAME,sum(BYTES) BYTES from dba_data_files group by
TABLESPACE_NAME ) a,(select TABLESPACE_NAME, sum(BYTES) BYTES
,max(BYTES) largest from dba_free_space group by TABLESPACE_NAME ) b where
a.TABLESPACE_NAME=b.TABLESPACE_NAME order by ((a.BYTES-
b.BYTES)/a.BYTES) desc");
int i=0;
String[] str=new String[1000];
int[] val = new int[1000];
float[] fval=new float[1000];
while(rs.next())
str[i]=rs.getString(1);
val[i]=rs.getInt(5);
fval[i]=rs.getFloat(5);
i++;
int l=i;
con.close();
for(i=0;i<l;i++)
for(int j=0;j<2;j++)
if(j==0)
data[i][j]=str[i];
else
data[i][j]=createBar(val[i],fval[i]);
catch(Exception e)
JOptionPane.showMessageDialog(TabelSpace_IF, "Please Unlock

the SDP", "Error", JOptionPane.ERROR_MESSAGE);
public JT1()
UIManager.put("ProgressBar.selectionBackground", new
ColorUIResource(Color.BLACK));
UIManager.put("ProgressBar.selectionForeground", new
ColorUIResource(Color.BLACK));
getvalueofTabelSpace();
init();
public JProgressBar createBar(int percentDone,float f)
JProgressBar progressBar = new JProgressBar(0, 100);
progressBar.setValue(percentDone);
progressBar.setStringPainted(true);
progressBar.setString(Float.toString(f));
progressBar.setFont(new Font("Arial", Font.BOLD, 14));
if(f<70)
progressBar.setForeground(Color.GREEN);
if(f>70 && f<90)
progressBar.setForeground(Color.ORANGE);
if(f>90)
progressBar.setForeground(Color.RED);
return progressBar;
private void init()
try
DefaultTableModel model = new

DefaultTableModel(data,headerval)
public boolean isCellEditable(int row, int column)
return false;
};
JT.setModel(model);
JT.getColumn("Used (%)").setCellRenderer(new ProgRenderer());
JT.getTableHeader().setFont(new Font("Verdana", Font.BOLD,

18));
JTableHeader anHeader = JT.getTableHeader();
anHeader.setForeground(new Color(0).BLACK);
anHeader.setAlignmentX(50);
anHeader.setAlignmentY(50);
((JLabel)anHeader.getDefaultRenderer()).setHorizontalAlignment(JLabel.CENTER);
class ProgRenderer implements TableCellRenderer
public Component getTableCellRendererComponent(JTable table, Object

value, boolean isSelected, boolean hasFocus, int row, int column)
return (JProgressBar)value;
Object headerval[]={"TabelSpace","File Name"};
public void getvalueofDataFiles()
try
try
sys518");
catch(Exception e)
{}
if(con==null)
try
"sys518");
tablespace_name,file_name from dba_data_files");
int i=0;
String[] val = new String[1000];
while(rs.next())
val[i]=rs.getString(2);
i++;
int l=i;
con.close();
for(i=0;i<l;i++)
if(j==0)
data[i][j]=str[i];
else
data[i][j]=val[i];
catch(Exception e)
JOptionPane.showMessageDialog(DataFiles_IF, "Please Unlock the

SDP", "Error", JOptionPane.ERROR_MESSAGE);
public JT2()
getvalueofDataFiles();
init();
private void init()
try

return false;
};
JT1.setModel(model);
JT1.getTableHeader().setFont(new Font("Verdana", Font.BOLD,

18));
JTableHeader anHeader = JT1.getTableHeader();
Object headerval[]={"Object Name","Object Type"};
public void getvalueofInvalidObjects()
try
try
sys518");
catch(Exception e)
{}
if(con==null)
try
"sys518");
object_name,object_type from all_objects where status like 'INVALID'");
int i=0;
String[] val = new String[1000];
while(rs.next())
val[i]=rs.getString(2);
i++;
int l=i;
con.close();
for(i=0;i<l;i++)
if(j==0)
data[i][j]=str[i];
else
data[i][j]=val[i];
catch(Exception e)
JOptionPane.showMessageDialog(InvalidObjects_IF, "Please Unlock

the SDP", "Error", JOptionPane.ERROR_MESSAGE);
public JT3( )
getvalueofInvalidObjects();
init();
private void init()
try

return false;
};
JT2.setModel(model);
JT2.getTableHeader().setFont(new Font("Verdana", Font.BOLD,

18));
JTableHeader anHeader = JT2.getTableHeader();
12. Bibliography
[1]. Herbert Schildt, “Java the Complete reference”, Seventh Edition,

McGraw-Hill Professional, 2006
[2]. Kathy Sierra and Bert Bates, “Head First Java”, First Edition, Oreilly &
Associates Inc, 2003
[3]. Marc Loy, Robert Eckstein, “Java Swings”, Second Edition, Oreilly
& Associates Inc, 2002
[4]. Kim Topley, “Core Swing Advanced Programming”, First Edition,

Prentice-Hall. Inc, 1999
[5]. Elliotte Rusty Harold, “Java Network Programming”, Third Edition,

Oreilly & Associates Inc, 2004
[6]. Real Time Billing System Monitoring Tool Architecture and Call Flow
Details
[7]. Service Manual for RTBS.

Sample Report

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Sample Report

Caricato da

Copyright:

Formati disponibili

Real Time Billing System Monitoring Tool

1.1 General Information

System. The project is used to monitor the different units like

application provides information about all the machines in a

Graphical User Interface in an efficient and easy way.

The user does not need to perform multiple login to the

different machine in the Real Time Billing System to check their

status. All the information is presented in the single window of the

The application has four modules

1.1.1 SYSTEM MONITOR

This module is used to fetch information about different

disk usage, processes running, memory utilization, disk capacity etc.

Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 1

We log onto a machine called TRM (TRilogue Manager) from

SGU machines available.

TRilogue Manager (TRM) holds the BIP (Billing interface

Package) that Provides Comprehensive, configured billing

information to the remote Station. It is Integrated Alarm Package

(IAP) that monitors the SN platform, Host Interface for Administration

(HIA) is a software package for external host provisioning of the

Service Logic Unit (SLU) is the RTBS controller entity that

the resources of these components.

Service Data Point (SDP) is a powerful database server system

for the Comverse line of IN value added services. It uses advanced

technology to deliver the best possible mass data server for IN

services. Provides high capacity storage and works in Load Sharing

Signaling Gateway Unit (SGU) is internal components of

signaling and messaging. It Interfaces between IN to the signaling

links of the telephone network. It is responsible for processing SS7

Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 2

After fetching the IP addresses and names of different

machines using file handling, TELNET is used to run different

commands in the remote machine.

This Module is design to show BHCA (Busy Hour Call

BHCA is usually used when planning telephoning switching

1.1.3 ALRAM MONITOR

This module contains three sub modules, they are

Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 3

1.1.3.1 Table Space:

A table space is a logical storage unit within an Oracle

Each table, index and so on that is stored in an Oracle

In Table Space module it shows the Table Spaces and

1.1.3.2 Data Files:

A table space in an Oracle database consists of one or more

Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 4

In this module we have to display the data files of each table

1.1.3.3 Invalid Objects:

Some types of schema objects reference other objects. For

Oracle Database provides an automatic mechanism to ensure

It is important to be aware of changes that can invalidate

In a typical running application, you would not expect to see

Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 5

patched or upgraded using a patch script or ad-hoc DDL statements.

This module contains 2 sub modules, they are

1.1.4.1 Admin Login:

by entering the username and password. If username and password

contains username and password is stored in the local machine.

1.1.4.2 Admin Operations:

This module is having 4 sections.

In this section the admin can change the TRM IP address,

Sir MVIT / Bangalore /1MV08MCA12 / 6th Sem MCA / June 2011 6

In this section we can add commands and we can delete

is stored in the local machine. It contains command description and