Nida Mirza - (180630107030) - Ly-Ce - 1 - Internship Report

HORIZONTAL DIGITAL TRAINING PORTAL
A PROJECT REPORT
Submitted By
NIDA MIRZA
180630107030
In partial fulfillment for the award of degree of
BACHELOR OF ENGINEERING
in
Computer Engineering
Madhuben and Bhanubhai Patel Institute of Technology, Anand
Gujarat Technological University, Ahmedabad

May 2022
CERTIFICATE
This is to certify that the project report submitted along with the project entitled Horizontal
Digital Training Portal has been carried out by Nida Mirza under my guidance in partial
fulfilment for the degree of Bachelor of Engineering in Computer Engineering, 8th
Semester of Gujarat Technological University, Ahmadabad during the academic year 2021-
22.
Prof. Sunit Parmar Prof. Nirav Raja

Internal Guide Head of the Department
DECLARATION
I hereby declare that the Internship / Project report submitted along with the Internship /
Project entitled Horizontal Digital Training Portal submitted in partial fulfilment for the
degree of Bachelor of Engineering in Computer Engineering to Gujarat Technological
University, Ahmedabad, is a Bonafede record of original project work carried out by me at
Horizontal Digital under the supervision of Sr. Smriti Khare and that no part of this report
has been directly copied from any students’ reports or taken from any other source, without
providing due reference.
Name of the Student Sign of Student

Nida Mirza
ACKNOWLEDGMENT
I hereby, would like to have the privilege to show our gratitude to all the persons, helped
me in whatever way for the successful completion of this internship without hindrance. I
am grateful to all our mentors who inspired me by setting an example of them for the kind
purpose of motivating me to reach my targeted objective. Without their knowledge and
wisdom along with experience and specialization in their specific field, I would not have
been able to think of doing or completing this work. All the persons who have contributed
directly or indirectly with their kind support and humble approach are highly appreciative
and I would always remain indebted to them in all the ways. I am especially thankful of
Prof. Sunit Parmar and Prof. Nirav Raja, who is our internal guide and HOD
respectively, for their kind support and motivation. I extend my heartfelt thanks to Sr.
Smriti Khare, Senior Quality Assurence Analyst for his co-operation in our project work.
Gujarat Technological University i MBIT

ABSTRACT
I carried out my internship at Horizontal Digital, India at Vadodara branch. Internship is

opportunity to relate what has been covered in class and what is applicable in the field in
an operational environment. The purpose of the program is to fulfill the core equipment for
the award of bachelor’s degree in Computer Engineering to get a practical aspect of
theoretical work studied at the university and to understand the operations in the IT industry
and to enable student gain experience in different tasks.
During Internship period I have worked on company’s internal project Horizontal Digital
Training Portal as Associate Quality Assurance Analyst along with other departments like
Backend department and Frontend department and Project Manager.
Horizontal Digital Training Portal is a web based responsive portal which will have a
flexibility to register the team members and go through the trainings hosted on the site.
Objective is to provide a training platform to the Horizontal Digital team members for team
and self-upgrade.
In conclusion, this was an opportunity to develop and enhance the skills and competencies
in my career field which I actually achieved.
Gujarat Technological University ii MBIT

List of Figures
Fig 1.1 Global Offices of Horizontal Digital…….….………………………………1

Fig 1.2 Sitecore……………..………….….…….…………………………………..3
Fig 1.3 Sitecore Platinum partner…….……….…….………………………………4
Fig 1.4 Salesforce……….…...…………….…….…………………………………..4
Fig 1.5 Acquia………….………………….…….…………………………………..4
Fig 1.6 Coveo…...………….. …………….…….…………………………………..5
Fig 1.7 Customer Data Management…………….………………………………….6
Fig 1.8 Digital Experience Management…..…….………………………………….7
Fig 1.9 Infrastructure, Integration & Governance.…………………………………8
Fig 1.10 Analytics & AI………..………….…….………………………………....9
Fig 1.11 Marketing Automation…….……………………………………………..10
Fig 1.12 Managed Services.…….…………………..……………………………...11
Fig 1.13 Sales, Services & CRM….………………………………………………. 12
Fig 1.14 Commerce…….…………………………………………………………. 12
Fig 1.15 Client Partnerships of Horizontal Digital…… ……………………. ……13
Fig 1.16 VP Structure…………………….…….………………………………….14
Fig 2.1 Layout of operations for development …….……………………………....16
Fig 3.1 Internship Scheduling …….………………………………………....…….17
Fig 4.1 System Analysis …….…………………………………………………….18
Fig 4.2 Scrum Ceremonies.…………………….………………………………….22
Fig 5.2 Agile Methodology…….………………………………………………….24
Fig 5.3 Agile-Scrum Methodology…….………………………………………..,,.25
Fig 5.4 Use case diagram …….……………………………………………………26
Fig 5.5 Activity diagram …….…………………………………………………… 27
Fig 5.6 Sign up …….…………………………………………………………….…28
Fig 5.7 Login….………………………………………………………………….…29
Fig 5.8 My Profile …….…………………………………………………………....30
Fig 5.9 Edit Profile…….…………………………………………………………....31
Fig 5.10 Change Password……………….…….……………………………….…..32
Fig 5.11 Forgot Password……………………….……………………………….….33
Fig 5.12 Reset Password …….……………………………………………….…….33
Gujarat Technological University iii MBIT

Fig 5.14 Style Guide……………………...…….…………………………….……..35
Fig 6.3 Home Page…….……………………………………………….……………32
Fig 6.4 Training Landing Page…….…………………………………………….......34
Fig 6.5 Category Landing Page…….………………………………………...….......46
Fig 6.6 Training Details Page…….………………………………..…………….......48
Fig 6.7 Certification Landing Page………….….………………………………........40
Fig 6.8 Certification Listing Page………….….………………………………..........42
Fig 6.9 Certification Details Page………….….………………………………..........44
Fig 7.1 Types of Software Testing in Software Engineering………….….................50
Fig 7.2 Test Deliverables.………….….……………………………….....................53
Fig 7.3 Develop Test Strategy ………….….…..……………....................................54
Fig 7.4 Commonly Used Testing Types ………….….…..…………….....................55
Fig 7.5 Suspension test criteria………….……..……………………….....................57
Fig 7.6 Test cases order………….….……………………………….........................58
Fig 7.7 Test Execution step 1………….….…...……………………….....................59
Fig 7.8 Test Execution step 2………….….……………………………....................59
Fig 7.9 Test Execution step 3………….….……………………………....................60
Fig 7.10 Test Execution step 4………….….……………………………..................60
Fig 7.11 Test Execution step 5……...….………………………………....................61
Fig 7.12 Test Execution step 6……...….………………………………....................61
Fig 7.13 Test Execution step 7………….….………………..…………....................62
Fig 7.14 Raising Bug step 1…………….….………………..…………....................62
Fig 7.15 Raising Bug step 2………….….………………..…………........................63
Fig 7.16 A newly created bug.………….….………………..…………....................63
Gujarat Technological University iv MBIT

List of Tables
Table 7.1 Types of Software Testing….……………………………………………….49

Table 8.1 Dates of continuous Evaluation……………….…………………………….64
Gujarat Technological University v MBIT

Table of Contents
Acknowledgement .......................................................................................................i
Abstract......................................................................................................................ii
List of Figures ...........................................................................................................iii
List of Tables ............................................................................................................. v
Table of Contents ...................................................................................................... vi
Chapter 1 Overview of the Company ...................................................................... 1
1.1 History.............................................................................................................. 1
1.1.1 Horizontal Talent ....................................................................................... 2
1.1.2 Horizontal Digital ....................................................................................... 3
1.2 Different product/scope of work ....................................................................... 5
1.2.1 Customer Data Management ................................................................... 5
1.2.2 Digital Experience Management .............................................................. 6
1.2.3 Infrastructure, Integration & Governance ................................................ 6
1.2.4 Analytics & AI ......................................................................................... 7
1.2.5 Marketing Automation ............................................................................. 7
1.2.6 Managed Services .................................................................................... 8
1.2.7 Sales, Services & CRM ............................................................................ 8
1.2.8 Commerce ................................................................................................ 9
1.3 Organization chart........................................................................................... 10
1.3.1 Horizontal Talent ................................................................................... 10
1.3.2 Horizontal Digital .................................................................................. 10
1.4 Capacity of Plant............................................................................................. 11
Chapter 2 Overview of different department .................................................... 12
2.1 Details about the work being carried out in each department ........................... 12
2.2 list of technical specification of major equipment ............................................ 13
2.3 Schematic layout about sequence of operations for development of product ... 14
2.4 Details of each stage ....................................................................................... 15
Chapter 3 Introduction to Internship and Project ............................................. 16
3.1 Internship / Project summary .......................................................................... 16
3.2 Purpose ........................................................................................................... 16
Gujarat Technological University vi MBIT

