Document Structure. 2.1 In general, the Agreement will consist of the following documents, whereby in the event of any inconsistency or conflict between or among provisions of the following documents, the contents of the document first listed shall have precedence and shall prevail over the documents listed later, in descending order:
Document Structure. Section 3.0 details the three opportunity analyses. Supporting information for Section 3.0 is contained in the Appendices. Appendix A contains the Minnesota wants and needs definitions, Appendix B contains the Minnesota services definitions, Appendix C contains the demand weight analysis data, and Appendix D contains the demographic analysis data. Section 4.0 details the strength relationship analysis.
Document Structure. The remainder of this document is structured as follows: in Section 2 we describe our approach to designing a protocol for the re-negotiation of contracts and com- pare it against other approaches. Section 3 then outlines the requirements (and non-requirements) for the protocol. Section 4 describes the assumptions made and the framework within which a re-negotiation occurs. Section 5 then specifies the protocol. The paper concludes with Section 6, which provides a summary and discusses future work.
Document Structure. The remainder of this report is organised to describe the design of the whole D4Science “system” to the reader through different views each adding more detail to the previous. Section 2 introduces the D4Science Reference Model, i.e. the concepts and relations among them characterising the overall system. Section 3 describes the gCube Reference Architecture, i.e. the overall design model adopted to implement the constituents 1 The gCube Framework consists of 22 subsystems and 166 components (more than 60 web services, libraries, third parties software, portlets, etc). identified by the Reference Model. In particular, it provides the reader with a picture of the whole system in a nutshell. Having introduced the overall picture, the rest of the sections focus on providing the reader with details about the various parts of the system. Section 4 presents the gCore Framework as well as its main features. Section 5 presents the gCube Infrastructure Enabling Services, i.e. the gCube technology designed to support the operation of the infrastructure as well as the dynamic creation of Virtual Research Environments. Section 6 introduces the gCube Information Organisation Services, i.e. the gCube technology supporting Information Objects management including the standard Repository-oriented facilities like creation, storage, access implemented by relying on (i) a rich notion of Information Objects and (ii) a very distributed operational environment including Grid storage facilities. Section 7 presents the gCube Information Retrieval Services, the gCube technology supporting the retrieval of Information Objects. The very open and customisable framework supporting the retrieval of heterogeneous Information Objects from different and distributed data sources through a broad set of methodologies and approaches ranging from Google-like queries to geo-spatial queries is discussed in detail. Section 8 introduces the gCube Presentation Services, i.e. the gCube technology designed to provide end-users, both human and inanimate, with an highly integrated and customisable environment making all gCube facilities available through a single access point. Finally, Section 9 summarises the overall main features and provides hints for future consolidation and enhancement activities of the system. The gCube system follows a Service Oriented Approach, thus its main constituents are implemented by Services (actually Web Services either stateful or plain). Each constituent Service is docu...
Document Structure. This document is comprised of the following chapters: Chapter 1 is the introductory section of this document.
Document Structure. This document is structured to capture the key conditions of the agreement in a logical order. It is understood that the agreement may be changed at any time by the mutual consent of both parties using the revision history and approval records contained in the Document Distribution, Approval and Revision History.
Document Structure. This section describes the structure of the document. - Section 1 is this introduction - Section 2 describes the service components - Section 3 define the services terms and conditions of usage
Document Structure. It is important to realise that an SLA, no matter how detailed, will not provide sufficient assurance for a customer to trust a service provider with their data. The approach of auditing a service provider and using an audit certificate as evidence of trustworthiness is discussed in Chapter 2 and a survey of the AV preservation community’s attitude to trust is described and the results presented. The key relationships between the service, resources, service level agreements (SLAs) and customer interactions are outlined in Chapter 3. Chapter 4 then provides the necessary background to understanding how SLAs can be managed, discussing the importance of not including objectives or constraints in an SLA that cannot be measured, proposing how to capture the necessary terms using a generic framework and outlining architectural options for measurement and management systems.
Document Structure. Following above concept, a set of six evaluation criteria was defined in order to evaluate all use cases. They are presented in chapter 2.1
Document Structure. The contents of this document are structured in sections as follows:
