School of Computer Science and Engineering

INTERNSHIP PROJECT REPORT

(Project Term January – May, 2019)

(Web Portal Enhancement– UPoint Implementation)

Submitted by

Name: Jashanpreet Kaur Registration Number: 11504725

Course Code: CSE441 (Industry Internship Project)

Under the Guidance of

Sukhwinder Singh—Manager of South-West SWAT Team

Wipro, Noida
ii
 DECLARATION

I hereby declare that the project work entitled “Web Portal Enhancement– UPoint
Implementation” is an authentic record of my own work carried out as requirements of
Internship Project for the award of B.Tech degree in Computer Science and Engineering
from Lovely Professional University, Phagwara, under the guidance of Sukhwinder Singh,
during January to May 2019. All the information furnished in this internship project report
is based on my own intensive work and is genuine.

Name of Student: Jashanpreet Kaur Signature of Student

Registration Number: 11504725 Date: 22-05-2019

iii
 CERTIFICATE

This is to certify that the declaration statement made by the student is correct to the best of
my knowledge and belief. He is ongoing with this Internship Project under my guidance
and supervision. The present work is the result of his original investigation, effort and
study. No part of the work has ever been submitted for any other degree at any University.
The Internship Project is fit for the submission and partial fulfillment of the conditions for
the award of B.Tech degree in Computer Science and Engineering from Lovely
Professional University, Phagwara.

Signature and Name of the Manager

Sukhwinder Singh

Designation
Manager (DC, South-West, SWAT Team)
Wipro Technologies
Sector – 127, Noida, UP-201301

Date: 22-05-2019

Name and Signature of mentor

Mr. Aseem Kumar Sukhija

Lovely Professional University, Phagwara.

iv
 ACKNOWLEDGEMNET

I hereby acknowledge that the project work entitled “Web Portal Enhancement– UPoint
Implementation” is an authentic record of my own work carried out as requirements of
Internship Project for the award of B.Tech degree in Computer Science and Engineering
from Lovely Professional University, Phagwara, under the guidance of Sukhwinder
Singh, during January to April 2018. All the information furnished in this internship
project report is based on my own intensive work and is genuine. I am thankful to the entire
people who have helped me in doing my internship project.

Name of Student: Jashanpreet Kaur Signature of Student

Registration Number: 11504725 Date: 22-05-2019

v
 TABLE OF CONTENTS

1. Introduction… ................................................................................................. (7)

2. Profile of the Problem… ............................................................................... (10)
3. Existing System…..........................................................................................(11)
3.1. Introduction ............................................................................................ (11)
3.2. Existing Software ................................................................................... (11)
3.3. DFD for present Software .......................................................................(12)
3.4. What’s new in the system to be developed..............................................(13)
4. Problem Analysis .......................................................................................... (14)
4.1. Product definition ................................................................................... (15)
4.2. Feasibility Analysis ................................................................................ (15)
4.3. Project Plan ............................................................................................. (15)
5. Software Requirement Analysis.....................................................................(16)
5.1. Introduction ............................................................................................ (16)
5.2. General Description ................................................................................ (16)
5.3. Specific Requirement ............................................................................. (17)
6. Design ........................................................................................................... (18)
6.1. System Design.........................................................................................(18)
6.2. Flow Chart…...........................................................................................(19)
7. Testing........................................................................................................... (20)
7.1. Functional testing ................................................................................... (20)
7.2. Levels of testing ...................................................................................... (21)
7.3. Testing the project… .............................................................................. (21)
8. Implementation… ........................................................................... (22)
8.1. Implementation of the project. ............................................................... (22)
8.2. Post-Implementation and Software Maintenance ................................... (22)
9. Project Legacy ................................................................................. (23)
9.1. Current Status of the project… ...............................................................(23)
9.2. Remaining Areas of concern… ...............................................................(23)
9.3. Technical and Managerial lesson learnt… .......................... (23)
10. System Snapshots….........................................................................(24)
11. Bibliography .................................................................................... (39)

