This presentation gives a high level view of a CAETI learning space architecture that is based on various agents interacting through a MUD.
[Balzer, 95b] Bob Balzer. Architecture Value Added {Slides}. Computer Assisted Education and Training Initiative. Kickoff Meeting. NASA AMES, October 11-13, 1995.
This presentation makes the case for a MUD-based learning space architecture, and summarizes the integrated learning space demo that is planned for spring 1996.
[Balzer, 95c] Bob Balzer. CAETI Architecture Concepts. October, 1995.
This paper is a working draft outlines some of the basic concepts (rooms, agents, objects, simulators) for a long term vision of a MUD-based learning space architecture. This draft is the basis for the formalization in [Smith, 96a], and it is considered in the hierarchy of architectures suggested in [Luckham, 96a].
[Baumgart, 96a] Jim Baumgart, Seth Golub, Eric Sincoff, Andrew Teklemariam, Neil Jacobstein. CAETI Common Object Services Architecture. Sixth Draft - for Review & Comment. February 28, 1996. "This draft is for review and comment only, and is not to be redistributed outside of the CAETI Architecture Working Group without authorization."
This 40 page paper, which has been developed by the EAGIL cluster, is the most detailed architecture document that we had seen to this point. "The purpose of this document is to propose a minimalist, low-level, data-sharing architecture for building CAETI applications." -p2. It is a client server architecture that is based on CAETI processes exchanging messages over TCP. It contains a statement of objectives, an architectural overview, and proposals for a common objective services architecture (COSA) and for some domain specific services.
[Bellman, 96a] Kirstie Bellman. {Architecture Slides, 21-28}. Computer Assisted Education and Training Initiative. CAETI Community Meeting, University of Texas, Arlington, March 20-22, 1996. Online {password required}
This part of Kirstie's opening presentation describes the role of architecture in CAETI. Slide 24, "Minimal Architectural Requirements", provides the best current description of the minimal CAETI architecture. Further elaboration of these minimal requirements is given in [Harbison, 96a].
[CAT, 96a] CAETI Architecture Team. CAETI Minimal Architecture with Extensions, Version 1.0, Rev 4. May 8, 1996.
"This paper documents the CAETI Minimal Architecture." It ".. formally specifies the minimal messaging compliance that developers are asked to achieve", gives some examples of the messages, lists some basic architectural requirements, and discusses some optional additional services, including name service and security."
[Coglianese, 95a] Lou Coglianese. Systems Integration {Slides}. Computer Assisted Education and Training Initiative. Kickoff Meeting. NASA AMES, October 11-13, 1995.
This presentation describes the role of the Loral System Integration Team and the computing environment expected in the DoDEA schools.
[Coglianese, 96a] Lou Coglianese, Mark Olson, Robert Pittman, Rich Saxton. Systems Integration Information Package. Loral Federal Systems - Owego. CAETI-LOR-95- 01 (Version 1.0). March 11, 1996.
This document describes Loral's system integration plan. "The main objective of the system integration process is to create integrated baseline systems for the CAETI schools from the TEEs, IFDs, and the site infrastructure. The system baseline provides both developers and DoDEA the information required to replicate, install and use the CAETI products." -- p3.
[Finin, 93a] Tim Finin, Jay Weber, Gio Wiederhold, Michael Genesereth Richard Fritzson, Donald McKay, James McQuire, Richard Pelavin, Stuart Shapiro, Chris Beck (The DARPA Knowledge Sharing Initiative External Interfaces Working Group). DRAFT Specification of the KQML Agent-Communication Language plus example agent policies and architectures. June 15, 1993.
"KQML is intendewd[sic] to be a high-level language to be used by knowledge- based system[sic] to share knowledge at run-time." Some of the minimal CAETI architecture is based on KQML. See [CAT, 96a].
[Good, 96a] Donald I. Good, Michael K. Smith. A CAETI Architectural Monitor. Computational Logic, Inc. April 12, 1996.
"The key idea is to build an architectural monitor that, at least in principle, could be executed to monitor ongoing compliance with the requirements. In addition, the monitor would have a mathematical definition that would enable rigorous analysis of the requirements. We believe that the architectural monitor would be useful in defining the requirements, in establishing a precise build-to specification for implementors and in testing compliance with the requirements." -- p1
[Good, 96b] Donald I. Good. Message Transport Model 1 of the Minimal CAETI Architecture. Computational Logic, Inc. May 21, 1996.
This note derives a mathematical model of the minimal CAETI architecture from i) Kirstie Bellman's slide [Bellman, 96a] that introduced the idea of a minimal architecture, and ii) Karan Harbison's April 14 email [Harbison, 96a] that elaborated on Kirstie's slide. The note also contains a simple simulator of the architecture.
[Good, 96c] Donald I. Good. Message Transport Model 1 of the Minimal CAETI Architecture. Computational Logic, Inc. Work in progress.
This working note is an attempt in progress to build a mathematical model of the minimal CAETI architecture that is based on [CAT, 96a]. This is the first draft document that attempts to described the minimal architecture.
[Harbison, 95a] Karan Harbison, Bud Hammons, Gail Haddock. CAETI Architecture/Domain Modeling Information {Slides}. Pogo Arch Team/ HIIP Arch Team. University of Texas - Arlington. Computer Assisted Education and Training Initiative. Kickoff Meeting. NASA AMES, October 11-13, 1995.
This presentation describes the potential roles of architecture and domain modeling in CAETI.
[Harbison, 96a] Karan Harbison. Architecture Efforts {CAETI Minimal Architecture Compliance Update}. Email 4/14/96 to caeti@nosc.mil.
This message provides some elaboration of Kirstie's March 20 slide [Bellman, 96a] that describes the minimal architectural requirements.
[Hayes-Roth, 95a] Hayes-Roth, Frederick. Architecture-Based Development & Acquisition -- Where are We and Where are We Going? {Slides}. Computer Assisted Education and Training Initiative. Kickoff Meeting. NASA AMES, October 11-13, 1995.
The presentation gives a DSSA view of software architecture.
[Luckham, 96a] David Luckham, James Vera, Frank Belz(TRW). Towards an Abstraction Hierarchy for CAETI Architectures, and Possible Applications. Program Analysis and Verification Group, Computer Systems Lab, Stanford University and TRW. March 18, 1996.
"This draft document proposes a four level abstraction hierarchy for CAETI systems architectures for review and discussion by the CAETI community. Some possible applications are described briefly." -- Abstract. This paper advocates multiple views of the CAETI architecture. It refers to concepts in [Balzer, 95c] and[Smith, 96a], and it shows how some of the architectural concepts discussed can be represented in Rapide.
[Postel, 81a] Jon Postel. Transmission Control Protocol: DARPA Internet Program Protocol Specification. (RFC 793). Information Sciences Institute, University of Southern California. September, 1981.
[Smith, 96a] Michael K. Smith. MOO Events: Preconditions and Effects. Computational Logic, Inc. 2/22/96.
"This document represents a step toward the formalization of LambdaMOO events, including their preconditions and postconditions. The documented events are based on those presented in [Balzer, 95c]." -- Abstract
[Suthers, 96a] Daniel D. Suthers. Abstraction hierarchies for architecture descriptions. Email to its-commarch, eagil-architecture. May 18, 1996.
This is a follow up to [Luckham, 96a]. The message "concerns" the utility of layered architectural descriptions, and discusses what levels of description may be useful."
[Suthers, 96b] Daniel D. Suthers. Abstraction hierarchies for architecture descriptions. Email to its-commarch, eagil-architecture. May 18, 1996.
"To exemplify the approach discussed in the previous post, here is the beginnings of a layered architecture description."
[Unknown, 95a] CAETI Home Page. {Password required}
Organizations and Groups. {CAT is not mentioned}
Architecture/Domain Modeling. {Password required}.
[Unknown, 95b] Software Architecture Technology Guide.
"This node was developed under a STARS task ... to provide DoD software developers with an overview of software architecture technology and to serve as "virtual road map" to additional web resources for understanding and applying architectural techniques to domain-specific reuse." -- 3/13/95.
[Unknown, 96a] CAPER Architecture. Atlanta Subgroup Meeting. March 1-2, 1996. {Slides}
This is a record of the meeting.
[Unknown, 96b] CAETI System Technical Requirements. Loral Federal Systems - Owego {I think}. FTPed 3/11/96.
[Unknown, 9x] The Stanford Rapide Project.