Jobs Portal Kotli

Submitted By:

Names Registration number

Sufyan Tariq 2013-UKIB-2030

Abid Hussain 2013-UKIB-2039

Tania Karamat 2013-UKIB-2049

Supervised By:

Mr. Zaheed Ahmed

Lecturer
Department of CS & IT
University of Kotli AJ&K

Department of Computer Science and Information Technology

Faculty of Administrative Sciences Kotli
University of Azad Jammu and Kashmir
Muzaffarabad

Session: 2013-2017

i
ii
 APPROVAL CERTIFICATE

It is certified that the project work presented in this report entitled “Jobs Portal Kotli”
submitted by Sufyan Tariq (Roll No. 30), Abid Hussain (Roll No. 40) and Tania Karamat
(Roll No.49) of Session (2013-17) supervised by Zaheed Ahmed in our opinion is fully
adequate in scope and quality of Bachelor of Science (Information Technology).

_________________
(Supervisor)
Mr. Zaheed Ahmed
Lecturer
Department of CS & IT
University of Kotli AJ&K

_______________
(Chairman)
Mr. Adnan Arif Butt
Department of CS & IT
University of Kotli AJ&K

iii
 UNDERTAKING

We declare that project work titled “Jobs Portal Kotli” is our own work. The work has
not been presented elsewhere for assessment. Where material has been used from other
sources it has been properly referred.

-----------------------------------------
Sufyan Tariq

2013-UKIB-2030

-----------------------------------------

Abid Hussain

2013-UKIB-2039

-------------------------------------
Tania Karamat

2013-UKIB-2049

iv
 ABSTRACT

Our aim is to develop an online “Job Portal District Kotli" which is easily accessible to
the user and administration as well. This system regulates the activities between users,
provide ease in their work by applying. All those activities that can be done manually
can be done in our system. Moreover our systems have auto result compilation facility
that is very useful for the user and admin.

This is a web-related application that permits us to approach the entire knowledge

regarding the users and admin etc. This application is also called as Job Portal. Here we
would gain the recent knowledge regarding the users and admin. This general
application planned for aiding the users of an organization about details on the users,
the administrator would maintain the accounts of the users and upload the current
information regarding the Jobs. We will take the record of users and save their info for
Job registration. The main problem projected is that user’s particulars are reported
manually in distinct records, which is a laborious job. Handling and updating these
records manually increase the chances of mistakes. It takes a lot of time and needs many
employees to accomplish the task. But here we will store all information of applicants
online and generate their result online and also will maintain their accounts.

v
 Acknowledgements

All the praise and glory to Allah, Who blessed us with the courage and knowledge to
achieve our goal. We can never thank Him enough for His countless blessings upon us.
Praise to Prophet Mohammad (S.A.W.W), who is and will always be a source of
guidance and knowledge for humanity as a whole.

For us, a mile stone of this nature would never have been possible to achieve without
the support of galaxy of some truly loving and kind people in our life. No words can
fully describe our feelings of respect and gratitude for our affectionate parents,
supporting sibling and friends, whose love, encouragement and prayers invariably
buoyed us up. Their concern, love and support can never be paid back.

We owe a lot of sincere gratitude to our respected supervisor Mr. Zaheed Ahmad whose
true guidance, positive criticism and sincere encouragement made us to get to our
destination. He became a source of inspiration for us and kept us moving in the right
direction towards our goal.

Abid Hussain

Sufyan Tariq

Tania Karamat

vi
 DEDICATION

“A TEACHER should inspire a child to reach academic success;

A PARENT should inspire their child to use that success in
a way that influences Positive change in the world.”

Dedicated to
Our
Beloved Parents,
Respected Teachers
&
Lovely Friends

vii
 Table of Contents
1 Chapter 1......................................................................................................................................... 1
1.1 Purpose ................................................................................................................................... 1
1.2 Product Scope ......................................................................................................................... 1
1.3 What problems will it solve? ................................................................................................... 2
1.4 Software Process Model ......................................................................................................... 2
2 Chapter 2......................................................................................................................................... 4
2.1 System Conception ....................................................................................................................... 4
2.1.1 What problems will it solve?...................................................................................................... 4
2.1.2 Where will it be used? ............................................................................................................... 4
2.1.3 who is the application for .......................................................................................................... 4
3 Chapter 3......................................................................................................................................... 5
3.1 Proposed System .................................................................................................................... 5
3.2 Functional Requirements ........................................................................................................ 5
3.2.1 Login: ............................................................................................................................... 5
3.2.2 Logout: ............................................................................................................................ 5
3.2.3 Add Record:..................................................................................................................... 5
3.2.4 Search Record: ................................................................................................................ 5
3.2.5 Delete Record.................................................................................................................. 5
3.2.6 Update Record ................................................................................................................ 5
3.2.7 Apply for job.................................................................................................................... 5
3.2.8 Search for job .................................................................................................................. 5
3.2.9 Submit CV ........................................................................................................................ 6
3.2.10 Collect CV ........................................................................................................................ 6
3.2.11 Alert on CV ...................................................................................................................... 6
3.3 User Classes and Characteristics ............................................................................................. 6
3.3.1 Admin .............................................................................................................................. 6
3.3.2 End user: ......................................................................................................................... 6
3.4 Operating Environment .......................................................................................................... 6
3.5 User Documentation ............................................................................................................... 6
3.6 Assumptions and Dependencies ............................................................................................. 6
3.6.1 Dependencies:................................................................................................................. 6
3.6.2 Assumptions: ................................................................................................................... 6
3.7 External Interface Requirements ............................................................................................ 6

viii
 3.7.1 User Interfaces ................................................................................................................ 7
3.7.2 Software Interfaces ......................................................................................................... 7
3.7.3 Communications Interfaces ............................................................................................ 7
3.7.4 Hardware Interfaces ....................................................................................................... 7
3.8 System Features ...................................................................................................................... 7
3.9 Performance Requirements .................................................................................................... 7
3.10 Security Requirements ............................................................................................................ 8
3.11 Software Quality Attributes .................................................................................................... 8
3.11.1 Availability: ...................................................................................................................... 8
3.11.2 Usability: ......................................................................................................................... 8
4 Chapter 4......................................................................................................................................... 9
4.1 System Design ......................................................................................................................... 9
4.2 Design Approach ................................................................................................................... 10
4.3 Database Design.................................................................................................................... 10
4.4 Conceptual Schema............................................................................................................... 10
4.4.1 Class Diagram ................................................................................................................ 10
4.4.2 Object Diagram ............................................................................................................. 10
4.4.3 Data Dictionary .............................................................................................................. 12
4.5 Interaction Model ................................................................................................................. 12
4.5.1 Use Case Model............................................................................................................. 12
4.6 Sequence Model.................................................................................................................... 21
4.6.1 Scenarios ....................................................................................................................... 21
4.6.2 Sequence Diagrams ....................................................................................................... 21
4.6.3 Activity Diagram ............................................................................................................ 26
4.7 Logical Schema ...................................................................................................................... 36
4.7.1 Relation ......................................................................................................................... 36
4.7.2 Associating Tables ......................................................................................................... 36
4.8 Database Diagram ................................................................................................................. 39
5 Chapter 5....................................................................................................................................... 40
5.1 Signup:................................................................................................................................... 40
5.2 Add Job.................................................................................................................................. 41
5.3 Apply Job ............................................................................................................................... 42
6 Chapter 6....................................................................................................................................... 45
6.1 Testing Objectives ................................................................................................................. 45
6.2 Testing Principles .................................................................................................................. 45

