General information

TAO concerns various type of users for various types of features. One of the main feature we provide is the opportunity for users to build some tests and to manage the whole tests delivery. All these features are gathered in the Back-office of the TAO platform but they may be accessed in 2 different ways, either using the complete Back-office Interface or by running a process monitored by the Workflow Engine providing access to available service from the platform.

Manage Back-office Users

The Tao Manager 1 User defined in figure 3 is the one created when installing the platform that let you access all features of the TAO platform and should only be accessed by a User having the TaoManager Role which is an instance of the BackOffice Role that controls all accesses to Back-office’s Services.

The TaoManager Role is also a sub-class of User Class in order to inherit specific properties of the User Class such as User’s Login, Password, Last Name, First Name, Languages.

Fig .1

You can add a user thanks to the top bar from the Home, will add a new TaoManager.

Fig .2

New TaoManager is also an instance of Role TaoManager.

Fig .3


The TAO platform also concerns Test Takers that will have to authenticate against the platform in order to take tests that are dedicated to them. In order to do that, the Test Taker Class is a sub-class of the TaoSubjectRole which is an instance of the FrontOffice Role. Users having the TaoSubjectRole may access the delivery platform.

Fig .4\ Adding a Test Taker in the Test Taker Extension will create an instance of the class Test Taker. (Jane and John)

Fig .5\ You can also obviously add sub-classes of Test Taker and add new properties to your own class in order to complete the description of your Test Taker that will then instantiate this class. (1StGrade is the class and Nicolas its instance)

Fig .6

Workflow Engine’s Users

As explained before, the TAO platform can be accessed through a work-flow that will drive the different steps needed to build, manage, and validate the process of tests’ creation. The creation of such a process will be the focus on another The Processes extension|guide. Different steps of this process can be executed by actors having different roles. You can define these specific users and roles in the Process Extension.

Fig .7

The predefined Role, Workflow User Role allow Users having this Role to access the Workflow Engine. Adding a User in the Process Extension will add an instance of the Workflow User Role(Chuck and Pedro have been created as Workflow User).

Fig .8

Adding a Role will create an instance of wfUser.

Fig .9

Then you can assign any created users to any created role (Chuck will remain Workflow User Role and Perdo will be both Workflow User Role and User Defined Role 1 ).

Fig .9

You can also assign any users to any roles (Tao Manager 1 will gain User Defined Role 1),

Fig .10