Table of Contents

1. Project Planning ........................................................................................................... 2

1.1. Problem Statement............................................................................................................ 2
1.2. Scheduling ......................................................................................................................... 3
1.3. Requirement Gathering ..................................................................................................... 3
Interview ......................................................................................................................................... 3
1.4: Concept Diagram ............................................................................................................... 5
Use Case Diagram ........................................................................................................................... 5
Use Case Description ...................................................................................................................... 6

2. Analysis ........................................................................................................................ 8
2.1. SRS .................................................................................................................................... 8
Functional Requirement ................................................................................................................. 8
Non-Functional Requirement ......................................................................................................... 8
2.2 Analysis Class Diagram ........................................................................................................ 9

3.Design ......................................................................................................................... 10
3.1. Design Pattern ................................................................................................................. 10
GRASP............................................................................................................................................ 10
3.2. Design Class Diagram ....................................................................................................... 11

4.Implementation........................................................................................................... 12
4.1. Testing ............................................................................................................................ 12
Test Plan for Jobseek Website ...................................................................................................... 12

5.Selection of Methodology ............................................................................................ 15

5.1. Rapid Application Development ....................................................................................... 15
Advantages of RAD for JobSeek .................................................................................................... 15
Limitations of RAD for JobSeek ..................................................................................................... 15
Stages of RAD ................................................................................................................................ 15
1. Project Planning
1.1. Problem Statement
Problem Statement - 1 Slow matching process
Description The clerk has to manually match the job from employer with
candidates. Each matching process takes about 20 minutes.
Cause/Source Redundancy
Solution Website.
All data are recorded in database
Later auto matching is done.

Problem Statement - 2 No buck-up data

Description All of the data are stored in book. There is no back-up data if the data
are missing.
Cause/Source Risk
Solution Database will automatically back-up daily data.

Problem Statement - 3 Time consuming

Description All data are needed to record in book. When users write the wrong
data, they need to rewrite again.
Cause/Source Redundancy
Solution User can easily rewrite in database without wasting time.

Problem Statement - 4 Editing

Description If employer records wrong data in book, this can’t be edit. Thus,
employer needs to record again.
Cause/Source Redundancy
Solution Employer can easily edit in website and database.

Problem Statement - 5 Illegible handwriting

Description All data are recorded into books. Book records are mix of type text
and handwriting. Illegible handwriting can cause the loss of data.
Cause/Source Lost data
 Solution Website can show clear data to user. Employer can also write with
different font in website.

1.2. Scheduling

Figure 1.2.1: Gantt Chart

1.3. Requirement Gathering

Interview
Definition Interview is a data collection method that includes oral
questioning of respondents (lshenqeeti, 2014).
Benefits of Interview  Interview gives high return rate
(project)  Interview can control answering order
 Body language and facial expressions are more clearly
identified and understood
Setback problem that  Interview is time consuming
you might face  The project will be undermined if the interviewer is not
highly skilled and experienced
 Interview can be costly
Who to interview Interview to manager because the interview method offers high
response quality and it takes advantage of the facilitators’
presence.
Tips/steps 1. Define the purpose of interview
2. Designing the interview format
3. Develop interview questions
4. Selecting and training
5. Analysing interview data
Samples Question  What is your role in this system?
 What kind of problems do you have in this system?
 How long does it take to match the job?

Questionnaire
Definition Questionnaire is the method of data collection in which each
person is asked to respond to the same set of the questions in
an order (Abawi, 2013).

Benefits of  Many information can be collected from a large number

Questionnaire of people in a short time
 The researcher can easily quantify the results of the
questionnaire
 Questionnaires are cost-efficient.
Setback Problem of  Questionnaire can be applicable only to those
Questionnaire respondents who have an experience.
 The information collected by questionnaire cannot say to
be valid.
 The full context of the situation can make forgetful to the
respondents.
Who to Questionnaire Questionnaire to the person who have experience because
experience person can give correct answer which will effective in
the system.
Tips/steps 1. Determine what information is required?
2. Decide on method of data collection.
3. Develop questionnaire question
4. Plan the timing of questionnaire
5. Analysis the responses
Samples Questions How many people control this system?
 3 to 4
 4 to 6
 6 to 10
 Others