ix
 6.3 Testing Approach .................................................................................................................. 45
6.4 Box Approach ........................................................................................................................ 45
6.4.1 White-Box testing ......................................................................................................... 46
6.4.2 Black-Box testing ........................................................................................................... 46
6.5 Testing Levels ........................................................................................................................ 46
6.6 Unit testing............................................................................................................................ 46
6.7 Integration testing ................................................................................................................ 46
6.8 System testing ....................................................................................................................... 46
6.9 Testing Types ........................................................................................................................ 46
6.9.1 Alpha Testing................................................................................................................. 47
6.9.2 Beta Testing................................................................................................................... 47
6.9.3 Acceptance Testing ....................................................................................................... 47
6.9.4 Usability Testing ............................................................................................................ 47
6.10 Test Cases.............................................................................................................................. 47
6.10.1 Test Case 01: Signup ..................................................................................................... 48
6.11 TestCase 02: Login……………………………………………………………………………………………..…….48
6.11.1 Test Case 03: Add Job ................................................................................................... 49
6.11.2 Test Case 04: Search Job ............................................................................................... 49
7 Chapter 6....................................................................................................................................... 50
7.1 Conclusion ............................................................................................................................. 50
7.2 Future Improvements ........................................................................................................... 50
7.3 Limitations............................................................................................................................. 51
Appendices........................................................................................................................................ 52
Glossary ............................................................................................................................................. 52
References ............................................................................................................................................ 53

x
List of Figures
Figure 1 Iterative Waterfall Process Model [Sommerville-2009] ............................................. 3
Figure 2 Class diagram of JPK ................................................................................................ 11
Figure 3 Use Case diagram for JPK......................................................................................... 14
Figure 4 Use Case Diagram for Login ..................................................................................... 22
Figure 5 Scenario and sequence diagram for Signup............................................................... 22
Figure 6 Scenario and Sequence Diagram for Log out ............................................................ 23
Figure 7 Scenario and Sequence Diagram for Add record ...................................................... 23
Figure 8 Scenario and Sequence Diagram for Delete data ..................................................... 24
Figure 9 Scenario and Sequence Diagram for Search job ....................................................... 24
Figure 10 Scenario and Sequence Diagram of Add job ........................................................... 25
Figure 11 Scenario and Sequence Diagram for Applying for Job ........................................... 25
Figure 12 Scenario and Sequence Diagram for Add user ........................................................ 26
Figure 13 Activity Diagram for log in ..................................................................................... 27
Figure 14 Activity Diagram for log out ................................................................................... 28
Figure 15 use case add record to JPK ...................................................................................... 28
Figure 16 Activity Diagram for Delete record ......................................................................... 29
Figure 17 Activity Diagram for Search job ............................................................................. 30
Figure 18 Activity Diagram for Add job ................................................................................. 31
Figure 19 Activity Diagram for Apply job .............................................................................. 32
Figure 20 Activity Diagram for Submit CV ............................................................................ 33
Figure 21 Activity Diagram for Remove user ......................................................................... 34
Figure 22 Activity Diagram for Signup ................................................................................... 35
Figure 23 Activity Diagram of alert......................................................................................... 35
Figure 24 Mapping between candidate and admin Classes .................................................... 37
Figure 25 Mapping between employers and job Classes ........................................................ 38
Figure 26 Database Diagram for JPK ...................................................................................... 39
Figure 27 JPK Login Panel ...................................................................................................... 40
Figure 28 JPK Add job panel .................................................................................................. 41
Figure 29 JPK Add job panel .................................................................................................. 43

xi
List of Tables
Table 1 Data Dictionary ........................................................................................................... 12
Table 2 Use Case ..................................................................................................................... 13
Table 3 Use Case Description for User Login ......................................................................... 15
Table 4 Use Case Description for User Logout ....................................................................... 15
Table 5 Use Case Description for Adding Record................................................................... 16
Table 6 Use Case Description for Deleting Record ................................................................. 17
Table 7 Use Case Description for Search job .......................................................................... 17
Table 8 Use Case Description for Add job .............................................................................. 18
Table 9 Use case Description for Apply job ............................................................................ 18
Table 10 Use case Description for Submit CV ........................................................................ 19
Table 11 Use Case Description for Add new user ................................................................... 19
Table 12 Use Case Description for Alert ................................................................................. 20
Table 13 Use Case Description for Remove user .................................................................... 20
Table 14 Test Case Name Signup ............................................................................................ 48
Table 15 Test Case Name Login .............................................................................................. 48
Table 16 Test Case Name Add Job .......................................................................................... 49
Table 17 Test Case Name Job search ...................................................................................... 49

xii
 1 Chapter 1

Introduction

This chapter describes the existing system and the proposed system in details. What problems
we were facing in the existing system, due to which we are going to atomize our system, are
described here? What functionality our system will provide, is described here.
1.1 Purpose
The basic purpose of our project is to make a portal that make easy to find the jobs
to sit at home and employees can put jobs. First the employee log in to portal through account
and password. After log in employee can put the job on portal .He can also check the Peoples
those who apply for job in his previous post. He can check the CV of candidate those who
apply. .People can search job of different title. People of district Kotli can apply and seek job
from any place within the district. At the end of this project; it will be easy to seek for job.
People can find job about their skills and apply for job online.Employe can put their job title
and require qualification on this portal. They can select the candidate and inform them.People
can check and search job on this portal .But if they want to apply for job they should be create
their account . It’s important to make sure you know the capabilities and qualities that will
make your users’ work-lives easier, and remember that users don’t have to necessarily use what
you put in front of them.

1.2 Product Scope

This web portal is solving the problems of peoples those who want to seek and apply
for job. It will also help the organization to put the available jobs.
It will provide following features.
 Online seek for job
 Online apply for job
 Give alert
 Put job ads
 Organization put the job
 Provide employer login form

1
 The user simply log in to the portal then he check any of the above service .If the user
