Introduction

The overall research work is based on the management of the recruitment process. Here all the related tasks have been performed in such a way that helps to obtain the candidate management successfully. In addition to that, the development of various activity diagrams of different tasks helps to understand the working functionality of the recruitment process. The recruitment agency can track the candidate details along with their addresses very efficiently. The responsible admin department manages all the tasks related to the recruitment agency.

Aims and objectives

Aims:

The main aim of this project is to construct a recruitment system to recruit candidates.

Objectives:

The primary objective of this project is

• To manage the recruitment process
• To view all the candidate details
• To develop a suitable system that helps in candidate management (THAKOET and Manirochana., 2021)
• To construct a report based on the overall project
• To produce a sequence diagram to understand the overall process

Several functionalities of the recruitment agency

The responsible agency related to recruitment provides several functionalities that help in obtaining the candidate management successfully (Vuorelma., 2018). However, there are several critical aspects of recruitment that are discussed below

• Management of adding candidates
• Construction of report based on the overall recruitment process
• Management of several categories of candidate
• Management of a detailed view of the candidate details (Thongsawang and Meebua, 2019).

A use case diagram for the Home page

 Figure 1: Homepage use case

(Source: Self-developed)

Activity Description about the registration page

Case Name	Registration on the webpage
Scenario	The responsible admin decides to register on the page
Triggering Event	The required user details have been provided to the webpage to complete the registration
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can also access other pages
	Flow of Activities
	Admin	System
	1. Admin desires to register	1. Admin provides details for registration
	2. Required details are provided	2. Important data needs to store in the database
	3. The database shows the confirmation for receiving data successfully	3. Registration has been completed successfully
Exception condition	If the user credentials are not valid.

Table 1: Activity Description of the registration page

 Screen diagram of the Registration page

Figure 2: Screen diagram for a Registration page

(Source: Self-developed)

Activity diagram of the Registration page

Figure 3: Activity diagram for the Registration page

(Source: Self-developed)

Activity Description about the login page 

Case Name	Admin logging in the page
Scenario	The responsible admin desires to log in to the web page
Triggering Event	All the required information has been provided for the logging process
Brief Description	The selected user requires .to produce valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	Valid user credentials are provided by the admin
Post-conditions	Admin can also access other pages
	Flow of Activities
	Admin	System
	1. Admin asks for logging	2. Instructions related to the registration process have been provided to the system
	2. Provides important information	2. All the important details need to be stored in the database.
	3. The database shows the receiving of data successfully	3. The logging process has been completed successfully.
Exception condition	If the credential of the candidate does not match with the existing data.

Table 2: Activity Description of Login page

 Screen diagram of a Login page

Figure 4: Screen diagram for Login page

(Source: Self-developed)

Activity diagram of the Login page

Figure 5: Activity diagram for login page

(Source: Self-developed)

Activity Description about password change page

Case Name	Changing of password
Scenario	The responsible admin desires to change the password
Triggering Event	The task of password change has been performed by the admin
Brief Description	The candidate must produce a valid user id and a new password to change the previous password
Stakeholders	candidate, Admin
Actors	Admin
Pre-conditions	The new password should be provided two times accurately
Post-conditions	Admin can successfully change the old password
	Flow of Activities
	Admin	System
	1. The responsible admin wants to change the previous password	1. Asks the candidate to produce a new password
	2. All the required credentials are provided on the webpage	2. All the credentials need to be stored in the database
	3. The database confirms that new data has been received successfully.	3. The changing of the password has been performed successfully.
Exception condition	If user credentials do not match with the existing data.

Table 3: Activity Description of password change page

Screen diagram for forgetting password page

Figure 6: Screen diagram for forgetting password page

(Source: Self-developed)

Activity diagram for password-changing page

Figure 7: Activity diagram for password-changing page

(Source: Self-developed)

Activity Description about the Log out page

Case Name	Logging out from the webpage
Scenario	The responsible admin desires to log out from the webpage
Triggering Event	The admin press the logout option
Brief Description	Admin selects the option yes or no for logging out and then press the logout button
Stakeholders	Applicants, Admin
Actors	Admin
Pre-conditions	A logout option should be provided
Post-conditions	Two optionsare there for logout. The admin either chooses yes or no for logout
	Flow of Activities
	Admin	System
	1. The task related to logout needs to be performed by the admin	1. The logout request is sent to the system
	2. The required option has been utilized for logout	2. All the required details need to be stored in the database.
	3. The database confirms the successful receiving of data	3. Successful logging out has been performed
Exception condition	If the cancel option is pressed then the log out will not be done.

Table 4: Activity Description of the Log out page

Screen diagram for logout page

Figure 8: Screen diagram for logout page

(Source: Self-developed)

Activity diagram for logout page

Figure 9: Activity diagram for logout page

(Source: Self-developed)

Activity Description of the Dashboard page

