Deliverable D8.3 Clients - Europa€¦ · SEVENTH FRAMEWORK PROGRAMME Challenge 1 ... 4 Brian...

Legal Notice All information included in this document is subject to change without notice. The Members of the TAS3 Consortium make no warranty of any kind with regard to this document, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The Members of the TAS3 Consortium shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material.

SEVENTH FRAMEWORK PROGRAMME Challenge 1 Information and Communication Technologies

Trusted Architecture for Securely Shared Services

Document Type: Release Guide with Software Deliverable

Title: Deliverable D8.3 Clients

Work Package: WP8

Deliverable Nr: D8.3

Dissemination: final

Preparation Date: December 31, 2010

Version: 2.3

TAS3 Deliverable 8.3 - Clients Dec 31, 2010

TAS3_D08p3_client.software_v2.3.doc Page 2 of 53

The TAS3 Consortium

Beneficiary Nr

Beneficiary name Beneficiary short name

Date enter project

Date exit project

1 Katholieke Universiteit Leuven (Proj. Coord)

KUL M1 M48

2 Synergetics nv/sa SYN M1 M48 3 University of Kent KENT M1 M48 4 University of Karlsruhe KARL M1 M48 5 Technical University

Eindhoven TU/E M1 M48

6 Consiglio Nazionale delle Ricerche

CNR M1 M48

7 University of Koblenz-Landau UNIKOLD M1 M48 8 Vrije Universiteit Brussel VUB M1 M48 9 University of Zaragoza UNIZAR M1 M30 10 University of Nottingham NOT M1 M48 11 SAP research (S&T Coord.) SAP M1 M48 12 Eifel asbl EIF M1 M30 13 Intalio Ltd INT M1 M18 14 Risaris Ltd RIS M1 M48 15 Kenteq KETQ M1 M48 16 Oracle ORACLE M1 M48 17 Custodix nv/sa CUS M1 M48 18 Medisoft bv MEDI M1 M12 19 KIT KARL M1 M48 20 Symlabs SA SYM M18 M30

Contributors

Name Organisation 1 Michael Kutscher UNIKOLD 2 Joy Cameran UNIKOLD 3 Jessica Streicher UNIKOLD 4 Brian Reynolds (internal review) Risaris 5 Louis Schilders (internal review) Custodix



Contents

1 EXECUTIVE SUMMARY ................................................................6

1.1 READER’S GUIDE .............................................................................................. 6

2 INTRODUCTION TO THE SOFTWARE ...........................................8

2.1 PURPOSE........................................................................................................... 8

2.1.1 TAS³-dashboard....................................................................................... 8 2.1.2 BusinessProcessGui ................................................................................ 9 2.1.3 PolicyEditor ............................................................................................. 9

2.2 SCOPE............................................................................................................. 10

2.2.1 TAS³-dashboard..................................................................................... 10 2.2.2 BusinessProcessGui .............................................................................. 10 2.2.3 PolicyEditor ........................................................................................... 10

2.3 FUNCTIONALITY ............................................................................................. 10


2.4 AVAILABLE RELEASES AND COMPONENTS..................................................... 12


3 INSTALLATION GUIDELINES.....................................................14

3.1 HARDWARE AND SOFTWARE PREREQUISITES ................................................ 14


3.2 INSTALLATION AND CONFIGURATION INSTRUCTIONS.................................... 15


3.3 RUNNING THE TESTS...................................................................................... 17


4 HOW TO USE THE SOFTWARE...................................................22

4.1 TAS³-DASHBOARD .......................................................................................... 22

4.1.1 Login ...................................................................................................... 22 4.1.2 Usage of the menu................................................................................. 25

4.2 BUSINESSPROCESSGUI .................................................................................. 26

4.3 POLICYEDITOR ............................................................................................... 31



4.3.1 Usage of the PolicyEditor...................................................................... 31

5 ARCHITECTURE ........................................................................33

5.1 TAS³-DASHBOARD .......................................................................................... 33


5.3 POLICYEDITOR ............................................................................................... 34

6 API AND LIBRARY INFORMATION............................................37

6.1 TAS³-DASHBOARD .......................................................................................... 37


6.3 POLICYEDITOR ............................................................................................... 37

7 LICENSE INFORMATION............................................................38

8 ROADMAP AND CONCLUSIONS..................................................51

8.1 TAS³-DASHBOARD .......................................................................................... 51


8.3 POLICYEDITOR ............................................................................................... 51

9 REFERENCES ............................................................................52

10 AMENDMENT HISTORY ...........................................................53



List of figures fig. 1 TAS³-dashboard with menu and login screen from the business process

engine (workflow) ................................................................................................8 fig. 2 Screenshot from the Kenteq APL business process........................................9 fig. 3 Screenshot PolicyEditor with policy matrix..................................................10 fig. 4 Screenshot PolicyEditor with policy matrix..................................................12 fig. 5 Screenshot IntalioDesigner - Integration of a form into a business process

............................................................................................................................16 fig. 6 Screenshot IntalioDesigner - Intalio Ajax - PolicyEditor - parameter in

javascript source................................................................................................17 fig. 7 PolicyEditor - inpt policyin natural language format ..................................18 fig. 8 PolicyEditor - policy displayed in a matrix ...................................................19 fig. 9 PolicyEditor - save policy button ...................................................................20 fig. 10 PolicyEditor - output "The new code".........................................................21 fig. 11 TAS³-dashboard initial screen - user is not logged in ...............................22 fig. 12 TAS³-dashboard - user selects his preferred idp for login..........................23 fig. 13 login at the users preferred idp ...................................................................24 fig. 14 TAS³-dashboard - user is logged in.............................................................25 fig. 15 TAS³-dashboard menu with opened submenu ...........................................26 fig. 16 login TAS³ Process Engine...........................................................................27 fig. 17 user selects a workflow at the business process engine .............................28 fig. 18 business process engine confirms the start of the selected business