want to apply for job then he will open the online job apply service .He check the available
vacancy. If he wants to apply for job then he will open online job form and put his detail.
Organizations put the available jobs. The benefits of jobs portal are well documented. If job
portals continually prove to increase employee and business productivity, as well as improve
communications, collaboration, and knowledge management, then why do so many portal
redevelopment projects can not fail.
1.3 What problems will it solve?
Nowadays there is a problem to seek job and apply job. So this problem is also facing
in the district of Kotli to get a job in school, colleges and other organization. It is also a problem
for organizations that how they advertise their jobs and find a good worker for a specific job.
There is no easy way for seek and apply job in district Kotli. To find an appropriate job there
is need of a Job Portal for District Kotli.
1.4 Software Process Model
Software process model is an abstract representation of a software process, which is a set
of activities that lead to the production of a software. Some of the generic process models are
waterfall model, evolutionary development and component based software engineering. For
this project we have used the iterative waterfall model because of clear and unchanging
business requirements. The waterfall development model originates in the manufacturing and
construction industries; highly structured physical environments in which after-the-fact
changes are prohibitively costly, if not impossible. Since no formal software development
methodologies existed at the time, this Hardware oriented model was simply adapted for
software development.The first known presentation describing use of similar phases in
software engineering was held by Herbet Belington at Symposium on advanced programming
methods for digital computers on 29 June 1956. This presentation was about the development
of software for SAGE.

2
Figure 1 Iterative Waterfall Process Model [Sommerville-2009]

3
 2 Chapter 2

Existing System Analysis

2.1 System Conception

Most of the systems start as vague ideas that need more substance. A good system
concept must answer the following questions as our system does:

2.1.1 What problems will it solve?

There is a problem to seek job and apply job. So this problem is also facing in the district
of kotli to get a job in school, colleges and other organization. It is also a problem for
organizations that how they advertise their jobs and find a good worker for a specific job. There
is no easy way for seek and apply job in district kotli. To find an appropriate job there is need
of a Job Portal for District Kotli.

2.1.2 Where will it be used?

It will be easy to seek for job. People can find job about their skills and apply for job
online.Employe can put their job title and require qualification on this portal. They can select
the candidate and inform them .People can search job of different title. People of district Kotli
can apply and seek job from any place within the district.

2.1.3 who is the application for

People of district Kotli can apply and seek job from any place within the district.

The portal will have the following features:

 People search job

 Apply online
 The Candidate will get the alert form the email automatically
 Organization put the job
 Provide employer login form
 Add jobs

4
 3 Chapter 3
Proposed System

3.1 Proposed System

System requirements are more detailed descriptions of the software system’s functions,
services, and operational constraints. The system requirements document (sometimes called a
functional specification) should define exactly what is to be implemented. It may be part of the
contract between the system buyer and the software developers. [Sommerville-2009]
3.2 Functional Requirements
These are statements of services the system should provide, how the system should
react to particular inputs, and how the system should behave in particular situations. In some
cases, the functional requirements may also explicitly state what the system should not do. The
functional requirements for a system describe what the system should do. [Sommerville-2009]
3.2.1 Login:
Administrator and end user will be able to login to admin side by using his user name
and Password.
3.2.2 Logout:
Administrator and end user will be able to logout from the admin side by pressing the
logout button.
3.2.3 Add Record:
Administrator will be able to add the record of user who will apply for job, check the
list of hospitals and police stations in emergency.
3.2.4 Search Record:
Administrator and check End Users will be able to search the record of a record holder.
3.2.5 Delete Record
Administrator will also be able to delete the record of job seekers.
3.2.6 Update Record
Administrator will be able to update the record.

3.2.7 Apply for job

End user can apply for job.
3.2.8 Search for job
End user search for job.

5
3.2.9 Submit CV
End user submit his CV
3.2.10 Collect CV
Admin collect the CV of end user.
3.2.11 Alert on CV
Admin give alert on selecting CV and user get alert on CV.
3.3 User Classes and Characteristics
There are two main user of this portal.
3.3.1 Admin
Admin is that who will manage this portal. The admin put new data in the portal. Admin
can add or remove the end user.
3.3.2 End user:
End user is that who will seek for job, apply for job and organization those put the
available jobs.
3.4 Operating Environment
This is a simple project so we will not make it for use in a specific environment. We
will make it as public can access and use it easily. Public can use it any environment.
This product is web-based and will be hosted by a web server. This product can be
viewed by any web browser, and has been tested for compliance with Internet Explorer, Google
and other one. The Windows OS will be used for this product.
3.5 User Documentation
• We follow the IEEE format and its different standard in documentation.
• We will run our system in software form.
• We will make hard binding of whole project.

3.6 Assumptions and Dependencies

3.6.1 Dependencies:
This is a web portal so it depends on internet. User can’t use it without internet. User
must be aware of using good web browser for using it. A web browser is also necessary for
use it.
3.6.2 Assumptions:
This web portal can’t use without linking internet. Without a supporting web browser
user can’t use it.
3.7 External Interface Requirements

6
  It is a web based system.

 We PHP language for making it.

 We use window based system.

3.7.1 User Interfaces

The first interface is the log-in screen. This is where the user has a specific Username
and Password so that they can gain access to the database. Next is the web interface where the
user can perform different types of functionality like adding records, searching records,
generating the reports and many other.
3.7.2 Software Interfaces
Along with the internet connection, the system makes indirect use of an internet
browser. Outside of the HTML code and PHP, the code doesn’t tell any software, including
the browser, what to do.
3.7.3 Communications Interfaces
The system uses an internet connection to connect to the database. The code itself
though, does not specifically direct the network controllers to do any work. The connection
with the API services to generate the SMS alert.
3.7.4 Hardware Interfaces
Though not necessarily interfacing with the hardware, the system must make use with
an internet connection
3.8 System Features
Our system provides the following features:

 Online job seeking in private schools , colleges and other organization:

The user can check the available vacancies in private sector online sit at home.
 Online CV submission:
The user can also put his CV and apply for job online.
 Selecting the candidate:
Schools and colleges admin can select the candidate online by checking their CV.\

 Alerts on CV of selecting candidate:

The selecting get alerts or some tag on his CV.
3.9 Performance Requirements
The performance requirements are as follows:

7
  System login/logout shall take less than 5 seconds.
 Searches shall return results within 10 seconds.
 Queries shall be processed within 10 seconds.
3.10 Security Requirements
There’s no special protection built into this system other than to provide the Jobs.
3.11 Software Quality Attributes
Quality attribute requirements such as those for performance, security, modifiability,
reliability, and usability have a significant influence on the software architecture of a system.
Architects need to understand their designs in terms of quality attributes.
3.11.1 Availability:
Checking that the system always has something to function and always pop up error
messages in case of component failure. In that case the error messages appear when something
goes wrong so to prevail availability problems.
3.11.2 Usability:
Checking that the system is easy to handle and navigates in the most expected way with
no delays. In that case the system program reacts accordingly and transverses quickly between
its states.

8
 4 Chapter 4

System Design

4.1 System Design