Case Name	Enter in the dashboard page
Scenario	The responsible admin decides to enter the dashboard page
Triggering Event	Admin can successfully choose the required options for entering into the dashboard
Brief Description	Several details related to the dashboard are present in the webpage that can be utilized for entering into the dashboard page.
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	Admin needs to select the correct option from the page.
Post-conditions	Admin needs to choose the actual button.
	Flow of Activities
	Admin	System
	1. The responsible admin asks for the dashboard page.	1. Several options like manage dashboard, manage candidate, manage interview schedules, and so on are selected by the selected.
	2. The required button is selected by the admin	2. All the necessary details are stored in the database.
	3. The database confirms the successful receiving of data.	3. Successful management of the dashboard page can be performed using the dashboard options.
Exception condition	If the required button is not selected then the task cannot be done properly.

Table 5: Activity Description of the Dashboard page

Screen diagram for the dashboard page

Figure 10: Screen diagram for the dashboard page

(Source: Self-developed)

Activity diagram for the dashboard page

Figure 11: Activity diagram for the dashboard page

(Source: Self-developed)

 A use case diagram for designing a Dashboard

Figure 12: Use a case diagram to design a Dashboard

(Source: Self-developed)

Description regarding activity for managing candidate in the recruitment process

Case Name	Management of candidate throughout the recruitment process
Scenario	The responsible admin department desires to manage the recruitment process.
Triggering Event	Admin successfully provided all the necessary details on the page.
Brief Description	Valid user credentials need to be provided during the process to manage the recruitment.
Stakeholders	Admin, candidate
Actors	Admin
Pre-condition	The responsible admin must provide valid credentials to execute the task successfully.
Post-condition	All the required information is provided to the system to manage the recruitment process.
	Flow of Activities
	ADMIN	SYSTEM
	Admin desires to add, edit, and view the candidate management process.	Prompts the admin to perform desired tasks successfully.
	All the necessary details related to the candidate management should be filled in.	The necessary details need to be stored in the database of the recruitment agency.
	The database shows the confirmation of the receiving of data	The recruitment management page is shown on the admin side
Exception condition	If the user credentials do not match with the previous data

Table 6: Activity description for managing applicants during recruitment process

Screen diagram to manage candidates

Figure 13: Screen diagram to manage candidates

(Source: Self-developed)

Figure 14: Activity diagram to manage candidates

(Source: Self-developed)

Activity description for controlling recruitment process

Case name	Controlling the recruitment process
Scenario	The responsible admin desires to control the overall recruitment process.
Triggering Event	The admin provides all the necessary details to control the process successfully.
Brief Description	A valid user credential must be provided to control the overall process.
Stakeholders	Admin, candidate
Actors	Admin
Pre-conditions	A valid user credential needs to provide to execute the task.
Post-conditions	A successful page needs to produce to control the recruitment process.
	Flow of Activities
	ADMIN	SYSTEM
	Admin asks for controlling the page using several attributes.	Prompts the admin to perform the task
	All the required options related to the recruitment process must be filled.	All the required details related to the recruitment must be stored in the database.
	The database shows the confirmation page for receiving data.	The controlling of the recruitment process page is shown on the admin page.
Exception condition	If the user credential does not match with the previous data

Table 7: Activity description for controlling the entire recruitment process

Screen diagram to control the recruitment process

Figure 15: Screen diagram to control the recruitment process

(Source: Self-developed)

Activity diagram to control the recruitment process

Figure 16: Activity diagram to control the recruitment process

(Source: Self-developed)

Activity description to manage recruitment category

Case name	Management of various recruitment categories
Scenario	The responsible admin desires to manage several recruitment categories.
Triggering Event	All the necessary details are provided for managing several categories of the recruitment process.
Brief Description	Valid user credentials must be provided to the system to perform the desired tasks.
Stakeholders	candidates, Admin
Actors	Admin
Pre-conditions	All the tasks need to be done properly
Post-conditions	The required page is successfully provided by the admin to execute the task successfully.
	Flow of Activities
	ADMIN	SYSTEM
	Admin desires to design the overall recruitment category by performing several tasks	Prompt the admin for adding several entities to design the webpage successfully.
	The requirements of the newly designed recruitment category should be filled.	All the necessary details related to the recruitment category need to be stored in the database.
	The database schema shows the confirmation message	The management of the recruitment category page must be shown on the admin page.
Exception condition	If the primary user credentials do not match with the previous data.

Table 8: Activity description to manage recruitment category

Screen diagram for controlling recruitment category

Figure 17: Screen diagram for controlling recruitment category

(Source: Self-developed)

Activity diagram for controlling recruitment category

Figure 18: Activity diagram for controlling recruitment category

(Source: Self-developed)

Activity description to view results of the recruitment process

