Database and Expert Systems Integration - Information Systems Reengineering, Integration and Normalization - page 322

Table 8.2 Personnel database subschema
Field Name Type Width

ID Character 8

Name Character 20

Age Number 2

Staff-Type Character 15

Directorate Character 20

Current-Status Character 15

Average-Mark Number 1

Skill-1 Character 20

Skill-2 Character 20

System (HRMS) ES and Table 8.2 only shows a part of the personnel database
subschema used by the EDS.
In this case study, the HRMS is to do the job-person matching. Its process in-
cludes the consideration of vacancy criteria, skills criteria, and staff's preferred next
work areas. As shown in Table 8.1 , the execution of a job-person match begins
with the matching process in vacancy criteria, which includes staff type (internal
or external), location, directorate, availability, and grade. Staff whose details match
vacancy details in these aspects will be selected from the database as first priority
group staff for further evaluation.
Staff selected as first priority group are then evaluated in their skill criteria. Each
vacancy skill is used to match those of staff's skill attainment, and each skill level
is checked if it meets the required level. During these processes, a skill qualification
point is calculated for each staff and then evaluated to decide whether this staff will
be selected as the candidate for this vacancy.
The third condition is to identify if this vacancy is one of the work areas that
have been recommended as staff's next moves, and also, if this vacancy is one of
staff's preferred next work areas. This information will be displayed together with
result explanations for users' reference in decision-making.
The development environment of this EDS example could be any of the three
cases as described above. In this case study, we assume that the situation is the case
3, which means the system will reuse an existing ES and an existing database. The
frame model metadata forms a communication bridge between the various subsystem.

8.4.1 EDS Development

Step 1. Knowledge Acquisition
In this step, the attributes of existing ES and DB must be analyzed. The EDS de-
veloper also must define the characteristics of each attribute. Table 8.3 shows a