Design is the first step in the development phase for any engineered product or system.
The designer’s goal is to produce a model or representation of a class that will later be built.
Beginning, once system requirement have been specified and analyses, system design is the
first of the three technical activities -design, code and test that is required to build and verify
software. This document details out the overall software design.
The importance can be stated with a single word “Quality”. Design is the place where
quality is fostered in software development. Design provides us with representations of
software that can assess for quality. Design is the only way that we can accurately translate a
customer’s view into a finished software product or system. Software design serves as a
foundation for all the software engineering steps that follow. Without a strong design we risk
building an unstable system that will be difficult to test, one whose quality cannot be assessed
until the last stage.
During design, progressive refinement of data structure, program structure, and
procedural details are developed reviewed and documented. System design can be viewed from
either technical or project management perspective. From the technical point of view, design
is comprised of four activities – architectural design, data structure design, interface design and
procedural design.
The development team devises a high level strategy, the system architecture, for solving
the application problem. They also establish policies that will serve as a default for the
subsequent, more detailed portions of design. The system designer must decide what
performance characteristics to optimize, choose a strategy of attacking the problem, and make
tentative resource allocations. For example, the system designer might decide that changes to
the workstation screen must be fast and smooth, even when windows are moved or erased, and
choose an appropriate communications protocol and memory buffering strategy.
We find it useful to model a system from three related but different perspectives, each
capturing important aspects of the system, but all required for a complete description. The class
model represents the static, structural, “data” aspects of a system. The state model describes
the temporal, behavioral, “control” aspects of a system. The interaction model represents the

9
collaboration of individual objects, the “interaction” aspects of a system. A typical software
incorporates all the three aspects: it uses data structures (class model), it sequences operations
in time (state model), and it passes data and control among objects (interaction model). [Balaha
M, Rum Baugh J-2005]
A class model captures the static structure of a system by characterizing the objects in
the system, the relationships between the objects, and the attributes and operations for each
class of objects. The class model is the most important of the three models.
There are two types of models of structures
1. Class Diagrams
2. Object Diagrams
4.2 Design Approach
Design approach for this software is conventional, that is, database model used is
relational and on the other side Object Modeling Technique (OMT) is used.
4.3 Database Design
This system would have a database as its data store, so the design of the database is
very important. We chose relational database model for our database. Database design includes
conceptual, logical and physical design phases, which are discussed in this section.
4.4 Conceptual Schema
Conceptual design is about understanding the organization, the real world modeling; it
captures the essence of the real world scenario. In this phase all the important classes of the
system are extracted with their essential attributes and the relationship between them are
established. This results in class diagram.
4.4.1 Class Diagram
Class diagrams provide a graphic notation for modeling classes and their relationships
thereby describing possible objects. Class diagrams are useful both abstract modeling and for
designing actual programs.
4.4.2 Object Diagram
We will also occasionally use object diagrams. An object diagram shows individual
objects and their relationships. Object diagrams are helpful for documenting test cases and
discussing examples. A class diagram corresponds to an infinite set of object diagrams. [Balaha
M, Rum Baugh J-2005]

10
 Person
-person_name
-cnic
-gender
-contact_no
-email
-address
-qualification
-experience
-
+Login()
+Logout()
Employer +search()
-designation candidate
-institution_name -marital_status
-institution_address Admin -DOB
-website -occupation
* 1
+addJob() +closeJob() -reference1
+signup() 1
+approve() -reference2
+selectCandidate() 1 *
+putCV()
+searchJob()
1 1 1 +applyJob()
+signup()

1 1

*
*

Job *
*
-job_title *
-institution_name Applications Alerts
-requiredExperience -applicationDate -is_read
* -status
-jobLocation
-lastDate +submitApplication()
-gender +getAlerts()
-ageLimit
-jobType
-NoOfSeats

Figure 2 Class diagram of JPK

11
 4.4.3 Data Dictionary
Data dictionary for all modeling elements help designers to understand the
meaning and purpose of all modeling elements. Here is the data dictionary for JPK classes:

Admin—it holds the data for admin of the system who operate mainly with the system
using all of its services by having a user name and password for it
End user —a person who use portal for apply, add and search job.
JPK– Job Portal Kotli.

Table 1 Data Dictionary

4.5 Interaction Model