vi
1. INTRODUCTION
When it comes to the compensation, every employee thinks, the salary should be
good enough to fulfill all the daily needs and to secure their future. It is the employer’s
responsibility that they must provide all the facilities to its employees in order to stay
in the company for longer time. The employer provides extra facilities and these are
known as Benefits.
Benefits can be of different types which include employer’s contribution (“bonus”) to
employee’s contribution, after retirement benefits, in-service retirement savings, health
insurance, medical insurance, life insurance, transport and increments.
These benefits are provided to employees on the basis of their service time, age and
type of benefits they have chosen. The amount of benefit needs to be calculated on a
regular interval of time, which requires a different team in the organization who will do
all these management. But hiring new people and making a new department in the
organization will cost a lot of money and effort that is not possible for the organization.
So, here comes in the picture, a multinational company Wipro.
The organization/companies are known as clients for alight, these clients come to
Wipro, which maintains the database of the employees of the alight’s client. These
employees are known as participants for alight. Alight provide benefit management
tools and software to the clients and is also responsible for the maintenance and
ongoing changes. The benefit administration done by alight is divided into three
domains discussed as follows:

1.1. DEFINED CONTRIBUTION (DC)

It is also known as 401(K) account. It can save money during employment for
their retirements. Employer may also contribute as well. Deduction or participant’s
payroll checks (pay checks). For employees it helps in tax saving and retirement
benefits. It is cost effective for employers. Participants have the option of choosing an
investment option from a variety of funds available. Here the ownership on the
investment is of employees and the risk associated with this investment is of
employees.
1.2. DEFINED BENEFITS (DB)

It is also known as pension plan. It is based on the formula which calculates

the benefits of participants on the basis of their age, service and salary. In this plan the
contribution is made by employer. The initial owner of the plan is employer. Employee
gets the ownership after the retirement or it depends on employer’s rule.

1.3. HEALTH AND MAINTENANCE (HM)

This plan includes health and wealth services which divide into two subgroup
as mentioned follows:

1.3.1. PREVENTIVE CARE

It focuses on the benefits related to following conditions:

i. Medical
ii. Dental
iii. Vision

1.3.2. FINANCIAL SUPPORT

It focuses on the benefits related to following conditions:

i. Medical insurance
ii. Life insurance
iii. Health insurance

The process of maintaining participant’s plan starts when they start enrolling into the
plan. They can either enroll into a single plan or multiple plans from the above
discussed.
The different teams of alight can be better understood in the form of a tree which
develop the system for new clients or change in the existing system of clients. Alight
collect the data from the clients and maintain in its database and TBA system. The TBA
structure and Human Resource Outsourcing Methodology (HROM) structure is
discussed as follows.

8
 ALIGHT

Total Benefit Administration (TBA)

Ongoing
Implementation Ongoing Change
Delivery Group
Service/Delivery Group (OCG)
(ODG)
Group (ISG/IDG) For existing
For new client system
system

Domain Operation Customer Service

(DC/DB/HM) (BOA &OCP) administration
(CSA)

Human Resource
Outsourcing Methodology
(HROM)

System Development Life Cycle Human Resource Outsourcing

(SDLC) Delivery (HROD)

ODG
ISG/IDG OCG

Tree Structure 1: Alight TBA System

9
2. PROFILE OF THE PROBLEM
After enrolling into a plan the details come to alight, and they maintain the data
and into TBA System which further process these data to start participant’s contribution
and deduct the contribution amount from their payroll. But it not only limited to
enrolling into the plan. Participants need to know the details of their account, make
changes in their contribution amount, withdraw money either on temporary basis or
permanently, applying for loans, manage their beneficiary details, change in their
personal details like address change, date of birth, adding more contributions to the plan
or enrolling into another plan when their eligible etc.

