The History Of Smart Phone Tele Systems

Published Date: 02 Nov 2017

The project addresses the development of a system of information management and automate the processes of an organization working in the field of telecommunications. Existing information systems are maintained through books and files. The system is operated. The system makes use of conventional methods of data management. It is difficult to provide the necessary information about customers and the phone receives efficient. The information is also difficult. Often, data is mishandled and this leads to loss of data.

proposed system is a web-based application. The system maintains a central repository of all information. This makes it possible to maintain the data. It's actually very easy to search all data and implement effective. The system allows the generation of reports. The system can be readily accessed and used by end users and personnel by using interfaces. In order to provide flexibility to the users, we have developed interfaces accessible through a browser. These interfaces help administrators all States transactional data such as insertion, data extraction and update, along with the extensive data search capabilities. The user interface also operating common helps users in managing their own information in a personalized way, according to the flexibility included.

CONTENTS:

1.Introduction....................................................................................................4

1.1 Introduction and objective..................................................................4

1.2 Existing system.....................................................................................4

1.3 Proposed system...................................................................................4

2.Study of the system........................................................................................4

2.1 Input& Output Representation..........................................................4

2.1.1 Input stage...................................................................................5

2.1.2 Input type...................................................................................5

2.1.3 Input media................................................................................5

2.1.4 Output design.............................................................................5

2.1.5 Output definition.......................................................................6

2.1.6 Output media.............................................................................6

3.Process model................................................................................................7

3.1 Software Development Life Cycle.....................................................7

3.1.1 Requirement Stage....................................................................7

3.1.2 Analysis Stage...........................................................................7

3.1.3 Designing Stage.........................................................................7

3.1.4 Development Stage...................................................................8

3.1.5 Integration and Testing Stage.................................................8

3.1.6 Installation &Acceptance test...................................................8

4.Feasibility Study..........................................................................................9

4.1 Technical Feasibility..........................................................................9

4.2 Operational Feasibility......................................................................9

4.3 Economic Feasibility........................................................................10

5.Functional Requirements Specification...................................................10

5.1 Performance Requirements.............................................................10

5.2 Software Requirements....................................................................10

5.3 Hardware Requirements..................................................................11

5.4 Java Architecture..............................................................................11

6.Testing........................................................................................................11

6.1 Testing Strategies..............................................................................12

7.System Security..........................................................................................13

7.1Security in Software..........................................................................13

8.Conclusion..................................................................................................14

9.References...................................................................................................14

1.Introduction:

INTRODUCTION & OBJECTIVE

The goal of the project is to develop a system for the management of information and to automate the processes of an organization that works in the field of telecommunications. The aim is to design a system that allows one to perform its functions effectively.

EXISTING SYSTEM

On current information kept in books and files. The system is operated manually. The system uses conventional methods of data management. It is difficult to retrieve the necessary data about customers and phone connections effectively. Generation of reports is also difficult. Often the data mismanagement and this leads to data loss.

PROPOSED SYSTEM

The proposed system is a web-based application. The system maintains a central repository for all information. This allows you to save the data. Effective information is very easy to search and perform all the functions effectively. The system allows you to make your own.

2. STUDY OF THE SYSTEM

1. Flexibility for users, these interfaces have been developed which can be accessed through a browser. The graphical user interface at the highest level have been identified as an administrative user

2. The user interface or generic operating

The "administrative user interface" focuses on consistent data that is practical, part of the activities of the organization, and that a good authentication for collecting the necessary data. These interfaces help administrators all States transactional, such as insertion, deletion and updation date data, together with the extensive data search capabilities.

The 'user interface operating or generic' helps end users transaction system through existing data and services required. The user interface also operating common helps users in managing their own information in a personalized way, according to the flexibility included

2.1 INPUT & OUTPOUT REPRESENTETION

Design entry is part of the overall system. The main objective in the input design is as follows:

• If you produce a cost effective method of entry.

