Teleserver Prjsohan dahiya

8/4/2019 Teleserver Prjsohan dahiya

1/103

Teleserver

Project Report

Submitted in partial fulfillment of the requirements for the degree of

Master of Computer Applications(MCA)

By

Sohan Singh

469472

July 2010

SHRI BALWANT INSTITUTE OF TECHNOLOGY

Approved by AICTE, Min of HRD, Govt of India & DTE, Govt of

Haryana

Affiliated to MD University, RohtakMeerut Road (Pallri), Near DPS, Sonepat-131001, Haryana


2/103

Teleserver

Project Report

Submitted in partial fulfillment of the requirements for the degree of

Master of Computer Applications(MCA)

By

Sohan Singh

469472

July 2010

under the Supervision ofMrs Neetu

SHRI BALWANT INSTITUTE OF TECHNOLOGY

Approved by AICTE, Min of HRD, Govt of India & DTE, Govt ofHaryana

Affiliated to MD University, Rohtak

Meerut Road (Pallri), Near DPS, Sonepat-131001, Haryana


3/103

CERTIFICATE

This is to certify that the Project titled Teleserver and submitted by Sohan Singh

having Roll No 469472 for the partial fulfillment of the requirements for the degree

ofMaster of Computer Applications (MCA), embodies the bonafide done by

him/her under my supervision.

____________________

Signature of the Supervisor

Place:

Date:


4/103

Acknowledgement

This report gives the details of the project work done in VI semester for partial

fulfillment of the requirements for the degree of Master of Computer

Applications(MCA), under the Supervision ofMrs. Neetu.

I am very grateful to my supervisor Mrs. Neetu for her help and able guidance for

the project. I am very thankful to my Institute, for providing me resources and

facilities to help in the project.

____________________

Signature of the Student

Name: Sohan Singh

Date: 07/07/2010


5/103

Company Profile

About CMC Limited - CMC Limited is a leading IT solutions company and a

subsidiary of Tata Consultancy Services Limited, one of the world's leading

information technology consulting, services and business process outsourcing

organizations. We are a part of the Tata group, India's best-known business

conglomerate. CMC is committed to the highest standards of corporate governance

and social responsibility. Rooted in the Tata group's long history of putting people

before profits and policy of leadership with trust, CMC believes in being ethical and

fair in its business dealings with all stakeholders -- employees, customers, partners,

investors and the community. CMC's commitment to the community is manifest in

the many projects such as health, education, livelihoods and women-children

welfare.

CMC Limited have proven expertise in a wide array of applications, including real-

time systems, online systems, embedded systems, process control, transaction

processing, image processing, data communications, networking, parallel

architectures, e-commerce technologies and e-governance applications. They also

conduct significant research into emerging technologies and competence areas at our

state-of-the-art, ISO 9001-certified R&D centre in Hyderabad, India. That is what

gives us an edge in complex, high technology projects.

CMC Limited was also the title of an Information Technology company based in the

United Kingdom and trading nationally and internationally during the 1970s and early1980s. The company no longer exists as such, although the business thread can be

traced to a number of currently trading companies. CMC Limited began as a branchof the US Company, Computer Machinery Corporation, which also no longer exists.

The original product line was Key Processing(R), which was an innovative and verysuccessful data-entry solution to replace 80-column punched cards.

History

During the year 1978, when IBM wound up its operations in India, CMC took over the

maintenance of IBM installations at over 800 locations around India and

subsequently, maintenance of computers supplied by other foreign players.CMC


6/103

visualized the need for total IT system solutions in 1980 and thus aligned its focus

with the government's thrust on IT development activities. 'Project Interact'

(International Education and Research for Applications of Computer Technology), a

United Nations project involving design, development and systems-engineering of

real-time, computer-based systems dedicated to applications in the areas of power

distribution, railway freight operations management and meteorology was a

significant milestone in CMC transition from a hardware maintenance company to a

complete end-to-end IT solutions provider.

Later CMC forayed into systems integration, interfacing, installation, commissioning,

software development, as well as education and training, on an ongoing basis. CMC's

R&D facility was set up in 1982 at Hyderabad, to undertake competency

development in niche areas in the frontiers of technology.

In tune to reflect diversified business activities, CMC renamed itself to 'CMC

Limited' in August 1984.

Following a spurt in the global demand for IT services in the early 1990s, particularly

in the United States, CMC decided to expand its operations and market its productand service offerings in these markets. Towards this end, in 1991, CMC acquired

Baton Rouge International Inc, USA (it was subsequently renamed CMC Americas,

Inc, in 2003), one of the first cross-border acquisitions by an Indian IT firm.

In 1992, the Indian government divested 16.69 per cent of CMC's equity to the

General Insurance Corporation of India and its subsidiaries who, in turn, sold part of

their stake to the public in 1996. In 1993, CMC's shares were listed on the

Hyderabad Stock Exchange and the Bombay Stock Exchange (BSE).

To service and develop its clientele in the UK and Europe, CMC opened a branch

office in London, in 2000. The next year, the government divested 51 per cent of

CMC's equity to Tata Sons Ltd, through a strategic sale, and CMC became a part of

the Tata group.

In line with its strategy of offering its products and services globally, in 2003, CMC

opened a branch office in Dubai to tap the hitherto unexplored markets of West Asia

and Africa.

In 2004, the government divested its remaining 26.5 per cent stake in CMC to the

public.


7/103

Table of Contents

Company Profile ................................................................................................................. 5

History .............................................................................................................................5

1. Introduction ................................................................................................................... 1

0.1 About .net ...................................................................................................................2

1.1.1Overview of .net framework ............................................................................... 2

2 Feasibility Report .............................................................................................................5

0.2 Purpose .......................................................................................................................5

0.3 Five common factors (TELOS) ................................................................................. 5

0.3.1 Technology and system feasibility ......................................................................50.3.2 Economic feasibility ........................................................................................... 6

0.3.3 Legal feasibility .................................................................................................. 6

0.3.4 Operational feasibility .........................................................................................6

0.3.5 Schedule feasibility ............................................................................................. 6

0.4 Scope .......................................................................................................................... 7

0.5 System Overview ....................................................................................................... 7

0.6 Project References ..................................................................................................... 8

0.7 Acronyms and Abbreviations .................................................................................... 9

0.8 Points of Contact ........................................................................................................ 9

0.8.1 Information ......................................................................................................... 9

2.8 Environment ..............................................................................................................9

2.8.1 Organizations Involved ...................................................................................... 9

2.8.2 Input/ Output ......................................................................................................9

2.8.3 Processing ........................................................................................................ 10

2.8.4 Security ............................................................................................................. 10

2.8.5 System Interaction ........................................................................................... 11

2.8.6 Physical Environment .................................................................................... 11

2.9 Current Functional Procedures ................................................................................ 11

2.10 Functional Objectives ............................................................................................11

2.11 Performance Objectives ....................................................................................... 12


8/103

2.12 Assumptions and Constraints .................................................................................12

2.13 Methodology .........................................................................................................13

2.14 Evaluation Criteria ................................................................................................13

2.15 Recommendation ..................................................................................................14

2.14.1 Description of Proposed System ........................................................................ 14

2.14.2 Improvements .................................................................................................... 14

2.14.3 Time and Resource Costs ....................................................................................15

2.14.4 Impacts ............................................................................................................... 16

