This development cycle will be a short one - 2 weeks. We will implement the classes to satisfy requirements 7 and partially 10. We will provide a way for a structured matcher to be loaded programmatically by the mesage StructuredMatcher.load( String matcherName ). To do this, the existing object serialization code which now resides in the view's inner controller, must be moved into a separate class (See Fig.1.1) .
Fig. 1.1: Serialization code is moved to class SerializationBroker.
By doing so, the structured matcher can delegate serialization tasks to the support object of SerializationBroker, instead of having it done in the controller (See Fig.1.2). This way, an external object can request the same service without going through the structured matcher's view.
Fig. 1.2: The task of loading a matcher is delegated to an object of SerializationBroker.