Generating statechart designs from scenarios
Proceedings of the 22nd international conference on Software engineering
Business Modeling With UML: Business Patterns at Work
Business Modeling With UML: Business Patterns at Work
UML Activity Diagrams as a Workflow Specification Language
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Strengthening Method Contracts for Objects
APSEC '06 Proceedings of the XIII Asia Pacific Software Engineering Conference
Enterprise Information Systems - Towards Model-driven Service-oriented Enterprise Computing - 12th International IEEE EDOC Enterprise Computing Conference (EDOC 2008)
From UML/OCL to SBVR specifications: A challenging transformation
Information Systems
Goal and model driven design of an architecture for a care service platform
Proceedings of the 2010 ACM Symposium on Applied Computing
A systematic review of the use of requirements engineering techniques in model-driven development
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
Transformation rules for translating business rules to OCL constraints
ECMFA'11 Proceedings of the 7th European conference on Modelling foundations and applications
A rule based approach for business rule generation from business process models
RuleML'12 Proceedings of the 6th international conference on Rules on the Web: research and applications
| Hi-index | 0.00 |
This paper presents a methodology for transforming business designs written in OMG's standard Semantics of Business Vocabulary and Rules (SBVR) framework, into a set of UML models. It involves the transformation of business vocabulary and rules written in SBVR's "Structured English" into a set of UML diagrams, which includes Activity Diagram(AD), Sequence Diagram(SD), and Class Diagram(CD). This transformation works by detecting the distinction between rules which will participate in the construction of Activity Diagram and rules which do not. These rules are imperative in nature. The work in the paper also includes the detection of activities embedded implicitly in those rules and establishment of sequence between those activities. These activities incur some action. We also detect their owner and refer to them as the doer of the action. This plays a very important role in the development of Class Diagrams