Case name	Viewing results
Scenario	Admin desires to view the result of the overall recruitment process
Triggering Event	All the required details are entered to generate the result of each candidate.
Brief Description	A valid user credential needs to be provided thereafter the viewing of the result page will appear.
Actors	Admin
Pre-conditions	The admin should select the correct option to access the result page successfully.
Post-conditions	All the required options from the page are selected thereafter the save button is pressed to generate the result successfully.
	Flow of Activities
	ADMIN	SYSTEM
	The selection of proper options is performed by the admin to view the result.	Prompt the admin to obtain the result viewing page related to various recruitment categories.
	The requirements for generating a result that needs to be filled.	All the necessary details require to be stored in the database.
	A confirmation message will be obtained from the database	The successful representation of the result will be shown on the admin page.
Exception condition	If the primary credentials do not match with the existing data.

Table 9: Activity description for designing a recruitment result to view

Screen diagram for viewing the result

Figure 19: Screen diagram for viewing the result

(Source: Self-developed)

Activity diagram for viewing the result

Figure 20: Activity diagram for viewing the result

(Source: Self-developed)

 Use Case Diagram to manage new candidate

Figure 21: Use Case Diagram to manage new candidate

(Source: Self-developed)

Description for adding new candidate

Case name	Adding new candidate
Scenario	The responsible admin desires to add new candidates.
Triggering Event	The admin completed the process of adding new candidates.
Brief Description	Valid user credentials must be provided to manage candidates.
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The admin must use proper user credentials.
Post-conditions	A successful page of candidate addition has been received by the admin.
	Flow of Activities
	Admin	System
	1. The admin desires to add a new candidate	1. Instruct the system to manage related tasks.
	2. The database shows the confirmation message.	2. A successful page for adding new candidates appears on the database.
Exception condition	If the user credential does not match with the existing data.

Table 10: Description for New Candidate Addition

Screen Diagram to add new candidate details

Figure 22: Screen Diagram to add new candidate details

(Source: Self-developed)

Activity Diagram to add new candidate details

Figure 23: Activity Diagram to add new candidate details

(Source: Self-developed)

Description for editing candidature

Case name	Editing the details of the candidate
Scenario	The responsible admin desires to edit the details of the candidate.
Triggering Event	At least one candidate detail should be added.
Brief Description	The candidate must provide all the necessary details to edit previous data.
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The recruitment agency must possess crucial details of the candidate.
Post-conditions	The responsible admin receives the editing page.
The flow of the activities	Admin	System
	1. Admin wants to edit new candidate details. The admin desires to edit the candidate details.	1. Instruction provided to the system to edit the candidate details.
	2. Candidate category along with candidate age has been provided by the admin.	2. The editing page has been shown in the database.
Exception condition	If the user credentials do not match with the previous data.

Table 11: Description for editing new candidature

Screen Diagram to edit new candidate details

Figure 24: Screen Diagram to edit new candidate details

(Source: Self-developed)

Activity Diagram to edit new candidate details

Figure 25: Activity Diagram to edit new candidate details

(Source: Self-developed)

Description of viewing all candidate details

Case name	Viewing of all the necessary details of the candidate
Scenario	The responsible admin desires to view the details of the candidate.
Triggering Event	The admin desires to view the necessary details of the candidate.
Brief Description	All the necessary details must be provided by the candidate to view the details.
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	At least one candidate detail must be viewed by the recruitment agency.
Post-conditions	A successful page is received by the admin that helps in viewing the candidate details.
The flow of the activities	Admin	System
	1. The admin desires to view the user details	1. Instruct the responsible agency to view candidate details.
	2. Confirmation of the detailed view of the new candidature will be obtained from the database. The database shows the successful addition of the candidature.	2. The database of the admin shows the viewing candidate page.
Exception condition	If the data provided by the candidate do not match with the existing data.

Table 12: Description for viewing all candidate details

Screen diagram for viewing all candidate details

Figure 26: Screen diagram for viewing all candidate details

(Source: Self-developed)

Activity diagram for viewing all candidate details

Figure 27: Activity diagram for viewing all candidate details

(Source: Self-developed)

Description of shortlisted candidate details

Case name	Short Listing the details of all candidates.
Scenario	The admin department wants to sort all the candidate details.
Triggering Event	Admin must add, edit, and view the overall details of the selected candidate.
Brief Description	The category of the candidate should be selected by the candidate himself in order to viewing the detailed view the entire details of the candidature.
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin department must shortlist the actual category of the candidate details.
Post-conditions	The admin department receives the page of candidate listing successfully.
The flow of the activities	Admin	System
	1. Admin wants to list all the required details of the candidate.	1.      Instruct the responsible department to list the candidate details.
	2. The listing of new candidature must be selected.	2. The details related to the selected candidate should be saved in the database.
	3. Confirmation of the listing of the new candidature will be obtained from the database.	3. The listing of the existing candidate details page shows in the admin database successfully.
Exception condition	If the existing candidate id is not matched with the database.

Table 13: Description for shortlisted candidate details

Screen diagram for short listing all candidate

Figure 28: Screen diagram for short listing all candidate

(Source: Self-developed)

Activity diagram for short listing all candidates

Figure 29: Activity diagram for shortlisting all candidates

(Source: Self-developed)

 Usecase for Interview process

