Różnice między wybraną wersją a wersją aktualną.
| Both sides previous revision Poprzednia wersja Nowa wersja | Poprzednia wersja | ||
|
pl:miw:miw08_bizrulesvocabularies [2008/05/26 12:42] miw |
pl:miw:miw08_bizrulesvocabularies [2019/06/27 15:50] (aktualna) |
||
|---|---|---|---|
| Linia 1: | Linia 1: | ||
| ====== BizRulesVocabularies ====== | ====== BizRulesVocabularies ====== | ||
| + | __**Projekt zakończony**__ | ||
| + | |||
| Tomasz, Bochen, <tomasz_bochen@o2.pl> | Tomasz, Bochen, <tomasz_bochen@o2.pl> | ||
| Linia 14: | Linia 16: | ||
| - | ====== Spotkania ====== | ||
| - | ===== 08.03.04 ===== | ||
| - | * podejścia do budowania słowników (bizrulesvocab) w uml | ||
| - | |||
| - | ===== 080318 ===== | ||
| - | * przykłady w sbvr, umieszczać w wiki, próba opisu [[hekate:hekate_case_thermostat|thermostatu]] w SBVR | ||
| - | * jak SBVR mapuje się na UML? | ||
| - | |||
| - | |||
| - | ===== 080401 ===== | ||
| - | * j.w. po ang | ||
| - | * jak zależności w SBVR maja się do ARD? | ||
| - | |||
| - | |||
| - | ===== 080415 ===== | ||
| - | * zapis słownika do thermostato w sbcr | ||
| - | * model thermostatu w sbeaver? | ||
| - | * wyszukanie narzędzi do SBVR w Internecie | ||
| - | |||
| - | ===== 080520 ===== | ||
| - | * początek sprawozdania: co to jest sbvr, structured english, skąd dok., narzędzia obecne i przyszle, opis therm w sbvr, przejscie do uml, prpozycja algorytmu __ard<->sbvr__, obserwacje->przyszłe możliwośći rozwoju | ||
| - | |||
| - | ====== Projekt ====== | ||
| - | ====== Sprawozdanie ====== | ||
| - | ====== Materiały ====== | ||
| - | * [[http://student.agh.edu.pl/~tbochen/SBVR.pdf|Źródło przykładu i trochę informacji na temat wykorzystania UML przy modelowaniu SBVR (słowników)]] | ||
| - | * [[http://portal.acm.org/citation.cfm?id=1342211.1342221&coll=Portal&dl=GUIDE&CFID=59641205&CFTOKEN=86539360|SBVR -> UML]] | ||
| - | * [[http://qrdn.brmsblog.com/2007/04/12/the-business-rules-development-cycle-an-introduction/|The Business Rule Development Lifecycle | ||
| - | ]] | ||
| - | * [[http://sbeaver.sourceforge.net/support/|SBeaver]] | ||
| - | * http://www.dulcian.com/papers/ODTUG/2001/RepresentingStructuralBusinessRules.htm | ||
| - | * http://www.omg.org/news/meetings/ThinkTank/past-events/2006/presentations/04-WS1-2_Hall.pdf | ||
| - | * http://objectriver.net/Leveraging%20Data%20Models.pdf | ||
| - | * http://www.semanticcore.org/Docs/Architecture%20of%20Business%20Modeling%2003-11-01.pdf | ||
| - | * http://bizrules.info/page/methodologies.htm | ||
| - | |||
| - | |||
| - | ===== Próba opisu termostatu w SBVR ===== | ||
| - | * [[hekate:hekate_case_thermostat|thermostat]] | ||
| - | * [[miw08_bizrulesvocabularies_sbvr_thermostat|thermostat sbvr]] | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | ===== Próba opisu termostatu za pomocą UML (Activity Diagram) ===== | ||
| - | *[[http://student.agh.edu.pl/~tbochen/MIW/p29-raj.pdf|Transformation of SBVR Business Design to UML Models]] | ||
| - | *[[http://student.agh.edu.pl/~tbochen/MIW/AD_themrostat.gif|Activity Diagram (thermostat)]] | ||
| - | ===== Model Development Tools (MDT) ===== | ||
| - | *[[http://www.eclipse.org/modeling/mdt/?project=sbvr|Coming soon...]] | ||
| Linia 342: | Linia 294: | ||
| **Downloads coming soon!** | **Downloads coming soon!** | ||
| + | |||
| + | |||
| Linia 369: | Linia 323: | ||
| == Rules == | == Rules == | ||
| - | * It is necessary, that in winter, on business hours, on workday, thermostat keep temperature 25 degrees Celsius in office. | + | * It is necessary, that in winter, on business hours, on workday, thermostat_settings is 25 degrees Celsius in office. |
| - | * It is necessary, that in winter, beside business hours, on workday, thermostat keep temperature 18 degrees Celsius in office. | + | * It is necessary, that in winter, beside business hours, on workday, thermostat_settings is 18 degrees Celsius in office. |
| - | * It is necessary, that in winter, all weekend, thermostat keep temperature 18 degrees Celsius in office. | + | * It is necessary, that in winter, all weekend, temperature_settings is 18 degrees Celsius in office. |
| - | * It is necessary, that in spring, on business hours, on workday, thermostat keep temperature 20 degrees Celsius in office. | + | * It is necessary, that in spring, on business hours, on workday, thermostat_settings is 20 degrees Celsius in office. |
| - | * It is necessary, that in spring, beside business hours, on workday, thermostat keep temperature 15 degrees Celsius in office. | + | * It is necessary, that in spring, beside business hours, on workday, thermostat_settings is 15 degrees Celsius in office. |
| - | * It is necessary, that in spring, all weekend, thermostat keep temperature 15 degrees Celsius in office. | + | * It is necessary, that in spring, all weekend, thermostat_settings is 15 degrees Celsius in office. |
| - | * It is necessary, that in summer, on business hours thermostat keep temperature 24 degrees Celsius in office. | + | * It is necessary, that in summer, on business hours thermostat_settings is 24 degrees Celsius in office. |
| - | * It is necessary, that in summer, beside business hours thermostat keep temperature 27 degrees Celsius in office. | + | * It is necessary, that in summer, beside business hours thermostat_settings is 27 degrees Celsius in office. |
| - | * It is necessary, that in summer, all weekend, thermostat keep temperature 27 degrees Celsius in office. | + | * It is necessary, that in summer, all weekend, thermostat_settings is 27 degrees Celsius in office. |
| - | * It is necessary, that in fall, on business hours thermostat keep temperature 20 degrees Celsius in office. | + | * It is necessary, that in fall, on business hours thermostat_settings is 20 degrees Celsius in office. |
| - | * It is necessary, that in fall, beside business hours thermostat keep temperature 16 degrees Celsius in office. | + | * It is necessary, that in fall, beside business hours thermostat_settings is 16 degrees Celsius in office. |
| - | * It is necessary, that in fall, all weekend, thermostat keep temperature 16 degrees Celsius in office. | + | * It is necessary, that in fall, all weekend, thermostat_settings is 16 degrees Celsius in office. |
| ===== 3. Transformation of SBVR Business Design to UML Models ===== | ===== 3. Transformation of SBVR Business Design to UML Models ===== | ||
| + | |||
| Linia 407: | Linia 362: | ||
| - | === 3.2. SBVR toUMLActivity Diagram Mapping Rules=== | + | ==== 3.2. SBVR toUMLActivity Diagram Mapping Rules ==== |
| This section mainly deals with the mapping of SBVR components | This section mainly deals with the mapping of SBVR components | ||
| to UML Activity diagram components. | to UML Activity diagram components. | ||
| - | == 3.2.1. Initial Node == | + | === 3.2.1. Initial Node === |
| This is the start state of the activity diagram. It doesn’t | This is the start state of the activity diagram. It doesn’t | ||
| Linia 419: | Linia 374: | ||
| ”start”. | ”start”. | ||
| - | == 3.2.2. Activity Node == | + | === 3.2.2. Activity Node === |
| As we have already discussed in section 3.3, the fact types | As we have already discussed in section 3.3, the fact types | ||
| having transitive verbs will be assumed as the activity node. | having transitive verbs will be assumed as the activity node. | ||
| - | == 3.2.3. Activity Edge == | + | === 3.2.3. Activity Edge === |
| An activity edge is a set of event, guard conditions and | An activity edge is a set of event, guard conditions and | ||
| Linia 475: | Linia 430: | ||
| - | == 3.2.4. ForkNode/JoinNode == | + | === 3.2.4. ForkNode/JoinNode === |
| * ForkNode: This is a pseudo-state where one transition | * ForkNode: This is a pseudo-state where one transition | ||
| Linia 498: | Linia 453: | ||
| conditions and only one outgoing transition. | conditions and only one outgoing transition. | ||
| - | == 3.4.5. ActivityGroup == | + | === 3.2.5. ActivityGroup === |
| The ActivityGroup in UML activity diagrams are generally | The ActivityGroup in UML activity diagrams are generally | ||
| Linia 515: | Linia 470: | ||
| these forms would be logically equivalent. | these forms would be logically equivalent. | ||
| - | == 3.4.6. Activity Final Node == | + | === 3.2.6. Activity Final Node === |
| This is the point in an activity diagram where all the | This is the point in an activity diagram where all the | ||
| activities get end up. We are creating a default end state | activities get end up. We are creating a default end state | ||
| with the default name ”End”. | with the default name ”End”. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ====3.3. Mappin ARD 'thermostat' to Activity Diagram ==== | ||
| + | |||
| + | There is attempt to map, moddeled in ARD, 'thermostat' to Activity Diagram | ||
| + | |||
| + | {{:pl:miw:miw08_bizrulesvocabularies:ad_themrostat.gif|ad_themrostat}} | ||
| + | |||
| + | More about mapping SBVR model to UML diagrams, You can find in {{:pl:miw:miw08_bizrulesvocabularies:sbvr2umlp29-raj.pdf|"Transformation of SBVR Business Design to UML Models"}} | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | =====4. Proposition of transformation ARD model to SBVR ===== | ||
| + | |||
| + | |||
| + | |||
| + | ==== 4.1. Approach 1# ==== | ||
| + | |||
| + | Creating diagram which shows all dependencies between SBVR vocabulary elements is often practice. | ||
| + | The example of this diagram is below. | ||
| + | |||
| + | {{:pl:miw:miw08_bizrulesvocabularies:example_vocabulary.png|example_vocabulary}} | ||
| + | |||
| + | The way of building this diagram is like building class diagram in UML. | ||
| + | |||
| + | The 'thermostat' vocabulary diagram is presented below. | ||
| + | |||
| + | {{:pl:miw:miw08_bizrulesvocabularies:diagram1.png|diagram1}} | ||
| + | |||
| + | When we try use, the same general rules, which were used to create ARD diagram to build class diagram the result of this operation is very similar to SBVR vocabulary diagram. It could be used to create way of mapping between ARD and SBVR vocabulary. | ||
| + | |||
| + | Thanks this approach we can try to build SBVR vocabulary. The Rules can be created also using 'general rules'. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ==== 4.2. Approach 2# ==== | ||
| + | |||
| + | Looking at ARD diagram we try compose mapping rules to SBVR, but the result will be a bit different then original SBVR model presented in 3.2. | ||
| + | |||
| + | {{:pl:miw:miw08_bizrulesvocabularies:thermostatard.png|thermostatard}} | ||
| + | |||
| + | The operation block value is 'during business hours' or 'not during business hours'. | ||
| + | The season value is 'summer' or 'autumn' or 'winter' or 'spring'. | ||
| + | |||
| + | So the first rules can be created are: | ||
| + | |||
| + | * It is necessary, that in winter, on business hours thermostat_settings is 25 degrees Celsius in office. | ||
| + | | ||
| + | * It is necessary, that in winter, beside business hours thermostat_settings is 18 degrees Celsius in office. | ||
| + | | ||
| + | * It is necessary, that in spring, on business hours thermostat_settings is 20 degrees Celsius in office. | ||
| + | | ||
| + | * It is necessary, that in spring, beside business hours thermostat_settings is 15 degrees Celsius in office. | ||
| + | |||
| + | * It is necessary, that in summer, on business hours thermostat_settings is 24 degrees Celsius in office. | ||
| + | | ||
| + | * It is necessary, that in summer, beside business hours thermostat_settings is 27 degrees Celsius in office. | ||
| + | |||
| + | * It is necessary, that in fall, on business hours thermostat_settings is 20 degrees Celsius in office. | ||
| + | |||
| + | * It is necessary, that in fall, beside business hours thermostat_settings is 16 degrees Celsius in office. | ||
| + | | ||
| + | We can use the the last block and blocks level lower to create SBVR model. | ||
| + | |||
| + | It's hard to build mapping algorithm using only one ARD diagram, but this, I think, it's good point to create universal way of mapping from ARD to SBVR. | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ===== 5. Literature ===== | ||
| + | |||
| + | * {{:pl:miw:miw08_bizrulesvocabularies:sbvr.pdf|Semantics of Business Vocabulary and Business Rules (SBVR)}} | ||
| + | * {{:pl:miw:miw08_bizrulesvocabularies:sbvr2umlp29-raj.pdf|Transformation of SBVR Business Design to UML Models}} | ||
| + | * [[http://qrdn.brmsblog.com/2007/04/12/the-business-rules-development-cycle-an-introduction/|The Business Rule Development Lifecycle | ||
| + | ]] | ||
| + | * [[http://sbeaver.sourceforge.net/support/|SBeaver]] | ||
| + | * {{:pl:miw:miw08_bizrulesvocabularies:04-ws1-2_hall.pdf|Semantics of Business Vocabulary and | ||
| + | Business Rules (SBVR) - presentation}} | ||
| + | * {{:pl:miw:miw08_bizrulesvocabularies:architecture_of_business_modeling_2003-11-01.pdf|Architecture of Business Modeling}} | ||
| + | * http://bizrules.info/page/methodologies.htm | ||
| + | * http://qrdn.brmsblog.com/2007/05/01/what-is-sbvr-a-preliminary-faq/ | ||
| + | * http://www.kdmanalytics.com/sbvr/ | ||
| + | * {{:pl:miw:miw08_bizrulesvocabularies:04-ws1-2_hall.pdf|Revised Submission to BEI RFP br/2003-06-03 | ||
| + | Semantics of Business Vocabulary and Business Rules (SBVR)}} | ||