2.14.4.1 Equipment Impacts .....................................................................................16

2.14.4.2 Software Impacts ......................................................................................... 16

2.14.4.3 Organizational Impacts ............................................................................... 17

2.14.4.4 Operational Impacts ....................................................................................17

2.14.4.5 Developmental Impacts ............................................................................... 17

2.14.4.6 Site or Facility Impacts ............................................................................... 18

2.14.4.6 Security and Privacy Impacts .......................................................................18

1 Requirement Specification ..............................................................................................20

3.1 Introduction .................................................................................................................20

3.1.1 Purpose ................................................................................................................20

3.1.2 Document Conventions ........................................................................................20

3.1.3Intended Audience and Reading Suggestions .......................................................203.1.4 Project Scope ................................................................................................... 21

3.2 Overall Description .....................................................................................................22

3.2.1 Product Perspective ..............................................................................................22

3.2.2 Product Features ...................................................................................................23

3.2.4 Operating Environment .....................................................................................27

3.2.5 Design and Implementation Constraints ............................................................27

3.2.6 User Documentation ............................................................................................28

3.2.7 Assumptions and Dependencies .......................................................................... 28

3.3 External Interface Requirements .................................................................................28

3.3.1User Interfaces ......................................................................................................28

3.3.2 Hardware Interfaces ............................................................................................. 28

3.3.3 Software Interfaces ..............................................................................................29

3.3.4 Communications Interfaces ................................................................................. 29


9/103

3.4 Other Nonfunctional Requirements ............................................................................ 29

3.4.1 Performance Requirements ..................................................................................29

3.4.2 Safety Requirements ............................................................................................ 29

3.4.3 Security Requirements .........................................................................................29

3.4.4 Software Quality Attributes ................................................................................. 30

3.4 Other Requirements ....................................................................................................30

2 Design Specification ....................................................................................................... 30

4.1 Introduction ............................................................................................................30

2.1.1 System Overview ..............................................................................................31

2.2 Design Considerations ............................................................................................. 31

2.2.1 Assumptions and Dependencies ....................................................................... 32

4.2.2 General Constraints ..............................................................................................32

4.2.3 Goals and Guidelines ........................................................................................... 33

4.2.4 Development Methods ......................................................................................33

4.3 Architectural Strategies ............................................................................................34

2.3 System Architecture .................................................................................................36

2.3.1 Subsystem Architecture ....................................................................................36

2.4 Policies and Tactics ..................................................................................................36

2.5 Detailed System Design ...........................................................................................37

2.5.1 Classification .....................................................................................................372.5.2 Definition ..........................................................................................................37

2.5.3 Responsibilities .................................................................................................38

2.5.4 Constraints ........................................................................................................38

2.5.5 Composition ...................................................................................................... 38

2.5.6 Database Design ................................................................................................38

3 Conclusion ......................................................................................................................90

This project is designed to meet the requirements of online telecommunications. It has

been developed in C# and Asp.net and the database has been built in SQL server keepingin mind the specification of system................................................................................... 90

6. Bibliography .................................................................................................................91

7. Checklist ........................................................................................................................ 92


10/103

Project Report

1. Introduction

The main intention of introducing this service is to serve the customers of service

provider in a better way. The following are the tasks performed by the system:

Receiving and Processing of new Telephone Connection requests.

Online Billing.

Online Payment Features.

Receiving, Processing and Routing complaints to different areas / exchanges.

Updating the status of the Telephone Connections.

Provides information about the services available.

The system also facilitates the customer to enquire about their application complaintstatus

The main idea to develop Teleserver is to take care of customer concerns such as

providing applications for connection, enquiries, bill entries and complaints.Teleserver provides its customers a qualitative and reliable telecom services the

current manual system is slow, laborious and error prone so there is need tocomputerize the same for quicker, efficient results and customer satisfaction.

Why we choose Teleserver

The need to be connected is increasing to extents where the inflow of connectionrequests exceeds which are handled manually. Hence computerization of application

requests and customer complaints brings better satisfaction and service orientedness .Quicker processing of application would mean better business and more

customers. Proper billing, timely payments and good customer feedback go a longway in identifying and succeeding a business and it future growth. Towards this

achievement the computerization of the Telecom industry will help greatly in meetingmarket requirements more satisfied customers would mean quicker growth and

hence obviously greater profits towards which all organizations strive.

1


11/103

Project Report

0.1 About .net

The .NET Framework is a collection of services and classes. It exists as a layer

between the applications we write and the underlying operating system. This

is a powerful concept: The .NET Framework need not be a Windows-only

solution. The.NET Framework could be moved to any operating system,

meaning our .NET applications could be run on any operating system hosting

the .NET Framework.

1.1.1Overview of .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:

o To provide a consistent object-oriented programming environment whether

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

distributed, or executed remotely.

o To provide a code-execution environment that guarantees safe execution of

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

o To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

o To make the developer experience consistent across widely varying types of

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

applications.

o To build all communication on industry standards to ensure that code basedon the .NET Framework can integrate with any other code.

2


12/103

Project Report

1.2 About visual studio.net

A Integrated Development Environment

To develop managed and unmanaged applications

Supports C#, C++, Visual Basic, JavaScript, ASP, etc.

Many useful tools and wizards.

Not part of the .NET Framework

Not necessary to build or run managed code.

The .NET Framework SDK includes command line compilers.

3


13/103

Project Report

FEASIBILITY REPORT

TELESERVER

4


14/103

Project Report

2 Feasibility Report

2.0 GENERAL INFORMATION

0.2 Purpose

The Feasibility Study represents whether it is financially and technically feasible to

develop the product. It helps in developing a abstract problem definition, it helps informulation of different solution strategies, analysis or alternative solution and it

requires making approximate estimate of resources, cost of development,development time.

This project is being developed keeping in mind the following objectives-


Receiving, Processing and routing complaints to different areas / exchanges.



0.3 Five common factors (TELOS)

0.3.1 Technology and system feasibility

Technical feasibility center around the existing computer system hardware etc. and

to what extent it can support the proposed addition. For example, if the current

computer is operating at 80% capacity - an arbitrary ceiling then running another

application could over load the system or require additional hardware. This involves

financial consideration to accommodate technical enhancements. If the budget is a

serious constraint then the project is judged not feasible.

5


15/103

Project Report

0.3.2 Economic feasibility

It looks at the financial aspects of the project. It determines whether the

management has enough resources and budget to invest in the proposed system and

the estimated time for the recovery of cost incurred. It also determines whether it is

worth while to invest the money in the proposed project. Economic feasibility is

determines by the means of cost benefit analysis.The proposed system is

economically feasible because the cost involved in purchasing the hardware and the

software are within approachable. The personal cost like salaries of employees hired

are also nominal, because working in this system need not required a highly qualified

professional. The operating-environment costs are marginal. The less time involved

also helped in its economical feasibility. It was observed that the organization has

already using computers for other purpose, so that there is no additional cost to be

incurred for adding this system to its computers.

0.3.3 Legal feasibility

It is common knowledge that computer installations have some thing to do

with turnover, transfers, retraining and changes in employee job status.

Therefore, it is understandable that the introduction of a candidate system

requites special efforts to educate, sell, and train the staff on new ways of

conducting business.

0.3.4 Operational feasibility

Is a measure of how well a proposed system solves the problems, and takes

