INDUSTRY INTERNSHIP

SUMMARY REPORT

<<<INTERNSHALA>>>

BACHELOR OF TECHNOLOGY in COMPUTER SCIENCE AND

ENGINEERING

Submitted by

Suraj Mishra (17SCSE101288)

SCHOOL OF COMPUTING SCIENCE AND ENGINEERING

GREATER NOIDA, UTTAR PRADESH
Winter 2020 – 2021
BONAFIDE CERTIFICATE
 CERTIFICATE

I hereby certify that the work which is being presented in the Internship project report entitled
“<<Internshala Web Development>>“in partial fulfillment for the requirements for the award of the degree
of Bachelor of Technology in the School of Computing Science and Engineering of Galgotias University ,
Greater Noida, is an authentic record of my own work carried out in the industry.
To the best of my knowledge, the matter embodied in the project report has not been submitted to
any other University/Institute for the award of any Degree.

Suraj Mishra (17SCSE101288)

This is to certify that the above statement made by the candidate is correct and true to the best of
my knowledge.

Signature of Internship Coordinator Signature of Dean (SCSE)

Dr.N.Partheeban Dr. MUNISH SABHARWAL
Professor & IIIC Professor & Dean
School of Computing Science & Engineering School of Computing Science & Engineering
Galgotias University, Greater Noida Galgotias University.
 TABLE OF CONTENTS

CHAPTER TITLE PAGE NO

Abstract
List of Figures & List of Tables
List of Abbreviations
1 Introduction

1.1 Objective of the project

1.2 Problem statement and research objectives
1.3 Description of Domain
1.4 A brief introduction about an organization.
2 Technical Description 3 System Design

3.1 General Architecture

3.2 Design Phase
3.2.1 Data flow diagram
3.2.2 UML Diagrams
3.3 Methodology
4 System Implementation 5
Results and Discussions

6 Conclusion and Future Work

7 Appendices-

7.1 Source Code

7.2 Learning Experiences
7.3 SWOT Analysis
8 References
 ABSTRACT

<<Internship project of Web Development>>

Internshala web development is an independent software testing and learning platform driven
by industry experts and thought leaders in software testing and test automation domain. We
work with some of the smartest software-driven businesses around the world including
software product start-ups as well as Fortune 500 companies. As a focused partner globally
with in-depth expertise in testing solutions we provide functional, Test Automation, Script
less Test Automation, Performance Testing and Mobile application testing services; serving
multiple industries.Apisys understands this gap and bridges it with its best in class testing
and test automation consulting services. Apisys Pleverages its extensive expertise in designing
and deploying test automation solutions with a measurable value. We focus on optimizing
investment on testing by deploying industry’s most reliable technology solutions for test
automation like unit, functional, GUI automation, performance, security.

Programmers and opportunities:

The Institute combines pioneering research with top class education. An innovative curriculum
allows the student flexibility in selecting courses and projects. Students, even at the
undergraduate level, get to participate in on-going research and technology development - an
opportunity unprecedented in India. As a result, a vibrant undergraduate programmer co-
exists with a strong postgraduate programmer.

Methodology:

This project is to provide classifieds information. The website will provide different
kinds of facilities to the user like rentals; travels. The user should register to utilize the site.
Each user will be given UserId and password. Using that Id and password user can enter in to
the site and can put the ads.Those who want to view the information they can without
registration. This project is implemented using jsp as the front-end and MySQL as back-end.
Key parts of the report:
In existed system, users have to go that particular car and user should reserve it. Here, time consuming
is more and there is no guarantee that car will come after waiting for long time.
We will not able know the fair details of the distance of our journey

Benfits to the company / institution through your report:

The Institute combines pioneering research with top class education. An innovative curriculum
allows the student flexibility in selecting courses and projects. Students, even at the
undergraduate level, get to participate in on-going research and technology development - an
opportunity unprecedented in India.
 1. INTRODUCTION

Software process automation is a technology that may be viewed as a two-edged sword. On

The one hand it can be viewed as a productivity and quality enhancer, while on the other
hand,
It can be viewed as a mechanism to control, routinize, and de-skill work. These views both
Have elements of truth, but with appropriate design and adoption considerations, we believe
That it is possible to enhance the positive elements while reducing the negative ones.
This report looks at the issues that have arisen for the early adopters of process automation.
These people are the innovators, the ones who have been through the ―school of hard
Knocks,‖ taken the brunt of an immature technology, and suffered from the fact that there are
Few experienced people to guide them. Some of the projects we saw succeeded, some failed,
But few found the going easy. This technology is not for the faint of heart—at least not yet.
However, we hope, through this report, to document experiences and lessons learned. We
Hope that we have extracted practical insights to provide insights to the developers of process
Automation tools and guidance to those who wish to automate their processes.

