coms document

8/12/2019 COMS Document

1/37

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 members details and their customer details. y using

this COM System they can divide their areas macro parts to micro parts. y using this system

they can meet their business re!uirements. Cable Operators once they divided their areas into

micro parts then they can assign their staff members to ta"e care about their micro part areas.

Cable operators they can maintain their staff members li"e collection boys# helpers and

technicians. $ll the collection boys will have user id and password. $t the end of the every day

they will login to the COM System they will feed their collection details and remar"s.y using this COM System they can "now about their e!uipments located on which areas. %ow

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# e(penses# pending amount#

complaints area wise and date wise# month wise.

CONTENTS

1. INTRODUCTION


2/37

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 DESIN

4.1 DATA FLOW DIARAMS

4.2 FLOW CHARTS

4.3 DATABASE DESIN

4.3.1 ER DIARAMS

4.3.2 TABLE DESCRIPTION

5. CODIN

!. TESTIN

". OUTPUT SCREENS

#. CONCLUSION

$. FURTHER ENHANCEMENT

10. BIBLIORAPHY

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 members details and their customer details. y


3/37

using this COM System they can divide their areas macro parts to micro parts. y using this

system they can meet their business re!uirements. Cable Operators once they divided their areas

into micro parts then they can assign their staff members to ta"e care about their micro part

areas.



they will login to the COM System they will feed their collection details and remar"s.

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

areas. $ll the collection boys will update their information in the system. So that Cable operators

will "now about their particular area collection on day wise# wee"ly wise. So that cable

operators can provide the better service to their customers.

y using this COM System they can "now about their e!uipments located on which

areas. %ow 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# e(penses# pending

amount# complaints area wise and date wise# month wise.

2. HARDWARE AND SOFTWARE REQURIMENTS

2.1. HARDWARE SPECIFICATIONS)*OC+SSO* , )- O* %I%+*

*$M , /01M

%$*2 2IS3 , 14


4/37

2.2. SOFTWARE SPECIFICATIONS

5*O6T +62 , VIS7$8 ST72IO 144/

$C3 +62 , MS $ccess

O)+*$TI6 S9ST+M S , :I62O:S 144- S+*V+* & ;)

-. 8IT+*$T7*+ S7*V+9

-.0 Overview of the .6+T 5ramewor"

The .6+T 5ramewor" is a new computing platform that simplifies application development in

the highly distributed environment of the Internet. The .6+T 5ramewor" is designed to fulfill

the following ob


5/37