3.3 Objective ........................................................................................................ 17
3.4 Scope .............................................................................................................. 17
3.5 Tools & Technologies ..................................................................................... 20
3.6 Project planning .............................................................................................. 21
3.6.1 Project development approach and justification ...................................... 21
3.6.2 Project effort and time, cost estimation ................................................... 21
3.6.3 Roles and Responsibility ........................................................................ 21
3.6.4 Group dependencies ............................................................................... 21
3.7 Internship Scheduling ..................................................................................... 22
Chapter 4 System analysis ..................................................................................... 23
4.1 Study of Current System ................................................................................. 23
4.2 Problem and Weaknesses of Current System ................................................... 23
4.3 Requirements of New System ......................................................................... 23
4.4 System Visibility ............................................................................................ 24
4.4.1 The System Contribute to the overall objectives of the organization ..... 24
4.4.2 The system be implemented with current technologies and be
completed within the given effort and time. .......................................... 24
4.5 Proposed System ............................................................................................. 24

4.6 Features of New System.................................................................................. 25
4.7 Processes ........................................................................................................ 25
4.8 Selection of Software, Methodology and Approaches ..................................... 26
4.8.1 List of software there are used to develop the system ............................ 21
4.8.2 Use agile methodology for system development ................................... 27
Chapter 5 System design ....................................................................................... 28
5.1 System design and methodology ..................................................................... 28
5.1.1 Model, View and Controller ..................................................................... 28
5.1.2 System methodology ................................................................................ 28
5.1.2.1 Agile methodology ....................................................................... 29
5.1.2.2 Agile scrum .................................................................................. 29
5.2 Database design/Data structure design/Circuit design/Process
design/Structure design ................................................................................... 30
5.2.1 Use case diagram ................................................................................... 31
Gujarat Technological University vii MBIT

5.3 Input/Output and Interface design ................................................................... 32
5.3.1 Activity diagram .................................................................................... 32
5.3.2 Samples of forms, reports and interface ............................................... 32
Chapter 6 Implementation ..................................................................................... 36
6.1 Module Specification ...................................................................................... 36
6.1.1 Team member Registration..................................................................... 36
6.1.2 Team member Login .............................................................................. 37
6.1.3 Logoff .................................................................................................... 37
6.1.4 Forgot Password..................................................................................... 37
6.1.5 Team member Profile ............................................................................. 37
6.1.6 Home Page ............................................................................................. 37
6.1.7 Training Landing Page ........................................................................... 37
6.1.8 Category Landing Page .......................................................................... 37
6.1.9 Training Details Page ............................................................................. 37
6.1.10 Certificate Landing Page ...................................................................... 38
6.1.11 Certification Listing Page ..................................................................... 38
6.1.12 Certification Details Page ..................................................................... 38
6.2 Outcomes ....................................................................................................... 38
Chapter 7 Testing ................................................................................................ 47
7.1 Test Plan/Strategy .......................................................................................... 47
7.2 Test Result and Analysis ................................................................................. 58
7.2.1 Test cases (Test ID, Test Condition, Expected output, Actual output,
remark)............................................................................................... 58
7.2.2. Test execution ..................................................................................... 62
7.3 Raising A Bug ............................................................................................... 63
Chapter 8 Conclusion and Discussion .............................................................. 64
8.1 Overall Analysis of Internship ........................................................................ 64
8.2 Dates of Continuous Evaluation ..................................................................... 64
8.3 Problem Encountered and Possible Solutions ................................................. 65
8.4 Summary of Internship ................................................................................... 66
8.5 Limitation and Future Enhancement ............................................................... 66
References .......................................................................................................... 67
Gujarat Technological University viii MBIT

Project ID: 19991 Overview of Company
CHAPTER 1: OVERVIEW OF THE COMPANY
Horizontal as an organization is contributing its services in two parts. One being Horizontal
Talent and other is the sister company named Horizontal Digital. Being a global
organization, its offices are spread worldwide
1.1 HISTORY
ONE BUSINESS. TWO SERVICES. INFINITE FLEX.
1. Location and spread of the company: We have offices in 5 different locations in India
i.e., Vadodara, Bangalore, Jaipur, Pune, and Hyderabad.
2. Number of employees: 800+
3. Functions of the company –
Horizontal Digital has 3 lines of business - Sitecore, Salesforce and DevOps. Horizontal
Talent – India Staffing and US Staffing.
Gujarat Technological University 1 MBIT

Fig. 1.1 Global Offices Of Horizontal Digital [“Courtesy of Horizontal Digital”]
1.1.1 Horizontal Talent

The Horizontal Talent team connects forward-thinking talent with companies that
are shaping today’s world. This is possible because of the team of 100+ expert
global recruiters that are helping making this possible.
NOT JUST ANOTHER STAFFING COMPANY
Our Expertise
Information Technology
Business & Strategy
Digital Marketing & Creative

1.1.2 Horizontal Digital

The digital team creates greater possibilities between brands and customers through
connected digital experiences that continually raise the bar.
AN EXPERIENCE-FORWARD DIGITAL CONSULTANCY
PLATFORM AND TECHNOLOGY PARTNER

Sitecore
Fig. 1.2 Sitecore [“Courtesy of www.sitecore.com”]

Sitecore is a customer experience management company that provides web content
management, and multichannel marketing automation software. Sitecore is a leading
digital experience software used by organisations globally to create seamless,
personalised digital experiences. Sitecore is an integrated platform powered by .net
CMS, commerce and digital marketing tools. Sitecore’s key product is the Sitecore
Experience Platform (XP) which combines their powerful content management
system (CMS) Sitecore Experience Manager and Sitecore Experience Database
(xDB).Sitecore is a fully featured, connected customer experience platform. You can
do much more than just manage your online content. With Sitecore you can create,
deliver, and optimise for an end-to-end customer experience that spans acquisition,
nurturing, conversion, retention and advocacy.

Horizontal is an original Sitecore Platinum partner
Fig. 1.3 Sitecore Platinum partner [“Courtesy of www.horizontaldigital.com”]
Salesforce
Fig. 1.4 Salesforce [“Courtesy of www.salesforce.com”]

Salesforce is an cloud-based software company. It provides customer relationship
management software and applications focused on sales, customer service, marketing
automation, analytics, and application development.
Salesforce services allow businesses to use cloud technology to better connect with
partners, customers, and potential customers. Using the Salesforce CRM, companies can
track customer activity, market to customers, and many more services.
A CRM platform helps you go deeper with all your metrics and data; you could also set up
a dashboard that showcases your data visually. In addition to this, you can also have
personalized outreach with automation. Another significant benefit is that a CRM platform

Acquia
Fig. 1.5 Acquia [“Courtesy of www.acquia.com”]

Acquia is a software-as-a-service company to provide enterprise products, services, and
technical support for the open-source web content management platform Drupal.
Drupal is a free and open-source web content management system written in PHP and
distributed under the GNU General Public License. Drupal provides an open-source back-
end framework. Drupal is a free Content Management System (CMS). Acquia is a company
that offers paid Drupal services, and also freely contributes important code to the Drupal
community.
Coveo
Fig. 1.6 Coveo [“Courtesy of www.coveo.com”]

Coveo is a software-as-a-service search engine, powered by artificial intelligence. Coveo
is a multi-faceted platform that uses search, machine learning, and behavioural signals
to increase the relevance of search, content recommendations, and personalized
experiences.
1.2 DIFFERENT PRODUCT / SCOPE OF WORK
1.2.1 Customer Data Management
It helps in building a holistic view for the customers. Truly connected customer experiences
across every channel and touchpoint give you a competitive edge in the marketplace. That’s
why it fuses experience-forward mindset with deep expertise in data and technology
platforms that builds seamless customer journeys for the clients.
The process starts by implementing a rock-solid customer 360 data management strategy.
This informs where and how your customer data is consolidated to drive contextual

personalization on a 1:1 level. Next, our team leverages an enterprise-grade customer data
platform (CDP) to unify your data and connect it to other systems sparking the creation of
personalized customer journeys. Throughout the process, our expertise empowers us to
gather the right data and keep it clean, protected, consistent, and actionable.
Fig. 1.7 Customer Data Management [“Courtesy of www.horizontaldigital.com”]
1.2.2 Digital Experience Management

It helps in specialize in strategizing, creating and executing enterprise experience
management platform (EXM) solutions that elevate customer experiences while driving
business outcomes. But where we truly excel is maximizing the potential of EXM platforms
to create seamless engagements that span devices, consumer/personal segments,
regions/countries/languages and more.
Fig. 1.8 Digital Experience Management [“Courtesy of www.horizontaldigital.com”]
1.2.3 Infrastructure, Integration & Governance

It helps in creating a superior customer experience that requires a powerhouse of technical
foundation. Users expect digital experiences that are safe, always-on and lightning fast.
Downtime, lag time, missing data and bugs can cost businesses dollars and customers. We
specialize in proven enterprise class infrastructure and integration solutions to connect
systems and data in ways that is seamless and secure and blazing fast. We pride ourselves

Fig. 1.9 Infrastructure, Integration & Governance
1.2.4 Analytics & AI
The promise of delivering real-time experiences is no longer science fiction. By harnessing

oceans of customer data, machine learning and AI platforms are answering customer needs
today while also anticipating what they want tomorrow. But data itself is not a solution.
Collecting it is so deceptively simple that many companies often drown themselves in data
points rather than using them to drive actions that prove real value.We partner with clients
to proactively collect data and act on it in real-time all to power in-the-moment interactions
with your customers and optimize future experiences with your organization. In addition,
we leverage best-of-breed machine learning and AI technologies to take these insights
further by accurately predicting customer behaviours and personalizing experiences that
build both long-term relationships and greater possibilities in the process.
Fig. 1.10 Analytics & AI [“Courtesy of www.horizontaldigital.com”]
1.2.5 Marketing Automation
Our marketing automation expertise powers successful communications programs across

