Justification As users trust requirements may evolve or be different in new settingsthe trust management system should be flexible enough to supportnew sources of trust This includes new metrics for existing servicesbut also support for new trust services
ReqID D12-59Requirement The trust management system SHALL provide trust policy formula-
tion supportJustification The flexibility of the trust policies can make it difficult for the user
to write policies To aid the user in formulating policies we plan toprovide a policy wizard
Interaction Supports D14-51(a-e)ReqID D12-510Requirement The TAS3 architecture SHALL support user identificationJustification Links requesters recommendations and feedback etc to names
Interaction Supports all trust policy related requirementsReqID D12-511Requirement The legalcontractual framework SHALL support feedback data use
policiesJustification Data on which trust is based may itself be sensitive Technical pro-
tection is provided for some data such as credentials through trustnegotiation Protection of other data such as feedback on perfor-mance needs to be supported by contractpolicy which specifies theallowed usage of the (feedback) data Such contracts should con-form to new legislation in Europe that is being composed on scoringalgorithms
ReqID D12-61Requirement Intake Process (Person) The intake process MUST include docu-
mentation validation of identity and a technical user interfaceJustification We need to enroll people into the systemInteraction The Intake process reviews the execution of contracts compliance
ability and infratructure requirements To that end the intake processboth supports and is informed by all the other requirements (it pro-vides the evolution of the policies practices contract and ability tocomply of a prospective service provider)
ReqID D12-62Requirement Intake Process (organization) The intake process MUST include
documentation validation of identity verification of policies con-tracts and the capacity to comply as well as a technical user inter-face
Justification We need to enroll organizations into the system and review their in-frastructure and compliance capacity
Interaction The Intake process reviews the execution of contracts complianceability and infratructure requirements To that end the intake processboth supports and is informed by all the other requirements (it pro-vides the evolution of the policies practices contract and ability tocomply of a prospective service provider)
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 141 of 196
ReqID D12-63Requirement Notice When information is collected it MUST be specified what
information is collected how it is collected who it might be sharedwith how it will be used and how it will be managed
Justification Required by the DirectiveInteraction Notice encompasses all foreseeable uses and sharing In many
ways it is dependent on all the following topics and they are depen-dent on it All requirements depend on and support D12-63
ReqID D12-64Requirement Collection LimitationData Minimization The TAS3 system and re-
lated processes MUST have appropriate limits on personal data col-lection to what is needed for legitimate identified and noticed busi-ness function The system must be supplemented by policies thatare articulated that limit employee access to information based onbusiness need
Justification Required by the DirectiveInteraction This section is informed by notice and use (below) but is also related
to security in terms of data minimization depends on and supports63 Depends on 65 Supports 612
ReqID D12-65Requirement Purpose specification The purpose(s) for collection MUST be clearly
specified The collection related to those purposes must be relevantand non-excessive
Justification Required by the directiveInteraction This is relatedcodependent on notice and collection limitationdata
minimization Which means this is relevant to not only those groupsthat collect information but also those that use the information asthey must appropriately minimize the data as well as secure it andcontrol access Depends on and supports 63 Supports 64
ReqID D12-66Requirement Consent Use and subsequent use of personal data MUST be com-
patible with the purposes specified and MUST be with the consent1
of the data subjectJustification Required by the DirectiveInteraction Dependent on notice and purpose specification applies torequires
subsequent consent capture 66 abstracts 67 Depends on andsupports 63 and 65
ReqID D12-67Requirement Subsequent consent capture If the use of information changes or
if there is a new use of information there MUST be a subsequentcapture of information
Justification Required by the DirectiveInteraction Contingent on business model and cross dependent on notice and
use 67 implements 66 Depends on and supports 63 and 65ReqID D12-68Requirement Access request process there MUST be a process to enable users
to request access (and possibly amend or correct) to types of infor-mation that have been collected and sharing of information Implicitin this requirement is the need to know where data came from or wassourced
Justification Required by the DirectiveInteraction Related to Collection Limitation and Notice Depends on and support
64 and 63
1It should be noted that consent often bears important adjectives of clear unambiguous or explicit From atechnical point of view this requires that the user opt in to the collection of personal information
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 142 of 196
ReqID D12-69Requirement Compliant capture system Potential abuses to the system or con-
cerns of either users or organizations MUST be capturedJustification Emanates from requirements of the Directive The directive specifies
that a person must be able to complain which is not the same as aspecification of a complaint handling system
Interaction Should reflect the major elements of these requirements may alsobe joined to access mechanism Has to support all requirementswhich could be basis of compliant is also a proof element of 61
ReqID D12-610Requirement Redressoversight Processes Once a compliant is captured redress
MUST be possible Oversight process is a proactive version of thisconcept
Justification Emanates from requirements of the DirectiveInteraction Interdependent with all of the major elements of these requirements
in terms of oversight specific to breach or harm in terms of redressThis will be defined in legal but may require a BPM process to bemade effective Audit information in redress is required as a proofelement and is essential to oversight depends on all proof elementrequired by 61
ReqID D12-611Requirement Confidentiality Controllers and processors MUST have duties to
maintain confidentiality of information In some cases this will meanencryption especially in the UK
Justification Required by the DirectiveInteraction Horizontal requirement that attaches to use management and stor-
age of data Everything across the project that touches PII has thisrequirement including all aspects of legal It also supports D12-612
ReqID D12-612Requirement Security Appropriate security (technical and organizational) mea-
sures against unauthorizedunlawfulaccidental access modificationdisclosure destruction loss or damage to personal data MUST bein place
Justification Required by the DirectiveInteraction Horizontal across requirements as well as all entities involved in de-
velopment and operationsReqID D12-613Requirement Contract execution All participants to the TAS3 system MUST exe-
cute the appropriate TAS3 contract documentsJustification Required to enable a contract framework that binds all parties to the
use of appropriate technologies and the rights and obligations ap-pertaining to the transactions and uses of information
Interaction Depends on D12-614 D12-615 D12-616 D12-617ReqID D12-614Requirement Use of TAS3 Technology and Processes According to the contract all
parties MUST agree to use the appropriate TAS3 or TAS3 compatibletechnology and processes
Justification This is required to assure that all parties can exchange informationand engage in transactions in a compatible and secure manner
Interaction Supports D12-613ReqID D12-615Requirement Implementation of Required Policies According to the contract or-
ganizational participants in the TAS3 infrastructure MUST implementTAS3 defined or compatible policies specified in the contract
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 143 of 196
Justification The contract framework is dependent on the need for appropriatepolices to support both the technology and the legal obligations setforth in the EU Directive and other applicable laws
Interaction Supports D12-613ReqID D12-616Requirement Agreement to be bound According to the contract all parties MUST
agree to be bound to the obligations they take on both as part ofthe TAS 3 infrastructure and as a result of transaction or choicesexercised through the TAS3 Architecture
Justification In order to give effect to the legal requirements of the Data Protec-tion Directive and other applicable laws all parties must agree tobe bound by both the infrastructure obligations as well as those thatarise through use of or transactions over the TAS3 architecture
Interaction Supports D12-613ReqID D12-617Requirement Binding Effect of technical processes All parties MUST agree to
be bound by the technical processes in the architecture to the extentthat they are working properly and have been appropriately disclosedand consented to
Justification The TAS3 architecture provides technical components that enhancetrust and facilitate transactions such as sticky polices The contentof the instructions contained in these policies or other technical com-ponents and the obligations associated with those instructions mustbe respected across the TAS3 architecture
Interaction Supports D12-613
C7 Requirements of WP7
ReqID D12-71Requirement A user sometimes needs to be able to authorise another user or
service to act on his behalfJustification A user needs to delegate to a portal to act on his behalf (step 7 of
the use case 2 in [22] Delegation from the user to the portal) Auser needs to delegate to his employer to access his eportfolio (step9 of use case 1 in [22] The employee authorizes his employer (HRmanager) to access the showcase of his ePortfolio)
Interaction Depends on D12-79 and implements D12-76ReqID D12-72Requirement Users sometimes need to be able to sign documents using their
rolesJustification It is a necessary functionality in step 8 of the use case 2 and step 6
of use case 1 Role based signing is requiredInteractionReqID D12-73Requirement The user must be able to prove who he is to any service and also be
sure that he is talking to the correct serviceJustification It is a necessary security need in step 1 of both use cases Mutual
authentication and authorisationInteraction Supports D12-716ReqID D12-74Requirement A user may need to present several authorisation credentials in order
to obtain a service eg a credit card and a club membership cardJustification It is a necessary functionality in step 2 of the use case 2 Attribute
aggregation of credentials
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 144 of 196
Interaction This is related to Requirement D12-75 but orthogonal to it WhilstD12-74 is stating that multiple credentials from multiple issuers maybe needed D12-75 is saying that each credentials should be re-leased incrementally even if they come from the same issuer HenceD12-74 depends on D12-75 and implements D12-76
ReqID D12-75Requirement Users should only need to provide the minimum of credentials that
are needed to obtain a service and no moreJustification It is a necessary condition in step 2 of the use case 2 and step 3 of
use case 1 Minimum of credentials in order to RegisterInteraction This is the user pushing his minimum credentials to a service
provider It is related to requirement D12-717 as the system mayuse similar mechanisms to accomplish both requirements D12-75hence depends on D12-717 supports D12-74 and implementsD12-76
ReqID D12-76Requirement Users must have the authorisation to perform any actionJustification It is explicit in step 1 of the use case 1 and implicit in most stepsInteraction This is a very generic high level requirement and abstracts require-
ments D12-71 D12-74 D12-75 D12-79 D12-710 D12-712D12-713 D12-715 D12-717 D12-724
ReqID D12-77Requirement Users should be able to dynamically set their privacy policiesJustification Its in step 2 of the use case 1 Set the userrsquos privacy policy for Per-
sonal Identifying Information (PII) and consent to use this PII andstep 3 of use case 2
Interaction Depends on D12-719 and supports D12-726ReqID D12-78Requirement Different service providers should not be able to collude together to
determine who a pseudonymous user is without the users consentJustification Service providers could jointly profile the user Related to step 4 of
use case 1Interaction May conflict with Requirement D12-718ReqID D12-79Requirement Credentials should be revocableJustification If a user delegates his credential to another person or process he
must be able to revoke this delegation if either the delegate abusesits privileges or the user changes his mind
Interaction Supports D12-71 and D12-714 and implements D12-76ReqID D12-710Requirement Credentials should be targetable to a specific relying partyJustification A credential owner does not wish a credential receiver to use the
credential on his behalf It is related to step 4 in use case 1Interaction implements D12-76ReqID D12-711Requirement The system must support the merging and enforcement of multiple
policiesJustification It is in step 5 of use case 1InteractionReqID D12-712Requirement The system must be able to pull additional user credentials on de-
mandas requiredJustification It is in step 6 and 7 of use case 1Interaction Depends upon D12-713 Supports D12-715ReqID D12-713
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 145 of 196
Requirement The system must be able to determine where to pull additional cre-dentials from
Justification It is in step 6 of use case 1Interaction Supports D12-712 and implements D12-76ReqID D12-714Requirement One service provider should be able to subcontract (delegate) to an-
other service provider to get work done on behalf of the original userJustification Another instance of delegation of authority this time service to ser-
viceInteraction This is similar to D12-71 only it is system to system rather than
person to person It may depend on D12-79ReqID D12-715Requirement Users should be able to push their credentials to the system dynam-
ically when more are neededJustification Step 3 of use case 2 Consent to collect additional PII or ask user to
provide itInteraction Supports D12-712 The authorisation system should be able to pull
user credentials and accept pushed user credentials and these mayneed to be supplemented at any time with additional user creden-tialsemphimplements D12-76
ReqID D12-716Requirement User should be able to use different pseudonyms in order to protect
their privacyJustification Step 3 of use case 2 User must be able to act with different personas
with different vacancy profilesInteraction May depend on D12-73ReqID D12-717Requirement Credentials should be incrementally released as trust is establishedJustification Step 4 of use case 2 Find possible Service Providers that provide
the right sort of jobs via the portal Find out which are trustworthyNeither party must reveal too much information about themselves
Interaction May use similar mechanisms to D12-75 as this requirement re-quires both the user and the remote service provider to push theminimum of their credentials to the other party It implements D12-76
ReqID D12-718Requirement A service provider should not be able to link together the sequential
requests of a user without the users consentJustification Services should not be able to profile users without their consentInteraction may conflict with D12-78ReqID D12-719Requirement Service providers should be able to update their policies dynamically
without having to bring down the systemJustification Service providers often need to be able to provide 2424 provision of
service and bringing the system down to change the policy is not fastenough or pro-active enough
Interaction Supports D12-77 in that a user policy may be one of the SPs poli-cies so D12-719 must be met before D12-77 can be fulfilled
ReqID D12-720Requirement Service providers should be able to distribute policy administration
between multiple administratorsJustification Different administrators have different skills and knowledge and
therefore are more competent to set particular polices Furthermoreit can be too big a job for anyone person to do
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 146 of 196
Interaction Could support Requirement D12-72 by having role based signingof policies
ReqID D12-721Requirement The system needs to be resilient to fraud or mistakes by users and
administratorsJustification Organisations have a legal duty of care to prevent fraudInteractionReqID D12-722Requirement The authorisation system needs to have an escape mechanism in
emergencies (so called break the glass policies)Justification For example when a patient is taken unconscious to an emergency
department and has not authorised the doctor on duty to access hispersonal health records the doctor may need to get access to thisregardless of the patients policy
Interaction Depends on D12-723ReqID D12-723Requirement The authorisation system needs to be able to make decisions based
on the current state of the application andor systemJustification Systems are naturally dynamic and authorisation systems need to
be able to cater for thisInteraction Supports D12-722ReqID D12-724Requirement The authorisation system should securely recordaudit the decisions
that have been made in a tamperproof and confidential mannerJustification Auditors and criminal investigators may need access to these events
post-facto and they need to be assured that the logs have not beentampered with
Interaction Supports D12-725 implements D12-76ReqID D12-725Requirement Auditing needs to be dynamic and adaptive to changes in the system
andor environmentJustification If the system detects an attack then the level of auditing should au-
tomatically increaseInteraction Depends on D12-724ReqID D12-726Requirement A user must provide consent for the use of his private data and cre-
dentialsJustification It is part of data protection legislation and in step 2 of the use caseInteraction Depends on D12-77ReqID D12-727Requirement Sensitive tasks must be split between multiple usersJustification Separation of duties is a well known procedure for ensuring the se-
curity and safety of sensitive tasks It is also required by the businessprocess managers in WP3
Interaction
C8 Requirements of WP8
ReqID D12-81Requirement The pilots MUST have a gateway to access the TAS3 infrastructureJustification Either the requesting applications or the providing or responding ap-
plications shall be able to access TAS3 over a unified interface Bythis it is also possible that other applications in the future can beeasily integrated into TAS3
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 147 of 196
InteractionReqID D12-82Requirement Legacy databases SHALL be able to provide their data and service
to TAS3Justification TAS3 shall be open for legacy systems like legacy databases To
provide such an easy way of integration there must be an interfaceespecially for legacy databases
Interaction Depends on D12-81 which specifies the ADPEPReqID D12-83Requirement An end-user SHALL be able to access TAS3 functionality through a
business processJustification Many workflows in organisations use a business process engine to
keep track of the workflow or business process Since TAS3 legit-imized service providers are part of these workflows they shall beeasily integrated into the business process
Interaction Depends on D12-81 which specifies the ADPEPReqID D12-84Requirement An end user SHALL be able to access TAS3 services through a spe-
cial TAS3 generic client without having to use a complete BusinessProcess Engine
Justification Not in every case the user accesses TAS3 through a business pro-cess engine Other possible clients are smart phones web front-endor fat clients To also support these types of clients we need a moregeneric client
Interaction Depends on D12-81 which specifies the ADPEPReqID D12-85Requirement An end user SHALL be able to access and manage herhis policiesJustification TAS3 user will get into contact with different layers of policies Poli-
cies may be user centric organisational or even TAS3 wide For usercentric policies the user needs a special front-end and back-end tomanage herhis policies
Interaction Depends on D12-81 which specifies the ADPEPReqID D12-86Requirement An end user SHALL be able to store and modify its data in a reposi-
tory for person related data This repository has to be reachable in aTAS3 secured and trusted way
Justification Among other things TAS3 is about storing and exchanging personrelated data in a secure and trusted way To store such data weneed special TAS3 adapted repositories
Interaction
C9 Requirements of WP9
ReqID D12-91Requirement Processes MUST have secure access to data drawn from a variety
of distributed sources but only be able to access the data they needJustification This is needed to ensure the efficiency and security of the process
accuracy and support for data protection requirementsInteractionReqID D12-92
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 148 of 196
Requirement Users MUST be able to set view control and change policies fortheir data at a variety of levels down to the lowest (field) level fromaccepting clearly-formulated pre-set policies to adding fine-grainedpolicies to specific sets of data they must clearly understand theimplications of this policy choice
Justification This is needed for the user to exercise control and to comply withprivacy legislation Users will want the same data to be used in avariety of processes so may want to add context-specific policies tohow it will be used
Interaction Supports D12-91 D12- 94 D12-96 Depends on D12-93ReqID D12-93Requirement Users MUST have easy and easily-understood access to the sys-
tem without the need for overly-complex authentication and autho-rization processes preferably via SSO
Justification This is necessary to support users support for the system if it istoo complex to access they will not use it unless they have to or willtake measures to simplify access that may compromise security (egwriting down passwords) however they also have to feel trust in thesystems security
Interaction Supports D12-92 D12-94 D12-913ReqID D12-94Requirement Users MUST be securely authenticated and authorised before any
access to data is allowedJustification The system needs to know that only appropriate access is being re-
quested and users must be matched against the correct sets of dataThis complies with legal and ethical requirements and is protectionagainst fraud There needs to be a provision for different levels ofauthentication and trust
Interaction Supports D12-91 D12-95 Depends onemphAbstracts D12-93ReqID D12-95Requirement There MUST be a secure and reliable audit trail showing who ac-
cessed user PII when and for what purpose and whether anychanges were made and this audit trail must in turn be secure andonly accessible by authorised individuals or service providers
Justification Necessary for investigation of breaches of security or any official en-quiry especially into breaches of data protection legislation or sus-pected fraud This is an administrative tool rather than the userinterface
Interaction Depends on D12-92 D12-94 Supports D12-98ReqID D12-96Requirement Users MUST be able to set specific policies for all possible data-
requesters from highest level (country) down to the lowest level(named actor) including accepting clearly-formulated pre-set poli-cies for common data-requesters they must clearly understand theimplications of this policy choice
Justification This is one of the main objectives and USPs (unique selling points)of TAS3 for users This should also allow for combinations of policiesand include a mechanism for when different policies are interactingat the same time
Interaction Supports D12-92 Depends on D12-93 D12-94ReqID D12-97Requirement Users MUST be able to check (read) their personal data stored in all
possible data stores connected to the TAS3 infrastructure and con-test any that they feel is inaccurate
Justification Users have the legal right to know from the system what data isstored about them and to challenge it if it is incorrect
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 149 of 196
Interaction Depends on D12-91 D12-93 D12-95ReqID D12-98Requirement Users MUST be able to see who has requested access to which of
their PII data and whether or not access was grantedJustification Users trust in the system depends on this it is the main reason for
them to engage with TAS3 They also have the legal right to knowwho has had access to personal data
Interaction Depends on D12-95 D12-94 Supports D12-92ReqID D12-99Requirement Users MUST be able to change the policies attached to their PII data
at any timeJustification User requirements and situations may change and the policies for
their data may change with them Evolving legal requirements alsomake this a necessity Includes interactive changes such as re-sponses to consent questions
Interaction Depends on D12-92 D12-96ReqID D12-910Requirement The policy management user interface MUST meet the highest
known current standards (complying with current best practice oninterface design w3c guidelines)
Justification Policy setting is a complex task and the implications of decisionsmade should be very clear to the user The policy interface is themain interface for users and thus the showpiece of TAS3 most of therest of the exchanges is performed by back office systems Usersfrom a variety of different social backgrounds and educational levelsshould be able to work easily with this interface To comply with UKSENDA legislation any user interface must adhere to strict accessi-bility guidelines
Interaction Supports D12-92 D12-93 D12-96 D12-98 D12-99ReqID D12-911Requirement Interoperability between different systems MUST be established to
exchange and share data This includes interoperability betweencredential providers
Justification Not all systems used in the pilots use the same standards formatstables or fields As the system will be web-based we need to ensurethat all legacy systems are web-service compliant and build in anynecessary interfaces to support interoperability which is not currentlyin place Any existing mandatory security mechanisms must be en-compassed Service Providers need to be able to provide data in aform that can be accepted by a Service Requester
Interaction Supports D12-91 D12-93ReqID D12-912Requirement Persistent and unique electronic means of identification MUST be
provided for usersactors of the TAS3 infrastructureJustification The system must be able to consistently uniquely and positively
identify all usersactors within the TAS infrastructure to ensure dataintegrity and correct levels of access permission
Interaction Supports D12-93 D12-94 D12-95ReqID D12-913Requirement Actors (data-requesters service providers) MUST be able to connect
to the TAS3 infrastructure in a secure way using varying levels ofauthentication and trust
Justification This is necessary to provide services access to the TAS3 infrastruc-ture and preserve confidentiality of data
Interaction Depends on D12-91 Supports D12-93
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 150 of 196
ReqID D12-914Requirement Back office services must be invisible to the userJustification While users must be able to know and verify how their data has been
used this needs to be done seamlessly users do not need to seethe internal workings of the system
Interaction Supports D12-93 Depends on D12-911ReqID D12-915Requirement TAS3 specific processes must not adversely affect performance or
add complications to existing processes from the users viewpointJustification For users the overall process must remain smooth speed and per-
formance must not be impaired by the trust and security processesIf additional complications and extra steps are added users are likelyto bypass or ignore them
Interaction Supports D12-93 D12-914ReqID D12-916Requirement Data within the ecosystem SHOULD not be copied or duplicated it
should be stored once used many timesJustification Copying data leads to version control issues issues with deletion
and issues with auditing and journalingInteraction Depends on D12-91
C10 Requirements of WP10
ReqID D12-101Requirement The TAS3 architecture MUST support perpetual (ie event-driven
periodical) and automated compliance testing of servicesJustification Service-oriented applications are characterized by great dynamism
eg service implementations and service bindings may change atruntime In the reference scenarios the services (instances) thatparticipate in the interaction may change independently and withoutinterrupting the service provision (eg a new implementation of afunctionality can be deployed the quality of the new implementa-tion needs to be assessed dynamically) Testing strategies that arebased only on offline techniques are therefore inadequate and in factimplementing run-time checking mechanism is generally recognizeda best practice in service-oriented settings
Interaction Depends on D12-108 in that continuous automatic testing requiresprecise models to be available for each service involved in a chore-ography
ReqID D12-102Requirement The TAS3 infrastructure SHALL detect service failures in granting or
denying access to resources with respect to their manifested policiesJustification This kind of failures is especially critical as the trustworthiness of
TAS3 heavily depends on proper handling (management and en-forcement) of policies
Interaction Depends on D12-108 this requirement can only be fulfilled if poli-cies are manifested by services as part of their specification
ReqID D12-103Requirement In a TAS3 choreography error messages returned after a request of
a resource (eg ldquoaccess deniedrdquo message) MUST be identifiable assuch eg through a special flag in the message header
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 151 of 196
Justification Applications might masquerade error messages for user-friendliness(eg they could produce a ldquopretty formattedrdquo page) nonetheless theTAS3 architecture needs to be able to unambiguously recognize errormessages without the need to delve into the semantics of the pay-load of the message If we consider for instance the APL scenariocertain operations (such as accessing data or using functions) mustbe allowed only upon exhibiting corresponding credentials (eg tofill-out portfolio information or to read certain portions of a portfolio)
Interaction Supports R101 as test automation needs an oracle to determinethe successfailure outcome of a test execution
ReqID D12-104Requirement Demonstrators SHALL provide good levels of end-user perceived
trustJustification The success of any information system architecture must be based
not only on technology schemes standards and protocols but alsoon usersrsquo perceptions We need to assure that TAS3 services areimproved in terms of perceived trust
Interaction Depends on D12-105 D12-106ReqID D12-105Requirement Demonstrators SHALL provide good levels of end-user perceived
service qualityJustification The success of any information system architecture must be based
not only on technology schemes standards and protocols but alsoon usersrsquo perceptions Thus we need to assure that TAS3 ser-vices are improved in terms of perceived service quality from a non-technical perspective
Interaction Supports D12-104 D12-106 D12-107ReqID D12-106Requirement Demonstrators SHALL provide good levels of end-user perceived us-
abilityJustification Usability is one of the most important validation issues for TAS3 ar-
chitecture It is necessary to assure that TAS3rsquos services achievegood usability levels
Interaction Supports D12-105 D12-104 Depends on D12-107ReqID D12-107Requirement Demonstrators SHALL provide good levels of accessibilityJustification According to several EUrsquos agreements accessibility must be consid-
ered especially in the case of public services (eg health) Thusaccessibility must be analyzed and taken into account in TAS3rsquos ser-vices
Interaction Supports D12-106ReqID D12-108Requirement Services that are to participate in a TAS3 choreography MUST be
accompanied with models describing their characteristicsJustification These models are part of a TAS3 ldquogovernance contractrdquo and consti-
tute the basis on which the services are verifiedInteraction Supports D12-101 D12-102 and D12-109ReqID D12-109Requirement All services willing to participate in a TAS3 choreography SHOULD
be validated against the accompanying models
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 152 of 196
Justification Mandating that service characteristics (eg their behaviour theirextra-functional characteristics) be documented enables a numberof (automated rigorous) validation activities that are key to enhancethe trustworthiness of services In both the reference scenarios allparties that interact should have gone through a preliminary valida-tion phase Furthermore the outcome of this validation can also beused when selecting providers based on their trustworthiness (egat step 3 of the APL scenario as well as at step 4 of the ML scenario)The type of validation and the extent to which such validation can becarried out depends on what information is included in the modelsattached to the services
Interaction Depends on D12-108 which mandates that services that are toparticipate in a TAS3 choreography must be accompanied by speci-fications
C11 Requirements of WP12
ReqID D12-121Requirement All developers testers and users MUST understand significant parts
of the complete system at least at the conceptual levelJustification TAS3 fundamentally secures business processes end to end Iso-
lated components may provide a tiny part of the end-to-end securitybut are still part of a chain or mesh that can break Knowledge out-side the component focus is required ahead of time so that expen-sive basic design mistakes can be avoided
Interaction Depends on D12-122ReqID D12-122Requirement All developers testers and users MUST have access to all project
documentation regardless of origin target audience or assumed rel-evance
Justification The scope of the project is too wide to predetermine which peopleneed what document so the distribution is going to be pull instead ofpush
Interaction Supports D12-121ReqID D12-123Requirement Project participants MUST be left free to choose when and how to
perform their contractual duties within reasonJustification TAS3 for nearly no participant is a 100 workload Care needs to
be taken that no process is pushed onto the participants that woulddictate their daily work process which takes place in another organi-sation
InteractionReqID D12-124Requirement A hierarchical escalation structure MUST be in place to raise im-
portant andor urgent events to organisational levels above non-responsive ones
Justification When reasonable limits on timeresource allocation flexibility are ex-ceeded and project progress is threatened other partners daily op-eration may need to be altered
Interaction Supports D12-123ReqID D12-125Requirement All developers and testers MUST maintain their component docu-
mentation in a central repository that at the very least MUST be cur-rent for software that has been released outside the developers lab
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 153 of 196
Justification When any developer tester or user wants insight in what a compo-nent does (s)he needs to be able to directly get the answer
Interaction Supports D12-121 D12-122ReqID D12-126Requirement E-mail as message system andor dissemination system MUST be
reduced as much as practical and replaced by on-demand (pull) sys-tems
Justification Twofold it is often not possible to determine for exactly which peoplea message is important or will become important yet broadcast to allis no option and most people already receive too many messagesso that the message would be likely lost anyway
Interaction Supports D12-122 D12-123 D12-124ReqID D12-127Requirement Released components MUST be checked and re-checked for correct
operation in the network environment and developers MUST be keptup to date as of the performance of their released component
Justification Even when a component adheres exactly to the specifications it mayhappen that situations arise where the specifications turn out to bewrong or incomplete Unit tests are only run in isolation Continuousintegration has the power to reveal integration problems at an earlystage
Interaction Depends on D12-124ReqID D12-128Requirement A controlled environment MUST be available to perform complex use
cases and abuse cases of components in an orchestrationJustification Situations will arise where unexpected events such as component
failures or unspecified environmental conditions interfere with a setof components Due to complex relationships and cause-and-eventpatterns problems may appear which are hard to create or foreseein isolated unit testing It needs to be demonstrated that the orches-tration is resilient to intentional abuse
Interaction Supports D12-127ReqID D12-129Requirement Components MUST be configurable in such a way that they inten-
tionally perform in abnormal waysJustification To fully test a constellation for resilience against malfunctions com-
ponents must be exposed to failing peers We do not want to specif-ically develop mock components just for abuse testing when the realthing is available and ldquoknowsrdquo exactly what nasty failure modes itwould have
Interaction Supports D12-127ReqID D12-1210Requirement Multiple controlled environments SHOULD be available to rig parallel
use and abuse setups with different components andor configura-tions
Justification It is cumbersome to schedule tests on one central rig and tell devel-opers to postpone testing until the rig has the right configuration in aspecific time window
Interaction Supports D12-127ReqID D12-1211Requirement An automated process SHOULD be available that allows hands-off
setup of a complete controlled environment in a pre-defined configu-ration running a set of use and abuse cases and report the results
JustificationInteraction Supports D12-127
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 154 of 196
ReqID D12-1212Requirement Components MUST come with a sub-component (ldquoinstallation
scriptrdquo) which allows partial automation of the installation and con-figuration of the component
Justification With the central useabuse rig central to the project there is no ex-cuse to rely on written textual material for very regular routine in-stallation and configuration procedures Given the controlled envi-ronment assumptions may be made about available resources andlocations that in a more generic case would need to be left to theinstalling person
Interaction Supports D12-1211ReqID D12-1213Requirement Users MUST be able to verify that a constellation of components
behaves according to their specificationsJustification TAS3 aims to demonstrate usability in user scenariosInteraction Depends on D12-128
Supports D12-1215ReqID D12-1214Requirement Specific test scenarios MUST be made available to automatically test
constellations of componentsJustification Without automation testing remains a one-off event that cannot be
used to continuously validate the quality of a constellation in produc-tion
Interaction Implements D12-1213ReqID D12-1215Requirement Users MUST be able to validate that a constellation of components
behaves according to their scenarioJustification TAS3 aims to solve user problems expressed in scenarios but we
need to make sure that the scenarios are correctly specifiedInteraction Depends on D12-1213ReqID D12-1216Requirement Most procedures and automated functions required for the test bed
MUST allow to be carried over to a production situation for perma-nent constellation monitoring
Justification TAS3 Quality of Service requirements assume continuous monitoringof the working system to provide KPI for quality assessment andtrust perception
InteractionReqID D12-1217Requirement All components MUST come with documentation according to es-
tablished standards and MUST follow an established delivery proce-dure
Justification To facilitate integration and production setup modules need to beroutinely handled by people not necessarily knowing the particulardetails of each module This holds both for externally provided andin-house manufactured components
Interaction Supports D12-125Abstracts D12-1212
ReqID D12-1218Requirement All external components used in TAS3 MUST have proper documen-
tation and installation procedures available and one responsible part-ner per component MUST keep them current
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 155 of 196
Justification It cannot be left to the integrator or production maintainer to takeon the burden of finding out exactly how one of the project partnerswants to set up an external component And more than one partnermay need a conflicting setup Component ownership
InteractionReqID D12-1219Requirement All components MUST come with documentation broken down in
sections or reading guides for 1 component developers 2 peercomponent developers 3 system administrators 4 users and 5user managers
Justification People at all levels may need to refer to the module Providing thisindex is little work for people familiar with the component and impos-sible for newcomers Having a clear management summary meansoverall trust in the system may improve
Interaction Implements D12-122ReqID D12-1220Requirement Training sessions for developers and system managers MUST be
providedJustification It cannot be expected from all people that they can without training
pick up and learn the important (security and business) aspects ofall components Expert help is required
Interaction Implements D12-121ReqID D12-1221Requirement Change management MUST be enforced on core integration re-
sourcesJustification Where changes have the potential to cause far-reaching conse-
quences not necessarily apparent to the changer we need to man-age the change proposal
Interaction Supports D12-122 D12-124 D12-126Conflicts with D12-123Abstracts D12-125
ReqID D12-1222Requirement Short medium and long term planning MUST be provided for the
component developers to set their prioritiesJustification The project-wide deliverable plan is too coarse to suggest daily
weekly and monthly development activities especially with respectto the interactions between components from different developersand the advancing insight gained during the project
Interaction Supports D12-121 D12-123Implements D12-124
ReqID D12-1223Requirement A single central place MUST be available where all known issues
and defects of all components are administratedJustification With the projects focus on integration even individual component
developers need to be very aware of problems with their componentoutside the laboratory And users of the component (peer develop-ers) must be aware of problems with their peer component even ifthey have not encountered them yet
Interaction Supports D12-122 D12-126 D12-1221Conflicts with D12-123
ReqID D12-1224Requirement One resource MUST be available which authoritatively lists all avail-
able and required components external and internal uniquely iden-tifiable throughout their life cycle
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 156 of 196
Justification For project planning and progress monitoring a current overview ofthe purpose status and use of all components needs to be main-tained
Interaction Supports D12-121 D12-1223ReqID D12-1225Requirement As part of a component catalog an interface catalog MUST be cen-
trally availableJustification Not all components are designed to talk to all other components
Designed or planned peer components share one interface whichmust be documented where possible ahead of implementation
Interaction Supports D12-1222ReqID D12-1226Requirement At least one reference constellation SHOULD be available which al-
lows application-independent components to be integration-testedwithout a specific demonstrator scenario
Justification It can be expected that application-dependent modules put less de-mand and stress on an infrastructural component than what the in-frastructural component was architecturally designed to cope with
Interaction Supports D12-127ReqID D12-1227Requirement A common reference system MUST be available to uniquely identify
data object types cross-applicationJustification Policies are used to specify what is allowed to happen with data
Unknown data types mean the data is not allowed to be stored orprocessed and must be rejected It is unlikely that any top-downstandard will develop soon which unifies data types Applications canbi-laterally agree on data types by using unique identifiers allowingsuccesfull forwarding of data and policies even if the data format itselfis as yet unprocessable
InteractionReqID D12-1228Requirement A transformation service SHOULD be available to help applications
use data which is not natively known to themJustification If parties have bi-laterally agreed on a unique data type they can
forward each others data while maintaining trust and privacy rulesBy adding transformations they can also process and manipulatethe data according to trust and privacy rules
Interaction Depends on D12-1227ReqID D12-1229Requirement On request developers MUST release a component which conforms
to the standard framework (documentation installation procedureinterface specification) even if this means releasing a mockup com-ponent without real functionality
Justification Peer developers often need to use a stub component to test theirown component Instead of developing the same stub over and overagain it is much more effective and efficient to have an early non-functional release of the actual component
Interaction Supports D12-1222 D12-1223ReqID D12-1230Requirement Central resources MUST be updatable by all relevant peopleJustification TAS3 is too small a project to allow dedicated full-time support staff
When a central resource is found being inadequate or in error ev-erybody relevant to the resource should be able to change it Theresource editor then can after the fact inspect the change and pos-sibly undo it or re-change This avoids resource update bottlenecks
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 157 of 196
Interaction Supports D12-123 D12-124 D12-125
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 158 of 196
D Existing SolutionsThe following is the list of software that provide existing solutions to some of the solved problems in TAS3
Solutions that solve the same problem that provide alternative solutions are listed in a single table one after theother Every separate table is another solution that will be adopted by the partners in TAS3
The following includes the complete list of existing solutions that will be used by WP 34578910 and 12The VUB team in WP2 has also provided us with existing solutions The solutions that will be utilized by theArchitecture team is included in Deliverable 21 [18]
Name of Solution Intalio Designer BPMS and TempoLink httpwwwintalioorgAccess open sourceopen standardFunctionality Graphical Process Modelling Tool based on BPMN
(Business Process Modelling Notation) allows to de-ploy BPEL processes which can be executed by Intal-ioBPMS Intalio Tempo is a enhancement of the IntalioSuite which supports human activities
Limitations with respect to TAS3 Open source part does not include XForms editor datamapper transformation into BPEL and automatic de-ployment IntalioBPMS does not support security is-sues like authorization access rules and their en-forcement Adaptation is only supported in a simpleform ie change a web service before its call withoutnewly deploying the process Tempo does not yet sup-port federated identitySSO
Related Requirements Fulfills D12-31 through D12-33 partially fulfills D12-34
Justification of Selection In main parts it is open source software Intalio pro-vides graphical modeling as well as process executionengine and integrates both parts The process model-ing tool together with human activities is a very com-prehensive and comfortably usable tool
Name of Solution Oracle BPM-SuiteLink httpwwworaclecomtechnologiesbpm
bpm-suitehtmlAccess proprietaryFunctionality Business Process Modelling and Management in a
SOALimitations with respect to TAS3 Not open source software not sufficient support of pro-
cess adaptations and process securityRelated Requirements Fulfills D12-31 through D12-33 partially fulfills D12-
34Name of Solution IBM Web Sphere Integration DeveloperLink httpwww-306ibmcomsoftware
integrationwidAccess proprietaryFunctionality Business Process Modelling and Management in a
SOALimitations with respect to TAS3 Not open source software not sufficient support of pro-
cess adaptations and process securityRelated Requirements Fulfills D12-31 through D12-33 partially fulfills D12-
34Name of Solution ActiveBPEL Community Edition EngineLink httpwwwactivevoscom
community-open-sourcephp
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 159 of 196
Access ProprietaryFunctionality Business Process Modelling and Management sup-
porting BPEL (Business Process Execution Language)Limitations with respect to TAS3 Not open source software not sufficient support of pro-
cess adatations and process securityRelated Requirements R31 through R33Name of Solution jBPMLink httpwwwjbosscomproductsjbpmAccess Open sourceFunctionality Business Process Modelling and ManagementLimitations with respect to TAS3 Lack of inherent web service support not sufficient
support of process adaptations and process securityno enhanced support for human activities
Related Requirements fulfills D12-31 fulfills D12-32 and D12-34 with limi-tations
Name of Solution PERMISLink httpseccskentacukpermisAccess open sourceopen standardFunctionality - Allows one user to dynamically delegate access right-
spermissions to another user and allows a process tobe split into two or more tasks that have to be under-taken by different entities (eg manager and clerk)- Has a PDP and a CVS Allows credentials to be pulledor pushed Supports separation of duties and statebased decision making Supports delegation of au-thority Has an XACML interface to the PDP SupportsXACML formatted obligations
Limitations with respect to TAS3 - Based on using X509 ACs stored in LDAP directoriesStart up can be time consuming if large audit trails arepresent- Originally build to support authorisation credentialsencoded as X509 attribute certificates Currently onlyhas limited support for SAML formatted attribute asser-tions (eg Delegation only works with ACs and not withSAML assertions)- The policy language is not standardized- Is purely RBACABAC based though could be ex-tended to support DAC
Related Requirements Fully fulfilled D12-76 D12-79 D12-724 Partially ful-filled D12-35 D12-36 D12-71 D12-72 D12-712-15 D12-721 D12-723
Justification of Selection - Open source software based on XACML-Has more required functionality than any other pack-age Is modular and allows plug and play with anXACML PDP
Name of Solution KULeuvens demonstrator frameworkLink To be providedAccess open source
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 160 of 196
Functionality Demonstrator framework that is able to illustrate theTAS3 concepts It currently provides a proof-of-conceptimplementation of the following TAS3 concepts break-the-glass policy enforcement user friendly policymanagement transparency of executed business pro-cesses secure communications
Limitations with respect to TAS3 The service provider discovery mechanism of thedemonstrator framework does not yet support trust andprivacy policy negotiation
Related Requirements D12-21 D12-25 D12-26 D12-37 D12-105D12-121
Justification of Selection The demonstrator framework is proven technology thatcan easily be extended During the first year of TAS3 the demonstrator framework has been extended withsupport for complex business processes the break-the-glass function and advanced policy enforcement
Name of Solution Belgian e-ID cardLink httpeidbelgiumbeAccess open source and proprietary for Belgian citizensFunctionality authentication mechanism used as a token that sup-
ports client authenticationLimitations with respect to TAS3 no limitations specific to TAS3
Related RequirementsJustification of Selection It is the authentication token that has the highest level
of assurance that is currently available in the consor-tium
Name of Solution Encryption Algorithm AESLink httpcsrcnistgovpublicationsfips
fips197fips-197pdfAccess open sourceFunctionality encryption and decryption of dataLimitations with respect to TAS3 no limitations specific to TAS3
Related RequirementsJustification of Selection It is a standard encryption algorithm
Name of Solution Tulip Trust Management systemLink httpdiescsutwentenl˜czenkom
tulipdocAccess open sourceFunctionality Credential based trust management systemLimitations with respect to TAS3 Credential based trust management only no support
for other trust metrics Does not use the TAS3 trustservice methodology
Related Requirements D12-56Justification of Selection Compared to other existing CTM systems TuLiP excels
in key aspects for TAS3 flexibility of the syntax userauthonomy and automation
Name of Solution PostgreSQL
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 161 of 196
Link httpwwwpostgresqlorgAccess Open sourceFunctionality Relational database Can be used to gather reputation
feedback information and make it available to the repu-tation based trust management engine
Limitations with respect to TAS3 Does not provide complex operations required forbehaviour-based trust policies Not yet a web serviceNo support for integrity of information Possibly re-quires strict access controls to prevent rigging of dataDoes not support users privacy policies
Related Requirements D12-53 D12-54Name of Solution ORACLELink httpwwworaclecomdatabaseindex
htmlAccess ProprietaryFunctionality Relational database Can be used to gather reputation
feedback information and make it available to the repu-tation based trust management engine
Limitations with respect to TAS3 Does not provide complex operations required forbehaviour-based trust policies Not yet a web serviceNo support for integrity of information Possibly re-quires strict access controls to prevent rigging of dataDoes not support users privacy policies
Related Requirements D12-53 D12- 54
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 162 of 196
Name of Solution SunXACMLLink httpsunxacmlsourceforgenetAccess Open sourceFunctionality - XACMLv2 policy language reference implementation
Can be used as a basis for the Trust PDPLimitations with respect to TAS3 - Supports the XACMLv2 standard but does not deal
with trust or other TAS3 extensions- Does not support separation of duties state baseddecision making- Requires a separate CVS to validate user credentials- Requires separate components to pull and push cre-dentials- Not good at supporting pure RBAC policies- No good user interfaces for writing policies
Related Requirements D12-51 D12-76Justification of Selection - Well known open source XACML implementation
- Uses an OASIS standard policy language- Supports a wide range of access control policies- Can be combined with PERMIS
Name of Solution Trust Policy WizardLink httpi40virt02ipdukadeCoSimAccess Open sourceFunctionality Allows guided interactive formulation of trust policiesLimitations with respect to TAS3 Only supports behaviour-based trust policiesRelated Requirements D12-59Justification of Selection Providing a wizard is a powerful yet straightforward way
of supporting user selected policies We do not excludethe possibility for more integrate solutions such as egnatural language policy editors
Name of Solution Shibboleth IDP and SP software for SSOLinkAccess Open SourceFunctionality Provides user authentication and SSO using SAMLv2Limitations with respect to TAS3 Not easy to install or configureRelated Requirements D12-73 D12-718Name of Solution SAMP PHPLinkAccess Open SourceFunctionality Provides user authentication and SSO using SAMLv2
Reputedly easy to useLimitations with respect to TAS3 Not sure will need to investigateRelated Requirements D12-73D12-718Name of Solution LassoLink httplassoentrouvertorgAccess Open SourceFunctionality Liberty Alliance Library support SAML2 ID-WSF ID-
SIS Personal Profile and HR (based on Europass CVprofile)
Limitations with respect to TAS3
Related Requirements D12-108 D12-102
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 163 of 196
Justification of Selection OpenSource certified by Liberty Alliance OASIS re-garding SAML2 support Supports the HR ID-SIS draftprofile which is a profile of the European Europass CVinitiative (promoted by CEDEFOP EU Agency) Notethat this HR profile is also supported by ZXID
Name of Solution AuthenticLink httpauthenticlabslibre-entrepriseorgAccess Open SourceFunctionality Liberty Alliance compliant ID Provider support
SAML2 ID-WSF ID-SIS Personal Profile and HR(based on Europass CV profile)
Limitations with respect to TAS3
Related Requirements D12-77 D12-710 D12-726 D12-727 D12-91D12-916 D12-91 D12-916 D12-108 D12-102
Name of Solution LARPELink httplarpelabslibre-entrepriseorgAccess Open SourceFunctionality Liberty Alliance Reverse Proxy It allows any website to
use Liberty Alliance features (Identity federation SingleSign On and Single Logout) without changing the codeof the service provider itself Its Liberty Alliance com-pliance relies on Lasso It also supports the draft HRID-SIS which allow mapping of an existing applicantre-cruiting form with user Europass CV data stored by an-other service in the Circle of Trust with privacy securedby ID-WSF
Limitations with respect to TAS3
Related Requirements D12-82 D12-911 D12-914 D12-916 D12-1228
Name of Solution CVT (CV Transcoding Web Service)Link httpcvteife-lorgAccess Open SourceFunctionality Interoperability gatewaybackoffice service which allow
transformation of CVePortfolio related data from oneformat to another one Support Europass CV IMSePortfolio Netherlands LinkedIn hResume HR ID-SIS
Limitations with respect to TAS3
Related Requirements D12-82 D12-911 D12-914 D12-108 D12-1228
Name of Solution TrustBuilder2LinkAccess Open SourceFunctionality Provides trust negotiation and gradual release of cre-
dentials It is written in Java and allows plugin modulesfor policy evaluation and negotiation strategy It allowscredentials and policies to be written in any languageproviding the correct plugins are available
Limitations with respect to TAS3 Not sure will need to investigateRelated Requirements D12-717Justification for Selection Whilst we will probably need to write some of our own
plugins in order to support the policies and credentialsof TAS3 nevertheless we anticipate that the Trust-Builder2 infrastructure will support this
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 164 of 196
Name of Solution Fedora RepositoryLink httpwwwfedora-commonsorgAccess open sourceFunctionality Repository for all kind of data Accessible through a
web service interface Can be integrated in a SOALimitations with respect to TAS3 Is not aware of TAS3 secure or trusted communicationRelated Requirements D12-86Justification of Selection - The Fedora repository can be completely integrated
in a SOA- In Fedora all functionalities of the repository are ac-cessible through a SOAP or REST based web serviceinterface- Moreover Fedora is Open Source and has a strongcommunity behind it
Name of Solution DSpaceLink httpwwwdspaceorgAccess Open sourceFunctionality Storage of documentsLimitations with respect to TAS3 Not all functions available over web service interfaceRelated Requirements Partially D12-86Name of Solution CDSwareLink httpcdswarecernchAccess Open sourceFunctionality Storage of documentsLimitations with respect to TAS3 Not all functions available over web service interfaceRelated Requirements Partially D12-86Name of Solution EPrintsLink httpwwweprintsorgAccess Open sourceFunctionality Storage of documentsLimitations with respect to TAS3 Not all functions available over web service interfaceRelated Requirements Partially D12-86
Name of Solution SaturnLink httpsaturnportalnottinghamacukAccess University of Nottingham authorised access only as the
system contains live student data Proprietary systemdesigned built and maintained in house
Functionality University of Nottingham student records systemLimitations with respect to TAS3 - Not yet web-service enabled
- Closed internal system - As this is live student datawe cannot create test accounts for the project
Related Requirements Used for authentication of student ID within our demon-strator also used to establish eligibility for scheme Al-lows access to module information to show which mod-ules the student is studying
Justification of Selection Source of student data as held by the institution
Name of Solution ePARS (electronic Personal and Academic RecordSystem)
Link httpseparsnottinghamacuksharedhtmaboutasp
Access University of Nottingham system
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 165 of 196
Functionality Designed to support tutorials and student personal de-velopment
Limitations with respect to TAS3 Used as a proxy for SaturnRelated Requirements Takes regular data dumps of data from the live Saturn
system and has a facility to create test accounts withdummy data so can act as a proxy for Saturn in thedemonstrator
Justification of Selection Allows access to Saturn data without having to accessSaturn direct which we would not be allowed to do fordemonstration purposes
Name of Solution OPUSLink httpfossulsteracukprojectsopusAccess Open source we have an instance installed on our de-
velopment serverFunctionality Placement co-ordination packageLimitations with respect to TAS3 Local implementations only can have multiple in-
stances in a systemRelated Requirements The software is specially designed for placement man-
agement and will be linked into the ePortfolio to aidstudents in the vacancy discovery process and skillsmatching scenarios
Justification of Selection Open source customisable
Name of Solution MaharaLink httpmaharaorgAccess Open sourceFunctionality ePortfolio systemLimitations with respect to TAS3 Designed primarily as a learning ePortfolio but a lot of
work is being done by the community to support use forwork placements
Related Requirements Learner-owned system needs to be hosted but is out-side the university or placement provider control Thelearner can control which information others can seeWeb access
Justification of Selection Many ePortfolio systems are available there are over80 in use in the UK at the moment but not all are freeand not all are web-based Many remain under institu-tional control This system is open source we are incontact with the developers through other project workand there is ongoing development to support use forwork placements so there is a strong community of in-terest
Name of Solution PebblePadLink httpwwwpebblepadcoukAccess ProprietaryFunctionality Personal ePortfolio systemLimitations with respect to TAS3 Designed primarily to support learningRelated Requirements Learner-owned system which interfaces to the ePortfo-
lio and letrsquos learners control which information otherscan see
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 166 of 196
Justification of Selection Web-based learner-controlled system We have agood relationship with the company through otherproject work The system supports exports in a varietyof standards including UK-LEAP and IMS ePortfolioFurthermore we are likely to be able to access demon-strator candidates who have established ePortfolios us-ing the system and offer a rich source of demonstratordata
Name of Solution Kenteq Competent WEB applicationLink httptestcompetentkenteqnlAccess The application is property of KenteqFunctionality Competent provides functionality to complete adminis-
tration services test employment candidates and gen-erate reports
Limitations with respect to TAS3 Competent does not support the full (complete) em-ployability process
Related Requirements See prior D12 chapter WP09 APL demo 8 - 14Justification of Selection Most applications that support (parts of) employability
processes are embedded in software for internal HRprocesses Competent supports the APL and profilematching process as such independently from the or-ganisation or individual who applies for an employabil-ity service There is no other off-the-shelve applicationavailable who supports employability processes Theapplication of the employability provider is outside theTAS3 infrastructure but within the scope of the TAS3
demonstrator where it is necessary as application tosupport and exchange data for the demonstrator sce-narios D14 13 APL and 14 Mass layoff The ap-plication is in English and Dutch language what is anadvantage for the NL demonstrator
Name of Solution PILS Patient Information Location ServiceLink httpwwwcustodixcomAccess Proprietary Custodix Software Available for the
demonstrators can be customized for the demonstra-tors
Functionality Front-end for looking up (distributed search) and dis-playing medical information from different medicalrepositories
Limitations with respect to TAS3 No known limitations at this point in timeRelated Requirements Providing a front-end for data retrieval in the eHealth
scenarios of D14 and D91Justification of Selection Fully working solution completely under the control of
one of the partners (Custodix) which means that thesolution can easily be customized to fit into the pilotsNext to PILS an XACML driven medical record repos-itory is available Together they form a complete sys-tem for access to distributed medical information withdynamic policy based access control The completesystem is a good benchmark for evaluating the addedvalue of TAS3
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 167 of 196
Name of Solution Personal Health RecordLink No link availableAccess Depending on official choice (presumed to be propri-
etary)Functionality Personal data store for managing personal medical in-
formation (ie patient controlled repository)Limitations with respect to TAS3 Originally Medisoft was providing the Orca system
However they left the project early as they felt theycould no longer provide the required software The ad-ministrative complexity of this event has delayed officialappointment of a new PHR subcontractor (a candidateis available though)
Related Requirements User centric (ie with user supplied data) medicalrepository A place where a patient can manage hisown data The PHR concentrates data from a vari-ety of sources (from accredited professionals to carersand the patient himself) and is an important element fortesting trust based components
Justification of Selection The current candidate is selected by the pilot end-usersthemselves for their pathology (patient organization)
Name of Solution WS-GuardLink httpplasticisticnritwikitoolsAccess Open source (GPLv3)Functionality WS-Guard provides a prototype implementation of a
framework augmenting the registration phase of a ser-vice within a registry with a testing phase Registrationis then guaranteed only if the service passes the test-ing phase
Limitations with respect to TAS3 The conformance validation is based on behaviouralmodels in the form of Service State Machines (SSM)Within TAS3 we intend to verify service compliancebased on the manifested policy Furthermore there isno support to the notions of identity and roles
Related Requirements D12-109 D12-101 D12-102Justification of Selection WS-Guard is developed by CNR as a result of research
in related areas There is no comparative tool perform-ing the same functionalities
Name of Solution ZXIDLink httpwwwzxidorgAccess Open source (Apache License 20)
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 168 of 196
Functionality ZXID aims at full stack implementation of all feder-ated identity management and identity web servicesprotocols Initial goal is supporting SP role followedby ID-WSF WSC and IdP roles Provides user au-thentication and SSO using SAMLv2 Specifically 1SAML 20 SSO SP role and XACML PEP for Apacheas modauthsaml2 SAML 20 SSO SP role as programming toolkit forC C++ Java C PHP and Perl3 SAML 20 SSO IdP role4 XACML PEP as programming toolkit for C C++Java C PHP and Perl5 ID-WSF WSC role as programming toolkit for CC++ Java C PHP and Perl6 ID-WSF WSP role as programming toolkit for CC++ Java C PHP and Perl7 Discovery client as programming toolkit for C C++Java C PHP and Perl8 Discovery registration as programming toolkit for CC++ Java C PHP and Perl9 Discovery service10 People Service Client as programming toolkit for CC++ Java C PHP and Perl11 People Service
Limitations with respect to TAS3
Related Requirements D12-108 D12-102Justification of Selection Nonexclusive choice Written by SAML ID-WSF and
XACML insider Well interopped SAML 20 and ID-WSF 20 certified in its commercial (Symlabs) incar-nation Developed by a TAS3 contributor so ensuresgood support Also selected by the architecture team
Name of Solution TAXILink httpwww1isticnritERITAXItaxi_
indexhtmlAccess Open source (GPLv2)Functionality TAXI is a tool for the systematic generation of XML in-
stances The TAXI methodology is largely inspired tothe well-known Category Partition which provides astepwise intuitive approach to functional testing as fol-lows identify the relevant input parameters define theenvironment conditions combine their significant val-ues into an effective test suite
Limitations with respect to TAS3 Cannot deal with negative tests and fuzz tests More-over it does not currently address handling of accesspolicies eg XACML
Related Requirements D12-101 D12-102Justification of Selection TAXI is developed by CNR as a result of research in
related areas There is no comparative tool performingthe same functionalities
Name of Solution Eye-Tracker TobiiLink httpwwwtobiicom
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 169 of 196
Access Proprietary Accessible by University of Zaragoza atWalqa (a technological park of reference in Spain)
Functionality Tools for identifying what participants look at during thecourse of a usability-accessibility test Other offeringsexist in the market but Tobbi solutions can be consid-ered as the leader in this field
Limitations with respect to TAS3 Any usability and accessibility analysis is limited if it isnot completed with indicators that allow accurate mea-surement of how easy it is to manage the applicationthat is perceived usability by end-users
Related Requirements D12-106 D12-107 (but this tool does not fully com-ply with the non-technical perspective of this require-ment)
Justification of Selection
Name of Solution ClickTracks WebTrendsLink httpwwwclicktrackscom http
wwwwebtrendscomAccess ProprietaryFunctionality Specific software packages for tracking the software
userrsquos behaviour especially when the software is im-plemented over web protocols Others free or low-costsolutions such Google Analytics dont offer the samelevel of functionalities
Limitations with respect to TAS3 This tools do not allow us to assess the levels of usabil-ity or accessibility so that it is not possible to determinewhether the software user is satisfied or not
Related Requirements D12-106 D12-107 (but these tools are insufficientto fully comply with the non-technical perspective of thisrequirement)
Justification of Selection
Name of Solution Structural Modeling (EQS PLS SPSS)Link httpwwwmvsoftcom httpwwwspss
comAccess ProprietaryFunctionality Analyze causal relationships among multiple latent
variables Others packages such as LISREL or AMOSoffer similar functionalities but the research group hasbeen working with EQS PLS and SPSS for severalyears In addition other techniques such as linear re-gression or cluster analysis do not allow to analyzerelationships among latent variables or to include avariable that plays a double role (independent as welldependent) which is possible to conduct in structuralmodeling
Limitations with respect to TAS3 NARelated Requirements D12-104 D12-105 D12-106 (these tools will help
to analyze relationships among variables that will serveto determine the main precursors of trust and servicequality on end-users mind)
Justification of Selection University of Zaragoza has the access to these specificstatistical packages
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 170 of 196
Name of Solution JiraLink httpwwwatlassiancomsoftwarejiraAccess ProprietaryFunctionality Flexible web based bug tracking issue tracking task
tracking and project management software solutionused for open source and enterprise projects
Limitations with respect to TAS3 Cost complexityRelated Requirements D12-122 D12-123 (D12-124 D12-125 D12-
126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 171 of 196
Name of Solution Concurrent Versions System CVSLink httpenwikipediaorgwikiConcurrent_
Versions_SystemAccess Open sourceFunctionality Basic file repository with good revision controlLimitations with respect to TAS3 File-based optimised for textRelated Requirements D12-122 D12-123 (D12-124 D12-125 D12-
126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution Subversion SVNLink httpsubversiontigrisorgAccess OpenSourceFunctionality Basic file repository with good revision controlLimitations with respect to TAS3 File-basedRelated Requirements D12-122 D12-123 (D12-124 D12-125 D12-
126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution MediaWikiLink httpwwwmediawikiorgAccess OpenSourceFunctionality Wiki package for document and file managementLimitations with respect to TAS3 Complexity needs a databaseRelated Requirements D12-122 D12-123 (D12-124 D12-125 D12-
126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution DokuWikiLink httpwwwdokuwikiorgAccess OpenSourceFunctionality Wiki package for document and file managementLimitations with respect to TAS3
Related Requirements D12-121 D12-122 D12-123 (D12-124 D12-125 D12-126 D12-126 D12-1217 D12-1218D12-1219 D12-1220 D12-1221 D12-1224D12-1225 D12-1227 D12-1230)
Name of Solution ConfluenceLink httpwwwatlassiancomsoftware
confluenceAccess ProprietaryFunctionality Confluence is a simple powerful wiki that lets you cre-
ate and share pages documents and rich content withyour team
Limitations with respect to TAS3 Cost complexity needs Java and a databaseRelated Requirements D12-121 D12-122 D12-123 (D12-124 D12-
125 D12-126 D12-126 D12-1217 D12-1218D12-1219 D12-1220 D12-1221 D12-1224D12-1225 D12-1227 D12-1230)
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 172 of 196
Name of Solution RedmineLink httpwwwredmineorgAccess OpenSourceFunctionality Redmine is a flexible project management web appli-
cation Written using Ruby on Rails framework it iscross-platform and cross-database
Limitations with respect to TAS3 Assumes a particular work flow model and dedicatedresources for response and dispatch
Related Requirements D12-122 D12-123 (D12-124 D12-125 D12-126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution TracLink httptracedgewallorgAccess OpenSourceFunctionality Trac is an enhanced wiki and issue tracking system for
software development projects Trac uses a minimal-istic approach to web-based software project manage-ment Our mission is to help developers write greatsoftware while staying out of the way Trac should im-pose as little as possible on a teamrsquos established de-velopment process and policies
Limitations with respect to TAS3 Complex and heavyweightRelated Requirements D12-122 D12-123 (D12-124 D12-125 D12-
126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution BugZillaLink httpwwwbugzillaorgAccess OpenSourceFunctionality Bugzilla is server software designed to help you man-
age software developmentLimitations with respect to TAS3 Complex and heavyweightRelated Requirements D12-123 (D12-124 D12-126 D12-1223 D12-
1224 D12-1230)
Name of Solution GITLink httpgit-scmcomAccess OpenSourceFunctionality Git is a free and open source distributed version con-
trol system designed to handle everything from small tovery large projects with speed and efficiency
Limitations with respect to TAS3 Possibly immatureRelated Requirements D12-122 D12-123 (D12-124 D12-125 D12-
126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution HudsonLink httpshudsondevjavanetAccess OpenSource
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 173 of 196
Functionality Hudson monitors executions of repeated jobs such asbuilding a software project or jobs run by cron
Limitations with respect to TAS3 Possibly heavyweight biased to JavaRelated Requirements D12-127 (D12-1211 D12-1215)
Name of Solution ActiveCollabLink httpwwwactivecollabcomAccess ProprietaryFunctionality ActiveCollab is a project management and collabora-
tion tool that you can set up on your own website Havean area where you can collaborate with your teamclients and contractors and keep projects on track whileretaining full control over access permissions and yourdata
Limitations with respect to TAS3 Implies a work process that relies on dedicated re-sources
Related Requirements D12-122 D12-123 (D12-124 D12-125 D12-126 D12-126 D12-1217 D12-1218 D12-1219D12-1221 D12-1224 D12-1225 D12-1230)
Name of Solution NagiosLink httpwwwnagiosorgAccess OpenSourceFunctionality Scalable resourcenetwork monitor frameworkLimitations with respect to TAS3
Related Requirements D12-127 (D12-1211 D12-1215)Justification of Selection
Name of Solution Semantic MediaWiki SMWLink httpenwikipediaorgwikiSemantic_
MediaWikiAccess OpenSourceFunctionality SMW allows for annotating semantic data within wiki
pages thus turning a wiki that incorporates the exten-sion into a semantic wiki
Limitations with respect to TAS3 Possibly over the top complex for what developers doRelated Requirements D12-121 D12-122 D12-123 (D12-124 D12-
125 D12-126 D12-126 D12-1217 D12-1218D12-1219 D12-1220 D12-1221 D12-1224D12-1225 D12-1227 D12-1230)
Name of Solution OntoPrise OntoStudioLink httpwwwontoprisedeenhome
productsontostudioAccess ProprietaryOpenSource dual licensedFunctionality Extensions of SMW for production purposes support-
ing ontology development and integrationLimitations with respect to TAS3 Possibly cost lack of dedicated resources to use it
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 174 of 196
Related Requirements D12-121 D12-122 D12-123 (D12-124 D12-125 D12-126 D12-126 D12-1217 D12-1218D12-1219 D12-1220 D12-1221 D12-1224D12-1225 D12-1227 D12-1230)
Name of Solution DOGMA Studio WorkbenchLinkAccess Although the solution is open-source the software is
located on a web server with restricted accessFunctionality It allows the elicitation and visualisation of DOGMA in-
spired ontologiesLimitations with respect to TAS3
Related Requirements D12-223Justification of Selection This is the only tool that supports DOGMA inspired on-
tology
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 175 of 196
E Inter-WP Requirements Interactions (First Itera-tion)E1 Interactions of WP2
Source Re-quirement
Interaction Type Target Requirements
D12-223
supports D12-312 D12-314depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP2
E2 Interactions of WP3
Source Re-quirement
Interaction Type Target Requirements
D12-31
supports D12-223 D12-55depends on D12-63abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP3
D12-32
supports D12-55 D12-612 D12-91depends on D12-62abstractsimplements D12-83similar toNote Partially implements D12-612
This requirement will be fulfilled by WPs WP3
D12-33
supports D12-610depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP3
D12-34
supports D12-912depends onabstractsimplementssimilar toNote I would have expected some requirement(s) that specif-
ically target(s) the ID management infrastructure thatD21 describes in so much detail but I cant find one(would be a depends on)
This requirement will be fulfilled by WPs WP7
D12-35
supports
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 176 of 196
depends on D12-713abstractsimplements D12-723 D12- 94similar toNote
This requirement will be fulfilled by WPs WP3 WP7
D12-36
supportsdepends on D1-713abstractsimplements D12-723 D12-94similar toNote
This requirement will be fulfilled by WPs WP2 WP3
D12-37
supportsdepends on D12-713abstractsimplements D12-71similar toNote
This requirement will be fulfilled by WPs WP3
D12-39
supportsdepends on D12-103abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP3
D12-311
supports D12-214depends onabstracts D12-77implements D12-726similar to D12-85 D12-96Note
This requirement will be fulfilled by WPs WP3 WP4
D12-312
supports D12-108depends onabstractsimplementssimilar to D12-214 D12-47 D12-223Note
This requirement will be fulfilled by WPs WP3 WP6
D12-313
supports D12-55depends on D12-66abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP3
D12-314
supportsdepends onabstractsimplements D12-223 D12-108similar toNote
This requirement will be fulfilled by WPs
D12-15
supportsdepends on D12-49 D12-51
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 177 of 196
abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP3
E3 Interactions of WP4
Source Re-quirement
Interaction Type Target Requirements
D12-41
supports D12-29 D12-220 D12-77 D12-726 D12-85D12-86 D12-92 D12-96 D12-97 D12-912D12-913 D12-98 D12-99
depends on D12-218 D12-219abstracts D12-311implementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-42
supports D12-78 D12-716 D12-718 D12-727 D12-916D12-1227
depends onabstracts D12-34implementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-43
supports D12-21 D12-25 D12-26 D12-37 D12-121D12-105
depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-44
supports D12-211 D12-212 D12-214 D12-71 D12-76D12-210 D12-215 D12-222 D12-33 D12-37D12-714 D12-721 D12-724 D12-725 D12-94D12-95 D12-911 D12-916 D12-917
depends on D12-218 D12-219abstracts D12-217 D12-312 D12-73 D12-910implementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-45
supports D12-211 D12-212 D12-214 D12-29 D12-210D12-220 D12-37 D12-312 D12-315 D12-910D12-916 D12-922
depends on D12-218 D12-219abstracts D12-221 D12-724implementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-46
supports D12-310 D12-722
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 178 of 196
depends on D12-218 D12-219abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-47
supports D12-25D12-210 D12-211 D12-212depends onabstracts D12-314implementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-48
supports D12-211 D12-212 D12-210 D12-213 D12-33D12-93 D12-97 D12-914 D12-106
depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP4
D12-49
supports D12-51 D12-210 D12-53 D12-54depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP4
E4 Interactions of WP 5
Source Re-quirement
Interaction Type Target Requirements
D12-51
supports D12-104depends onabstractsimplementssimilar toNote As part of the overall authorization framework this re-
quirement also support requirements on authorization(D12-220 D12-311 D12-45 D12-66 D12-612D12-76 D12-91 D12-94)
This requirement will be fulfilled by WPs WP5
D12-55
supportsdepends on D12-31 and D12-313abstractsimplementssimilar toNote Business process management (WP3) should provide
support for and check inclusion of a feedback formwhich enables the user to give feedback on the cur-rent process For the demonstrator use cases it will beaddressed by WP9 in the trust dashboard
This requirement will be fulfilled by WPs WP3 WP9
D12-56
supports
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 179 of 196
depends on D12-712 D12-715abstractsimplements D12-713similar toNote The credential based trust management (CTM) service
will require credential handling For credentials ex-pressing trust relationships finding credentials is partof the CTM service design
This requirement will be fulfilled by WPs WP5 WP7
D12-59
supports D12-212 D12-213 D12-43 D12-84 D12-85D12-96
depends onabstractsimplements D12-713similar toNote The credential based trust management (CTM) service
will require credential handling For credentials ex-pressing trust relationships finding credentials is partof the CTM service design
This requirement will be fulfilled by WPs WP5 WP7
D12-510
supportsdepends onabstractsimplementssimilar to D12-73 D12-34 D12-912Note Implementing D12-73 in such a way that D12-34 is
achieved will also satisfy this requirement D12-912 isa reformulation of the same requirement (with differentjustification)
This requirement will be fulfilled by WPs WP7
E5 Interactions of WP 6
WP 6 consists of the legal requirements and contractual framework Both of these topics are horizontal andcrosscutting impacting or being impacted by every aspect of the project To that end WP6 Interactions willbe set forth in a more text-based fashion at the level of the interaction with the WP rather than at the specificrequirement level though attempts will be made to call out those requirements that have special relationshipswith legal requirements or the contractual framework
We mentioned in Section 44 that WP6 entails three kind of requirements intake and qualification basic legalrequirements that emanate from the EU Data Protection Directive and requirements related to the contractand policy frameworks In the course of mapping interactions they will be described as the Intake LegalRequirement and Contract Framework sections respectively
WP2 ndash Architecture As a central element of TAS3 the architecture is perhaps most closely in-tertwined with both the legal requirements and contract framework Oneof the innovative approaches of TAS3 was the development of technologypolicy and contractlegal in collaboration and there has been significant in-teraction between the architecture team in addressing legal requirements(D12-221 -222) and in functions such as authentication (D12-217) log-ging access control and audit (D12-218 The Important relationshipsalso exist as related to the contract framework where contract and re-quired policies support security (D12-27 -216) oversightaccountability(D12-215) implementation of TAS3 (D12-29) and functions such aslimits on disclosure (D12-220)
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 180 of 196
WP3 ndash Business ProcessModeling
Business processes are related to legal requirements because in theirmodeling they must operate within the confines of the legal requirementsIssues like treating PIIIdentity management ((D12-34) Access controland role management (D12-36-36 -310) and user controls (D12-311)They are likewise supported and constrained by contractual requirementsthat impose obligations The most important one is the requirement tohave access to a privacy policy (D12-314) Contract framework canalso help support functions like special circumstances and error recov-ery (D12-39) and delegation (D12-37)
WP4 ndash Secure and Trust-worthy Processing
By its very subject matter WP4 is tasked to give effect to many of thelegal requirements Concepts of user control (D12-41) confidentiali-typseudonymity (D12-42 contributes) and proofcompliance functions(D12-45-46) are all essential to privacy The latter two are also essen-tial elements that both support and are supported by the contract frame-work One of the reasons why the collaborative approach is so needed isbecause of these interactions where a requirements is both supported byand supporting an aspect of the contract framework
WP5 ndash Flexible Trust Man-agement Framework
Legal and contract framework interaction with WP5 may be more in termsof how some elements of WP5 give effect to requirements through mech-anisms as well as how those mechanisms may be enabled For instancelegal requirements of user control will be given effect through (D12-51-53) the need for trust policies and management is essential to users mak-ing informed choices and setting appropriate controls The ability to usereputation and other feedback information (D12-54-55) will need to beenabled by contracts binding the reputation services ((D12-511)
WP7 ndash Privacy Authoriza-tion Infrastructure
In many ways WP7 provides the technical mediation of privacy which isinformed by privacy requirements and supported by the contract frame-work to bind service providers to the processestechnical elementsAmong the more important legal requirements support by WP7 are col-lection limitation ((D12-75) user control (D12-77) pseudonymity (D12-716) data minimization (D12-718) and consent (D12-726) WP7 alsoprovides functions in support of the contract framework which are like-wise supported by provisions of the contract framework most notablyoversight by tracking delegations (D12-71 -714) authorizations (D12-76 -723) and preventing collusion (D12-78 -718)
WP8 ndash Uniform Interface WP8 is mostly providing technical functionalityspecification which maybe related to legal requirements and contract framework in elements suchas end user interface ((D12-84) user control ((D12-85) and access toboth legacy (D12-82) and repository data (D12-86)
WP9 ndash Demonstrators The demonstrators are the place where we test the contract frameworkand assess mechanisms of compliance with legal requirements as suchthey are part of the iterative development process of the operation ofthe contract framework and the completeness and usability of the legalrequirements Essential elements of both legal requirements and con-tract framework such as user control (D12-92 -96) audit (D12-95)Access (D12-97-98) data minimization (D12-916) and security (D12-94-913) are all specified and brought to life in the demonstrators
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 181 of 196
WP10 ndash Quality WP10 is an important element in testingdemonstrating compliance andoversight This role is important to help assure that legal requirementsare followed and to enable better visibility of possible contract frameworkviolations or issues Some aspects of the testing process may also beuseful in judging the capacity for compliance as part of the intake pro-cess The WP requirements specify important compliance elements in-cluding ongoing testing (D12-101) Detection of service failures and er-rors (D12-102-103) and propagation of service provider characteristics(D12-108)
WP12 ndash Integration WP12 plays an important project role to help assure that the elementsof TAS3 work in unison From both the legal requirements and contractframework perspective these are import functions as both require thatTAS3 be able to provide a cohesive trust and security architecture withappropriate end-to end controls and functionality Integration of programcomponents is an obvious necessity
E6 Interactions of WP 7
Source Re-quirement
Interaction Type Target Requirements
D12-71
supports D12-37depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-73
supports D12-510 D12-94 D12-916 D12-917 D12-918D12-919 D12-920 D12-921
depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-76
supports D12-220 D12-45 D12-91 D12-94 D12-910D12-922
depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-77
supports D12-311 D12-41 D12-85 D12-92 D12-96D12-98 D12-912
depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-79
supports D12-310depends onabstracts
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 182 of 196
implementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-712
supports D12-56 D12-93depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-713
supports D12-56 D12-93depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-715
supports D12-56depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-717
supports D12-56depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-719
supports D12-36 D12-37 D12-313depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-720
supports D12-36 D12-37depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-722
supports D12-46depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-724
supports D12-95depends onabstracts
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 183 of 196
implementssimilar toNote
This requirement will be fulfilled by WPs WP7
D12-727
supports D12-38depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP7
E7 Interactions of WP 8
Source Re-quirement
Interaction Type Target Requirements
D12-81
supports D12-23 D12-24 D12-25 D12-26 D12-29 D12-213 D12-92 D12-911 D12-914 D12-312 D12-314 D12-718
depends on D12-221 D12-223 D12-72 D12-71 D12-73D12-76 D12-714
abstractsimplementssimilar toNote ADPEP - gateway
This requirement will be fulfilled by WPs WP8 WP2 WP7 WP4
D12-82
supports D12-97 D12-718depends onabstractsimplementssimilar toNote Legacy databases
This requirement will be fulfilled by WPs WP8 WP7
D12-83
supports D12-312 D12-314depends on D12-31 D12-32 D12-33 D12-36 D12-35
D12-37 D12-38 D12-39 D12-311abstractsimplementssimilar toNote Business process
This requirement will be fulfilled by WPs WP8 WP3
D12-84
supports D12-97 D12-911 D12-914 D12-915 D12-916depends on D12-31 D12-32 D12-33abstractsimplementssimilar toNote Generic client
This requirement will be fulfilled by WPs WP8 WP3
D12-85
supports D12-96 D12-99 D12-711depends on D12-719 D12-720abstractsimplementssimilar toNote policymanagement
This requirement will be fulfilled by WPs WP8 WP7 WP5
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 184 of 196
D12-86
supports D12-97 D12-916depends onabstractsimplementssimilar toNote repository
This requirement will be fulfilled by WPs WP8
E8 Interactions of WP 9
Source Re-quirement
Interaction Type Target Requirements
D12-91
supports D12-220 D12-223 D12-1214 D12-1215depends on D12-21 D12-22 D12-25 D12-36 D12-37
D12-38 D12-310 D12-612 D12-711 D12-81D12-82
abstracts D12-24 D12-86implements D12-66 D12-108 D12-109similar toNote
This requirement will be fulfilled by WPs WP9
D12-92
supports D12-215 D12-220 D12-36 D12-44 D12-45D12-63 D12-66 D12-76 D12-726
depends on D12-211 D12-212 D12-314 D12-41 D12-48D12-59 D12-1213
abstracts D12-214 D12-311 D12-77 D12-711implementssimilar to D12-85Note
This requirement will be fulfilled by WPs WP6 WP7
D12-93
supports D12-212D12-43 D12-612depends on D12-510 D12-76 D12-712 D12-714 D127-15abstracts D12-28 D12-210 D12-213 D12-48 D12-73implements D12-73 D12-106 D12-107similar to D12-75Note
This requirement will be fulfilled by WPs WP7 WP2 WP4
D12-94
supports D12-210 D12-214 D12-215 D12-220 D12-34D12-43 D12-68D12-612 D12-726 D12-104D12-105 D12-1213
depends on D12-218 D12-219 D12-61 D12-723abstracts D12-36 D12-74implements D12-27 D12-1215similar to D12-510 D12-73 D12-76Note
This requirement will be fulfilled by WPs WP7 WP2 WP4
D12-95
supports D12-215 D12-222 D12-41 D12-44 D12-69D12-610 D12-721 D12-725 D12-102 D12-124 D12-1210 D12-1213 D12-1215
depends on D12-34abstractsimplements D12-217similar to D12-724Note
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 185 of 196
This requirement will be fulfilled by WPs WP4 WP7
D12-96
supports D12-211 D12-214 D12-220 D12-41 D12-44D12-45 D12-64 D12-66 D12-71 D12-723D12-104 D12-1215
depends on D12-48 D12-77 D12-1213abstracts D12-210 D12-314 D12-711implements D12-85similar toNote
This requirement will be fulfilled by WPs WP6 WP7
D12-97
supports D12-211 D12-215 D12-43 D12-610 d12-721depends on D12-28 D12-219 D12-62 D12-63 D12-612
D12-73 D12-76 D12-82abstractsimplementssimilar to D12-68 D12-86Note
This requirement will be fulfilled by WPs WP8
D12-98
supports D12-210 D12-211 D12-220 D12-43 D12-55D12-66 D12-69 D12-610 D12-722
depends on D12-213 D12-217 D12-311 D12-315 D12-41D12-510 D12-76 D12-716 D12-724
abstractsimplementssimilar to D12-222 D12-68Note
This requirement will be fulfilled by WPs WP7 WP8
D12-99
supports D12-311 D12-41 D12-66depends on D12-29 D12-210 D12-211 D12-214 D12-48abstracts D12-315 D12-67 D12-85implements D12-726similar to D12-77 D12-711Note
This requirement will be fulfilled by WPs WP7
D12-910
supports D12-210 D12-212 D12-311 D12-314depends onabstractsimplements D12-213 D12-214 D12-106 D12-107similar to D12-33 D12-48 D12-84Note
This requirement will be fulfilled by WPs WP04WP8 WP10
D12-911
supports D12-22 D12-24 D12-210 D12-213 D12-312D12-41 D12-42 D12-1213
depends on D12-34 D12-612 D12-716 D12-82 D12-86abstracts D12-1227 D12-1228implements D12-29similar to D12-223Note
This requirement will be fulfilled by WPs WP08 WP09 WP12
D12-912
supports D12-210 D12-211 D12-213 D12-217 D12-220 D12-36 D12-41 D12-66 D12-68 D12-72D12-73 D12-76 D12-722 D12-726
depends on D12-218 D12-219abstracts D12-74 D12-75 D12-716implements D12-510similar to
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 186 of 196
NoteThis requirement will be fulfilled by WPs WP7
D12-913
supports D12-214 D12-220 D12-46 D12-612 D12-73D12-726
depends on D12-43 D12-74 D12-75 D12-715 D12-716abstracts D12-27 D12-216 D12-310implementssimilar to D12-218 D12-219 D12-76Note
This requirement will be fulfilled by WPs WP7 WP8
D12-914
supports D12-24 D12-210depends onabstractsimplementssimilar toNote May contradict D12-211
This requirement will be fulfilled by WPs WP8
D12-915
supports D12-22 D12-210 D12105 D12-106depends onabstractsimplementssimilar toNote
This requirement will be fulfilled by WPs W2 WP4 WP8 WP10
D12-916
supports D12-215 D12-216 D12-63 D12-612depends on D12-82 D12-86abstracts D12-64implementssimilar toNote
This requirement will be fulfilled by WPs WP8 WP9
E9 Interactions of WP 10
Source Re-quirement
Interaction Type Target Requirements
D12-101
supports D12-216depends on D12-21 D12-22 D12-25 D12-26 D12-121
D12-1211abstracts D12-129 D12-1214implementssimilar toNote
This requirement will be fulfilled by WPs
D12-102
supports D12-216depends on D12-223 D12-56 D12-74 D12-76 D12-1211abstracts D12-1214implementssimilar toNote
This requirement will be fulfilled by WPs WP10
D12-103
supports D12-1214 D12-1215depends on D12-223abstractsimplements
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 187 of 196
similar toNote
This requirement will be fulfilled by WPs WP2
D12-108
supports D12-47 D12-1214 D12-1215depends on D12-223abstractsimplements D12-1213 D12-1217similar toNote
This requirement will be fulfilled by WPs WP9 WP8
D12-109
supports D12-216depends on D12-21 D12-22abstractsimplements D12-1213 D12-1214 D12-1215similar toNote
This requirement will be fulfilled by WPs WP10 WP2
D12-104
supports D12-58depends on D12-214 D12-216 D12-51 D12-43 D12-86
D12-94 D12-96abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP10 WP9
D12-105
supportsdepends on D12-29 D12-43 D12-94 D12-915abstractsimplementssimilar toNote
This requirement will be fulfilled by WPs WP10 WP9
D12-106
supports D12-210 D12-211 D12-212 D12-213 D12-48D12-915
depends onabstracts D12-93 D12-910implementssimilar toNote
This requirement will be fulfilled by WPs WP10 WP9
D12-107
supportsdepends on D12-28 D12-83 D12-84 D12-85abstracts D12-93 D12-910implementssimilar toNote
This requirement will be fulfilled by WPs WP10 WP9
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 188 of 196
F Inter-WP Requirements Interaction (Second It-eration)
The following is a depiction of the interaction between the technical requirements after the second iterationof this analysis with all the updated requirements The inconsistencies are combed out of this list which ispresented in the DOT notation which is interpreted as follows
ldquoRequirement 1rdquorarr ldquoRequirement 2rdquo [label = ldquoType of interactionrdquo]
The number of ldquoRequirement 1rdquo also indicates the WP that authored the interaction
F1 Interactions of WP3
ldquoD12-31rdquorarr ldquoD12-55rdquo [label = ldquoIrdquo]ldquoD12-31rdquorarr ldquoD12-63rdquo [label = ldquoDrdquo]
ldquoD12-32rdquorarr ldquoD12-55rdquo [label = ldquoIrdquo]ldquoD12-32rdquorarr ldquoD12-612rdquo [label = ldquoSrdquo]ldquoD12-32rdquorarr ldquoD12-91rdquo [label = ldquoSrdquo]ldquoD12-32rdquorarr ldquoD12-62rdquo [label = ldquoDrdquo]ldquoD12-32rdquorarr ldquoD12-83rdquo [label = ldquoIrdquo]ldquoD12-32rdquorarr ldquoD12-612rdquo [label = rdquoPart Irdquo]
ldquoD12-33rdquorarr ldquoD12-610rdquo [label = ldquoSrdquo]
ldquoD12-35rdquorarr ldquoD12-713rdquo [label = ldquoDrdquo]ldquoD12-35rdquorarr ldquoD12-723rdquo [label = ldquoIrdquo]ldquoD12-35rdquorarr ldquoD12-729rdquo [label = ldquoDrdquo]ldquoD12-36rdquorarr ldquoD12-713rdquo [label = ldquoDrdquo]ldquoD12-36rdquorarr ldquoD12-723rdquo [label = ldquoIrdquo]
ldquoD12-37rdquorarr ldquoD12-713rdquo [label = ldquoDrdquo]ldquoD12-37rdquorarr ldquoD12-71rdquo [label = ldquoIrdquo]
ldquoD12-39rdquorarr ldquoD12-103rdquo [label = ldquoDrdquo]
ldquoD12-311rdquorarr ldquoD12-214rdquo [label = ldquoSrdquo]ldquoD12-311rdquorarr ldquoD12-77rdquo [label = ldquoArdquo]ldquoD12-311rdquorarr ldquoD12-726rdquo [label = ldquoIrdquo]
ldquoD12-312rdquorarr ldquoD12-108rdquo [label = ldquoSrdquo]
ldquoD12-313rdquorarr ldquoD12-55rdquo [label = ldquoSrdquo]ldquoD12-313rdquorarr ldquoD12-66rdquo [label = ldquoDrdquo]
ldquoD12-314rdquorarr ldquoD12-223rdquo [label = ldquoIrdquo]ldquoD12-314rdquorarr ldquoD12-108rdquo [label = ldquoIrdquo]
ldquoD12-315rdquorarr ldquoD12-49rdquo [label = ldquoDrdquo]ldquoD12-315rdquorarr ldquoD12-51rdquo [label = ldquoDrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 189 of 196
F2 Interactions of WP4
ldquoD12-41rdquorarr ldquoD12-29rdquo [label = ldquoSrdquo] ldquoD12-41rdquorarr ldquoD12-220rdquo [label = ldquoSrdquo]ldquoD12-41rdquorarr ldquoD12-77rdquo [label = ldquoIrdquo]ldquoD12-41rdquorarr ldquoD12-726rdquo [label = ldquoSrdquo]ldquoD12-41rdquorarr ldquoD12-86rdquo [label = ldquoSrdquo]ldquoD12-41rdquorarr ldquoD12-92rdquo [label = ldquoSrdquo]ldquoD12-41rdquorarr ldquoD12-96rdquo [label = ldquoArdquo]ldquoD12-41rdquorarr ldquoD12-98rdquo [label = ldquoSrdquo]ldquoD12-41rdquorarr ldquoD12-99rdquo [label = ldquoSrdquo]ldquoD12-41rdquorarr ldquoD12-218rdquo [label = ldquoDrdquo]ldquoD12-41rdquorarr ldquoD12-219rdquo [label = ldquoDrdquo]ldquoD12-41rdquorarr ldquoD12-31rdquo [label = ldquoArdquo]
ldquoD12-42rdquorarr ldquoD12-78rdquo [label = ldquoSrdquo]ldquoD12-42rdquorarr ldquoD12-716rdquo [label = ldquoSrdquo]ldquoD12-42rdquorarr ldquoD12-718rdquo [label = ldquoSrdquo]ldquoD12-42rdquorarr ldquoD12-727rdquo [label = ldquoSrdquo]ldquoD12-42rdquorarr ldquoD12-916rdquo [label = ldquoSrdquo]ldquoD12-42rdquorarr ldquoD12-1227rdquo [label = ldquoSrdquo]ldquoD12-42rdquorarr ldquoD12-34rdquo [label = ldquoArdquo]
ldquoD12-43rdquorarr ldquoD12-21rdquo [label = ldquoSrdquo]ldquoD12-43rdquorarr ldquoD12-25rdquo [label = ldquoSrdquo]ldquoD12-43rdquorarr ldquoD12-26rdquo [label = ldquoSrdquo]ldquoD12-43rdquorarr ldquoD12-37rdquo [label = ldquoSrdquo]ldquoD12-43rdquorarr ldquoD12-121rdquo [label = ldquoSrdquo]
ldquoD12-44rdquorarr ldquoD12-211rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-212rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-214rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-71rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-76rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-210rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-215rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-222rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-33rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-37rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-714rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-721rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-724rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-725rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-95rdquo [label = ldquoArdquo]ldquoD12-44rdquorarr ldquoD12-916rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-917rdquo [label = ldquoSrdquo]ldquoD12-44rdquorarr ldquoD12-218rdquo [label = ldquoDrdquo]ldquoD12-44rdquorarr ldquoD12-219rdquo [label = ldquoDrdquo]ldquoD12-44rdquorarr ldquoD12-217rdquo [label = ldquoArdquo]ldquoD12-44rdquorarr ldquoD12-312rdquo [label = ldquoArdquo]ldquoD12-44rdquorarr ldquoD12-73rdquo [label = ldquoArdquo]
ldquoD12-45rdquorarr ldquoD12-211rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-212rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-214rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-29rdquo [label = ldquoSrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 190 of 196
ldquoD12-45rdquorarr ldquoD12-210rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-220rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-37rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-312rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-315rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-916rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarr ldquoD12-922rdquo [label = ldquoSrdquo]ldquoD12-45rdquorarrldquoD12-218rdquo [label = ldquoDrdquo]ldquoD12-45rdquorarr ldquoD12-219rdquo [label = ldquoDrdquo]ldquoD12-45rdquorarr ldquoD12-221rdquo [label = ldquoArdquo]ldquoD12-45rdquorarr ldquoD12-724rdquo [label = ldquoArdquo]
ldquoD12-46rdquorarr ldquoD12-310rdquo [label = ldquoSrdquo]ldquoD12-46rdquorarr ldquoD12-218rdquo [label = ldquoDrdquo]ldquoD12-46rdquorarr ldquoD12-219rdquo [label = ldquoDrdquo]
ldquoD12-47rdquorarr ldquoD12-25rdquo [label = ldquoSrdquo]ldquoD12-47rdquorarr ldquoD12-210rdquo [label = ldquoSrdquo]ldquoD12-47rdquorarr ldquoD12-211rdquo [label = ldquoSrdquo]ldquoD12-47rdquorarr ldquoD12-212rdquo [label = ldquoSrdquo]ldquoD12-47rdquorarr ldquoD12-314rdquo [label = ldquoArdquo]
ldquoD12-48rdquorarr ldquoD12-211rdquo [label = ldquoSrdquo]ldquoD12-48rdquorarr ldquoD12-212rdquo [label = ldquoSrdquo]ldquoD12-48rdquorarr ldquoD12-210rdquo [label = ldquoSrdquo]ldquoD12-48rdquorarr ldquoD12-213rdquo [label = ldquoSrdquo]ldquoD12-48rdquorarr ldquoD12-33rdquo [label = ldquoSrdquo]ldquoD12-48rdquorarr ldquoD12-93rdquo [label = ldquoSrdquo]ldquoD12-48rdquorarr ldquoD12-914rdquo [label = ldquoSrdquo]
ldquoD12-49rdquorarr ldquoD12-51rdquo [label = ldquoSrdquo]ldquoD12-49rdquorarr ldquoD12-210rdquo [label = ldquoSrdquo]ldquoD12-49rdquorarr ldquoD12-53rdquo [label = ldquoSrdquo]ldquoD12-49rdquorarr ldquoD12-54rdquo [label = ldquoSrdquo]
F3 Interactions of WP5
ldquoD12-51rdquorarr ldquoD12-921rdquo [label = ldquoSrdquo]ldquoD12-51rdquorarr ldquoD12-922rdquo [label = ldquoSrdquo]ldquoD12-54rdquorarr ldquoD12-1011rdquo [label = ldquoSrdquo]ldquoD12-55rdquorarr ldquoD12-31rdquo [label = ldquoDrdquo]ldquoD12-55rdquorarr ldquoD12-313rdquo [label = ldquoDrdquo]
ldquoD12-56rdquorarr ldquoD12-712rdquo [label = ldquoDrdquo]ldquoD12-56rdquorarr ldquoD12-715rdquo [label = ldquoDrdquo]ldquoD12-56rdquorarr ldquoD12-713rdquo [label = ldquoDrdquo]
ldquoD12-59rdquorarr ldquoD12-212rdquo [label = ldquoSrdquo]ldquoD12-59rdquorarr ldquoD12-213rdquo [label = ldquoSrdquo]ldquoD12-59rdquorarr ldquoD12-43rdquo [label = ldquoSrdquo]ldquoD12-59rdquorarr ldquoD12-84rdquo [label = ldquoSrdquo]ldquoD12-59rdquorarr ldquoD12-96rdquo [label = ldquoSrdquo]ldquoD12-59rdquorarr ldquoD12-713rdquo [label = ldquoIrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 191 of 196
ldquoD12-510rdquorarr ldquoD12-73rdquo [label = ldquoIrdquo]
F4 Interactions of WP7
ldquoD12-71rdquorarr ldquoD12-37rdquo [label = ldquoArdquo]
ldquoD12-73rdquorarr ldquoD12-510rdquo [label=ldquoArdquo]ldquoD12-73rdquorarr ldquoD12-916rdquo [label=ldquoSrdquo]ldquoD12-73rdquorarr ldquoD12-917rdquo [label=ldquoSrdquo]ldquoD12-73rdquorarr ldquoD12-918rdquo [label=ldquoSrdquo]ldquoD12-73rdquorarr ldquoD12-919rdquo [label=ldquoSrdquo]ldquoD12-73rdquorarr ldquoD12-920rdquo [label=ldquoSrdquo]ldquoD12-73rdquorarr ldquoD12-921rdquo [label=ldquoSrdquo]
ldquoD12-76rdquorarr ldquoD12-220rdquo [label=ldquoSrdquo]ldquoD12-76rdquorarr ldquoD12-45rdquo [label=ldquoSrdquo]ldquoD12-76rdquorarr ldquoD12-91rdquo [label=ldquoSrdquo]ldquoD12-76rdquorarr ldquoD12-922rdquo [label=ldquoSrdquo]ldquoD12-76rdquorarr ldquoD12-923rdquo [label=ldquoArdquo]
ldquoD12-77rdquorarr ldquoD12-311rdquo [label=ldquoSrdquo]ldquoD12-77rdquorarr ldquoD12-41rdquo [label=ldquoArdquo]ldquoD12-77rdquorarr ldquoD12-92rdquo [label=ldquoSrdquo]ldquoD12-77rdquorarr ldquoD12-96rdquo [label=ldquoArdquo]ldquoD12-77rdquorarr ldquoD12-98rdquo [label=ldquoSrdquo]ldquoD12-77rdquorarr ldquoD12-912rdquo [label=ldquoSrdquo]
ldquoD12-79rdquorarr ldquoD12-310rdquo [label=ldquoSrdquo]
ldquoD12-711rdquorarr ldquoD12-917rdquo [label=ldquoArdquo]
ldquoD12-712rdquorarr ldquoD12-56rdquo [label=ldquoSrdquo]ldquoD12-712rdquorarr ldquoD12-93rdquo [label=ldquoSrdquo]
ldquoD12-713rdquorarr ldquoD12-56rdquo [label=ldquoSrdquo]ldquoD12-713rdquorarr ldquoD12-93rdquo [label=ldquoSrdquo]
ldquoD12-715rdquorarr ldquoD12-56rdquo [label=ldquoSrdquo]
ldquoD12-717rdquorarr ldquoD12-56rdquo [label=ldquoSrdquo]
ldquoD12-719rdquorarr ldquoD12-36rdquo [label=ldquoSrdquo]ldquoD12-719rdquorarr ldquoD12-37rdquo [label=ldquoSrdquo]ldquoD12-719rdquorarr ldquoD12-313rdquo [label=ldquoSrdquo]
ldquoD12-720rdquorarr ldquoD12-36rdquo [label=ldquoSrdquo]ldquoD12-720rdquorarr ldquoD12-37rdquo [label=ldquoSrdquo]
ldquoD12-724rdquorarr ldquoD12-95rdquo [label=ldquoSrdquo]
ldquoD12-727rdquorarr ldquoD12-38rdquo [label=ldquoSrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 192 of 196
F5 Interactions of WP8
ldquoD12-81rdquorarr ldquoD12-23rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-24rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-25rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-26rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-29rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-213rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-92rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-914rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-312rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-314rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-718rdquo [label=ldquoSrdquo]ldquoD12-81rdquorarr ldquoD12-221rdquo [label=ldquoDrdquo]ldquoD12-81rdquorarr ldquoD12-223rdquo [label=ldquoDrdquo]ldquoD12-81rdquorarr ldquoD12-72rdquo [label=ldquoDrdquo]ldquoD12-81rdquorarr ldquoD12-71rdquo [label=ldquoDrdquo]ldquoD12-81rdquorarr ldquoD12-73rdquo [label=ldquoDrdquo]ldquoD12-81rdquorarr ldquoD12-76rdquo [label=ldquoDrdquo]ldquoD12-81rdquorarr ldquoD12-714rdquo [label=ldquoDrdquo]
ldquoD12-82rdquorarr ldquoD12-718rdquo [label=ldquoSrdquo]
ldquoD12-83rdquorarr ldquoD12-312rdquo [label=ldquoSrdquo]ldquoD12-83rdquorarr ldquoD12-314rdquo [label=ldquoSrdquo]ldquoD12-83rdquorarr ldquoD12-31rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-32rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-33rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-36rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-35rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-37rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-38rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-39rdquo [label=ldquoDrdquo]ldquoD12-83rdquorarr ldquoD12-311rdquo [label=ldquoDrdquo]
ldquoD12-84rdquorarr ldquoD12-914rdquo [label=ldquoSrdquo]ldquoD12-84rdquorarr ldquoD12-916rdquo [label=ldquoSrdquo]ldquoD12-84rdquorarr ldquoD12-31rdquo [label=ldquoDrdquo]ldquoD12-84rdquorarr ldquoD12-32rdquo [label=ldquoDrdquo]ldquoD12-84rdquorarr ldquoD12-33rdquo [label=ldquoDrdquo]
ldquoD12-86rdquorarr ldquoD12-916rdquo [label=ldquoSrdquo]
F6 Interactions of WP9
ldquoD12-91rdquorarr ldquoD12-220rdquo [label = ldquoSrdquo]ldquoD12-91rdquorarr ldquoD12-223rdquo [label = ldquoSrdquo]ldquoD12-91rdquorarr ldquoD12-214rdquo [label = ldquoSrdquo]ldquoD12-91rdquorarr ldquoD12-215rdquo [label = ldquoSrdquo]ldquoD12-91rdquorarr ldquoD12-36rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-37rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-38rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-310rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-21rdquo [label = ldquoDrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 193 of 196
ldquoD12-91rdquorarr ldquoD12-22rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-25rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-612rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-711rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-81rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-82rdquo [label = ldquoDrdquo]ldquoD12-91rdquorarr ldquoD12-24rdquo [label =ldquoArdquo]ldquoD12-91rdquorarr ldquoD12-86rdquo [label =ldquoArdquo]ldquoD12-91rdquorarr ldquoD12-66rdquo [label=ldquoIrdquo]ldquoD12-91rdquorarr ldquoD12-108rdquo [label=ldquoIrdquo]ldquoD12-91rdquorarr ldquoD12-109rdquo [label=ldquoIrdquo]
ldquoD12-92rdquorarr ldquoD12-215rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-220rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-36rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-44rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-45rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-63rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-66rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-76rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-726rdquo [label=ldquoSrdquo]ldquoD12-92rdquorarr ldquoD12-211rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-212rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-314rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-41rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-48rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-59rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-1213rdquo [label =ldquoDrdquo]ldquoD12-92rdquorarr ldquoD12-214rdquo [label=ldquoArdquo]ldquoD12-92rdquorarr ldquoD12-311rdquo [label=ldquoArdquo]ldquoD12-92rdquorarr ldquoD12-77rdquo [label=ldquoArdquo]ldquoD12-92rdquorarr ldquoD12-711rdquo [label=ldquoArdquo]
ldquoD12-93rdquorarr ldquoD12-212rdquo [label=ldquoSrdquo]ldquoD12-93rdquorarr ldquoD12-43rdquo [label=ldquoSrdquo]ldquoD12-93rdquorarr ldquoD12-612rdquo [label=ldquoSrdquo]ldquoD12-93rdquorarr ldquoD12-73rdquo [label=ldquoIrdquo]
ldquoD12-95rdquorarrldquoD12-215rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-222rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-44rdquo [label=ldquoIrdquo]ldquoD12-95rdquorarrldquoD12-69rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-610rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-721rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-725rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-102rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-124rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-1210rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-1213rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-1215rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-34rdquo [label=ldquoSrdquo]ldquoD12-95rdquorarrldquoD12-217rdquo [label=ldquoIrdquo]
ldquoD12-96rdquorarrldquoD12-211rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-214rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-220rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-41rdquo [label=ldquoIrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 194 of 196
ldquoD12-96rdquorarrldquoD12-44rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-45rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-64rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-66rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-71rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-723rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-1215rdquo [label=ldquoSrdquo]ldquoD12-96rdquorarrldquoD12-48rdquo [label=ldquoDrdquo]ldquoD12-96rdquorarrldquoD12-77rdquo [label=ldquoIrdquo]ldquoD12-96rdquorarrldquoD12-1213rdquo [label=ldquoDrdquo]ldquoD12-96rdquorarrldquoD12-210rdquo [label=ldquoArdquo]ldquoD12-96rdquorarrldquoD12-314rdquo [label=ldquoArdquo]ldquoD12-96rdquorarrldquoD12-711rdquo [label=ldquoArdquo]
ldquoD12-98rdquorarrldquoD12-210rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-211rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-220rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-43rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-55rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-66rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-69rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-610rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-46rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-728rdquo [label=ldquoSrdquo]ldquoD12-98rdquorarrldquoD12-213rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-217rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-311rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-315rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-41rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-510rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-76rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-716rdquo [label=ldquoDrdquo]ldquoD12-98rdquorarrldquoD12-724rdquo [label=ldquoDrdquo]
ldquoD12-99rdquorarrldquoD12-311rdquo [label=ldquoSrdquo]ldquoD12-99rdquorarrldquoD12-41rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-66rdquo [label=ldquoSrdquo]
ldquoD12-99rdquorarrldquoD12-29rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-210rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-211rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-214rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-48rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-728rdquo [label=ldquoDrdquo]ldquoD12-99rdquorarrldquoD12-315rdquo [label=ldquoArdquo]ldquoD12-99rdquorarrldquoD12-67rdquo [label=ldquoArdquo]ldquoD12-99rdquorarrldquoD12-726rdquo [label=ldquoIrdquo]
ldquoD12-912rdquorarrldquoD12-210rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-211rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-213rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-217rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-220rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-36rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-66rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-68rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-72rdquo [label=ldquoSrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 195 of 196
ldquoD12-912rdquorarrldquoD12-73rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-76rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-46rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-726rdquo [label=ldquoSrdquo]ldquoD12-912rdquorarrldquoD12-218rdquo [label=ldquoDrdquo]ldquoD12-912rdquorarrldquoD12-219rdquo [label=ldquoDrdquo]ldquoD12-912rdquorarrldquoD12-74rdquo [label=ldquoArdquo]ldquoD12-912rdquorarrldquoD12-75rdquo [label=ldquoArdquo]ldquoD12-912rdquorarrldquoD12-716rdquo [label=ldquoArdquo]ldquoD12-912rdquorarrldquoD12-510rdquo [label=ldquoIrdquo]
ldquoD12-914rdquorarrldquoD12-24rdquo [label=ldquoSrdquo]ldquoD12-914rdquorarrldquoD12-210rdquo [label=ldquoSrdquo]ldquoD12-914rdquorarrldquoD12-211rdquo [label=rdquoCrdquo]
ldquoD12-916rdquorarrldquoD12-215rdquo [label=ldquoSrdquo]ldquoD12-916rdquorarrldquoD12-216rdquo [label=ldquoSrdquo]ldquoD12-916rdquorarrldquoD12-63rdquo [label=ldquoSrdquo]ldquoD12-916rdquorarrldquoD12-612rdquo [label=ldquoSrdquo]ldquoD12-916rdquorarrldquoD12-82rdquo [label=ldquoDrdquo]ldquoD12-916rdquorarrldquoD12-86rdquo [label=ldquoDrdquo]ldquoD12-916rdquorarrldquoD12-64rdquo [label=ldquoArdquo]ldquoD12-916rdquorarrldquoD12-216rdquo [label=ldquoSrdquo]
F7 Interactions of WP10
ldquoD12-101rdquorarrldquoD12-21rdquo [label=ldquoDrdquo]ldquoD12-101rdquorarrldquoD12-22rdquo [label=ldquoDrdquo]ldquoD12-101rdquorarrldquoD12-25rdquo [label=ldquoDrdquo]ldquoD12-101rdquorarrldquoD12-26rdquo [label=ldquoDrdquo]ldquoD12-101rdquorarrldquoD12-121rdquo [label=ldquoDrdquo]ldquoD12-101rdquorarrldquoD12-1211rdquo [label=ldquoDrdquo]ldquoD12-101rdquorarrldquoD12-129rdquo [label=ldquoArdquo]ldquoD12-101rdquorarrldquoD12-1214rdquo [label=ldquoArdquo]ldquoD12-102rdquorarrldquoD12-216rdquo [label=ldquoSrdquo]ldquoD12-102rdquorarrldquoD12-223rdquo [label=ldquoDrdquo]ldquoD12-102rdquorarrldquoD12-56rdquo [label=ldquoDrdquo]ldquoD12-102rdquorarrldquoD12-74 rdquo [label=ldquoDrdquo]ldquoD12-102rdquorarrldquoD12-76rdquo [label=ldquoDrdquo]ldquoD12-102rdquorarrldquoD12-1211rdquo [label=ldquoDrdquo]ldquoD12-102rdquorarrldquoD12-1214rdquo [label=ldquoArdquo]
ldquoD12-103rdquorarrldquoD12-1214rdquo [label=ldquoSrdquo]ldquoD12-103rdquorarrldquoD12-1215rdquo [label=ldquoSrdquo]ldquoD12-103rdquorarrldquoD12-223rdquo [label=ldquoDrdquo]
ldquoD12-108rdquorarrldquoD12-47rdquo [label=ldquoSrdquo]ldquoD12-108rdquorarrldquoD12-1214rdquo [label=ldquoSrdquo]ldquoD12-108rdquorarrldquoD12-1215rdquo [label=ldquoSrdquo]ldquoD12-108rdquorarrldquoD12-223rdquo [label=ldquoDrdquo]ldquoD12-108rdquorarrldquoD12-1213rdquo [label=ldquoIrdquo]ldquoD12-108rdquorarrldquoD12-1217rdquo [label=ldquoIrdquo]
ldquoD12-109rdquorarrldquoD12-216rdquo [label=ldquoSrdquo]
Version 20
D12ndash REQUIREMENTS ASSESSMENT REPORT Page 196 of 196
ldquoD12-109rdquorarrldquoD12-21rdquo [label=ldquoDrdquo]ldquoD12-109rdquorarrldquoD12-22rdquo [label=ldquoDrdquo]ldquoD12-109rdquorarrldquoD12-1213rdquo [label=ldquoIrdquo]ldquoD12-109rdquorarrldquoD12-1214rdquo [label=ldquoIrdquo]ldquoD12-109rdquorarrldquoD12-1215rdquo [label=ldquoIrdquo]
Version 20