See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/371501704

A PROJECT PROPOSAL ON "Internship Management and Portal System"

Submitted By: Aashish Katila [PAS076BCT001] Ashish Acharya [PAS076BCT007]
Nitesh Devkota [PAS076BCT019] Saurab Bhatt...

Conference Paper · June 2023

CITATIONS READS
0 1,072

1 author:

Saurab Bhattarai
Tribhuvan University
5 PUBLICATIONS 0 CITATIONS

SEE PROFILE

All content following this page was uploaded by Saurab Bhattarai on 12 June 2023.

The user has requested enhancement of the downloaded file.

 PASHCHIMANCHAL CAMPUS
Institute of Engineering, Tribhuvan University
Lamachaur, Pokhara

A PROJECT PROPOSAL ON

“Internship Management and Portal System”

Submitted By:

Aashish Katila [PAS076BCT001]

Ashish Acharya [PAS076BCT007]

Nitesh Devkota [PAS076BCT019]

Saurab Bhattarai [PAS076BCT037]

Submitted To:

Department of Electronics and Computer Engineering

1
 12 Poush, 2078

TABLE OF CONTENTS

Abstract 4

CHAPTER 1: INTRODUCTION 5
1.1 Background 5
1.2 Problem Statement 5
1.3 Goals of the Project 6
1.4 Scope of the Project 6
1.5 Modules 6
1.6 Feasibility Analysis 7
1.6.1 Economic Feasibility 7
1.6.2 Technical Feasibility 8
1.6.3 Operational Feasibility 8
1.7 System Requirement 9
1.8 Hardware Requirements 9
1.9 Software Requirements 10

CHAPTER 2: LITERATURE REVIEW 11

CHAPTER 3: METHODOLOGY 12
3.1 System Development Life Cycle 12
3.2 Requirements 13
3.2.1 Functional Requirements 13
3.2.2 Non Functional Requirements 14
3.2.3 Design 15
3.2.3.1 Use Case Diagram 16
3.2.3.2 ER Diagram 17
3.3 Implementation 17
3.4 Verification and testing 18
3.5 Deployment and maintenance 18

CHAPTER 4: EPILOGUE 21
4.1 Work Schedule 19

REFERENCES 20

2
 LIST OF FIGURES

Figure 3.2.3.1 Use Case Diagram 18

Figure 3.2.3.1 ER Diagram 19

LIST OF TABLES

Table 1.6.1 Expense Table 8

Table 1.8 Minimum System Requirements 9
Table 3.2.1 Functional Requirements 13
Table 3.2.2 Non Functional Requirements 14

3
Abstract

Internships are an essential part of many students' educational and professional development,
providing them with valuable hands-on experience and exposure to the working world.To address
these challenges, we propose the development of an intern management system that streamlines and
automates the intern management process. This system will allow organizations to easily recruit,
onboard, and manage their interns. It will also provide a platform for communication and
collaboration between interns and their supervisors, helping to facilitate a positive and productive
internship experience.

The intern management system will be web-based, user-friendly, and customizable to meet the
specific needs of different organizations. It will also integrate with existing HR systems and be
scalable to accommodate the needs of organizations of all sizes.

We believe that this intern management system has the potential to greatly improve the efficiency and
effectiveness of intern management, ultimately benefiting both interns and organizations. We look
forward to working with you to bring this innovative solution to fruition

4
 CHAPTER 1: INTRODUCTION

1.1 Background

“meroIntern” is supposed to be a singular system which interconnects a company’s vacancies

with the internship seeker people.The whole system is designed on a few key pillars.The first one
being friendly, the system is supposed to be so simple that a layman with a few hours of training
on the system and workflow can use this.It is supposed to be efficient both in terms of how it
organizes the company and how much resource is needed to deploy and use it. Most of all the
system is intended to make the internship experience a lot better.

“meroInternship” is the first of its kind as it imagines a nationwide problem for the new job
seekers and solve the problem of companies to find the readily available candidate for the work.

1.2 Problem Statement