email, SMS notifications, social, blogs and other content vehicles. The result gives
personalized messages at scale for unique users, without the need to churn marketing team
hours and intervention to ensure effective outcomes. But we don’t stop there. Through our

connected experience focus, we help organizations use their data from interactions across
their digital platforms to provide an in-depth, 360-degree view of your customers. And with
this intelligence, we activate marketing messages that anticipate customer needs vs simply
reacting to them.
Fig. 1.11 Marketing Automation [“Courtesy of www.horizontaldigital.com”]
1.2.6 Managed Services

Users expect digital experiences that are safe, always-on and lightning fast. Downtime, lag
time, missing data and bugs can cost businesses dollars and customers. We specialize in
proven enterprise class infrastructure and integration solutions to connect systems and data
in ways that is seamless and secure and blazing fast. We pride ourselves on providing safe
hands and a knowledgeable team to guide customers through hosting, connecting, securing,
scaling and governing their experience platform infrastructure.
Fig. 1.12 Managed Services [“Courtesy of www.horizontaldigital.com”]
1.2.7 Sales, Services & CRM
It helps in simply putting and converting new customers and keeping in mind that loyal
customers requires care. It help businesses nurture lasting relationships through intelligence
and interactions that prove value to your prospects, at every opportunity. This connected

approach enables us to capture more actionable data about the prospects from what they
find most useful on your digital properties to the types of messages that resonate most with
them. Personalization and context are weaved into every customer engagement. Therefore
no more customer service dead-ends or constant restarts from the beginning. Instead, it
counts on fluid conversations that resolve customer issues in the moment.
Fig. 1.13 Sales, Services & CRM [“Courtesy of www.horizontaldigital.com”]
1.2.8 Commerce
It’s a purpose-built that deliver on these expectations of the clients. It is done so by

seamlessly fusing sales, service and marketing data across the ecommerce destinations we
build. We know how each of the customers are using the ecommerce platforms. Where
they’re discovering the products. What they’re buying and what they’re leaving for maybe
later. Even what they want next.
Fig. 1.14 Commerce [“Courtesy of www.horizontaldigital.com”]
Till now the organization has successfully partnered with various clients across the globe.
Some of them have been mentioned below.

Fig. 1.15 Client Partnerships Of Horizontal Digital
1.3 ORGANIZATION CHART

Horizontal
Horizontal Talent Horizontal Digital
1.3.1 Horizontal Talent
Horizontal Talent specializes in staffing for information technology, digital marketing &
creative and business & strategy markets. This part of company works on Information
Technology, Business and Strategy. They have their expertise in digital marking and
creativity. Their solutions are contingent, permanent, search, managed Search, offshore
staffing. They have top 2% world staffing companies, 82.6% net promoter score, 1300+
active billing consultant, 100+ active global recruiter.
1.3.2 Horizontal Digital
Our sister company, Horizontal Digital, creates meaningful omnichannel experiences for
clients from strategic planning to creative execution. Our experience hiring top-tier talent
for Horizontal Digital gives us precise insights into the skills it takes to move the needle.
This same specialized knowledge helps us spot the right talent for our clients. This part of

company works on CX Strategy and Design, Marketing Automation, data Analytics and
AI, Commerce. They are expertise in Sales Service and CRM, Digital Experience
Management. Platform and Partners are Sitecore, Salesforce, Acquia, Coveo. Company
has 100+ web implementations, 14+ Sitecore MVPs, 150+ Certified Developers, 300+
Sitecore Cross-Cloud Certified. Horizontal Digital is an experience forward consultancy
that invests in understanding the needs, wants and ambitions of customers through the
data they provide — data that is unlocked across every digital experience and
engagement. We use this data to meet customers in the right moment with precise
strategies, technologies and creative approaches that maximize their value. Founded in
2003, we are a certified Minority Business Enterprise that proudly invests in diversity and
growth of our in-house talent as well as our local communities through charitable and on-
site volunteer efforts. Horizontal Digital is headquartered in Minneapolis, MN. Additional
U.S. offices are in Denver, Dallas and Indianapolis, with a global presence in Dubai;
U.A.E.; Bengaluru, Vadodara and Pune, India; and Kuala Lumpur, Malaysia.
Fig. 1.16 VP Structure
1.4 CAPACITY OF PLANT

The overall capacity of Horizontal as an organization, including all the global offices would
be more than 800. This bunch of people is divided into various departments, each working
exceptionally to deliver the best.

Project ID: 206585 Different Departments of Company
CHAPTER 2: OVERVIEW OF DIFFERENT

DEPARTMENTS
2.1. DETAILS ABOUT THE WORK BEING CARRIED OUT IN EACH

DEPARTMENT
1. UI/UX Department:
After getting the requirements form the client flow starts form this department, this
department handles clients’ requirements very carefully and implements client’s
ideas into design.
2. Front End Department:

A front-end department is responsible for implementing visual elements that users
see and interact with in a web application. They are usually supported by back-end
web developers.
3. Back End Department:

A back-end web developer is responsible for server-side web application logic and
integration of the work front-end web developers do. Back-end developers usually
write web services and APIs used by front-end developers and mobile application
developers. Integration of user-facing elements developed by a front-end developer
with server-side logic Implementation of security and data protection Design and
implementation of data storage solutions building reusable code and libraries for
future use
4. QA Department :
The main goal of the Quality Assurance (QA) department is to help create a
quality product. Their job is not only bug searching and regular product testing,
but to also prevent defects accordingly. They ensure the high quality of the
development process and its results. Testing the product during all phases of the
software development lifecycle (SDLC) Identifying weaknesses and

inconsistencies in the product helping to identify project requirements providing

the team with complete information on product quality
5. HR Department :
An HR department is tasked with maximizing employee productivity and
protecting the company from any issues that may arise within the workforce. HR
responsibilities include compensation and benefits, recruitment, firing, and
keeping up to date with any laws that may affect the company and its employees
managing and using people effectively tying performance appraisal and
compensation to competencies Increasing the innovation, creativity, and flexibility
necessary to enhance competitiveness managing the implementation and
integration of technology through improved staffing, training, and communication
with employees
2.2. LIST OF MAJOR TOOLS AND TECHNOLOGIES USED IN EACH

DEPARTMENT
1. Front End Department :

Technologies: HTML, CSS, SCSS, jQuery, React, NodeJS
Tools: Microsoft Visual Studio Code, Photoshop, Invision
2. Back End Department:

Technologies: Sitecore 10, .NET MVC, Microsoft SQL Server 2019
Tools: Microsoft Visual Studio, SQL Server Management Studio
3. QA Department:
Qmetry, SnagIt, Sitecore, Java Programming, Selenium IDE and
WebDriver
4. HR Department :
GreytHR

2.3. SCHEMATIC LAYOUT ABOUT SEQUENCE OF

OPRATIONS FOR DEVELOPMENT OF END PRODUCT
Fig 2.1 layout of operations for development
Above Chart/Figure Show how the work is carried out in organization and in figure as we
can see the flow the very first step will be the discovery after that planning/strategy phase
and then design and development phase there might me some back-and-forth situation
between design and development because of requirements changes after that deployment
and final stage will be measurement and optimization that will repeat whole cycle if there
is any optimization.
2.4. DETAILS OF EACH STAGE:
a. Discovery:
Discovery is the first phase of the service design and delivery process. Doing user
research during Discovery is critical to understand the problem you need to solve
for your users. When you know their challenges, needs and wants, you gain insights
into what aspects of the problem you will need to prioritise. Discovery usually takes
between four to eight weeks.
b. Strategy:
Planning and testing a project must be directly linked to its strategy. In this phase,
you put the project under the microscope and analyse all the details. It involves
making strategic decisions on who will be assigned what duties in the project,
designing a timetable, and setting timescales, allocating resources, and putting in
place measures that will ensure that forecasts made in the initiation stages are met.
Mapping out the project in well-articulated details gives the project bigger
chances of success.

c. UX and Design:
Project design is an early phase of the project where a project's key features,
structure, criteria for success, and major deliverables are all planned out. The aim
is to develop one or more designs that can be used to achieve the desired project
goals.
d. Development:
Development stage refers to the first phase in the life cycle of a new business.
During the development stage, companies focus on establishing themselves
through activities such as market research, product development, and the
construction of new manufacturing facilities.
e. Deploy and Release:

Release and Deployment aims to plan, schedule, and control the movement of
releases to test and live environments. The primary goal of this process is to ensure.

CHAPTER 3: INTRODUCTION TO INTERNSHIP AND

PROJECT
3.1 INTERNSHIP / PROJECT SUMMARY
I have joined Horizontal as Associate Quality Assurence Engineer and currently
working as an Intern.
Goal of this internship/training is to get grip on fundamental technology for respective
department and understanding how we approach it at here Horizontal.
And for that we have worked on an internal project that is in level of real-time
industry project.
Project Title: Horizontal Digital Training Portal