• To reach. Highest accuracy

• To ensure that the item is acceptable and understandable for the user.

2.1.1 Input Stages:

The main input stages can be listed as below:

Data recording

Data transcription

Data conversion

Data verification

Data control

Data transmission

Data validation

Data correction

2.1.2 Input Types:

You must define the different types of items. Tickets can be categorized as follows:

• External inputs, which are the main input for the system.

• The internal user inputs that are communicating with the system.

• Operationally, the communication of the department in the system?

• Interactive, inputs that are introduced during the dialogue.

2.1.3 Input Media:

At this stage of choice has to be made about the input media. To conclude on the entrance exam of the media has to be given to;

• Input Type

• Format flexibility

• speed

• Accuracy

• Methods for testing

• Rejection rates

• Ease of correction

• Storage and Handling Requirements

• Security

• Easy to use

• Portability

Given the above description of the input types and input media, you can say that most of the entries are the internal and interactive way. As the input data is the assembly directly by the user, the keyboard can be considered the most suitable input device.

2.1.4 Output Design:

In common are:

• External Outputs whose destination is outside the organization.

• Internal Outputs whose destination is in the organization and are the primary interface for the computer user. The outputs from the first place necessary systems for communicating the results of the users. They are also used to create a permanent copy of the results for later use to provide. The different types of outputs

• Operational outputs whose use is pure computer science department.

• The outputs of the interface, which means that the user interacts with the system directly.

2.1.5 Output Definition:

The outputs are to be defined in terms of the following points:

Output Type

Output content

Output format

Output Location

Output frequency

Output Volume

Output Sequence

Not always convenient to data as it runs on a computer to print or display. You must be the most suitable decide which way to the exit.

for instance

• Will you need a decimal

• If the zeros are suppressed.

2.1.6 Output Media:

In the next stage which is to be decided that the medium that is most appropriate for output. The main considerations when deciding on the means of production are:

• The suitability for the device with the particular application.

• The need for a hard copy.

• The required response time.

• The location of the users

• The software and hardware available.

Given the above description of the project is to have outputs mainly coming under the category of domestic products. The main desired results according to the requirements specification are:

They need products that have been generated on paper and as well as the questions you see on the screen. Given these results, the format of the output is taken from the products currently being obtained after manual processing. The printer's standard is to be used as output means for printouts.

3.PROCESS MODEL :

3.1 Software Development Life Cycle:

SDLC is simply the software development cycle. It is a standard used by the software industry to develop good software.

Requirement

Analysis

Designing

Development

Testing

Maintenance

3.1.1 Requirement Stage:

The requirements process takes as input the objectives stated in the requirements section of the senior project. Each object is refined in a series of one or more rules. These requirements define the main functions of the intended application, operational data areas and reference data areas, and defines the initial data entities. Important features are the critical processes are managed, as well as critical inputs, results and reports. A user class hierarchy has been developed and, in relation to this important role, data fields and data entities. Each of these definitions is called a requirement. The requirements are identified by unique identifiers required and, at least, have a title and text description requirement.

These requirements are described fully in the main features of this phase: the requirements document and Requirements Traceability Matrix (RTM). The requirements document contains a complete description of every need, including diagrams and references to external documents when necessary. Note that the list of database tables and fields are not included in the requirements document.

The title of each requirement is also placed in the first version of the RTM, along with the title of each project objective. The purpose of the RTM to demonstrate that the product developed formally components connected components developed in earlier stages. During each stage of software development tools to

In the requirements phase, the RTM consists of a list of requirements or high-level objectives by title, with a list of the associated requirements for each goal scored by the diploma required. In this hierarchical list, the RTM that any requirement that developed during this phase is formally linked to a specific product goal. In this format can be traced to a specific purpose to the product, any requirement hence the term requirements traceability.

The results of the requirements definition phase, the requirements document, the RTM, and updated project plan.

• Feasibility study is all about identifying troubles in a project.

