Last Updated: 9 January 2009
There are a number of essential tools required to apply Shlaer-Mellor OOA/RD or Executable UML successfully:
OOA Tool is a Shlaer-Mellor and Executable UML CASE tool implemented in 100% pure Java™ which includes a model editor and will include a simulator and translator. It is currently being developed in parallel with OOA10. Once development finishes, a Professional edition will be released at a competitive price, while a Standard edition will be distributed at no cost indefinitely. In the meantime, an early access BETA release is available for download.
Service domain products consist of several deliverables:
Service domains may be supplied as black boxes with no documentation beyond the public interface. The supplier may even obfuscate model element names to deter users from investigating the internal logic. Black box domains generally restrict the scope of any bridging to the public interface, i.e. synchronous services and external events incoming, domain-crossing events and bridging processes outgoing. However, service domains are more adaptable if supplied as white boxes with documentation covering the whole domain. White box domains allow users to create arbitrary bridge mappings between internal model elements. They also make it easier for users to debug the service domain in a model simulator and optimize bridges from the service domain to new software architectures in unforeseen ways.
Once development of OOA Tool finishes, a number of service domains will be developed. The first will be a Java Swing User Interface domain which plugs into the OOA Tool simulator allowing simple graphical user interfaces to be created and used prior to any translation effort. This service domain will also be bridged to any Java software architectures offered by Kavanagh Consultancy.
Software architecture products consist of several deliverables:
The use of a model for the software architecture allows complex validation and optimization processes to be performed that can't easily be carried out in archetype templates. However, archetype templates should still be used since this allows users to tailor the structure and content of generated code without having to change the generated code.
Once development of OOA Tool finishes, a production quality Java Software Architecture will be developed. This software architecture will support concurrent and distributed applications using Java Remote Method Invocation (RMI).
We would like to talk to anyone interested in developing software architectures for other deployment platforms. Few Shlaer-Mellor or Executable UML users have the ability or resources to develop a software architecture from scratch. Therefore, the more deployment platforms there are available, the faster the Shlaer-Mellor and Executable UML user base will grow.