Issues for Business Motivation Model 1.1 Revision Task Force

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 11695: class diagram issue
Issue 11812: Should BMM include business rules, decisions, both, or neither
Issue 12280: Issues on BMM Beta 3 dtc/07-08-03 table 8.2
Issue 12281: Issues on BMM Beta 3 dtc/07-08-03 table 8.9

Issue 11695: class diagram issue (bmm-rtf)

Class diagrams in Business Motivation Model show association names where we expect role names as per UML specifications. This is misleading. Drawing Fig 8.2 on Star UML produced the following code: public class Vision { public Goal amplified_by; } public class Goal { public Vision amplifies; } 

At the BMI meeting on 10Dec07/Burlingame, there was a discussion on decision modeling and its relationship to existing modeling needs and standards. An action from the meeting was to raise the question of whether business decisions per se should be defined in BMM alongside, or instead of, business rules, or whether business motivation per se should be independent of business decisions (and/or business rules). 

 

{This was considered a possible issue for a BMM v2 RFP, but I am raising it with the RTF on the basis that it is up to the RTF to determine whether any “issue” is for a future version or not.}

 

[From my understanding of BMM v1.2, processes are defined outside of BMM, and probably decisions are related more to processes and are guided by business rules / driven by policies.]

 

Caveat: this is going to be difficult to answer without a formal definition of a decision model. And I am not going to define one at this stage of discussions! J 

However, it is probably safe to assume that a Decision Table (which I define as a table of conditional elements with some action as a conclusion, rather than the fact definition type of “Decision Table” that Donald was telling me is defined as a part of SBVR) is an instance of a Decision Model. And that you invoke decision tables (and services) in process activities in order to direct processes (and services). But decisions may be defined separately from process, of course, although their “execution” (manual or automated) context is probably always going to be in a process of some kind.

 

Disclaimer: this issue may be subject to revision as the terminology is refined. 

 

2 cents of Comment: I think the answer is “yes, decisions are related to motivation but are not part of motivation”. I will leave to others the discussion on whether (SBVR type) business rules are part of motivation or a simply related to motivation. 

 Table 8.2 has a duplicate line:

EU-Rent           To provide industry-leading customer service

 Table 8.9 has the first entry duplicated in the second (which has some additional text)