ABSTRACT

Cable Operator Management System is integrated and automation software for cable operators.
Cable operators will distribute TV channels to their customers for that they charge some money
monthly.

To maintain their customers and number of users this software provides automation. In this
COM System they can main their staff member’s details and their customer details. By using
this COM System they can divide their areas macro parts to micro parts. By using this system
they can meet their business requirements. Cable Operators once they divided their areas into
micro parts then they can assign their staff members to take care about their micro part areas.
Cable operators they can maintain their staff members like collection boys, helpers and
technicians. All the collection boys will have user id and password. At the end of the every day
they will login to the COM System they will feed their collection details and remarks.
By using this COM System they can know about their equipments located on which areas. How
many active / non active customers are there? all these details they can view it by using the
reports. MIS reports were generated for the month of collections, expenses, pending amount,
complaints area wise and date wise, month wise.
 CONTENTS
1. INTRODUCTION

2. HARDWARE AND SOFWARE REQUIREMNTS

2.1 HARDWARE SPECIFICATIONS

2.2 SOFTWARE SPECIFICATIONS

3. LITERATURE SURVEY

3.1 OVERVIEW OF THE .NET FRAMEWORK

3.2 MICROSOFT VISUAL STUDIO 2005

3.3 DATABASE OBJECTS

3.4 ADO.NET

4. SOFTWARE DESIGN

4.1 DATA FLOW DIAGRAMS

4.2 FLOW CHARTS

4.3 DATABASE DESIGN

4.3.1 ER DIAGRAMS

4.3.2 TABLE DESCRIPTION

5. CODING

6. TESTING

7. OUTPUT SCREENS

8. CONCLUSION

9. FURTHER ENHANCEMENT

10. BIBLIOGRAPHY
1. INTRODUCTION

Cable Operator Management System is integrated and automation software for

cable operators. Cable operators will provide distributed channels to their customers. In

those distributed channels some channels are regular channels and few channels are

paid channels.

To maintain their customers and number of users this software provides

automation. In this COM System they can main their staff member’s details and their

customer details. By using this COM System they can divide their areas macro parts to

micro parts. By using this system they can meet their business requirements. Cable

Operators once they divided their areas into micro parts then they can assign their staff

members to take care about their micro part areas.

Cable operators they can maintain their staff members like collection boys,

helpers and technicians. All the collection boys will have user id and password. At the

end of the every day they will login to the COM System they will feed their collection

details and remarks.

Cable operators can configure this COM system centrally and they can distribute

their areas. All the collection boys will update their information in the system. So that

Cable operators will know about their particular area collection on day wise, weekly

wise. So that cable operators can provide the better service to their customers.

By using this COM System they can know about their equipments located on

which areas. How many active / non active customers are there? all these details they

can about it by using the reports. MIS reports were generated for the month of

collections, expenses, pending amount, complaints area wise and date wise, month

wise.
2. HARDWARE AND SOFTWARE REQURIMENTS

2.1. HARDWARE SPECIFICATIONS

PROCESSOR : P3 OR HIGHER

RAM : 512MB

HARD DISK : 20GB

2.2. SOFTWARE SPECIFICATIONS

FRONT END : VISUAL STUDIO 2005

BACK END : MS Access

OPERATING SYSTEM S : WINDOWS 2003 SERVER / XP

3. LITERATURE SURVEY

3.1 Overview of the .NET Framework

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. The .NET

Framework is designed to fulfill the following objectives

i. To provide a consistent object-oriented programming environment whether

object code is stored and executed locally, executed locally but Internet-

distributed, or executed remotely.

ii. To provide a code-execution environment that minimizes software

deployment and versioning conflicts.

iii. To provide a code-execution environment that guarantees safe execution of

code, including code created by an unknown or semi-trusted third party.

iv. To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

v. To make the developer experience consistent across widely varying types of

applications, such as Windows-based applications and Web-based

applications.

vi. To build all communication on industry standards to ensure that code based

on the .NET Framework can integrate with any other code.

The .NET Framework has two main components: the common language runtime and

the .NET Framework class library.

3.1.1 Features of the Common Language Runtime

The common language runtime is the foundation of the .NET Framework. The common

