Process Model Used With Justification

Published Date: 02 Nov 2017

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 the information. This allows you to keep the data effectively. It is easy to search for data and to perform all the functions effectively. The system allows you to create their own

2.1 STUDY OF THE SYSTEM

To provide flexibility to users, these interfaces have been developed that are accessed through a browser. The GUI on the top level have been identified as Administrative user interface

The operational or generic user interface

The ‘administrative user interface’ concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. These interfaces help the administrators with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The ‘operational or generic user interface’ helps the end users of the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the included flexibilities

2.2 INPUT & OUTPOUT REPRESENTETION

Input design is a part of overall system design. The main objective during the input design is as given below:

To produce a cost-effective method of input.

To achieve the highest possible level of accuracy.

To ensure that the input is acceptable and understood by the user.

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

INPUT TYPES:

It is necessary to determine the various types of inputs. Inputs can be categorized as follows:

External inputs, which are prime inputs for the system.

Internal inputs, which are user communications with the system.

Operational, which are computer department’s communications to the system?

Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:

At this stage choice has to be made about the input media. To conclude about the input media consideration has to be given to;

Type of input

Flexibility of format

Speed

Accuracy

Verification methods

Rejection rates

Ease of correction

Storage and handling requirements

Security

Easy to use

Portability

Keeping in view the above description of the input types and input media, it can be said that most of the inputs are of the form of internal and interactive. As Input data is to be the directly keyed in by the user, the keyboard can be considered to be the most suitable input device.

OUTPUT DESIGN:

In general are:

External Outputs whose destination is outside the organization.

Internal Outputs whose destination is with in organization and they are the User’s main interface with the computer. Outputs from computer systems are required primarily to communicate the results of processing to users. They are also used to provide a permanent copy of the results for later consultation. The various types of outputs

Operational outputs whose use is purely with in the computer department.

Interface outputs, which involve the user in communicating directly with the system.

OUTPUT DEFINITION

The outputs should be defined in terms of the following points:

Type of the output

Content of the output

Format of the output

Location of the output

Frequency of the output

Volume of the output

Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It should be decided as which form of the output is the most suitable.

For Example

Will decimal points need to be inserted

Should leading zeros be suppressed.

OUTPUT MEDIA:

In the next stage it is to be decided that which medium is the most appropriate for the output. The main considerations when deciding about the output media are:

The suitability for the device to the particular application.

The need for a hard copy.

The response time required.

The location of the users

The software and hardware available.

Keeping in view the above description the project is to have outputs mainly coming under the category of internal outputs. The main outputs desired according to the requirement specification are:

The outputs were needed to be generated as a hard copy and as well as queries to be viewed on the screen. Keeping in view these outputs, the format for the output is taken from the outputs, which are currently being obtained after manual processing. The standard printer is to be used as output media for hard copies.

2.3 PROCESS MODEL USED WITH JUSTIFICATION

SDLC (Spiral Model):

SDLC is nothing but Software Development Life Cycle. It is a standard which is used by software industry to develop good software.

Stages in SDLC:

Requirement Gathering

Analysis

Designing

Coding

Testing

Maintenance

Requirements Gathering stage:

The requirements gathering process takes as its input the goals identified in the high-level requirements section of the project plan. Each goal will be refined into a set of one or more requirements. These requirements define the major functions of the intended application, define

operational data areas and reference data areas, and define the initial data entities. Major functions include critical processes to be managed, as well as mission critical inputs, outputs and reports. A user class hierarchy is developed and associated with these major functions, data areas, and data entities. Each of these definitions is termed a Requirement. Requirements are identified by unique requirement identifiers and, at minimum, contain a requirement title and textual description.

These requirements are fully described in the primary deliverables for this stage: the Requirements Document and the Requirements Traceability Matrix (RTM). The requirements document contains complete descriptions of each requirement, including diagrams and references to external documents as necessary. Note that detailed listings of database tables and fields are not included in the requirements document.

The title of each requirement is also placed into the first version of the RTM, along with the title of each goal from the project plan. The purpose of the RTM is to show that the product components developed during each stage of the software development lifecycle are formally connected to the components developed in prior stages.

