Object oriented design question - how should business objects relate to Windows workflow foundation in n-tier solution
Posted on 2007-10-12
I'm designing an n-tier solution using a smart client (WPF) . Using Windows workflow foundation in business layer looks nice because a lot of the functionality revolves around workflow. So I'm hoping that using WF instead of rolling our own support for saving workflow to database, retrieveing workflow from database, monitor if changes in status have been made etc wil save some implementation time.
Does anyone have any info on how typical business objects should relate to workflow concerning classes?
If I want to design a sales support application for real estate agents I could have a class House. Status changes in workflow could be "waiting for assessment", "assessment done", "ready to advertise", "advertised", "offer is made","offer rejected","offer accepted","waiting for contract to be signed","contract signed","sold" etc.
Should I have a class "House" and how should it relate to workflow?
Does it make sense to use WF in this case?
Are there samples or info available that could shed some light on this?