Figure 30: Use case for interview scheduling

(Source: Self-developed)

Description for controlling Interview schedule

Case name	controlling Interview schedule
Scenario	The responsible administrative department requires in order to select a new candidate
Triggering event	The admin has completed the login area in order to add an interview schedule.
Brief Description	A authentic user id and password must be inputed by the user, after finishing  that particular procedure the ‘adding new interview process’ page will open.
Stake holders	Admin, candidate
Actors	Admin
Preconditions	A valid user id and password need to be given by the Admin.
Post conditions	The successful page has been received by the administrative department for the cause of adding a new interview schedule.
	Flow of activities
	Admin	System
	1. Admin seeks a new interview candidate.	1. Instruct the responsible department to find an interview schedule for a candidate.
	2. The number of interviews must be added.	2. All the important details associated with the new interview processes system must be saved in the database.
	3. Confirmation of adding an interview schedule will be generated from the database.	3. The successful addition of a new interview process page has appeared on the admin database.
Exception condition	If the added interview requirement is not matched with the database.

Table 14: Description for controlling interview process

Screen diagram of controlling interview schedule

Figure 31: Screen diagram of controlling interview schedule

(Source: Self-developed)

Activity diagram of controlling interview schedule

Figure 32: Activity diagram of controlling interview schedule

(Source: Self-developed)

Description of editing interview schedule

Case name	Modifying of the previous interview procedure.
Condition	The accountable admin department wants to oversee the current interviewing procedure.
Triggering Event	The administrative staff should include at least one interview schedule.
Brief Description	The reader must supply the category for organizing the interview procedure as well as the schedule.
Stakeholders	Admin, candidate
Actors	Admin
Preconditions	The recruitment company cart must include at least one applicant.
Post conditions	The administrator receives a successful page for editing a new applicant.
	Flow of activities
The flow of the activities	Admin	System
	1. Employers are sought for editing positions.	1. The system has been given instructions to edit candidates.
	2. The price must be chosen as well as the necessary quantity of applicants.	2. The database must be saved with all the necessary information related to the management system for recruitment agencies.
	3. From the database, confirmation of editing current candidates will be generated.	3. The database of the admin shows that the existing candidate page has been successfully edited.
Exception condition	If the database does not match the amended existing candidate ID.

Table 15: Description for editing interview schedule

Screen diagram of an edit interview schedule

Figure 33: Screen diagram of an edit interview schedule

(Source: Self-developed)

Activity diagram of controlling interview schedule

Figure 34: Activity diagram of controlling interview schedule

(Source: Self-developed)

Description of viewing interview schedule

Case name	Viewing the interview’s specifics.
Scenario	The administrative department in charge would want to see all future interview times.
Triggering event	The admin must view the chosen applicants.
Brief Description	The reader must choose the category for the in-depth look of the interview.
Stakeholders	Admin, candidate
Actors	Admin
Preconditions	The interview system should include at least one candidate, and the administrator edited the confirmed candidates.
Post conditions	The admin department should receive the revised page for the new interview procedure.
	Flow of activities
The flow of the activities	Admin	System
	1. The administrator wants to view each candidate.	1. The system should be instructed to display all of the applicants.
	2. It is necessary to choose the interview category’s thorough view.	2. The database must have all the information needed for the interview category.
	3. The database will be used to confirm the detailed perspective of the candidates.	3. The database of the administrator successfully displays a detailed view of the interview web page.
Exception condition	If the tasks associated with the detailed view of the interviews are not matched with the database.

Table 16: Description for viewing all interviews

Screen diagram of viewing interview schedule

Figure 35: Screen diagram of viewing interview schedule

(Source: Self-developed)

Activity diagram of viewing interview schedule

Figure 36: Activity diagram of viewing interview schedule

(Source: Self-developed)

Description of shorting listing all interview candidates

Case name	Listing of all interview candidates
Scenario	The responsible admin department desire to listing all the process and select candidates.
Triggering event	Admin must add, edit, and viewed and the selected interview process.
Brief Description	The listing interview category must be selected by the user for listing the detailed view of the interview process.
Stakeholders	Admin, Candidate
Actors	Admin
Preconditions	The details of the selected category of candidates must be viewed by the admin.
Post conditions	The successful page for a listing of selected candidates are received by the admin.
	Flow of activities
The flow of the activities	Admin	System
	1. Admin seeks for listing all the required interview schedules.	1. Instruction has been provided to the system to list all candidate’s schedules.
	2. The listing of candidates  associated with the interview process category must be selected.	2. The details of the required interviews must be saved in the database.
	3. Confirmation of the listing of the interview schedule will be generated from the database.	3. The successful listing of the existing interview web page is shown on the database of the admin.
Exception condition	If the candidate id is not matched with the database.

Table 17: Description for shortlisting all the interviews

Screen diagram of short listing interview candidates

Figure 37: Screen diagram of short listing interview candidates

(Source: Self-developed)

