CHAPTER THREE
3.1 Preamble
SYSTEM ANALYSIS AND DESIGN
This chapter describes the workings and problems of the existing system, it also analyses the proposed system using various models and lastly gives us a sense of what the system design would entail. In the analysis phase we determine the functional and non-functional requirements of the system, the use case model is used to show how the users interact with the system, the data flow diagram shows how data is transformed and moves between processes in the new system while the E-R diagram depicts the systems various entities and their relationships. In the system design phase the functional hierarchical diagram serves as a kind of organogram for the system, the logic model of the system uses pseudo code to model the systems association rules, an activity diagram is used to show the high level processes within the system and lastly prototypes of the various systems interface is described in the ï¬nal sections of this chapter.
3.2 Description of the Existing Recruitment Management System
In the system currently in use at dragnet solutions when an organization engages dragnet solutions to recruit for its available vacancies dragnet starts out by placing advertorials in both electronic and print media calling for CV’s to fill the available vacancies. Qualified candidates are then then informed via e-mail of a screening with their test centres and date enclosed within. These candidates then have to make themselves available for the screening at appropriate time and place. This ensures that the hiring organizations do not have access to real time results but depend on reports sent to them by the recruitment agencies.
3.2.1 Analysis of the existing system
Here we would look at the problems and beneï¬ts of the existing system
3.2.2 Problems of the existing system
The main problem of the existing system is that it lacks transparency it gives room for a lot of back room deals to occur. Take for example someone who as o travel all the way from the north to a test centre in the south or south west only to be told he didn’t get the job because he doesn’t share the same faith as the C.E.O of the recruitment agency.
3.2.3 Beneï¬ts of the existing system
The existing system has the beneï¬t of being easy to use with little technical requirements required it also provides top notch security to data within the system due to its centralized nature.
3.3 Analysis of the Recruitment Management System
The new system aims to reduce the level of inconvenience experienced by job seekers it also provides real time access to results of aptitude test whilst providing an open repository available to external actors. The existing system fails to provide real time access to results with hiring organizations being dependent on reports generated by the recruitment agencies.
In this section and its corresponding sub sections we model the new system using models such as the use case model, the functional hierarchical Diagram, the context data flow diagrams, the level 0 and level 1 data flow diagrams whilst also stating the functional and non-functional requirements of the system.
3.3.1 System Requirements
The requirements needed by the system can be broken into two namely:
=> Functional Requirements
=> Non-Functional Requirements
3.3.1.1 Functional Requirements
These are the requirements that show what the system should do, they include the following
=> Input:
o Capture organizations details.
o Capture Candidates details.
o Schedule an exam.
o Capture questions and answers for the exam.
=> Processing:
=> Compare answers entered by candidate with answer set by organization.
=> Count the number of equal and unequal comparisons.
=> Process and store organizations details.
=> Mine available data to find patterns in candidate’s details and result.
=> Output:
=> Display result of exams taken.
=> Display result of data mining operation.
=> Generate various reports for the hiring organization (e.g. Report of results of an exam, Report of schools with highest score etc.)
=> Generate report of schools that produce the most qualiï¬ed candidates from mined data.
3.3.1.2 on-Functional Requirements
These are the attributes of the new system
=> Enable registered users take an aptitude test.
=> Use of passwords to prevent unauthorized access.
=> Provide users with real time access to results of aptitude tests taken.
=> Provide a repository which would be used to support managers in making decisions with respect to recruitment.