These general objectives have been met through a series of activities that include in-depth
interviews followed by a questionnaire survey and a workshop. The specific objectives of
these activities are as follows:
• The interviews are aimed at gathering practitioner experiences in a relatively unstructured
Way, to identify what individuals believe are the important issues in the adoption of software
process automation, and to establish a basis for the more structured questionnaire survey.
Some of the interviewees were contacted about a year after the initial interviews.
• The questionnaire survey assesses a wider cross-section of those involved with process
automation and includes individuals outside the software community. Because the
questionnaire respondents are following a standard format, the data in this phase of the study
will be analysed in a more quantitative fashion.
• Finally, the workshop was aimed at identifying success strategies for the introduction of
Software automation. The workshop brought together a widely diverse group of individuals
withexperience in research and development, adoption, management and end use of process
automation, and to raise awareness of critical issues across these communities.
As described by Christie [Christie 96], the specific objectives of the study are to
• Identify the technical, social, and organizational inhibitors to the adoption of
processautomation:
– Assess the prevalence and scope of software process automation.
 – Categorize the technologies and practices that are currently being used.
– Identify effective and ineffective technologies and practices.
– Develop guidelines for process automation implementers.
• Support vendors and researchers in developing products more in tune with end-userneeds:
– Develop guidelines for researchers and vendors to improve producteffectiveness.
– Foster effective communications between researchers, vendors, developers and end users.

Recruitment life cycle diagram:

1.1 MODULES:

1. Login page
2. Registration page
3. Background verification form
4. Induction form
5. Employee form
 2. ANALYSIS

2.1 Requirement Analysis

The main objectives for undertaking this project are:

➢ To understand the internal Recruitment process in organization.

➢ To identify areas where there can be scope for improvement.
➢ To give suitable recommendation to streamline the hiring process.
➢ To develop practical knowledge with theoretical aspects.
➢ To know about the importance of recruitment and selection.
➢ To find out better process of recruitment.
➢ To know about the role of recruiter.

Need for recruitment:

It makes possible to choose the right person in the right time at the right place. It also makes it
possible to acquire the number and type of people necessary to ensure the continued operation
of the organization. Planned needs: - such needs arise from changes in the organization
policies.

Anticipated needs: - It refers to those movements in personnel which an organization can

predict by studying trends in internal or external need. Unexpected needs: - Such need arises

due to illness, death and resignation.

Recruitment follows HR planning and goes hand in hand with selection process by which
organizations evaluate the suitability of candidates. With successful recruiting to create a
sizeable pool of candidates, even the most accurate selection system is of little use. Recruiting
begins when a vacancy occurs and the recruiter receives authorization to fill it.

The next step is careful examination of skills, abilities and experience needed to perform the
job successfully. Other steps follow:
• Creating an applicant pool using internal or external methods.
• Evaluate candidate via selection
• Convince the candidate
• And finally make an offer
Selection process is good but it should also be modified according to the requirements and
should job profile so that main objective of selecting the candidate could be achieved. Further
from this survey I hope the organization will be benefited and with the help of the suggestions
given the organization can improve its functioning and the overall Recruitment and Selection
Process in the organization and its performance will increase.

2.2 The Interviews

This report is based upon interviews with individuals who are knowledgeable about and
experiencedwith process automation. We performed a qualitative analysis of these interviews
to arrive at the findings reported here. The material in this section closely follows that
presented in an earlier report [Christie 96].
Three independent organizations were involved in performing the interviews reported here:
The SEI, Nolan Norton and Company (a division of KPMG Peat Marwick), and Cap
GeminiSogeti(located in Grenoble, France).

2.2.1 The Interviewees

An extensive list of candidates was identified early on, including end-user organizations,
commercialand in-house developers, and researchers. Our original goal was to interview
mostly end users of process automation. However, that was not to be. Because of the
immaturity of the technology, we interacted with relatively few experienced end users of the
technology.
Most of our interviews were with people who were involved in developing and implementing
process-centered environments (PCEs).

These individuals came from a wide variety of organizations including

