Chapter 3: System Build

8/12/2019 Chapter 3: System Build

1/15

CHAPTER THREE: SYSTEM BUILD

3.1 Overview

This chapter covers system structure and website architecture of the UAE Jobs

build phase. The creation of UAE Jobs by team members involves programming andbuilding release versions of the online recruitment system and testing by team members

with later testing by potential users along with training, support and maintenance 1.

3.2 System Str!tre "#$ %e&site Ar!'ite!tre

According to 3.!1, it shows the system structure divided into four areas" public,

see#er, employer and $%%. Under public, there is search &ob, search candidate, register

employer, register &ob see#er and login features. These features are intended for the users.

%imilarly, under the see#er there is view &ob post and edit candidate profile. The employer

consists of view candidate profile, edit employer profile, and post new &ob. The website

architecture is shown in figure 3.!.

(i)re 3.2*1: %e&site Str!tre

1http"''f&doyle.dit.ie'(usiness)*+nformation)*%ystems)*slides'(+%)*1)*(uild,)*+mplement,)*aintain.ppt

! - !

repared by" /end Abdullah Altenai&i 0***2-, 4ahla Abdullah Al %hehhi 0**5*-, and 6ubaidah Abdul 7ehman 0**-**repared for" 8r. %elma El!%hei#h, (+% +mplementation ro&ect


2/15


(i)re 3.2*2: %e&site Ar!'ite!tre

3.3 System Pr+)r"mmi#) ,C+$i#)-

The system built is by using the language of $9.4ET using icrosoft :isual %tudio

**. The website was developed using icrosoft A%.4ET. A%.4ET is a dynamic web

development language that is integrated with icrosoft $9.4ET programming language. +n

A%.4ET the web page comes in the format of .A%; where the /T< and A% code are

written. A%; files contain references to the relevant $9 programming class that should be

e=ecuted along with the page. A% stands for Active %erver age technology that was

written by icrosoft in early ***. The web development language was developed to wor#

with icrosoft .4ET framewor# and $9. A%.4ET forces the code to be e=ecuted on the

server side based on the client side events such as button clic#s, Te=t $hange or selection

done2.

http"''en.wi#ipedia.org'wi#i':isual>%tudio>**9:isual>%tudio>**

! 5 !



3/15


4/15


A48 00JobTitles.Title4ame


5/15


N)H age TitleCOO


6/15


%elect$ommandTypeCO%toredrocedureOK N'asp"%?l8ata%ourceK N'tdK N'trK NtrK NtdalignCOrightOK Nasp"(utton +8CObtnAll+ndustriesO runatCOserverO Te=tCOAll +ndustriesO 'K N'tdKN'trK N'tableK N'tdK N'trK N'tableK N'divK N'asp"$ontentK

(i)re 3.3*: H+me P")e C+$i#)

H)Kage TitleCOO 8efaultfont" 1p= O%egoe U+O, Arial, sans!serifRcolor"