advantages of the opportunities identified during scope definition and how it

satisfies the requirements identified in the requirements analysis phase of

system development.

0.3.5 Schedule feasibility

The result of the feasibility study is a formal proposal. This is simply report-a

formal document detailing the nature and the scope of the proposed solution.

The proposals summarize what is known and what is going to be done. Three

key considerations are involved in the feasibility analysis: economic, technical

and operational behavior.

6


16/103

Project Report

0.4 Scope

The main intention of introducing this service is to serve the customers of service

provider in a better way.

The system also facilitates the customer to enquire about their application complaint

status.The main idea to develop Teleserver is to take care of customer concerns suchas providing applications for connection, enquiries, bill entries and complaints.

Teleserver provides its customers a qualitative and reliable telecom services thecurrent manual system is slow, laborious and error prone so there is need to

computerize the same for quicker, efficient results and customer satisfaction.

.NET is the fast growing technology, which is being used, in day-to-day environmentas the fast growing technology for developing the user-friendly applications. The

applications are very much compatible to all the interfaces and can run at anyoperating system with the advantage of connectivity to any kind of database and

providing the web page facility.

0.5 System Overview

The system fulfills following objectives: -


Receiving, Processing and routing complaints to different areas / exchanges.



Responsible organization

The CMC and SBIT is the responsible organization which trained us throughout the

training.

System name or title

Name of our system is TELESERVER.

7


17/103

Project Report

System category

Major application:

There is always room for improvements, and the software we created can also beimproved. This is especially because we had to create it within a limited time. With

more time, the software can be improved to include security and different types ofusers. This would be the first step in making the software network-enabled, and

eventually web-enabled.

System environment or special conditions

Different privileges for Administrator and the Standard User are specified. Every

user has the same access to the system irrespective of his designation but he must

be authenticated by the System administrator.

0.6 Project References

During the development of this project following references were used

Books:

o John Sharp and Jon Jagger, Microsoft Visual C#.NET STEP BY STEP 2002

Edition.

References:

Book References

Software Engineering By Roger Pressman

ASP.NET Complete Reference

Microsoft Visual Studio.NET Documentation

Web References

www.google.co.in

www.c-sharpcorner.com/

www.mastercsharp.com/

8
http://www.google.co.in/http://www.c-sharpcorner.com/http://www.mastercsharp.com/http://www.google.co.in/http://www.c-sharpcorner.com/http://www.mastercsharp.com/


18/103

Project Report

0.7 Acronyms and Abbreviations

Ado.net

SQL

0.8 Points of Contact

0.8.1 Information

Name Status Organization Contact

SBIT Sponsor SBIT [email protected]

Mrs. Neetu Trainer CMC

Sohan Developer SBIT [email protected]

2.7 MANAGEMENT SUMMARY

2.8 Environment

2.8.1 Organizations Involved

Project sponsor: SBIT

Developer:

Sohan Developer SBIT [email protected]

User: Administrator/Authenticated User

2.8.2 Input/ Output

The user can provide the inputs in the following sections only:

MODULES:

The Teleserve customer services project has been divided into four modules.

9
mailto:[email protected]:[email protected]


19/103

Project Report

The project is divided into four modules.

1) Applications: Application for New Phone Connection.

Application for Phone Transfer.

Application for Temporary Phone Connection.

Application for Cancellation.

2) Entries: Bill Entry

Paid Bill Entry.

Payment Bill Entry.

Changed Number Entry.

3) Enquiry: Bill Enquiry.

Paid Bill Enquiry.

Changed Number Enquiry.

Enquiry by Telephone Number.

Application Enquiry

4) Complaints:

Line Disturbance.

Dead Phone.

In Correct Billing.

2.8.3 Processing

o System processing includes adequate system Memory to store the databaseof product and the customer details for future use.

o Following Software requires for system processing:

Windows 95/98/XP.

Sql Server 2005 as backend for storing details of books and member.

Visual Studio 2008.

2.8.4 Security

For ensuring the safety of the project, a login form is provided with the following

fields:

Username

10


20/103

Project Report

Password

It forces the access of authenticated user only to the application.

An additional feature is also provided which stores the date and time of users login.

2.8.5 System Interaction

The project is mainly divided into 4 modules as follows:

Applications

Entries

Enquiry

Complaints

The project is developed in such a way that enables modules of the system tointeract with each other in a convenient way which makes the system to increase itsfunctionality.

All the modules mentioned above are able to access the database of every othermodule.

2.8.6 Physical Environment

o Intel P- IV100 MHz or higher processor.

o Minimum of 128 MB RAM

o Display settings 800*600 on 16 bit high color.

o 15 MB of hard disk space.

o Operating system: Windows 9x/Windows XP/Windows NT.

2.9 Current Functional Procedures

The system also facilitates the customer to enquire about their application complaintstatus.The main idea to develop Teleserver is to take care of customer concerns such

as providing applications for connection, enquiries, bill entries and complaints.Teleserver provides its customers a qualitative and reliable telecom services the

current manual system is slow, laborious and error prone so there is need to

computerize the same for quicker, efficient results and customer satisfaction.

2.10Functional Objectives

11


21/103

Project Report

The newly system is developed in ASP.NET by using the SQL at the back end which

offers the following functional objectives:

.NET is used by programmers to create web based solutions.

.NET also provides graphic interface, forms to display and enter data, and

reports for printing.

The underlying Jet database which contains these objects is multi user aware

and handles record locking and referential integrity including cascading

updates and deletes.

Its easy to place a database on a network and have multiple users share and

update data without overwriting each others work.

Database solutions created entirely in SQL are well suited for individual and

workgroup use across a network. The number of simultaneous users that can

be supported depends on the amount of data, the tasks being performed,level of use, and application design.

2.11 Performance Objectives

Project Tasks are directly proportional to the Performance Criteria which have beenset for the project. The Performance Criteria, therefore, determines the amount of

work to be done. So, to increase the performance criteria it is almost alwaysnecessary to increase the Work or to obtain resources with greater capabilities (i.e.

they can perform the same work in a shorter period of time).

Therefore, the performance objectives are classified as follows:

Increase in the performance

Increase in the productivity

Fast and Easy retrieval of the data

Better security measurements Better accuracy

2.12Assumptions and Constraints

12


22/103

Project Report

The system used to run the application must support the internet explorer.

Also, the system must have .NET framework and C# installed on it.

2.13 Methodology

As the project is developed in .NET and SQL, therefore it is developed with the help

of tables, queries, forms and reports. For each module of the project a separatetable is created and a separate form is designed. Corresponding to each table and

form queries are defined. A brief description of these objects is illustrated as:

Tables

2.14 Evaluation Criteria

The evaluation criteria can be estimated easily with the help of following constraints:

Cost

Work x Resource Cost = Total Cost

To reduce the cost of a project and/or to conserve resources for other projects wekeep the work to a minimum consistent with achieving the aims and objectives of the

project. But as the Work is reduced by increasing the Resource Capability there is atrade off between resource cost and Total Cost. There may also be a reduction in

overall project time and this may have its own opportunities, benefits and/or cost

savings.

Ease of system use

o It is easy to use, since it uses the GUI provided in the user dialog.

o User friendly screens are provided.

Development time

o To reduce the Resource Days by increasing the ResourceCapability will not necessarily reduce the Total Cost because thereduction in resource days may be out weighed by the