• A vendor of a major process-oriented configuration management (CM) product
• FourDOD sites implementing process-centered environments (PCEs)
• Two U.S. government contractors who were developing process tools and implementing
PCEs
• Two French government contractors who were implementing PCEs
• A French bank that is operating with a PCE
• A university group with strong ties to industry

2.3 How the Interviews Were Conducted

A total of 14 interviews were conducted with 12 projects.1in the large majority of these
interviewsessions, two interviewers were present. The number of interviewees in each
interview ranged from one to eight. All interviews were taped to ensure that the comments
were recorded accurately. The interviews took approximately 36 hours with an average length
of 2.4 hours per interview. All in all, the interviews yielded 150 pages of transcripts.
In one organization, two different projects were interviewed. With two other projects,
multiple interviews wereconducted.

A standard script supported each interview. This script provided a consistent framework and
ensured that we would have comparable information from each of the interviews. While the
questions were used to support the interviews and to ensure coverage, they were not followed
mechanically; areas of interest were often probed in depth. Christie provides further details of
the interview format [Christie 96].

2.4 Interview Findings

The interviewees represented one or more automation efforts that, loosely speaking, can be
seen as pilot projects. These projects ranged in size from fewer than 10 to more than 60
people.
For purposes of discussion, the numbers cited include the personnel for whom the automation
was intended, as well as the developers of the automation if they are part of the same
organization. Typical project size was toward the low end.

While we made no attempt to measure formally the process maturity level of the
organizations/projects interviewed, some had previously undergone formal process
assessments using the SEI Capability Maturity Model (CMM). These projectsranged in
maturity from level 1 (ad hoc/chaotic) to level 5 (optimizing). However, most can
becharacterized as relatively immature (at or below level 2). Other projects had not been
assessedformally, but many characterized themselves as having a poorly defined set of
softwaredevelopment processes. Two projects were attempting software development
activitiesfor the first time.

Of the twelve projects interviewed (seven currently active, four inactive, one experimental),
only two were far enough along for the automation to be considered institutionalized. In one
case, the automation was associated with a company that developed and distributed a
configurationmanagement product. This product has significant process capability that is used
to support further development of the product. The other organization that effectively adopted
PCE technology did so to support software problem tracking.

Four points may be made about the interviews and the findings derived from them. First,
because of the immaturity of the technology, we interviewed few people who could be
considered experienced end users of the technology. The great majority of interviewees were
either developersof process-centered environments, developers of the process tools from
which PCEs can be built, or managers of development projects. Second, the findings not only
surfaced problems but identified potential solutions to these problems. We hope that this
information will be useful to organizations intending to build and use PCEs. Third,
interviewees’ experiences were not always consistent, and these inconsistencies may at times
be reflected in the report.
Fourth, as might be expected, we found that many of the adoption issues we identified
have much in common with adoption issues associated with other technology areas. The
findings fall into three major categories
• drivers and inhibitors
• contributors to success
• technology issues
In the following discussions, we make heavy use of quotes (indicated in italics) from the
interviews.
A major reason for this is that interviewees were surprisingly frank in giving us their views
about process automation and how their organizations were dealing with it.

3. SYSTEM REQUIREMENTS SPECIFICATIONS

3.1 System configurations

The software requirement specification can produce at the culmination of the analysis task.
The function and performance allocated to software as part of system engineering are
refined by established a complete information description, a detailed functional description,
a representation of system behavior, and indication of performance and design constrain,
appropriate validate criteria, and other information pertinent to requirements. 3.2 Software
requirements:

Operating System: Windows

Coding Language: HTML, CSS, PHP, JavaScript, and Bootstrap.

Text Editor : Sublime Text3.

Database : My SQL.

Package : XAMPP.

3.3 Hardware Requirements:

Processor : Intel core i3

Memory : 8GB RAM

Hard Disk : 1TB

4. TECHNOLOGY

4.1 PHP

PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source
general-purpose scripting language that is especially suited for web development and can be
embedded into HTML.PHP is server side scripting language designed for web development
but also used as a general purpose programming language.