The interaction model describes how the objects in a system cooperate to achieve
broader results. The interaction model starts with use cases that are then elaborated with
sequence and activity diagrams. A use case focuses on the functionality of a system that is,
what a system does for users. A sequence diagram shows the objects that interact and the time
sequence of their interactions. An activity diagram elaborates important processing steps.
[Balaha M, Rum Baugh J-2005]
4.5.1 Use Case Model
Use case model consists of three things: actors, use cases, use case diagram
4.5.1.1 Actors
An actor is a direct external user of a system, an object or set of objects that
communicates directly with system but that is not part of the system. Each actor represents
those objects that behave in particular way towards the system. [Balaha M,
4.5.1.2 Use Cases
A use case is a coherent piece of functionality that a system can provide by interacting
with various actors.
Each use case involves one or more actors as well as the system itself. The actor needs
not all be the persons.
A use case involves a sequence of messages among the system and its actors. Some use
cases have a fixed sequence of messages. More often, however, the message sequence may
have some variations. [Balaha M, Rum Baugh J-2005]
12
4.5.1.3 Use Case Diagrams
A system involves a set of use cases and a set of actors. Each use case represents a slice
of the functionality the system provides. The set of use cases shows the complete functionality
of the system at some level of detail. Similarly each actor represents one kind of object for
which the system can perform behavior. The set of actors represents the complete set of objects
that the system can serve. Objects accumulate behavior from all the systems with which they
interact as actors. [Balaha M, Rum Baugh J-2005]
Our system involves a set of use cases like add job, search job, update record, delete
record and some other mention in use diagram with actors like administrator and End user.
Simply use cases define; in how many ways a system can be used or in how many ways a
system can act. Given below Use case summaries:

Login: Administrator and end user can login to their respective panels to access their related
functionalities/services.
Logout: Administrator and end user can logout from the system after performing their
required functions and operations.
Add Record: Administrator can add any type of data to the system’s database.
Delete Record: Admin can delete any data from portal.
Search job: Admin and end user can search job by name or job title.
Add job: End user can add any type of job on portal after log in.
Apply job: End user can apply for any job that is in the portal after log in.
Submit CV: End user can submit his cv through cv form.
Alert: Admin give alert to end user for new job or select for job.
Add new user: Admin can add or register new user in portal.

Table 2 Use Case

13
 Job Portal Kotli

Sign up

Log in

Log out

Add Job

Delete record

Search job
Visitor

Apply job

Admin Add Job

Submit cv

Add new user

Remove user

User

Email Alert

View

Figure 3 Use Case diagram for JPK

14
4.5.1.4 Use Case Description
Use case description is written to describe a use case overall. Everything related to a use
case would be described here.
4.5.1.5 Login
Use Case Name: Login
Summary: Administrator and user can log in to their respective panels to use their
relative services.
Actor: Administrator and user
Precondition: The System is launched and Login page is waiting to get login details.
Post condition: After the Successful login operation Users will be able to navigate to
their respective panels.
Description: Administrator and user will provide Id & Password so they can log in
to their relative Panels.
Exceptions: If User will provide wrong Login information JPK will deny the access
showing an error message of invalid username and password.

Table 3 Use Case Description for User Login

4.5.1.6 Logout
Use Case Name: Logout
Summary: Administrator and User can log out of their respective panels after
using their relative services.
Actor: Administrator and User
Precondition: The System is launched and Administrator or User is having some
JPK service from their respective panels.
Post condition: After the Successful logout operation Users will navigate to the
Home Page of the system with general services available for all.
Description: Administrator and End User will click on the “LOG OUT” button
after completing their sessions; will be closed.
Exceptions: Exit: If the Administrator or User presses the exit or ALT+F4 before
clicking on the Log Out button, system will be closed.

Table 4 Use Case Description for User Logout

1.1.1.1.1
15
4.5.1.7 Add Record
Use Case Name: Add Record
Summary: The administrator will login and from menu bar he can add any type
of Data.
Actor: Administrator
Precondition: The admin will be on admin panel main page for using the option of add
new from the navigation menu.
Post condition: After the Successful insertion operation Users will be prompted
with a success message, and returned to the Home Page of the Admin
Panel.

Description: First the user will log in and he will be on the main screen of the
admin panel, from there he can select the “insert a new data” option
and will navigate through different form inserting data into mandatory
fields as guided by the interface being provided to him, a new data
will be inserted into the database of JPK.

Exceptions: Wrong user name or password: If the Administrator enters a wrong

password or user name the systems will ask for valid user name and
password.
Canceled: If the Administrator presses the cancel button instead of
submitting details of the new License processing will be stopped.
Missing Field: If the Administrator leaves some mandatory fields
empty, system will ask him to enter data in all mandatory fields.
Sign Out: If Administrator presses the sign out button during entering
the data about the new license to be stored, the insertion will fail and
system will return back to its general main page.
Back to main menu: If the Administrator presses the back to main
menu button without entering the details to be stored, system will
return to main menu cancelling the insertion operation.

Table 5 Use Case Description for Adding Record

16
4.5.1.8 Delete Record
Use Case Name: Delete Record
Summary: Administrator will login from the admin view and then delete a record.
Actor: Administrator
Precondition: The system will ask for login first, to enter main menu and there should
be records on the database to be deleted.
Post condition: Message will be shown record deleted successfully.
Description: Administrator will have the authority to delete a record but there will
be a constraint or password that is escaped from the administrator.
Exceptions: Wrong user name or password: If the administrator enters a wrong
password or user name the systems will ask for valid user name and
password.
Sign Out: If the administrator enters the sign out button without
entering the CNIC number to delete a record, the system will return
to login form

Table 6 Use Case Description for Deleting Record

4.5.1.9 Search job

Use Case Name Search for job
Summary User can search for any job.
Actors End user
Pre-conditions The End user open the page .He will be on home page.
Post condition The End user will click on search button .He will asked for job search. He
can search specific job.
Description The end user can search any job in any area or city
Expectation Leave page: If an End User presses the Leave page button without
entering the search for job, the system will return back to main page.
Incorrect data: If the administrator enters the incorrect data a message will
be displayed, record does not exist.

Table 7 Use Case Description for Search job

17
4.5.1.10 Add job
Use Case Name: Add job
Summary: End User can add any type of job after log in.
Actor: End User
Precondition: End user will be on home page after log in.
Post condition: After login, End User add new job by filling the form of add job.
He will putt all detail on form.
Description: Only registered user can add a job after log in to system. Other user
Can add job without registration.
Exceptions: Wrong user name or password: If the administrator enters a
wrong password or user name the systems will ask for valid
User name and password.
Missing Field: If the End left the form fields empty, system will ask
For entering that field.

Table 8 Use Case Description for Add job

4.5.1.11 Apply job

Use Case Name Apply for job

Summary The end user can apply for a specific job.

Actors End user

Pre-conditions End Users will be on main page. He will asked for apply job.

Post condition End user will click on apply for job button .Then he will be able for apply
a specific job.

Description End user will be able for apply for job.

Expectation Leave page: If End User presses the Leave page button without entering
the apply for job, the system will return back to main page. Missing Field:
If the administrator or end user left the any mandatory field empty,

Table 9 Use case Description for Apply job

18
4.5.1.12 Submit CV
Use Case Name Submit CV

Summary End user can submit his CV for a job.

Actors End user
Pre-conditions End user apply for a job and he ask for submit CV.

Post condition End user will click on CV submit button. End user will get a form for
filling.
Description End user can submit CV for specific job. The CV form is available on
portal.
Expectation Missing Field: If the user left some fields empty, system will ask for
entering all the fields.
Back: If user presses the back button in the browser he will return to the
home page. Browser Closed: If user closes the browser unintentionally
then he will have to open the browser again to send a query.

Table 10 Use case Description for Submit CV

4.5.1.13 Add user

Use Case Name: Add user
Summary: Administrator will login to the admin panel and add new user in portal.
Actor: Administrator
Precondition: System will ask for Add new user.
Post condition: Admin will log in to system and add new user by user name and password.
Description: The Administrator will login to the system and add new user to the
system that ask for adding Admin will save name of new user in
system database.
Exceptions: Wrong user name or password:
If the administrator or operator enters a wrong password or user name the
systems will ask for valid user name and password.

Table 11 Use Case Description for Add new user

19
4.5.1.14 Alert
Use Case Name: Alert
Summary: The administrator will login and give alert the user about new jobs and
other.
Actor: Administrator
Precondition: System will ask the admin to give alert the user for new adding.
Post condition: Admin will ask for give alert the user.
Description: The administrator will login and give alert the user for their related job
or alert them if they are selected for job.
Exceptions: Wrong user name or password:
If the administrator or operator enters a wrong password or user name
the systems will ask for valid user name and password.
Browser Closed:
If the administrator unintentionally closes the browser administrator will
have to open browser again to add news.
Sign Out: If Administrator or operator presses the sign out button
without entering the news title or detail the system will return back to
user side.

Table 12 Use Case Description for Alert

4.5.1.15 Remove user

Use Case Name: Remove user
Summary: Admin will remove the user who miss use the portal.
Actor: Admin
Precondition: Admin check the user who miss using the portal.
Post condition: Admin remove the user.
Description: Admin will log in to the system .Check the user who don’t follow the
rules or miss use portal.Admin will remove that user.
Exceptions: Browser Closed:
If the administrator unintentionally closes the browser administrator
will have to open browser again to add to an application.

Table 13 Use Case Description for Remove user

20
4.6 Sequence Model
The sequence model elaborates the themes of use cases. There are two kinds of sequence
models: scenarios and a more structured format called sequence diagrams.
4.6.1 Scenarios
A scenario is a sequence of the events that occurs during one particular execution of a
system such as for a use case. The scope of a scenario can vary; it may include all events in the
system or it may include only those events impinging on or generated by certain objects. A
scenario can be the historical record of executing an actual system or a thought experiment of
executing a proposed system.
A scenario can be displayed as a list of text statements. A scenario contains messages
between objects as well as activities performed by objects. Each message transmits information
from one object to another.
4.6.2 Sequence Diagrams
A sequence diagram shows the participants in an interaction and the sequence of
message among them. A sequence diagram shows the interaction of a system with its actor to
perform all or part of a use case.
Each use case requires one or more sequence diagrams to describe its behavior. Each sequence
diagram shows a particular behavior sequence of the use case.
Scenarios for our system i.e. JPK are given below and also their related sequence diagrams are
also presented below each of the scenario.
Sequence diagrams are start from figure no. 4 to figure no. 13.

21
 User will request for login.

Login Form will validate user from

database. Database validates user.

Secure communication starts for administrator.

:USER :SYSTEM :DATABASE

Enter user name and password

Verify user

User verified

Secuire communication

Figure 4 Use Case Diagram for Login

User will request for Signup

System will show signup form to user
User will fill the form
User will signup successfully
User detail will be saved into Data base

:USER :SYSTEM :DATABASE

Request for Signup

Allow user to signup

Fill Signup form

Checking any field not NULL

Save Record

Save to Database

Show to User

Figure 5 Scenario and sequence diagram for Signup

22
 User will request for log out for

Data base will verify user

User will be log out successfully

:USER :SYSTEM :DATABASE

Click on logout

Verify user

Secuire communication

Log outed user

Figure 6 Scenario and Sequence Diagram for Log out

Admin request for add data

Ask for which type of data
Data save in data base successfully

:USER :SYSTEM :DATABASE

Request for adding record

show Portfolio

Fill Portfolio

Checking any field not NULL

confirmed

Save Record in database

Record saved

Show to User

Figure 7 Scenario and Sequence Diagram for Add record

23
 Admin will ask for show record.
Database give access to record.

Data base send conformation message

Data will be deleted from data base

:USER :SYSTEM :DATABASE

Show Record

Give acess to record

Confirmed Message

confirmed Deletion

Delete from Database

confirm Deletion

Show to User

Figure 8 Scenario and Sequence Diagram for Delete data

User put the job name for search

Database check job list
Database show job to user

:USER :SYSTEM :DATABASE

Job name

Request to database

Show list

Show to User

Figure 9 Scenario and Sequence Diagram for Search job

24
 User put the job title System Save it to Database
System.
show message to user

:USER :SYSTEM :DATABASE

job title

save in job list

job added

Show to Message

1.1.1.2 Figure 10 Scenario and Sequence Diagram of Add job

End user will request for apply job.

End user will ask for job type.
Data base show job list.
End user applied for job.

:USER :SYSTEM :DATABASE

Job type

Job list

Job name

Applied

Save to Database

Show Message to User

Figure 11 Scenario and Sequence Diagram for Applying for Job

25
 Admin will save name and password
of user in database.

:Admin :SYSTEM :DATABASE

Give password for the user

Save to Database

Figure 12 Scenario and Sequence Diagram for Add user

4.6.3 Activity Diagram

An activity diagram shows the sequence of steps that make up a complete complex
process, such as an algorithm or workflow. An activity diagram shows flow of control, similar
to a sequence diagram, but focuses on operations rather than on objects. Activity diagrams are
most useful during the early stages of designing algorithms and workflows.
Below a list of activity diagrams for JPK is provided which are explaining the workflow
for different operations of JPK.
Activity diagrams are start from figure no. 14 to figure no. 25.

26
 Get detail

[Unsuccessful]

[Successful]

Login out from system

Figure 13 Activity Diagram for log in

27
 Log Out

Log out sucessfuly

Log out from system

Figure 14 Activity Diagram for log out

1.1.1.3

Login

[unsuccessful]

[Successful]

Add record

[unsuccessful]

[Successfuly added]

Save to Database

Figure 15 use case add record to JPK

28
 Login

[Unsuccesful]

[Succesful]

Delete record

[Unsuccesful]

[Succesfully deleted]

Remove from database

Figure 16 Activity Diagram for Delete record

29
 Login

Search job

[Unnsuccessful]
Job Name/Type

[Successfull]

Display job

Figure 17 Activity Diagram for Search job

30
 Login

[Unsuccessful]

[Login Successfuly]

Add job

[Unsuccessful]

[Successfuly Added]

Save to Database

Figure 18 Activity Diagram for Add job

31
 Login
[Unsuccessful]

[Login Successfuly]

Apply job

[Unsuccessful]
Job Type/Name

[Successfuly Apply]

Display job

Applied

Figure 19 Activity Diagram for Apply job

32
 Login

[Unsuccessful]

[Successful]

Submit cv

[Unsuccessful]

[Submit Successfully]

Save to database

Figure 20 Activity Diagram for Submit CV

33
 Login

[Unsuccesful]

[Login Successfully]

User name

Remove user

[Unsuccesful]

[Removed Successfully]

Figure 21 Activity Diagram for Remove user

34
 Request for Signup

[unsuccessful]

[Successful]

Add Detail

[unsuccessful]

[Successfuly added]

Save to Database

Figure 22 Activity Diagram for Signup

Log in

[Record not found]

[Login Unsuccessfully]

Show record to send email alert

[Record not found]

[Record founded]

Show record

Send Email alert

Figure 23 Activity Diagram of alert

35
4.7 Logical Schema
Logical database design is the process of transforming the conceptual data model into
a logical data model. The logical model we will use is object data model. It represents data in
the form of tables/relations.
4.7.1 Relation
A relation is a named, two-dimensional table of data. Each relation (or table) consists
of a set of named columns and an arbitrary number of unnamed rows. An attribute is a named
column of a relation. Each row of a relation corresponds to a record that contains data (attribute)
values for a single class.
Primary key is an attribute or a combination of attributes that uniquely identifies each row in
a relation.
Foreign key is an attribute (possibly composite) in a relation that serves as the primary key of
another relation.
4.7.2 Associating Tables
During logical design, we transform the class diagram that was developed during
conceptual design into relational database schemas. The inputs to this process are the class
diagram and the outputs are the relational schemas.
Regular tables are classes that have an independent existence and generally represent
real-world objects, such as persons and CV. Each regular table type in a class diagram is
transformed into a relation. The name given to the relation is generally the same as the table
type. Each simple attribute of the table type becomes an attribute of the relation. The identifier
of the table type becomes the primary key of the corresponding relation.

36
 Person
-person_name
-cnic
-gender
-contact_no
-email
-address
-qualification
-experience
-
+Login()
+Logout()
Employer +search()
-designation candidate
-institution_name -marital_status
-institution_address Admin -DOB
-website -occupation
+addJob() +closeJob() -reference1
+signup() +approve() -reference2
+selectCandidate() +putCV()
+searchJob()
+applyJob()
+signup()

Person

Employer:

Candidate:

Admin:

Figure 24 Mapping between candidate and admin Classes

37
 Employer
-designation
-institution_name
-institution_address
-website
+addJob()
+signup()
+selectCandidate()

Job
-job_title
-institution_name
-requiredExperience
-jobLocation
-lastDate
-gender
-ageLimit
-jobType
-NoOfSeats

Employer:

Job:

Figure 25 Mapping between employers and job Classes

38
4.8 Database Diagram
Following is the database diagram

Figure 26 Database Diagram for JPK

39
 5 Chapter 5

System Implementation

5.1 Signup:
The implemented code for User Sign up interface panel shown in figure 29 and implemented
coding is given below:

Figure 27 JPK Login Panel

Coding

<!DOCTYPE html>
<html lang="en">
<head>
<title>Online Job Portal</title>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet"
href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
<style>
/* Remove the navbar's default margin-bottom and rounded borders */

40
 .navbar {
margin-bottom: 0;
border-radius: 0;
}
<footer class="container-fluid text-center">
<p>Copy Right 2017. All rights reserved.</p>
</footer>

</body>
</html>
5.2 Add Job
The implemented code for User Add Job interface panel shown in figure 30 and implemented
coding is given below:

Figure 28 JPK Add job panel

Code

<?php
require_once './includes/employer_session.php';
$errors = [];
$missing = [];

if (isset($_POST['add_job'])) {
$expected = ['job_title', 'institution_name', 'degree', 'subjects', 'req_exp', 'job_loc',
'last_date', 'gender', 'age_limit', 'duty_time', 'job_type', 'no_of_seats', 'sel_proc', 'job_spec'];
$required = ['job_title', 'institution_name', 'degree', 'subjects', 'req_exp', 'job_loc',
'last_date', 'gender', 'age_limit', 'duty_time', 'job_type'];
if (!isset($_POST['duty_time'])) {
$_POST['duty_time'] = '';
}
?>
>both</label>
</div>

41
 </fieldset>
<div class="form-group">
<label for="job_spec">Detailed Job Specifications (Optional):</label>
<textarea class="form-control" name="job_spec" rows="5"
id="job_spec"></textarea>
</div>

<button type="submit" name="add_job" value="add" class="btn btn-primary">

<span class="glyphicon glyphicon-plus-sign"></span> Add</button>

</form>
<?php } ?>
<!-- 00000000000000 -->
</div>
<div class="col-sm-2 sidenav">
<img class="img-responsive img-thumbnail" src="./images/emp5.jpg" alt="">

<img class="img-responsive img-thumbnail" src="./images/emp10.jpg" alt="">

</div>

</div>

</div>

<footer class="container-fluid text-center">

<p>Copyright &copy; Online Job Portal 2017</p>

</footer>

</body>

</html>

5.3 Apply Job

42
The implemented code for User Apply Job interface panel shown in figure 31 and
implemented coding is given below:

Figure 29 JPK Add job panel

Code
<?php
require_once './includes/candidate_session.php';
if (isset($_POST['apply_job'])) {
require_once './includes/process_apply_job.php';
}
/* require_once './classes/candidate.class.php';
$candidate_id = 3;
$data['candidate_id'] = $candidate_id;
$candidate = new Candidate($data);*/
?> <th scope="row">Total Vacancies</th>
<td><?= $job->no_of_seats; ?></td>
</tr>
<tr>
<th scope="row">Selection Procedure</th>
<td><?= ($job->sel_proc == 'both') ? 'Test & Interview Both' : $job->sel_proc;
?></td>
</tr>
<tr>
<th scope="row">Job Specifications</th>
<td><?= $job->job_spec; ?></td>

43
 </tr>
</tbody>
</table>
<?php if (isset($_REQUEST['applyBtn'])) { ?>
<form method="post" action="<?= $_SERVER['PHP_SELF']; ?>">
<input type="hidden" name="job_id" value="<?=$job_id;?>">
<p><button type="submit" name="apply_job" value="apply_job" class="btn btn-
info"><span class="glyphicon glyphicon-ok"></span> Apply Now</button></p>
</form>
<?php } ?>
<?php }
if (isset($_REQUEST['apply'])) { ?>
<form method="post" action="show_applications.php">
<input type="hidden" name="job_id" value="<?=$job_id;?>">
<button type="submit" name="show_applications" value="show_applications"
class="btn btn-success"><span class="glyphicon glyphicon-check"></span> Show
Applications</button>
</form>
<?php } ?>
<?php } ?> <!-- 00000000000000 -->
</div>
<div class="col-sm-2 sidenav">
<img class="img-responsive img-thumbnail" src="./images/job22.jpg" alt="">
<img class="img-responsive img-thumbnail" src="./images/job20.png" alt="">
</div>
</div>
</div>
<footer class="container-fluid text-center">
<p>Copyright &copy; Online Job Portal 2017</p>
</footer>
</body>
</html>