process................................................................................................................28 fig. 19 first task within the users task list .............................................................29 fig. 20 BusinessProcessGui - welcome screen of the Kenteq APL process ...........29 fig. 21 task list with the users next task ................................................................30 fig. 22 BusinessProcessGui - button with link to an external website .................31 fig. 23 BusinessProcessGui - user selection to accept or decline Kenteq PCP

terms and conditions .........................................................................................31 fig. 24 PolicyEditor displays policy in a matrix .....................................................32 fig. 25 TAS³-architecture .........................................................................................33 fig. 26 PolicyEditor - policy displayed as a matrix.................................................36



1 Executive Summary

TAS³ is an acronym for TASSS or in detail Trusted Architecture for Securely Shared Services. Its purpose is to provide a secure and trustworthy environment for a user to share his (most personal) data in a trustworthy and controlled manner. A lot of different parties can be a producer and/or a consumer of the users data. TAS³ provides control and ensures that only services and persons that are authorised by the user can access the data..

The client part of TAS³ that is described in this document covers the different software modules the user interacts with to use tasssified1 and TAS³ services.

This document provides information about the purpose, functionality, installation and usage of these software modules.

The TAS³-dashboard is the main entrance for the user. He uses it with his web browser to access business processes and the audit logs that are produced by different service providers and processes e.g. while accessing the users data.

The BusinessProcessGui is the front part of the business processes that the user interacts with. It provides information for the user and asks him for information necessary for the business process. Also the BusinessProcessGui gives the user the opportunity to make decisions (e.g. selection of a service provider, accept or decline terms and conditions, ...).

The policy editor is also a user interface (actually) used inside of business processes. It enables the user to set and modify policies to control the accessibility of his data.

Although the BusinessProcessGui and the PolicyEditor are strongly bound to a business process they are put together in this document because of these components are of major concern towards user centricity and usability.

1.1 Reader’s Guide

The three software modules TAS³-dashboard, BusinessProcessGui and PolicyEditor are described in this document. These are main frontends to the user.

Basically chapters 1 – 2 are for managers to get an overview about the mentioned software modules. Chapters 1 – 4 addresses testers, installers, deployers, and integrators. Chapters 5 – 8 are intended to provide information for developers who want to interface to or extend the software modules.

All three modules are usable at the current stage of the demonstrators. The TAS³-dashboard will be enhanced as soon as additional TAS³-components (e.g. data-discovery, standalone PolicyEditor, …) are available to be integrated. A later version of the PolicyEditor is intended to become a standalone version. This should be useable outside of a business process e.g. From within the TAS³- 1 The term ‚tasssified’ shall express that a former unsecured service is now secured by using TAS³-services and infrastructure.



dashboard.. The BusinessProcessGui is enhanced along the needs of the business processes.

Beside of technical enhancements it is planned to check the usability of the different modules and to modify them according to the users needs.



2 Introduction to the Software

2.1 Purpose

The following section explains the purposes of the three software components TAS³-dashboard, BusinessProcessGui and PolicyEditor.

2.1.1 TAS³-dashboard

The TAS³-dashboard is the main entrance for the user to access tasssified business processes and to view their audit logs. The user uses his web browser to access the TAS³-dashboard. He can login using his preferred tasssified identity provider. The integrated login solution (zxid) offers SSO (Single sign-on)2 features to the TAS³-dashboard and the other components of TAS³ as well as to other tasssified services. After login the user can access his personal set of workflows and the audit viewer pointing to his audit data.

fig. 1 TAS³-dashboard with menu and login screen from the business process engine (workflow)

The TAS³-dashboard also provides some basic information about TAS³ and contact information to the user.

As soon as there are more TAS³-components available the functionality of the portal will be upgraded.

2 SSO (Single sign-on) provides access control of different but related systems. The user logs in only once and gets access to all the systems without the need to login separately to each system.



2.1.2 BusinessProcessGui

The BusinessProcessGui is part of the different business processes and strongly connected with them. It is the frontend of the business process towards the user. It enables the user to walk through the business process - to retrieve information, to provide information and to make decisions.

fig. 2 Screenshot from the Kenteq APL business process

The user can access an external website by clicking a button (see fig. 3), view additional information (e.g. Kenteq APL terms and conditions) and make the decision to accept or decline the listed terms and conditions.

2.1.3 PolicyEditor

The policy editor (fig. 4) enables the user to view and edit policies. These policies can be basically generated by a service provider or can be set up by the user himself. The user can simply do this by clicking some checkboxes that represent a specific right that will be granted to a certain role and for the mentioned kind of data.



fig. 3 Screenshot PolicyEditor with policy matrix

This version of the policy editor has been implemented to be used inside a business process. Therefore from the user perspective it is a specific GUI element in the business process. One of the next steps will be to extend the PolicyEditor to a standalone version that can directly be handled outside a business process – e.g. from the TAS³-dashboard.

2.2 Scope

The scope section provides in one sentence the use of the TAS3-portal, the BusinessProcessGui and the editor.

To get more details please consult the section 2.3 - Functionality and chapter 4 - How to use the software.


The TAS³-dashboard enables the user to access the different functionality of TAS³ and the secured and trustworthy services he needs via a webbrowser.


The BusinessProcessGui is strongly bound to the business process enables the user to get or put information from or to the business process and make decisions to influence the further flow of the process.

2.2.3 PolicyEditor

The PolicyEditor enables the user to view, set up and modify new or existing policies that grant different access rights to specific persons to his personal data.

2.3 Functionality

This section provides a deeper insight into the functionality of the TAS³-dashboard, the BusinessProcessGui and the PolicyEditor.



To get more information about the usage of these modules please check chapter 4 – How to use the software.


