IV. RCSES DEVELOPMENT
The development of the proposed RCSES system includes the development of different sub-systems. Fig.4 shows the block diagram of the entire proposed system RCSES. 

The following section describes the different sub-systems in the proposed RCSES system as well as its functionality in the proposed system RCSES: 
1. The knowledge builder unit: Developed to enable the expert or knowledge engineer to enter and save domain ontology and domain rules in an efficient and easy way. 

2. The morphological analyzer unit: Developed to check if the entered words or sentences in the domain model rules are found in the ontology stored in the knowledge base or not; to avoid the unwanted reasoning results or the results concluded due to the user inputs errors and mistakes. 

3. Web page interface of the proposed RCSES system: For using purposes includes entering ontology, knowledge, and the use of the expert system by entering the questions and get the output results with reasoning too. 

4. The entire control and operation of the system is done by the inference engine; that is developed using Visual 

(IJCSIS) International Journal of Computer Science and Information Security, 

![0_image_0.png](0_image_0.png)

structure that relates given information or facts in the IF part to some action in the THEN part. A rule provides some description of how to solve a problem. Rules are relatively easy to create and understand. Any rule consists of two parts: 
the IF part, called the antecedent (premise or condition) and the THEN part called the consequent (conclusion or action). 

The basic syntax of a rule is: IF *<antecedent>THEN* 
<consequent> . The rules in XML format have a different structure with the previous meaning but in different format. 

Sample of rule built in the proposed RCSES is shown in Fig.3; it can be interpreted as following: 
1. <KSA_Civil_Regulation>; represents the total regulations' in the domain of the civil regulations. 

2.The node of "Model" represents a regulation data and has attribute "ModelName" its value takes the regulation name as 
 ."إنھـاء الخـدمة" 3.The child nodes "Rule" represent the decision rule for each part in regulation; takes R1, R2,…and so on. 

4.The node attribute "RegItem" represents the consequent in the selected rule in the regulation. 

5.The node "Finding" represents antecedent in the rule. 

6.The condition equal to attribute "Cpt" value as concept, attribute 
"Prop" value as property, and attribute "Val" value as value. The condition for example equal to separation "الاستقالة =الاستقالة تقدیم ."وقبولھا The proposed system RCSES, developed a tool component to build the domain model rules for the acquired knowledge in an efficient, easy, and dynamic way for changing and/or modifying the rules as required. 

![0_image_1.png](0_image_1.png)

Basic dot net (VB.NET); which handles the knowledge in format of XML to get the result from the XML file 
(Knowledge base) that stores the knowledge rules. Fig. 5 shows the block diagram of inference engine. The main roles of the inference engine are summarized as: It applies the expert domain knowledge to what is known about the present situation to determine new information about the domain. The inference engine is the mechanism that connects the user inputs in the form of answers to the questions to the rules of knowledge base and further continues the session to come to conclusions. This process leads to the solution of the problem. The inference engine also identifies the rules of the knowledge base used to get decision from the system and also forms the decision tree. 

## A. Reasoning Mechanism

The reasoning mechanism consists of three main components namely: working memory manager (WM manager), XML matcher, and result browser. Fig.5 (a) 