Automation of Business Requirement

INTRODUCTION OF BHARTI AIRTEL

Bharti Airtel Limited is a leading global telecommunications company with operations
in 20 countries across Asia and Africa. Headquartered in New Delhi, India, the company
ranks amongst the top 4 mobile service providers globally in terms of subscribers. In
India, the company's product offerings include 2G, 3G and 4G wireless services, mobile
commerce, fixed line services, high speed DSL broadband, IPTV, DTH, enterprise
services including national & international long distance services to carriers. In the rest of
the geographies, it offers 2G, 3G wireless services and mobile commerce. Bharti Airtel
had over 307 million customers across its operations at the end of November 2014.
Bharti Airtel Limited is an Indian multinational telecommunications Services Company
headquartered in New Delhi, India. It operates in 20 countries across South Asia, Africa,
and the Channel Islands. Airtel provides GSM, 3G and 4G LTE mobile services, fixed
line broadband and voice services depending upon the country of operation. It is
the largest cellular service provider in India, with 192.22 million subscribers as of August
2013. Airtel is the largest mobile operator in South Asia and the fourth largest in the
world by subscriber base.
Airtel is credited with pioneering the business strategy of outsourcing all of its business
operations except marketing, sales and finance and building the 'minutes factory' model
of high cost and low volumes. The strategy has since been adopted by several operators
because it is highly lucrative and easy. Airtel's telecom equipment is provided and
maintained by Ericsson and Nokia Solutions and Networks whereas IT support is
provided by IBM. The transmission towers are maintained by subsidiaries and joint
venture companies of Bharti including Bharti Infratel and Indus Towers in India. Ericsson
agreed for the first time to be paid by the minute for installation and maintenance of their
equipment rather than being paid up front, which allowed Airtel to provide low call rates
of 1/minute (US$0.02/minute).

11-CSE-2037

Page

Automation of Business Requirement

Corporate Structure
Airtel has two distinct Customer Business Units (CBU) with focus on B2C (Business to
Customer) and B2B (Business to Business) segments. Airtel's B2C business unit deals
with servicing the retail consumers, homes and small offices providing mobile, fixed line,
DTH and m-commerce services while the B2B unit deals with large corporate accounts.
Worldwide presence
Airtel is the one of the largest mobile operator in the world in terms of subscriber base
and has a commercial presence in 20 countries and the Channel Islands.
Its area of operations include:
The Indian Subcontinent:

Airtel India

Airtel Sri Lanka

Airtel Bangladesh

Airtel Africa

Highlights:

Bharti Airtel becomes the fourth largest mobile operator in the world.

Education is now available anytime, anywhere with Airtel mEducation.

Business Divisions:
Mobile Services: Bharti Airtel offers GSM mobile services in all the 22-telecom circles of
India and is the largest mobile service provider in the country, based on the number of
customers.
Telemedia Services: The group offers high-speed broadband with the best in class
network. With fixed line services in 87 cities, we help you stay in touch with your friends
& family and keep you updated round the clock.
Airtel Business: Airtel business provides a broad portfolio of services to large Enterprise,
Government, Small & Medium businesses and carrier customers. It is India's leading and
11-CSE-2037

Page

Automation of Business Requirement

most trusted provider of communication and ICT services, offering services that include
voice, data, network integration, data centre & managed services, enterprise mobile
applications and digital media.
Digital TV Services: Discover the magical experience of digital entertainment with Airtel.
From DVD quality picture and sound, the best and widest variety of channels and
programmes to the best on-demand content on Airtel Live, your TV viewing experience
change forever with digital TV from Airtel!
THE BRAND AIRTEL
Airtel was born free, a force unleashed into the market with a relentless and unwavering
determination to succeed. A spirit charged with energy, creativity and a team driven to
seize the day with an ambition to become the most admired telecom service provider
globally. Airtel, in just ten years of operations, rose to the pinnacle of achievement and
continues to lead.
As India's leading telecommunications company, Airtel brand has played the role of a
major catalyst

in India's reforms, contributing to its economic resurgence.

Today it touches people's lives with their Mobile services, Telemedia services, to
connecting India's leading 1000+ corporates. It also connects Indians living in USA, UK
and Canada with our call home service.

11-CSE-2037

Page

