Job Seeker Website Project Report On Object-Oriented Analysis And Design Major Computer Science.pdf

The Visitor can continue making changes to the registration form or cancel the registration, at which point the use case ends.. The Visitor can continue making changes to the registratio

UNIVERSITY OF ENGINEERING AND TECHNOLOGY

Job Seeker Website

PROJECT REPORT ON OBJECT-ORIENTED ANALYSIS and

DESIGN Major: Computer Science

Supervisor : Assoc Prof Trương Ninh Thuận

HA NOI – 2022

1.1 Admin interface

CHAPTER 1 INTRODUCTION

1 Problem statement

1.1 Addressing the problem

As technology develops, online job portal is becoming increasingly popular It is amuch more convenient and easier way to find a appropriate jobs as seekers don’t have towaste their time outside This evokes the need for a system to help the communicationbetween job seekers and companies representatives Jobs seekers need to find a jobquickly and companies representatives need to find human resources meeting therequirements This has come to a demand for a system to solve this problem

The system’s end users are as below:

2.2 Definitions

Introduction This document is used to define terminology specific to the problem domain, explaining terms, which may be unfamiliar to the reader of the use-case

descriptions or other project documents Often, this document can be used as an informal data dictionary, capturing data definitions so that use-case descriptions

and other project documents can focus on what the system must do with the information Definitions The glossary contains the working definitions for the key concepts in the JobSeeker.com website

a Account

A record about a user/administrator containing information about his/her name, e-mail address, password, phone number and optional self-introduction Each account has a unique user ID and a password, which are used to identify the user/administrator and grant them access to secure parts of the system

b Administrator

A person whose job is to ensure that the site is free of spam offer jobs or abusive behaviors This entails approving offer jobs before they are published, deleting users withabusive behaviors

A person who has a registered candidate account on the website Candidate users are able

to publish CV, view lists of jobs and apply for appropriate one

2 Company

A person who has a registered company account on the website Company users are able

to publish offer job that can be uploaded after administrator approving

e Visitor

A person who is interested in viewing offer jobs on the website but does not have an account

CHAPTER 2 SOFTWARE SYSTEM REQUIREMENTS

1 Use case diagram

Figure 2.1 Use case model for JobSeeker website system

2. Use case specification

a User

This use case starts when the Visitor request to create an Candidate Account on the website

1 The system display a form that asks the Visitors to enter the following information

Alternative Flows

Missing Information

If any of the above fields (except for self-introduction) are not filled in, the system displays an error message The Visitor can continue making changes to the registration form or cancel the registration, at which point the use case ends

User ID Already Exists

If the specified user ID already exists, the system displays an error message The Visitor can continue making changes to the registration form or cancel the registration, at which point the use case ends

This use case starts when the Candidate user request to sign in the website

1 The system display a form that asks the Candidate user to enter the following information:

- Username

- Password

2 Once the Candidate user provides the requested information, the system verifies that the username and password is correct with the username and password in candidate user databases.Alternative Flows

Missing Information

If any of the above fields (except for self-introduction) are not filled in, the system displays an error message The Candidate user can continue making changes to the registration form or cancel the registration, at which point the use case ends

User ID or password doesn’t match

If the specified user ID or password doesn’t match with the username or password in candidate user databases, the system displays an error message.

The Candidate user can continue making changes to the sign in form or cancel it, at which point the use case ends

This use case starts when the Candidate user request to change password in the website

1 The system display a form that asks the Candidate user to enter the following information:

- Old password

- New password

- Retype new password

2 Once the Candidate user provides the requested information, the system verifies that the password is correct with password in candidate user databases; check new password with consistent security and match with retype new password

Alternative Flows

Missing Information

If any of the above fields (except for self-introduction) are not filled in, the system displays an error message The Candidate user can continue making changes to the

registration form or cancel the registration, at which point the use case ends

Password doesn’t match