So, this required the participants to call every time the benefit centers or Interactive
Voice Response (IVR) to make their changes. But later this system became
inconvenient to the participants. It was also inconvenient for the employers to provide
the services by collecting the daily data and processing the daily job by this method.
Then, the employers shared this problem of their participants with alight and alight
came up with the solution to make a new system which can be used by participants as
well as employers through which every individual participant can make changes and all
those requirements for which they used to call the benefit center, can be done by their
own. The new system was proposed as UPoint. An online portal, a website of the
organization in which the participants are employed. This portal is customized
according to need of individual employer (organization). This new system is being
delivered to the clients and it is solving the participant’s as well as client’s problem.
The changes in this system are made according the client’s profile of the problem and
requirements.

10
3. EXISTING SYSTEM
3.1. INTRODUCTION

The existing TBA system and Your Benefit Resource (YBR) are the tools that
are used to maintain participant’s data. YBR is the online website through which
participants manage their accounts. According to increase need and technology, this
YBR is needed to be upgraded. This upgraded version of YBR is known UPoint.

3.2. EXISTING SOFTWARE

The existing software is described into parts as follows:

3.2.1. HRO MAESTRO

This tool is for alight people. All the tasks related to clients are created and
assigned through this tool to the related team. The discussions, supports, and issues are
done through this tool.

3.2.2. GRAPHICAL USER INTERFACE (GUI)

This tool is also for alight people. This tool is used to upload, update and change
the participant’s data by running the activities/events on TBA System. This tool is also
used to get the enquiry of the plans of the participants. This is the backend tool for
maintain the participants and can also be used when user in not able to request any query
from UPoint. This can be done by calling to the benefit center.

3.2.3. ADVANCE TABLE EDITOR (ATE)

This is the database where participants are stored. The queries are already
written in the tool. There is no need to write a full big query to find a particular type of
participants. Just need to give the values and results will be in front of us. This tool has
been made to save time and resources.

3.2.4. YOUR BENEFIT RESOURCE (YBR)

The website for end users (participants) to maintain their account and apply for
loans, withdrawals, check status, action needed, etc.

11
3.3 DATA FLOW DIAGRAM (DFD)

3.3.1 LEVEL 0

INPUT
USER TBA
0.1 0.2
OUTPUT

3.3.2 LEVEL 1

VERIFICATION
LOG IN DATABASE
YBR
1 UNSECCESSFULL

YBR
YOUR ACTION HOME PAGE
NEEDED 1.1
1.1.1
LIFE
HEALTH & EVENT
USER INSURANCE 1.1.3
Backend

0 1.1.2 KNOWLEDGE
CENTRE
1.1.5
SAVINGS &
RETIREMENTS
1.1.4 YOUR PROFILE
1.1.6
User side

SECURE
MAILBOX
1.1.7

12
3.4 WHAT’S NEW IN THE SYSTEM TO BE DEVELEPED

The new system is the updated version of YBR, which will be having new look,
features, enhancements, security and all these things. It will be having 7 section,
discussed follows:
3.4.1 LIFE EVENTS

This section will be used when there is any life event in the user’s life. For
example marriage, child birth, death, changes property, etc.
3.4.2 YOUR PROFILE

This section used for managing personal information. For example DOB, address,
contact, etc.
3.4.3 SAVINGS AND RETIREMENTS

This section is used to maintain user’s DC plan. In which they can view their plan
balance, fund investment strategy, fund performance, apply loan, withdraw money,
distribute rollover the plan balance, enroll into the plan, add contribution, change
contribution, fund transfer, reallocation, etc.
3.4.4 HEALTH AND MAINTENANCE

This section is used to maintain their HW plan. In which they can maintain the
health insurance, medical insurance, life insurance, medical insurance and other
education loan facilities, etc.
3.4.5 KNOWLWDGE CENTRE

This section is used for getting information about employer’s plan and policies,
guidance about enrolling into the plan, investing into funds, etc.
3.4.6 YOUR ACTION NEEDED

This section is used when there is any action need to be completed by user and
these actions are generated either by system or employer.
3.4.7 SECURE MAILBOX

This section is like personal mailbox, where user gets information about their plan
and some PCS.

13
4 PROBLEM ANALYSIS

