News Feed
Forgot your password?
New user?
D1.4 Design Requirements v3.0 open for public review
June 2009 version (v3.0) of deliverable D1.4 (Design Requirements) is open to public comments, feedback and review !
All feedback welcome !
You could download it and publish comment from here:
http://www.tas3.eu/project/publications/download
(you need to login first to put a comment)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.