• Number of employees needed to handle a project is proposed as a team, only modules are individual tasks are assigned to employees who work for that project in this case.

• Project disclaimer are all about representing different possible entries submitted to the server and the corresponding output along with reports kept by the administrator.

3.1.2 Analysis Stage:

The planning phase is a panoramic view of the desired software and uses to regulate, assess the feasibility and risks associated with the project, and describe appropriate management approaches and technique. The basic structure of the work.

3.1.3 Designing Stage:

The design takes as input the first requirements of the approved documentation requirements. For each condition, a set of one or more elements that occurs as a result of interviews, workshops, and / or prototype efforts. Design elements describe the desired software features in detail and generally functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo code and complete diagram with a comprehensive dictionary of entity-relationship data. These design elements are intended to describe in sufficient detail that skilled programmers to develop with minimal additional input.

When completed and accepted the design document, the RTM is updated to show that each element is associated with a specific standard requirement. The results of the study, work, updating RTM and updated project plan.

3.1.4 Development Stage:

The stage of development is mainly based design elements are described in the design. Document approved For each design, to produce a set. Of one or more software objects Software objects include, but are not limited to, menus, dialogs, forms, data management, data reports and specific procedures and functions. Suitable test cases are developed for each set of functionally related artifacts of the software, and an online help system should be developed to guide users in their interactions with the software.

The RTM is updated to show that each developed artifact associated with a certain design element, and that any one or more artifact developed similar cases the controls. At this point, the RTM in the final configuration. The outputs of the development is a fully functional set of software requirements and design elements previously documented, an online help system that describes the functionality of the software, a map application, outlining the main points of entry code identifies all fulfills important functions of the system, a test program that the basic tests are used to validate an updated RTM and an updated project described. the accuracy and completeness of the software

3.1.5 Integration and Test stage:

During the integration and testing, software objects, online help and test data migrated from the development environment to a separate test environment. At present, all the test cases for testing. The accuracy and integrity of the successful execution of software test suite confirms a strong ability and comprehensive migration. During this phase has been completed baseline data on the cost of production of users can be identified and linked to the appropriate functions. The final reference data (or links to reference data sources) and production user list compiled into the project into production.

3.1.6 Installation & Acceptance Test:

During installation and acceptance, software objects, online help, and the first production server elements production load. At this point, all copies of the control test. The accuracy and integrity of the software The successful application of the test suite is a prerequisite for acceptance of the software by the customer.

Personal customer following, "found that the initial burden of production data is correct and the test suite has been executed, the customer formally accepts delivery of the software.

The main results of the implementation and acceptance of the application include manufacturing, an integrated set of acceptance tests, and a Memorandum of customer acceptance of software. Finally, the PDR is the ultimate reality of working in project planning and blocks work as a permanent project file. At this point the PDR "locks" the task of archiving all the details of the software implementation of the map, the source code and documentation for future reference.

4.Feasibility Study:

The main purpose of the feasibility study is to test for adding new modules and debugging old operating system. Technical, operational and economic feasibility All systems are feasible if given unlimited resources and infinite time.

4.1 TECHNICAL FEASIBILITY

Research to explore the feasibility of projects, the probability that the system will be useful to the organization. The main purpose of the feasibility study is to test for adding new units to the technical, operational and economic feasibility and debugging old operating system. All systems are feasible if given unlimited resources and infinite time.

The technical problem usually during the feasibility phase of the study consists of the following:

• Does the technology exist to do what is suggested?

• Touch the proposed equipment have the technical ability to maintain the necessary information to use the new system?

• Will the proposed system is adequate for answers to questions, regardless of the number or location of users?

• Can the system be upgraded if developed?

Are there technical guarantees accuracy, reliability, ease of access and data security?

4.2 OPERATIONAL FEASIBILITY

User-friendly

Customer shall use the forms for various transactions, ie adding new routes, viewing detailed routes. The client wants to see. Reports from different transactions based restrictions These forms and reports generated as a user on the client computer.