The TAS³-dashboard provides a variety of functions to the user.

To access the TAS³-dashboard the user opens a browser window and goes to the URL of his TAS³-dashboard. There he can login using his preferred tasssified identity provider (zxid). Using zxid for the login provides SSO (Single Sign On) capabilities to the TAS³-dashboard. Therefore for using other services that also support SSO the user does not need to login to that service separately.

The TAS³-dashboard is part of a JBoss portal. As it is positioned in its own tab it offers the possibility to add additional tabs with other content in the portal.

The TAS³-dashboard contains two windows (portlets). One on the left side it shows a menu window (portlet) almost similar to a standard website menu and a second window that provides different types of content (dynamic, static, embedded websites) related to the selected point in the menu. The size of the windows can be enhanced to full width inside the portal. Because of that, the content window can be maximised so there is more space for content. In this case the menu window is not visible. It is also possible to resize the content window to the smaller size to get access to the menu again.

Via the menu the user can select several points to get more information e.g. about TAS³. The main functionality of the TAS³-dashboard is to provide access to the most important applications inside the portal: the audit viewer and the workflows / business processes.

The audit viewer provides logging information about the different kinds of access to the users data.

Information about the business processes can be found in the next section of this document (BusinessProcessGui) and in Deliverable D3.3 (BusinessProcesses Kenteq and Nottingham).


The BusinessProcessGui is part of a business process that offers the services the user wants to utilise. The business process itself runs on a Intalio BPMN server. That business process server itself is integrated into the TAS³-dashboard as an iframe.

Each business process needs his own customised BusinessProcessGui. This GUI offers the user static and dynamic information provided by the business process. Also the user is able to provide information to the business process or the services in the background. It is possible to open an additional browser window with related content via buttons and links to redirect the user to an external website to continue the work there. Last but not least the user is enabled to make decisions that influence the further flow of the business process.



More information about business processes and the technical background can be found in Deliverable 3.3.

To provide a user-friendly and more unique appearance of the BusinessProcessGui it is planned to set up a Style Guide and a Design Guide.

2.3.3 PolicyEditor

The PolicyEditor enables the user to view and edit policies (depending on the configuration). In the actual version it is a special kind of a business process GUI form and therefore bound to a business process. The PolicyEditor accepts a string with a policy in a special form of natural language3 as input. Based on that natural language policy the PolicyEditor sets up a matrix with roles, data items and actions that represent the given natural language policy. Also the rights for the combination of role – data item and action are described in the natural language policy. By clicking the checkboxes the user is able to change the rights. After changing the policy according to his needs the user clicks on Save policy to start the generation of the new policy in natural language format. That natural language policy is then provided as a string to the business process for usage in following steps.

The PolicyEditor has two internal parameters that control the behaviour of it. Parameter 1 controls whether the matrix is editable or not which is useful in case of the policy shall only be shown but not edited. Parameter 2 controls whether

fig. 4 Screenshot PolicyEditor with policy matrix

2.4 Available Releases and Components

This section contains information about the actual releases of the TAS³ software components TAS³-dashboard, the BusinessProcessGui, the PolicyEditor and where to get them.

3 The natural language policy is described in detail in Deliverable D6.3 chapter 1.




The actual version of the portal can be viewed at http://141.26.66.254/portal or at http://nekton.tas3.eu:16180/portal.

The actual version of the TAS³-dashboard is the file TAS³-dashboard-ear-2.0.0.FINAL.ear and can be found in the components pool on the TAS³-project website https://portal.tas3.eu/.

The JBoss-portal-zxid-connector (zxidvalve.jar) is actually version 1.0 and also available in the component pool at the TAS³-project-website.


The BusinessProcessGui is strongly related to the business process. The major business processes using the GUI are the Kenteq and the Nottingham business processes. The actual versions are integrated into the business processes that can be accessed via the TAS³-dashboard or directly at taipei.uk.karlsruhe.de or at nekton.tas3.eu.

The GUI itself is part of the actual business process. Information about the actual package of the business process is available in Deliverable D3.3.

2.4.3 PolicyEditor

The actual version of the PolicyEditor is V1.0. The corresponding file is PolicyChoser1 and can be found in the components pool on the TAS³-project website. This version can be imported into business process projects using the IntalioDesigner.



3 Installation Guidelines

This chapter provides information about the hardware and software prerequisites and the necessary steps to install the software modules.

3.1 Hardware and Software Prerequisites

This section provides the specifications about the hardware and software that is needed to run and access the TAS³-dashboard, the BusinessProcessGui and the PolicyEditor.