Nepal is in a weird place in terms of advancement of job facilities, where the competition is
heavily growing and advancing. Although there are many quality people with significant skills,
indeed they had to go abroad for their career due to lack of employment opportunities. We still
use the old age technique called “paper pen” technique for the job seekers which is not so
efficient in time and cost. Although technology has penetrated this area, this is not so influential
due to lack of proper understanding and recognition.

● Lack of a integrated system

Companies use computer’s but it is mostly for their office related works. Systems are not
designed in integrated fashion.

5
 ● Use of old operating procedures in a modern world

Modern high technologies are not used, it is only in theory. Majority of companies use
old “paper and pen” technique during hiring.

1.3 Goals of the Project

● Creating a simple cost effective and efficient platform designed around how best Nepali
Companies can hire good candidates.
● Creating a connected system which can be deployed at every part of the hiring.
● Creating a stable, secure and robust application with no downtime and high security.

1.4 Scope of the Project

1. The user can login to our websites and can be verified by sending their citizenship and
apply for the internship published by the companies through our webapp.
2. The companies can login too, but they have to send the company registration form in
order to get verified as legitimate company.
3. The user gets the customized vacancy opening page according to their skills.
4. In order to apply for the job, the user needs to upload their CVs, their training certificates
(if any), Cover letter, and links of their social media and github (if any)

1.5 Modules

The entire project mainly consists of 6 modules, which are

1. User(internship seeker) Module

○ Login
○ Create and edit profile
○ Apply for the vacancy.
○ Upload
■ CV
■ Cover letter
■ Certificates
■ Project links related to the vacancy

2. Company Module

6
 ○ Register as Company
○ Create a vacancy
○ Look at internship seeker Information
3. Admin Module
○ Verify company and users
○ Reset Passwords
○ Delete old users/company

1.6 Feasibility Analysis

The objective of feasibility study is not to solve the problem but to acquire a sense of its scope.
During the study, the problem definition is crystallized and aspects of the problem to be included
in the system are determined. Consequently, costs and benefits are estimated with greater
accuracy at this stage. The result of the Feasibility study is a formal proposal.This is simply a
report-a formal document detailing the nature and scope of the Proposed solution. Finally,
Feasibility Study is carried out to select the best system that meets the performance
requirements. A feasibility study is carried out to select the best system that meets the
performance requirements.Feasibility is the determination of whether or not a project is worth
doing. The process followed in making this determination is called a Feasibility study.

1.6.1 Economic Feasibility

Economic analysis is the most frequently used method for evaluating the effectiveness of an
Internship System .Most commonly known as cost/benefit analysis, the procedure is to determine
the benefits and savings that are expected from a system and compare them with costs involved.

Benefits from The System are:

● It will greatly improve the internship seekers experience.

● It will help the companies at 100% efficiency as most work will be done through a
computerized system.
● Internship seekers CV’s and skills uploaded will help the company to find the best
candidate.
● It streamlines the way one interacts with the company and makes it hassle free.
● Greatly reduces the advertisement cost and precious time.

7
The costs are negligible as most of the needed infrastructure already exists. Much of the work is
to integrate the existing systems and make it a cohesive experience. In terms of exact cost the
table is given below.

Table 1.6.1

Activities Cost

Domain Registration Rs 1,000/-

Server Cost Rs 1500/- per month

Maintenance Cost Rs 100000 /year

Miscellanous Rs 5000

1.6.2 Technical Feasibility

Technical feasibility centers on the existing computer system (Hardware and software etc.) and
to what extent it can support the proposed system. In case of this system, the required
infrastructure i.e. hardware, software application and technical know-how already exists .Thus
the project is then technically feasible.This is concerned with specifying equipment and software
that will successfully satisfy the user requirements.

We can use existing computers ( some little amount needs to be brought ) and since the users use
some sort of software now it won't be easy to implement ( we can just use the web browser ).

As there are people who might not know how to use the computer system, the design is such that
the user can use the system easily

1.6.3 Operational Feasibility

Since most of the system is supposed to be used by companies and internship seekers it should
be easy to implement. It provides a lot of information but all that information can also be used in
the traditional use.

