Requirement: Modeling Language

Textual Annotation

Purpose:

1. Model Re-use

The system shall enable (re)use of model-defined items (business terms, role names, process task names, etc.) in text-based contents.

It is difficult to keep textual contents consistent if we do not reuse model-based items.

2. Content - Semantic Search

The system shall guide users to relevant contents using semantic features (a search engine) to find appropriate contents.

As the learning experience is modeled in a sort of workflow, it should be useful for learners to jump directly to certain end or middle points of the BP, not considering the whole path.

3. Expert to Domain Classification

The system shall be able to classify the experts according to their contribution to the learning material (documents and BP models).

The classification of experts is useful to suggest experts to learners and to understand who can change the model of a procedure, or the wiki content of the same procedure, when change requests are issued by the community or by the regulations that are represented in the BP models and associated wiki pages.

Scope:

The scope of the implementation of the textual annotation at present includes

  • Import of externally generated RDF file containing annotation of model
  • Annotation of objects using user selection from imported list of annotations

In addition to these it is envisioned that the scope be extended to

  • A semantic search facility
  • Categorisation of experts to ease the change requests process

 

Target System:
ADOxx 1.3UL1

Functional Requirements Specification:

The modelling environment should allow for the import of a list of concepts so that these can be re-used in subsequent models.  In addition, it should be possible to search content using particular semantic features. The modelling environment should enable the use of semantic features. The modelling environment should have an expert categorisation to clarify responsibilities and contact points for the user, or represented entity in a business process, when making change requests to the related wiki resource or business process.

Non-Functional Requirements Specification:

The modelling environment should allow the importation of concepts from external sources.

Average (0 Votes)
The average rating is 0.0 stars out of 5.
No comments yet. Be the first.