language runtime manages memory, thread execution, code execution, code safety

verification, compilation, and other system services. These features are intrinsic to the

managed code that runs on the common language runtime. The runtime also

accelerates developer productivity. For example, programmers can write applications

in their development language of choice, yet take full advantage of the runtime, the

class library, and components written in other languages by other developers.

3.1.2 Features of the Class Library

The .NET Framework class library is a collection of reusable types that tightly integrate

with the common language runtime. The class library is object oriented, providing

types from which your own managed code can derive functionality. This not only

makes the .NET Framework types easy to use, but also reduces the time associated with

learning new features of the .NET Framework. In addition, third-party components can

integrate seamlessly with classes in the .NET Framework.

3.2 VISUAL BASIC .NET

The Microsoft Visual Basic is a Rapid Application development Tool (RAD) that is very

useful for GUI based development. Visual Basic is the fastest and easiest way to

create the applications for Microsoft Windows. The “Visual” part refers to the method

used to create the graphical user interface (GUI). Rather than writing numerous lines of

code, we can simply drag and drop built-in object onto the forms on screen. The “Basic”

part refers to the BASIC (Beginners All Purpose Symbolic Code) language, used by

more programmers than any other language in the history of computing. Visual Basic is

evaluated from the original BASIC language and now contains several hundred

statements, functions, and keywords, many of which relate directly into the Windows

GUI.

Data access feature allows you to create database, front-end applications, and scalable

server-side components for most popular database formats, including Microsoft

SQL server and other enterprise - level database.ActiveX TM technologies allow you

to use the functionality provided by the applications, such as Microsoft Word

processor, Microsoft Excel spreadsheet, and other windows applications. You can even

automate applications and objects created using the Professional or Enterprise editions

of Visual Basic.
It has several types of primary Controls and ActiveX controls, which gives more

flexibility for designing forms. It facilities to created own user define ActiveX controls

for effective Design of Forms. Visual Basic supports object oriented programming. By

this we can create classes, objects with all features of OOP. Like information Hiding,

Data Encapsulation, Inheritance and Polymorphism. It gives more facility for the

database programming with Data Controls, Data Access Objects (DAO), Remote Data

Objects (RDO), and Active Data Object (ADO) and several data bound control

like DBcombo, DBlist and DBgrid controls which makes application simple way to

access several database through open database connectivity (ODBC).

3.4 ADO.NET

The ADO.NET components have been designed to factor data access from data

manipulation. There are two central components of ADO.NET that accomplish this: the

Dataset, and the .NET data provider, which is a set of components including the

Connection, Command, Data Reader, and Data Adapter objects.

The ADO.NET Dataset is the core component of the disconnected architecture of

ADO.NET. The Dataset is explicitly designed for data access independent of any data

source. As a result it can be used with multiple and differing data sources, used with

XML data, or used to manage data local to the application. The Dataset contains a

collection of one or more Data Table objects made up of rows and columns of data, as

well as primary key, foreign key, constraint, and relation information about the data in

the Data Table objects.

The other core element of the ADO.NET architecture is the . NET data provider, whose

components are explicitly designed for data manipulation and fast, forward-only, read-

only access to data. The Connection object provides connectivity to a data source. The

Command object enables access to database commands to return data, modify data, run
stored procedures, and send or retrieve parameter information. The Data Reader

provides a high-performance stream of data from the data source. Finally, the Data

Adapter provides the bridge between the Dataset object and the data source. The Data

Adapter uses Command objects to execute SQL commands at the data source to both

load the Dataset with data, and reconcile changes made to the data in the Dataset back

to the data source.

.NET Framework Class Library

The .NET Framework class library is a collection of reusable types

that tightly integrate with the common language runtime. The class

library is object oriented, providing types from which your own

managed code can derive functionality. This not only makes

the .NET Framework types easy to use, but also reduces the time

associated with learning new

features of the .NET Framework. In addition, third-party

components can integrate seamlessly with classes in the .NET

Framework.

For example, the .NET Framework collection classes implement a

set of interfaces that you can use to develop your own collection
classes. Your collection classes will blend seamlessly with the

classes in the .NET Framework.