Major functions like applying for the job and receiving the mail can be done using phone and
computer respectively. Since operations are flexible to all users, it is operationally feasible.

8
1.7 System Requirement

To be used efficiently, all computer software needs certain hardware components or the other
software resources to be present on a computer. These prerequisites are known as system
requirements and are often used as a guideline as opposed to an absolute rule. Most software
defines two sets of system requirements: minimum and recommended. With increasing demand
for higher processing power and resources in newer versions of software, system requirements
tend to increase over time. Industry analysts suggest that this trend plays a bigger part in driving
upgrades to existing computer systems than technological advancements.

1.8 Hardware Requirements

The most common set of requirements defined by any operating system or software application
is the physical computer resources, also known as hardware. A hardware requirements list is
often accompanied by a hardware compatibility list (HCL). An HCL lists tested, compatibility
and sometimes incompatible hardware devices for a particular operating system or application.
The intended system is not heavy and will work on most commercial devices available in the
market.

The minimum hardware requirements are as follows. Anything above should provide a very
good experience.

Table 1.8

CPU 800 MHz Intel Pentium III or 800 MHz AMD Athlon or 1.2GHz Intel Celeron or
1.2GHz AMD Duron processor

RAM 1 GB of RAM

GPU 32 MB video card with DirectX 9.0 compatible drivers ("GeForce" or better)

DX DirectX 9.0

9
1.9 Software Requirements

Software Requirements deal with defining software resource requirements and prerequisites that
need to be installed on a computer to provide optimal functioning of an application. These
requirements or prerequisites are generally not included in the software installation package and
need to be installed separately before the software is installed. A user doesn’t need any
specialized software to run the system. The server hosting the server will need specialized
software such as Laravel, React and MySQL. The server will be a linux server with the latest
version of Red Hat Enterprise Linux.

10
 CHAPTER 2: LITERATURE REVIEW

There are various online platforms available for the internship seekers. One of the most popular
systems is “LinkedIn, merojob, freelancer.com” by different companies which is currently
deployed nationally and internationally.

The general procedure followed by these platforms are:

1. Users are logged in and can create a profile.

2. Users can search for the suitable internship vacancies according to their skills and choice.

3. Users can upload all the credentials and apply for the vacancies.

4. User receives the mail from the company side, if they are shortlisted.
5. Users can interact directly with the company and set up the meeting.

Since this hiring technology is new to the context of Nepal. So, there is no any such
significant competitor.

11
 CHAPTER 3: METHODOLOGY

3.1 System Development Life Cycle

Since the project is one which requires a lot of planning and the product will require a high level
of security and has to be robust we will use the Scrum to develop the project. This is ideal
because frequent analysis and development is needed according to the feedbacks.

The Scrum methodology— is a framework for effective collaborations among teams working on
complex products. Scrum is a type of agile technology that consists of meetings, roles, and tools
to help teams working on complex projects collaborate and better structure and manage their
workload.

Scrum is an agile development methodology used in the development of Software based on an

iterative and incremental processes. Scrum is adaptable, fast, flexible and effective agile
framework that is designed to deliver value to the customer throughout the development of the
project. The primary objective of Scrum is to satisfy the customer’s need through an environment
of transparency in communication, collective responsibility and continuous progress. The
development starts from a general idea of ​what needs to be built, elaborating a list of
characteristics ordered by priority (product backlog) that the owner of the product wants to
obtain.

12
3.2 Requirements

The Scrum methodology is an adaptable, fast, flexible and effective agile framework. In order to
find the requirements for the project we first will visit various companies to know how they hire
the candidates. We will also note down the things that need to be changed and look at the
systems from an outside perspective. The software requirements are set up such that it is quite
robust i.e it is made a lot more detailed and dependable then what is required.

3.2.1 Functional Requirements

Table 3.2.1.1 Functional Requirements

Identifier Priority Weight Requirements

REQ-1 10 System should have a secure login.

REQ-2 10 System should adequate protections against leakage of

critical data.

REQ-3 6 System should allow password resets.

