Hi Rockford,
I'm writing the question for you, but I'm really interested in the way other forum users work for designing BO's.
I'm fairly new to CSLA, but convinced that it is the right choice for the "command" part of our library. In the "Simple OOP Design question" post I read your answer on a question and as a "rookie" Scrum user I noticed the ending of the first sentence "... business use case (or story, or user scenario - which ever term works for you)".
Now, I'm not a purist, but reading the web on Agile, it would probably be seen as "blasphemy" to imply a use case being the same as a user story. Again, personally I don't care, but it made me wonder how does your design process work?
Do you design from customer artifacts like narrative documents, or do you use UML use cases, or perhaps user stories and specifications (as a ..., I want..., so that, etc.)?
Maybe the question isn't really within the scope of this forum, however, you being the creator of CSLA I can imagine that somehow you also had your design process in mind.
I'm hoping that you want to share your wisdom with the forum. I also bought the e-books today, so if the answer is in there, please let me know.
Cheers,
Peter