44
 6 Chapter 6

Testing and Evaluation

Testing is the one step in the software engineering process that could be viewed as destructive
rather than constructive. Testing requires that the developer discard preconceived notions of
the “correctness” of the software just developed and overcome a conflict of interest that occurs
when errors are uncovered. If testing is conducted successfully, it uncovers errors in the
software. As a secondary benefit, testing demonstrates that software functions appear to be
working according to the specification. Testing provides a good indication of software
reliability and some indication of software quality as a whole. Testing cannot show the absence
of defects, it can only show that software defects are present.
6.1 Testing Objectives
 To execute a program with the intent of finding an error.
 To uncovers an undiscovered error.
6.2 Testing Principles
 All tests should be traceable to end user requirements.
 Tests should be planned long before testing begins.
 Testing should begin on a small scale and progress towards testing in large.
 Exhaustive testing is not possible.
 To be most effective testing should be conducted by an independent third party.
6.3 Testing Approach
The choice of test approaches or strategies is one of the most powerful factors in the
success of the test effort and the accuracy of the test plans and estimates. This factor is under
the control of testers and test leaders.
6.4 Box Approach
The primary objective for test case design is to derive a set of tests that has the highest
livelihood for uncovering defects in software. To accomplish this objective two different
categories of test case design techniques are used.
They are:
 White box testing.
 Black box testing.