increased Resource Cost.o However, improved Resource Capability will reduce the task time and

there is often a delivery Time Cost associated with a project so that thecost to the organization will be less or its income improved. This is the so

called 'window of opportunity' factor.

13


23/103

Project Report

2.15 Recommendation

It is strictly recommended to backup your database time to time because the

application runs in the SQL and in case of remote access the data may become

inconsistent. So the backup database will serve as a great relief in case of data

inconsistency or data loss.

2.14 PROPOSED SYSTEM

2.14.1 Description of Proposed System

TELESERVER is an automatic, effective and efficient computer users tool. Withdynamic and attractive interface it is well laid out with a variety of features for the

users to choose from.

The software enables the user to maintain records of the various computers in thecompany and their owners. The software maintain the Teleserver detail of the

company. It allows the user to filter various request registered .It also allowsgenerating various reports and running various queries.

The software technologies used for developing the project are ASP.NET under C#and SQL

2.14.2 Improvements

There is always room for improvements, and the software we created can also be

improved. This is especially because we had to create it within a limited time. Withmore time, the software can be improved to include security and different types of

users. This would be the first step in making the software network-enabled, andeventually web-enabled. This was our original after-thought to programming the

software, and we had chosen SQL. In addition, the software can also be improved interms of the calculations it can do, and more flexibility in the retrieval and storage of

data.

14


24/103

Project Report

2.14.3 Time and Resource Costs

Resources are people, equipment and money. They may be internal or external andinclude suppliers, contractors, partners, statutory bodies, governments, banks,

loans, grants, expert opinion (Lawyers, Accountants, and Consultants), etc.

Generally, we are reasonably good at estimating or obtaining estimates for the use

and costs of external resources. Where we aren't we can obtain expert opinion(another cost). Where we often fail is in estimating the cost of the use of our internal

resources, particularly people.

Aside from the employment costs, there are:

the costs to the service provision they normally perform, the cost of substitution to maintain the service,

the loss of opportunity for them to work on other projects

And the cost of training associated with the project work.

Because internal resources are so constrained it is vital that we select our projects

with the utmost care to maximize the use of that resource. Defining projects helps usto make this selection objectively and rationally. Consider these definitions:

Work in a project is proportional to the number of Objectives and the Performance

Criteria

Clearly, if we reduce the number of our objectives and the performance standard(e.g. 5% rather than 10% improvement of sales or reduction of costs then we canreduce the work required to complete the project.

Number of resources deployed x Time = Work

So, another way of expressing work is in the number of resources we will need andthe time those resources will have to be deployed on the project. If we can reduce

the work we can reduce the time and/or the number of resources. It must be bornein mind that the relationship between the numbers of resources deployed and the

time it takes to do a given amount of work is not linear. Often, just adding people to

a project can increase the time because they have to be trained, managed and their

work co-ordinate with others. All this takes work and therefore time.

If we decide that all the objectives must be met and we cannot reduce the work thenwhat other options do we have?

Time =Work Resource Capability

Sometimes we can speed up the work by using bigger, faster, more powerful

machines (computers, plant and machinery) but, of course, this has a cost. When

15


25/103

Project Report

the resource is people we can employ more highly skilled, more intelligent and more

capable people (if we can find them and persuade them to work on the project). But,whether it is machines or people:

Resource Capability is normally directly proportional to Resource Cost

Time Cost:

The time limit for the module is approximately 4 months.

2.14.4 Impacts

2.14.4.1 Equipment Impacts

In actual, the project is not concerned too much with the need of adding any

additional equipment and the already existing equipments will be efficient to perform

the work effectively.

However, in order to increase the performance of the system, more processors can

be attached (i.e. multi-processor system).

The requirements for the application to run on any system are as follows:-






o IBM PC Keyboard.

2.14.4.2 Software Impacts

ASP.NET3.5 or later version must be available on the system at which the

application runs.

Also, the system must have .NET framework and C# installed on it.

16


26/103

Project Report

2.14.4.3 Organizational Impacts

Staff of the organization using the project should be familiar with all the

aspects of ASP.NET 3.5 version or any later.

Also, the designated staff should have a sound knowledge of C#

programming.

The organization taking benefits of the project should be capable of handling

the large database using multiprocessors system and have an efficient

knowledge of database connectivity to explore the system to its full potential.

2.14.4.4 Operational Impacts

Various operational impacts are categorized as:

User operating procedures: Reduces the complexities by providing the user

friendly screens and user dialogue boxes.

Operating center procedures: Different privileges for Administrator and

the Standard User are not specified. Every user has the same access(exceptcreation of new user and power of authentication) to the system but first he

must be authenticated by the system administrator.

Data entry procedures: Various user friendly forms are provided toenter the data and records.

System failure contingencies and recovery procedures: Backup

of the database is recommended in case of the system crash and datainconsistency.

2.14.4.5 Developmental Impacts

The various developmental impacts that effect the processing and functioning of thesystem are described as below:

Resources used to perform the computer processing for .NET and SQL

validation fields are required.

For the privacy and security implications, a login interface is developed using

ASP.NET validation control scheme that includes the three fields (e.g.

Username, Password and Confirm Password).

17


27/103

Project Report

2.14.4.6 Site or Facility Impacts

The modification in the building or office requirements has no such impacts on theproject development.

2.14.4.6 Security and Privacy Impacts

Imposing the security and privacy restrict the any user other than the administratoritself to modify or update the database until he is not authenticated by the system

administrator to use the system. This will somehow affects the development process

of the system database at a steady rate.

18


28/103

Project Report

Software Requirements Specification

TELESERVER

19


29/103

Project Report

1 Requirement Specification

3.1 Introduction

3.1.1 Purpose

The main intention of introducing this service is to serve the customers of serviceprovider in a better way. The following are the tasks performed by the system:


Online Billing.

Online Payment Features.

Receiving, Processing and Routing complaints to different areas / exchanges. Updating the status of the Telephone Connections.


The system also facilitates the customer to enquire about their application complaint

status

The main idea to develop Teleserver is to take care of customer concerns such as

providing applications for connection, enquiries, bill entries and complaints.Teleserver provides its customers a qualitative and reliable telecom services the

current manual system is slow, laborious and error prone so there is need tocomputerize the same for quicker, efficient results and customer satisfaction.

3.1.2 Document Conventions

o All the text in this SRS is written in Times font.

o The headings have the font size 18.

o The sub-headings will have font size 14.

o The text is written in font size 12.

o Important points are written in bullets.

3.1.3Intended Audience and Reading Suggestions

o Developers - Take into consideration the objective of the product.o Project Manager - The development should take place stepwise.o Users - Read the working of the project.o Testers - Start building test cases while taking into consideration the

product.o Documentation Writer - Take a look at the perspective of document and

include requirements in the given format.

20


30/103

Project Report

The rest of the SRS contain project scope, objective and limitations.The

document must be read in the given sequence itself.

3.1.4 Project Scope

Objectives:


Receiving, Processing and routing complaints to different areas /

exchanges.



Scope :

Limitation of existing systems :-

The existing systems are facing the following problems that we are trying to

overcome in our networking site-

o The existing systems are not very much user interactive and are complicatedto use.

o Those systems do not provide a higher level of security.o The existing system does not provide support only 1 organization.o In the existing systems it is very difficult to add new features thus lacking in

future scope.o One must register himself/herself to buy new connection.o Administrator can view the details of all the members .

o He can edit, add and update the details of the members.o Only administrator has the perMsion to view, edit, add and update the details of

members.

We have referred the following books:

o ASP.NET Complete referneceo C# Complete Reference

21


31/103

Project Report

3.2 Overall Description

3.2.1 Product Perspective

MODULES:The Teleserve customer services project has been divided into four modules.

The project is divided into four modules.

1)Applications.