Activity diagram of shorting interview candidates

Figure 38: Activity diagram of shorting interview candidates

(Source: Self-developed)

Use-case diagram to manage recruitment process

Figure 40: Use case diagram for requirement process

(Source: Self-developed)

Use case description for recruitment process

Case name	Adding of recruitment processes
Scenario	Admin aims to change the recruitment process and generating new recruitment processes
Triggering event	At first the admin do the login in order to change the process of requirement effectively.
Brief Description	The password and username have been given by the admin for adding the changes accurately.
Stakeholders	Admin, applicants
Actors	Admin
Preconditions	The authentication of the user_id and password has been given.
Post conditions	The adding has been successfully done by the admin and viewing the page has been done.
	Flow  activities
The flow	Admin	System
	1. Admin can make asking for adding the process for recruitment.	1. Through the system, all the permission has been properly given.
	2. The quantifiable number of recruitment must be added.	2. The database storing has been successfully done.
	3. All the confirmation has been accessed by the admin.	3. The process has been successfully created.
Exception condition	The change of recruitment has been accurately utilized.

 Table 18: Use case description for recruitment process

Screen diagram for adding new processes

Figure 41: Screen diagram for adding new processes

(Source: Self-developed)

Activity diagram for adding new processes

Figure 42: Activity diagram for adding new processes

(Source: Self-developed)

Description of editing the new procedures

Case name	The editing of the processes has been accurately done.
Scenario	The admin aims to edit the processes
Triggering Event	The login credential has been done for editing the scenario
Brief Description	The authentification of the username, as well as the password, has been perfectly produced
Stakeholders	Admin, Applicants
Actors	Admin
Preconditions	The valid types of the password has given by admin.
Post conditions	The viewing of the page is done where the admin can edit the information and the procedures
	Flow activities
Flow for activity	Admin	System
	1. Sending a request for adding a new process	1. The permission has been provided by system
	2. The editing has been processed by the admin.	2. The editing has been saved in the database.
	3. Conformation has come from the database design.	3. Editing has been successfully invented.
Exception condition	After editing a new record of the processes has been created.

 Table 19: Description of editing the new procedures

Screen diagram for editing processes

Figure 43: Screen diagram for editing processes

(Source: Self-developed)

Activity diagram for editing processes

Figure 44: Activity diagram for editing processes

(Source: Self-developed)

Description for viewing the detailed information of candidates

Case name	View of the new recruitment process
Scenario	Admin view the detailed new procedures of recruitment.
Triggering Event	Admin has successfully processed the login in order to view details
Brief Description	The correct password and id have been given.
Stakeholders	Admin, Applicants
Actors	Admin
Preconditions	Validation has been checked the password and id
Post conditions	The viewing of the successful page has been seen by the admin
	Flow activities
Flow activities	Admin	System
	1. Requesting the viewing of detailed page	1. The instruction has been given to view the pages.
	2. The details has properly checked and viewed	2. The database store all the viewing objects.
	3. The confirmation has been checked	3. The details page has been successfully viewed.
Exception condition	The adding and editing have not been processed here the whole viewing this page.

 Table 20: Description for viewing the detailed information of candidates

Screen diagram for viewing detailed processes

Figure 45: Screen diagram for viewing detailed processes

(Source: Self-developed)

Activity diagram for viewing detailed processes

Figure 45: Activity diagram for viewing detailed processes

(Source: Self-developed)

Use case diagram for the Report page

Figure 46: Usecase diagram for the Report page

(Source: Self-developed)

Activity Description of the report

Case name	Reporting of the interview process as well as interview schedules.
Scenario	Wishes to view interview schedules as well as the process along with candidates.
Triggering Event	The adding of candidates and scheduling interviews has done here.
Brief Description	The interview form has been filled out by the applicants.
Stakeholders	Admin, Applicant
Actors	Admin
Preconditions	The given data must be covered up by admin
Post conditions	All the data has been provided accurately.
	Flow activities
Flow activities	Admin	System
	1. Admin requests for the report of the interview process.	1. Instruction has been sent by system
	2. Interview types and the account have been saved.	2. Saving all information in the database.
	3. Confirmation can be got	3. Successfully done
Exception condition	The checking of the field has been covered up or not

 Table 21: Activity Description of the report

Screen for a report of the new interview process

Figure 47: Screen for a report of the new interview process

(Source: Self-developed)

Activity diagram of interview process

Figure 48: Activity diagram of interview process

(Source: Self-developed)

Use case diagram for enrollment

Figure 51: Use case for enrollment

(Source: Self-developed)

Use case description for enrollment

Case name	Performing the enrollment
Scenario	Admin wishes for performing enrollment for recruitment process
Triggering event	Login has been done for performing
Brief Description	The correct information of password and user id has been given
Stakeholders	Admin, applicants
Actors	Admin
Preconditions	Authentication must be checked
Post conditions	Through providing details the enrollment has been processed
	Flow activities
