Common use of HEP Applications Clause in Contracts

HEP Applications. At the beginning of the project, and throughout its lifetime, there will be a continuing dialogue between HEP applications and middleware developers for the processes of requirements gathering , grid service design and the practical evaluation of software for its functionality and performance. Applications will also be part of the testing and acceptance processes for the middleware. We have learned from DataGrid that all of these processes need to be ongoing to avoid ‘big bang’ effects due to infrequent overall system status reviews. This ongoing dialogue will be accomplished by HEP applications participation in the architecture, design and system testing groups. To facilitate this dialogue the HEP applications staff will have to work as a coherent team, whilst still maintaining experiment specific support, but looking for commonality in the support and associated tools.

HEP Applications. At the beginning of the project, and throughout its lifetime, there will be a continuing dialogue between HEP applications and middleware developers for the processes of requirements gathering , grid service design and the practical evaluation of software for its functionality and performance. Applications will also be part of the testing and acceptance processes for the middleware. We have learned from DataGrid DataGRID that all of these processes need to be ongoing to avoid ‘big bang’ effects due to infrequent overall system status reviews. This ongoing dialogue will be accomplished by HEP applications participation in the architecture, design and system testing groups. To facilitate this dialogue the HEP applications staff will have to work as a coherent team, whilst still maintaining experiment specific support, but looking for commonality in the support and associated tools.