News Feed
Forgot your password?
New user?
WP1 Requirements Analysis
TAS3_D1p1_State_of_the_Art.pdf
State of the Art Accepted by European Commission in June 2009. State of the Art structure: As described in the overall introduction, TAS3 covers a wide area of trust & security architecture. The definition of work packages fits the different requirements and expertise needed in particular areas of interest. Accordingly the document’s chapters are structured by each area and they address today’s standards and solutions. Each chapter outlines a specific problem in the context of TAS3, describing existing standards, research/commercial solutions, and can be the starting point for future enhancement. The structure of the document allows a quick overview of the overall project and the possibility to drill down into a specific and challenging area of TAS3. In addition, some of the chapters interlink and therefore provide a more detailed cross-reference. The purpose of the state of the art is to become the handbook of the TAS3 project permitting it to evolve beyond this current state.
TAS3_D1p2 Requirements Assessment Report v229052009.pdf
Requirements Assessment Report Accepted by European Commission in June 2009. Executive Summary: The objective of Deliverable 1.2 is to gather requirements regarding unsolved problems in the field of security and trust in service-oriented open and distributed environments that apply to the TAS3 project. Specifically, the deliverable translates the design requirements defined in Deliverable 1.4 [21] into the research and development activities that will be carried out in the different TAS3 WPs. In order to fulfill the objectives of this deliverable, we have completed a number of sequentially ordered activities. The results of these activities are documented in the different sections while some of the material we used and collected is included in the Appendices. First, we have reviewed the objectives of each work package and the solved and unsolved problems they are addressing with respect to the objectives of their work package. Next, we asked partners to elaborate or refine requirements based on these objectives and scenarios provided by the demonstrators in D1.4. Then, we compared the requirements elaborated by the TAS3 partners with the existing solutions for trust and security in service-oriented open and distributed environments. Last, we identified research and development challenges to be addressed by the partners in their future activities in order to fulfill their requirements. Last, we mapped the requirements to the TAS3 architecture. Some of these activities are to be re-iterated in the future based on our current analyses. In addition, in order to prioritize activities and discover interdependencies within and among work package activities, we analyzed requirements interactions in each WP. We have also analyzed the interdependencies among requirements elicited in different WPs. The prior interactions are represented in form of graphs to support the analysis, and the latter interdependencies in tables with the future prospect of visualizing inter-WP requirement interactions. The inter-WP requirements interaction analysis provides the partners with an understanding of the relationships between WPs. We expect the results to support the partners in partitioning their requirements and temporally ordering their activities in the future. Hence, the contribution of the deliverable is threefold. It provides a gap analysis which is used to map out future activities. The deliverable also elaborates on the technical, legal, policy and application domain requirements of TAS3. In addition, it gives an initial analysis of the interaction of the TAS3 requirements and maps out responsibilities and necessary cooperations for fulfilling these requirements as perceived by the WPs. Readers Guide: Section 3 provides a review of the objectives of each work package and the objectives are related to solved and unsolved problems in the field of security and trust in service-oriented open and distributed environments. Section 4 provides an analysis of the technical, legal and application domain requirements that address the solved and unsolved problems related to TAS3. The technical, legal, policy and application domain requirements elaborated for D1.2 are documented in Appendix B. This detailed listing of the requirements includes the justifications for each requirement and the interactions of each requirement within each WP. Section 5 provides the results of the first round of inter-WP requirements interaction analysis. Section 6 maps the requirements to the Architecture. Section 7 provides an analysis of the requirements fulfilled by existing solutions. The justifications for selected solutions are summed up in Section 7 and are included in detail in Appendix C. The templates we sent out to all the partners for requirements, requirements interactions, and existing solutions is included in Appendix A. Section 8 lists the activities that each work package has to complete in order to fulfill the requirements that cannot be fulfilled using existing solutions. We conclude in Section 9.
TAS3_D1p4 Design Requirements.pdf
Design Requirements Accepted by European Commission in June 2009. Executive Summary The WP01 “Design Requirements” (D1.4) has been updated concurrently with the “Requirement Report (D1.2)”. Whereas “Design Requirements” links in detail scenario and design requirements, the “Requirement Report” focuses on unsolved problems. Both “Requirement Report” and “Design Requirements” are cross-referenced to provide refinement, support or additional information. The “Design Requirements” document” and the “Requirements Report” takes as input the “State of the Art” (D1.1) and “Pilots Specifications and Use Case Scenarios” (D9.1) to ensure that the future design is achievable and consistent with TAS3’s expectations. These Design Requirements directly impact the Architecture Design (D2.1) and must be fulfilled within the future framework’s architecture. “Requirement Reports” and “Design Requirements” are the outcome of multiple meetings and discussions involving all partners. This document is a first iteration from January 2009, including the updates from June 2009; it provides a list of necessary features for TAS3 architecture. The included Design Requirements are derived from on a set of scenarios selected for having the most common requirements among the different demonstrator’s domains. This document will be updated, in its next version, with all the details from other scenarios and use cases. For a wider approach and a better understanding, specific Legal Requirements have been included. Legal aspects have been checked in relevant Design Requirements, however describing specific legal issues in the design document gives a better visibility of what should be part of contractual agreements or IT solutions. The same approach has been taken for Technical Validation that defines requirements to ensure that the framework will be testable.
