【24h】

SBVR vs OCL: A comparative analysis of standards

机译:SBVR与OCL:标准比较分析

获取原文
获取原文并翻译 | 示例

摘要

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.
机译:在软件建模中,设计人员必须生成具有软件约束的UML可视模型。同样,在业务建模中,设计人员必须使用业务约束(业务规则)对业务流程进行建模。约束是业务或软件模型框架中的关键组件。设计人员必须编写约束条件以在语义上补充业务模型或UML模型,最后将约束条件实现到业务流程或源代码中。可以使用SBVR(业务词汇和规则语义)来编写业务约束/规则,而OCL(对象约束语言)是用于编写软件约束的众所周知的介质。 SBVR和OCL是OMG的两个重要标准。两种标准在本质上是不同的,因为SBVR通常用于业务领域,而OCL用于补充软件模型。但是,我们已经确定了两个标准中有一些相似之处值得研究。在本文中,我们正在对两种标准进行比较分析,因为我们正在寻找将SBVR自动转换为OCL的机制。这项研究的主要重点是强调SBVR和OCL的主要特征,例如两者可以共同工作的相似性,差异和关键参数。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号