Scenario (MVP) Layer
The plan is to create a swimlane diagram that allows the user the ability to model the interaction between the user and the domain. When the code generation runs it will create the View and Presenter following the Passive View Model View Presenter pattern as described by Matin Fowler at http://martinfowler.com/eaaDev/PassiveScreen.html.

The View is a an interface code file that describes how the UI should act. The Presenter is responsible for handling the state, the process and other elements associated with the interaction. The View should not have any business logic as should be as dumb (or Passive) as possible. This allows the MVP pattern to be used to implement other flavors of user interfaces.

Last edited Nov 4, 2007 at 8:29 PM by pliekhus, version 2

Comments

No comments yet.