Continuous learning is the core of self-growth. It is also a return on an investment done
on you by the organization. To provide a shared and guided platform which has the
trainings that can be in textual format, internal or external recordings. Team members can
register themselves and then look for the designated trainings based on the categories
tagged for these individual trainings, once they login. They would also have a provision
to add their feedback, comments, their learnings etc. for these individual trainings. There
would be a Certification section as well which will have official certifications linked to
the trainings. A dashboard would have a provision to publish the achievements and
certifications displayed.
3.2 PURPOSE
Learning and implementing the core technologies for respective departments.
Learning and following standards and best practices while developing Getting Ready
for Live Clients Projects. Learning to work in collaborative way with other
departments. Understanding Agile Methodology and SCRUM framework.
Hands on practice and training of latest technologies.
3.3 Objective
Provide a training platform to the Horizontal Digital team members for team and self-
upgrade

Project ID: 19991 Introduction to Internship
A web based responsive portal which will have a flexibility to register the team
members and go through the trainings hosted on the site
3.4 SCOPE
Team member Registration
For someone who wants to access the training portal will have to register themselves. The
registration process would have the following criteria:
A normal registration page which will ask for the basic information like name, email
address and password as mandatory fields, along with some other information.
Criteria for a STRONG password should be visible to the person registering for the
portal
A sign-up confirmation email will go to the registered user.
Email address would have the @horizontal.com domain.
Existing users should be validated with the email ID and if they try to create a new
registration with the existing email ID, they should be notified on the page with a link
to ‘Forgot Password’
Team member Login

The registered team members will have to login to the portal using the horizontal email
ID using which the registration was done. Once done, they will have an active session in
which they will be able to access the training resources and provide their feedback on the
same.
Logoff
A common feature which would end the current session. The team member will have to
login to the application again, to access the training resources. All resources can be
accessed by logged in users only.
Forgot Password
The registered user can click on the Forgot Password link, which will redirect the user to
the Forgot password screen. The team member will have to provide their horizontal email
ID. Once submitted, the reset password link would go to their registered email address.

Clicking on the link will take the team member to the Reset password screen which will
have password and confirm password fields. On submission, a confirmation page and a
confirmation email would go to the person making the change.
Team member Profile

The registered team member will have to login to the portal and navigate to the profile
section. They will be able to change password and modify basic information. Email ID
cannot be changed by them.
Home Page
The key landing page would mostly have a snapshot of all highlighters. Key
certifications, featured training courses, categories of trainings etc.. Different components
would be placed on the home page to provide links to the next level pages so that the
team members can navigate to them from the home page.
Category Listing Page

All the trainings published on the portal will have a category associated with it. The
category listing page will have a list of all categories that are added in the Sitecore CMS.
Clicking on a category block will open the list of trainings that fall under the selected
category.
Training Listing Page

The list of trainings that fall under the selected category will be displayed on the Training
Listing page. The list will have pagination or lazy loading feature to handle bigger lists.
Links to the other categories will be provided on the page, clicking which, the list will be
updated based on the category selected.
Training Details Page

Clicking on an individual training from the training list or home page, will navigate to the
training details page. Training details page will have information that is authored in
Sitecore. It can have textual information, uploaded video, or external video. There will be
a provision to provide feedback and learnings for each training. The information like

feedback date, name and feedback details will be displayed in the descending order of the
submission date.
Certification guidelines
There would be a provision to go to certification section on the home page. Clicking on
this will navigate to the selected Certification details. This would be an information
sharing; in case someone wants to go for an external certification. Information in this
section is to provide the basic guidance for someone who is new to this certification
course.
Later phases...
Considering the current timelines, we consider the above scope of work as a part of the
first phase. In later phases, we will have more features like Playlist, Favourites, Self-
Evaluation and a lot of other features.
3.5 TOOLS AND TECHNOLOGIES

1. Front-end technologies:
a. Technologies: HTML, CSS, SCSS, jQuery, React, NodeJS
b. Tools: Microsoft Visual Studio Code, Photoshop, Invison
2. Back-end technologies:
a. Technologies: Sitecore 10, .NET MVC, Microsoft SQL Server 2019
b. Tools: Microsoft Visual Studio, SQL Server Management Studio
3. QA Tools:
a. Qmetry, SnagIt, Sitecore, Java Programming, Selenium IDE and
WebDriver
4. Project management tools:

a. Bitbucket, Jira, Confluence, MavenLink
5. HR Tools:
a. GreytHR

3.6 PROJECT PLANNING

3.6.1 Project Development Approach And Justification
We will be following Agile approach to keep a track of the project deliveries. The Sprint
cadence would be of 3 weeks. Sprint 0 will be a training sprint which will give the
mentors sufficient time to provide the basic trainings that can be the pre-requisites of the
project execution. Agile is a project management methodology characterized by building
products using short cycles of work that allow for rapid production and constant revision.
SCRUM ceremonies:
Scrum is a framework for project management that emphasizes teamwork, accountability,
and iterative progress toward a well-defined goal. Backlog Refinement, Sprint Planning
Daily SCRUM meeting, Sprint review, Sprint Retrospective.
3.6.2 Project Effort and Time, Cost Estimation

Project estimation is the process of forecasting the time, cost, and resources needed to
deliver a project. It typically happens during project initiation and/or planning and takes
the project’s scope, deadlines, and potential risks into account.
A project estimate gives you and your stakeholders a general idea of how much time,
effort, and money it’ll take to get the job done. That makes it easier to build a feasible
project budget and plan so you can set your team and organization up for success.
A realistic effort estimate requires you to have a clear understanding of certain elements
of the project:
After getting assigned with any component, developer first reviews the design,
understands the functional requirement, analyse their own capabilities and dependency on
others for development and estimates Time and effort cost in storypoints.
For example,
Header components requirement includes mobile navigation menu so, based on design
and requirement developer estimated 8 storypoints. One storypoint for our project
consists of 4 hours.

3.6.3 Roles and Responsibilities

Role: Associate Quality Assurence Engineer
Responsibilities:
1. Writing Test Plan
2. Writing, Reviewing and Executing Test Cases
3. Reporting Bugs on JIRA
4. Understanding Requirements
5. Attending SCRUM Meetings
6. Cooperating with Developers
3.6.4 Group Dependencies

Dependencies are the relationships between work that determine the order in which the
work items (features, stories, tasks) must be completed by Agile teams.
No project is managed in a vacuum. Within a single project, dependencies occur –
between people, steps, functions, or teams.
Front-End and Back-End Team depends on each other while developing.
Front-End Team requires proper design and functional requirements from
Clients/Project Manager.
FED team creates such web structure that FED-BED integration can be done easily
BED team depends on FED team for HTML structure, CSS, and JavaScript
functionality.
Once development is done, QA team performs testing and raises bugs.
Every team depends on Project Manager for project management and detailed client’s
requirements.
3.7 Internship Scheduling

Scheduling in project management is the listing of activities, deliverables, and milestones
within a project. A schedule also usually includes a planned start and finish date,
duration, and resources assigned to each activity. Effective project scheduling is a critical
component of successful time management.

As we are following Agile methodology for Project development, we have divided whole
internship plan into 7 stages.
Fig 3.1 Internship Schedule
Induction and Department Training:

Internship was started in this phase, it included Induction and introduction to department
and company. Departmental Training needed for working on project was provided in this
phase.
Sprint-0:
Sprint-0 is beginning of the Internship Project. Agile and scrum training, Branching and
merging, Environment setups are taken care of in this sprint. Sprint-0 is only of one week.
Sprint 1-4:
One sprint consist of three weeks. And our Project consists of total Four sprint.
Development and testing part in done in sprints.
Documentation:
Last Phase is dedicated for documenting the Project work and completing the Internship
Project.

Project ID: 19991 System Analysis
CHAPTER 4: SYSTEM ANALYSIS

4.1 Study of Current System
Systems analysis is "the process of studying a procedure or business to identify its goal and
purposes and create systems and procedures that will efficiently achieve them". The basic
goal of system analysis is to develop a clear understanding of the new system’s
requirements.
Fig 4.1 System Analysis [“Courtesy of Horizontal Digital”]
Continuous learning is the core of self-growth. Currently the system provides the online
training for new technologies and the recoding of training for future purpose. Right now
the whole process of the examinations and certifications are going through different
platforms like email, slack(for communication), and confluence-page etc. In current
system, The examiner has to create the form and the form should be filled by Candidates
to give any exam.
4.2 Problem and Weaknesses of Current System

There is not any static organised platform in which candidate can find all the data
related to training, recoding, and certifications.
This is the time-consuming process for finding the resources related to new technology
on different platforms.
In current system the whole process of examination is done manually so that many
people are occupied in this process, and they can’t be able to concentrate in his/her
actual work.

4.3 Requirements of New System

It should be such that all training, certification, and examination related resources are
organized at one platform.
There should be an organized platform where candidate can easily find all training
related resources without wasting his/her important time.
There should be open platform in which any candidate can apply any department
courses and track his/her learning journey.
4.4 System Feasibility