As you would expect from an object-oriented class library, the .NET

Framework types enable you to accomplish a range of common

programming tasks, including tasks such as string management,

data collection, database connectivity, and file access. In addition

to these common tasks, the class library includes types that

support a variety of specialized development scenarios. For

example, you can use the .NET Framework to develop the following

types of applications and services:

 Console applications.
 Scripted or hosted applications.
 Windows GUI applications (Windows Forms).
 ASP.NET applications.
 XML Web services.
 Windows services.

For example, the Windows Forms classes are a comprehensive set

of reusable types that vastly simplify Windows GUI development. If

you write an ASP.NET Web Form application, you can use the Web

Forms classes.
Client Application Development

Client applications are the closest to a traditional style of

application in Windows-based programming. These are the types of

applications that display windows or forms on the desktop,

enabling a user to perform a task. Client applications include

applications such as word processors and spreadsheets, as well as

custom business applications such as data-entry tools, reporting

tools, and so on. Client applications usually employ windows,

menus, buttons, and other GUI elements, and they likely access

local resources such as the file system and peripherals such as

printers.

Another kind of client application is the traditional ActiveX control

(now replaced by the managed Windows Forms control) deployed

over the Internet as a Web page. This application is much like other

client applications: it is executed natively, has access to local

resources, and includes graphical elements.

In the past, developers created such applications using C/C++ in

conjunction with the Microsoft Foundation Classes (MFC) or with a

rapid application development (RAD) environment such as

Microsoft® Visual Basic®. The .NET Framework incorporates

aspects of these existing products into a single, consistent

development environment that drastically simplifies the

development of client applications.

The Windows Forms classes contained in the .NET Framework are

designed to be used for GUI development. You can easily create

command windows, buttons, menus, toolbars, and other screen

elements with the flexibility necessary to accommodate shifting

business needs.

For example, the .NET Framework provides simple properties to

adjust visual attributes associated with forms. In some cases the

underlying operating system does not support changing these

attributes directly, and in these cases the .NET Framework

automatically recreates the forms. This is one of many ways in

which the .NET Framework integrates the developer interface,

making coding simpler and more consistent.

Unlike ActiveX controls, Windows Forms controls have semi-trusted

access to a user's computer. This means that binary or natively

executing code can access some of the resources on the user's

system (such as GUI elements and limited file access) without being

able to access or compromise other resources. Because of code

access security, many applications that once needed to be installed

on a user's system can now be safely deployed through the Web.

Your applications can implement the features of a local application

while being deployed like a Web page.

 4. SOFTWARE REQUIREMENT ANALYSIS

4.1 PRESENT SYSTEM

DISADVANTAGES

Cable operators they are maintaining their accounts and customers details manually.

By doing manually their business activity details some times lot of mistakes will occur

or misusage chances are there in their business. Difficult to maintain their monthly

collection details like who were paid and who were not paid. Some times they might

not know about their new customers and about their equipments and assets. They used

to maintain their customers details in the way of monthly collection cards. If they loose

their customer card they may loose about that particular customer track.

If they need to check their customer’s dues and collection they have to check it

manually by checking the collection cards. They don’t have any particular reports if

they need they have to do on paper manually.

4.4 PROPOSED SYSTEM

Cable Operator Management System is integrated and automation software for

cable operators. Cable operators will provide distributed channels to their customers. In

those distributed channels some channels are regular channels and few channels are

paid channels.
 To maintain their customers and number of users this software provides

automation. In this COM System they can main their staff member’s details and their

customer details. By using this COM System they can divide their areas macro parts to

micro parts. By using this system they can meet their business requirements. Cable

Operators once they divided their areas into micro parts then they can assign their staff

members to take care about their micro part areas.

Cable operators they can maintain their staff members like collection boys,

helpers and technicians. All the collection boys will have user id and password. At the

end of the every day they will login to the COM System they will feed their collection

details and remarks.

Cable operators can configure this COM system centrally and they can distribute

their areas. All the collection boys will update their information from the branch offices.

So that Cable operators will know about their particular area collection on day wise,

weekly wise. Once they configured this centrally if any customer made a call regarding

new connection or complaint about the connection they can forward that message to