After enrolling into a plan the details come to alight, and they maintain the data
and into TBA System which further process these data to start participant’s contribution
and deduct the contribution amount from their payroll. But it not only limited to
enrolling into the plan. Participants need to know the details of their account, make
changes in their contribution amount, withdraw money either on temporary basis or
permanently, applying for loans, manage their beneficiary details, change in their
personal details like address change, date of birth, adding more contributions to the plan
or enrolling into another plan when their eligible etc. After the analysis of the problem
the related tasks assigns to different teams through Maestro.

4.3 PRODUCT DEFINITION

The new system was proposed as UPoint. An online portal, a website of the
organization in which the participants are employed. This portal is customized
according to need of individual employer (organization). This new system is being
delivered to the clients and it is solving the participant’s as well as client’s problem.
The changes in this system are made according the client’s profile of the problem and
requirements. The new system is the updated version of YBR, which will be having
new look, features, enhancements, security and all these things. It will be having 7
section, discussed follows:
4.3.1 LIFE EVENTS

This section will be used when there is any life event in the user’s life. For
example marriage, child birth, death, changes property, etc.
4.3.2 YOUR PROFILE

This section used for managing personal information. For example DOB, address,
contact, etc.
4.3.3 SAVINGS AND RETIREMENTS

This section is used to maintain user’s DC plan. In which they can view their plan
balance, fund investment strategy, fund performance, apply loan, withdraw money,
distribute rollover the plan balance, enroll into the plan, add contribution, change
contribution, fund transfer, reallocation, etc.

14
 4.3.4 HEALTH AND MAINTENANCE

This section is used to maintain their HW plan. In which they can maintain the
health insurance, medical insurance, life insurance, medical insurance and other
education loan facilities, etc.
4.3.5 KNOWLWDGE CENTRE

This section is used for getting information about employer’s plan and policies,
guidance about enrolling into the plan, investing into funds, etc.
4.3.6 YOUR ACTION NEEDED

This section is used when there is any action need to be completed by user and
these actions are generated either by system or employer.
4.3.7 SECURE MAILBOX

This section is like personal mailbox, where user gets information about their plan
and some PCS.

4.4 FEASIBILITY ANALYSIS

The feasibility analysis goals to the acceptance of the product to the working
environment flawless. It should support multiple browsers, all the functions that has
been implemented into the system should be visible to user and should be able to
perform required action without any technical difficulty or system error.
4.5 PROJECT PLAN

The project when comes to alight, it is assigned to different teams. If the project
is of new implantation, then it comes to Product Deployment Team, which comes under
IDG. If the project is of existing system, then it goes to Plan Change team which comes
under OCG. The tasks are assigned on maestro with a due date in a series of tasks,
which are completed in a chain. For example:
Analysis and Documentation Configuration and Unit Testing Integration
Testing Regression testing I-cat/e-cat preparation and execution Prod
Verification Prod Migration.

15
5. SOFTWARE REQUIREMENT ANALYSIS

a. INTRODUCTION

The new system was proposed as UPoint. An online portal, a website of the
organization in which the participants are employed. This portal is customized
according to need of individual employer (organization). This new system is being
delivered to the clients and it is solving the participant’s as well as client’s problem.
The changes in this system are made according the client’s profile of the problem and
requirements. The new system is the updated version of YBR, which will be having
new look, features, enhancements, security and all these things. It will be having 7
sections.
b. GENERAL DESCRIPTION

The system should have the following functionalities:

i. Able to view the plan account.
ii. Able to view fund performance.
iii. Able to invest into funds.
iv. Able to change contributions.
v. Able to enroll into plan.
vi. Able to view company’s policies and schemes.
vii. Able to receive PCS and mails.
viii. Able to change personal information.
ix. Able to add life events.
x. Able to add money into plan.
xi. Able to apply for loan.
xii. Able to withdraw money from plan.
xiii. Able to distribute money.
xiv. Able to transfer funds.
xv. Able to reallocate plan balance into multiple funds.
xvi. Able to perform actions generated by system.
xvii. Able to change password.
xviii. Able to add beneficiary.
xix. Able to view account details.

