Dashboard > CI Development > ... > Agent Contract Network > Agent CN Iteration4
Log In   View a printable version of the current page.
CI Development
Agent CN Iteration4
Added by Emilia Farcas , last edited by Emilia Farcas on Jul 10, 2009  (view change)
Labels: 
(None)

Scope

Main goal: end to end view of the story using the messaging service as use case example. Provide a consistent write up at the end of the iteration as input for a report and as baseline for MREFC construction efforts.

Tasks

Tasks proposed for iteration 4:

  • Investigate Messaging Service Use case. Use as example to check out the completeness of the specification. We need a real-world example of a distributed system where policy is applied.
    • Broker is a Community and has two types of resources (Named Exchanges - for publishing, and Queues - for retrieving data)
    • OOI MS Federation is a Community (is the Broker seen here as a resource of the federation or as a community affiliation?)
    • Exchange Space Community has resources as Exchange Points
    • Extend the use case such that a data stream from an instrument is published to an exchange point.
    • Core pattern: registration, allocation, use
  • Investigate prototype portability - interfaces between the transport, AMS, and policy.
  • Map the specification language into executable code
  • Policy Specification - investigate Rule languages 
  • Consistent documentation

Timeline for Iteration 4

  • Start - July 6th
  • End - mid/end of August

Design

Integrated model showing the relationship between organization specification, contracts, agents, conversations, Jess rules, etc.

The registration pattern for the Messaging Service use case. (Notation: the black arrow shows the scope)


 

Powered by Atlassian Confluence 2.7.1, the Enterprise Wiki. Bug/feature request - Atlassian news - Contact administrators