the particular branch office regarding connection or complaints. So that cable operators

can provide the better service to their customers.

By using this COM System they can know about their equipments located on

which areas. How many active / non active customers are there? all these details they

can about it by using the reports. MIS reports were generated for the month of

collections, expenses, pending amount, complaints area wise and date wise, month

wise.

4.5 MODULE DIVISION

 COM System (COMS) is an integrated software deals with Cable

Operators. Helps the Cable Operators manage their customers and provides the

information about various channels. It makes easy to all operations of the Cable

Operators and accurate.

Masters :

The information specified in the Master is regarded static, in the sense that it is

“Permanent” or non-changing or stable. The updates are infrequent and may be

regarded as permanently stored in the Database. The Master Group has functionality to

View / Change.

The master pages will have access to administrator only.

Area Master --– Cable Operators they will divide their areas macro parts to micro parts

like huge area will be divided in to small areas, divisions. In this module admin will

add areas and code numbers.

Employee Master -- Admin will add the staff and will provide the privileges as per the

staff designation. All the staff members cannot access all the modules. He can add or

delete the staff accounts.

Customer Master -- Admin will add the new customers those who come in their areas

and take new connection. Admin can add or delete the customers and they can view

the entire customers list in area wise.

Monthly Charges -- Admin will add or modify the monthly charges depends on the

areas. Some areas they will charge more and some areas less depends on the channels

they provide.

Transaction:

Transactions deal with dynamic or transient data.

Transactions do not affect the MASTER Data.

The TRANSACTION Group of functionality is as follows:

1. Collection Screen -- In this module Cable operators will generate the monthly

wise collection statement for their particular areas and customer wise. They can

generate the date to date collection statements. Staff wise collection statements

and area wise statements will generate by using this module.

2. Customer Status – Customer can take connection and remove connection due to

various reasons at any point of time. Once is disconnected we make him inactive

. We can change customer status any point of time.

Reports Module

In this module we can generate the various MIS Reports to keep track of the

revenue, customer statistics area wise, month wise, during the days and year wise etc.,

1. Area List

2. Employee List

3. Customer List

4. Collections Area wise

5. Total Collections

6. Collections between Dates

7. Customer A/c

UML
 7.TESTING

BLACK BOX TESTING

In clearing house across various modules this testing was performed to check the

following.

a) Establishing communication with the database for handling request and response.

b) Verification of OLE-DB providers(ADO) in functionality

c) Parameters passing and report generation used from the application with crystal

report.

WHITE BOX TESTING

All the statements included in the code across various modules were tested to find none

of the statements where overlooked or skipped from execution. This enabled isolating

of errors that would have otherwise occurred and would have resulted in abnormal

terminal or exceptions thrown. The test was corely tested in patient and responsibility,

Insured party, ailments, procedures and applied payment modules.

STRING TESTING
The applications was tested for inputs pertaining to patient data, responsible party,

insured party for strings such as name, relation, employ information, policy details,

insurance company details, claim centre information and attorney data physician,

reference physician information were tested for the following

a. null data

b. string length

c. data format

d. alpha numeric characters

In addition, numeric inputs were tested for invalid characters, invalid data format,

size of the input data and the data type being handled.

UNIT TESTING

Module pertaining to patient, responsible party, and soon were tested individually to

check if the system performed the business logic or processors for the inputs provided

and effective communication with the data base, the units were tested to check whether

the data were reflected and updated across other tables that were used by other

modules. The core modules

1. Responsible party and patient

2. Insured party

3. Ailments

4. Procedures

5. Applied payments

Were tested for the availability of data from other modules.

All the units were found to execute independently and had appropriate communication

with the data base. Dependent modules were tested with static data and were found to

execute as per SRS.

INTEGRATED TESTING

All the units were combined from a menu driven application which then provided for

integration with other modules the following well tested.

1. Message passing and communication between the modules

2. Data usage and synchronization

3. Flow of control using top-down testing confirming appropriate return of control as

well as associated usability features.

SYSTEM TESTING

The system as a whole along with required external resources was executed to check

the dependencies, exception across the unavailability of the resources pertaining to the

network connection, OLEDB providers, authentication of database and database it self.