16
 c. SPECIFIC REQUIREMENTS

These are the customizable requirement that depends client to client.

i. Company Detail.
ii. Design & Layout.
iii. Templates.

17
6. DESIGN

a. SYSTEM DESIGN

Every functionality in the system is referred as activity. These activities are

composed of different components. The below mentioned structure is an example of
one activity.

Category Client
Definition Defined
Field Set

Transactions Transaction
(Required) (Optional)

Activity

Request Enquiry
Panel Panel

Elemental Composite
Function Function

18
 b. FLOW CHART

UPOINT LOGIN
(USER ID & PASSWORD)

HOME
(Tiles, Highlights, Tips, Company
Logo, etc.)

LIFE EVENTS SAVINGS & RETIREMENTS YOUR PROFILE

(Child Birth, (Account Summary, (DOB, Address,
Marriage, Death, Withdrawal & Loan, Phone, Email,
Property Buy/Sell, Investments, Enroll, Password, SSN,
etc.) Account Activity, etc.)
Beneficiaries, Fund
Election,
Contribution, etc.)

SECURE MAILBOX HEALTH AND KNOWLEDGE

(PCS, notices, WEALFARE CENTER
forms, messages, (Medical (Policies, guidance,
etc.) Insurance, Health procedures, etc.)
Insurance, Life
Insurance,
Finance, etc.)

YOUR ACTION
NEEDED
(Enroll into the CONTACT US
plan, start saving, (BENEFIT CENTER)
add beneficiary,
LOG OUT
loan payoff,
confirm residence,
etc.)

19
7. TESTING

Testing is the most important stage of any software development life cycle,
where all the bugs, defects, misbehaviors, faulty configurations, missing requirements
and all are tested and are documented. In alight, the testing tasks are given high priority
and these tasks are performed by SCS role. There is performed unit testing, integration
testing, and regression testing, I-cat/e-cat, and production verification.
a. FUNCTIONAL TESTING

In this testing, all the minor and major areas are covered for testing. So that,
there should not be any bug in the software or the configuration that has been done in
the system. There are some common points that are tested in all the projects.
i. Browser support like Mozilla, Chrome, Safari, etc.
ii. Functionality of buttons implanted.
iii. Visibility of each component implemented.
iv. Smooth flow of a process that is in process.
v. No option should jump by skipping any step in any process.
vi. Link routing.
vii. Matching the data of UPoint with GUI.
viii. Matching the data on back date as well as future date
ix. PCS related testing covers that each and every information about a particular
transaction should print in a proper format.
x. Company logo and details should be visible where the requirement was.
xi. Contact information of company should be there on PCS.
xii. While processing the activity, it should trigger the edit, if there is any.
xiii. These edits are like red, yellow and green.
xiv. Correct amount of money is taken or contributed from/to the plan and it should be
updated in the database.
xv. There should not be any system error while processing the activity.
xvi. Each and every page should be able to load on browser in UPoint.
xvii. User should be able to login/ logout from the UPoint.
xviii. The color scheme and template should be according to company’s requirement.

20
 b. LEVEL OF TESTING

The level of testing has been discussed below.

i. UNIT TESTING

This is performed after making the changes in the system or after adding new
functionality by taking only major parts in consideration.
ii. INTEGRATION TESTING

This testing covers each and every corner of the system in detail and tested all
the functionality of new system implemented. If there is any defect or unexpected
behavioral of system occurs then a support issue is generated and after resolving the
issue, it is again tested.
iii. REGRESSION TESTING

This testing is done by considering only risky areas, where the chance of failing
the system is more and also if there is any changes made to the system.
iv. PRODUCTION VERIFICATION

This is the step which is performed after migrating the system from testing
environment to live environment before delivering it to the client because sometimes it
happens that the system is working fine in testing environment but fails while migrating
to live environment. So, this resolves the issue.
c. TESTING THE PROJECT

The complete project is tested by client team and that process is known as I-cat/
e-cat. Where I-cat stands for Internal Client Assurance testing which is done by internal
client team who on not interact with our clients and e-cat stands for External Client
Assurance Testing. This is performed by the client team who deliver the product to our
clients. After this testing the client team gets assures that everything is working fine and
now can be delivered to client to run it in live environment.