Automation of Business Requirement

Chapter 1: INTRODUCTION ABOUT THE PROJECT
Bharti Airtel Ltd. Being the largest cellular provider in India, deals with various other
companies for business purposes. Since Airtel outsources its Business Operations, it
requires an interface through which its business associates can file a business service
request and estimate whether it is profitable or not by consulting it with an appropriate
department head.
1.1 Business Service:
An IT Service that directly supports a Business Process, as opposed to an Infrastructure
Service which is used internally by the IT Service Provider and is not usually visible to
the Business. The term Business Service is also used to mean a Service that is delivered
to Business Customers by Business Units. For example delivery of financial services to
Customers of a bank, or goods to the Customers of a retail store. Successful delivery of
Business Services often depends on one or more IT Services.
1.2 Service Request:
A request from a User for information, or advice, or for a Standard Change or
for Access to an IT Service. For example to reset a password, or to provide standard IT
Services for a new User. Service Requests are usually handled by a Service Desk, and do
not require an RFC to be submitted.
A request for a change, usually both common and straightforward, to be made to
a service. A Service Request is characterized by the fact that the Change can be made
under strict, well-defined procedural control and is therefore (virtually) risk-free.
Providing access to services for a new member of staff and relocating PCs are two typical
examples
1.3 Business Service Requirement is a request made by an associate business partner or
a staff member to a company so as to fulfill their business requirements for the project
which is seen by the selected approver. A User can login into their account dashboard and
can view or add their new project requirements stored in the database
11-CSE-2037

Page

Automation of Business Requirement

Chapter 2: REQUIREMENTS, FEASIBILITY AND OBJECTIVES
2.1 REQUIREMENTS
2.1.1 Deployment environment
Deployment Platform

Core2duo Processor.

Deployment Environment

Google Chrome or Internet Explorer

Web Server

Apache Tomcat
Version-7.0

2.1.2 Software Requirements

Client Side
Web Browser

Google Chrome, Mozilla Firefox, IE, Bing

Server Side
Operating System

Microsoft Windows XP SP3, Windows 7,

Windows 8

2.1.3 Hardware Requirements

RAM

1 GB or above

Processor

Intel Pentium 3 or above

Disk Space

1GB or above

2.1.4 Technical Environment

Development Platform
11-CSE-2037

Java Server Pages

Page

Automation of Business Requirement

Development Language

Java J2EE and JavaScript

Database

MySQL Server

Database Connector

Version-5.6
MySQL Connector J

2.2 FEASIBILITY STUDY

The feasibility study proposes one or more conceptual solution to the problem set of the
project. In fact, it is an evaluation of whether it is worthwhile to proceed with project or
not.
Evaluation of feasibility of such solutions. Such evaluation often indicates shortcomings
in the initial goals. This step is repeated as the goals are adjusted and the alternative
solutions are evaluated.
Feasibility analysis usually considers a number of project alternatives, one that is chosen
as the most satisfactory solution. These alternatives also need to be evaluated in a broad
way without committing too many resources. Various steps involved in feasibility
analysis are:
To propose a set of solution that can realize the project goal. These solutions are usually
descriptions of what the new system should look like.
Four primary areas of interest in feasibility study are:
2.2.1 Economic Feasibility: An evaluation of development cost weighed against the
ultimate income of benefit derived from the development system of product. In economic
feasibility, cost benefit analysis is done in which expected cost and benefits are evaluated.
2.2.2 Technical Feasibility: Technical Feasibility includes existing and new H/W and
S/W requirements that are required to operate the project using JSP. The basic S/W
requirement is J2EE in which the front end of the online hospital management project has

11-CSE-2037

Page

Automation of Business Requirement