The TAS³-dashboard must be deployed on a JBoss server. Therefore a running JBoss server with included JBoss-portal (http://sourceforge.net/projects/jboss/files/JBoss%20Portal/JBoss-Portal-2.7.2.GA/jboss-portal-2.7.2-bundled.zip/download) is needed. This package includes JBoss 4.2.3 and JBoss-portal 2.7.2. Installation documentation for the JBoss-portal can be found on that website too.

To run the portal, a server (possibly virtual) with at least 512 mb Ram running Linux or MS Windows as operating system and an JAVA JDK should be used. Other software that is needed comes along within the JBoss-portal-package.

To access the running TAS³-dashboard a browser is needed (e.g. Firefox 3.6).

To provide the basic zxid SSO capabilities it is also necessary to install zxid. The actual zxid package (V 0.69) can be downloaded from the component pool of the TAS³-project-website or – as well as the installation documentation – from the official zxid-website (zxid.org).

In addition to zxid the jbossportal-zxid-connector is needed to be installed. This piece of software has been written to enable zxid for the JBoss-portal and is therefore necessary for the TAS³-dashboard. It can be downloaded as zxidvalve V1.0 from the component pool of the TAS³-project website.


The BusinessProcessGui is part of the corresponding business process. Therefore a running business process on a working Intalio Business Process Server is needed. Further information about the processes and the IntalioServer can be found in D3.3.

To integrate the BusinessProcessGui into a business process the IntalioDesigner 6.x is needed. This software is free and is available for download for Linux or windows version from http://www.intalio.com/. To use the IntalioDesigner a standard PC with Linux or windows and a running JAVA is needed. For the handling of larger business processes a high resolution monitor is recommended.

To access the GUI and the business process a browser (e.g. Firefox 3.6) is required.



3.1.3 PolicyEditor

The actual version of the policy editor is also part of BusinessProcessGui. Therefore the same prerequisites are valid as for the BusinessProcessGui.

3.2 Installation and Configuration Instructions


The installation of the TAS³dashboard is quite easy. The TAS³-dashboard is provided as an EAR-file. This can be installed / deployed by simply copying the EAR-file into the folder server/default/deploy (e.g. /data/jboss-portal-2.7.2/server/default/deploy/ - assuming that the JBoss-portal was installed at /data/jboss-portal-2.7.2).

As the JBoss-server is able to hot deploy .ear-files, the TAS³-dashboard will automatically be deployed while the JBoss-server is running or when it is started again. Prior to the install remove any previous version installed.

To install the JBoss-portal-zxid-connector simply copy the file zxidvalve.jar into the folder /data/jboss-portal-2.7.2/server/default/lib - assuming that the JBoss-portal was installed at /data/jboss-portal-2.7.2.

Beside of these software prerequisites it is necessary to have a valid user at a zxid IDP.


To integrate the GUI forms into a business process, the Intalio Designer is required. Assuming that the target business process is open in the Intalio designer, simply copy the forms from the package of the BusinessProcessGui into the business process project. Then open the business process model and drag the needed form to a pool that is marked as non-executable. Now select Use XXXXX.gi for People Activity (create and complete). Next step is to connect the new tasks to the calling tasks in an executable pool. It is also necessary to set up the description text in the workflow tab of the first new tasks (create). This is the text that will be shown at the task panel of the business process server. Last but not least it might be necessary to use the Mapper to connect fields within the form to the corresponding data objects of the business process.



fig. 5 Screenshot IntalioDesigner - Integration of a form into a business process

3.2.3 PolicyEditor

The current version of the Policy Editor is a specific BusinessProcessGui form which can be integrated in the same way as a normal BusinessProcessGui form.

Additionally it should be checked that the two parameters showInAndOutput and tableIsEditable are set correctly. They can be found by opening the PolicyEditor.gi (1, 2) in the IntalioDesigner, looking at the top lines (4) of the logic.js tab (3).



fig. 6 Screenshot IntalioDesigner - Intalio Ajax - PolicyEditor - parameter in javascript source

3.3 Running the Tests


To test the TAS³-dashboard after installation ensure that the JBoss-server is up and running. Use a browser and enter the URL to the JBoss installation. Now add the term /portal to the URL. Then the JBoss portal should appear in your browser window. There should be a TAS³-dashboard tab visible at the portal. Click on the TAS³-dashboard tab and a menu and content-portlet will become availiable. By clicking on the different buttons in the (left) menu-portlet the appropriate content should appear in the content portlet.

A second test is to login via zxid. By clicking on the link Login or Anmeldung (at the top, right corner of the portal) the browser should be redirected to the IDP selection page of the server. After selecting an available IDP where you have an account, the next redirection goes to the selected IDP. After entering the correct user-id and password the next redirection ends back at the portal and the user name should be presented at the top of the menu or content-portlet. The concrete steps for the login are shown in detail in chapter 4 – How to use the software.


To test the BusinessProcessGui it is necessary to run the Intalio BPMS (business process management server) and to start the corresponding process. Now it is

1

2

3

4



possible to test the BusinessProcessGui by running through the possible steps of the business process.

3.3.3 PolicyEditor

The actual version of the PolicyEditor can be tested in the same way.

Additionally it is possible to perform developer tests on the PolicyEditor within the IntalioDesigner.

Therefore the IntalioDesigner has to be started and the PolicyEditor has to be loaded in the IntalioAjax editor (form editor and part of the IntalioDesigner). The tab appCanvas.xml should be open. A valid natural language policy should be in the field Insert Policy Code. E.g.

End_User,Admin,Organizer,Assessor are Roles. create,read,update,delete are Actions. Personal-Data,Competences,Qualifications are Resources. End_User can create Personal-Data. End_User can read Personal-Data. End_User can update Personal-Data.

fig. 7 PolicyEditor - inpt policyin natural language format

After clicking the button Initiate with these values the matrix is generated and displayed on the screen..



fig. 8 PolicyEditor - policy displayed in a matrix

The generated matrix represents the inserted policy code. Roles are columns, Resources are rows and the check boxes represent the policy settings.

The status changes when clicking on the checkboxes.



fig. 9 PolicyEditor - save policy button

When clicking “save policy” (fig. 9) the natural language policy generated from the checked boxes will appear in the field “The new code” (fig. 10).



fig. 10 PolicyEditor - output "The new code"

Resulting code - policy in natural language:

End_User,Admin,Organizer,Assessor are Roles. create,read,update,delete are Actions. Personal-Data,Competences,Qualifications are Resources. End_User can create Personal-Data. End_User can read Personal-Data. End_User can update Personal-Data. Admin can create Personal-Data. Admin can read Personal-Data. Admin can update Personal-Data. Admin can delete Personal-Data. Organizer can read Personal-Data. Assessor can read Personal-Data. Admin can read Competences. Assessor can create Competences. Assessor can read Competences. Assessor can update Competences. Assessor can delete Competences. Admin can read Qualifications. Organizer can read Qualifications. Organizer can update Qualifications. Organizer can delete Qualifications.



4 How to Use the Software

This part of the document shows how the user can work with the TAS³-dashboard, the BusinessProcessGui and the PolicyEditor.

4.1 TAS³-dashboard

The TAS³-dashboard can be accessed via web browser.

4.1.1 Login

The TAS³-dashboard provides a login with SSO-capabilities using zxid.

fig. 11 TAS³-dashboard initial screen - user is not logged in

The user is at the TAS³-dashboard and he’s not logged in. This is displayed at the top of the menu part of the portal. By clicking at login / Anmeldung (fig. 11) the user is directed to the screen where he can select his preferred tasssified identity provider.

Detailed information SSO, authentication and authorization in TAS³ can be found in deliverable D7.1 Design of Identity Management, Authentication and Authorization Infrastructure.



fig. 12 TAS³-dashboard - user selects his preferred idp for login

The screenshot (fig. 12) shows that the user has selected the zxididp.uni-koblenz.de from the dropdown box. By clicking the button Login (P2) the user is directed to his Identity provider.



fig. 13 login at the users preferred idp

Now the user identifies himself by entering his user id and password. By clicking the button Login he finishes the login procedure at his identity provider and gets redirected to the TAS³-dashboard again.



fig. 14 TAS³-dashboard - user is logged in

At the top of the menu part of the TAS³-dashboard the user id now is shown and the login process is finished (fig. 14).

4.1.2 Usage of the menu

The menu of the portal contains several groups of functions addressing different questions of a user (e.g. What is my workflow). To open that group of functions the user clicks on the arrow down sign on the right side of the menu group. The Menu group level will expand into menu group items e.g. The user selects “What is my workflow” which expands into “workflows” and “search” (fig. 15). The user selects “workflows” and he is redirected to the TAS³ process engine on the Intalio Business Process Management Server.



fig. 15 TAS³-dashboard menu with opened submenu

Other menu points provide information about TAS³ as well as contact possibilities to TAS³.

Another important menu group Who accessed my data leads to the audit information which informs the user who accessed the users personal data.

4.2 BusinessProcessGui

The BusinessProcessGui is part of a business process. The access to the business process is provided via the TAS³-Dashboard (“What is my workflow”) or directly via the URL of the business process server.

If the user is not already logged in at the business process server this should happen now.

If the business process server is SSO enabled and the user is already logged in at the TAS³-dashboard then the user is automatically logged into the business process server too.



fig. 16 login TAS³ Process Engine

The user selects the business process at the processes at the tab of the business process server.



fig. 17 user selects a workflow at the business process engine

The business process engine confirms the start of the selected business process.

fig. 18 business process engine confirms the start of the selected business process

The user selects the first task under the task tab.



fig. 19 first task within the users task list

The first BusinessProcessGui form appears on the screen.

fig. 20 BusinessProcessGui - welcome screen of the Kenteq APL process

After checking the information at the form – perhaps entering required data the user clicks at the button Complete to close the form and to continue the business process.



Again the task list of the business process engine is shown and the user can select the next task (fig. 21). Note: If the user now leaves the business process server and logs in again later, the next task is still waiting for the user to continue.

fig. 21 task list with the users next task

The next screen (fig. 22) contains a button that links to an external website with additional information. By clicking on that button a new tab (or window) in the browser is opened and the additional information (e.g. terms and conditions) is shown.



fig. 22 BusinessProcessGui - button with link to an external website

Other BusinessProcessGui forms can contain radio buttons. Using these the user can influence the further flow of the business process. When the form is finished the user goes on by clicking the Complete button.

fig. 23 BusinessProcessGui - user selection to accept or decline Kenteq PCP terms and conditions

4.3 PolicyEditor

4.3.1 Usage of the PolicyEditor

The current version of the PolicyEditor is integrated into the business process.

Calling the Policy Editor is the same as calling another BusinessProcessGui form within a Business Process..

The PolicyEditor is started in editing mode. The policy string in natural language is shown as a matrix to the user (fig. 24).



fig. 24 PolicyEditor displays policy in a matrix

The columns of the matrix show the different roles that are relevant for the policy and the related business process. The rows show the relevant data items (resources). The checkboxes that are next to the characters c, r, u, d allow (checked) or prevent (unchecked). In other words a checked box means to grant the right to a role to perform the action (c,r,u,d) on the corresponding type of data. As mentioned in the legend at the bottom of the matrix c, r, u, d are the abbreviations for create, read, update and delete. These are all possible actions for any combination of role and data. E.g. the checked box in column 1 and row 1 means that “End_User is allowed to create Personal Data”.

Changing the status of a checkbox changes the policy setting.

It is important to click the Save Policy button before leaving the editor – otherwise the resulting policy in natural language is not generated. Clicking complete finishes this step and the user returns to the business process..



5 Architecture

This chapter provides a description of the position of the software modules in the TAS³- architecture and an explanation of the internal architecture of the module for developers.

fig. 25 TAS³-architecture

The TAS³-dashboard can be found in the TAS³-architecture picture at number 5 – dashboard.

The BusinessProcessGui is called FrontEnd / Web GUI in the TAS³-architecture picture. It is labelled with number 2 and belongs to the box PayloadApplications.

The PolicyEditor belongs to the box TAS³ User Tools and is labelled with number 6.

5.1 TAS³-dashboard

The TAS³-dashboard is the central client application that enables the user to access the TAS³ services and other tasssified services e.g. special business processes/workflows.

The TAS³-dashboard is based on the JBoss-portal technology. It contains two portlets: menu and content. The menu portlet sends a message with the requested information to the content portlet. The content portlet refreshes and



displays the content related to the selected menu item. The content portlet can display various types of data: e.g. static or dynamic text or an external website as an inline-frame.

The portlet communication using Portlet bridge follows the standard JSR 329. Additional information for the portlet bridge communication can be found at http://www.infoq.com/articles/jsf-ajax-seam-portlets-pt-3.


The BusinessProcessGui belongs to the business processes and to the business process engine.

The BusinessProcessGui is created using IntalioAjax that is part of the IntalioDesigner.

The integration into the business process also is done within the IntalioDesigner. The GUI form is dragged and dropped at the business process. After binding the form to tasks in the business process (via create and complete) the form can be used immediately.

It provides the possibility to process data in and out via the business process. Therefore IntalioAjax provides a library of GUI elements that can be dragged and dropped onto the form.

It is possible to edit various sets of parameters to change the design and functionality of the GUI elements.

The data mapper can be used to bind GUI elements to data fields from within the business process.

At a later stage it is planned to provide a style guide and design guide for the implementation of BusinessProcessGui forms.

5.3 PolicyEditor

The PolicyEditor was developed using IntalioAjax.

The integration into the business process is also done with the IntalioDesigner, the business process designer.

The design of the PolicyEditor is mainly changed at the canvas. The functionality of the PolicyEditor is mainly written in JavaScript at the JavaScript part of the IntalioAjax editor.

The PolicyEditor accepts a string as input. This string contains the policy that shall be shown or edited in a special form. This form is called natural language policy and follows a strict syntax. More information about the natural language policy can be found in the deliverable D6.3 chapter 1. The converter to translate this policy into the appropriate format for the PERMIS nPDP is described in D6.3 chapter 5.



The natural language policy is a set of sentences that describe roles and types of personal data. Roles and data are usually bound to a certain business process. Possible actions are also described. These structural sentences represent the columns and rows of a matrix that contain itself small matrices belonging to the actions in each field. In addition to that another set of sentences describe the allowed actions for each field.

Below there is an example of a natural language policy. To make it more readable the string is split into one sentence per line.

End_User,Admin,Organizer,Assessor are Roles. create,read,update,delete are Actions. Personal-Data,Competences,Qualifications are Resources. End_User can create Personal-Data. End_User can read Personal-Data. End_User can update Personal-Data. Admin can create Personal-Data. Admin can read Personal-Data. Admin can update Personal-Data. Admin can delete Personal-Data. Organizer can create Personal-Data. Organizer can read Personal-Data. Organizer can update Personal-Data. Organizer can delete Personal-Data. Assessor can read Personal-Data. End_User can create Competences. End_User can read Competences. End_User can update Competences. Admin can create Competences. Admin can read Competences. Admin can update Competences. Admin can delete Competences. Organizer can read Competences. Assessor can create Competences. Assessor can read Competences. Assessor can update Competences. Assessor can delete Competences. End_User can create Qualifications. End_User can read Qualifications. End_User can update Qualifications. Admin can create Qualifications. Admin can read Qualifications. Admin can update Qualifications. Admin can delete Qualifications. Organizer can read Qualifications. Assessor can create Qualifications. Assessor can read Qualifications. Assessor can update Qualifications. Assessor can delete Qualifications.

The resulting output in the PolicyEditor is shown below (fig. 26).



fig. 26 PolicyEditor - policy displayed as a matrix



6 API and Library Information

The following chapter provides information about the APIs used (evt. generated).

6.1 TAS³-dashboard

For the TAS³-dashboard no new APIs were created.

To generate the Jboss-portal-zxid-connector (zxidvalve) the JBoss API and the zxid API were used. Further information can be found at jboss.org and zxid.org.


For the BusinessProcessGui no API was used or created.

6.3 PolicyEditor

For the PolicyEditor no API was used or created.



7 License Information

This chapter provides information about the licences that are related to the software.

University of Koblenz-Landau All software produced in TAS3 by the IWM4 at the University of Koblenz-Landau is released under the BSD license.

Intalio - Intalio|BPMS Community Edition License http://community.intalio.com/intalio-bpms-community-edition-license.html

Written by Admin Intalio on Dec 01 2005 The Community License is a free version of Intalio|BPMS, but does have restrictions on usage. Please read the license agreement for details. PLEASE READ THIS LICENSE CAREFULLY BEFORE DOWNLOADING OR USING THE SOFTWARE This Intalio|BPMS Community Edition License (the "Agreement") is entered into between you ("Developer") and Intalio, Inc., a Delaware corporation, having offices located at 644 Emerson St, Suite 200, Palo Alto, CA 94301 ("Intalio"), and sets forth the terms and conditions governing Developer's downloading and use of Intalio's proprietary software program called Intalio|BPMS Community Edition (the "Intalio Software"). Developer should carefully read this Agreement and indicate its acceptance of, and agreement to be bound by the terms and conditions of this Agreement by COMPLETING THE REGISTRATION PROCESS AND DOWNLOADING THE INTALIO SOFTWARE DEVELOPER IS INDICATING ITS AGREEMENT TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS AGREEMENT. If Developer does not agree to this Agreement, Developer may not register to use, download or use the Intalio Software. 1. LICENSE (a) Limited Development, Testing and Live Production License. Subject to all other terms and conditions set forth herein, Intalio hereby grants to Developer a royalty-free, personal, nontransferable, nonsublicenseable and nonexclusive limited license to (a) download the Intalio Software in object code form only, from Intalio's website in accordance with any rules or procedures set forth thereon and (b) to use the Intalio Software solely for evaluation, development, testing, demonstration, and live production only in accordance with the terms and conditions of this Agreement and any associated documentation provided by Intalio, (c) to use the Intalio Software only with Apache Geronimo with a process data persistence provided by the Derby java database or by the MySQL database, and with authentication services provided by the built-in file-based authentication or Apache DS. (b) Ownership of Intalio Software. As between the parties, Intalio retains all right, title and ownership in and to all proprietary rights with respect to the Intalio Software and all copies and portions thereof and any and all modifications and enhancements thereto. Nothing herein, including the license set forth above, shall constitute a sale of the Intalio Software or any portion or copy thereof. (c) Restrictions. Unless otherwise agreed in writing by the Parties, Developer shall not (and shall not allow any third party to): (i) copy the Intalio Software or any portion thereof, (ii) use the Intalio Software in live production or with live data except on allowed databases, authentication services and application server, (iii) decompile, disassemble, or otherwise reverse engineer or attempt to reconstruct or discover any source code or underlying ideas or algorithms of the Intalio Software by any means whatsoever, (iv) remove any product identification, copyright or other notice, (v) provide, lease or lend the Intalio

4 Institut fuer Wissensmedien – Knowledge Media Institute



Software to any third party or use the Intalio Software for timesharing or service bureau purposes, (vi) modify or create a derivative work of any part of the Intalio Software, (vii) load or use any portion of the Intalio Software at any site or on any equipment other than that indicated above, or (viii) disclose any performance information or analysis to any third party (including, without limitation, benchmarks or evaluation test results) from any source relating to the Intalio Software. 2. OBLIGATIONS AND ACKNOWLEDGMENTS OF DEVELOPER (a) Access. Developer acknowledges and agrees that Intalio, in its sole discretion, may restrict or terminate Developer's access to or use of the Intalio Software. (b) Computer System. Developer acknowledges and agrees that Developer is responsible for providing all computer and other equipment and facilities required under this Agreement. (c) Feedback or Suggestions. Developer acknowledges and agrees that Intalio shall retain any and all right, title and interest in and to any such actual or suggested modifications, design changes or improvements of the Intalio Software that Developer or its employees or agents may provide to Intalio as a result of Developer's use of the Intalio Software, without the payment of any additional consideration therefore. 3. WARRANTY DISCLAIMER THE PARTIES AGREE THAT THE INTALIO SOFTWARE IS PROVIDED "AS IS" AND THAT INTALIO MAKES NO WARRANTY AS TO THE INTALIO SOFTWARE. INTALIO DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF PERFORMANCE OR MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT. DEVELOPER BEARS ALL RISK RELATING TO QUALITY AND PERFORMANCE OF THE SYSTEM. INTALIO DOES NOT WARRANT THAT THE INTALIO SOFTWARE OR THE FUNCTIONS CONTAINED IN THE INTALIO SOFTWARE WILL MEET DEVELOPER'S REQUIREMENTS, OPERATE WITHOUT INTERRUPTION OR BE FREE OF ERROR. 4. LIMITATION OF LIABILITY IN NO EVENT SHALL INTALIO BE LIABLE FOR ANY DAMAGES, WHETHER IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), INCLUDING BUT NOT LIMITED TO DIRECT, CONSEQUENTIAL (INCLUDING WITHOUT LIMITATION LOSS OF PROFITS), COST OF SUBSTITUTE GOODS, SPECIAL, EXEMPLARY, INCIDENTAL AND INDIRECT DAMAGES, ARISING OUT OF OR IN CONNECTION WITH THIS AGREEMENT OR THE USE, THE RESULTS OF USE OR THE INABILITY TO USE THE INTALIO SOFTWARE. 5. TERM AND TERMINATION (a) Term. Unless earlier terminated as set forth herein, the term of this Agreement shall commence on the date Developer completes the registration process and downloads the Intalio Software and continue for as long as Developer keeps one or more copy of Intalio Software. (b) Termination. Developer may terminate this Agreement immediately upon ceasing any and all use of the Intalio Software and destroying all copies of Intalio Software for any reason or for no reason. Intalio may terminate this Agreement immediately upon written electronic notice to Developer if at any time Intalio believes that Developer has failed to comply with the terms and conditions hereof. (c) Effect of Termination or Expiration. Upon termination, the license and all rights granted to Developer hereunder shall terminate and Developer shall immediately cease any and all use of the Intalio Software and destroy all copies of Intalio Software. 6. GENERAL (a) Non assignability. Neither the rights nor the obligations arising under this Agreement are assignable or transferable by Developer, and any such attempted assignment or transfer shall be void and without effect. (b) Entire Agreement. This Agreement constitutes the entire agreement between the parties pertaining



to the subject matter hereof, and except as expressly provided herein any and all written or oral agreements previously existing between the parties are expressly cancelled. (c) Equitable Relief. Developer acknowledges and agrees that due to the unique nature of Intalio's Confidential Information, there can be no adequate remedy at law for any breach of Developer's obligations hereunder, that any such breach may allow a party or third parties to unfairly compete with Intalio resulting in irreparable harm, and therefore, that upon any such breach or threat thereof, Intalio shall be entitled to injunctions and other appropriate equitable relief in addition to whatever remedies it may have at law. (d) Entire Agreement; Severability; Waiver. This Agreement is the complete, final and exclusive expression of the agreement of the Parties and supersedes all prior agreements and communications, written or oral, concerning the subject matter herein and may not be changed or terminated except by a document in writing signed by the party against whom the same is sought to be enforced. If any of the provisions of this Agreement are invalid under any applicable statute or rule of law, such provisions or portions thereof are to that extent deemed to be omitted. The waiver or failure of either party to exercise in any respect any right provided for herein shall not be deemed a waiver of any further right hereunder. (e) Choice of Law; Jurisdiction. This Agreement shall be governed by the laws of the State of California and shall be effective as of the date of execution by a duly authorized agent or employee of Intalio. Any legal action or proceeding relating to this Agreement shall be instituted in a state or federal court in the Northern District of California. Intalio and Developer agree to submit jurisdiction of, and agree that venue is proper in, these courts in any such action or proceeding. (f) Attorneys' Fees. If a legal action or arbitration proceeding is commenced in connection with the enforcement of this Agreement or any instrument or agreement required under this Agreement, the prevailing party shall be entitled to attorneys' fees actually incurred (including allocated costs for in-house legal services), costs and necessary disbursements incurred in connection with such action or proceeding, as determined by the court or arbitrator. (g) Headings. The section headings used in this Agreement are intended for reference purposes only and shall not affect the interpretation of this Agreement. (h) Survival. Sections 1(b), 1(c), 2(c), 3, 4 and 6 shall survive termination of this Agreement. Last Updated ( Jul 18 2008 )

JBoss portal (new GateIn) JBoss portal is released under LGPL v2.1. This can be found at http://www.gnu.org/licenses/lgpl-2.1.html

GNU Lesser General Public License, version 2.1

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.



This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public



License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION



0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you".

A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.

The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)