Do you want to upgrade this system?
 Yes
  No
Are you having problem with this system?
 Yes
 No

1.4: Concept Diagram

Use Case Diagram

Figure 1.4.1: Use Case Diagram

Use Case Description
Use Case Name Apply Job

Triggering event Jobseekers want to apply job

Brief description Jobseekers login with their account. Jobseekers create resume to
apply job. Before jobseekers apply the job, jobseekers need to register.
The system will save the data when jobseekers apply the job.
Actor Jobseekers

Preconditions Jobseeker accounts must exist.

Post conditions Job must be applied. Database must exist.

Flow of activities Actor System

1. Jobseekers login with 1.1. System validates

their account jobseeker account
2. Jobseekers create 2.1. System create the new
resume resume
3. Jobseekers apply job 3.1. System save the data of
applied job through
database
Exception 2.1. If there is no jobseeker account of applied job, the system will
show the register screen.
conditions

Use Case Name Manage Users

Scenario Manage account of jobseeker and employee

Triggering event Admin manages user account

Brief description Admin login with admin account. Admin can search user account.
Admin can delete only to registered users account. Admin can also
update their accounts. When admin delete users account, the system
will delete through the database.
Actor Admin

Preconditions Jobseeker accounts must exist. Employee accounts must exist.

Post conditions Records of users must be deleted. Records of employee must be

updated. Database must exist.
Flow of activities Actor System

4. Admin login with admin 3.2. System validates admin

account account
 5. Admin search user 2.1. System shows the list of user
account accounts.
6. Admin delete user 3.1. System delete the user
account account through the database
7. Admin update user 4.1. System update the user
account account through the database
Exception 2.1. If there is no user account of admin searched, the system will
show error message.
conditions
2. Analysis
2.1. SRS
Functional Requirement
1. Employer can advertise their vacancies. Website should have employer’s web portal
section where employer can advertise their vacancies by filling up a standard online
‘Job Offer’ form.
2. Admin should manage the payment of both employer and job seekers. The Website
should contain edit payment section where the payment can be managed for both
parties.
3. The system should match the Employer’s vacancy ads with suitable CV of the
applicants. The website should have the function to match vacancy with CV.
4. Jobseekers can register their account. Website should have registration section where
jobseekers can register their account.
5. Jobseekers should be able to apply job. The website should have resume section
where jobseekers can create their resume with their account to apply job.

Non-Functional Requirement
1. The website should be easy to use by the user. The website should have clear
navigation bar, menu and also should contain the help section.
2. All data should be stored with safety. The system should use some of the web security
feature in the website.
3. The website should have different language. The website should include the multiple
languages (France, English, Spain, Germany) where user can read with suitable
language.
2.2 Analysis Class Diagram

Figure 2.2.1: Class Diagram

3.Design
3.1. Design Pattern
GRASP
GRASP is known as the General Responsibility Assignment Software Patterns. GRASP is the
fundamental principles of object oriented design related to assigning defining objects (Duncan,
2012). GRASP patterns focus on one of the most important aspects of design. GRASP classes
use their own information to fulfil tasks. GRASP patterns are used to assign responsibility to
objects.

Figure 3.1.1: GRASP

Controller
Controller is a non-user interface object responsible for receiving or handling a system event
(Duncan, 2012). The task of controller is the breaking up the general function into the sub
function.
In Jobseek, ‘Edit Resume function is break up into ‘Add Resume’, ‘Update Resume’ and
‘Delete Resume’.

Figure 3.1.2: Controller

Low Coupling
Low coupling is a measure of how loosely one element is connect to other elements (Duncan,
2012). If the sub class is deleted, it doesn’t effect to other irrelevant classes.
In JobSeek, ‘Company’ class is low coupling because if the ‘Job’ class or ‘Vacancy’ class is
deleted, it doesn’t effect to others classes.

Figure 3.1.3: Low Coupling

3.2. Design Class Diagram

Figure 3.2.1: Design Class Diagram