been done. The basic entry forms are developed in JSP and the data is stored in the MY
SQL.
2.2.3 Operational Feasibility: Operational feasibility is mainly concerned with issues
like whether the system will be used if it is developed and implemented. Whether there
will be resistance from users that will affect the possible application benefits? The
essential questions that help in testing the technical feasibility of a system are following:
Does management support the project?
Are the users not happy with current business practices? Will it reduce the time
considerably? If yes, then they will welcome the change and the new system.
Have the users involved in the planning and development of the project? Early
involvement reduced the probability of resistance towards the new system.
Will the proposed system really benefit the organization? Does the overall
response increase? Will accessibility of information be lost? Will the system affect
the customers in considerable way?
2.2.4 Legal Feasibility: A determination of any infringement, violation, or liability that
could result from development of the system. Legal feasibility tells that the software used
in the project should be original purchased from the legal authorities and they have the
license to use it or the software are pirated.
2.3 OBJECTIVES
The objectives of the project are broadly the following:
1. The first objective of the project was to gain the skills required to develop this portal.
This involved learning and gaining expertise on the interfaces being used in this industry
i.e. JSP, JavaScript, MySQL and Apache Tomcat.
2. The second objective of the project was to plan, in detail, the entire User Interface of the
portal i.e. how the different aspects of the portal such as login, home page, registration
page would appear to the associates.
3. After the UI had been planned, the third objective involved coding which enables the
business user to store his/her business request in the database.
11-CSE-2037

Page

Automation of Business Requirement

4. The fourth objective of the project was to understand and implement the methodology by
which the retrieved information from database can be sorted or filtered using certain
parameters.

Chapter 3: ANALYSIS, ACTIVITY TIME SCHEDULE (PERT)

A business requirements analysis is an overall comprehensive declaration of what the
project is supposed to achieve. This is a step-by-step procedure to discover, analyze, and
document the essential requirements connected to a business project.
3.1 Software Requirements Specification
The software requirement specification document is written by the development team
with the help of the documents management system. The specifications for the Portal for
request submission in an operating environment are stated below.
11-CSE-2037

Page

Automation of Business Requirement

3.1.1 Introduction
This document aims at defining the overall software requirements for Portal for Business
Requirement. Efforts have been made to define the requirements exhaustively and
accurately. The final product will be have all functionalities as described in this document
and no assumption is made by any of the parties involved in development, testing,
implementation or using this product. In case furthermore any other functionality or
feature is required then, it must be reported formally and subsequently a new release of
this document will be released and will be reflected in final product. These steps will
further explain the analysis:
Step 1: Identify the project requirements: The requirements describes the capabilities that will
be incorporated into portal for Business Request Submission. All the constraints have to
be listed in the document by which the system will abide. The intended audiences for the
document are the development team, testing team and users of the product.
Step 2: Capture the listed requirements: This portal will be a web based application
intended for documentation management system of the organisation. This system is to be
developed for managing documents of the different requests and from any location in
contrast to conventional documentation management system. The related reports are to be
generated in a portable document format. The information must be presented in a modern
graphical user interface.
Step 3: Use the requirements to achieve the product: In developing the portal, the
following services should be provided by the system:
1. Employees or associates will login using their Username.
2. A new user should also be able to register himself/herself.
3. A User can create a new request or view the existing ones.
4. The new request should be forwarded to the respective department head.
5. Every new request will be distinguished with a unique TicketID.
6. The status for each request will also get updated.

3.2 Schedule Estimate

11-CSE-2037

Page

Automation of Business Requirement

Over the course of the project the methodology for project schedule that is being used to
make this project complete and working well as follows:
During the project development, the project scope is adjusted in order to get the
maximum business value from the project. The methodology for project schedule being
adopted is based on rapid application development model. The process involves user
participation at each step of software development cycle. This methodology focuses on
resolving requests faster with higher quality.

CHAPTER 4- DESIGN
4.1 Overall System design

11-CSE-2037

Page |

Automation of Business Requirement

4.2 Activity Designs

4.2.1 Login Activity

11-CSE-2037

Page |

Automation of Business Requirement

4.2.2 Home Page Activity

11-CSE-2037

Page |

Automation of Business Requirement

4.3 Database Design

11-CSE-2037

Page |

Automation of Business Requirement

Column Name

Data Type

Remarks

ID

INT(10) UNSIGNED

AUTO_INCREMENT

FIRST_NAME

VARCHAR(45)

NOT NULL

LAST_NAME

VARCHAR(45)

NOT NULL

EMAIL

VARCHAR(45)

NOT NULL

UNAME

VARCHAR(45)

NOT NULL

PASS

VARCHAR(45)

NOT NULL

REGDATE

DATE

NOT NULL

Column Name

Data Type

Remarks

REQ_SUBJ

VARCHAR(255)

NOT NULL