The flow	Admin	System
	1. Admin can make a request for filling up enrollment form	1. The permission has been provided by the system
	2. The enrollment name and place details have been filled in for enrolling	2. The enrollment data has been stored
	3. Admin confirms	3. The enrollment has been successfully done
Exception condition	The enrollment for the candidates has been successfully produced.

 Table 22: Use case description for enrollment

Screen diagram for enrollment

Figure 52: Screen for enrollment

(Source: Self-developed)

Activity diagram for enrollment

Figure 53: Screen for enrollment

(Source: Self-developed)

Description table for building a resume

Case name	The building of the resume is done.
Scenario	Admin wants to build an effective resume with all information
Triggering Event	Admin does the login by providing credentials
Brief Description	Password along with user_id is provided
Stakeholders	Admin, Applicants
Actors	Admin
Preconditions	Validation has checked for the password with user id
Post conditions	Resume building page has successfully created
	Flow activities
Flow activities	Admin	System
	1. Requesting for building the resume	1. Permission has been provided
	2. The name, qualification age, place, and experiences of candidates has been given	2. The database stores all the information for creating a resume
	3. Admin confirms the details	3. The resume building has been done
Exception condition	Several resumes have been properly built.

 Table 23: Description table for building a resume

Screen diagram for building a resume

Figure 53: Screen for resume building

(Source: Self-developed)

Activity diagram for building a resume

Figure 54: Activity diagram for resume building

(Source: Self-developed)

Activity description of preliminary test

Case name	Conducting preliminary test
Scenario	Amin conducts a preliminary test for the recruitment
Triggering Event	The login credential has been given for conducting the preliminary test.
Brief Description	Correct credentials have been provided.
Stakeholders	Admin, Applicants
Actors	Admin
Preconditions	Authentication for credentials and passwords are checked accurately.
Post conditions	The test is conducted for applicants so that successful recruitment has been done
	Flow activities
Flow activities	Admin	System
	1. Requesting the test page for conducting test	1. The instruction has been given
	2. All the test timing, test duration, test type, and test questions have been set.	2. The database store all the test information
	3. A confirmation has been made by admin	3. The test details have been successfully saved
Exception condition	Conduction of test has done without facing any problems

Table 24: Activity description of preliminary test

Screen diagram for Preliminary test

Figure 55: Screen diagram for Preliminary test

(Source: Self-developed)

Activity diagram for Preliminary test

Figure 56: Activity diagram for Preliminary test

(Source: Self-developed)

ERD for enrollment

Figure 57: ERD for enrollment

(Source: Self-developed)

The use case for conducting preliminary test

Figure 58: Use case diagram for Preliminary test

(Source: Self-developed)

Activity description for conducting meeting

Case name	Conducting meeting with externals
Scenario	Admin conduct a meeting with all qualified internal
Triggering Event	Admin does the login
Brief Description	The accurate password has been given.
Stakeholders	Admin, Applicants
Actors	Admin
Preconditions	Authentication is checked at first for entering in that page
Post conditions	The conduction of meeting has been processed
	Flow activities
Flow activities	Admin	System
	1. The request sent by admin for conducting a meeting with internal	1. The provision of permission has been done by system
	2. The meeting time, date, purpose, topic, and selected candidates have been filled up.	2. The database stores the meeting details
	3. Admin confirms the meeting	3. Meeting successfully conducted
Exception condition	The meeting has been conducted switch the internals who have passed the preliminary test.

 Table 24: Activity description for conducting meeting

Screen diagram for conducting a meeting with the internal team

Figure 59: Screen diagram for conducting a meeting with the internal team

(Source: Self-developed)

Activity diagram for conducting a meeting with the internal team

Figure 60: Activity diagram for conducting a meeting with the internal team

(Source: Self-developed)

ERD for Preliminary test

Figure 62: ERD for Preliminary test

(Source: Self-developed)

A use case diagram for Training

Figure 1: Training use case

(Source: Self-developed)

Description of the Training use case

Case Name	Training use case
Scenario	The responsible admin provides training to those who have not passed the preliminary test
Triggering Event	The required user details have been provided to the webpage to complete the training
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the training evaluation outcome
	Flow of Activities
	Admin	System
	1. Admin desires to log in	1. Admin provides training who are unable to pass the preliminary test
	2. The training evaluation has been done.	2. Those who have achieved the skill proceed to the internal team meeting.
	3. Those who have not achieved skills again send for the training.	3. Successfully log out from the page.
Exception condition	If the user credentials are not valid.

Table 1: Activity Description of the training use case

Activity Description of the Training login page

Case Name	Training login page
Scenario	The responsible admin asks to provide the details of the candidates for training.
Triggering Event	The required user details have been provided to the webpage to start the training
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the training details of the candidates.
	The flow of Activities
	Admin	System
	1. Admin desires to log in	1. Provides the training ID
	2. Admin asks for training type and training duration	2. Provides training type and duration of the candidates
	3. Asks for a password for successful login	3. Successfully log in to the training page.