Reliability

The package wills lift up current transactions online. on the subject of the old transactions, User will enter them within the system.

Security

The web server and database server should be protected from hacking, virus etc

Portability

The application will be developed using standard open source software (Except Oracle) like Java, tomcat web server, Internet Explorer Browser etc these software will work both on Windows and Linux o/s. Hence portability problems will not arise.

Availability

This software will be accessible always.

Maintainability :

The system called ewheelz used the two-tier architecture. The first level is the graphical interface, which is said to be the front end and the second layer is the database, which makes use of My-SQL, which is the back end.

The front-end can run on different systems (clients). The database will be running on the server. Users can access these forms through the use of user names and passwords.

4.3 ECONOMIC FEASILITY

The automated system takes care of the current existing data flow system processes and complete and all reports of manual system besides a host of other management to generate reports.

It must be built as a web-based application with a separate web server and database server. This is necessary if the activities are spread across the client organization wants a central database. Furthermore, a number associated transactions take place at different locations. Open source software such as Tomcat, Java, MySQL and Linux is used to overcome Cost to the customer.

5. FUNCTIONAL REQUIREMENTS SPECIFICATION

5.1 PERFORMANCE REQUIREMENTS

Performance is measured in terms of production is provided by the application. Requirements Specification plays an important role in the analysis of the system. Only when the claim specification given well, it is possible to have a system that is appropriate to design. Into the desired environment Is largely left to the users of the existing system to provide the required specifications, because they are the people who use the system eventually. This is because the conditions are well known in the early stages, so that the system can be designed in accordance with these requirements. It is very difficult to change the system because it is designed on the other hand, the design of a system that does not meet the requirements of the user, not in use.

The specification required for each system can be broadly stated as follows:

• The system is to interface with the existing system

• The system must be accurate

• The system should be better than the current system

The existing system is completely dependent on the user to perform all tasks.

5.2 SOFTWARE REQUIREMENTS:

Operating System : Windows

Technology : Java and J2EE

Web Technologies : Html, JavaScript, CSS

IDE : My Eclipse

Web Server : Tomcat

Database : Oracle

Java Version : J2SDK1.5

5.3 HARDWARE REQUIREMENTS:

Hardware : Pentium

RAM : 1GB

Additional Tools:

HTML Designing : Dream weaver Tool

Development Tool kit : My Eclipse

5.4 JAVA ARCHITECTURE:

Java architecture provides a portable, robust, high-performance environment for development. Java provides the portability training of byte codes for the Java Virtual Machine, which is then interpreted on any platform from the runtime environment.

A servlet There is a general extension of the server. a Java class that can be loaded.

Forces to the functionality of a common server. Servlets extend web servers. Where they can take their place. CGI scripts.

A servlet is similar to proprietary extension of the server, except that runs within a Java Virtual Machine (JVM) to the server, so it is safe and portable

Servlets operate solely within the domain of the server.

Unlike CGI and Fast CGI, using multiple methods to individual programs or individual applications, separate threads within the process of the web server to handle all servlets handle. This means that servlets are efficient and scalable.

Servlets are used as a replacement for CGI scripts on a web server, can be extended, such as a mail server that allows servelts t expand its functionality may perform virus detection in all attached documents or handling mail filtering tasks. Every kind of server

Servlets provide a Java-based solution that is used to deal with the problems that at this time in connection with the making of the scheduling server-side scripting, including non-extensible solution platform-specific API, and a poor interface.

Servlets are objects that match a given environment can be plugged into a Java-based server. Servlets are server-side applications that are in the server-side applications that client-side object byte code that can be dynamically loaded into the net. Form applets differ from what impersonal objects (images from an item or GUI). Serve as an independent platform, loaded dynamically linked objects assistant-byte code on the server that can be used to expand. Dynamic server-side functionality.

6. TESTING:

