A

Project Report

On

TRAVEL AGENCY

Submitted in partial fulfillment of the requirement for award of the degree of

MASTER OF COMPUTER APPLICATIONS

(Session-2021-2023)

SUPERVISED BY: SUBMITTED BY:

Dr. Kapil Kaswan Rachna Rani
Assistant Professor MCA 4th Semester
Dept. of Computer Science and Engineering Roll No:- 21111990870006

Department of Computer Science and Engineering

Chaudhary Devi Lal University, Sirsa-125055

(May 2023)
 DECLARATION

I, Rachna Rani, Roll No 21111990870006 hereby declare that this project work
entitled, “Travel Agency”, has been carried out by me during last semester of
MCA under the guidance of Dr. Kapil Kaswan, Assistant Professor, Department of
Computer Science and Engineering, CDLU Sirsa, in the partial fulfillment of
Master of Computer Applications degree prescribed by the department. I also
declare that this project is the outcome of my own efforts and it has not been
submitted to any other university for the award of any degree.

DATE: Rachna Rani

i
 Department of Computer Science and Engineering

Chaudhary Devi Lal University, Sirsa

CERTIFICATE FROM THE SUPERVISOR

This is to certify Rachna Rani, Roll No 21111990870006, a student of Master of

Computer Applications has completed his project entitled “Travel Agency”,
under my supervision satisfactorily. I wish him all success in her life.

DATE: Dr. Kapil Kaswan

PLACE: Sirsa (Supervisor)

ii
 Department of Computer Science and Engineering
Chaudhary Devi Lal University, Sirsa

CERTIFICATE FROM THE CHAIRPERSON

This is to certify Rachna Rani Roll No. 21111990870006, a student of Master of

Computer Applications has completed his project entitled “Travel Agency”,
under the supervision of Dr.Kapil Kaswan for award of degree of “Master of
Computer Applications”, Department of Computer Science and Engineering. I
wish her all success in life.

Date:

Place:Sirsa (Chairperson)

iii
 ACKNOWLEDGEMENT

I take this opportunity to express my deepest gratitude to those who have

generously helped me in providing the valuable knowledge and it is with real
pleasure, that I record my indebtedness to my supervisor, Dr. Kapil Kaswan,
Assistant Prof. Dept. of Computer Science and Engineering, for his counselling
and guidance during the preparation of this project and I would also like to thank
research scholars, the teaching and non-teaching staff members of my department.

I am also highly grateful to my parents for constantly reminding me about the work
and helping me in my work. I am also grateful to my friends for providing critical
feedback and support whenever required.

Last but not the least I thanks to all those people who helped me directly or
indirectly in shaping up my project.

Rachna

iv
 INDEX
S No. TITLE PAGE NO.
Declaration i
Certificate from Supervisor ii
Certificate from Chairperson iii
Acknowledgement iv
1. Introduction……………………………………………………………………………1-2

1.1. About the Project

1
1.2. Objective of the project
2
1.3. Modules
2
2. Technology used……………………………………………………………................3-10

2.1. PHP 3
2.2. HTML 6
2.3. CSS 6
2.4. JavaScript 8
2.5. MySql 9
3. Requirement Analysis………………………………………………………………11-16

3.1. System Requirement 11

3.1.1. Minimum Hardware Requirement 11
3.1.2 Minimum Software Requirement 11
3.2 Feasibility Study 12
3.2.1. Economic Feasibility 12
3.2.2. Technical Feasibility 13
3.2.3. Operational Feasibility 13
3.2.4. Legal Feasibility 13
3.3. System Implementation 13
3.4. Functional Requirement 13
3.5. Non-Functional Requirement 13
3.6. System Requirement Specification (SRS) 14
3.7. Process Model 15
 3.7.1. Requirement Analysis 16
3.7.2. System Design 16
3.7.3. Coding 16
3.7.4. Testing 16
3.7.5. Implementation and Maintenance 16
4. System Design……………………………………………………………………….16-23

4.1. System Design 16

4.2. Architectural Design 17
4.2.1. The External Design 18
4.2.2. Physical Design 18
4.2.3. Logical Design 18
4.3. Data Flow Diagram (DFD) 19
4.3.1. Zero Level DFD 21
4.3.2. First Level DFD 22
4.3.3. Second Level DFD 23
5. Coding and Screen Shots…………………………………………………………...24-39

5.1. Introduction to Coding 24

5.2. Coding Approach 25
5.3. Screen Shots 26
6. Testing………………………………………………………………………………..40-46

6.1.Why testing is done 43

6.2. Type of Test 46
7. Implementation and Maintenance…………………………………………………47-51

7.1. Implementation and Output 48

7.2. Maintenance 50
7.2.1. Corrective Maintenance 51
7.2.2. Adaptive Maintenance 51
8. Conclusion………………………………………………………………………………52

9. Future Scope……………………………………………………………………………53

Bibliography……………………………………………………………………………54
 CHAPTER 1
INTRODUCTION OF PROJECT

1.1. INTRODUCTION

About the Project:

Online Tour and Travel is a very user friendly project. In this project user can easily understand
and book all packages and also register for hotel. In this project there are various types of
forms, like all types of packages, book for package and Room Registration Page in which user
can insert his personal needs & facilities then upload his form by which user can register in the
web site. In this website user can also pay money through credit card.

This site provides different tour packages, hotel booking and summer special tour packages.
Through this site, user can book different types of room such as deluxe room, ac room etc on
flexible price.

This site provides different packages, destination, and hotel booking services in one particular
state of India. Himachal Pradesh is very popular hill station of north India. Visitors enjoy snow
covered mountain peaks and adventure sports like trekking, mountaineering and skiing.

In this website, according to the tour packages it provides services like online booking facilities
for all packages and hotels registration to the customer. In this project user can easily
understand and fill up the Room Reservation form. User can search for various types of rooms.

Online Tour and Travel is a web based application made in Asp.Net. So with the help of this
project user can apply for packages of tour and room reservation.

1.2. OBJECTIVE

The Main Goal of this project is to provide a very faster room reservation services and also
booking services for different types of packages so any user can get this service very easily.

1
This system provides Online Registration, Tour Package Information, Bus ticket booking and all
other destinations. The purpose of this project is very clear that user can find room facilities
easily & hotel service providers also get good customers very easily. Customer can register in the
website & can create his own registration then he can receive email for his room status related to
his reservation and book all packages. User can register hotel for different types of room what
they want.

 Our objective is to make strong relationship with customers so that they can enjoy the holiday
of their dreams.
 It saves lots of time , now a days there is a fast process world any one can work quickly