21
8. IMPLEMENTATION

The projects come to alight for development of new system or to make the
changes in the existing system is divided into four environments.

Database
(Environment)

Development Test Staging Production

Database Database Database Database
(Base (Unit & (Regression (Live
Development) Integration Testing) Environment)
Testing)

Flow of the project

a. IMPLEMENTING THE PROJECT

This is the final step of SDLC; the project is moved to production database. This
process is called migration. After development and testing in test database, the project
is migrated to staging database where after performing the testing it is migrated to
production database and that is the live environment where the developed project is
implemented.

b. POST-IMPPLEMENTATION AND SOFTWARE MAINTENANCE

Post implementation the client uses the system gives their reviews to alight
about the product and based on the reviews the required changes are made if there is
any change required otherwise the project works smoothly. Later on changes are made
according to client requirements if they want some new implementation in their
system. The documentation is made so that in future it can be helpful for the new
engineers to understand the system and work accordingly. This whole documentation
is done Alight’s project database and the name of the database is Lotus Notes.

22
9. PROJECT LEGACY

The UPoint tool is made for the use of participants of the plan. It does not have
any admin panel. In spite of that the existing TBA system is available that is usually
known as GUI. Which is used to by the employer to make changes in the participant’s
accounts. Although all the facilities are not available in UPoint but for some
requirements they need to call the benefit center, which is admin for UPoint. If the
UPoint might not work due to any reason the, benefit center is available all working
days for support and this works and an alternative for UPoint.

a. CURRENT STATUS OF THE PROJECT

The new system has been implemented for a number of clients and working as
expected giving a good result of success over past few years. Alight is implementing
new features in UPoint to increase user experience and every changes that are being
made is giving good result. In future we are hoping for more good results and success
reports.
b. REMAINING AREAS OF CONCERN

The company is developing the new system for user convenient. In future there
will be a mobile app for this existing system. User will be able to manage and view their
account and plans while the go.
c. TECHNICAL AND MANEGERIAL LESSON LEARNT

In alight while working on different projects of different clients I have learnt

that industries need only client’s satisfaction. If the client is satisfied. Industry is
satisfied. Being a MNC, the company has clients from many countries. I have worked
on the clients of USA. And it was a good experience with them. Punctuality is must if
you are working in a live environment. Other’s tasks are affected if your task is getting
delayed due to any reason. Technical lesson learnt that, the core knowledge requirement
is must if you are working on any project. I have used SDLC and SQL knowledge in
my internship duration. Being a tester it was my responsibility, that there should not be
any defect in the system. Otherwise there is no use of testing.

23
 10. SYSTEM SNAPSHOTS

a. TOOLS

i. WORKBENCH

Fig. 1

24
ii. WORKBENCH TOOLS PAGE

Fig. 2

25
iii. SQL UTILITY TOOL

Fig. 3

26
iv. PERSON DATA MANAGER

Fig. 4

27
v. TEST PLANS IN ECHO TOOL

Fig. 5

28
vi. CONVERSATION

Fig. 6

29
vii. SQL EDITOR

Fig. 7

30
viii. ADVANCE TABLE EDITOR

Fig. 8

31
ix. HRO MAESTRO

Fig. 9

32
x. GRAPHICAL USER INTERFACE (GUI)

Fig. 10

33
xi. BLUEZONE

Fig. 11

34
xii. TEST PLAN

Fig. 12

35
 b. UPOINT

i. LOG IN PAGE

Fig. 13

36
ii. HOME PAGE

Fig. 14

37
iii. SAVINGS AND RETIREMENTS PAGE

Fig. 15

38
11. BIBLIOGRAPHY

The project report has been made from Alight’s project database and the tasks
assigned to me during training period. All the details are confidential to company’s
policies and there is no any web URL for external user to access the repository. The
source of this document is Alight’s Project Database “LOTUS NOTES”.

39