Date: Fri, 29 Mar 2024 13:14:43 +0100 (CET) Message-ID: <711107991.119.1711714483999@web11-ede01.marin.local> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_118_124962926.1711714483997" ------=_Part_118_124962926.1711714483997 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
As mentioned for the classic knowledge based applications, the = necessity to have influence on the order in which input is requested and ca= lculations are made has resulted in the sc= enario based approach.
The main idea in the scenario = based approach is to use the reasoning mechanism to come to a solution, but= with a sequence or scenario of input steps and intermediate calculation st= eps to come to the total result. Furthermore, special attention is paid to = the coupling of the data set with the scenario solution. A user will always= select a data container (call it a "Ship" or "Transport") in combination w= ith the task to perform (which is the scenario for the process). All the in= put steps are stored in the data set and used for the calculations further = in the scenario.
In other words, a user can prepare much of= the required input for the calculations steps, without carrying out the ca= lculations yet. Furhtermore, this input can be requested in any layout and = sequence you want (so no unexpected questions will be asked due to the reas= oning process). And moreover, during calculation only missing information (= input, choices) will be requested because for every scenario goal Quaestor is still working in the classic way.
For the Knowledge = Engineer the approach= means that the calculations steps can be developed in the normal way and t= he overall process can be defined using the SCEN= ARIO$ function.
The advantage of the approach is clear, yo= u have better control over your total calculation process. There are howeve= r, also some disadvantages. The main disadvantage is that creating a smooth= scenario requires effort using a number of special attributes and constrai= nts. For this reason, Qnowledge continued developing improved methods to ac= hieve the same goals: combining the strength of reasoning with easy and fle= xible definition and control of the process. This has resulted in the Taxonomy or model/process configuration based approac= h. Not going into technical details, the biggest difference of the Taxonomy or model/process con= figuration based applications = span>is the ease of development and use.
Very powerful applications can be made on = the basis of the scenario approach. Examples are Sea Trial Analysis program= QSTAP of the STA-JIP and the speed-power prediction tool QDESP of MARIN. T= he QDESP knowledge base is also used on the internet as Web based application.
For more about the examples go to Scenario examples.