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

Class Name: Availability

Attributes:
Person-id: text

Current-Status: ethod(current-status)

Availability: Method(availability)

Methods:
Current-status(): text
{ Request(Personnel.Current-Status)}

availability(): text;
( IF Current-Status = “Vacancy”
THEN Availability = “yes”
ELSE Availability = “no” }

Class Name: Average-Grade

Attributes:
Person-id: text

Average-Mark: ethod(average-mark)

Average-Grade ethod(average-grade)

Methods:
Average-mark(): number
{ Request(Personnel.average-mark)}

Average-grade(): text;
( IF Average-Mark >= 80
THEN Average-Grade = “high”
ELSE IF Average-mark >= 50
THEN Average-Grade =“middle”
ELSE Average-Grade = “low” }

Fig. 8.14 Availability and average-grade active classes

After this, the developer can insert the synonym data into the IRDS. Table 8.5
shows the synonym part information of the IRDS for the IHRMS.
The processing flow for the coupling class method is:

IF the attribute is an output part of attribute
THEN IF the attribute has a synonym
THEN send message to the synonym object to retrieve
the data
ELSE ask users to input the data
ELSE execute the coupling module functions

The coupling module functions are a group of low level communication procedures,
e.g., RPC. Different systems will have different procedures.
The EDS is created as a result of the previous step and it consists of the integrat-
ed classes (static or active), coupling classes, source ES, and source DBS. When the
current EDS needs any information from the external existing systems, the frame
model metadata will execute a RPC function to trigger an interface program via