"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:



a) The modified work must itself be a software library.

b) You must cause the files modified to carry prominent notices stating that

you changed the files and the date of any change.

c) You must cause the whole of the work to be licensed at no charge to all

third parties under the terms of this License.

d) If a facility in the modified Library refers to a function or a table of data to

be supplied by an application program that uses the facility, other than as an

argument passed when the facility is invoked, then you must make a good faith

effort to ensure that, in the event an application does not supply such function

or table, the facility still operates, and performs whatever part of its purpose

remains meaningful.

(For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.



Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.

This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)



Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:

a) Accompany the work with the complete corresponding machine-readable

source code for the Library including whatever changes were used in the work

(which must be distributed under Sections 1 and 2 above); and, if the work is

an executable linked with the Library, with the complete machine-readable

"work that uses the Library", as object code and/or source code, so that the

user can modify the Library and then relink to produce a modified executable

containing the modified Library. (It is understood that the user who changes the

contents of definitions files in the Library will not necessarily be able to

recompile the application to use the modified definitions.)

b) Use a suitable shared library mechanism for linking with the Library. A

suitable mechanism is one that (1) uses at run time a copy of the library

already present on the user's computer system, rather than copying library

functions into the executable, and (2) will operate properly with a modified

version of the library, if the user installs one, as long as the modified version is

