Possible Model - View - Presenter (Supervising Controller)?

[emaiannone]

The architectural pattern might actually be a MVP Supervising Controller, where views do not have any data binding and do not call model logic.
Model is the application, View is the set of Swing dialogs (along with their event handlers) + StartAction and Presenter might be CoreDriver.

Proposal:

• Rename application --> model
• Rename presentation --> gui (this allow future User Interfaces)
• Rename CoreDriver --> CorePresenter
• CoreDriver(Presenter) should observe on each dialogs instead of using callback interfaces
  • Dialogs should implement a View/Observable interface
  • CoreDriver(Presenter) should implement an Observer interface
• Split CoreDriver(Presenter) into some Presenters

Another alternative is with Mediator pattern