45
6.4.1 White-Box testing
White box testing focuses on the program control structure. Test cases are derived to ensure
that all statements in the program have been executed at least once during testing and that all
logical conditions have been executed.
6.4.2 Black-Box testing
Black box testing is designed to validate functional requirements without regard to the
internal workings of a program. Black box testing mainly focuses on the information domain of
the software, deriving test cases by partitioning input and output in a manner that provides
through test coverage. Incorrect and missing functions, interface errors, errors in data structures,
error in functional logic are the errors falling in this category.
6.5 Testing Levels
Tests are frequently grouped by where they are added in the software development process
6.6 Unit testing
Unit testing, also known as component testing refers to tests that verify the functionality of
a specific section of code, usually at the function level. These types of tests are usually written
by developers as they work on code (white-box style), to ensure that the specific function is
working as expected
6.7 Integration testing
Integration testing seeks to verify the interfaces between components against a software
design. Integration testing works to expose defects in the interfaces and interaction between
integrated components (modules). In this project integrating all the modules forms the main
system. When integrating all the modules we have checked whether the integration effects
working of any of the services by giving different combinations of inputs.
6.8 System testing
System testing tests a completely integrated system to verify that it meets its requirements.
 The application is easy to maintain.
 The application is fast and takes less memory space.
 The application is easily usable by the intended user.