Testing is a process, which reveals errors in the program. This is the great quality measure used during software development. During software development. During the test, and this program is implemented with a set of test cases and results of the program are evaluated for test cases to see if the program works as expected performance.

6.2 TESTING IN STRATEGIES:

To make sure that the system has no errors, as different levels of control strategies applicable to the various stages of software development:

Unit Testing:

The unit testing is in individual sections as soon as completed and become doable. Limited only to the requirements of the designer.

Black Box Testing:

In this strategy is to create some test cases as entry conditions are fully implemented by all the operational requirements of the program. This assay has been used to find errors in the following categories:

• Jobs incorrect or missing

• Interface errors

• errors in the data structure or access to external database

• performance errors

• creation and termination errors.

In this test only the output is checked for validity. Does not identify the logical data flow.

White Box testing:

That in order to create test cases on the logic of each unit by drawing flowcharts is unity and logical decisions tested in all cases. Has been used to generate test cases in the following cases:

• Ensure that all paths are executed independently.

• Implementation of all rational decisions about the right and wrong sides.

• implementation of all the episodes in borders and operating within its borders

• implementation of internal data structures to ensure its accuracy.

Testing can be done in two ways:

This is done in two ways 1)bottom up approach 2)top down approach

Bottom up Approach:

No test can be performed starting from sections smaller and less and moving at the same time. Each section at the bottom to the top of a short test program performs unit and provides the data necessary to ensure the unit is to perform the way it is when combined with a larger system. When the test units lower level attention turns to those of the next level by using the lowest level when tested separately and then linked to the previously studied and lower-level units.

Top down approach:

This type of test launches of the top floor modules. Given that these activities usually performed at a lower level processes provide not written a seed. The heel is a unit called the shell of the unit before the top level, and that's when I got properly will return a message to the unit indicate that the call was appropriate interaction. No attempt has been made to validate the unit at a lower level.

Validation:

The system has been tested and implemented successfully and thus ensured that all the requirements as listed in the software requirements specification are completely fulfilled. In case of erroneous input corresponding error messages are displayed.

7. System Security:

If you configure authentication for Web applications, and the use of element <login-config> and web.xml deployment descriptor. At this point you can set the security space with user data, and verification method, and the position of the means for authentication.

7.1 SECURITY IN SOFTWARE

To set up substantiation designed for Web application:

Open the web.xml descriptor development in a text editor or use the Administration Console. Specify the authentication method by using the <auth-method>. The available options are:

BASIC

Basic authentication uses the browser to display. A username / password dialog This user name and password are validated by the kingdom.

FORM:

Forms-based authentication requires an HTML form that contains the user name and password returns. The answers of the form elements fields must be: j_username and j_password, and the action attribute must be j_security_check. Here is an example of using the HTML coding to FORM authentication:

method = "POST"

<form action="j_security_check">

<input name="j_username">

type = "password"

<input name="j_password">

</ Form>

The source used to generate the HTML form, an HTML page a JSP or a servlet are. Define the source <form-login-page> element.

The HTTP session object is created when served to the login page. Therefore, the method New () returns FALSE session when called from pages served after successful authentication.

8. Conclusion:

This project deals with the security and management of information in telecommunications. which is manually entered before in ledgers and files. Now the all the data is computerized and secured with the help of java technology. Creating lot more security to the customer data and ease of access to organizations to access the details of each and every customer very quick and reliable. . It is very difficult to change the system because it is designed on the other hand, the design of a system that does not meet the requirements of the user. The first level is the graphical interface, which is said to be the front end and the second layer is the database, which makes use of My-SQL, which is the back end. The front-end can run on different systems (clients). At this point you can set the security space with user data, and verification method, and the position of the means for authentication. In this different kinds of testing can be used to secure the customer data or clients data. In existing system The system is operated manually. The system uses conventional methods of data management. It is difficult to retrieve the necessary data about customers and phone connections effectively. To overcome these problems proposed system is a web-based application. The system maintains a central repository for all information.