interface-compatible with the version that the work was made with.

c) Accompany the work with a written offer, valid for at least three years, to

give the same user the materials specified in Subsection 6a, above, for a

charge no more than the cost of performing this distribution.

d) If distribution of the work is made by offering access to copy from a

designated place, offer equivalent access to copy the above specified materials

from the same place.

e) Verify that the user has already received a copy of these materials or

that you have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need



not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:

a) Accompany the combined library with a copy of the same work based on

the Library, uncombined with any other library facilities. This must be

distributed under the terms of the Sections above.

b) Give prominent notice with the combined library of the fact that part of it

is a work based on the Library, and explaining where to find the accompanying

uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.



11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the



Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under



these terms (or, alternatively, under the terms of the ordinary General Public License).

To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.

one line to give the library's name and an idea of what it does.

Copyright (C) year name of author This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. signature of Ty Coon, 1 April 1990 Ty Coon, President of Vice

That's all there is to it!



8 Roadmap and Conclusions

This chapter describes possible and already planned upgrades of the TAS³-dashboard, the BusinessProcessGui and the PolicyEditor.

8.1 TAS³-dashboard

For the TAS³-dashboard it is planned to strip unused points from the menu. Additional points will be added as soon as new modules (e.g. data discovery) are available.

It is planned to intensely check the usability of the TAS³-dashboard and redesign it according to the users needs.