DSN less connection and its effective communication for database was found to be as

per their SRS.

MUTATION TESTING

All fields across every module were tested rigorously with inputs that were

intentionally provided with wrong data. This testing resolves bugs and errors through

exception handling. That was a result of any kind of invalid data.

DATABASE TESTING

Database testing is done to uncover the errors which occur as a

consequence of fetching large equities of data from the database, extracting
relevant data from the database, accessing the database using several
queries etc,

In this project, I have tested the application for database errors in

following areas.
o While converting the user request into a database query
o While fetching dynamic content to the web pages.
o While opening and closing the active connections to the
database
o While presenting the raw data fetched from database in a
formatted HTML output.
o Communication between the web application and the remote
database.

USER INTERFACE TESTING

All the interfaces that have been designed are reviewed whether they meet the

customer requirement or not. While testing all interfaces I have verified for errors as

follows.
o Errors related to specific interface mechanisms for example proper
execution of all menu links that are provided in each web page
o Errors related to all semantics of navigation and web application
functionally that is provided in each web page.
o Errors in consistency related to different aspects of the interfaces like
font style, color, size, screen background color etc.,
o Errors in viewing the interfaces in different web browsers like Microsoft
internet explorer, Mozilla firefox etc.,
INTERFACE MECHANISM TESTING

When a user interacts with a web application, the interaction occurs

through one or more mechanisms which are called interface mechanisms.
Testing done within theses mechanisms is the interface mechanism testing.
This testing is done in following areas.
Links:
Each navigation link is tested to ensure that appropriate web page is
linked or not. I have listed all the links in each form to test whether each
link is connecting the appropriate page or not.

Forms:
Testing forms has been done at two different levels i.e. at minimum
level and at more targeted level. At minimum level I have tested for:
o Whether labels been correctly defined for fields or not.
o Whether server is receiving all the information contained in the form
and no data are lost in the transmission between client and server.
o Whether appropriate default values are available when the user does
not select any item in the selection box.
o Whether scripts that perform data validation from the client-side are
working properly or not.
At more targeted level I have tested for:
o Whether text fields have proper width to enter data.
o Whether text fields are allowing string length more than specified
length.
o Whether tab order among different controls is in required order or not.
Client Side Scripting:
Each and every function written in scripting has been tested by Black
Box Testing.
I have combined the forms testing with this client-side script testing,
because input for scripting is provided from forms. Some methods of
scripting will be performed in some particular browsers and in others not. So
I have also performed compatibility testing to ensure that the scripting
functions will work properly in all browsers.

USABILITY TESTS
In this testing I have verified up to, which level that, users can
interact with the system effectively. Tests are designed to determine the
degree to which the web application interface makes users easy to work
with. I have designed test case so that usability testing can be verified at
different levels:
o Usability test has been performed on each and every individual
interface i.e. forms.
o Usability test has been performed on total web page with related client
side scripting functions.
o Usability test has been performed on total web application.

COMPATIBILITY TESTS

As this is a web application, it should run on different environments

like different computer architectures, operating systems, browsers and
network connection speeds.
As different computing configurations can result in difference in client
side scripting speeds and display resolution, operating system variance may
cause web application processing issues.

Different browsers produce slightly different result as we expected, in

some cases this results may not be a problem but in some cases there will
be serious errors.
To perform these testing strategies first we have prepared what are all
the client side functions that encounter problems with different
compatibilities. In essence of those we have tested by identifying different
computing platform, typical display devices, the operating systems
supported on the platform, the browsers that are available with me.

SCREEN SHOTS
9. CONCLUSION

10. FUTURE ENHANCEMENTS

This project can be further enhanced to provide greater flexibility and

performance with certain modifications whenever necessary.

11. BIBILIOGRAPHY

1. Visual Studio 2005 Black Book - Rob Thayer

5. Mastering Database Programming with Visual Basic 6 -Evangelos Petroutsos

6. Software Engineering - Pressman

7. System Analysis and Design - James A.Senn

8. An Introduction to Database Management System - C.J.Date

9. ORACLE Administration - Manual, Oracle Press

10. ORACLE SQL Reference Manual -Manual, Oracle Press