Teleserver Prjsohan Dahiya

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, Rohtak Meerut Road (Pallri), Near DPS, Sonepat-131001, Haryana
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 of Mrs Neetu
SHRI BALWANT INSTITUTE OF TECHNOLOGY

Approved by AICTE, Min of HRD, Govt of India & DTE, Govt of Haryana Affiliated to MD University, Rohtak Meerut Road (Pallri), Near DPS, Sonepat-131001, Haryana
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 of Master of Computer Applications (MCA), embodies the bonafide done by him/her under my supervision.
____________________
Signature of the Supervisor Place: Date:
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 of Mrs. 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
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 realtime 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 early 1980s. 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 branch of the US Company, Computer Machinery Corporation, which also no longer exists. The original product line was Key Processing(R), which was an innovative and very successful 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
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 product and 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.
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......................................................................5 0.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
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.......................................................20 3.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
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.....................................................................................................37 2.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 keeping in mind the specification of system...................................................................................90 6. Bibliography.................................................................................................................91 7. Checklist........................................................................................................................92
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 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 to computerize 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 connection requests exceeds which are handled manually. Hence computerization of application requests and customer complaints brings better satisfaction and service oriented ness .Quicker processing of application would mean better business and more customers. Proper billing, timely payments and good customer feedback go a long way in identifying and succeeding a business and it future growth. Towards this achievement the computerization of the Telecom industry will help greatly in meeting market requirements more satisfied customers would mean quicker growth and hence obviously greater profits towards which all organizations strive.
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 Internetdistributed, 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 based on the .NET Framework can integrate with any other code.
Project Report
1.2 About visual studio.net

Not part of the .NET Framework Not necessary to build or run managed code. The .NET Framework SDK includes command line compilers. A Integrated Development Environment To develop managed and unmanaged applications Supports C#, C++, Visual Basic, JavaScript, ASP, etc. Many useful tools and wizards.
Project Report
FEASIBILITY REPORT
TELESERVER
Project Report
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 in formulation 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 and Processing of new Telephone Connection requests. Receiving, Processing and routing complaints to different areas / exchanges. Updating the status of the Telephone Connections. Provides information about the services available.
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.
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.
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 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. .NET is the fast growing technology, which is being used, in day-to-day environment as the fast growing technology for developing the user-friendly applications. The applications are very much compatible to all the interfaces and can run at any operating 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 and Processing of new Telephone Connection requests. Receiving, Processing and routing complaints to different areas / exchanges. Updating the status of the Telephone Connections. Provides information about the services available.
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.
Project Report
System category Major application:

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. With more 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, 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
Project Report
0.7 Acronyms and Abbreviations

Ado.net SQL
0.8 Points of Contact

0.8.1 Information
Name SBIT Mrs. Neetu Sohan Status Sponsor Trainer Developer Organization SBIT CMC SBIT mca07137.sbit@gmail.com Contact info.sbit@gmail.com
2.7 MANAGEMENT SUMMARY 2.8 Environment
2.8.1 Organizations Involved

Project sponsor: SBIT Developer: Sohan Developer SBIT mca07137.sbit@gmail.com
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.
Project Report
The project is divided into four modules.
1) Applications:
Application Application Application Application for for for for New Phone Connection. Phone Transfer. Temporary Phone Connection. 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 database 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. of product and the customer details for future use.
2.8.4 Security
For ensuring the safety of the project, a login form is provided with the following fields: Username
10
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 to interact with each other in a convenient way which makes the system to increase its functionality. All the modules mentioned above are able to access the database of every other module.
2.8.6 Physical Environment

o o o o o Intel P- IV100 MHz or higher processor. Minimum of 128 MB RAM Display settings 800*600 on 16 bit high color. 15 MB of hard disk space. Operating system: Windows 9x/Windows XP/Windows NT.
2.9 Current Functional Procedures

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 to computerize the same for quicker, efficient results and customer satisfaction.
2.10 Functional Objectives

11
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 been set for the project. The Performance Criteria, therefore, determines the amount of work to be done. So, to increase the performance criteria it is almost always necessary 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.12 Assumptions and Constraints