4.Implementation
4.1. Testing
Test Plan for Jobseek Website
Test Test Area Purpose Test Steps Excepted Actual Correcti
Type Result Result ons
Unit Test Jobseeker To test 1. Access the Database will
Registrati Register website save the data
on with 2. Type name of jobseeker.
correct into “User Then, user will
email Name” box successfully
3. Type email in Register.
“Email address”
box
4. Type
password in
“Password” box
5. Click
“Register”
button
Unit Test Log-in To test 1. Access the Database will
Employee sing-in website check the data
with 2. Type ID into of employee
correct “Log-in” box and then
password 3. Type employee will
password into log-in
“Password” box successfully.
4. Click “Log-in”
button
Unit Test Advertise To test 1. Access the Employee will
Vacancies the job offer form successfully
function through the advertise
of employer ‘s web vacancies.
advertise portal Data will save
vacancie 2. Click “Add to the
s Job” button database.
 3. Upload
vacancies
4. Click
“Upload” button
Stub Test Email To test 1.Access the The website
the email website will display as
with 2. Click on “Correct E-
correct register page mail” after the
format 3. Type the system
“jobseek@gmail checks the
.com” validations.
on “E-mail” box

Stub Test Login ID To test 1. Access the The system

the log in website will check the
with 2. Click on validations
correct id employee login and then then
page website will
3. Type display as
“EmpJob1” on “Correct ID”.
“Login ID” box

Stub Test Upload To test 1.Access the Jobseeker will

CV the CV website successfully
with 2. Click on upload CV
correct jobseeker after the
format register page system
3. Click “Choose checks the
File” button validations.
4. Select the
“job.pdf” CV
Collabora Password To test 1. Access the The website
tion test password website will display as
with 2. Click on “correct
confirm register page password”
password after the
 3.Type system
“123Job123” checks the
on “Password” validations.
box
4.Type
“123Job123”
on “Confirm
Password” box

Collabora Matching To test 1.Access the The job will

tion test process the website and successfully
matching click on match after
process employee site. the system
of 2. Upload match the
employer’ vacancy vacancy with
s 3. Click on cv.
vacancy jobseeker site.
with the 4. Upload CV
CV
5.Selection of Methodology
5.1. Rapid Application Development

RAD knows as a development life cycle which give faster development and higher quality
results for JobSeek (Hirschberg, 2014). It focuses developing software in a short time. This
methodology is iterative and incremental which means that it uses the same step to do
everything and increase in feature additions. This methodology uses case tool to do test which
give faster the development time for JobSeek.

Figure 5.1.1: RAD

Advantages of RAD for JobSeek

1. It reduces development time for JobSeek because this methodology uses case tool to
do the test
2. It produces better quality by having customer feedback and iterative and incremental
methods.
3. It develops the software in a short time because this methodology cuts red tape
process
4. It completes the projects on time and within budget by focusing on iterative and
incremental development.
Limitations of RAD for JobSeek
1. RAD requires highly skilled developers and designers because it uses the CASE tools
to develop the system.
2. It is high costly because this method uses tools and software to develop the system.
3. It required complete business requirements before start the project
Stages of RAD
1. Requirements Planning Stage: In requirements planning stage designers, developers
and users agree on project scope and application requirements. This Stages requires
intense users at different levels of organization.
2. User Design Stage: During user design stage, the system analysts meet with users.
This stage allows users to interact with systems analysts. Case tools will be useful in
this stage. The designed product will be refined by the system analysts by the user
responses to the product.
3. Construction Stage: In the construction stage, developers finalize the design and build
the system. This stage also includes the cutover the red tape. Construction stage is
repeated during the necessary of the new components are required. The coding,
testing and integration are the tasks of this stage.
4. Cutover Stage: The cutover stage includes the integrating the old system to the new
system. User training tasks and completing the necessary are also done this stage.
User acceptance is the last point of this stage.
Bibliography
Rapid Application Development (RAD): A Brief Overview [Book] / auth. Hirschberg Morton
A.. - 2014. - Vol. 2 : 1.
Interviewing as a Data Collection Method: A Critical Review [Book] / auth. lshenqeeti
Hamza. - United Kingdom : Sciedu Press, 2014. - Vol. 3.
Data Collection Instruments (Questionnaire & Interview) [Book] / auth. Abawi Karim. -
2013.
GRASP Patterns [Book] / auth. Duncan David. - 2012.