REQ-4 9 System should clearly separate between user roles and

manage accordingly.

REQ-5 8 System should allow registration of new users and

companies.

REQ-6 7 System should allow companies to view their request to

their vacancies

REQ-7 8 System should verify users and companies.

REQ-8 8 System should allow users to apply vacancies safely

13
REQ-9 8 System should allow companies to view the profile of the
users.

REQ-10 3 Users can get the verification message after they apply
for the job vacancies.

3.2.2 Non Functional Requirements

Table 3.2.2.1 Non Functional Requirements

Identifier Priority Weight Requirements

REQ-16 8 As a system, size and generality of the data must be

defined

REQ-17 10 As a system, all the user data must be encrypted

REQ-18 7 As a system, application/portal must be supported in

different browsers of both web and mobile platforms.

REQ-19 4 As a system, data of the entire system must be archived

periodically

REQ-20 6 As a system, backups of the data must be taken

periodically

REQ-21 7 As a system, appropriate business continuity policies and

disaster recovery strategy must be implemented

14
 REQ-22 3 As a system, system maintenance should be done
regularly in order to keep systems up to date

REQ-23 8 As a system, user requests/issues should be supported and

addressed

REQ-24 8 A system, deployment strategy should be implemented

along with roll back strategy in case of deployment failure

REQ-25 10 As a system, data across all the nodes in the system must
be synchronized

REQ-26 3 As a system, logging and monitoring of the system and

application must be in place

REQ-27 8 User manual and Architecture Diagram along with proper

Documentation of the system must be provided

3.2.3 Design

After thorough investigation and reviewing the current system we will start the design of our
system. Design phase will focus on a technical solution to the problems set out by the product
requirements, including scenarios, layouts, and data models. First, a higher-level or logical
design will be created that describes the purpose and scope of the project, the general traffic flow
of each component, and the integration points. Once this is complete, it will be transformed into
a physical design using specific hardware and software technologies.

15
3.2.3.1 Use Case Diagram

16
3.2.3.2 ER Diagram

3.3 Implementation

Once the design is complete, technical implementation starts. This will include turning our
design into a project which can be used and deployed. We will implement the project with
Laravel, in the back-end, React as the front-end with APIs joining the two. A mobile app may
also be developed as per requirements.

17
3.4 Verification and testing

Before a product can be released to customers, testing needs to be done to ensure the product has
no errors and all of the requirements have been completed, ensuring a good user experience with
the software. The testing team will turn to the design documents, personas, and user case
scenarios supplied by the product manager to create their test cases.

Since this project contains critical components verification and validation will be an important
part of the process. There will be extensive checks and penetration tests to ensure that the
website is up to the mark.

3.5 Deployment and maintenance

Once the software has been deployed in the market or released to customers, the maintenance
phase begins. As defects are found and change requests come in from users, a team will be
assigned to take care of updates and release new versions of the software.

18
 CHAPTER 4: EPILOGUE

4.1 Work Schedule

The development of this project is divided into four main parts:

1. Analysis and Design: The relationship between various elements, the structure of the website,
the platform for hosting and design of website using WireFrame will be done in the 1st two week
of the project.

2. Development: This part is further divided into two parts: frontend and backend. The frontend
development will be done from (3rd - 5th) week whereas the backend development will be done
from (6th – 8th) week. All the development will be completed in this phase.

3. Testing: Alpha testing will be performed in the 9th week. All unit and integration testing will
be accomplished this week.

4. Debugging: All the errors and bugs will be fixed in the last 10th week. For fixing the bugs,
platforms like Snyk, Retire etc. will be used.

So, there will be altogether 10 weeks to complete this project hopefully.And in the 8th week, the
website will be live and according to the feedback obtained, some modifications can be done
following the above process iteratively in the interval of 2-4 weeks.

19
View publication stats

REFERENCES
1. [https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model]
2. [https://www.digite.com/agile/scrum-methodology/]
3. [https://www.linkedin.com]
4. [https://www.freelancer.com]
5. [https://www.merojob.com]

20