4.4.1 The System Contribute to the overall objectives of the organization
The new system Provide a training platform to the Horizontal Digital team members
for team and self-upgrade and the system is technically feasible it can be access from any
devices.
4.4.2 The system be implemented with current technologies and be completed within
the given effort and time.
The system would be developed using agile methodologies and also developed
with current technologies within scheduled time.
4.5 Proposed System
The system provide a training platform to the organization’s team members for team and
self-upgrade. A web based responsive portal which will have a flexibility to register the
team members and go through the trainings hosted on the site.
This is a central platform for the employees of Organization where they will get the details
about available training. All departments can add their training material to this portal. The
users can view all available trainings on the listing page and the training details page will
contain the information like description, pre-requisites, material (videos, documents, online
links to blogs or any other material), and all the supported information. The user can enrol
into the training and the training owner or admin will be notified regarding the same. The
Users can also view their enrolled training in the profile section. This portal will also
contain the list of certified employees of various departments. There will be certification

details page as well. If the user wants to pursue any certification exam, they can get all the
information like description, preparing material, guidance, etc. on the details page.
4.6 Features of New System

User-friendly: The system provides all the recordings and resources in organised way
so user can easily find these resources.
Timesaving: It is timesaving because all the training, certification and examination
related processes are organized at one platform.
Support: Supported by all the latest devices.
Quality: In the system all the component’s quality are well maintained, and it is user-
interactively.
4.7 Processes
1. Organization’s Employees must register to this portal using organization’s
email ID to gain access
2. Use the same credentials to login to the portal
3. Home page will have abstracts of all pages, trainings and certification guidelines
that are published on the portal
4. Team members can click on the category of their choice. This click will take
them to the list of trainings that fall under that category.
5. Team members can click on the trainings from the list. The training details page
will be opened which will have the details about the selected training
6. The selected training can have textual, internal uploaded video or externally
linked video hosted on the page
7. The readers / team member attending that training would have a provision to
post their learnings, their feedback for that selected training.
8. All feedback along with the name and date of feedback will be listed on the
training details page
9. For a team member who wants to appear for any external certifications, initial
guidance / pre-requisites are very important. Those guidelines will be
documented on the Certification Guidelines section.

4.8 Selection of Software, Methodology and Approaches

4.8.1 List of software there are used to develop the system
Bitbucket
Bitbucket is our Git repository management solution designed for professional
teams. It gives you a central place to manage git repositories, collaborate on your
source code and guide you through the development flow.
It provides awesome features that include:
1. Access control to restrict access to your source code.
2. Workflow control to enforce a project or team workflow.
3. Pull requests with in-line commenting for collaboration on code review.
4. Jira integration for full development traceability.
Jira tools
Jira is a software application used for issue tracking and project management. The
tool, developed by the Australian software company Atlassian, has become widely
used by agile development teams to track bugs, stories, epics, and other tasks.
Confluence
Create, collaborate, and organize all your work in one place. Confluence is a team
workspace where knowledge and collaboration meet. Dynamic pages give your
team a place to create, capture, and collaborate on any project or idea. Spaces help
your team structure, organize, and share work, so every team member has visibility
into institutional knowledge and access to the information they need to do their best
work.
InVision
InVision works to support the entire design process from brainstorming, designing,
testing, collaborating, and delivering. The application includes Studio, Cloud,
Freehand, Craft, and Enterprise. InVision works on both macOS and Windows.
InVision was one of the first applications to offer a collaboration feature, so many
designers were used to working in Adobe Photoshop and then uploading their
project to InVision to build prototypes and workshop the design. Other programs
like Adobe XD and Sketch that can handle the entire process have emerged since,
but some UX and UI Designers still prefer to finish the process with InVision.

4.8.2 Use agile methodology for system development

Agile is a term used to describe software development approaches that employ continual
planning, learning, improvement, team collaboration, evolutionary development, and early
delivery.
Scrum is a framework of rules, roles, events, and artifacts used to implement Agile
projects. It is an iterative approach, consisting of sprints that typically only last one to four
weeks. This approach ensures that your team delivers a version of the product regularly.
Fig 4.2 Scrum Ceremonies [“Courtesy of www.magdamiu.com”]
Scrum in Agile requires particular roles and responsibilities, including the following:
Product owner: The product owner is responsible for representing the customer’s
best interest. This person has the ultimate authority over the final product.
Scrum master: This person is a facilitator, responsible for arranging the daily
meetings, improving team interactions, and maximizing productivity. The project
manager often takes on the role of Scrum master, but they can delegate it to anyone
on the team who is a Scrum expert and strong facilitator.

Project ID: 19991 System Design
CHAPTER 5: SYSTEM DESIGN

5.1 SYSTEM DESIGN & METHODOLOGY
Web application design is an important stage when building a web application. It focuses
on the look and feel of the web application. The process of defining a system’s entire
requirements, such as the interface, modules, and design, is called system design. We can
say that system design ranges from discussing about the system requirements to product
development. A systematic approach is needed to manage the system requirements and
design methodology.
5.1.1 Model-View-Controller (MVC)

In software engineering, this pattern is very popular and it has existed for a long time.
This architecture can be used in desktop, web, or mobile applications. In MVC we
separate the whole application logic into three components.
Models (Data and Logic): It represents and maintains the data of the
application in the database. How the information is stored and how it can be
retrieved.
Views (User Interface): It displays the data using the model to the user such
as an output or a GUI.
Controller (Request Handler): It handles the user request and acts as
an interface between models and views.
Fig 5.1 MVC Architecture [“Courtesy of www.geeksforgeeks.org”]

5.1.2 System Methodology

Successful projects are managed well. To manage a project efficiently, the manager or
development team must choose the software development methodology that will work
best for the project at hand. All methodologies have different strengths and weaknesses
and exist for different reasons.
5.1.2.1 Agile Methodology

Teams use the agile development methodology to minimize risk (such as bugs, cost
overruns, and changing requirements) when adding new functionality. In all agile
methods, teams develop the software in iterations that contain mini-increments of the new
functionality.
Fig 5.2 Agile Methodology [“Courtesy of www.clariontech.com”]

5.1.2.2 Agile Scrum
Agile Scrum Methodology is a sprint-based system for managing software projects,
whose goal is to deliver the highest value to stakeholders. Agile Scrum Methodology, a
specially treated project management system, works on incremental development in
product development. The iterations are divided into manageable time slabs, each of
about four-week Sprints. Every goal-driven Sprint offers vital features that constructively
develop a complete product. In subsequent sprints, add-on features and enhancements
based on customer and team feedback are built into the product.

Fig 5.3 Agile-Scrum Methodology [“Courtesy of www.volkansel.com”]

5.2 DATABASE DESIGN / DATA STRUCTURE DESIGN / CIRCUIT

DESIGN / PROCESS DESIGN / STRUCTURE DESIGN
5.2.1 Use case diagram
Fig 5.4 Use case diagram
5.3 INPUT / OUTPUT AND INTERFACE DESIGN

5.3.1 Activity Diagram
Activity diagram describes the flow of control in a system. It consists of activities and
links. The flow can be sequential, concurrent, or branched. Activities are nothing but the
functions of a system. Numbers of activity diagrams are prepared to capture the entire
flow in a system.

Fig 5.5 Activity diagram
5.3.2 Samples of Forms, Reports, and Interface
Sign up
A signup page enables users to independently register and gain access to site.
Fig 5.6 Sign Up

Login
A login page is a web page or an entry page to a website that requires user identification
and authentication, regularly performed by entering a username and password
combination.
Fig 5.7 Login

My Profile
The My Profile page allows site customers to modify their own profiles
Fig 5.8 My Profile

Edit Profile
The edit Profile page allows site customers to modify their own profiles

Fig 5.9 Edit Profile

Change Password
The change password Page provides your applications' users with a way to change their
passwords.
Fig 5.10 Change Password

Forgot Password
It allows users to reset password who have forgotten their password to unlock, retrieve, or
reset it, usually by sending them an e-mail.
Fig 5.11 Forgot Password

Reset Password
The Password Reset Page provides your applications' users with a way to change their
passwords.
Fig 5.12 Reset Password

Interface Style Guide
The Interface Style Guide requirements are mentioned below.
Fig 5.13 Style guide

Project ID: 19991 Implementation
CHAPTER 6: IMPLEMENTATION
6.1 MODULES SPECIFICATION
6.1.1 Team member Registration
For someone who wants to access the training portal will have to register themselves. The
registration process would have the following criteria:
A normal registration page which will ask for the basic information like name,
emailaddress and password as mandatory fields, along with some other
information.
The registration notification will go to the user just registered with copy to the
administrator list for their reference.
A sign-up confirmation email will go to the registered user.
Criteria for a STRONG password should be visible to the person registering for
the portal
Email address would have the @horizontal.com domain. This domain can
be set as a static suffix rather than asking team member to enter it in the
email ID text field.
Existing users should be validated with the email ID and if they try to create a new
registration with the existing email ID, they should be notified on the page
with a link to ‘Forgot Password’
6.1.2 Team member Login

The registered team members will have to login to the portal using the horizontal email ID
using which the registration was done. Once done, they will have an active session in which
they will be able to access the training resources and provide their feedback on the same.
6.1.3 Logout
A common feature which would end the current session. The team member will have to
login to the application again, to access the training resources. All resources can be
accessed by logged in users only.

Project ID: 19991 Implementation
6.1.4 Forgot Password