6.9 Testing Types
There are many types of testing some of them are:
 Alpha Testing
 Beta Testing
 Regression Testing

46
6.9.1 Alpha Testing
Alpha testing is simulated or actual operational testing by potential users/customers or
an independent test team at the developers site. Alpha testing is often employed for off the shelf
software as a form of internal acceptance testing, before the software goes to beta testing.
During alpha testing of our project we find following minor errors and solve them.
6.9.2 Beta Testing
It is also known as field testing. It takes place at customer’s site. It sends the system to
users who install it and use it under real-world working conditions. A beta test is the second
phase of software testing in which a sampling of the intended audience tries the product out.
6.9.3 Acceptance Testing
Acceptance testing is performed by the customer on their own hardware, also called
user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off
process between any two phases of development. In this project we have checked by sending
and receiving data and tested whether project is working correctly or not.
6.9.4 Usability Testing
Usability testing is needed to check if the user interface is easy to use and understand.
It is concerned mainly with the use of the application.
6.10 Test Cases
Test cases are derived to ensure that all statements in the program have been executed
at least once during testing and that all logical conditions have been executed. Using White
Box testing methods, the software engineer can drive test cases that
Guarantee that logical decisions on their true and false sides.
 Exercise all logical decisions on their true and false sides.
 Execute all loops at their boundaries and within their operational bounds.
 Exercise internal data structure to assure their validity.

47
6.10.1 Test Case 01: Signup
ID 01

Name Signup

Brief Description Used to sign up to the system

Expected Input First Name, Last Name, User Name, Email, Password,

Re-type Password

Alternate flow of Events Invalid password, email, first name

Pre-Condition Register

Post Condition Logged In

Actor User

Status Pass

Table 14 Test Case Name Signup

6.11 5.11.2 Test Case 02: Login

ID 02
Name Login
Brief Description Used to login to the system
Expected Input User Name, Password
Expected flow of Events 1. Enter User name. 2. Enter Password. 3. Press “Login”.
Alternate flow of Events Invalid user name or password
Pre-Condition Signup
Post Condition Logged in
Actor User
Status Pass

Table 15 Test Case Name Login

48
6.11.1 Test Case 03: Add Job
ID 03
Name Add job
Brief Description Used to add a job in the Portal
Expected Input Job title, Organization, minimum qualification, select
degree, subject, experience required, Last date, Job type,
Gender, Age limit, Duty timing
Expected flow of Events Job title 2. Organization 3. minimum qualification
4. Select degree, 5. Subject, experience required 6. Last date,
7. Job type, 8.Gender 9. Age limit 10. Duty timing 11.Click “save”

Alternate flowof Events User Quits/Enters Incomplete information

Pre-Condition Login into Job portal

Post Condition Job added
Actor User
Status Pass

Table 16 Test Case Name Add Job

6.11.2 Test Case 04: Search Job

ID 04
Name Search Job
Brief Description Used search job on Jobs Portal
Expected Input Job title, Organization, experience required, Job location, Who
can apply, Age limit, Job nature, Job type,
Alternate flow User Quits/Enters Incomplete information
of Events
Pre-Condition Login into Job portal
Post Condition Job Searched

Actor User

Table 17 Test Case Name Job search

49
 7 Chapter 6

Future Extension

7.1 Conclusion
The following conclusions and future extensions can be deduced from the
development of the project: It provides a friendly graphical user interface which proves to be
better when compared to the existing system.
• It gives appropriate access to the authorized users depending on their permissions.
• System security, data security and reliability are the striking features.
• The System has adequate scope for modification in future if it is necessary.
• The system is designed in such a way that future modifications can be done easily.
• it can easily be extended to include other relating applications.
The proposed system is built successfully and it performs according to the requirements
specified in the requirements specification document. System is satisfactorily tested with
example data, it provides intended results. It is found to be bug free as per the testing standards
that are implemented.
At the end of this project; it will be easy to seek for job. People can find job about
their skills and apply for job online.Employe can put their job title and require
qualification on this portal. They can select the candidate and inform them .People
can search job of different title. People of district Kotli can apply and seek job
from any place within the district.
7.2 Future Improvements
As it’s an emerging era so changes according to emergent requirements can easily be
made and maintained. Since organization systems and the business environment undergo
continual changes, the information system should keep place.
As this system is computerized and a database is also maintained with it so in near
future it can go well with large amount of data.
This system being web-based and an undertaking of Cyber Security Division, needs to
be thoroughly tested to find out any security gaps.

50
7.3 Limitations
• Internet connectivity is required to get benefits of this system for all end users.
• People who’re going to operate this system need to know the basic uses of computer.
• Users and administrator advanced computing machine which can open a web site.
• It is also a problem for organizations that how they advertise their jobs and find a good
worker for a specific job.
• There is no easy way for seek and apply job in district kotli. To find an appropriate job
there is need of a Job Portal for District Kotli.

51
 Appendices and References
Appendices
These should provide detailed, specific information that is related to the application
being developed; for example, hardware and database descriptions. Hardware requirements
define the minimal and optimal configurations for the system. Database requirements define
the logical organization of the data used by the system and the relationships between data.
[Sommerville-2009]
Glossary
Below a small list of possible abbreviations and definitions used in this document is

presented:

JPK: Job Portal Kotli.

Admin: It holds the data for admin of the system who’ll operate mainly with the system

Using all of its services by having a user name and password for it

End user: a person who use portal for apply, add and search job.

CNIC: Computerized National Identity Card, used to uniquely identify each person of the

country.

Preconditions: The state of the system before an operation.

Post Conditions: The state of the system after an operation.

Exceptions: Erroneous and unusual situation in a process or operation.

Markup Languages: Web programming Technologies like HTML, CSS, PHP etc.

Query Language: Language for relational databases.

52
 References

[1] https://w3layouts.com/[Access Date: june-2017 ]

[2] Jeffrey A. Hoffer, V. Ramesh, HeikkiTopi.Modern Database Management. 10. s.l.: Prentice
Hall, 2010. 0136088392[Access Date: june-2017 ]
[3] Ian Summerville. Software Engineering. 8. Publisher: Edison Wels Publishing.[Access
Date: May-2017 ]
[4] Michael Blaha, James Rumbaugh. Object Oriented Modeling and Design with UML.
Second. Prentice Hall India, 2007. 978812033016[Access Date:June-2017 ]
We also take help from the following books and web Sites for the software engineering and
development of this project.

Book Name: Object Oriented Modeling with UML 2.0

Author: Michael Blah

Book Name: Software Engineering

Author: Ian Somerville
FOR DEPLOYMENT [Access Date: July-2017]
http://php.net/manual/en/mongo.queries.php
http://www.w3schools.com
http://www.codeguru.com/
http://www.cssdesignawards.com/
FOR WampServer [Access Date:July-2017]https://sourceforge.net/projects/wampserver/
FOR JavaScript [Access Date:july-2017 ]

53