Application for New Phone Connection.

Application for Phone Transfer.

Application for Temporary Phone Connection.

Application for Cancellation.

2)Entries.

Bill Entry Paid Bill Entry.

Payment Bill Entry.

Changed Number Entry.

3)Enquiry.

Bill Enquiry.

Paid Bill Enquiry.

Changed Number Enquiry.

Enquiry by Telephone Number.

Application Enquiry

4)Complaints. Line Disturbance.

Dead Phone.

In Correct Billing.

22


32/103

Project Report

3.2.2 Product Features

Data flow Diagram

23

TELESERVER

USERAdmin

Context Diagram


33/103

Project Report

24

SubscriptionDetails

NewSubscriptio

n

Process

NewSubscription

Data Base

Addsubscription

New Subscription DFD

SubscriptionDetails

Renewal

Subscription

Process

RenewalSubscription

Data Base

Add Renewalsubscription

Renewal Subscription DFD


34/103

Project Report

25

Details

ChangeAddress

Process

ChangeAddress

Data Base

RecordModified

Change Address DFD

ViewSubscriptio

n

Process

ViewSubscription

Data Base

View Details

View Subscription DFD


35/103

Project Report

26

ViewFeedback

Process

View FeedBack

Data Base

View Details

View Feed Back DFD


36/103

Project Report

E-R DIAGRAMS

Entity Set

Works in relationship set

3.2.4 Operating Environment

The requirements for the system to run on any system are as follows:-





o Operating system: Windows XP/Windows NT.

3.2.5 Design and Implementation Constraints

o The developer must know how to use SQL Server

27

Sub ID Name Registratio

n

User

Addre


37/103

Project Report

o The LAN connection must be of 256 mbps at least since the application might

not work to the expected level and perform with delays.o There should be a separate server room where authenticated people are

allowed only since the database information will be present there only.

3.2.6 User Documentation

o User manuals.

o Online Tutorial.

3.2.7 Assumptions and Dependencies

o There could be change in the objective of the application.o There could be change due to some aspect that comes to us later.

3.3 External Interface Requirements

3.3.1User Interfaces

o When the customer visits teleserver website the first page heviews are the home page.

o When the customer views the home page he is only able to see the

Services provided.o When customer visit website he can also view all the modules defined in the project.o If he wants to buy new connection he will have to first register himself through the

New Application page.o When he registered himself so he can authority to buy the product of his

choice.

o Next is the role of the Administrator: when he click on Administrator menu

a login form is displayed after sign in he is able to view the Customer Details

who has taken the membership.o The Administrator is able to view the bill details after clicking on the bill details.

.

3.3.2 Hardware Interfaces

The requirements for the system to run on any system are as follows:-





28


38/103

Project Report


3.3.3 Software Interfaces

o Asp.net for server side application and designing the page.o C# for business logico Sql server for database as back end

3.3.4 Communications Interfaces

o This business networking site can be used in any web browser but we have

used only Internet Explorer.

o The communication standard used is HTTP.

o The security is provided with the help of password that will certainly contain a

special character.

3.4 Other Nonfunctional Requirements

3.4.1 Performance Requirements

Project Tasks are directly proportional to the Performance Criteria which have beenset for the project. The Performance Criteria, therefore, determines the amount of

work to be done. So, to increase the performance criteria it is almost alwaysnecessary to increase the Work or to obtain resources with greater capabilities (i.e.

they can perform the same work in a shorter period of time).

Therefore, the performance objectives are classified as follows:

Easy to use

Increase in the performance

Increase in the productivity

Fast and Easy retrieval of the data

3.4.2 Safety Requirements

o The operating system used must be licensed.

o LAN connection must have 256 mbps speed.

o Antivirus must be installed to avoid spywares and malwares.

3.4.3 Security Requirements

29


39/103

Project Report

o The product is provided security with the help of a password.

o If the user name and password did not match with the same stored inside the

database then an error message will be displayed.

o The password will certainly contain a special character otherwise it will not be

accepted.

o The server room will be provided sufficient security.

3.4.4 Software Quality Attributes

o The product is able to adapt in any environment.

o It is available freely.

o It is flexible to use as can be used on any browser.

o Easily maintained.

o It is portable as you dont need any additional software to use it. You will

need only a LAN connection.

o It is very much reusable.

3.4 Other Requirements

o To make this application a success we need to obtain website rights on which

users can use this chat application.

o We also need perMsions to install this application on all the systems of SBIT.

2 Design Specification

4.1 Introduction

o The purpose of this document is to understand the design of our Teleserverin a better way.

o This document can be used as a user manual or user guide to the software.

o Describe this document's intended audience

Developers This document is a guide to the developers and

shape the way in which he will proceed in the coding part.

Project Manager He can keep a view on the process of

development and can manage the future tasks.

Marketing Staff The marketing staff would design their

strategy on the basis of the design.

30


40/103

Project Report

Users They will get help in the form of user manual.

o Teleserver This name is given since our product is an Teleserver site in whichthe customers can view all the details of telecommunications and can registerthemselves online and becoming the member.The payment should be through

credit card only.o Other documents that must also be referenced for better understanding of the

product are:

Software Feasibility Report(2)

Software Requirement Specification(3)

2.1.1 System Overview

Login Page

o It will have 2 text boxes for user name and password.o There will be a login button that will check if the user name and password is correct

and navigate to the next web page.

Home Page

o It will be opened if the user name and password entered on the login

page

o There will be links to different pages like registration page, admin page

etc inside the home page that will direct to different web pages.

New Application Page

o Inside the new application page some of the text boxes are there forkeeping the overall details of the members.

o There is a text box to write messages.

o There will be a button to submit your message.

2.2 Design Considerations

This section describes many of the issues which need to be addressed or resolved

before attempting to devise a complete design solution.

31


41/103

Project Report

2.2.1 Assumptions and Dependencies

Describe any assumptions or dependencies regarding the software and its use. Thesemay concern such issues as:

Software Used

o Microsoft Visual Studio 2008 In this software we have used C#

language as a front end to design the application.

o Microsoft SQL Server 2005- It is the back end that is used to design the

databases.

Hardware Used





o IBM PC Keyboard.

Operating system used must be a Windows environment as .net applicationsbasically works on windows operating system.

End-users must know how to use the applications and they must know the

netiquettes to use this application in a better way.

There might be some changes due to addition of some features as the project

proceeds but the basic structure will be the same.

4.2.2 General Constraints

The end-user may want to have more features in the application but they will

be surely handled.

The application may work when users are connected through some LAN

connection.

The screen resolution should be 800*600 and protocol should preferably beHTTP.

For database may face a problem if memory is overloaded.

The user must remember his or her requirements and the database server

must be protected properly.

The LAN connection should be atleast 256kbps and a Pentium IV processor.

32


42/103

Project Report