Also it is planned to enhance the JBoss-portal-zxid-connector to automatically create new users if the user is a valid / TAS³-verified user that has no account yet. In reality that user has to be created manually via the user management of the JBoss portal.


The usability of the BusinessProcessGui is being verfied. It is planned to build a redesigned version of the Kenteq business process GUI based on the results. Also the Use Cases of the Nottingham demonstrator are checked for usability. The results of these tests will also influence the design of the screens that later will be realised as the BusinessProcessGui for the Nottingham business process.

The results of the usability tests will also be the base for a style guide and design guide.

Beside the usability enhancements other changes resulting from the further development of the storyboards and the business processes for the use cases. will be implemented

Further information and details of the use cases can be found in the deliverable D9.1 - Pilots specification and use case scenarios.

8.3 PolicyEditor

As with the two other software modules, the PolicyEditor will be checked and its usability enhanced.

Beside that it is planned to develop a standalone version of the policy editor that can be used independently outside of a business process – e.g. as a separate menu point of the TAS³-dashboard.

Another possible enhancement of the PolicyEditor could be the integration of a drilldown functionality e.g. towards persons that belong to a role of a business process or details of a data group.



9 References

We decided two support two standards for references.

[1] J. Muelle, “Integration with TAS³ trust applications of employment and eHealth processes”, TAS³ Deliverable D3.3, Dec. 2010

[2] D. Chadwick, “Controlled Natural Language Policies”, Deliverable D6.3, Jun

2010 [3] M. Santos, “Repository services”, TAS³ Deliverable D8.1, Dec. 2010 [4] B. Claerhout, S. Winfield, T. Kirkham, L. Polmann, “Pilots specification and

use case scenarios”, TAS³ Deliverable D9.1, Dec. 2010



10 Amendment History

Ver Date Author Description/Comments 2.0 2010-11-07 MK First structure 2.1 2010-12-06 MK Draft version for internal review 2.1.1 2010-12-12 BR Version internally reviewed 2.1.2 2010-12-15 LSC Version internally reviewed 2.2 2010-12-13 MK Included comments from internal reviewer 2.3 2010-12-16 MK Included comments from internal reviewer

Date post:	27-Jul-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

Deliverable D8.3 Clients - Europa€¦ · SEVENTH FRAMEWORK PROGRAMME Challenge 1 ... 4 Brian...

Documents