myGrid development is planned and executed in four-month cycles. For an overview of activities in the current and forthcoming and forthcoming development cycles, see the ProjectRoadmap.

The principal development activities in myGrid are as follows:

• BioServices: enabling existing bioinformatics services as Web Services and (later) as Grid Services

• LabBook: a demonstration application that allows users to annotate and organise data and provenance metadata into a narrative

• ServiceDirectory: an extended UDDI registry that will hold entries for relevant services discovered from other mor public registries, where relevance is tailored to the scientist or research group

• NotificationService: a general-purpose Web Service that supports a publish/subscribe model of event notification, based on JMS

• ContainerFramework: a container-based framework for conveniently impementing myGrid applications and services

• MyGridInformationRepository: a repository that can hold and support tailorable views over data of interest to an individual scientist, a research team and a research organization

• DistributedQueryProcessor: support for queries over multiple independent and distributed databases

• DatabaseUpdateNotification: a specific application of notification for alerting scientists to changes in relevant databases

• MetaData: support for creating and querying metadata that describes scientific resources

• ServiceOntologies: classifying and discovering scientific web services through ontologicial descriptions using decision logic reasoning

• GenericOperationInvocation: how are actual (e.g. Web or Grid Service or workflow) invocations constructed by general-purpose clients (e.g. the Gateway)? How are the operations related to services? How are the parameters described? What about optional or default parameters? etc.

• ProvenanceData: annotating and relating resources (data, workflow invocations, ...) to describe derivation, authorship, status, ...

• WorkFlow: support for capturing and enacting scientific workflows as "business processes" that coordinate interaction with web services

• EScienceMediator: an e-Science integration broker & process manager (supersedes the EScienceLayer aka Gateway: integrated access for applications via an API and scientist via command line and web portal interfaces)

• TalismanRAD: web based rapid application development, including access to both MyGrid and other resources.

• TextExtraction: support for intelligent mining of natural language text in documents and database fields

• User requirements: gathering the requirements of potential myGrid users, formally specify these requirements and produce exemplars from them.

• A matrix diagram showing the possible interactions between technologies in myGrid: AlansMatrixDiagram.

• ServiceInteractions: descriptions of the pairwise interactions between services as identified in AlansMatrixDiagram.

• ArchFigures: Architecture and Service stacks.

• ComponentInventory: a summary of what we intend to produce.

• SecurityArchitecture: preliminary steps to designing a myGrid security architecture.

-- NickSharman - 15 Nov 2002