Journal of Science and Sustainable Development

Solid State Technology 
Volume: 63 Issue: 6 
Publication Year: 2020
19670
Archives Available @ www.solidstatetechnology.us 
In addition to the constructor, the Analyzer object has methods: getCase() that will return the case, 
getTree() returns the analyzing tree, getDIT() returns the direct influence topics, getIIT() returns the indirect 
influence topics, getValue() returns the value, and update() to reevaluate the significance values and returns 
the new value. The Analyzer object is serializable and can be saved and reconstructed from the Storage.
The last object is the Exhibitor. As its name suggests, it is the object that shapes the Analyzer in a 
meaningful form for the user. To understand the Exhibitor, we need to have a look at some objects that inherit 
it. Charts builder, dashboards, reporters, alerts, synthesizers, and print spoolers are examples of Exhibitor 
objects. The Exhibitor has a single attribute which is the case Analyzer objects and it is set in the constructor. 
It has two main methods: summarize() which return a summary of the Analyzer as the following: The case, 
its state, the major effecting factors, DIT, and IIT. The other method is reveal() which renders the exhibitor 
According to its output type. The end Exhibitor object might implement a descriptive object which will need 
no more methods. It might be an analytical object like an Advisor object where it will use the Analyzer to 
conclude the affective topics and advise to work on modifying the most significant topics. An advisor object 
is an object that implements decision support techniques and applies it to the Analyzer object. It is applicable 
to be extended to the other objects the Exhibitor supports. 
With this, we come out with the finalUABI model revealed in Figure 5. 
<>
Information
content
topic
<>
Storage
<>
Retriever
retreive(Information)->Information
<>
Analyzer
case
constructor(case)->Analyzer
<>
Exhibitor
Analyzer
summarize()->summary
<>
Advisor
conclude()
keywords
value
weights
consturctor(topic)->Information
appendContent(content)->content
setWeight(keyword,weight)->weight
getValue()->value
keep(Information)->Information
replace(Information)->Information
provide(topic)->Information
value
tree
significanceThreshold
getCase()->case
update()
getTree()->tree
getIIT()->topic list
getDIT()->topic list
getValue()->value
reveal()
Figure 5UABI model diagram 
With good understanding to the model, we find that the user will interact with BI application while the 
application will handle contacting the model. The application implements an exhibitor object or translate one 
into the form that serve the goal of the application. This propose the following scenario in Figure 6as a 
routine scenario for UABI implementing application. 

---