In the requirements stage, the RTM consists of a list of high-level requirements, or goals, by title, with a listing of associated requirements for each goal, listed by requirement title. In this hierarchical listing, the RTM shows that each requirement developed during this stage is formally linked to a specific product goal. In this format, each requirement can be traced to a specific product goal, hence the term requirements traceability.

The outputs of the requirements definition stage include the requirements document, the RTM, and an updated project plan.

Feasibility study is all about identification of problems in a project.

No. of staff required to handle a project is represented as Team Formation, in this case only modules are individual tasks will be assigned to employees who are working for that project.

Project Specifications are all about representing of various possible inputs submitting to the server and corresponding outputs along with reports maintained by administrator

Analysis Stage:

The planning stage establishes a bird's eye view of the intended software product, and uses this to establish the basic project structure, evaluate feasibility and risks associated with the project, and describe appropriate management and technical approaches.

Designing Stage:

The design stage takes as its initial input the requirements identified in the approved requirements document. For each requirement, a set of one or more design elements will be produced as a result of interviews, workshops, and/or prototype efforts. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudo code, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input.

When the design document is finalized and accepted, the RTM is updated to show that each design element is formally associated with a specific requirement. The outputs of the design stage are the design document, an updated RTM, and an updated project plan.

Development (Coding) Stage:

The development stage takes as its primary input the design elements described in the approved design document. For each design element, a set of one or more software artifacts will be produced. Software artifacts include but are not limited to menus, dialogs, data management forms, data reporting formats, and specialized procedures and functions. Appropriate test cases will be developed for each set of functionally related software artifacts, and an online help system will be developed to guide users in their interactions with the software.

The RTM will be updated to show that each developed artifact is linked to a specific design element, and that each developed artifact has one or more corresponding test case items. At this point, the RTM is in its final configuration. The outputs of the development stage include a fully functional set of software that satisfies the requirements and design elements previously documented, an online help system that describes the operation of the software, an implementation map that identifies the primary code entry points for all major system functions, a test plan that describes the test cases to be used to validate the correctness and completeness of the software, an updated RTM, and an updated project plan.

Integration & Test Stage:

During the integration and test stage, the software artifacts, online help, and test data are migrated from the development environment to a separate test environment. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite confirms a robust and complete migration capability. During this stage, reference data is finalized for production use and production users are identified and linked to their appropriate roles. The final reference data (or links to reference data source files) and production user list are compiled into the Production Initiation Plan.

Installation & Acceptance Test:

During the installation and acceptance stage, the software artifacts, online help, and initial production data are loaded onto the production server. At this point, all test cases are run to verify the correctness and completeness of the software. Successful execution of the test suite is a prerequisite to acceptance of the software by the customer.

After customer personnel have verified that the initial production data load is correct and the test suite has been executed with satisfactory results, the customer formally accepts the delivery of the software.

The primary outputs of the installation and acceptance stage include a production application, a completed acceptance test suite, and a memorandum of customer acceptance of the software. Finally, the PDR enters the last of the actual labor data into the project schedule and locks the project as a permanent project record. At this point the PDR "locks" the project by archiving all software items, the implementation map, the source code, and the documentation for future reference.

Architecture Flow:

Below architecture diagram represents mainly flow of requests from users to database through servers. In this scenario overall system is designed in three tires separately using three layers called presentation layer, business logic layer and data link layer. This project was developed using 3-tire architecture.

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.

3.1 TECHNICAL FEASIBILITY

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?

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

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

4.1 FUNCTIONAL REQUIREMENTS SPECIFICATION

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.

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

HARDWARE REQUIREMENTS:

Hardware : Pentium

RAM : 1GB

Additional Tools:

HTML Designing : Dream weaver Tool

Development Tool kit : My Eclipse

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.

INTRODUCTION TO TESTING

Introduction to 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.

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.

8.1 INTRODUCTION

System Security:

Setting Up Authentication for Web Applications

Introduction:

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.

8.2 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

Form-based authentication requires that you return an HTML form containing the username and password. The fields returned from the form elements must be: j_username and j_password, and the action attribute must be j_security_check. Here is an example of the HTML coding for using FORM authentication:

<form method="POST" action="j_security_check">

   <input type="text" name="j_username">

   <input type="password" name="j_password">

</form>

The resource used to generate the HTML form may be an HTML page, a JSP, or a servlet. You define this resource with the <form-login-page> element.

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