In addition to asking questions from a page

[Arzina333]

The knowledge model has been added to the wiki using a semantic plugin . This means that when creating a page, you determine what type of content you are entering (a use case, actor, process, core system, etc.). The wiki then asks you what it wants to know about that specific piece of information; for a use case, this could be the goal, the reason, the result and the associated actors. Because in addition to text, the requested information can also consist of references to other information in the wiki. In this way, specific characteristics and mutual relationships are recorded per wiki page. By doing this, the system gains knowledge of the meaning of the information. This offers the possibility to draw the user's attention to cross-connections and related information, making it even easier to find your way and wander around in the information.

The wiki stores the semantic information together with the content of the wiki page in an underlying database. A special query language makes it possible to query this information from any wiki page. For example, a process page can ask: "To which core system do I belong? And in which main group do I fall?", or "Of which use cases do I consist?". The answer to these questions can be presented on the process page itself. In this way, as a user you always have an overview of how the uk phone data information on your screen relates to the rest of the wiki, no matter how deeply you have dug into the information.


This image is no longer available.


the recorded semantics also make it possible to ask questions across different pages. In this way, overviews can be quickly generated from the wiki that automatically change (along with) when the content of the wiki is modified. For example, a list of all use cases will automatically grow when more use cases are added to the wiki. More advanced overviews, in which filtering is done on properties and/or information from different pages is combined, are also possible. For example, you can create an overview of all actors involved in a random use case within a certain process, including the description of the relevant use case(s). The wiki will therefore actually behave more like a kind of database.