Transformation of SBVR business design to UML models

Raj, Amit; Prabhakar, T. V.; Hendryx, Stan

doi:10.1145/1342211.1342221

Cited by 43 publications

(33 citation statements)

References 7 publications

(12 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…[4] Amit Raj, et al presented a approach where they transformed the requirements specified in Object Management Group's standard Semantics of Business Vocabulary and Rules (SBVR) framework into UML models. M.G Illieva et al .…”

Section: Related Workmentioning

confidence: 99%

A Software Requirement Engineering Technique Using OOADA-RE and CSC for IoT Based Healthcare Applications

Srivastava¹,

Patel²,

Sivagami³

2018

IJSEA

View full text Add to dashboard Cite

show abstract

Section: Related Workmentioning

confidence: 99%

A Software Requirement Engineering Technique Using OOADA-RE and CSC for IoT Based Healthcare Applications

Srivastava¹,

Patel²,

Sivagami³

2018

IJSEA

View full text Add to dashboard Cite

show abstract

“…It is worth noting that the relations defined by QVT-R can be sophisticated, rather than simply one-to-one mapping between model elements. Similar to the meta-models, the specification of relations could also benefit from existing research on the transformation between different layers (Raj et al, 2008). Figure 4 illustrates the QVT relations we defined between business layer and service layer.…”

Section: Relationsmentioning

confidence: 99%

Model Driven Engineering of Cross-Layer Monitoring and Adaptation

Song¹,

Raj²,

Hajebi³

et al. 2013

Proceedings of the 1st International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

Abstract:Monitoring and adaptation of multilayer systems are challenging, because the mismatches and adaptations are interrelated across the layers. This interrelation introduces two important but difficult questions. 1) When a system change causes mismatches in one layer, how to identify all the cascaded mismatches on the other layers? 2) When an adaptation is performed at one layer, how to find out all the complementary adaptations required in other layers. This paper presents a model-driven engineering approach towards cross-layer monitoring and adaption of multilayer systems. We provide standard meta-modeling languages for system experts to specify the concepts and constraints separately for each layer, as well as the relations among the concepts from different layers. An automated engine uses these meta-level specifications to 1) represent the system states on each layer as a runtime model, 2) evaluate the constraints to detect mismatches and assist adaptations within a layer, and 3) synchronize the models to identify cascaded mismatches and complementary adaptations across the layers. We illustrate the approach on a simulated crisis management system, and are using it on a number of ongoing projects.

show abstract

“…3. Unified Modeling Language (UML): As, UML [1] is also based on MOF like SBVR as SBVR can be mapped to UML models [14] and back to SBVR [15]. The typical domain of SBVR is business modelling but SBVR based semantically formal representation can be used to capture software requirement specifications and improve automated software modelling process.…”

Section: Model Object Facility (Mof)mentioning

confidence: 99%

“…activity diagram, sequence diagram, class diagram. Linehan's work [14] for the transformation of SBVR rules into formal languages e.g. Java is one of the only case.…”

Section: E Expected Contributionsmentioning

confidence: 99%

SBVR vs OCL: A comparative analysis of standards

Bajwa

Bordbar

Lee

2011

2011 IEEE 14th International Multitopic Conference

View full text Add to dashboard Cite

Abstract-In software modelling, the designers have to produce UML visual models with software constraints. Similarly, in business modelling, designers have to model business processes using business constraints (business rules). Constraints are the key components in the skeleton of business or software models. A designer has to write constraints to semantically compliment business models or UML models and finally implementing the constraints into business processes or source code. Business constraints/rules can be written using SBVR (Semantics of Business Vocabulary and Rules) while OCL (Object Constraint Language) is the well-known medium for writing software constraints. SBVR and OCL are two significant standards from OMG. Both standards are principally different as SBVR is typically used in business domains and OCL is employed to compliment software models. However, we have identified a few similarities in both standards that are interesting to study. In this paper, we have performed a comparative analysis of both standards as we are looking for a mechanism for automatic transformation of SBVR to OCL. The major emphasis of the study is to highlight principal features of SBVR and OCL such as similarities, differences and key parameters on which these both standards can work together.

show abstract

Transformation of SBVR business design to UML models

Cited by 43 publications

References 7 publications

A Software Requirement Engineering Technique Using OOADA-RE and CSC for IoT Based Healthcare Applications

A Software Requirement Engineering Technique Using OOADA-RE and CSC for IoT Based Healthcare Applications

Model Driven Engineering of Cross-Layer Monitoring and Adaptation

SBVR vs OCL: A comparative analysis of standards

Contact Info

Product

Resources

About