APPR

VARCHAR(255)

NOT NULL

IBM

VARCHAR(255)

NOT NULL

BR_JUST

VARCHAR(255)

NOT NULL

DOC_UP

VARCHAR(255)

NULL

BUD_DESC

VARCHAR(255)

NULL

4.3.1 MEMBERS table:

4.3.2 BR table:

CHAPTER 5- IMPLEMENTATION

11-CSE-2037

Page |

Automation of Business Requirement

5.1 IMPLEMENTATION
5.1.1 Login and Validation
The user i.e. business associate or the employee logins here.

5.1.2 Registration
A new business associate can register here.
11-CSE-2037

Page |

Automation of Business Requirement

5.1.3 User successfully registered

5.1.4 Search Screen

11-CSE-2037

Page |

Automation of Business Requirement

5.1.5 Create new request

11-CSE-2037

Page |

Automation of Business Requirement

5.2 TESTING
5.2.1 System testing
Here the System testing involved is the most widely used testing process consisting of
five stages as shown in the figure. In general, the sequence of testing activities is
component testing, integration testing, and then user testing. However, as defects are
discovered at any one stage, they require program modifications to correct them and this
may require other stages in the testing process to be repeated.

Unit testing

Module
testing
Sub-system
testing
System
testing
Acceptance
testing

(Component testing)

(Integration testing)

(User testing)

Fig-5.1

11-CSE-2037

Page |

Automation of Business Requirement

Testing is the process of detecting errors. Testing performs a very critical role for quality
assurance and for ensuring the reliability of the software. The results of testing are used
later on during maintenance also.
Testing is vital to the success of the system. System testing makes a logical assumption
that if the parts of the system are correct, the goal will be successfully achieved. In
adequate testing or non-testing leads to errors that may not appear until months or even
years later (Remember the New York three day power failure due to a misplaced Break
statement).
This creates two problems:
1. The time lag between the cause and the appearance of the problem.
2. The time interval effect of the system errors on files and the records on the
system.
A small error can conceivably explode into a much larger problem. Effective testing early
in the process translates directly into long term cost savings from a reduced number of
errors.
Another reason for system testing is its utility as a user oriented vehicle before
implementation. The best program is worthless if it does not meet the user requirements.
Unfortunately, the users demands are often compromised by efforts to facilitate program
or design efficiency in terms of processing time or design efficiency.
Thus in this phase we went to test the code we wrote. We needed to know if the code
compiled with the design or not? Whether the code gave the desired outputs on given
inputs? Whether it was ready to be installed on the users computer or some more
modifications were needed
Through the web applications are characteristically different from there software
counterparts but the basic approach for testing these web applications is quite similar.
These basic steps of testing have been picked from software engineering practices. The
following are the steps, we undertook:
1. The content of the Intranet site is reviewed to uncover Content
2. The design model of the web application is reviewed to uncover the navigation
errors. Use cases, derived as a part of the analysis activity allows a web designer
11-CSE-2037

Page |

Automation of Business Requirement

to exercise each usage scenario against the architectural and navigational design.
In essence these non-executable tests help to uncover the errors in navigation.
3. When web applications are considered the concept of unit changes. Each web
page

encapsulate

content

navigation

links,

content

and

processing

elements(Forms, Scripts, JSPs as in our case). It is not always possible to test

each of these individually. Thus is the base of the web applications the unit to be
considered is the web page. Unlike the testing of the algorithmic details of a
module the data that flows across the module interface, page level testing for web
applications is driven by content, processing and links encapsulating the web
page.
4.

The Assembled web application is tested for overall functionality and content
delivery. the various user cases are used that test the system for errors and
mistakes.

5. The Web application is tested for a variety of environmental settings and is tested
for various configurations and upon various platforms.
6. Thread based testing is done to monitor the regression tests so that the site does
not become very slow is a lot of users are simultaneously logged on.
7. A controlled and monitored population of end users tests Intranet application , this
all comprises of the User Acceptance Testing .
Because web application evolve continuously , the testing process is an ongoing activity,
conducted by web support staff in our case the Organizations IS people who will finally
update and manage the application.
5.2.2 Psychology of testing
The aim of testing is often to demonstrate that a program works by showing that it has no
errors. The basic purpose of testing phase is to detect the errors that may be present in the
program. Hence one should not start testing with the intent of showing that a program
works, but the intent should be to show that a program doesnt work. Testing is the
process of executing a program with the intent of finding errors.
11-CSE-2037

