I think his point is to be wary of the Noun / Verb approach and focus on 'what you want to do' and start building from there. That way you'll end up with a design where each object has a purpose and responsibilities will be spread evenly throughout your model.
Rather than think about classes he urges you to think about messages between objects. ie the containment vessel tells the hot water source to do something so you now have ContainmentVessel with a dependency to HotWaterSource. When you think about behaviour your Model gradually forms from there. I don't think there's any formula or magic wand to designing a domain model and even after I finish coding something I tend to see bits I've gotten wrong and hopefully learn from. I am improving though, slowly but surely! Alan www.alanlivie.com ________________________________ From: John Whish <[email protected]> To: [email protected] Sent: Friday, January 9, 2009 10:03:47 AM Subject: [CFCDEV] Re: Analysis and Design process @Alan, I've just finished reading the excellent "Coffee Maker" article you recommended. Good food (or drink!) for thought, however he does say "I did not just sit down one day and develop this design in a nice straightfoward manner.... this design has been refined over time." Which does rather bring us back full circle. How do we decide on our classes in the first place? Sorry, if I sound like I'm whining, I guess I'm just frustrated by my lack of knowledge :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
