I'm still looking for industry standards that enable us to decide issues like this. Which tools do we use to model business rules? What are business rules? Does the BOM (Business Object Model) *explicitly* capture all the business rules? Is there one BOM for the system, or one BOM per business area (for example: sales, accounting, warehousing) within the system?
Responding to Steven Baynes: The need for a thing is not the same as the thing. A use case may capture requirements that motivate the creation of business rules, without stating the rules, themselves. What are business rules, exactly? The matter is unsettled. Responding to Les Munday (And how could I resist?): I find it surprising that you visualize business rules being about "attributes and relationships between attribut[e]s", and that you see them as flexible. Surely business rules must be in the domain of business activity, which is a set of mandatory and banned behaviour in a particular instance of a business. This looks to me like the right material for use cases. The point about flexibility is a good warning. The client wants flexibility when he has not clearly visualized the system. He may not want to clearly visualize the system. Your mission, if you choose to accept it, is to implement the fuzzy system that the client vaguely visualizes. It is impossible (or at least, highly unlikely), and you should not accept. -Eric "Baynes, Steve" wrote: > > All, The need for business rules must be captured in the use cases. Use > cases are the requirements documents. The implementation of the business > rules will flow throughout the rest of the analysis, design, implementation > and testing. > > Business rules may be driven by object state transition, the > inter-relationship between objects etc. This means no single artefact, > other than use cases, can capture the need for these rules. > > This is all "in my opinion". I look forward to some different views... > > Regards > Stephen Baynes > > -----Original Message----- > From: Les Munday [mailto:[EMAIL PROTECTED]] > Sent: 13 August 2002 22:24 > To: '[EMAIL PROTECTED]' > Subject: Re: (ROSE) UML and Business Rules > > Since I think of business rules as generally applying to > attributes and relationships between attributs, and since we > don't reference attributes within use cases, I would not > recommend stating business rules in use cases. > > I also think of business rules as being flexible, much more so > than I want my use cases to be. > > So my expectation would be to see business rules described by a > business object model. I think that they attach quite nicely to > the attributes and relationships in the class diagram. > > Much better place than use cases, IMO. > > Les. > > > > > UML and Business Rules - are these two things complementary? > > Some people believe that when you use UML/Use Cases you don't > need > > business rules techniques to capture business policies, > regulations, > > restrictions, etc. > > - since it got captured in use cases anyway. > > Other people think that UML is not sufficient for these > purposes. > > > > What is your approach to this? > > > > Thank you. > > > > David Lyalin ************************************************************************ * Rose Forum is a public venue for ideas and discussions. * For technical support, visit http://www.rational.com/support * * Post or Reply to: [EMAIL PROTECTED] * Subscription Requests: [EMAIL PROTECTED] * Archive of messages: * http://www.rational.com/support/usergroups/rose/rose_forum.jsp * Other Requests: [EMAIL PROTECTED] * * To unsubscribe from the list, please send email * To: [EMAIL PROTECTED] * Subject: <BLANK> * Body: unsubscribe rose_forum *************************************************************************