4.2.3 Goals and Guidelines

If the database is overloaded the speed will be degraded as more time will be

needed to access the data in database so it is needed to be organized in an

efficient way.

This networking site can be used on any company location leading to the greataid in communication.

4.2.4 Development Methods

SDLC of a project is defined as the duration of time that starts with theconceptualization of the software being developed and ends with the software being

discarded after its usage.

There are a number of SDLC models available and used for the development of

software projects but the one that best describes the development of this project andthat we used for developing this project is

33


43/103

Project Report

Advantages of using the ITERATIVE ENHANCEMENT MODEL

Incremental development is particularly useful when staffing is unavailable for

a complete implementation by the business deadline that has been established

for the project.

Early increments can be implemented with a fewer number of people. If the

core product is well received, then additional staff if required can be added to

implement the next increment.

Increments can be planned to manage technical risk.

4.3 Architectural Strategies

Software Used

o Microsoft Visual Studio 2008 using C# language as a front end.

o Microsoft SQL Server 2005- It is the back end that is used to design the

databases.

Future plans for extending or enhancing the software

o This application can be upgraded with various features like secure

online bill payment by credit cards .

There are 4 user interfaces:

o Application

o Entries

o Enquiry

o Complaints

Hardware Used





o IBM PC Keyboard.

Error detection and recovery

34


44/103

Project Report

Microsoft Visual Studio .NET supports the following data providers, each

of which has its own set of objects and collections that are used when

handling errors in a smart device applications

.NET Compact Framework Data Provider for SQL Server CE

This data provider belongs to the System.Data.SqlServerCenamespace, and

stores Microsoft SQL Server 2005 Windows CE (SQL Server CE)

Replication, RDA, and Engine object error information in the following error

objects and collections.

Object/Collection Description

SqlCeException class When an error occurs, an instance of

theSqlCeException class is created thatcontains the collection

of SqlCeError objects.

SqlCeErrorCollectionclass The SqlCeErrorCollection object contains

one or more SqlCeError objects for

aSqlCeException object. The collection can

be accessed using

the SqlCeException.Errorsproperty.

SqlCeError class Each SqlCeError object contains an array

of error parameters that provide detailedinformation about the error.

The .NET Compact Framework Data Provider for SQL Server CE is included in

the Microsoft .NET Compact Framework that ships with Visual Studio .NET.

For more information, see .NET Compact Framework Data Providers.

Memory management policies

The Microsoft .NET common language runtime requires that all resources be

allocated from the managed heap. Objects are automatically freed when they

are no longer needed by the application.When a process is initialized, the runtime reserves a contiguous region of

address space that initially has no storage allocated for it. This address space

region is the managed heap. The heap also maintains a pointer. This pointer

indicates where the next object is to be allocated within the heap. Initially,

the pointer is set to the base address of the reserved address space region.

The garbage collector checks to see if there are any objects in the heap that

are no longer being used by the application. If such objects exist, then the

35
http://msdn.microsoft.com/en-us/library/aa275630(SQL.80).aspxhttp://msdn.microsoft.com/en-us/library/aa275630(SQL.80).aspx


45/103

Project Report

memory used by these objects can be reclaimed. (If no more memory is

available for the heap, then the new operator throws an out

ofMemoryException.)

We have created 31 database tables taking into account the members,

administrators, member profiles, messages sent, etc.

Firstly you will be assigned a id with which you can login the profile.

Communication is done with the help of keyboard.

2.3 System Architecture

2.3.1 Subsystem Architecture

Login Page:

This page contains an option to enter into the profile of the user.

Home Page :

It contains all the information about the project that means over all descriptions of

modules in the teleserver. It also contains all the links to other pages like loginpage,new application page,admin page etc.

New Application Page:

This page is here to allow new users to register themselves so as to become the

member of this site so that they can buy new connections.

In this the User should enter various information about him.

Enquiry page :

This page contains all the details about the services provided by the teleserver

project. Anyone of the end user can visit on this page and enquire about hisproblems.

2.4 Policies and Tactics The system must have the necessary settings to run a asp.net program or

framework 2.0.

Coding must be done in a healthy and secure way and should follow good

coding practices.

The protocol of one or more subsystems, modules, or subroutines.

The choice of a particular algorithm or programming idiom (or design pattern)

to implement portions of the system's functionality

36


46/103

Project Report

Testing should be done through alpha and beta testing.

Software can be maintained by doing database updates and removing addition

backlog.

Interfaces that we have used are for administrator and members of thecompany.

2.5 Detailed System Design

2.5.1 Classification

The various components used are login, home, sign up, admin etc.

2.5.2 Definition

Login Page:

This page contains an option to enter into the profile of the user.

Home Page :

It contains all the information about the project that means over all descriptions ofmodules in the teleserver. It also contains all the links to other pages like login

page,new application page,admin page etc.

New Application Page:

This page is here to allow new users to register themselves so as to become themember of this site so that they can buy new connections.

In this the User should enter various information about him.

Enquiry page :

This page contains all the details about the services provided by the teleserverproject. Anyone of the end user can visit on this page and enquire about his

problems

Admin page :

This page contains all the information about the different members of this book store

, all the books,editorials etc.He can add new books,editorials to the system by logingin through this page only.

37


47/103

Project Report

2.5.3 Responsibilities

The various responsibilities are described in most details in the above section.

2.5.4 Constraints

The communication between components is described above in more detail.

2.5.5 Composition

There are no subcomponents used in our application.

2.5.6 Database Design

The databases play a very important role in this application and will be describedcarefully in the following sections.

cancel Table :

2.5.6.1 Name of thetable

Cancel

Description This table describes the information about to cancel thenetwork connection.

Attribute Description Type2.5.6.2 Exam

ple ofvalues

Reg Registrationnumber .

Int Any number.

Fathername Father name ofthe customer.

Varchar(2000) Any text.

Name Name of customer Varchar(2000) Any text

Peraddress Address of thecustomer

Varchar(2000) Any text

38


48/103

Project Report

Corraddress Corraspondance

address of thecustomer


Email varchar(2000) Any text

Dob Dob of customer varchar(2000) Any text

contact Phone number Varchar(2000) Any text

Canceldate Date of

cancellation


Nationality Nationality Varchar(2000) Any text

2.5.6.3 PrimaryKey

Reg

2.5.6.4 Foreign Keys-

2.5.6.5 SQL Code

CREATETABLE [dbo].[cancel]([reg] [int] IDENTITY(2000,1)NOTNULL,

[name] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[fathername] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,

[gender] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[peraddress] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[corraddress] [varchar](2000)COLLATE


[email] [varchar](2000)COLLATE


[dob] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[contact] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[canceldate] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[nationality] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL

)ON [PRIMARY]

Tables data:

Here we have shown the various tables-

39


49/103

Project Report

Viewbill1:

2.5.6.6 Name of thetable

Viewbill1

Description This table describes the information about to viewbill thenetwork connection.

Attribute Description Type2.5.6.7 Exam

ple ofvalues

registration Identity Int Any number.

Jan Name of month Int January

Feb Name of month Int February

March Name of month Int March

April Name of month Int April

Mayw Name of month Int May

June Name of month Int June

July Name of month Int July

Aug Name of month Int August

Sep Name of month Int September

Oct Name of month Int October

Nov Name of month Int November

Dec Name of month Int December

40


