Difference between revisions of "GCore Based Information System Specification"
Manuele.simi (Talk | contribs) (→Architecture) |
Manuele.simi (Talk | contribs) (→Architecture) |
||
| Line 28: | Line 28: | ||
=== Architecture === | === Architecture === | ||
To deliver the quality of service and performances and to handle growing amounts of information (scalability), the Information System is composed by a set of Web Services and client libraries. | To deliver the quality of service and performances and to handle growing amounts of information (scalability), the Information System is composed by a set of Web Services and client libraries. | ||
| + | |||
| + | [[Image:IS-Architecture.jpg|frame|center|Figure 1. Information System Architecture and Main Interactions]] | ||
== Deployment == | == Deployment == | ||
Revision as of 23:28, 23 February 2012
Contents |
Overview
The Information System (IS) is the core facility connecting producers of resources to their consumers. It acts as a registry of the infrastructure by offering global and partial views of its resources and their current status.
The approach provided by the IS is of great support for the dynamic deployment capabilities and the interoperability solutions offered by the Resource Management facilities.
Key features
- Resource Publication, Access and Discovery
- ...
- Standards - compliant with WS-DAIX Specification v1.0
- IS offers a full implementation of WS-DAIX v.1.0, a widely accepted standard defining a set of data access interfaces for XML data resources
- Distribution
- ...
Design
Philosophy
This is the rationale behind the design. An example will be provided.
Architecture
To deliver the quality of service and performances and to handle growing amounts of information (scalability), the Information System is composed by a set of Web Services and client libraries.
Deployment
Usually, a subsystem consists of a number of number of components. This section describes the setting governing components deployment, e.g. the hardware components where software components are expected to be deployed. In particular, two deployment scenarios should be discussed, i.e. Large deployment and Small deployment if appropriate. If it not appropriate, one deployment diagram has to be produced.
Large deployment
A deployment diagram suggesting the deployment schema that maximizes scalability should be described here.
Small deployment
A deployment diagram suggesting the "minimal" deployment schema should be described here.
Use Cases
The subsystem has been conceived to support a number of use cases moreover it will be used to serve a number of scenarios. This area will collect these "success stories".
Well suited Use Cases
UC: Resource Publication
UC: Resource Discovery
UC: Resource Access
UC: Resource Notifications
UC: Mediator among Resource Models
Less well suited Use Cases
Describe here scenarios where the subsystem partially satisfied the expectations.