The registered user can click on the Forgot Password link, which will redirect the user to
the Forgot password screen. The team member will have to provide their horizontal email
ID. Once submitted, the reset password link would go to their registered email address.
Clicking on the link will take the team member to the Reset password screen which will
have password and confirm password fields. On submission, a confirmation page and a
confirmation email would go to the person making the change.
6.1.5 Team member profile

The registered team member will have to login to the portal and navigate to the profile
section. They will be able to change password and modify basic information. Email ID
cannot be changed by them.
6.1.6 Home Page

The key landing page would mostly have a snapshot of all highlighters. Key certifications,
featured training courses, categories of trainings etc.. Different components would be
placed on the home page to provide links to the next level pages so that the team members
can navigate to them from the home page.
6.1.7 Training Landing Page

category.
6.1.8 Category Landing Page

The list of trainings that fall under the selected category will be displayed on the Category
Landing page. The list will have pagination or lazy loading feature to handle bigger lists.
6.1.9 Training Details Page

Project ID: 19991 Testing
submission date.
6.1.10 Certificate Landing Page

All the certifications published on the portal will have a category associated with it. The
certificate landing page will have a list of all categories that are added in the Sitecore CMS.
Clicking on a category block will open the list of certifications that fall under the selected
category.
6.1.11 Certification Listing Page

The list of certifications that fall under the selected category will be displayed on the
Certification Listing page. The list will have pagination or lazy loading feature to handle
bigger lists.
6.1.12 Certification Details Page

Clicking on an individual certification from the certificate list or home page, will navigate
to the certification details page. Certification details page will have information that is
authored in Sitecore. It can have textual information, uploaded video, or external video.
There is a recently certified component which shows the list of certified employees under
the specific training.
6.2 OUTCOMES
Home Page
Starting page of website after the login page. It includes different components which need
to be placed on the home page to provide links to the next level pages so that the team
members can navigate to them from the home page.
List of components:

Header: Common component which includes navigation list for authenticated

user.
Banner: It contains title and description for specific pages.
Content Block: It includes the content which gives the overview of the portal.
Tile Cards: List of cards refers to the internal pages like training and
certifications.
Featured Category: List of training categories which refers to the specific pages
associated with the specific categories.
Featured Training: It displays the list of featured trainings.
Link List: List of tiles for the certifications pages which refers to the specific
certifications.
Footer: Common component which includes a copyright notice, link to a privacy
policy, logo, contact information, social media links. It contains information that
improves a website's overall usability.
Fig. 6.3 Home Page

Training Landing Page
category.
User will be redirected to this page once clicked on Training Menu - First sub menu item
link from the Header. Different components are there to describe the Training Landing
Page.
List of components:
user.
Breadcrumb: It is a secondary navigation scheme that reveals the user’s location
in a website.
Content Block: It includes the content which gives the overview of the training.
Category Listing: It includes the list of categories defined in Sitecore.
Fig 6.4 Training Landing Page

Category Landing Page
The list of trainings that fall under the selected category will be displayed on the Category
Landing page. The list will have pagination or lazy loading feature to handle bigger lists.
List of components:
user.
Breadcrumb: It is a secondary navigation scheme that reveals the user’s location
in a website.
Title: Title Component is used on any page to insert the title between two
components.
Tag Filter Component: It is a global component which is used to apply filters on
any given list of items.
Training Listing: It includes the list of categories defined in Sitecore. Training list
will be displayed based on selected tag.
Fig 6.5 Category Landing Page

Training Details Page
submission date.
User will be redirected to the training detail page on clicking on any of the training list
items on Category Landing Page.
List of components:
Header: Common component which includes navigation list for authenticated user.
Breadcrumb: It is a secondary navigation scheme that reveals the user’s location in a

website.
Title: Title Component is used on any page to insert the title between two components.
Training Detail RTE Field: Details of the training which includes image, bulleted list,
content, and any other content with CSS styling.
Video: Video related to specific training.
Related Training: Recommendation of other trainings related to the current training.
Feedback: Feedback section to take feedback of users.


Fig: 6.6 Training Details Page
Certificate Landing Page
All the certifications published on the portal will have a category associated with it. The
certificate landing page will have a list of all categories that are added in the Sitecore CMS.
Clicking on a category block will open the list of certifications that fall under the selected
category.
List of components:

website.
Content Block: It includes the content which gives the overview of the training.
Category Listing: It includes the list of categories defined in Sitecore.


Fig 6.7 Certificate Landing Page

Certification Listing Page
The list of certifications that fall under the selected category will be displayed on the
Certification Listing page. The list will have pagination or lazy loading feature to handle
bigger lists.
User will be redirected to this page once clicked on Tiles present on Certificate
Landing Page.
List of components:

website.
Certification Listing: It includes the list of categories defined in Sitecore.


Fig 6.8 Certification Listing Page
Certification Details Page

Clicking on an individual certification from the certificate list or home page, will navigate
to the certification details page. Certification details page will have information that is
authored in Sitecore. It can have textual information, uploaded video, or external video.
There is a recently certified component which shows the list of certified employees under
the specific training.
User will be redirected to the Certification detail page on clicking on any of the
certifications on Certification Listing Page.
List of components:

website.
Certification Detail RTE Field:
Video: Video related to specific training.
Related Certifications: Recommendation of other certifications related to the current

certification page.

Recently Certified: It includes the list of certified employees under that certification
category.

Fig 6.9 Certification Details Page

CHAPTER 7: TESTING
1. What is Software Testing?
Software Testing is a method to check whether the actual software product matches
expected requirements and to ensure that software product is Defect free. It involves
execution of software/system components using manual or automated tools to evaluate
one or more properties of interest. The purpose of software testing is to identify errors,
gaps, or missing requirements in contrast to actual requirements.
2. Why Software Testing is Important?
Software Testing is Important because if there are any bugs or errors in the software, it
can be identified early and can be solved before delivery of the software product.
Properly tested software product ensures reliability, security, and high performance which
further results in time saving, cost effectiveness and customer satisfaction.
3. What is the need of Testing?

Testing is important because software bugs could be expensive or even dangerous.
Software bugs can potentially cause monetary and human loss, and history is full of such
examples.
In April 2015, Bloomberg terminal in London crashed due to software glitch affected
more than 300,000 traders on financial markets. It forced the government to postpone
a 3bn pound debt sale. Nissan cars recalled over 1 million cars from the market due to
software failure in the airbag sensory detectors. There has been reported two accidents
due to this software failure. Starbucks was forced to close about 60 percent of stores
in the U.S and Canada due to software failure in its POS system. At one point, the
store served coffee for free as they were unable to process the transaction. Some of
Amazon’s third-party retailers saw their product price is reduced to 1p due to a
software glitch. They were left with heavy losses.Vulnerability in Windows 10. This
bug enables users to escape from security sandboxes through a flaw in the win32k
system.

4. What are the benefits of Software Testing?
Here are the benefits of using software testing:
Cost-Effective: It is one of the important advantages of software testing. Testing any

IT project on time helps you to save your money for the long term. In case if the bugs
caught in the earlier stage of software testing, it costs less to fix.
Security: It is the most vulnerable and sensitive benefit of software testing. People
are looking for trusted products. It helps in removing risks and problems earlier.
Product quality: It is an essential requirement of any software product. Testing

ensures a quality product is delivered to customers.
Customer Satisfaction: The main aim of any product is to give satisfaction to their
customers. UI/UX Testing ensures the best user experience.
5. Types of Software Testing
Typically Testing is classified into three categories.

Functional Testing
Non-Functional Testing or Performance Testing
Maintenance (Regression and Maintenance)
Fig 7.1 Types of Software Testing in Software Engineering

Table 7.1 Types of Software Testing
Testing Category Types of Testing
Unit Testing
Integration Testing
Smoke
UAT (User Acceptance Testing)
Functional Testing Localization
Globalization
Interoperability
So, on
Performance
Endurance
Load
Volume
Non-Functional Testing
Scalability
Usability
So, on
Regression
Maintenance
Maintenance
6. Testing Strategies in Software Engineering
Here are important strategies in software engineering:

Unit Testing: This software testing basic approach is followed by the programmer to test
the unit of the program. It helps developers to know whether the individual unit of the code
is working properly or not.
Integration testing: It focuses on the construction and design of the software. You need to
see that the integrated units are working without errors or not.
System testing: In this method, your software is compiled as a whole and then tested as a
whole. This testing strategy checks the functionality, security, portability, amongst others.

7.1 TEST PLAN / STRATEGY
What is Test Plan
A Test Plan is a detailed document that describes the test strategy, objectives, schedule,
estimation, deliverables, and resources required to perform testing for a software product.
Test Plan helps us determine the effort needed to validate the quality of the application
under test. The test plan serves as a blueprint to conduct software testing activities as a
defined process, which is minutely monitored and controlled by the test manager.
As per ISTQB definition: “Test Plan is A document describing the scope, approach,
resources, and schedule of intended test activities.”
What is the Importance of Test Plan?
Making Test Plan document has multiple benefits like helping people outside the test
team such as developers, business managers, customers to understand the details of
testing. Test Plan guides our thinking. It is like a rule book, which needs to be followed.
Important aspects like test estimation, test scope, Test Strategy are documented in Test
Plan, so it can be reviewed by Management Team and re-used for other projects.
How to write a Test Plan
You already know that making a Test Plan is the most important task of Test
Management Process. Follow the seven steps below to create a test plan as per IEEE 829
Step 1: Analyse the product
Step 2: Design the Test Strategy
Step 3: Define the Test Objectives
Step 4: Define Test Criteria
Step 5: Resource Planning
Step 6: Plan Test Environment
Step 7: Schedule & Estimation
Step 8: Determine Test Deliverables