50/103

Project Report

2.5.6.8 PrimaryKey

Registration

2.5.6.9 Foreign Keys-

2.5.6.10 SQLCode

CREATETABLE [dbo].[viewbill1](

[registration] [int] NOTNULL,[jan] [int] NULLCONSTRAINT [def_tel] DEFAULT

(NULL),[feb] [int] NULLCONSTRAINT [def_tel1]

DEFAULT(NULL),[march] [int] NULLCONSTRAINT [def_tel2]

DEFAULT(NULL),[april] [int] NULLCONSTRAINT [def_tel3]

DEFAULT(NULL),[may] [int] NULLCONSTRAINT [def_tel4]

DEFAULT(NULL),

[june] [int] NULLCONSTRAINT [def_tel5]DEFAULT(NULL),

[july] [int] NULLCONSTRAINT [def_tel6]

DEFAULT(NULL),[aug] [int] NULLCONSTRAINT [def_tel7]

DEFAULT(NULL),[sep] [int] NULLCONSTRAINT [def_tel8]

DEFAULT(NULL),[oct] [int] NULLCONSTRAINT [def_tel9]

DEFAULT(NULL),[nov] [int] NULLCONSTRAINT [def_tel10]

DEFAULT(NULL),

[december] [int] NULLCONSTRAINT [def_tel11]DEFAULT(NULL),PRIMARYKEYCLUSTERED

([registration] ASC

)WITH(PAD_INDEX =OFF, IGNORE_DUP_KEY =OFF)ON [PRIMARY]

)ON [PRIMARY]

CREATETABLE [dbo].[viewbill1]([registration] [int] NOTNULL,

[jan] [int] NULLCONSTRAINT [def_tel] DEFAULT(NULL),[feb] [int] NULLCONSTRAINT [def_tel1] DEFAULT(NULL),

[march] [int] NULLCONSTRAINT [def_tel2] DEFAULT(NULL),[april] [int] NULLCONSTRAINT [def_tel3] DEFAULT(NULL),

[may] [int] NULLCONSTRAINT [def_tel4] DEFAULT(NULL),[june] [int] NULLCONSTRAINT [def_tel5] DEFAULT(NULL),

[july] [int] NULLCONSTRAINT [def_tel6] DEFAULT(NULL),

41


51/103

Project Report

[aug] [int] NULLCONSTRAINT [def_tel7] DEFAULT(NULL),

[sep] [int] NULLCONSTRAINT [def_tel8] DEFAULT(NULL),[oct] [int] NULLCONSTRAINT [def_tel9] DEFAULT(NULL),

[nov] [int] NULLCONSTRAINT [def_tel10] DEFAULT(NULL),[december] [int] NULLCONSTRAINT [def_tel11] DEFAULT(NULL),

PRIMARYKEYCLUSTERED(

[registration] ASC)WITH(PAD_INDEX =OFF, IGNORE_DUP_KEY =OFF)ON [PRIMARY]

)ON [PRIMARY]

Viewbill:

CREATETABLE [dbo].[viewbill](

[registration] [int] NOTNULL,[jan] [int] NULL,

[feb] [int] NULL,[march] [int] NULL,

[april] [int] NULL,[may] [int] NULL,

[june] [int] NULL,[july] [int] NULL,

[aug] [int] NULL,

[sep] [int] NULL,[oct] [int] NULL,

[nov] [int] NULL,

[december] [int] NULL,PRIMARYKEYCLUSTERED

([registration] ASC

)WITH(PAD_INDEX =OFF, IGNORE_DUP_KEY =OFF)ON [PRIMARY])ON [PRIMARY]

42


52/103

Project Report

Feedback:

CREATETABLE [dbo].[feedback]([reg] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NOTNULL,[email] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[rate] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[satisfaction] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,PRIMARYKEYCLUSTERED

([reg] ASC

)WITH(PAD_INDEX =OFF, IGNORE_DUP_KEY =OFF)ON [PRIMARY])ON [PRIMARY]

2.5.6.11 Name of the table

Feedback

Description This table describes the information about to feedback thenetwork connection.

Attribute Description Type2.5.6.12 E

xample ofvalue

s

Reg Identity Varchar(2000) Any number.

Email Email id Varchar(2000) Any text

Rate Rate Varchar(2000) Any Text

Satisfaction Satisfaction Varchar(2000) Any Text

43


53/103

Project Report

2.5.6.13 PrimaryKey

Reg

2.5.6.14 ForeignKeys

-

2.5.6.15 SQLCode

CREATETABLE [dbo].[feedback](

[reg] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NOTNULL,

[email] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[rate] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[satisfaction] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,


[reg] ASC)WITH(PAD_INDEX =OFF, IGNORE_DUP_KEY =OFF)

ON [PRIMARY])ON [PRIMARY]

Mastertable:

CREATETABLE [dbo].[mastertable](

[reg] [int] IDENTITY(22345,1)NOTNULL,

[name] [varchar](255)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[fathername] [varchar](255)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,

[gender] [varchar](7)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[peraddress] [varchar](255)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[corraddress] [varchar](255)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,[email] [varchar](255)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[dob] [varchar](20)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[contact] [varchar](20)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[regdate] [varchar](20)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[nationality] [varchar](40)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[pwd] [varchar](40)COLLATE SQL_Latin1_General_CP1_CI_AS NULL)ON [PRIMARY]


Feedback

Description This table describes the information about to feedback thenetwork connection.

44


54/103

Project Report


xample ofvalues

Reg Identity Int Any number.


Fathername Father name of

customer

Varchar(255) Any Text

Gender Male or female Varchar(7) Any Text

Peraddress Address Varchar(255) Any text

Corraddress Correspondaddress


Email Email address ofcustomer


Dob Date of birth Varchar(255) Any text

Contact Contact number Varchar(20) Any text

Regdate Reg date Varchar(20) Any text

Nationality Indian orcountry


Pwd Password Varchar(40) Any text

45


55/103

Project Report

2.5.6.18 PrimaryKey

Reg


-

2.5.6.20 SQLCode

CREATETABLE [dbo].[feedback](

[reg] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NOTNULL,


[rate] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[satisfaction] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,


[reg] ASC)WITH(PAD_INDEX =OFF, IGNORE_DUP_KEY =OFF)

ON [PRIMARY])ON [PRIMARY]

Phonetransfer:

CREATETABLE [dbo].[phonetransfer](

[id] [int] IDENTITY(2000,1)NOTNULL,

[newname] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[newfather] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,

[oldname] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[oldfather] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[peradd] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[corradd] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[email] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,


[regdate] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[nationality] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL, [pwd] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[gender] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL

)ON [PRIMARY]

46


56/103

Project Report


Phonetransfer

Description This table describes the information about to phone transfer

the network connection.


xample ofvalues

Id Identity Int Any number.

newname Name of customer Varchar(2000) Any text

newFathername Father name of

customer






Email Email address of

customer





Nationality Indian orcountry



Oldname Old name Varchar(2000) Any text

oldfather Old father name Varchar(2000) Any text

47


57/103

Project Report

2.5.6.23 PrimaryKey

Id


-

2.5.6.25 SQLCode