so, this project helps that people who are searching for reservation in organization, so
they can easily fill up the form and search rooms and different tourist place.

 Possess complete back up services.

2
.

CHAPTER 2

Technology Used

TELECOM SERVICE , have many the stacks as building blocks as the website is made with
different technology according to need and demand of the website as for server side scripting
language PHP is used, for front end HTML,CSS,JAVASCRIPT is used and for storing data in
backend SQLite is used.

2.1. PHP

History:Rasmus Lerdorf, who wrote the original Common Gateway Interface (CGI)
component together with Andi Gutmans and Zeev Suraski, who rewrote the parser that formed
PHP 3.

PHP development began in 1994 when the Danish/Greenlandic/Canadian programmer Rasmus

Lerdorf initially created a set of Perl scripts he called "Personal Home Page Tools" to maintain

3
his personal homepage. Lerdorf initially announced the release of PHP on the
comp.infosystems.www.authoring.cgi Usenet discussion group on June 8, 1995.

He rewrote these scripts as Common Gateway Interface (CGI) binaries in C, extending them to
add the ability to work with Web forms and to communicate with databases and called this
implementation "Personal Home Page/Forms Interpreter" or PHP/FI. PHP/FI could be used to
build simple, dynamic Web applications. Lerdorf released PHP/FI as "Personal Home Page
Tools (PHP Tools) version 1.0" publicly on June 8, 1995, to accelerate bug location and improve
the code.

Afterward, public testing of PHP 3 began, and the official launch came in June 1998. Suraski and
Gutmans then started a new rewrite of PHP's core, producing the Zend Engine in 1999.They also
founded Zend Technologies in Ramat Gan, Israel.

On May 22, 2000, PHP 4, powered by the Zend Engine 1.0, was released. As of August 2008
this branch is up to version 4.4.9. PHP 4 is no longer under development nor will any security
updates be released.

On July 13, 2004, PHP 5 was released, powered by the new Zend Engine II. PHP 5 included new
features such as improved support for object-oriented programming.

A new major version has been under development alongside PHP 5 for several years. This
version was originally planned to be released as PHP 6 as a result of its significant changes,
which included plans for full Unicode support.

Many high-profile open-source projects ceased to support PHP 4 in new code as of February 5,
2008, because of the GoPHP5 initiative, provided by a consortium of PHP developers promoting
the transition from PHP 4 to PHP 5.

PHP interpreters are available on both 32-bit and 64-bit operating systems, but on Microsoft
Windows the only official distribution is a 32-bit implementation, requiring Windows 32-bit
compatibility mode while using Internet Information Services (IIS) on a 64-bit Windows
platform.

ADVANTAGES:

4
There are the following advantages of PHP:-

1. Cost: PHP is completely free.

2. Ease of Use: PHP is easy to learn compared to many other scripting languages. PHP has a
syntax that is easy to parse and is actually rather human-friendly.
3. Embedded: PHP can be easily embedded directly into HTML.
4. Compatibility: PHP runs native on all UNIX and Windows platforms.
5. Not Tag-Based: PHP is a real programming language.
6. Stability.
7. Speed.
8. Open source licensing.
9. Many extensions.
10. Fast feature development.
11. PHP is ideal for web programming.
12. It provides high performance.
13. Features native support for most popular databases.

FEATURES:

There are the following main features of the PHP:-

1. Open Source: PHP is an open source language and is freely available for use. The
community of open source PHP developers provides technical support and is constantly
improving updating the core PHP functionalities.
2. Compatibility: PHP provides high compatibility with leading operating systems and web
servers such as thereby enabling it to be easily deployed across several different platforms.
3. File Handling: PHP be used to read text and generate files in various formats such as PDF
and XML. Using the file manipulation functions, files and documents can be uploaded and stored
on the server. The uploaded documents can be accessed and manipulated through PHP code.
4. Improved Performance: The PHP compiler includes features to optimize and
improve the quality of compiled code by reducing the size execution time of the code thereby
leading to improved performance.
5. Debuggers: Several debuggers are available with PHP enabling developers to identify
and analyze the code for potential bugs and bottlenecks.

5
6. Sessions: PHP provides extensive session and cookie management features and
functions enabling the creation and development of personalized web pages.
7. Graphics: PHP can be used to generate images and graphics dynamically. Using the
image functionalities available with PHP, the header information of images can be accessed and
manipulated.
The PHP is a high-level language that can be characterized by all of the following buzzwords:

● Simple
● Object oriented
● Secure
● Portable
● High performance

6
2.2. HTML
The first version of HTML was written by Tim Berners-Lee in 1993. Since then, there have been
many different versions of HTML. The most widely used version throughout the 2000's
was HTML 4.01, which became an official standard in December 1999.
The Hypertext Markup Language or HTML is the standard markup language for documents
designed to be displayed in a web browser. It can be assisted by technologies such CSS an
scripting languages such as javascript.
World Wide Web (WWW) programming deals with the development of hypertext document
interaction mechanisms, which provide the client with a rich and intuitive interface to the
information that he or she desires to view. Web development heavily utilizes the functionality of
the Hypertext Markup Language, commonly known as HTML. HTML is a simple scripting
language that is interpreted within a web browser. It provides functionality to identify and
specify how information is presented to the user. Some of the important features of HTML that
make it ideal for online representation of information are –

● Ease of Use – HTML constructs are very easy to comprehend, and can be used
effectively by anybody.

● Machine Independence – The methodology used by HTML to markup information is

independent of its representation on a particular hardware or software architecture.

● Standardization – HTML syntax is a worldwide standard, developed by the W3C

● Flexible – HTML has been extended in many forms to provide additional functionality.

2.3. CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a