Exception condition	If the user credentials are not valid.

Table 2: Activity Description of the training login page

 Screen for Training page login

Figure 2: Screen for Training page login

(Source: Self-developed)

Activity diagram for the training login page

Figure 3: Activity diagram for the training login page

(Source: Self-developed)

Activity Description of the skills achieved page

Case Name	Skills achieved page
Scenario	The responsible admin wants to know the achieved skills of the candidates by the training
Triggering Event	The required user details have been provided to the webpage to understand the achieved skills
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the achieved skills of the candidates
	The flow of Activities
	Admin	System
	1. Admin asks for providing the training ID	1. Enters the training ID
	2. Admin asks for types of skills	2. Provides the types of skills achieved through the training
	3. Asks for training duration	3. Provides required details and submits
Exception conditions	If the user credentials are not valid.

Table 3: Activity Description of the skills achieved page

 Screen for Skills achieved page

Figure 4: Screen for Skills achieved page

(Source: Self-developed)

Activity diagram for the skills achieved page

Figure 5: Activity diagram for the skills achieved page

(Source: Self-developed)

ER Diagram for Training

Figure 6: ER Diagram for Training

(Source: Self-developed)

Use case diagram for the recruitment on the internal team

Figure 7: Use case diagram for the recruitment on the internal team

(Source: Self-developed)

Description of the recruitment on the internal team

Case Name	Recruitment on the internal team
Scenario	The responsible admin wants to know about the recruitment in the internal team
Triggering Event	The required user details have been provided to the webpage to know about the recruitment of the internal team
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the recruitment in the internal team
	The flow of Activities
	Admin	System
	1. Admin asks for login	1. Enters the training ID
	2. Admin asks for details of the recruitment of internal team candidate’s salary and benefits	2. Provides all the details
	3. Asks for offer letter	3. Download the offer letter and logout
Exception conditions	If the user credentials are not valid.

Table 4: Description of the recruitment in the internal team

Activity Description of the internal team details

Case Name	Internal team details
Scenario	The responsible admin wants to know about the internal team details
Triggering Event	The required user details have been provided to the webpage to know about the internal team details
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the internal team details
	The flow of Activities
	Admin	System
	1. Admin asks for user ID	1. Enters the training ID
	2. Admin asks for the name of project	2. Provides the details
	3. Asks for project time duration	3. Provides the project time and submit
Exception conditions	If the user credentials are not valid.

Table 5: Activity Description of the internal team details

Screen for internal team details

Figure 8: Screen for internal team details

(Source: Self-developed)

 Activity diagram for the internal team details

 Figure 9: Activity diagram for the internal team details

(Source: Self-developed)

Activity Description of the salary and benefits details

Case Name	Salary and benefits details
Scenario	The responsible admin wants to know about the salary and benefits details
Triggering Event	The required user details have been provided to the webpage to know about the salary and benefits details
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the salary and benefits details
	The flow of Activities
	Admin	System
	1. Admin asks for user ID	1. Enters the training ID
	2. Admin asks salary	2. Provides the details
	3. Asks for benefits	3. Provides the details and submits
Exception conditions	If the user credentials are not valid.

Table 6: Activity Description of the salary and benefits

Screen for the salary and benefits details

Figure 10: Screen for the salary and benefits details

(Source: Self-developed)

Activity diagram for the salary and benefits details

Figure 11: Activity diagram for the salary and benefits details

(Source: Self-developed)

Activity Description of the Offer letter details

Case Name	Offer letter details
Scenario	The responsible admin wants to know about the Offer letter details
Triggering Event	The required user details have been provided to the webpage to know about the offer letter details
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can see the Offer letter details
	The flow of Activities
	Admin	System
	1. Admin asks for user ID	1. Enters the training ID
	2. Admin asks for the password	2. Provides the password
	3. Asks to download the offer letter	3. Download the offer letter
Exception conditions	If the user credentials are not valid.

Table 7: Activity Description of the offer letter details

Screen for the offer letter details

Figure 12: Screen for the offer letter details

(Source: Self-developed)

Activity diagram for the offer letter details

Figure 13: Activity diagram for the offer letter details

(Source: Self-developed)

ER diagram for the recruitment details

Figure 14: ER diagram for the recruitment details

(Source: Self-developed)

 A use case diagram for applying the relevant jobs

Figure 1: Apply relevant jobs use case

(Source: Self-developed)

Activity Description about the relevant jobs page

Case Name	Apply relevant jobs on the webpage
Scenario	The responsible admin decides to apply on the page
Triggering Event	The required user details have been provided to the webpage to complete the application
Brief Description	The candidate requires to provide valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	The responsible admin needs to use valid credentials
Post-conditions	Admin can also access other pages
	Flow of Activities
	Admin	System
	1. Admin desires to apply for jobs	1. Admin provides details for application
	2. Required details are provided	2. Important data needs to store in the database
	3. The database shows the confirmation for receiving data successfully	3. Application has been completed successfully