9333Rte=t!align" leftRV.7ad$ombo(o=>8efaultvertical!align"middleRV.7ad$ombo(o=>8efaultfont" 1p= O%egoe U+O, Arial, sans!serifRcolor" 9333R

te=t!align" leftRV.7ad$ombo(o=>8efaultvertical!align" middleRV.7ad$ombo(o=>8efaultfont" 1p= O%egoe U+O, Arial, sans!serifRcolor" 9333Rte=t!align"leftRV.7ad$ombo(o=>8efault W margin" *Rpadding" *RV.7ad$ombo(o=>8efault Wmargin"

*Rpadding" *RV.7ad$ombo(o=>8efault Wmargin" *Rpadding"*RV.7ad$ombo(o=>8efault .rcb+nput$ell8efault .rcb+nput$ell


7/15


.7ad$ombo(o=>8efault .rcb7eadnly .rcb+nputcursor" defaultRV.7ad$ombo(o=>8efault .rcb7eadnly .rcb+nputV

cursor" defaultRV.7ad$ombo(o=>8efault .rcb+nputfont" 1p= O%egoe U+O, Arial,sans!serifRcolor" 9333Rte=t!align" leftRV

.7ad$ombo(o=>8efault .rcb+nputfont" 1p= O%egoe U+O, Arial, sans!serifR

color" 9333Rte=t!align" leftRV.7ad$ombo(o=>8efault .rcb+nput Vfont" 1p= O%egoe U+O, Arial, sans!serifRcolor" 9333Rte=t!align" leftR.7ad$ombo(o=>8efault .rcbArrow$ell7ightV

bac#ground" url0mvwres"''Teleri#.Feb.U+, :ersionC**X.1.311.35, $ultureCneutral,ublicGeyTo#enC11faeM125ba3d-'Teleri#.Feb.U+.%#ins.8efault.$ombo(o=.rcb%prite.png no!repeatRV.7ad$ombo(o=>8efault .rcbArrow$ell7ightV

bac#ground" url0mvwres"''Teleri#.Feb.U+, :ersionC**X.1.311.35, $ultureCneutral,ublicGeyTo#enC11faeM125ba3d-'Teleri#.Feb.U+.%#ins.8efault.$ombo(o=.rcb%prite.png no!repeatRV.7ad$ombo(o=>8efault .rcbArrow$ell7ightV

bac#ground" url0mvwres"''Teleri#.Feb.U+, :ersionC**X.1.311.35, $ultureCneutral,ublicGeyTo#enC11faeM125ba3d-'Teleri#.Feb.U+.%#ins.8efault.$ombo(o=.rcb%prite.png no!repeatRV N'styleKN'asp"$ontentKNasp"$ontent +8CO$ontentO

$ontentlace/older+8CO$ontentlace/older1O runatCOserverOK Ntable styleCOwidth"1**)NORKtrK Ntd styleCOwidth" 15)OK Nasp"


8/15


$onnection%tringCON)S $onnection%trings"6


9/15


4avigateUrlCOP'Employer'[email protected]=OKN'asp"/yper


10/15


(i)re3..1*1: A$$ 9+& S!ree#

The employer will be adding &ob posting by entering this form as shown in figure

3.-.1!1. +t re?uests number of items that they employer should ma#e available before

posting a &ob. At the same time, the employer can search for potential candidates by

entering #eyword, and ma#ing selection of &ob titles, industry, ?ualifications, e=perience,

and s#ills as shown in the figure 3.-.1!3.

(i)re 3..1*2: A$$ Seeer S!ree#

! 33 !



11/15


The &ob see#er will be ma#ing their profile presence online by entering this form as

shown in figure 3.-.1!1. The &ob see#er should enter number of information to ma#e their

account. At the same time, the &ob see#er can also search for &obs based on #eywords,

location and sector as shown in figure 3.-.1!3.

(i)re 3..1*3: Se"r!' 9+& S!ree#

(i)re 3..1*: Se"r!' Seeer S!ree#

The system does not contain classic reporting features. 7ather, it contains ?uic#

statistics for both the see#er and employer. The system uses the home page to show the

statistics to all #ind of users including the anonymous one. The statistics that are shown to

users on home page are 0as shown in figure 3.-!1"

4umber of Jobs submitted in each emirate

4umber of Jobs submitted in each category

4umber of &obs submitted in each industry

4umber of &obs submitted by each employer.

! 3- !



12/15


The statistics are being collected immediately after successful completion of a

transaction. The system reports the search result as a tabular report in the same page for the

&ob see#er as shown in figure 3.-!. The final forms of reports are emails that are being

sent from the system in the following function points"

User submits a contact us en?uiry

Job %ee#er applies for a &ob.

(i)re 3.*2: User St"tisti!s

(i)re 3.*3: 9+& Se"r!' Re+rt

The user dialogs are built based on the system analysis in chapter two. The system

uses the same page to report the status of submitted re?uired function in figure 3.-!3.

(i)re 3.*: Seeer Re)istr"ti+# (+rm

! 35 !



13/15


The form depends on 1 inputs that are mapped directly to the database table

named Job%ee#er. The s#ills and ?ualifications are set as multiple selection dropdown lists

where the user can select multiple entries. The same design is done in multiple locations

such as &ob post that is shown in figure 3.-!-.

(i)re 3.*: 9+& P+st M/ti/e Se/e!ti+#

The employer registration has been designed to be separate as the function inputs

are much less than the inputs for the &ob see#er. The main input is the email id that the

employer can use as a login username. @igure 3.-!5 shows the inputs of the employer

registration.

(i)re 3.*4: Em/+yer Re)istr"ti+# (+rm

3. System C+#8i)r"ti+# Cst+mi;"ti+# "#$ Testi#)

! 32 !



14/15


The configuration conducted with setting and modifications of UAE Jobs build.

The new functionalities for Job %ee#er and Employer build and developed are allowing

customiation. The performance of UAE Jobs tested and evaluated3. The system is a

general system type. The website is not built to match the needs of most of employers and

&ob see#ers in United Arab Emirates. The generaliation comes from the following points"

7egistration is open for anyone

%earch is open for all visitors

Any registered employer can add a &ob

Any registered &ob see#er can apply for a &ob

Lualifications, %#ills and +ndustries are not limited to a specific sector or &ob.

3.4 Systems D+!me#t"ti+# Tr"i#i#) "#$ S+rt

The website has been documented from both technical and business re?uirements

side. @rom technical prospective, the system design has been documented to cover the

system entity relationship diagram, system search algorithms flow charts and coloring

design.

%ystem architecture is described using bloc# diagrams and conte=t diagrams. The

business logic of the system is documented in terms of documentation of the data

dictionary categoried by process. The data flow throughout the system is documented

using data flow diagrams to display the inputs and outputs of each component in the

system.

User screens are designed to elaborate the way the system wor#s. /ence, user can

use the documentation of system conversion in this chapter as well as the documentation in

of the screens design in chapter two for training. Users ?uestions can be received over the

information email as well as en?uiry submission in contact us page.

3 http"''higheredbcs.wiley.com'legacy'college'piccoli'*-M**M*3;'ppt'ch11.ppt

! 3M !



15/15


The system support will be done using regular chec# on the system deployment

server chec#ing the database sie. %ystem errors will be reported using the page of contact

us that is built in the system or throughout the information contact email that is displayed

in contact us page.

! 3 !


Chapter 3: System Build

Documents

Transcript of Chapter 3: System Build