document written in a markup language such as HTML or XML (including XML dialects such
as SVG, MathML or XHTML. CSS is a cornerstone technology of the World Wide Web,
alongside HTML and JavaScript.

CSS is designed to enable the separation of content and presentation, including layout, colors,

and fonts. This separation can improve content accessibility; provide more flexibility and control
in the specification of presentation characteristics; enable multiple web pages to share formatting
by specifying the relevant CSS in a separate .css file, which reduces complexity and repetition in

7
the structural content; and enable the .css file to be cached to improve the page load speed
between the pages that share the file and its formatting.

Separation of formatting and content also makes it feasible to present the same markup page in
different styles for different rendering methods, such as on-screen, in print, by voice (via speech-
based browser or screen reader, and on Braille-based tactile devices. CSS also has rules for
alternate formatting if the content is accessed on a mobile device.

The name cascading comes from the specified priority scheme to determine which style rule
applies if more than one rule matches a particular element. This cascading priority scheme is
predictable.

Advantages of CSS

 CSS saves time − You can write CSS once and then reuse the same sheet in multiple
HTML pages. You can define a style for each HTML element and apply it to as many
Web pages as you want.
 Easy maintenance − To make a global change, simply change the style, and all elements
in all the web pages will be updated automatically.
 Global web standards − Now HTML attributes are being deprecated and it is being
recommended to use CSS. So it's a good idea to start using CSS in all the HTML pages to
make them compatible with future browsers.
 Platform Independence − The Script offer consistent platform independence and can
support latest browsers as well.
  Better Website Speed-For a website to function efficiently, it should have a faster load
time. In modern times, people usually wait for just a couple of seconds for a website to
load. So, it’s important to ensure faster speed. For companies wanting to ensure a faster
and smooth website experience, CSS becomes paramount to their success.
 Easier to Maintain-CSS is easy to maintain due to less maintenance time. This is
because a single line code change affects the entire web page. Also, if improvements are
required, then less effort is required to affect changes in the webpage code.
 Better Device Compatibility-People use different smart devices to view a particular
website. It can be a smartphone, PC or laptop. For this purpose, websites are required to
be device compatible. CSS ensures the task is done smoothly by providing better
compatibility. 

8
2.4.JavaScript

Java script is one of the most simple, versatile and effective languages used to extend
functionality in websites. Uses range from on screen visual effects to processing and calculating
data on web pages with ease as well as extended functionality to websites using third party
scripts among several other handy features, however it possesses some negative effects that
might make you want to think twice before implementing JavaScript on your website.

Advantages

● Java is executed on the client side: this means that the code is executed on the user's
processor instead of the web server thus saving bandwidth and strain on the web server.

● Java Script is a relatively easy language The JavaScript language is relatively easy to
learn and comprises of syntax that is close to English. It uses the DOM model that provides
plenty of prewritten functionality to the various objects on pages making it a breeze to
develop a script to solve a custom purpose.

● JavaScript is relatively fast to the end user As the code is executed on the user's
computer, results and processing is completed almost instantly depending on the task (tasks
in javascript on web pages are usually simple so as to prevent being a memory hog ) as it does
not need to be processed in the site's web server and sent back to the user consuming local
as well as server bandwidth.

● Extended functionality to web pages Third party add-ons like Grease monkey enable
JavaScript developers to write snippets of JavaScript which can execute on desired web pages to
extend its functionality. If you use a website and require a certain feature to be included, you can
write it yourself and use an add-on like grease monkey to implement it on the web page.

Disadvantages of JavaScript

Security Issues:

JavaScript snippets, once appended onto web pages execute on client servers immediately and
therefore can also be used to exploit the user's system. While certain restriction is set by modern
web standards on browsers, malicious code can still be executed complying with the restrictions
set.

9
2.5. MYSQL

MySQL is an Oracle-based open source relational database management system (RDBMS)

based on Structured Query Language (SQL). MySQL runs on virtually all platforms,
including Linux, UNIX and Windows. Although it can be used in a wide range of applications,
MySQL is most often associated with web applications and online publishing.

Introduction:

MySQL is the most popular online database. It can be used as a stand alone database, or used as

a back-end for your PHP based website. Using a database of information allows to you create on
the fly results for your users.

⮚ MYSQL is a database server

⮚ MYSQL is ideal for both small and large applications
⮚ MYSQL supports standard SQL
⮚ MYSQL compiles on a number of platforms
⮚ MYSQL is free to download and use

You can use MYSQL to create databases that contain several tables of information, and within
each table you can hold several fields of information. Once you have an existing database you
can always add more tables, or remove tables at any time.

MYSQL is one of the top databases available in the market. MYSQL is a relational database
with many advanced features and options. Over time, MYSQL has proved itself to be a fast,
reliable and cost effective competitor to the other more expensive databases like MS SQL Server
and Oracle. Here are a few of the advantages of using MYSQL in database development.

Advantages of MYSQL:

10
1. Open Source: - MYSQL is an open source database system which means that anyone can
use it for free. Developers can amend its code to suit their requirements which means that
MYSQL is highly customizable as well.
2. Fast Development: - A lot of people around the globe are continuously developing new
modules for integration with MYSQL. This means that it has a wider and faster development
circle.
3. Better for Small Business: - This relational database system is free so it reduces the cost
of overall database solution for small business and companies.
4. Cross Platform Operability: - MYSQL is easily installable and operable on different
platforms including Windows, Linux, OS2 and Solaris. Cross platform operability makes it a
favorable choice for development companies.
5. Security: - MYSQL as a relational database is secure as all access password are
stored in an encrypted format restricting any unauthorized access to the system
6. Connectivity: - MYSQL clients can access this relational database through
standard TCP/IP sockets, named pipes, UNIX sockets and many more. Standard ODBC 2.5 and
above functions and commands are also supported in MYSQL.

11
 3. REQUIREMENT ANALYSIS

Requirement analysis is one of the important phase of the software development. In the
development of the project, all the entries requirement like hardware, software and other
resources are analyzed clearly that are easily available free of cost. Various requirements for the
project are as:-

3.1. System Requirements

3.1.1 Minimum Hardware Requirement:

System type : 32-bit or 64-bit operating system

RAM : 512 MB

Hard Disk : 128 GB

Internet speed : 512kbps

Monitor : 15’’ color monitor

3.1.2 Minimum Software Requirement:

Operating system : Windows/iOS/Unix

Web Browser : IE/Google Chrome/Firefox

Technology : PHP

Tools : XAMPP

Web Design : HTML, CSS, JAVASCRIPT

Backend : MYSQL

Scripting Language : PHP

12
3.2. Feasibility Study

Preliminary investigation examine project feasibility, the likelihood the

systemwillbeusefultotheorganization.ThemainobjectiveofthefeasibilitystudyistotesttheTechnical,

OperationalandEconomicalfeasibilityforaddingnewmodules and debugging old running system.

All system is feasible if they areunlimited resources and infinite time. There are aspects in the

feasibility studyportionofthe preliminary investigation:

 TechnicalFeasibility
 OperationFeasibility
 EconomicFeasibility

3.2.1. Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the
following:

 Do the proposed equipment have the technical capacity to hold the data required to
use the new system?
 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?

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

security?
3.2.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned out into informationsystem. That will
meet the organization’s operating requirements.
Operationalfeasibilityaspectsoftheprojectaretobetakenasanimportantpartoftheprojectimplementati
on. Some of the important issues raised are to test the operationalfeasibilityofa
projectincludesthefollowing:-
 Istheresufficient supportforthemanagementfromtheusers?
 Willthesystembeusedandworkproperlyifitisbeingdevelopedand implemented?
 Willtherebeanyresistancefromtheuserthatwillunderminethepossibleapplicationbenefits?

13
3.2.3. Economic Feasibility
Asystemcanbedevelopedtechnicallyandthatwillbeusedifinstalledmuststillbe a good investment for
the organization. In the economic feasibility,
thedevelopmentcostincreatingthesystemisevaluatedagainsttheultimatebenefitderivedfromthenews
ystems.Financialbenefitsmustequalorexceedthecosts.
3.2.4. Legal Feasibility
In the legal feasibility it is necessary to check that the software we are going to develop is legally
correct which means that the ideas which we have taken for 15 the proposed system will be
legally implemented or not so, it is also an important step in feasibility study.
3.3. System implementation
During the implementation stage in physically stage in physically created. Necessary program
are coded, debugged and documented. A new hardware is selected, ordered and installed.
3.4. Functional Requirements
Requirement analysis is a software engineering technique that is composed of the various tasks
that determine the needs or conditions that are to be met for a new or altered product, taking into
consideration the possible conflicting requirements of the various users. Functional requirements
are those requirements that are used to illustrate the internal working nature of the system, the
description of the system, and explanation of each subsystem. It consists of what task the system
should perform, the processes involved, which data should the system holds and the interfaces
with the user. The functional requirements identified are:
 Customer’s registration: The system should allow new users to register online and
generate membership card
 Online selection of Service: Customers should be able to use the system to make
booking and online options selection.
 Automatic update to database onceorder is made or new customer
registered: Whenever there’s new reservation or new registration, the system should be
able update the database without any additional efforts from the admin.
3.5. Non Functional Requirements
It describes aspects of the system that are concerned with how the system provides the functional
requirements. They are:
 Security: The subsystem should provide a high level of security and integrity of the
data held by the system, only authorized personnel of the company can gain access to

14
 the company’s secured page on the system; and only users with valid password and
username can login to view user’s page.
 Availability:This system should always be available for access at 24 hours, 7 days
a week. Also in the occurrence of any major system malfunctioning, the system
should be available in 1 to 2 working days, so that the business process is not severely
affected.
 Ease of use: Considered the level of knowledge possessed by the users of this
system, a simple but quality user interface should be developed to make it easy to
understand and required less training.

3.6. System Requirement Specification(SRS)

A software requirements specification (SRS) is a complete description of the behavior of the
system to be developed. It includes a set of use cases that describe all of the interactions that the
users will have with the software. Use cases are also known as functional requirements. In
addition to use cases, the SRS also contains nonfunctional (or supplementary) requirements.
Non- functional requirements are requirements that impose constraint on the design or
implementation (such as performance requirements, quality standard or design constraint).

In system engineering and software engineering, requirements analysis encompasses those tasks
that go into determining the requirements of a new or altered system, taking account of the
possibly conflicting requirements of the various stakeholders, such as users. Requirements
analysis is critical to the success of project. The document that contains all the requirements of
the project is determined as “Software Requirements Specification”.

Software requirements specification states the goals and objectives of the software, describing it
in the context of the computer based system.

The Information Description provides a detailed description of the problem that the software
must solve. Information content, flow and structure are documented.

A description of each function required to solve the problem is presented in the Functional
Description. Validation Criteria is probably the most important and ironically the most often
neglected section of the software requirement specification.

15
An SRS minimizes the time and effort required by developers to achieve desired goals and also
minimizes the development cost. A good SRS defines how an application will interact with
system hardware, other programs and human users in a wide variety of real-world situations.
Parameters such as operating speed, response time, availability, portability, maintainability,
footprint, security and speed of recovery from adverse events are evaluated. Methods of defining
an SRS are described by the IEEE (Institute of Electrical and Electronics Engineers)
specification 830-1998.

3.7. Process Model

For this project the process model suitable is Iterative Waterfall. Waterfall model organizes the
phases in a sequence order. The development of the portal begins with requirement analysis. On
successfully understanding the requirement of a project, the requirement analysis and project
planning is completed. The coding begins after the completion of design phase. Once the
programming is completed, the coding is performed and testing is done.

Reason for using waterfall model in project development:

In the case of this portal, waterfall model is used because the requirements have been will
defined and stable which is one of the primary criteria for applicability of waterfall model. Also,
the time allowed for the project was limited. This model is easy to understand and easy to
explain to the viewers and users. Being one person for developing this project, this model seems
16
appropriate. This project is also small and suitable for using waterfall model, as all the
requirements are very well known and it is short term also, this project one phase is completed
before next phase begins i.e., after the examine the requirement phase analyses phase, system
design phase is undertaken. After the system design phase, the coding is done and then testing
and so on. All the phases of SDLC are performed according to the need during the project
development.
3.7.1. Requirements Analyses
Requirements analyses is one of the important phase of the software development. For the
development of the project, all the requirements are analyzed clearly before performing any other
task. Details of the requirements analyses are given in this chapter.
3.7.2. System Design
The system design phase of this project follows system analyses phase as design is the bridge
between system analyses and implementation. The design is the solution of “how to” approach to
the creation of a new system. Details of the system design are given in chapter 4.
3.7.3. Coding

The purpose of coding is to express the program logic in the best possible way and to check it. In
this project we use the top-down approach for coding the module. Detail information of coding is
given in chapter 5.

3.7.4. Testing

Testing is a process of analyzing a system or system components to detect the differences

between specified and observed behave. In other word, testing is a fault detection technique that
try to create failure or erroneous states in a planned way. This allows the developer to detect
failures in the system before it is released to the customer. We can use different testing with
different taste cases in the project.

3.7.5. Implementation and Maintenance

System implementation and maintenance are the stages when the user has thoroughly tested the
system and approves all the features provide by the system.

17
 CHAPTER 4

System Design

Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

Once the software requirements have been analyzed and specified the software design involves
three technical activities - design, coding, implementation and testing that are required to build
and verify the software.

The design activities are of main importance in this phase, because in this activity, decisions
ultimately affecting the success of the software implementation and its ease of maintenance are
made. These decisions have the final bearing upon reliability and maintainability of the system.
Design is the only way to accurately translate the customer’s requirements into finished software
or a system.

Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software design is
conducted in two steps. Preliminary design is concerned with the transformation of requirements
into data.

Design process for the software system has two levels, namely:

 System Design
 Detailed Design

4.1. SYSTEM DESIGN

This design level is also called top level design. At this level, the focus is on:

• Deciding which modules are needed for the system.

• The specifications of the system
• How the modules should be interconnected?
4.2. ARCHITECTURAL DESIGN

Analysts collect a great deal of unstructured data through interviews, questionnaires, on-site
observations, procedural manuals and like. It is required to organize and convert the data through

18
system flowcharts, data flow diagrams, structured English, decision tables and the like which
support future developments of the system.
The Data flow diagrams and various processing logic techniques show how, where, and when
data are used or changed in an information system, but these techniques do not show the
definition, structure, and relationships within the data.
It is a way to focus on functions rather than the physical implementation. This is analogous to the
architect’s blueprint as a starting point for system design. The design is a solution, a “how to”
approach, compared to analysis, a “what is” orientation.
System design is a highly creative process. This System design process is also referred as data
modeling. The most common format used for data modeling is entity-relationship (E-R)
diagramming. Data modeling using the E-R notation explains the characteristics and structure of
data independent of how the data may be stored in computer memories.

4.2.1. The External Design

External design consists of conceiving, planning out and specifying the externally observable
characteristics of the software product. These characteristics include user displays or user
interface forms and the report formats, external data sources and the functional characteristics,
performance requirements etc. External design begins during the analysis phase and continues
into the design phase.

4.2.2. Physical design

The physical design relates to the actual input and output processes of the system. This is laid
down in terms of how data is input into a system, how it is verified/ authenticated, how it is
processed, and how it is displayed as output. Physical design, in this context, does not refer to the
tangible physical design of an information system. To use an analogy, a personal computer's
physical design involves input via a keyboard, processing within the CPU, and output via a
monitor, printer, etc. It would not concern the actual layout of the tangible hardware, which for a
PC would be a monitor, CPU, motherboard, hard drive, modems, video/graphics cards, USB
slots, etc.

4.2.3. Logical design

The logical design of a system pertains to an abstract representation of the data flows, inputs and
outputs of the system. This is often conducted via modeling, which involves a simplistic (and

19
sometimes graphical) representation of an actual system. In the context of systems design,
modeling can undertake the following forms, including:
● Data flow diagrams
● Entity Relationship Diagrams
Prototyping Model has been used for software development according to which a throwaway
prototype of the proposed system, based on the currently known requirements, is given to the
user so that he has a fair idea about how the proposed system is going to be like. This will help
him in deciding the interface, input and output requirements.
It can be easily adjudged that inputs and outputs are big in number, can increase exponentially
and may create a big chaos if not restricted properly. As the user spends some time on the
prototype, he will become more precise about his own input and output requirements. This
prototype will provide him with an environment analogous to the proposed system’s
environment.
Because of lack of hierarchical structure in object oriented approach, there is no meaning of
Bottom-up or Top-down testing. Testing will begin from the most rudimentary levels of the
system and will move towards higher level components which will be based on design phase
rather than coding phase. In little words, it can be said that ‘CLUSTER Testing’ will be
exercised to scrutinize all the parts and their associative functionality.

4.3. Data Flow Diagram (DFD)

A Data Flow Diagram (DFD) is a graphical representation that depicts the information flow and
the transforms that are applied as data moves from input to output.
A data-flow diagram is a way of representing a flow of data through a process or a system
(usually an information system). The DFD also provides information about the outputs and
inputs of each entity and the process itself. A data-flow diagram has no control flow — there are
no decision rules and no loops. Specific operations based on the data can be represented by
a flowchart.

There are several notations for displaying data-flow diagrams. The notation presented above was
described in 1979 by Tom DeMarco as part of structured analysis.

For each data flow, at least one of the endpoints (source and / or destination) must exist in a
process. The refined representation of a process can be done in another data-flow diagram, which
subdivides this process into sub-processes.

20
The data-flow diagram is a tool that is part of structured analysis and data modeling. When
using UML, the activity diagram typically takes over the role of the data-flow diagram. A special
form of data-flow plan is a site-oriented data-flow plan.

Basic DFD

21
4.3.1. Zero level DFD

Zero Level DFD of telecom system, it elaborate high level process oftelecom system. It is
overview of whole online telecom system therearesomehigh levelentitiesfortheprocessofcar
rentalsystem.

22
4.3.2 First Level DFD

1st Level DFD of telecom system shows how the system is divided intosubsystem,eachof
whichdealswithoneormoreofthedataflowstoorfromanexternal agent which together provide all the
functionality of telecomsystemas whole, above are somegiven entities andoutputof 1st level.

23
4.3.3 Second level DFD

In the second level DFD for the portal is showing the main module which is the admin module in
basic flow. In admin the admin can do many things as shown in the DFD. Admin can check the
credentials of the customers, check the details about the bookings. Also admin can accept or
reject the user bookings.

Chapter 5
24
 Coding and Screen Shots

5.1. Introduction to coding

The purpose of coding is to express the program logic in the best possible way and to the check
it. The main reasons for coding are:

 Unique Identification: Each item in a system should be identified uniquely and

correctly.
 Cross referencing: Diverse activities in an organization give rise to Transactions in
different sub systems but affect the same item
 Efficient storage: Code is a concise representation it reduces data entry me and
improves reliability, Code as a key reduces storage space required for the data Retrieval
based on a key search is faster in a computer.

Requirements of coding scheme:

The number of digits / characters used in a code must be minimal to reduce storage space of the
code and retrieval efficiency. It should be expandable, that is it must allow new items to be
added easily.

Type of Codes:

 Serial Numbers: This method is that it is concise, precise and expandable. It is however
not meaningful.
 Block Codes: The block codes use blocks of serial numbers. This code is Expandable
and more meaningful than the serial number coding. It is precise but not
comprehensive.
 Code Efficiency: It is often said that readability of a program is much more important
than the intricacies of its code.

Main emphasis while coding was on style so that the end result was an optimized code.
The following points were kept into consideration while coding:

I. Coding Style: - The Structured programming method was used in all the modules of the
project. It incorporated the following features:
 The code has been written so that the definition and implementation of each
function is contained in one file.

25
  A group of related function was clubbed together in one file to include it when
needed and save us from the labor of writing it again and again.

II. Naming Convention: - As the project size grows, so does the complexity of recognizing
the purpose of the variables. Thus the variables were given meaningful names, which
would help in understanding the context and the purpose of the variable. The function
names are also given meaningful names that can be easily understood by the user.

III. Indentation: - Judicious use of indentation can make the task of reading and
understanding a program much simpler. Indentation is an essential part of a good
program. If code id intended without thought it will seriously affect the readability of the
program. The higher-level statements like the definition of the variables, constants and
the function are indented, with each nested block indented, stating their purposes in the
code. Blank line is also left between each function definition to make the code look neat.
Indentation for each source file stating the purpose of the file is also done.

5.2. Coding Approach

Top-Down Approach:
A top-down approach (also known as stepwise design and in some cases used as a synonym
of decomposition) is essentially the breaking down of a system to gain insight into its
compositional sub-systems. In a top-down approach an overview of the system is formulated,
specifying but not detailing any first-level subsystems. Each subsystem is then refined in yet
greater detail, sometimes in many additional subsystem levels, until the entire specification is
reduced to base elements. A top-down model is often specified with the assistance of "black
boxes", these make it easier to manipulate. However, black boxes may fail to elucidate
elementary mechanisms or be detailed enough to realistically validate the model. Top down
approach starts with the big picture. It breaks down from there into smaller segments. A “top-
down” approach is where an executive decision maker or other top person makes the decisions of
how something should be done. This approach is disseminated under their authority to lower
levels in the hierarchy, who are, to a greater level or lesser extent, bound by them.

26
5.3. Screen Shots

Home Page:

Fig 5.1 Home Page

This is the home page. All other sections can be accessed through this page , navigation links of
about, services, blogs, contacts are available. Features of the company like internet, smart
living,entertainment is show in this page.

27
 Fig 5.2

This figure shows another services provided by the company. Different products like airtel, Vi, jio, BSNL
are shown. User can select one of these and proceed for further details. The customer can also click on the
learn more button and get details in brief.

Fig 5.3
This page is the part of home page itself. It is like short description of the services section for
complete details the user will have to click on the services navigation link.

28
 Fig 5.4
In this figure all packages offered by the company are shown. Different packages according to
user needs and with different offers etc are shown. User can select any plan according to their
need.

Fig 5.5
This is a short introduction of the news and article. A short display of news is provided on the
home page.

29
 Fig 5.6
This section is also a part of home page itself, the contact details of the company are provided,
any user can contact if they had any query.

Fig 5.7

30
 Fig 5.8
This page is showing past data, company approach , total number of users till now.

Fig 5.9
This is also part of the about section, the vision, mission, Values and another details are given.

31
 Fig 5.10

Fig 5.11
This figure is the section of services part. User can get access to different services provided by
the company. And from here also customer can navigate to other sections.

32
 Fig 5.12
These are the services which are offered by the company. User can buy a prepaid sim, a postpaid
sim. Hey can also go for broadband services. And can also buy DTH services.

Fig 5.13
This payment gateway will be opened when user choose any service out of postpaid, prepaid, DTH. User
will fill the details like name, email, address, city. The company of sim and prepaid or postpaid option.
After filing these details customer will have to fill details for payment .and as user will click on pay
button new window will be opened.

33
 Fig 5.14
This page will come after the customer click on the pay button. After clicking on the okay button
customer will go to the home page again.

Fig 5.15

34
 Fig 5.16
This figure shows the Blog section of the website. Any news any article related to the company
will be published on this page.

Fig 5.17

35
 Fig 5.18
This is the get in touch page of the website. Customer can write any query or any feedback they
want to give for the company. Complete address and the contact number is also provided so that
customer can interact.

Fig 5.19

36
 Fig 5.20
This page is for the admin only, admin can access all the data, orders made by customers etc. this
is the login page for the admin. Only admin have these credentials.

5.21
This page is opened after logging in with the credentials of the admin. Admin have access to all
sections of blogs, dashboards, feedbacks etc. admin can update or delete the data saved for the
website.

37
 Fig 5.22
This is the feedback section where all the feedbacks given by customers are stored and admin
can easily access these.

Fig 5.23
These are the subscription details, of the customers.

38
 Fig 5.24

Fig 5.25
This is the database section for contact, blog, feedbacks etc.

39
 Fig 5.26
This is the database section of the blogs part. Admin can delete, edit the details.

40
 Chapter 6
Testing
During testing the program to be tested is executed with the set of test cases and have the
output of the program for the test cases is evaluated to determine if the program is performing
as expected. Due to its approach dynamic testing can only ascertain the presence of errors in
the program, the exact nature of errors is not usually decided by testing. Testing forms is the
first in determining errors in the program.

Once a programs are tested individually then the system as a whole needs to be tested. During
testing the system is used experimentally to ensure that the software does not fail i.e. it will run
according to its specification. The programs executed to check for any syntax and logical
errors. The Errors are corrected and test is made to determine whether the program is doing
what it is supposed to do.

This system is tested using unit testing firstly then all the modules are integrated and again the
system is tested using integrated testing and it was find that system is working according to its
expectation.

6.1. Why testing is done

● Testing is the process of running a system with the intention of finding errors.
● Testing enhances the integrity of a system by detecting deviations in design and errors in
the system.
● Testing aims at detecting error-prone areas. This helps in the prevention of errors in a
system.
● Testing also add value to the product by confirming to the user requirements.

Causes of Errors
The most common causes of errors in a software system are:
● Communication gap between the developer and the business decision maker: A
communication gap between the developer and the business decision maker is normally due to
subtle differences between them. The differences can be classified into five broad areas:
Thought process, Background and Experience, Interest, Priorities, Language.
● Time provided to a developer to complete the project: A common source of errors in
projects comes from time constraints in delivering a product. To keep to the schedule, features

41
can be cut. To keep the features, the schedule can be slipped. Failing to adjust the feature set or
schedule when problems are discovered can lead to rushed work and flawed systems.
● Over Commitment by the developer: High enthusiasm can lead to over commitment by
the developer. In these situations, developers are usually unable to adhere to deadlines or quality
due to lack of resources or required skills on the team.
● Insufficient testing and quality control: Insufficient testing is also a major source of
breakdown of e-commerce systems during operations, as testing must be done during all phases
of development.
● Inadequate requirements gathering: A short time to market results in developers starting
work on the Web site development without truly understanding the business and technical
requirements. Also, developers may create client-side scripts using language that may not work
on some client browsers.
● Keeping pace with the fast changing Technology: New technologies are constantly
introduced. There may not be adequate time to develop expertise in the new technologies. This is
a problem for two reasons. First, the technology may not be properly implemented. Second, the
technology may not integrate well with the existing environment.

Testing Principles
● To discover as yet undiscovered errors.
● All tests should be traceable to customer’s requirement.
● Tests should be planned long before the testing actually begins.
● Testing should begin “in the small” & progress towards “testing in the large”.
● Exhaustive Testing is not possible.
● To be most effective training should be conducted by an Independent Third Party

Testing Objectives
● Testing is a process of executing a program with the intent of finding errors.
● A good test case is one that has a high probability of finding an as yet undiscovered error.
● A successful test is one that uncovers an as yet undiscovered error.

42
Developing a Test Plan:
The first step in testing is developing a test plan based on the product requirements. The test plan
is usually a formal document that ensures the product meets the following standards:

● Is thoroughly tested?  Untested code adds an unknown element to the product and

increases the risk of product failure.
● Meets product requirements: To meet customer needs, the product must provide the
features and behavior described in the product specification. For this reason, product
specifications should be clearly written and well understood.
● Does not contain defects: Features must work within established quality standards, and
those standards should be clearly stated within the test plan.

A good test plan answers the following questions:

● How are tests written?  Describe the languages and tools used for testing.
● Who is responsible for the testing?  List the teams or individuals who write and perform
the tests.
● When are the tests performed?  The testing schedule closely follows the development
schedule
● Where are the tests and how are test results shared?  Tests should be organized so that
they can be rerun on a regular basis.
● What is being tested?  Measurable goals with concrete targets let you know when you
have achieved success.
43
Some of these questions might have more than one answer, depending on the type of test. For
instance, individual developers are often responsible for writing the first level of tests for their
own code, while a separate testing team might be responsible for ensuring that all code works
together.

The following sections describe the different types of tests and the techniques used with Visual
Studio .NET to perform these tests.

6.2. TYPES OF TESTS

The test plan specifies the different types of tests that will be performed to ensure the product
meets customer requirements and does not contain defects. Table 10-1 describes the most
common test types.

Test type Ensures that

Unit test Each independent piece of code works correctly

Integration test All units work together without errors

Newly added features do not introduce errors to other

Regression test
features that are already working

Load test (also called stress test) The product continues to work under extreme usage

The product works on all of the target hardware and

Platform test
software platforms

A test plan has the following steps:

● Prepare test plan

● Specify conditions for user acceptance testing
● Prepare test data for program testing
● Prepare test data for transaction path testing
● Plan user testing
● Compile/Assemble program
● Prepare job performance aids
● Prepare operational documents
44
 Test Test Method Expected Actual Result Remarks
Subject Result

Complete The whole The project Because High HD picture Browser can
testing of project is should give Quality, the size of the sometime effect the
system executed the same Website Become Large & working and
on using output on on executing It takes Time performance of
different different all the to View. execution of the
browsers browsers like browsers. project.
opera,
Mozilla
firefox, and
internet
explorer.

Table: Test cases for system testing

⮚ Component testing
⮚ Integration testing
⮚ User testing

UNIT TESTING

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the
detailed design and the process specifications, testing is done to uncover errors within the
boundary of the module. All modules must be successful in the unit test before the start of the
integration testing begins.

INTEGRATION TESTING

After unit testing, we have to perform integration testing. The goal here is to see if modules can
be integrated properly, the emphasis being on testing interfaces between modules. This testing
activity can be considered as testing the design and hence the emphasis on testing module
interactions.

SYSTEM TESTING

Here the entire software system is tested. The reference document for this process is the
45
requirements document, and the goal is to see if software meets its requirements. Here entire
‘HRRP’ has been tested against requirements of project and it is checked whether all
requirements of project have been satisfied or not.

ACCEPTANCE TESTING

Acceptance Testing is performed with realistic data of the client to demonstrate that the software
is working satisfactorily. Testing here is focused on external behavior of the system; the internal
logic of program is not emphasized.

WHITE BOX TESTING

This is a unit testing method, where a unit will be taken at a time and tested thoroughly at a
statement level to find the maximum possible errors

White-box test focuses on the program control structure. Test cases are derived to ensure that all
statement in the program control structure. Test cases are derived to ensure that all statement in
the program control structure.

Test cases are derived to ensure that all statement in the program has been executed at least once
during testing and that all logical conditions have been exercised. Basis path testing, a white box
technique, makes use of program graphs (or graph matrices) to derive the set of linearly
independent test that will ensure coverage. Condition and data flow testing further exercising
degrees of complexity.

BLACK BOX TESTING

This testing method considers a module as a single unit and checks the unit at interface and
communication with other modules rather getting into details at statement level. Here the module
will be treated as a block that will take some input and generate output. Output for a given set of
input combinations are forwarded to other modules.

Black-box testing techniques focus on the information domain of the software, deriving test
cases by partitioning the input and output

TEST INFORMATION FLOW

A strategy for software testing may also be viewed in the context of the spiral. Unit testing
begins at the vortex of the spiral and, concentrates on each unit, component of the software as

46
implemented in source code.Testing progresses moving outward along the spiral to integration
testing, where the focus is on designed the construction of the software architecture.

System Testing

Validation Testing

Integration Testing

Validation testing

Fig: Stages of Testing

47
 Chapter 7
Implementation and Maintenance

An Implementation plan is a management tool for a specific policy measure, or package of

measures, designed to assist agencies to manage and monitor implementation effectively.

Implementation plans are intended to be scalable and flexible; reflecting the degree of urgency,
innovation, complexity and/or sensitivity associated with the particular policy measure. Agencies
are expected to exercise judgment in this area; however, the level of detail should be sufficient to
enable the agency to effectively manage the implementation of a policy measure.

At a minimum, plans should reflect the standards outlined in the Guide to Preparing
Implementation Plans.

Implementation is the stage in the project where the theoretical design is turned into the working
system and is giving confidence to the new system for the users i.e. will work efficiently and
effectively. It involves careful planning, investigation of the current system and its constraints on
implementation, design of method to achieve the change over, an evaluation, of change over
methods. A part from planning major task of preparing the implementation is education of users.
The more complex system is implemented, the more involved will be the system analysis and
design effort required just for implementation. An implementation coordinating committee based
on policies of individual organization has been appointed. The implementation process begins
with preparing a plan for the implementation for the system. According to this plan, the activities
are to be carried out, discussions may regarding the equipment has to be acquired to implement
the new system.

Implementation is the final and important phase. The most critical stage is in achieving a
successful new system and in giving the users confidence that the new system will work and be
effective. The system can be implemented only after thorough testing is done and if it found to
working according to the specification. This method also offers the greatest security since the old
system can take over if the errors are found or inability to handle certain types of transaction
while using the new system.

At the beginning of the development phase a preliminary implementation plan is created to

schedule and manage the many different activities that must be integrated into plan. The
implementation plan is updated throughout the development phase, culminating in a changeover

48
plan for the operation phase. The major elements of implementation plan are test plan, training
plan, equipment installation plan, and a conversion plan.

7.1 IMPLEMENTATION AND OUTPUTS

A crucial phase in the system development life cycle is the successful implementation of the new
system design. Implementation simply means converting a new system design into operation.
Implementation phase is used to translate the design phase into programming constructs. actual
implementation of the project is done or we can say that in this phase we develop all the aspect
of the project. In this phase the programmer also does user documentation of the project.

Implementation Phases: - These are the following implementation different phases.

Phase 1:- During this phase, the project water quality goals and plant capacity are set. Then,
with assistance from membrane manufacturers and specialty consultants, a critique of various
technologies is conducted to assess feasibility and cost-effectiveness of membrane options. Many
utilities can complete this phase with their own staff. It is crucial to give a “yes” or “no” to
membranes in this phase. Remember, membranes may not be the best option for all types of
waters and in every application.

Phase 2: - In this phase, advice from a specialized consultant is a must. This is when layouts and
conceptual design are done to evaluate membrane options. This is also the last practical and cost-
effective phase where you can go back to the feasibility study if the membrane is not found to be
the best alternative. Detailed water quality investigation and sometimes piloting is done in this
phase to verify membrane applicability and type of systems to use, as well as setting design
parameters for the next phase. Depending on the piloting requirements and periods, this phase
could take as little as two or three months to more than a year; if seasonal, water quality changes
are substantial. If a pilot study is required, a detailed test protocol should be prepared to not only
evaluate various manufacturers but also as a basis for operations and maintenance (O&M) cost
evaluation. It is highly recommended to prepare this test protocol with guidance from the
permitting agencies and make them a part of the decision process.
The conclusion of Phase 2 should determine what type of membrane to use and the membrane
manufacturer. If manufacturers were invited to pilot test, you must ensure that they are being

49
evaluated in a fair and open environment. Test protocol is the key evaluation tool. It is also
recommended to get them involved early in the draft test protocol so there are no surprises.

Phase 3:- Before starting Phase 3, all design parameters, plant capacity, reliability and
redundancy factors, stand-by provisions, temperature and water quality considerations must be
established. They will then become the design basis for the specialty consultant. Phase 3 is
essentially when the local engineers working with the specialty consultants to perform detail
designs and preparing the bidding documents while the local engineer is focusing on the site
work, building, incoming power, etc. The specialty consultant is doing detail design and layout
for the process equipment and setting the bidding requirements for the membrane system.
Depending on the project schedule and local requirements, typically three major submittals are
prepared: 20% to 30%, 60% to 70% and 100% design.
It is critical to establish the type of procurement and short list manufacturers, and identify all key
process needs during the 20% to 30% phase. Even with the same membrane technology, the
system layout, process needs and power/chemical requirements are very different.

Phase 4:- This phase is the most complex phase in membrane system implementation. There are
many different methods and ways of bidding membrane systems, each with its own
advantages/disadvantages.

Phase 5:- The success and smoothness of Phase 5 depends on phases 3 and 4. The single most
important factor becomes how detailed the bid document is and who is responsible for what
material and equipment, as well as testing and guarantees.

Phases 6 and 7: - Typically, each entity performs its own function in phases 6 and 7, except the
overall controls, for which one entity should be taking charge.

Phase 8: - This phase is preparing as- built, final O&M manuals and each entity completing its
punch lists. The specialty consultant can be of great assistance to compile all O&M and shop
drawings and provide a comprehensive operator training on the overall plant process, while each
supplier provides training of individual components.

Post implementation:-

50
A Post-Implementation Review (PIR) is an assessment and review of the completed working
solution. It will be performed after a period of live running, sometime after the project is
completed.
There are three purposes for a Post-Implementation Review:
● To ascertain the degree of success from the project, in particular, the extent to which it
met its objectives, delivered planned levels of benefit, and addressed the specific requirements as
originally defined.
● To examine the efficacy of all elements of the working business solution to see if further
improvements can be made to optimize the benefit delivered.

To learn lessons from this project, lessons which can be used by the team members and by the
organization to improve future project work and solutions.
In some cases, the first of these objectives can be a contractual issue. Where that is the case, it
may be safer to run separate reviews - one focused on contractual compliance and the other
seeking to derive further benefit from a no-blame review.
 
TYPES OF IMPLEMENTATION

● Implementation of a computer system to replace a manual system.

● Implementation of a new computer system to replace an existing system.
● Implementation of a modified application to replace an existing one, using the same
computer.
Successful implementation may not guarantee improvement in the organization using the new
system, but improper installation will prevent it. It has been observed that even the best system
cannot show good result if the analysts managing the implementation do not attend to every
important detail. This is an area where the systems analysts need to work with utmost care.

7.2 MAINTENANCE

Once the website is launched, it enters the maintenance phase. All systems need maintenance.
Maintenance is required because there are often some residual errors remaining in the system
that must be removed as they are discovered. Maintenance involves understanding the effects of
the change, making the changes to both the code and the documents, testing the new parts and
retesting the old parts that were not changed. Maintenance is mainly of two types:

1. Corrective Maintenance

51
 2. Adaptive Maintenance

7.2.1 Corrective Maintenance:

Almost all software that is developed has residual errors or bugs in them. Many of these surfaces
only after the system have been in operation, sometimes for a long time. These errors once
discovered need to be removed, leading to the software to be changed. This is called Corrective
Maintenance.

7.2.2 Adaptive Maintenance:

Even without bugs, software frequently undergoes change. The software often must be upgraded
and enhanced to include more features and provide more services. This requires modification of
the software. This type of maintenance is known as the Adaptive Maintenance

52
 Chapter 8
Conclusion
Telecom Services is PHP based website which contains information about various details of
Services Company. In this project, user can view information about various types of Services
available at the company Telecom services. Users can contact the admin also give feedback.
User can view pictures of company and their team. User can see contact information and location
of the office in website. User can contact the admin if they want to enquiry about any
information.

Admin will maintain all types of record on the website. Admin can view enquiries send by the
users and delete them. Admin can insert, update and delete the company information on the
website.
Telecom Services is a global leader in telecommunication, with over 40 years of experience in
the design and development of high performance network communication solutions.

53
 Chapter 9
Future scope of project
Thus, the future of the telecom sector will have to deal with additional advancements posited by
new technologies. Some digital applications of the future generation technologies are cloud
computing, Internet of Things (IoT), Artificial Intelligence (AI), 3-D Printing etc., where devices
shall communicate with each other. Big data and analytics are also there and thus proper policies
must be at place to handle security and privacy issues. IoT and other associated technologies are
likely to compound these problems. 

54
 Bibliography
Books Used:
• Software Engineering - R.S. Pressman
• PHP For Dummies
• PHP Begineers Guide ByMcGrawhill Publication
• Javascript By McGrawhill Publication

References Used:
• http://www.carrentingsolutions.com/
• Wikipedia.org
• www.w3schools.com

55