iv. To provide a code=e(ecution environment that eliminates the performance problems

of scripted or interpreted environments.

v. To ma"e the developer e(perience consistent across widely varying types of

applications# such as :indows=based applications and :eb=based applications.

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

.6+T 5ramewor" can integrate with any other code.

The .6+T 5ramewor" has two main components, the common language runtime and the .6+T

5ramewor" class library.


6/37

3.1.1 F%&'()%* +, '-% C++/ L&/(&% R(/'%

The common language runtime is the foundation of the .6+T 5ramewor". The common

language runtime manages memory# thread e(ecution# code e(ecution# 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. 5or

e(ample# programmers can write applications in their development language of choice# yet ta"e

full advantage of the runtime# the class library# and components written in other languages by

other developers.

3.1.2 F%&'()%* +, '-% C&** L)&)

The .6+T 5ramewor" class library is a collection of reusable types that tightly integrate with the

common language runtime. The class library is ob


7/37

and other windows applications. 9ou can even automate applications and ob


8/37

commands at the data source to both load the D&'&*%'with data# and reconcile changes made to

the data in the D&'&*%'bac" to the data source.

.NET Framework Class Library

The .6+T 5ramewor" class library is a collection of reusable types that tightly

integrate with the common language runtime. The class library is ob


9/37

support a variety of speciali>ed development scenarios. 5or e(ample# you can use

the .6+T 5ramewor" to develop the following types of applications and services,

Console applications.

Scripted or hosted applications.

:indows 7I applications ?:indows 5orms@.

$S).6+T applications.

;M8 :eb services.

:indows services.

5or e(ample# the :indows 5orms classes are a comprehensive set of reusable

types that vastly simplify :indows 7I development. If you write an $S).6+T

:eb 5orm application# you can use the :eb 5orms classes.

Client Application Development

Client applications are the closest to a traditional style of application in :indows=

based programming. These are the types of applications that display windows or

forms on the des"top# enabling a user to perform a tas". 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 7I elements# and they li"ely

access local resources such as the file system and peripherals such as printers.


10/37

$nother "ind of client application is the traditional $ctive; control ?now replaced

by the managed :indows 5orms control@ deployed over the Internet as a :eb

page. This application is much li"e other client applications, it is e(ecuted

natively# has access to local resources# and includes graphical elements.

In the past# developers created such applications using C&CEE in con


11/37

5ramewor" automatically recreates the forms. This is one of many ways in which

the .6+T 5ramewor" integrates the developer interface# ma"ing coding simpler

and more consistent.

7nli"e $ctive; controls# :indows 5orms controls have semi=trusted access to a

userGs computer. This means that binary or natively e(ecuting code can access

some of the resources on the userGs system ?such as 7I elements and limited file

access@ without being able to access or compromise other resources. ecause of

code access security# many applications that once needed to be installed on a userGs

system can now be safely deployed through the :eb. 9our applications can

implement the features of a local application while being deployed li"e a :eb

page.


12/37

4. SOFTWARE REQUIREMENT ANALYSIS

D.0 )*+S+6T S9ST+M

DISADVANTAES

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

manually their business activity details some times lot of mista"es will occur or misusage

chances are there in their business. 2ifficult to maintain their monthly collection details li"e who

were paid and who were not paid. Some times they might not "now about their new customers

and about their e!uipments 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 trac".

If they need to chec" their customers dues and collection they have to chec" it manually by

chec"ing the collection cards. They dont 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 members details and their customer details. y

using this COM System they can divide their areas macro parts to micro parts. y using this

system they can meet their business re!uirements. Cable Operators once they divided their areas

into micro parts then they can assign their staff members to ta"e care about their micro part

areas.


13/37



they will login to the COM System they will feed their collection details and remar"s.

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

areas. $ll the collection boys will update their information from the branch offices. So that

Cable operators will "now about their particular area collection on day wise# wee"ly 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.

y using this COM System they can "now about their e!uipments located on which

areas. %ow 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# e(penses# 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. %elps

the Cable Operators manage their customers and provides the information about various

channels. It ma"es 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 A)ermanentB or

non=changing or stable. The updates are infre!uent and may be regarded as permanently stored

in the 2atabase. The Master roup has functionality to View & Change.

The master pages will have access to administrator only.


14/37

$rea Master ==9 Cable Operators they will divide their areas macro parts to micro parts li"e

huge area will be divided in to small areas# divisions. In this module admin will add areas and

code numbers.

+mployee Master == $dmin will add the staff and will provide the privileges as per the staff

designation. $ll the staff members cannot access all the modules. %e can add or delete the staff

accounts.

Customer Master == $dmin will add the new customers those who come in their areas and ta"e

new connection. $dmin can add or delete the customers and they can view the entire customers

list in area wise.

Monthly Charges == $dmin 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 notaffect the M$ST+* 2ata.

The T*$6S$CTIO6 roup of functionality is as follows,

0. 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.

1. Customer Status H Customer can ta"e connection and remove connection due to various

reasons at any point of time. Once is disconnected we ma"e him inactive . :e can

change customer status any point of time.

*eports Module

In this module we can generate the various MIS *eports to "eep trac" of the revenue#

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

0. $rea 8ist

1. +mployee 8ist

-. Customer 8ist


15/37

D. Collections $rea wise

/. Total Collections

. Collections between 2ates

J. Customer $&c

7M8

Admin Module Usecase Diagram

Hotel

Area

Employee

Customers

CustomerStatus

MonthlyCharges


16/37

Reports Module Usecase Diagram

Reports

Area List

Employee List

Customers List

CollectionsAreaWise

TotalCollections

CollectionsBetween

Dates

Customer A/C


17/37

Amin

Login Data Base

Admin Usecase Diagram

Area

Employee

Customer

CustomerStatus

MonthlyCharges


18/37

Activity diagram for Login

Enter !ser "D an #asswor

$aliation

%o

Type

!ser Aministrator

Display

Amin Moule

DisplayAuthorise Moule


19/37

Login Type

!ser

Aminstrator!sersorSta&&

Usecase Diagram for Login

Chec' user type

DisplayAuthorise Moule

DisplayAmin Moule


20/37

USER ACTIVIT

DIA!RAM

!ser or Agent

Login

TypeType Type

Masters Collections Reports


21/37

Login

Admin Start

Typeno

yes

AreaMaster

"ranc# Details

Logout

Adding $e% Area

$e% AreaE&isting Area

Area


22/37

Amin

LoginAdminMenu LogutData "ase

"n(ali!ser

Login

$iew Details

$iew Branch Details

Branch Details

Sa(e Success&ully

Logout

Logout Success&ully

T#ese are t#e fe%

options in Admin menu

Admin Se'uence Dataflo% Diagram

%ew Area

Area Details

Area Master

Employee Master%ew Employee

%ew Employee Sa(e

Eit Emplyee Details

Eit Emp loyee Success


23/37

".TESTIN

BLACK BO: TESTIN

In clearing house across various modules this testing was performed to chec" the following.

a@ +stablishing communication with the database for handling re!uest and response.

b@ Verification of O8+=2 providers?$2O@ in functionality

c@ )arameters passing and report generation used from the application with crystal report.

WHITE BO: TESTIN

$ll the statements included in the code across various modules were tested to find none of the

statements where overloo"ed or s"ipped from e(ecution. This enabled isolating of errors that

would have otherwise occurred and would have resulted in abnormal terminal or e(ceptions

thrown. The test was corely tested in patient and responsibility# Insured party# ailments#

procedures and applied payment modules.

STRIN TESTIN

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 informationwere tested for the following

a. null data

b. string length

c. data format

d. alpha numeric characters


24/37

I/ &66'+/; /(%) /7('*


25/37

The system as a whole along with re!uired e(ternal resources was e(ecuted to chec" the

dependencies# e(ception across the unavailability of the resources pertaining to the networ"

connection# O8+2 providers# authentication of database and database it self.

2S6 less connection and its effective communication for database was found to be as per their

S*S.

MUTATION TESTIN

$ll fields across every module were tested rigorously with inputs that were intentionally

provided with wrong data. This testing resolves bugs and errors through e(ception handling.

That was a result of any "ind 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 H!" output.

o #ommunication between the web application and the remote

database.

USER INTERFACE TESTING


26/37

$ll the interfaces that have been designed are reviewed whether they meet the customer

re!uirement or not. :hile testing all interfaces I have verified for errors as follows.

o $rrors related to specific interface mechanisms for example proper

execution of all menu lin%s that are provided in each web page

o $rrors related to all semantics of navigation and web application

functionally that is provided in each web page.

o $rrors in consistency related to different aspects of the interfaces li%e

font style, color, si&e, screen bac%ground color etc.,

o $rrors in viewing the interfaces in different web browsers li%e !icrosoft

internet explorer, !o&illa 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.

esting done within theses mechanisms is the interface mechanism testing.

his testing is done in following areas.

Links:

$ach navigation lin% is tested to ensure that appropriate web page is

lin%ed or not. I have listed all the lin%s in each form to test whether each

lin% is connecting the appropriate page or not.

Forms:

esting forms has been done at two different levels i.e. at minimum

level and at more targeted level. 't 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.


27/37

o Whether scripts that perform data validation from the client)side are

wor%ing properly or not.

't 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 Scriptin:

$ach and every function written in scripting has been tested by Bl!ck

Bo" Testin#

I have combined the forms testing with this client)side script testing,

because input for scripting is provided from forms. *ome methods of

scripting will be performed in some particular browsers and in others not. *o

I have also performed compatibility testing to ensure that the scripting

functions will wor% properly in all browsers.

USABILIT$ TESTS

In this testing I have verified up to, which level that, users can

interact with the system effectively. ests are designed to determine the

degree to which the web application interface ma%es users easy to wor%

with. I have designed test case so that usability testing can be verified at

different levels(

o +sability test has been performed on each and every individual

interface i.e. forms.

o +sability test has been performed on total web page with related client

side scripting functions.

o +sability test has been performed on total web application.

C%M&ATIBILIT$ TESTS


28/37

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

li%e different computer architectures, operating systems, browsers and

networ% connection speeds.

's 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.

o 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.

SC*++6 S%OTS


29/37


30/37


31/37


32/37


33/37


34/37


35/37


36/37

K.CONCLUSION


37/37

10. FUTURE ENHANCEMENTS

This pro+vangelos )etroutsos

. Software +ngineering = )ressman

J. System $nalysis and 2esign = Lames $.Senn

. $n Introduction to 2atabase Management System = C.L.2ate

K. O*$C8+ $dministration = Manual# Oracle )ress

04. O*$C8+ S8 *eference Manual =Manual# Oracle )ress

coms document

Documents