12
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 separate table 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 we keep 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 a trade 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 o It is easy to use, since it uses the GUI provided in the user dialog. User friendly screens are provided.
Development time
o To
reduce the Resource Days by increasing the Resource Capability will not necessarily reduce the Total Cost because the reduction in resource days may be out weighed by the increased Resource Cost. However, improved Resource Capability will reduce the task time and there is often a delivery Time Cost associated with a project so that the cost to the organization will be less or its income improved. This is the so called 'window of opportunity' factor.
13
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. With dynamic 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 the company and their owners. The software maintain the Teleserver detail of the company. It allows the user to filter various request registered .It also allows generating 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. With more 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, and eventually 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 in terms of the calculations it can do, and more flexibility in the retrieval and storage of data.
14
Project Report
2.14.3
Time and Resource Costs
Resources are people, equipment and money. They may be internal or external and include 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 us to 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 can reduce 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 and the 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 borne in 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 then what 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
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
2.14.4.1
Impacts 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 o o o o o Intel P- IV100 MHz or higher processor. Minimum of 128 MB RAM Display settings 800*600 on 16 bit high color. 15 MB of hard disk space. Operating system: Windows 9x/Windows XP/Windows NT. 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
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 programming. staff should have a sound knowledge of C#
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(except creation 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 to enter the data and records. System failure contingencies and recovery procedures: Backup of the database is recommended in case of the system crash and data inconsistency.
2.14.4.5
Developmental Impacts
The various developmental impacts that effect the processing and functioning of the system 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
Project Report
2.14.4.6
Site or Facility Impacts
The modification in the building or office requirements has no such impacts on the project development.
2.14.4.6
Security and Privacy Impacts
Imposing the security and privacy restrict the any user other than the administrator itself 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
Project Report
Software Requirements Specification
TELESERVER
19
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 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 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 to computerize the same for quicker, efficient results and customer satisfaction.
3.1.2 Document Conventions

o o o o o All the text in this SRS is written in Times font. The headings have the font size 18. The sub-headings will have font size 14. The text is written in font size 12. Important points are written in bullets.
3.1.3Intended Audience and Reading Suggestions

o o o o o
Developers - Take into consideration the objective of the product. Project Manager - The development should take place stepwise. Users - Read the working of the project. Testers - Start building test cases while taking into consideration the product. Documentation Writer - Take a look at the perspective of document and include requirements in the given format.
20
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 and Processing of new Telephone Connection requests. Receiving, Processing and routing complaints to different areas / exchanges. Updating the status of the Telephone Connections. Provides information about the services available.
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 complicated
to use.
o
o
o o
future scope. One must register himself/herself to buy new connection. Administrator can view the details of all the members . He can edit, add and update the details of the members. Only administrator has the perMsion to view, edit, add and update the details of members. We have referred the following books:
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
o ASP.NET Complete refernece o C# Complete Reference
21
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
Project Report
3.2.2 Product Features Data flow Diagram
USER
Admin
TELESERVER
Context Diagram
23
Project Report
Data Base
New Subscriptio n
New Subscription
Subscription Details
Add subscription
Process
New Subscription DFD
Data Base
Renewal
Renewal Subscription
Subscription Details
Subscriptio n
Add Renewal subscription
Process
Renewal Subscription DFD
24
Project Report
Data Base
Change Address
Details
Change Address
Process
Record Modified
Change Address DFD
Data Base
View Subscriptio n
View Subscription
View Details
Process
View Subscription DFD
25
Project Report
Data Base
View Feed Back
View Feedback
View Details
Process
View Feed Back DFD
26
Project Report
E-R DIAGRAMS
Entity Set
Sub ID
Name
Registratio n
User
Works in relationship set
Address
3.2.4 Operating Environment

The requirements for the system to run on any system are as follows:o o o o o Intel P- IV100 MHz or higher processor. Minimum of 128 MB RAM Display settings 800*600 on 16 bit high color. 15 MB of hard disk space. Operating system: Windows XP/Windows NT.
3.2.5 Design and Implementation Constraints

o The developer must know how to use SQL Server
27
Project Report
o 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. 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 o User manuals. Online Tutorial.
3.2.7 Assumptions and Dependencies

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

3.3.1User Interfaces
o
o When the customer visits teleserver website the first page he views are the home page. When the customer views the home page he is only able to see the Services provided. When customer visit website he can also view all the modules defined in the project. If he wants to buy new connection he will have to first register himself through the New Application page. When he registered himself so he can authority to buy the product of his choice. 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. The Administrator is able to view the bill details after clicking on the bill details.
o o
o o
3.3.2 Hardware Interfaces

The requirements for the system to run on any system are as follows:o o o o Intel P- IV100 MHz or higher processor. Minimum of 128 MB RAM Display settings 800*600 on 16 bit high color. 15 MB of hard disk space.
28
Project Report
Operating system: Windows 9x/Windows XP/Windows NT.
3.3.3 Software Interfaces

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

o o o This business networking site can be used in any web browser but we have used only Internet Explorer. The communication standard used is HTTP. 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 been set for the project. The Performance Criteria, therefore, determines the amount of work to be done. So, to increase the performance criteria it is almost always necessary 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 o o The operating system used must be licensed. LAN connection must have 256 mbps speed. Antivirus must be installed to avoid spywares and malwares.
3.4.3 Security Requirements

29
Project Report
o o o o
The product is provided security with the help of a password. If the user name and password did not match with the same stored inside the database then an error message will be displayed. The password will certainly contain a special character otherwise it will not be accepted. The server room will be provided sufficient security.
3.4.4 Software Quality Attributes

o o o o o o The product is able to adapt in any environment. It is available freely. It is flexible to use as can be used on any browser. Easily maintained. It is portable as you dont need any additional software to use it. You will need only a LAN connection. 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. 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 Teleserver
o o
in a better way. This document can be used as a user manual or user guide to the software. 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
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 which
the customers can view all the details of telecommunications and can register themselves online and becoming the member.The payment should be through credit card only. 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 o It will have 2 text boxes for user name and password. 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 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

o o Inside the new application page some of the text boxes are there for keeping the overall details of the members. There is a text box to write messages. 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
Project Report
2.2.1 Assumptions and Dependencies

Describe any assumptions or dependencies regarding the software and its use. These may 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 o o o o Intel P- IV100 MHz or higher processor. Minimum of 128 MB RAM Display settings 800*600 on 16 bit high color. 15 MB of hard disk space. IBM PC Keyboard.
Operating system used must be a Windows environment as .net applications basically 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 be HTTP. 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
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 great aid in communication. 4.2.4
Development Methods
SDLC of a project is defined as the duration of time that starts with the conceptualization 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 and that we used for developing this project is
33
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 o o o Application Entries Enquiry Complaints
Hardware Used o o o o o Intel P- IV100 MHz or higher processor. Minimum of 128 MB RAM Display settings 800*600 on 16 bit high color. 15 MB of hard disk space. IBM PC Keyboard.
Error detection and recovery
34
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 SqlCeException class
Description When an error occurs, an instance of theSqlCeException class is created that contains the collection of SqlCeError objects. The SqlCeErrorCollection object contains one or more SqlCeError objects for aSqlCeException object. The collection can be accessed using the SqlCeException.Errorsproperty. Each SqlCeError object contains an array of error parameters that provide detailed information about the error.
SqlCeErrorCollectionclass
SqlCeError class
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
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 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 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 his problems.
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
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 the company.
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 of modules 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 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 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 loging in through this page only.
37
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 described carefully in the following sections.
cancel Table :
2.5.6.1 Name table

Description Attribute
of
the
Cancel
This table describes the information about to cancel the network connection. Description Type
2.5.6.2 Exam
ple of value s
Reg Fathername Name Peraddress
Registration number . Father name the customer.
Int of Varchar(2000) Varchar(2000)
Any number. Any text. Any text Any text
Name of customer Address of customer
the Varchar(2000)
38
Project Report
Corraddress
Corraspondance Varchar(2000) address of the customer varchar(2000) Dob of customer Phone number Date cancellation Nationality Reg varchar(2000) Varchar(2000) of Varchar(2000) Varchar(2000)
Any text
Email Dob contact Canceldate Nationality
Any text Any text Any text Any text Any text
2.5.6.3 Primary Key 2.5.6.4 Foreign Keys 2.5.6.5 SQL Code
CREATE TABLE [dbo].[cancel]( [reg] [int] IDENTITY(2000,1) NOT NULL, [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 SQL_Latin1_General_CP1_CI_AS NULL, [corraddress] [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 SQL_Latin1_General_CP1_CI_AS NULL, [canceldate] [varchar](2000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [nationality] [varchar](2000) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ) ON [PRIMARY]
Tables data: Here we have shown the various tables-
39
Project Report
Viewbill1: 2.5.6.6 Name table

of
the
Viewbill1
This table describes the information about to viewbill the network connection. Description Type
2.5.6.7 Exam
ple of value s
registration Jan Feb March April Mayw June July Aug Sep Oct Nov Dec
Identity Name of month Name of month Name of month Name of month Name of month Name of month Name of month Name of month Name of month Name of month Name of month Name of month
Int Int Int Int Int Int Int Int Int Int Int Int Int
Any number. January February March April May June July August September October November December
40
Project Report
Registration
CREATE TABLE [dbo].[viewbill1]( [registration] [int] NOT NULL, [jan] [int] NULL CONSTRAINT [def_tel] DEFAULT (NULL), [feb] [int] NULL CONSTRAINT [def_tel1] DEFAULT (NULL), [march] [int] NULL CONSTRAINT [def_tel2] DEFAULT (NULL), [april] [int] NULL CONSTRAINT [def_tel3] DEFAULT (NULL), [may] [int] NULL CONSTRAINT [def_tel4] DEFAULT (NULL), [june] [int] NULL CONSTRAINT [def_tel5] DEFAULT (NULL), [july] [int] NULL CONSTRAINT [def_tel6] DEFAULT (NULL), [aug] [int] NULL CONSTRAINT [def_tel7] DEFAULT (NULL), [sep] [int] NULL CONSTRAINT [def_tel8] DEFAULT (NULL), [oct] [int] NULL CONSTRAINT [def_tel9] DEFAULT (NULL), [nov] [int] NULL CONSTRAINT [def_tel10] DEFAULT (NULL), [december] [int] NULL CONSTRAINT [def_tel11] DEFAULT (NULL), PRIMARY KEY CLUSTERED ( [registration] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY]
CREATE TABLE [dbo].[viewbill1]( [registration] [int] NOT NULL, [jan] [int] NULL CONSTRAINT [def_tel] DEFAULT (NULL), [feb] [int] NULL CONSTRAINT [def_tel1] DEFAULT (NULL), [march] [int] NULL CONSTRAINT [def_tel2] DEFAULT (NULL), [april] [int] NULL CONSTRAINT [def_tel3] DEFAULT (NULL), [may] [int] NULL CONSTRAINT [def_tel4] DEFAULT (NULL), [june] [int] NULL CONSTRAINT [def_tel5] DEFAULT (NULL), [july] [int] NULL CONSTRAINT [def_tel6] DEFAULT (NULL),
41
Project Report
[aug] [int] NULL CONSTRAINT [def_tel7] DEFAULT (NULL), [sep] [int] NULL CONSTRAINT [def_tel8] DEFAULT (NULL), [oct] [int] NULL CONSTRAINT [def_tel9] DEFAULT (NULL), [nov] [int] NULL CONSTRAINT [def_tel10] DEFAULT (NULL), [december] [int] NULL CONSTRAINT [def_tel11] DEFAULT (NULL), PRIMARY KEY CLUSTERED ( [registration] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY]
Viewbill:
CREATE TABLE [dbo].[viewbill]( [registration] [int] NOT NULL, [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, PRIMARY KEY CLUSTERED ( [registration] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY]
42
Project Report
Feedback:
CREATE TABLE [dbo].[feedback]( [reg] [varchar](2000) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [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, PRIMARY KEY CLUSTERED ( [reg] ASC )WITH (PAD_INDEX = OFF, IGNORE_DUP_KEY = OFF) ON [PRIMARY] ) ON [PRIMARY]
2.5.6.11 Name the table

of
Feedback
This table describes the information about to feedback the network connection. Description Type
2.5.6.12
E xamp le of value s
Reg Email Rate Satisfaction
Identity Email id Rate Satisfaction
Varchar(2000) Varchar(2000) Varchar(2000) Varchar(2000)
Any number. Any text Any Text Any Text
43
Project Report
Reg
Mastertable:
CREATE TABLE [dbo].[mastertable]( [reg] [int] IDENTITY(22345,1) NOT NULL, [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]

Description
of
Feedback
This table describes the information about to feedback the network connection.
44
Project Report
Attribute
Description
Type
2.5.6.17
Reg
Identity Name of customer Father name customer Male or female Address Correspond address
Int Varchar(255)
Any number. Any text Any Text Any Text Any text Any text Any text Any text Any text Any text Any text Any text
Name Fathername Gender Peraddress Corraddress Email Dob Contact Regdate Nationality Pwd
of Varchar(255) Varchar(7) Varchar(255) Varchar(255)
Email address of Varchar(255) customer Date of birth Contact number Reg date Indian country Password Varchar(255) Varchar(20) Varchar(20) or Varchar(20) Varchar(40)
45
Project Report
Reg
Phonetransfer:
CREATE TABLE [dbo].[phonetransfer]( [id] [int] IDENTITY(2000,1) NOT NULL, [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 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
Project Report

of
Phonetransfer
This table describes the information about to phone transfer the network connection. Description Type
2.5.6.22
Id
Int Varchar(2000)
Any number. Any text Any Text Any Text Any text Any text Any text Any text Any text Any text Any text Any text Any text Any text
newname newFathername Gender Peraddress Corraddress Email Dob Contact Regdate Nationality Pwd Oldname oldfather
Email address of Varchar(2000) customer Date of birth Contact number Reg date Indian country Password Old name Old father name Varchar(2000) Varchar(2000) Varchar(2000) or Varchar(2000) Varchar(2000) Varchar(2000) Varchar(2000)
47
Project Report
Id
CREATE TABLE [dbo].[phonetransfer]( [id] [int] IDENTITY(2000,1) NOT NULL, [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 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]
Tempcon:
CREATE TABLE [dbo].[tempcon]( [id] [int] IDENTITY(1000,1) NOT NULL, [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 SQL_Latin1_General_CP1_CI_AS NULL,
48
Project Report
[corresaddress] [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 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]

of
Tempcon
This table describes the information about to temp connection the network connection. Description Type
2.5.6.27
Id
Int Varchar(2000)
Any number. Any text Any Text Any Text Any text Any text Any text Any text Any text Any text Any text
Name Fathername Gender Peraddress Corraddress Email Dob Contact Regdate Nationality
Email address of Varchar(2000) customer Date of birth Contact number Reg date Indian Varchar(2000) Varchar(2000) Varchar(2000) or Varchar(2000)
49
Project Report
country Pwd Password Id Varchar(2000) Any text
CREATE TABLE [dbo].[tempcon]( [id] [int] IDENTITY(1000,1) NOT NULL, [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 SQL_Latin1_General_CP1_CI_AS NULL, [corresaddress] [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 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
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
SELECT "column_name" FROM "table_name" WHERE "column_name" IN ('value1', 'value2', ...)
Between
SELECT "column_name" FROM "table_name" WHERE "column_name" BETWEEN 'value1' AND 'value2'
Like
SELECT "column_name" 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
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
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 funds from 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 is not 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 maintain the 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 some reason, 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 state consistent 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 another state that is also consistent with the rules.
Isolation
Isolation refers to the requirement that other operations cannot access or see the data in an intermediate state during a transaction. This constraint is required to maintain the performance as well as the consistency between transactions in a DBMS. 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't need 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 is safely in the log. Durability does not imply a permanent state of the database. Another transaction may 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, the pictures of all the forms in the graphical user interface with a reference to the functional requirement it implements. You may use html to present the graphical user interfaces.
53
Project Report
For each form in the graphical user interface, provide: o o o The names of the controls and fields on that form, The names of the events, methods, or procedures that cause that form to be displayed, and The names of the events, methods, or procedures triggered by each control.
Coding
We have divided our project into different modules:
Admin:
using using using using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Data.SqlClient;
public partial class Admin : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "select m.name,m.reg from mastertable3 m"; SqlCommand cmd = new SqlCommand(query, con); SqlDataReader dr = cmd.ExecuteReader(); GridView1.DataSource = dr; GridView1.DataBind(); con.Close(); } protected void Button1_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString);
54
Project Report
con.Open(); string query; query = "create table "+TextBox1.Text+TextBox2.Text+"(year varchar(2000),months varchar(2000),bill varchar(2000),noc varchar(2000))"; SqlCommand cmd = new SqlCommand(query,con); int i= cmd.ExecuteNonQuery(); if (i < 0) { System.Windows.Forms.MessageBox.Show("Data inserted"); } else { System.Windows.Forms.MessageBox.Show("Already exist"); } con.Close(); } }
AppCancel:
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; public partial class Default9 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open();
55
Project Report
string query; query = "select reg from mastertable3 "; SqlCommand cmd = new SqlCommand(query,con); SqlDataReader dr =cmd.ExecuteReader(); //cmd.ExecuteNonQuery(); //con.Close(); //Response.Redirect("Default.aspx?name=" + TextBox1.Text + "&fathername=" + TextBox2.Text); } }
Application:
using using using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq;
public partial class Default6 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void LinkButton1_Click(object sender, EventArgs e) { Response.Redirect("AppNewCon.aspx"); } protected void LinkButton2_Click(object sender, EventArgs e) { //Response.Redirect("Login.aspx?name2=" + "complaints"); Response.Redirect("Login.aspx?name2=" + "AppPhoneTr" ); } protected void LinkButton3_Click(object sender, EventArgs e) { Response.Redirect("AppTempConn.aspx"); } protected void LinkButton4_Click(object sender, EventArgs e) {
56
Project Report
} }
//Response.Redirect("AppCancel.aspx"); Response.Redirect("Login.aspx?name3=" + "AppCancel");
AppNewCon:
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; using System.Data.OleDb; using System.Data.SqlClient; public partial class Default7 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "insert into mastertable3 values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + RadioButtonList1.SelectedItem.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox8.Text + "','" + DropDownList2.SelectedItem.Text + "','" + TextBox9.Text + "')"; SqlCommand cmd = new SqlCommand(query, con); if (cmd.ExecuteNonQuery() > 0) { System.Windows.Forms.MessageBox.Show("Data inserted successfully"); } con.Close(); Response.Redirect("Default.aspx?name=" + TextBox1.Text + "&fathername=" + TextBox2.Text); }
57
Project Report
protected void TextBox4_TextChanged(object sender, EventArgs e) { } protected void TextBox3_TextChanged(object sender, EventArgs e) { } }
AppPhoneTr:
public partial class Default8 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "insert into phonetransfer values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + TextBox9.Text + "','" + TextBox10.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox11.Text + "','" + DropDownList2.SelectedItem.Text + "','" + TextBox8.Text + "','" + RadioButtonList1.SelectedItem.Text + "')"; SqlCommand cmd = new SqlCommand(query, con);
58
Project Report
if (cmd.ExecuteNonQuery() > 0) { System.Windows.Forms.MessageBox.Show("Data inserted successfully"); } con.Close(); Response.Redirect("Default.aspx?name=" + TextBox1.Text + "&fathername=" + TextBox2.Text); } }
AppTempConn:
public partial class Default10 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "insert into tempcon values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + RadioButtonList1.SelectedItem.Text + "','" + TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + TextBox7.Text + "','" + TextBox9.Text + "','" + DropDownList2.SelectedItem.Text + "','" + TextBox8.Text + "')";
59
Project Report
SqlCommand cmd = new SqlCommand(query, con); if (cmd.ExecuteNonQuery() > 0) { System.Windows.Forms.MessageBox.Show("Data inserted successfully"); } con.Close(); Response.Redirect("Default.aspx?name=" + TextBox1.Text + "&fathername=" + TextBox2.Text); } }
Complaintregno:
public partial class complaintregno : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "select regno,complainttype from complaint"; SqlCommand cmd = new SqlCommand(query, con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) { Label1.Text = dr[0].ToString(); Label2.Text = dr[1].ToString(); } con.Close(); //Response.Redirect("complaintregno.aspx?name=" + TextBox1.Text ); } }
60
Project Report
Default:
using using using using using using using using using using using using using using using System; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Data.SqlClient ; System.Data.OracleClient; System.Data.OleDb; System.Data.SqlClient;
public partial class _Default : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); SqlCommand cmd = new SqlCommand("select reg from mastertable3 ", con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) { Label1.Text = dr[0].ToString(); } Label4.Text = Request.QueryString["name"]; Label5.Text = Request.QueryString["fathername"]; } }
Default3:
using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web;
61
Project Report
using using using using using using
System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq;
public partial class Default3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("Application.aspx"); } protected void Button3_Click1(object sender, EventArgs e) { // Response.Redirect("Login.aspx"); Response.Redirect("Login.aspx?name1=" +"viewbill");
} protected void Button6_Click(object sender, EventArgs e) { // Response.Redirect("Feedback.aspx"); Response.Redirect("Login.aspx?name4=" + "Feedback"); } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("Login.aspx"); }
Default8:
using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls;
62
Project Report
using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.SqlClient; public partial class Default8 : System.Web.UI.Page { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); protected void Page_Load(object sender, EventArgs e) { } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { con.Open(); string query; query = "insert into complaint (regno,complainttype) values ('" + TextBox2.Text + "','" + DropDownList1.SelectedItem.Text + "')"; SqlCommand cmd = new SqlCommand(query, con); if (cmd.ExecuteNonQuery() > 0) { System.Windows.Forms.MessageBox.Show("Complaint registered"); } con.Close(); //Response.Redirect("complaintregno.aspx?name=" + TextBox1.Text ); } protected void TextBox2_TextChanged(object sender, EventArgs e) { //SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; string pd; pd = Request.QueryString["pwd"]; query = "select reg from mastertable3 where pwd='"+pd+"'"; SqlCommand cmd = new SqlCommand(query, con); SqlDataReader dr= cmd.ExecuteReader(); while (dr.Read()) { //Response.Write(dr[0].ToString()); if (TextBox2.Text == dr[0].ToString()) { TextBox2.Text = dr[0].ToString(); } else { TextBox2.Text = "";
63
Project Report
System.Windows.Forms.MessageBox.Show("Registration number is not valid"); } con.Close(); } } }
Enquiry:
public partial class Default12 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void LinkButton1_Click(object sender, EventArgs e) { Response.Redirect("Login.aspx"); } protected void LinkButton2_Click(object sender, EventArgs e) { Response.Redirect("Login.aspx"); } protected void LinkButton3_Click(object sender, EventArgs e) { Response.Redirect("Login.aspx"); } protected void LinkButton4_Click(object sender, EventArgs e) { Response.Redirect("Login.aspx"); }
64
Project Report
Feedback:
public partial class Default10 : System.Web.UI.Page { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); protected void Page_Load(object sender, EventArgs e) { } protected void RadioButton4_CheckedChanged(object sender, EventArgs e) { } protected void Button5_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "insert into feedback1 values('" + TextBox4.Text + "','" + TextBox3.Text + "','" + RadioButtonList1.SelectedItem.Text + "','" + RadioButtonList2.SelectedItem.Text + "')"; SqlCommand cmd = new SqlCommand(query, con); if (cmd.ExecuteNonQuery() > 0) { System.Windows.Forms.MessageBox.Show("Thank you"); } con.Close(); Response.Write("Your feedback has been submitted"); }
65
Project Report
protected void TextBox4_TextChanged(object sender, EventArgs e) { //System.Windows.Forms.MessageBox.Show("Registration number is not valid"); //SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; // string pd; // pd = Request.QueryString["pwd"]; query = "select reg from mastertable3 where pwd='" + Request.QueryString["pwd"] + "'"; // query = "select reg from mastertable3 where pwd=9"; //System.Windows.Forms.MessageBox.Show(query ); SqlCommand cmd = new SqlCommand(query, con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) { //Response.Write(dr[0].ToString()); if (TextBox4.Text == dr[0].ToString()) { TextBox4.Text = dr[0].ToString(); } else { TextBox4.Text = ""; System.Windows.Forms.MessageBox.Show("Registration number is not valid"); } con.Close(); } } }
Login:
using using using using System; System.Collections; System.Configuration; System.Data;
66
Project Report
using using using using using using using using using using using
System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.HtmlControls; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts; System.Xml.Linq; System.Data.OleDb; System.Data.OracleClient; System.Data.SqlClient;
public partial class Default12 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void ImageButton2_Click(object sender, ImageClickEventArgs e) { string str=Request .QueryString ["name"]; string str1=Request .QueryString ["name1"]; string str2 = Request.QueryString["name2"]; string str3 = Request.QueryString["name3"]; string str4 = Request.QueryString["name4"]; if (DropDownList1.SelectedItem.Text =="User") { if (str2 == "AppPhoneTr") { Response.Redirect("AppPhoneTr.aspx"); } if (str3 == "AppCancel") { Response.Redirect("AppCancel.aspx"); } if (str4 == "Feedback") { Response.Redirect("Feedback.aspx?pwd="+TextBox5.Text); } if (str == "complaints") { Response.Redirect("default8.aspx?pwd="+TextBox5.Text); } if (str1 == "viewbill") { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query;
67
Project Report
query = "select m.name from mastertable3 m where m.name='" + TextBox4.Text + "'and m.pwd='" + TextBox5.Text + "'"; SqlCommand cmd = new SqlCommand(query, con); SqlDataReader dr = cmd.ExecuteReader(); if (!dr.Read()) { Label1.Text = "Name & password is not valid"; } else { Response.Redirect("ViewBill.aspx"); } } } if (DropDownList1.SelectedItem.Text == "Administrator") { if (TextBox4.Text == "Administrator" && TextBox5.Text == "admin") { Response.Redirect("Admin.aspx"); } } } protected void LinkButton1_Click(object sender, EventArgs e) { } protected void LinkButton2_Click(object sender, EventArgs e) { // Response.Redirect(); } protected void LinkButton3_Click(object sender, EventArgs e) { Response.Redirect("forgot_pwd.aspx"); }
MasterPage:
using using using using using using using using using using System; System.Collections; System.Configuration; System.Data; System.Linq; System.Web; System.Web.Security; System.Web.UI; System.Web.UI.WebControls; System.Web.UI.WebControls.WebParts;
68
Project Report
using System.Web.UI.HtmlControls; using System.Xml.Linq; public partial class MasterPage : System.Web.UI.MasterPage { protected void Page_Load(object sender, EventArgs e) { } protected void Button2_Click(object sender, EventArgs e) { Response.Redirect("Home.aspx"); } protected void Button3_Click(object sender, EventArgs e) { Response.Redirect("Services.aspx"); } protected void Button4_Click(object sender, EventArgs e) { //Response.Redirect("default4.aspx"); } protected void ImageButton1_Click(object sender, ImageClickEventArgs e) { Response.Redirect("http://www.google.com"); } protected void Button1_Click(object sender, EventArgs e) { //Response.Redirect("complaintregno.aspx ); Response.Redirect("Login.aspx?name=" +"complaints"); } }
Serveces:
public partial class Default3 : System.Web.UI.Page
69
Project Report
{ protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { Response.Redirect("Application.aspx"); } protected void Button3_Click1(object sender, EventArgs e) { Response.Redirect("Login.aspx"); } protected void Button5_Click(object sender, EventArgs e) { } }
Services:
public partial class Default3 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button1_Click(object sender, EventArgs e) { } Response.Redirect("Application.aspx");
70
Project Report
protected void Button3_Click1(object sender, EventArgs e) { Response.Redirect("Login.aspx"); } protected void Button5_Click(object sender, EventArgs e) { Response.Redirect("Enquiry.aspx"); } protected void Button2_Click(object sender, EventArgs e) { } protected void Button4_Click(object sender, EventArgs e) { } protected void Button6_Click(object sender, EventArgs e) { Response.Redirect("Feedback.aspx"); } }
Tempregistration:
public partial class tempregistration : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); SqlCommand cmd = new SqlCommand("select reg from tempcon ", con); SqlDataReader dr = cmd.ExecuteReader(); while (dr.Read()) {
71
Project Report
} }
Label1.Text = dr[0].ToString(); } Label4.Text = Request.QueryString["name"]; Label5.Text = Request.QueryString["fathername"];
ViewBill:
using System; using System.Collections; using System.Configuration; using System.Data; using System.Linq; using System.Web; using System.Web.Security; using System.Web.UI; using System.Web.UI.HtmlControls; using System.Web.UI.WebControls; using System.Web.UI.WebControls.WebParts; using System.Xml.Linq; using System.Data.OleDb; using System.Data.OracleClient; using System.Windows.Forms; using System.Data.SqlClient; public partial class Default11 : System.Web.UI.Page { protected void Page_Load(object sender, EventArgs e) { } protected void Button5_Click(object sender, EventArgs e) { SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["con"].ConnectionString); con.Open(); string query; query = "select m.name,m.reg,b.month,b.year,b.bill,b.noc from mastertable3 m,"+TextBox2.Text+TextBox3.Text+" b where m.name='"+TextBox2.Text+"' and b.month='"+DropDownList2.SelectedItem.Text+"'"; //SqlCommand cmd = new SqlCommand(query, con); //SqlDataReader dr = cmd.ExecuteReader(); //GridView1.DataSource = dr; //GridView1.DataBind(); //con.Close(); try { SqlCommand cmd = new SqlCommand(query, con);
72
Project Report
SqlDataReader dr = cmd.ExecuteReader(); GridView1.DataSource = dr; GridView1.DataBind(); con.Close();
} }
catch (Exception exw) { System.Windows.Forms.MessageBox.Show(exw.Message); }
Web.Config:
<?xml version="1.0"?> <!-Note: As an alternative to hand editing this file you can use the web admin tool to configure settings for your application. Use the Website->Asp.Net Configuration option in Visual Studio. A full list of settings and comments can be found in machine.config.comments usually located in \Windows\Microsoft.Net\Framework\v2.x\Config --> <configuration> <configSections> <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePerMsion="false" allowDefinition="MachineToApplication"/> <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePerMsion="false" allowDefinition="Everywhere"/> <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection,
73
Project Report
System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePerMsion="false" allowDefinition="MachineToApplication"/> <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePerMsion="false" allowDefinition="MachineToApplication"/> <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePerMsion="false" allowDefinition="MachineToApplication"/> </sectionGroup> </sectionGroup> </sectionGroup> </configSections> <appSettings/> <connectionStrings> <add name="con" connectionString="data source=MASTER0E8ED16C\SQLEXPRESS;integrated security=yes;database=piyush"/> </connectionStrings> <system.web> <!-Set compilation debug="true" to insert debugging symbols into the compiled page. Because this affects performance, set this value to true only during development. --> <compilation debug="true"> <assemblies> <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Data.OracleClient, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/> <add assembly="System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/></assemblies> </compilation> <!-The <authentication> section enables configuration of the security authentication mode used by ASP.NET to identify an incoming user. --> <authentication mode="Windows"/>
74
Project Report
<!-The <customErrors> section enables configuration of what to do if/when an unhandled error occurs during the execution of a request. Specifically, it enables developers to configure html error pages to be displayed in place of a error stack trace. <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm"> <error statusCode="403" redirect="NoAccess.htm" /> <error statusCode="404" redirect="FileNotFound.htm" /> </customErrors> --> <pages> <controls> <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </controls> </pages> <httpHandlers> <remove verb="*" path="*.asmx"/> <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false"/> </httpHandlers> <httpModules> <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </httpModules> </system.web> <system.codedom> <compilers> <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"> <providerOption name="CompilerVersion" value="v3.5"/> <providerOption name="WarnAsError" value="false"/> </compiler>
75
Project Report
<compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"> <providerOption name="CompilerVersion" value="v3.5"/> <providerOption name="OptionInfer" value="true"/> <providerOption name="WarnAsError" value="false"/> </compiler> </compilers> </system.codedom> <!-The system.webServer section is required for running ASP.NET AJAX under Internet Information Services 7.0. It is not necessary for previous version of IIS. --> <system.webServer> <validation validateIntegratedModeConfiguration="false"/> <modules> <remove name="ScriptModule"/> <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </modules> <handlers> <remove name="WebServiceHandlerFactory-Integrated"/> <remove name="ScriptHandlerFactory"/> <remove name="ScriptHandlerFactoryAppServices"/> <remove name="ScriptResource"/> <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </handlers> </system.webServer> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> <dependentAssembly>
76
Project Report
<assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0"/> </dependentAssembly> </assemblyBinding> </runtime> </configuration>
77
Project Report
OUTPUT
Home page
78
Project Report
Services page
Applications page
79
Project Report
Application for new connection
80
Project Report
Application for phone transfer
Application for new temporary connection
81
Project Report
Application for cancellation
82
Project Report
Forgot password
83
Project Report
Application for new temporary connection
84
Project Report
Pay bill
Feedback page
Contact us
85
Project Report
Application for new connection
86
Project Report
Telephone complaints
Bill payment
87
Project Report
Enquiry Page
88
Project Report
Login page
89
Project Report
3 Conclusion
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 keeping in mind the specification of system. The Following features are present in the project: 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.
90
Project Report
6. Bibliography
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.
o Francesco Balena. Programming Microsoft Visual C# 2005. o Jesse Liberty. Visual C# 2005: A developers notebook.
References: General Visual C# Help, Tutorials and Examples: Microsoft Visual Studio.NET Documentation
Websites: General Visual C# Help, Tutorials and Examples:
http://msdn.microsoft.com/vcsharp http://www.microsoft.com/net/default.asp http://www.csharphelp.com/ http://www.c-sharpcorner.com/ http://www.csharphelp.com/ http://www.mastercsharp.com/ http://www.codeproject.com/csharp/ http://www.codehound.com/csharp/
91
Project Report
Checklist
This checklist is to be attached as the last page of the report. This checklist is to be duly completed by the student and verified by the Supervisor, Project Coordinator and HOD
1.
Is the report properly hard bound?
Yes / No
2.
Is the Cover page (on hard bound cover) in proper format?
Yes / No
3.
Is the Title page (Inner cover page) in proper format?
Yes / No
4.
(a) Is the Certificate from the Supervisor in proper format? (b) Has it been signed by the Supervisor?
Yes / No Yes / No Yes / No
5.
(a)
Is the Acknowledgement from the Student in proper
format? (b) Has it been signed by the Student? 7. Does the Table of Contents include page numbers? (i). (ii). (iii). (iv). (v). 8. Are the Pages numbered properly? Are the Figures numbered properly? Are the Tables numbered properly? Are the Captions for the Figures and Tables proper? Are the Appendices numbered properly? Yes / No Yes / No Yes / No Yes / No Yes / No Yes / No Yes / No
Is the conclusion of the Report based on discussion of the work?
9.
Are References or Bibliography given in the Report? Have the References been cited inside the text of the Report?
Yes / No Yes / No
92
Project Report
Is the citation of References in proper format?
Yes / No
10.
A Compact Disk (CD) containing the softcopy of the Final Report (preferably in PDF format) and a Final Project Presentation in MS power point only (made to the Supervisor / Examiner has been placed in a protective jacket securely fastened to the inner back cover of the Final Report. Write the name and Roll No on the CD.
Yes / No
Declaration by Student
I certify that I have properly verified all the items in the checklist and ensure that the report is in proper format as specified in the course handout.
Name: Place: Date: Signature of the Student:
Verification by Supervisor
I have duly verified all the items in the checklist and ensured that the report is in proper format. Name: Place: Date: Signature of the Supervisor:
93
Project Report
Verification by Project Coordinator

I have duly verified all the items in the checklist and ensured that the report is in proper format. Name: Place: Date: Signature of the Project Coordinator:
Verification by Head of Department (HOD)

I have duly verified all the items in the checklist and ensured that the report is in proper format. Name: Place: Date: Signature of the HOD:
94

Teleserver Prjsohan Dahiya

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Teleserver Prjsohan Dahiya

Загружено:

Авторское право:

Доступные форматы

Teleserver

Master of Computer Applications(MCA)

Sohan Singh 469472

SHRI BALWANT INSTITUTE OF TECHNOLOGY

Master of Computer Applications(MCA)

Sohan Singh 469472

under the Supervision of Mrs Neetu

SHRI BALWANT INSTITUTE OF TECHNOLOGY

____________________ Signature of the Student Name: Sohan Singh Date: 07/07/2010

Why we choose Teleserver

0.1 About .net

1.1.1Overview of .net framework

1.2 About visual studio.net

Feasibility Report 2.0 GENERAL INFORMATION

0.3 Five common factors (TELOS)

0.3.2 Economic feasibility

0.3.3 Legal feasibility

0.3.4 Operational feasibility

0.3.5 Schedule feasibility

0.5 System Overview

System name or title

System category Major application:

System environment or special conditions

0.6 Project References

References: Book References

Microsoft Visual Studio.NET Documentation

Web References www.google.co.in www.c-sharpcorner.com/ www.mastercsharp.com/

0.7 Acronyms and Abbreviations

0.8 Points of Contact

2.7 MANAGEMENT SUMMARY 2.8 Environment

2.8.1 Organizations Involved

User: Administrator/Authenticated User

2.8.2 Input/ Output

The project is divided into four modules.

2.8.5 System Interaction

2.8.6 Physical Environment

2.9 Current Functional Procedures

2.10 Functional Objectives

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

2.11 Performance Objectives

2.12 Assumptions and Constraints

2.14 Evaluation Criteria

2.14 PROPOSED SYSTEM

Time and Resource Costs

Impacts Equipment Impacts

Various operational impacts are categorized as:

Site or Facility Impacts

Security and Privacy Impacts

Software Requirements Specification

1 Requirement Specification 3.1 Introduction

3.1.2 Document Conventions

3.1.3Intended Audience and Reading Suggestions

3.1.4 Project Scope Objectives:

o ASP.NET Complete refernece o C# Complete Reference

3.2 Overall Description

3.2.2 Product Features Data flow Diagram

New Subscription DFD

Add Renewal subscription

Renewal Subscription DFD

Change Address DFD

View Subscription DFD

View Feed Back