If the specified password doesn’t match with the password in candidate user databases, the system displays an error message

The Candidate user can continue making changes to the sign in form or cancel it, at which point the use case ends

Password and retyped password don’t match

If the new password doesn’t match with the retyped password, the system displays an error message

The Candidate user can continue making changes to the sign in form or cancel it, at which point the use case ends

1 The system display a form that asks the Candidate user to view and change some of the following information:

This use case starts when the Candidate user request to update CV on the website

1 The system display a form that asks the Candidate user to upload CV as pdf file

Alternative Flows

Error File

If this file is not a pdf file, the systems displays an error message The Candidate user can continue making changes to the registration form or cancel the registration, at which point the use case ends

This use case starts when the Candidate user request to filter job display on the website

1 The system display a list of filter button that Candidate user can choose to filter job:

- Name of job with Search field

- Field of job with Select field

- Location with Select field

2 Once the Candidate user provides the requested information, the system displays the appropriate list of offered job with filters

Alternative Flows

Not available Job

If the system can’t find any job with these filters, the system displays a notification message.Pre-Conditions

The Candidate user have to log in successfully

1.3 Identify subsystems and interfaces

Figure 4.5 The Database subsystem and interfaces

1.4 Identify design mechanisms

Table 4.2 Design and implementation mechanisms

2 Use case design and architecture refinement

2.1 Subsystem design

Figure 4.6 The Database subsystem elements diagram

Figure 4.7 System dependencies class diagrams

2.2 Design sequence diagram

Figure 4.8 Design sequence diagram for Apply Job Use Case

Figure 4.9 Design sequence diagram for Approve Job UC

Figure 4.10 Design sequence diagram for Create Account UC

Figure 4.11 Design sequence diagram for Delete User UC

Figure 4.12 Design sequence diagram for Edit Job UC

Figure 4.13 Design sequence diagram for Filter Job UC

Figure 4.14 Design sequence diagram for Login UC

Figure 4.15 Design sequence diagram for Publish Job UC

Figure 4.16 Design sequence diagram for Resolve Job UC

Figure 4.17 Design sequence diagram for Update Account UC

2.3 Class design

Figure 4.18 Design VOPC for Apply Job UC

Figure 4.19 Design VOPC for Approve Job UC

Figure 4.20 Design VOPC for Create Account UC

Figure 4.21 Design VOPC for Delete User UC

Figure 4.22 Design VOPC for Add To Edit Job UC

Figure 4.23 Design VOPC for Filter Job UC

Figure 4.24 Design VOPC for Login Form UC

Figure 4.25 Design VOPC for Publish Job UC

Figure 4.26 Design VOPC for Resolve Job UC

Figure 4.27 Design VOPC for Update Account UC

2.4 Database design

CHAPTER 5 USER INTERFACE DESIGN

1 User interface design

Objectives of designing user interface:

● User-friendly interface

● Information is presented clearly and highlight important information

● Harmonious and bright colors

● Improve user experience on the website

Most of the admin interface pages are divided into 3 parts as follows:

Figure 5.1 Admin interfaceInside:

- Menu is the place to store a list of features for administrator, for example: Filter job, Apply Job,

- Header contains the website's logo, user’ name

- Content contains the content of the specific function contained in the Menu.The admin page usually manages a list of objects, so it is necessary to build a tabular interface that the administrator can interact with Thus, Content part usually has the following layout:

Figure 5.2 Content part

2 Result

Figure 5.4 Sign up

Figure 5.5 Sign in

Figure 5.6 Candidate Homepage

Figure 5.7 Company Homepage

Figure 5.8 Visitor View

Figure 5.9 Candidate Apply Job

Figure 5.10 Candidate Pending Job

Figure 5.11 Candidate Update profile

Figure 5.12 Company Resolve Job

Figure 5.13 Company Pending Candidate

Figure 5.14 Job

Figure 5.15 Admin manage account

Figure 5.16 Admin manage job