Page |

Automation of Business Requirement

Testing objectives:
The main objective of testing is to uncover a host of errors, systematically and with
minimum effort and time. Stating formally, we can say,

Testing is a process of executing a program with the intent of finding an error.

A successful test is one that uncovers an as yet undiscovered error.

A good test case is one that has a high probability of finding error, if it exists.

The tests are inadequate to detect possibly present errors.

The software more or less confirms to the quality and reliable standards.

Levels of testing
In order to uncover the errors present in different phases, we have the concept of levels of
testing. The basic levels of testing are

Client Needs

Acceptance

Testing
Requirements

System Testing

Design

Integration Testing

Code

Unit Testing
Fig-5.2

5.2.3 Unit testing

11-CSE-2037

Page |

Automation of Business Requirement

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.
In this project each service can be thought of a module. There are so many modules like
Login, HR Department, Interviewer Section, etc. Each module has been tested by giving
different sets of inputs. When developing the module as well as finishing the
development, the module works without any error. The inputs are validated when
accepting them from the user.
5.2.4 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.
In this project the main system is formed by integrating all the modules. When integrating
all the modules I have checked whether the integration effects working of any of the
services by giving different combinations of inputs with which the two services run
perfectly before Integration.
5.2.5 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.
Test cases should be selected so that the largest number of attributes of an equivalence
class is exercised at once. The testing phase is an important part of software development.
It is the process of finding errors and missing operations and also a complete verification
to determine whether the objectives are met and the user requirements are satisfied.
5.2.6 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.

11-CSE-2037

Page |

Automation of Business Requirement

I tested step wise every piece of code, taking care that every statement in the code is
executed at least once. The white box testing is also called Glass Box Testing.
I have generated a list of test cases, sample data, which is used to check all possible
combinations of execution paths through the code at every module level.
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.
5.2.7 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 test are designed to uncover errors functional requirement without regard to
the internal workings of a program. Black-box testing techniques focus on the
information domain of the software, deriving test cases by partitioning the input and
output domain of a program in manner that provides through test coverage. Graph based
testing methods explore the relationship between and behavior of program objects.
Equivalence partitioning divides the input classes of data are likely to exercise specific
software function. Boundary values analysis probes the programs ability to handle data at
the limits of acceptability.
5.3 Test Plan
Testing process starts with a test plan. This plan identifies all the testing related
activities that must be performed and specifies the schedules, allocates the
resources, and specified guidelines for testing. During the testing of the unit the
specified test cases are executed and
11-CSE-2037

Page |

Automation of Business Requirement

The actual result compared with the expected output. The final output of the
testing phase is the test report and the error report. The following tables represents
various test cases of unit testing.
Testing has been carried out at every stage of the project, some of the test cases are listed
as follows:
5.3.1 Test Cases
No.

Description

Expected

Actual

Output

Output

1.

To check whether each Submit-Button is Yes

Yes

2.

Working correctly.
To check whether each Reset-Button is Yes

Yes

3.

Working correctly.
To check whether the different text boxes are Yes

Yes

enabled and populated

according to proper selection.
4.

To check the connectivity with the database.

Yes

Yes

5.

To check whether the correct data is going to Yes

Yes

the correct field of the correct table.

6.

To check whether the application is

Yes

Yes

running properly at remote side.

11-CSE-2037

Page |

Automation of Business Requirement

BIBLOGRAPHY
1. The following books were referenced before starting and during the project:
a.
b.
c.
d.
e.
f.
g.

2.
a.
b.
c.
d.
e.
f.

Fundamentals of database systems by Navathe

HeadFirst Servlets and JSP
MySQL by Paul DuBois
PL/SQL by Ivan Bayross
The complete reference Java
The complete reference JSP
The complete reference SQL

Sources:
www.google.com
www.wikipedia.com
http://www.tutorialspoint.com
http://www.coreservlets.com/Apache-Tomcat-Tutorial/
http://mrbool.com/how-to-create-a-login-form-with-jsp/25685
http://stackoverflow.com/

11-CSE-2037

Page |