PHP code may be embedded into HTML code, or it can be used in combination with various
web template systems, web content management systems and web frameworks. PHP code is
usually processed by a PHP interpreter implemented as a module in the web server or as a
common gateway interface (CGI) executable. The web server combines the results of the
interpreted and executed PHP code, which may be any type of data, including images, with
the generated web page. PHP code may also be executed with a common-line interface (CLI)
and can be used to implement standalone graphical applications.
Instead of lots of commands to output HTML (as seen in C or Perl), PHP pages contain
HTML with embedded code that does "something" (in this case, output "Hi, I'm a PHP
script!"). The PHP code is enclosed in special start and end processing instructions <?
php and ?> that allow you to jump into and out of "PHP mode."

What distinguishes PHP from something like client-side JavaScript is that the code is
executed on the server, generating HTML which is then sent to the client. The client would
receive the results of running that script, but would not know what the underlying code was.
You can even configure your web server to process all your HTML files with PHP, and then
there's really no way that users can tell what you have up your sleeve.

The best things in using PHP are that it is extremely simple for a newcomer, but offers many
advanced features for a professional programmer. Don't be afraid reading the long list of
PHP's features. You can jump in, in a short time, and start writing simple scripts in a few
hours.
4.2 HTML

HTML is the standard mark-up language for creating Web pages.

HTML stands for Hyper Text Mark-up Language

HTML describes the structure of Web pages using mark-up

HTML elements are the building blocks of HTML pages

HTML elements are represented by tags

HTML tags label pieces of content such as "heading", "paragraph", "table", and so on
 5. CODING

Frontend

<! DOCTYPE>

<html>

<title>Induction</title>

<meta charset="UTF-8">

<meta name="viewport" content="width=device-width, initial-scale=1">

<link rel="stylesheet" href="https://www.w3schools.com/w3css/4/w3.css">

<link rel="stylesheet" href="https://www.w3schools.com/lib/w3-theme-blue-grey.css">

<link rel='stylesheet' href='https://fonts.googleapis.com/css?family=Open+Sans'>

<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-

awesome/4.7.0/css/font-awesome.min.css">

<style>
html,body,h1,h2,h3,h4,h5 {font-family: "Open Sans", sans-serif}

</style>

<body class="w3-theme-l5">

<!--Navbar -->

<div class="w3-top">

<div class="w3-bar w3-theme-d2 w3-left-align w3-large">

<a class="w3-bar-item w3-button w3-hide-medium w3-hide-large w3-right w3-padding-large

w3-hover-white w3-large w3-theme-d2" href="javascript:void(0);" onclick="openNav()"><i
class="fafa-bars"></i></a>
<a href="#" class="w3-bar-item w3-button w3-padding-large w3-theme-d4"><i class="fafa-
home w3-margin-right"></i>Logo</a>
<a href="#" class="w3-bar-item w3-button w3-hide-small w3-padding-large w3-hover-white"
title="News"><i class="fafa-globe"></i></a>

<a href="#" class="w3-bar-item w3-button w3-hide-small w3-padding-large w3-hover-white"

title="Account Settings"><i class="fafa-user"></i></a>

<a href="#" class="w3-bar-item w3-button w3-hide-small w3-padding-large w3-hover-white"

title="Messages"><i class="fafa-envelope"></i></a> <div class="w3-dropdown-hover w3-

hide-small">

<button class="w3-button w3-padding-large" title="Notifications"><i class="fafa-

bell"></i><span class="w3-badge w3-right w3-small w3-green">3</span></button> <div

class="w3-dropdown-content w3-card-4 w3-bar-block" style="width:300px">

<a href="#" class="w3-bar-item w3-button">One new friend request</a>

<a href="#" class="w3-bar-item w3-button">Ram posted on your wall</a>

<a href="#" class="w3-bar-item w3-button">Ritesh likes your post</a>

</div>

</div>

<a href="#" class="w3-bar-item w3-button w3-hide-small w3-right w3-padding-large w3-

hover-white" title="My Account"><imgsrc="/w3images/avatar2.png" class="w3-circle"
style="height:25px;width:25px" alt="pic"></a>

</div>

</div>

<!--Navbar on small screens -->

<div id="navDemo" class="w3-bar-block w3-theme-d2 w3-hide w3-hide-large w3-hide-

medium w3-large">

<a href="#" class="w3-bar-item w3-button w3-padding-large">Link 1</a>

<a href="#" class="w3-bar-item w3-button w3-padding-large">Link 2</a>

<a href="#" class="w3-bar-item w3-button w3-padding-large">Link 3</a>

<a href="#" class="w3-bar-item w3-button w3-padding-large">My Profile</a>

</div>

<!-- Page Container -->

<div class="w3-container w3-content" style="max-width:1400px;margin-top:80px">

<!-- The Grid -->

<div class="w3-row">

<!-- Left Column -->

<div class="w3-col m3">

<!-- Profile -->

<div class="w3-card-2 w3-round w3-white">

<div class="w3-container">

<h4 class="w3-center">My Profile</h4>

<p class="w3-center"><imgsrc="/w3images/avatar3.png" class="w3-circle"

style="height:106px;width:106px" alt="pic"><center><form action="upload.php"
method="post" >

<input type="submit" value="Upload Image" name="submit">

</form></form>

</center>

</p>

<hr>

<p><i class="fafa-pencil fa-fw w3-margin-right w3-text-theme"></i> Designer, UI</p>

<p><i class="fafa-home fa-fw w3-margin-right w3-text-theme"></i>Gunupur, INDIA</p>

<p><i class="fafa-birthday-cake fa-fw w3-margin-right w3-text-theme"></i> Dec 18,

1997</p></div></div><br>
<!-- Accordion -->

<!-- Alert Box -->

<div class="w3-container w3-display-container w3-round w3-theme-l4 w3-border w3-theme-

border w3-margin-bottom w3-hide-small">

<span onclick="this.parentElement.style.display='none'" class="w3-button w3-theme-l3 w3-

display-topright">

<i class="fafa-remove"></i>

</span>

<p><strong>Hey!</strong></p>

<p>Positions that are available with our clients which suites your profile!...</p>

</div>

<!-- End Left Column --></div>

<!-- Middle Column -->

<div class="w3-col m7">

<div class="w3-row-padding">

<div class="w3-col m12">

<div class="w3-card-2 w3-round w3-white">

<div class="w3-container w3-padding">

<h6 class="w3-opacity">How do you feel?</h6>

<p contenteditable="true" class="w3-border w3-padding">Status: Feeling Blue</p>

<button type="button" class="w3-button w3-theme"><i class="fafa- pencil"></i>

Post</button>
</div>

</div></div></div>

<div class="w3-container w3-card-2 w3-white w3-round w3-margin"><br>

<center><h1>Login Form</h1>

<form></center>

<table align="center">

<tr>

<td colspan="2" align="center"></td>

</tr>

<tr>

<td>id</td>

<td><input type="text" name="t1"></td>

</tr>

<tr>

<td>Pass</td>

<td><input type="text" name="t2"></td>

</tr>

</table>

</form>

<div class="w3-row-padding" style="margin:0 -16px">

</div>

<center><button type="button" class="w3-button w3-theme-d2 w3-margin-

bottom">Submit</button>
</div></center>

<div class="w3-row-padding" style="margin:0 -16px">

</div>
<!-- End Middle Column -->

</div>

<!-- Right Column -->

<div class="w3-col m2">

<div class="w3-card-2 w3-round w3-white w3-center">

<div class="w3-container">

<p>Upcoming Events:</p>

<imgsrc="/w3images/forest.jpg" alt="pic" style="width:100%;">

<p><strong>Recruitment</strong></p>

<p>Friday 15:00</p>

<p><button class="w3-button w3-block w3-theme-l4">Info</button></p>

</div></div>

<!-- End Right Column --></div>

<!-- End Grid --></div>

<!-- End Page Container --></div><br>

<!-- Footer -->

<footer class="w3-container w3-theme-d3 w3-padding-16"></footer>

<script>

// Accordion functionmyFunction(id)

{ var x =

document.getElementById(id); if

(x.className.indexOf("w3-show")

== -1) {
x.className += " w3-show";

x.previousElementSibling.className += " w3-theme-d1"; }

else {

x.className = x.className.replace("w3-show", "");

x.previousElementSibling.className =

x.previousElementSibling.className.replace(" w3-theme-d1", ""); }

}
// Used to toggle the menu on smaller screens when clicking on the menu button

functionopenNav() { var x = document.getElementById("navDemo"); if

(x.className.indexOf("w3-show") == -1) {

x.className += " w3-show"; }

else {

x.className = x.className.replace(" w3-show", "");

}}

</script>

</body>

</html>
6. SCREENSHOTS
 7. CONCLUSION

Once the on-boarding and training phase wraps up, the new staff member should be ready to
engage in a rewarding long-lasting career. The full cycle recruiting process can indeed be a
gruelling experience for all parties involved. But, will the addition of a new, reliable
employee for the firm, it is also a much needed and appreciated part of nurturing a successful
business.

Even for owners of small enterprises, for peace of mind in hiring the best candidate for a job,
following the steps of the recruitment life cycle is well worth the time and effort and is a
proven method of reducing turnovers within a company, saving both time and money in the
long run.