Fig. 7.2 Test Deliverables [“Courtesy of www.devgenius.io”]
Step 1: Analyse the product
How can you test a product without any information about it?
The answer is impossible. You must learn a product thoroughly before testing it. We
should research clients and the end users to know their needs and expectations from the
application
Who will use the website?
What is it used for?
How will it work?
What is software/ hardware the product uses?
Step 2: Develop Test Strategy

Test Strategy is a critical step in making a Test Plan in Software Testing. A Test Strategy
document is a high-level document, which is usually developed by Test Manager. This
document defines:
The project’s testing objectives and the means to achieve them
Determines testing effort and costs
We should follow steps below
Fig 7.3 Develop Test Strategy
Step 2.1: Define Scope of Testing
Before the start of any test activity, scope of the testing should be known. We must think
hard about it.
The components of the system to be tested (hardware, software, middleware, etc.)

are defined as “in scope“
The components of the system that will not be tested also need to be clearly
defined as being “out of scope.”
Defining the scope of testing project is very important for all stakeholders. A precise
scope helps to give everyone a confidence and accurate information of the testing you are
doing, and all project members will have a clear understanding about what is tested and
what is remaining to be test
Step 2.2 Identify Testing Type
A Testing Type is a standard test procedure that gives an expected test outcome.
Each testing type is formulated to identify a specific type of product bugs. But, all Testing
Types are aimed at achieving one common goal “Early detection of all the defects before
releasing the product to the customer”.

The commonly used testing types are described as following figure
Fig 7.4 Commonly Used Testing Types
Step 2.3 Document Risk & Issues
Risk is future’s uncertain event with a probability of occurrence and a potential for loss.
When the risk happens, it becomes the ‘issue’.
Step 2.4 Create Test Logistics
In Test Logistics, the Test Manager should know who will test and when will the test
occur.
Who will test?

We may not know exact names of the tester who will test, but the type of tester can be
defined.
To select the right member for specified task, you must consider if his skill is qualified
for the task or not, also estimate the project budget. Selecting wrong member for the task
may cause the project to fail or delay.
Person having the following skills is most ideal for performing software testing:
Ability to understand customers point of view
Strong desire for quality
Attention to detail and good cooperation

When will the test occur?

Test activities must be matched with associated development activities.
You will start to test when you have all required items shown in following figure.
Step 3. Define Test Objective
Test Objective is the overall goal and achievement of the test execution. The objective of
the testing is finding as many software defects as possible; ensure that the software under
test is bug free before release. To define the test objectives, you should do the following
steps :-
1. List all the software features (functionality, performance, GUI…) which may need to
test.
2. Define the target or the goal of the test based on above features.
Step 4: Define Test Criteria
Test Criteria is a standard or rule on which a test procedure or test judgment can be based.
There are two types of test criteria as following:-
Suspension Criteria
Specify the critical suspension criteria for a test. If the suspension criteria are met during
testing, the active test cycle will be suspended until the criteria are resolved.
Test Plan Example: If your team members report that there are 40% of test cases failed,
you should suspend testing until the development team fixes all the failed cases.
Fig 7.5 Suspension test criteria [“Courtesy of www.guru99.com”]

Exit Criteria
It specifies the criteria that denote a successful completion of a test phase. The exit
criteria are the targeted results of the test and are necessary before proceeding to the next
phase of development. Some methods of defining exit criteria are by specifying a
targeted run rate and pass rate.
1. Run rate is ratio between number test cases executed/total test cases of test
specification. For example, the test specification has total 120 TCs, but the tester
only executed 100 TCs, So the run rate is 100/120 = 0.83 (83%)
2. Pass rate is ratio between numbers of test cases passed / test cases executed. For
example, in above 100 TCs executed, there’re 80 TCs that passed, so the pass rate
is 80/100 = 0.8 (80%)
This data can be retrieved in Test Metric documents.
Run rate is mandatory to be 100% unless a clear reason is given.
Pass rate is dependent on project scope but achieving high pass rate is a goal.
Step 5: Resource Planning
Resource plan is a detailed summary of all types of resources required to complete project
task. Resource could be human, equipment and materials needed to complete a project.
The resource planning is important factor of the test planning because helps
in determining the number of resources (employee, equipment…) to be used for the
project. Therefore, the Test Manager can make the correct schedule & estimation for the
project.
Step 6: Plan Test Environment
What is the Test Environment?
A testing environment is a setup of software and hardware on which the testing team is
going to execute test cases. The test environment consists of real
business and user environment, as well as physical environments, such as server, front
end running environment.
Step 7: Schedule & Estimation

In the article Test estimation, you already used some techniques to estimate the effort to
complete the project. Now you should include that estimation as well as the schedule to
the Test Planning.
Step 8: Test Deliverables
Test Deliverables is a list of all the documents, tools and other components that has to be
developed and maintained in support of the testing effort. There are different test
deliverables at every phase of the software development lifecycle.
Test deliverables are provided before testing phase.
Test plans document.
Test cases documents
Test Design specifications
Test deliverables are provided during the testing
Test Scripts
Simulators.
Test Data
Test Traceability Matrix
Error logs and execution logs.
Test deliverables are provided after the testing cycles is over.
Test Results/reports
Defect Report
Installation/ Test procedures guidelines
Release notes
7.2 TEST RESULTS AND ANALYSIS
7.2.1 Test Cases:

A test case is a set of actions performed on a system to determine if it satisfies software
requirements and functions correctly. The purpose of a test case is to determine if
different features within a system are performing as expected and to confirm that the
system satisfies all related standards, guidelines, and customer requirements. The process
of writing a test case can also help reveal errors or defects within the system.

Test cases are typically written by members of the quality assurance (QA) team or the
testing team and can be used as step-by-step instructions for each system test. Testing
begins once the development team has finished a system feature or set of features. A
sequence or collection of test cases is called a test suite. A test case document includes
test steps, test data, preconditions and the postconditions that verify requirements.
How to Write Software Test Cases:
Test cases have a few integral parts that should always be present in fields. However,
every test case can be broken down into 8 basic steps.
Step 1: Test Case ID
Test cases should all bear unique IDs to represent them. In most cases, following a
convention for this naming ID helps with organization, clarity, and understanding.
Step 2: Test Description
This description should detail what unit, feature, or function is being tested or what is
being verified.
Step 3: Assumptions and Pre-Conditions
This entails any conditions to be met before test case execution. One example would be
requiring a valid Outlook account for a login.
Step 4: Test Data
This relates to the variables and their values in the test case. In the example of an email
login, it would be the username and password for the account.
Step 5: Steps to be Executed
These should be easily repeatable steps as executed from the end user’s perspective. For
instance, a test case for logging into an email server might include these steps:

Open email server web page.
Enter username.
Enter password.
Click “Enter” or “Login” button
Step 6: Expected Result
This indicates the result expected after the test case step execution. Upon entering the
right login information, the expected result would be a successful login.
Step 7: Actual Result and Post-Conditions
As compared to the expected result, we can determine the status of the test case. In the
case of the email login, the user would either be successfully logged in or not. The post-
condition is what happens as a result of the step execution such as being redirected to the
email inbox.
Step 8: Pass/Fail
Determining the pass/fail status depends on how the expected result and the actual result
compare to each other.
Same result = Pass
Different results = Fail
QMetry Tool for Test case writing
QMetry Test Manager for JIRA Add-on is developed to extend the use of QMetry Test
Manager tool in integration with JIRA. The Add-on empowers the users to manage their
testing projects within JIRA itself and, hence, it enhances the potentiality of JIRA
projects to carry on the entire test cycles smoothly.

In our project, QMetry was used both for writing test cases and executing them.
Fig 7.6 Test cases order

7.2.2 Test Execution
Once we are done writing the test cases, we start test execution.
1. In doing so, first, we need to select “Test Cycle” from the top navigation bar.
Fig 7.7 Test Execution step 1
2. Add a folder under Test Cycle Tab. Name this newly created folder after the
current sprint. In this folder, created another folder and rename this folder after the
component for which you want to perform test execution.

3. In this folder, add the execution cycle for desktop, device, and Sitecore test cases.
4. In these test cycles, fill these fields

5. After filling these fields, go to the “Test Cases” Section on Top Navigation Bar
and Click on Link Test Cases(s) button.
6. Select the test cases that you want to link and click on “Link and close”. These
new test cases should appear in the list of linked test cases.
7. Click on Execute and start Executing Test Cases. Check the actual site and
compare it with designs present on InVision. If you find any bug, report the bug
on Jira.
While executing test cases, we can give these statuses to the test cases:
I. Not Executed: If the test cases are not yet been executed
II. Blocked: If requirements are not mentioned for a particular test case
III. Failed: If the actual outcome is different from the expected outcome
IV. Pass: If the actual outcome is the same as the expected
In the below image we will get clear idea about the execution of the test cases.