Exception condition	If the user credentials are not valid.

Table 1: Activity Description of the application for relevant job page

Screen diagram of applying for relevant jobs

 Figure 2: Screen diagram of applying relevant jobs

(Source: Self-developed)

Activity diagram of applying for the relevant jobs page

Figure 3: Activity diagram for the relevant jobs

Activity Description about scheduling time page

Case Name	Admin schedule time for the page
Scenario	The responsible admin desires to schedule a time for the web page
Triggering Event	All the required information has been provided for the scheduling time process
Brief Description	The selected user requires .to produce valid user credentials
Stakeholders	Candidate, Admin
Actors	Admin
Pre-conditions	Valid user credentials are provided by the admin
Post-conditions	Admin can also access other pages
	Flow of Activities
	Admin	System
	1. Admin asks for scheduling time	2. Instructions related to the scheduled time process have been provided to the system
	2. Provides important information	2. All the important details need to be stored in the database.
	3. The database shows the receiving of data successfully	3. The schedule time process has been completed successfully.
Exception condition	If the credential of the candidate does not match with the existing data.

Table 2: Activity Description of schedule time page

Screen diagram of a scheduled time page

 Figure 4: Screen diagram of schedule time

(Source: Self-developed)

Activity diagram of the scheduled time page

Figure 5: Activity diagram for the scheduled time

Activity Description about negotiating payment and benefits page

Case Name	Negotiating payment and benefits
Scenario	The responsible admin desires to negotiate payments and benefits
Triggering Event	The task of negotiating pay and benefits has been performed by the admin
Brief Description	The candidate must negotiate to pay up and benefits.
Stakeholders	candidate, Admin
Actors	Admin
Pre-conditions	Negotiating pay up and benefits should be provided accurately
Post-conditions	Admin can successfully negotiate payment and benefits
	Flow of Activities
	Admin	System
	1. The responsible admin wants to negotiate pay up and benefits.	1. Asks the candidate to negotiate payment and benefits.
	2. All the required credentials are provided on the webpage	2. All the credentials need to be stored in the database
	3. The database confirms that negotiating pay-up data has been received successfully.	3. Negotiating payment and benefits have been performed successfully.
Exception condition	If user credentials do not match with the existing data.

Table 3: Activity Description of negotiating payment and benefits page

Screen diagram for negotiating pay up and benefits on the page

 Figure 6: Screen diagram of negotiating pay up and benefits

(Source: Self-developed)

Activity diagram for negotiating pay up and benefits on the page

Figure 7: Activity diagram for the negotiating pay up and benefits

Activity Description about the release offer letter page

Case Name	Release offer letter from the webpage
Scenario	The responsible admin desires to release offer letter  from the webpage
Triggering Event	The admin press the release offer letter option
Brief Description	Admin selects the option release offer letter  and then press the login button
Stakeholders	Applicants, Admin
Actors	Admin
Pre-conditions	A release offer letter option should be provided
Post-conditions	One option is there for release offer letter. The admin either chooses yes or no for releasing offer letter
	Flow of Activities
	Admin	System
	1. The task related to releasing the offer letter  needs to be performed by admin	1. The releasing offer letter request is sent to the system
	2. The required option has been utilized for releasing offer letter	2. All the required details need to be stored in the database.
	3. The database confirms the successful receiving of data	3. Successful releasing offer letter out has been performed
Exception condition	If the cancel option is pressed then the release offer letter will not be done.

Table 4: Activity Description of the release offer letter page

Screen diagram for release offer letter page

Figure 8: Screen diagram of release offer letter

(Source: Self-developed)

Activity diagram for release offer letter page

Figure 9: Activity diagram for releasing offer letter

(Source: Self-developed)

ER diagram of applying for jobs

Figure 10: A ER diagram of applying for jobs

(Source: Self-developed)

ER diagram for the recruitment agency

Figure 49: ER diagram for the recruitment agency

(Source: Self-developed)

Sequence diagram for the recruitment agency

Figure 50: Sequence diagram for the recruitment agency

(Source: Self-developed)

References

THAKOET, A. and Manirochana, N., 2021. INFLUENTIAL FACTORS OF ORGANIZATION SELECTION AMONG MEMBERS OF GENERATION Y THROUGH A RECRUITMENT AGENCY IN ASOKE IN THE BANGKOK METROPOLITAN AREA.

Vuorelma, L., 2018. A LinkedIn Job Ad Case study for a small Recruitment Agency in London.

Thongsawang, S. and Meebua, S., 2019. The Analysis of Corruption in Transnational Migrant Workers’ Brokerage Networks within the Thai Seafood Processing Industry: A Case of Recruitment Agency through Memorandum of Understanding between the Governments in the Employment of Workers (MOU). Asia Social Issues, 12(2), pp.187-215.

Santos, A., Armanu, A., Setiawan, M. and Rofiq, A., 2020. Effect of recruitment, selection and culture of organizations on state personnel performance. Management science letters, 10(6), pp.1179-1186.