You are on page 1of 4


4.1 Overview
This chapter discusses the system implementation phase: making the new system
available to a prepared set of users (the deployment), and positioning on-going support and
maintenance of the system within the transition. At a finer level of detail, deploying the
system consists of eecuting all steps necessary to educate the users on the use of the new
system, placing the newly developed system into convention, confirming that all data
re!uired is available and accurate, and validating that recruitment functions (for "ob seeker
or employer) interact with the system are functioning properly. Transitioning the system
support responsibilities involves changing from a system development to a system support
and maintenance mode of operation
4.2 System Se!i"i!#ti$%s
4.2.1 S$"tw#re Se!i"i!#ti$%s
#- $icrosoft %nternet &plorer ' with compatibility mode
(- )indows *+ ,+( as operating system (or higher)
4.2.2 H#r&w#re Se!i"i!#ti$%s
#- -omputer with a (.. megahert/ ($0/) processor or higher (+entium processor
(- 12 $3 4A$ $emory
.- #56 $3 47$ $emory
2- ,uper 89A ('66 166) or higher-resolution monitor with (51 colors
5- $odem or %nternet connection
1- $icrosoft $ouse, $icrosoft %ntelli$ouse
4.' C(#%)e$ver #%& Im*eme%t#ti$%
%t involves the transition or changeover from the old system to the new. The
preparation for this such as making sure the hardware and network infrastructure for a new
+ ', -
+repared by: 0end Abdullah Altenai"i ((66'(612), ;ahla Abdullah Al ,hehhi ((665(6(2), and <ubaidah Abdul 4ehman ((662(6'6)
+repared for: =r. ,elma &l-,heikh, 3%, %mplementation +ro"ect
system are in place> testing of the system and also human issues of how best to educate and
train staff who will be using or will be affected by the new system
The epected users "ob seekers and employers are epected to switch from traditional
recruitment to online recruitment system. This will undergo either one or any combination
of adoption strategies such as
+arallel: 4un old ? new systems for awhile to check validity.
+ilot: %nstall in one part of organi/ation at a time.
+hased: %n large system change one function at a time.
-utover: ,tart using entire system.
%t is safe for employer and "ob seeker to follow parallel strategy of changeover and
implementation. Therefore, they can use their traditional recruitment practices and at the
same time, make use of online recruitment system. @sers who do not have much
background about online recruitment system can implement piloting by implementing
partially. This way they will learn and adapt using @A& Aobs. ,imilarly, users who
implements cutover will be adopting @A& Aobs entirely. The operation side of @A& Aobs is
simple so training people or starting to use it will not be complicated. ,imilarly, @A& Aobs
will undergo implementation of maintenance whenever needed. @A& Aobs implementation
will help people to establish their needs and to measure its fulfillment. %t is designed to
help local and international "ob seekers or local employers
. %n order to introduce @A&
Aobs in an organi/ation or in the community, everyone should work together closely
According to figure 2..-#, it shows that even though @A& Aobs B online recruitment
system is implemented, there would be use of traditional recruitment practices.
+ 4. -
+repared by: 0end Abdullah Altenai"i ((66'(612), ;ahla Abdullah Al ,hehhi ((665(6(2), and <ubaidah Abdul 4ehman ((662(6'6)
+repared for: =r. ,elma &l-,heikh, 3%, %mplementation +ro"ect
Fi)/re 4.'+1: Fr$m C(#%)e$ver #%& Im*eme%t#ti$%
4.4 System 0eri"i!#ti$%
8erifying of the individual units : modules within the system (such as each page
checking whether it is valid and working).
-hecking various units : modules as they are pieced together within the system B
to eercise their interfaces (integration testing). This will be including checking
whether all the links and connecting )eb+ages are working.
-hecking of the entire system from end-to-end as it becomes possible (system
verifying). The overall @A& Aobs is checked and verified that under each page,
the functions are working and integrated or connected pages are error free.
4.1 P$st+Im*eme%t#ti$% Review2Ev#*/#ti$%
A post-implementation evaluation is based on fact-finding methods similar to
techni!ues used during the systems analysis phase
. A team meeting occurs after @A& Aobs
is operational to review the success of the pro"ect. The review could include the following
Haults and suggested enhancements with agreement on which need to be
implemented in a future release>
,uccess of system in meeting its budget and timescale targets>
,uccess of system in meeting its business re!uirements B has it delivered the
anticipated benefits described in the feasibility studyF
+ 41 -
+repared by: 0end Abdullah Altenai"i ((66'(612), ;ahla Abdullah Al ,hehhi ((665(6(2), and <ubaidah Abdul 4ehman ((662(6'6)
+repared for: =r. ,elma &l-,heikh, 3%, %mplementation +ro"ect
=evelopment practices that worked well and poorly during the pro"ect.
According to the post-implementation review:evaluation
, there were faults such as
errors in linked pages and registration process. The suggestions made during the meeting
were incorporated and issues were resolved. $oreover, it was epected delay in success of
the pro"ect due to issues of local browsing, which was also resolved. The benefits and
advantages determined are fully done and the @A& Aobs is enhanced from old graphic
design to better one. The system is fully reliable and accurate
+ 42 -
+repared by: 0end Abdullah Altenai"i ((66'(612), ;ahla Abdullah Al ,hehhi ((665(6(2), and <ubaidah Abdul 4ehman ((662(6'6)
+repared for: =r. ,elma &l-,heikh, 3%, %mplementation +ro"ect