We don’t have a roadmap currently defined. We do have a wishlist, which follows…
The following is a list of areas in which Cougaar would benefit based upon our experience. We have done research in the past on some of these, but the research did not lead to a production ready feature. Others, like Java modernization, are due to the underlying language evolving.
- Documentation improvements:
- updates to the Architecture and Developers guides,
- additional tutorials,
- instructions for installation and use on more recent operating systems,
- mining the old Forum for topics to add to the documentation or FAQ.
- A highly available distributed nameserver.
- Modernization to match evolution in the Java language which would involve first building Cougaar with Java 6 and then incorporating new language features. We anticipate using Java 6 will require changes in the Doclet interface and our bootstrap code. Cougaar is aspect orientated and could benefit from Java annotations and generics, especially having typed subscriptions with the Blackboard. (Java 7 is too new to be a useful deployment target for Cougaar.)
- A monitoring and deployment user interface. Cougaar is proven to scale to huge societies, but configuration of them is manual with the existing tools. Since the configuration files are XML, a tool to generate and view the configuration files would help manage large societies.