8. Once all the Test Cases are passed, the execution will be complete for that
component.
7.3 RAISING A BUG
While performing test execution if a test case gets blocked or gets failed, a bug should be
reported.
Steps for reporting a bug are mentioned below:
1. Go to JIRA dashboard and click on the “Create” button on the top Navigation Bar.
Fig 7.14 Raising Bug step 1

2. A pop-up box should open.
Fig 7.15 Raising Bug step 2
3. Select the Project Title, Issue Type, Enter Bug Summary, Components,
Description for the Bug, Priority, Labels, Environment, Attachments, Linked
Issues, Assignee, Epic Link and Sprint Details. And then Click on Create Button
to create a bug.
Fig 7.16 A newly created bug

CHAPTER 8: Conclusion and Discussion

8.1 Overall Analysis of Internship
We have completed our project work based on using software engineering with Agile
Software development method. Our project started after on first week of January and
completed till last week of April. We had training on pre-requisites for project during first
3 weeks of Internship program. We were also involved in Global & Department meetings
and also lots of various events like Hackathon, Fun activities, Team Bonding activities and
more. Where we got idea about the workflow and culture of the organization, and it also
helped us learning so many new things apart from technical things like communication,
documentation, and presentation skills. There were monthly feedback forms from our
mentors and based on that 1:1 meeting was arranged for proper feedback and improvement
on that.
8.2 Dates of Continuous Evaluation
On 1st April and 28th April, mid-term exams were conducted at our college where the
overall progress of the internship project and presentation demo was conducted. Apart
from this, every Saturday the internal guide reviewed our log books, signed it and gave
their precious suggestions to improve our quality of work.
Table 8.1 Dates of continuous Evaluation
Review 1 1st April, 2022

Review 2 28th April, 2022
8.3 Problem Encountered and Possible Solutions
We had never worked on any live or big project previously, therefore we were unaware about many
of the procedures and standards of working in a global organization. As a result, after getting this
opportunity to work on an amazing project at Horizontal we faced some technical as well as some
non-technical challenges. As a part of technical challenges we faced some coding related issues and
for that luckily we had mentors assigned for each intern and they helped us to make our technical
skills better. Along with that they also cleared our doubts and helped us learn more. Second problem
that we faced was communicating with other team members from different departments. So to

overcome that we had daily scrum/stand-up meetings in which we share our daily work and in this
way we got comfortable with each other and narrowed that communication gap that was a barrier in
our communication with other departments. Lastly the problem was to get mixed up with all the other
employees that were present at office or working at different global centres across the globe. The
possible solution for this was to interact with them. For this, at Horizontal meetings were conducted
online so that everyone can connect and get to know each other better. Along with this fun activities,
technical talks and team-bonding sessions were also conducted on every Friday. Apart from this,
global technical meetings, zoomboriee (online celebration for successfully completing two years of
work from home) and many other events are organised to overcome our cross departmental as well
as global reach of communication.
8.4 Summary of Internship

The internship was carried out at Horizontal Digital, India at the Vadodara branch.
Internship is basically an opportunity to relate what has been covered in class and what is
applicable in the field in an operational environment. The purpose of the program is to fulfil
the core equipment for the award of bachelor’s degree in Computer Engineering to get a
practical aspect of theoretical work studied at the university and to understand the
operations in the IT industry and to enable student gain experience in different tasks.
During Internship period I have worked on company’s internal project Horizontal Digital
Training Portal as a Front-End developer along with other departments like Backend
department and Quality Analyst department and the Project Manager.
Horizontal Digital Training Portal is a web based responsive portal which will have a
flexibility to register the team members and go through the trainings hosted on the site.
Objective is to provide a training platform to the Horizontal Digital team members for team
and self-upgrade. In past four months, I have learnt how to convert theoretical knowledge
into practical experience. Learnt various technologies, sharpened my soft skills and
strengthened my basics. This all has not only boosted me to do better but also increased the
zeal to work more. The work place is well organised which has created a nice environment
around me to focus on my work and the aura here is amazing. Discipline maintained here
is like icing on the cake. Also, the global exposure one can get here is something that cannot
be missed. So, in conclusion, my experience in horizontal till date has been a roller coaster
ride of new learnings, fun, team bonding and growth. Because of Horizontal, I have come
a short yet a long way.

8.5 Limitation and Future Enhancement
Limitations of current system
There is not any static organised platform in which candidate can find all the
data related to training, recoding, and certifications.
This is the time-consuming process for finding the resources related
to new technology on different platforms.
In current system the whole process of examination is done manually so that many
people are occupied in this process, and they can’t be able to concentrate in his/her
actual work.
Future Enhancement
It should be such that all training, certification, and examination related resources
are organized at one platform.
In later phases, application will have more features like Playlist, Favourites, Self-
Evaluation and a lot of other features.
There should be open platform in which any candidate can apply any department
courses and track his/her learning journey.

Project ID: 19991 References
REFERENCES
1. Horizontal Digital: https://www.horizontaldigital.com/
2. Wikipedia: https://en.wikipedia.org/wiki/Main_Page
3. Sitecore: https://www.sitecore.com/
4. JIRA: https://www.atlassian.com/software/jira
5. Confluence: https://www.atlassian.com/software/confluence
6. GreytHR: https://www.greythr.com/
7. Qmetry: https://www.qmetry.com/
8. Selenium Automation: https://www.selenium.dev/

Nida Mirza - (180630107030) - Ly-Ce - 1 - Internship Report

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nida Mirza - (180630107030) - Ly-Ce - 1 - Internship Report

Uploaded by

Copyright:

Available Formats

HORIZONTAL DIGITAL TRAINING PORTAL

In partial fulfillment for the award of degree of

Gujarat Technological University, Ahmedabad

Prof. Sunit Parmar Prof. Nirav Raja

Name of the Student Sign of Student

Gujarat Technological University i MBIT

I carried out my internship at Horizontal Digital, India at Vadodara branch. Internship is

Gujarat Technological University ii MBIT

Fig 1.1 Global Offices of Horizontal Digital…….….………………………………1

Gujarat Technological University iii MBIT

Gujarat Technological University iv MBIT

Table 7.1 Types of Software Testing….……………………………………………….49

Gujarat Technological University v MBIT

Gujarat Technological University vi MBIT

4.4.2 The system be implemented with current technologies and be

completed within the given effort and time. .......................................... 24

4.5 Proposed System ............................................................................................. 24

Gujarat Technological University vii MBIT

Gujarat Technological University viii MBIT

CHAPTER 1: OVERVIEW OF THE COMPANY

organization, its offices are spread worldwide

ONE BUSINESS. TWO SERVICES. INFINITE FLEX.

Gujarat Technological University 1 MBIT

Fig. 1.1 Global Offices Of Horizontal Digital [“Courtesy of Horizontal Digital”]

1.1.1 Horizontal Talent

NOT JUST ANOTHER STAFFING COMPANY

Digital Marketing & Creative

Gujarat Technological University 2 MBIT

1.1.2 Horizontal Digital

AN EXPERIENCE-FORWARD DIGITAL CONSULTANCY

PLATFORM AND TECHNOLOGY PARTNER

Fig. 1.2 Sitecore [“Courtesy of www.sitecore.com”]

Gujarat Technological University 3 MBIT

Horizontal is an original Sitecore Platinum partner

Fig. 1.3 Sitecore Platinum partner [“Courtesy of www.horizontaldigital.com”]

Fig. 1.4 Salesforce [“Courtesy of www.salesforce.com”]

Gujarat Technological University 4 MBIT

Fig. 1.5 Acquia [“Courtesy of www.acquia.com”]

Fig. 1.6 Coveo [“Courtesy of www.coveo.com”]

1.2 DIFFERENT PRODUCT / SCOPE OF WORK

1.2.1 Customer Data Management

Gujarat Technological University 5 MBIT

Fig. 1.7 Customer Data Management [“Courtesy of www.horizontaldigital.com”]

1.2.2 Digital Experience Management

Fig. 1.8 Digital Experience Management [“Courtesy of www.horizontaldigital.com”]

1.2.3 Infrastructure, Integration & Governance

Gujarat Technological University 6 MBIT

Fig. 1.9 Infrastructure, Integration & Governance

1.2.4 Analytics & AI

The promise of delivering real-time experiences is no longer science fiction. By harnessing

Fig. 1.10 Analytics & AI [“Courtesy of www.horizontaldigital.com”]

1.2.5 Marketing Automation

Our marketing automation expertise powers successful communications programs across

Gujarat Technological University 7 MBIT

Fig. 1.11 Marketing Automation [“Courtesy of www.horizontaldigital.com”]

1.2.6 Managed Services

Fig. 1.12 Managed Services [“Courtesy of www.horizontaldigital.com”]

1.2.7 Sales, Services & CRM

Gujarat Technological University 8 MBIT

Fig. 1.13 Sales, Services & CRM [“Courtesy of www.horizontaldigital.com”]

It’s a purpose-built that deliver on these expectations of the clients. It is done so by

Fig. 1.14 Commerce [“Courtesy of www.horizontaldigital.com”]

Gujarat Technological University 9 MBIT