Related Activities

COSA. COSA [Baumgart, 96a] is a much more detailed architecture than the minimal architecture [CAT, 96a]. If is-CMA-msg(m) is replaced by is-COSA-msg(m), a model of the transport of COSA messages is obtained. This simply requires that all messages transported be COSA messages instead of just minimal CMA messages. The requirement for COSA to comply with the minimal architecture can be expressed as _ is-CMA-msg(m) -> is-COSA-msg(m).

In short, every minimal CMA message must be admitted by COSA, but many other kinds of messages also may be COSA messages.

Learning Space Demo. The integrated learning space demo that was given in Arlington on March 22, 1996 illustrated the architecture described in [Balzer, 95a] at the October, 1995 kick-off meeting. This architecture consists of several agents communicating through a MUD. It appears that the CMA could not support this learning space demo because for adequate performance that demo would require direct use of TCP, and the CMA does not provide a way of opening and closing the connections needed to support the learning space.

Architecture Hierarchy. [Luckham, 95] proposes a four level hierarchy of architectures. Progressing from most abstract to least abstract, the four levels are user interface, concept of operations, abstract implementation, and resource. The CMA appears to fit in at approximately at the resource level, and the mathematical model proposed here appears to be an interface connection architecture as [Luckham, 95] recommends for CAETI.

Architectural Monitor. In [Good, 95] the idea of a architectural monitor was proposed. It is conceptually easy to envision such a monitor which continually observes the traffic at a CAETI address and checks it for compliance with various architectural requirements.

This page is URL http://www.computationallogic.com/software/caeti/architecture/model/related-activities.html