CREATETABLE [dbo].[phonetransfer](

[id] [int] IDENTITY(2000,1)NOTNULL,[newname] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[newfather] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[oldname] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[oldfather] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[peradd] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[corradd] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[email] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[dob] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[contact] [varchar](2000)COLLATE


[regdate] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,

[nationality] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[pwd] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[gender] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL)ON [PRIMARY]

Tempcon:

CREATETABLE [dbo].[tempcon]([id] [int] IDENTITY(1000,1)NOTNULL,[name] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,

[fathername] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_ASNULL,

[gender] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[peraddress] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,

48


58/103

Project Report

[corresaddress] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,[email] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,


[regdate] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL,[nationality] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS

NULL,[pwd] [varchar](2000)COLLATE SQL_Latin1_General_CP1_CI_AS NULL

)ON [PRIMARY]


Tempcon

Description This table describes the information about to tempconnection the network connection.


xample ofvalues

Id Identity Int Any number.


Fathername Father name ofcustomer






Email Email address ofcustomer





Nationality Indian or Varchar(2000) Any text

49


59/103

Project Report

country


2.5.6.28 PrimaryKey

Id


-

2.5.6.30 SQLCode

CREATETABLE [dbo].[tempcon](

[id] [int] IDENTITY(1000,1)NOTNULL,[name] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[fathername] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[gender] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[peraddress] [varchar](2000)COLLATE


[corresaddress] [varchar](2000)COLLATESQL_Latin1_General_CP1_CI_AS NULL,


[dob] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[contact] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[regdate] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[nationality] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL,[pwd] [varchar](2000)COLLATE

SQL_Latin1_General_CP1_CI_AS NULL)ON [PRIMARY]

50


60/103

Project Report

SQL queries:

Select Statement

SELECT "column_name" FROM "table_name"

Distinct

SELECT DISTINCT "column_name"FROM "table_name"

Where

SELECT "column_name"FROM "table_name"

WHERE "condition"

And/Or

SELECT "column_name"

FROM "table_name"WHERE "simple condition"

{[AND|OR] "simple condition"}+

In


FROM "table_name"

WHERE "column_name" IN ('value1', 'value2', ...)

Between


FROM "table_name"WHERE "column_name" BETWEEN 'value1' AND 'value2'

Like


FROM "table_name"

WHERE "column_name" LIKE {PATTERN}

Order By

SELECT "column_name"FROM "table_name"

[WHERE "condition"]ORDER BY "column_name" [ASC, DESC]

51
http://www.1keydata.com/sql/sqlselect.htmlhttp://www.1keydata.com/sql/sqldistinct.htmlhttp://www.1keydata.com/sql/sqlwhere.htmlhttp://www.1keydata.com/sql/sqlandor.htmlhttp://www.1keydata.com/sql/sqlin.htmlhttp://www.1keydata.com/sql/sqlbetween.htmlhttp://www.1keydata.com/sql/sqllike.htmlhttp://www.1keydata.com/sql/sqlorderby.htmlhttp://www.1keydata.com/sql/sqlselect.htmlhttp://www.1keydata.com/sql/sqldistinct.htmlhttp://www.1keydata.com/sql/sqlwhere.htmlhttp://www.1keydata.com/sql/sqlandor.htmlhttp://www.1keydata.com/sql/sqlin.htmlhttp://www.1keydata.com/sql/sqlbetween.htmlhttp://www.1keydata.com/sql/sqllike.htmlhttp://www.1keydata.com/sql/sqlorderby.html


61/103

Project Report

Count

SELECT COUNT("column_name")

FROM "table_name"

Group By

SELECT "column_name1", SUM("column_name2")

FROM "table_name"GROUP BY "column_name1"

Having

SELECT "column_name1", SUM("column_name2")FROM "table_name"

GROUP BY "column_name1"HAVING (arithematic function condition)

Create Table Statement

CREATE TABLE "table_name"("column 1" "data_type_for_column_1",

"column 2" "data_type_for_column_2",)

Drop Table Statement

DROP TABLE "table_name"

Truncate Table Statement

TRUNCATE TABLE "table_name"

Insert Into Statement

INSERT INTO "table_name" ("column1", "column2", ...)

VALUES ("value1", "value2", ...)

Update Statement

UPDATE "table_name"

SET "column_1" = [new value]WHERE {condition}

Delete From Statement

DELETE FROM "table_name"

WHERE {condition}

Transactions implementation:

52
http://www.1keydata.com/sql/sqlcount.htmlhttp://www.1keydata.com/sql/sqlgroupby.htmlhttp://www.1keydata.com/sql/sqlhaving.htmlhttp://www.1keydata.com/sql/sqlcreate.htmlhttp://www.1keydata.com/sql/sqldrop.htmlhttp://www.1keydata.com/sql/sqltruncate.htmlhttp://www.1keydata.com/sql/sqlinsert.htmlhttp://www.1keydata.com/sql/sqlupdate.htmlhttp://www.1keydata.com/sql/sqldelete.htmlhttp://www.1keydata.com/sql/sqlcount.htmlhttp://www.1keydata.com/sql/sqlgroupby.htmlhttp://www.1keydata.com/sql/sqlhaving.htmlhttp://www.1keydata.com/sql/sqlcreate.htmlhttp://www.1keydata.com/sql/sqldrop.htmlhttp://www.1keydata.com/sql/sqltruncate.htmlhttp://www.1keydata.com/sql/sqlinsert.htmlhttp://www.1keydata.com/sql/sqlupdate.htmlhttp://www.1keydata.com/sql/sqldelete.html


62/103

Project Report

Atomicity

Atomicity refers to the ability of the DBMS to guarantee that either all of the tasks of

a transaction are performed or none of them are. For example, the transfer of fundsfrom one account to another can be completed or it can fail for a multitude of

reasons, but atomicity guarantees that one account won't be debited if the other isnot credited.

Atomicity states that database modifications must follow an all or nothing rule.Each transaction is said to be atomic if when one part of the transaction fails, the

entire transaction fails. It is critical that the database management system maintainthe atomic nature of transactions in spite of any DBMS, operating system or

hardware failure.

Consistency

The consistency property ensures that the database remains in a consistent state

before the start of the transaction and after the transaction is over (whether

successful or not).

Consistency states that only valid data will be written to the database. If, for somereason, a transaction is executed that violates the databases consistency rules, the

entire transaction will be rolled back and the database will be restored to a stateconsistent with those rules. On the other hand, if a transaction successfully executes,

it will take the database from one state that is consistent with the rules to anotherstate that is also consistent with the rules.

Isolation

Isolation refers to the requirement that other operations cannot access or see thedata in an intermediate state during a transaction. This constraint is required to

maintain the performance as well as the consistency between transactions in aDBMS. Thus, each transaction is unaware of other transactions executing

concurrently in the system.

Durability

Durability refers to the guarantee that once the user has been notified of success,

the transaction will persist, and not be undone. This means it will survive system

failure, and that the database system has checked the integrity constraints and won'tneed to abort the transaction. Many databases implement durability by writing all

transactions into a transaction log that can be played back to recreate the system

state right before a failure. A transaction can only be deemed committed after it issafely in the log.

Durability does not imply a permanent state of the database. Another transactionmay overwrite any changes made by the current transaction without hindering

durability.

All of these ACID properties are inbuilt properties in the SQL sever 2005.

Graphical User Interface

Provide, in an organized way, t

Teleserver Prjsohan dahiya

Documents

Transcript of Teleserver Prjsohan dahiya