TAS3_D8p1_v1p0.pdf

Software Documentation System: Repository services - Accepted by European Commission in June 2009. Executive Summary: This document provides the description of ‘Repository Services’ – a component of the TAS3 Trusted Application Infrastructure. Repositories are needed in TAS3 to store personal identifying information. Moreover, they need to be able to also store so called ‘Sticky Policies’ with those data items. The TAS3 Trusted Application Infrastructure is the application dependent part of the TAS3 infrastructure. Its purpose is to provide the services needed to realize the pilots of WP9 in the fields of employability and eHealth. The TAS3 Trusted Application Infrastructure depends on the requirements collected in WP1, the architecture design provided by WP2 and the business process models developed in WP3. It allows the application independent services developed in WP4, WP5 and WP7 to be used in the WP9 pilots. Most of the concrete technical solutions in this deliverable are inherited from deliverable 4.2. [1], which has a more generic view on Repositories. Within the TAS3 Trusted Application Infrastructure the ‘Repository Services’ component serves to store, protect and deliver PII1 (Asset Banks). This document describes • The Conceptual model - the assumptions on which the development of ‘Repository Services’ is based. • An evaluation of existing Open Source repositories and a description for a chosen TAS3 reference repository. • The services provided by ‘Repository Services’ and a description of its architecture. • Plans for the further development of the services in the next phase of the TAS3 project. NOTE: The software components produced in WP 8 implement application specific adaptors that are required to use the application independent TAS3 infrastructure in the TAS3 pilots in eHealth and eEmployability. The overall architecture, semantically enriched executable business process models with an XForms user interface and the design of the core TAS3 services are the pre-requisites for WP8. The TAS3 architecture has been finalized only recently (see D2.1). While all our results are consistent with and usable for the current TAS3 architecture it cannot be a surprise that some alignments and refinements will be required. Moreover new service needs, for example the request for a service bus, are emerging from the architecture document, which still need to be detailed before they can be implemented and documented in any of the deliverables of WP8. Technical Note: All produced components (web services, libraries and clients) of Deliverables D8.1., D8.2. and D8.3. can be found in a binary version at this location: http://citrix.uni-koblenz.de:9000/homepage/tas3/default.aspx Readers Guide To help the reader of this document to better understand its contents together with the other two deliverables of WP8 (especially Deliverable D8.2.), we provide this readers guide. Deliverables D8.2. is based on this deliverable D8.1. D8.1. has many references to D8.2., because D8.2. describes services that extend the repository services described in this document. Section 2 in D8.1. is the section that contains the conceptual model for TAS3 repositories. This conceptual model is then filled with flesh by section 4 and 5 from this document and section 2 in deliverable D8.2. The reader can use section 2 in D8.1. as a starting point for reading deliverable D8.1. and D8.2. Section 6 (applied software engineering methods) in this deliverable is optional and in an initial state, but we decided to leave it in the document, because this document is a software documentation and we have to document our applied software engineering methods.

TAS3_D8p1_Version1p0.pdf — PDF document, 1384Kb