什么是 JRules？商业管理系统？
什么是“商业规则”？请用一些例子来解释。
业务逻辑是构建的核心逻辑 申请要求。
但什么是业务规则呢？
What is "business rules"? Please explain with some example.
Businees logic is core logic to build
the application for the requirements.
But what is business rules?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
BRMS = 一组编辑和执行业务规则的工具
JRules = BRMS 解决方案，例如 JBoss 规则、Blaze advizor 等等
您希望使用 BRMS 将应用程序中的业务逻辑外部化。
它与数据库相同，用于外部化数据。
业务规则是原子的，代表业务逻辑的一部分。
例如：
“如果申请人年龄小于 18 岁，则拒绝申请”
BRMS 由以下部分组成：
- 规则存储库（文件系统或数据库）
- 开发人员（如 Eclipse）和业务用户（非技术）界面（Web）
- 执行规则的环境
您使用 BRMS 来创建决策服务。
它可以在 J2SE、J2EE、EJB、Web 服务、MDB 等中“可调用”
因此，作为决策服务一部分的业务规则（JRules 中的ruleapp/ruleset）可以由各种应用程序调用。
决策服务的真正优势。
可以将其想象为 BPM 需要做出决定，而不是在应用程序本身中对条件和操作进行编码，然后调用 DS 以获得答案，从而做出决定。
创建虚拟 DS 并从 BPM 应用程序（例如 Tibco Business Works）调用它只需 1 小时。
业务规则的另一个定义是它是业务策略实施的结果。
经营方针：“好客户，年终有奖”
业务分析师的工作是从该语句中提取规则，从而最终得到如下规则：
“如果客户的状态为 GOLD，并且客户购物车的金额大于 5,000 英镑，则将客户的状态设置为 PLATINUM”
创建规则时，您必须问自己很多问题，例如：
银牌和铜牌状态如何？规则是否涵盖了所有门槛？等等...
决策服务可能包含数千条业务规则
例如：有些用于验证，有些用于资格，有些用于报价等等...
希望有帮助
BRMS = a set of tools to edit and execute business rules
JRules = a BRMS solution like JBoss rules, Blaze advizor, and much more
You want to use BRMS to externalize the business logic from the application.
It is the same as a database which is there to externalize data.
A business rule is atomic and represent a part of the business logic.
E.g:
"if the age of the applicant is less than 18 then reject the application"
BRMS is composed of:
- a rule repository (filesystem or DB)
- a developper (like Eclipse) and a business user (non technical) interface (web)
- an environment to execute the rules
You use BRMS in order to create a Decision Service.
It can be "callable" in J2SE, J2EE, EJB, Web Service, MDB, ...
Hence the businees rules which are part of a Decision Service (ruleapp/ruleset in JRules) can be called by various application.
The real advantage of a Decision Service.
Think of it like when a BPM needs to make a decision, rather than code the condition and actions in the application itself then make a call to a DS to have the answer, hence the decision.
It will takes you nothing more than 1 hour to create a dummy DS and call it from a BPM application such as Tibco Business Works.
Another definition of Business rules is that it is the result of a business policy implementation.
Business policy: "A good customer should be reward for the end of the year"
The Business Analyst job is to extract the rule from this statement and hence end up with rules like that:
"if the status of the customer is GOLD and the amount of the shopping cart of the customer is greater than £5,000 then set the status of the client to PLATINUM"
When you create the rule you have to ask yourself a lot of question like:
What about SILVER and BRONZE status? Are all the threshold covered by rules? and so on...
A Decision Service can potentially contain several thousands of business rules
For example: Some for validation, some for eligibility, some for quotation and so on...
Hope it helps
我不明白你关于 TAG 的最后一句话。但简单来说，业务规则是驱动业务逻辑的规则。例如在银行领域 - 如果帐户余额介于此之间，则此帐户状态将是这样的，如果余额低于这样的值，状态将是其他值，并且会触发一些工作流程，例如发送邮件/电子邮件给客户等。这只是一个例子。
出于更好的维护、关注点分离以及允许主题专家等非开发人员编写和维护 BRMS 发展的业务规则等原因，将业务规则与核心应用程序隔离开来。 BRMS 代表业务规则管理系统。包含业务规则的软件。 JRules 就是这样一种 BRMS。您的应用程序与 BRMS 通信以获取业务规则信息。
I don't understand your last sentence regarding TAG. But simply speaking, Business Rules are the rules which drive your business logic. For example in the banking domain - if the account balance is between this and this account status will be such and such, if the balance falls below such and such value, status will be something else and it will trigger some workflow like sending mail/email to the customer etc. This is just an example.
To isolate the business rules from the core application for reasons like better maintenance, separation of concern and allowing non-developers like subject matter experts to author and maintain the business rules the BRMS evolved. BRMS stands for Business Rule Management System. The piece of software which contains business rules. JRules is one such BRMS. Your application talk to BRMS to get the business rule information.
如果您希望看到 JBoss 业务规则管理系统 (BRMS) 的实际效果，那么您可能想尝试这个可重复的演示：
http://www.schabell.org/2012/06/jboss-enterprise-brms-bpm-made-simple.html
它使用简单地浏览业务流程，以直观地演示规则集成（从流程中进行规则调用），以决定业务流程中要采取的路径。
希望你喜欢它。 :)
If you would like to see this in action with JBoss Business Rules Management System (BRMS) then you might like to try this repeatable demo:
http://www.schabell.org/2012/06/jboss-enterprise-brms-bpm-made-simple.html
It uses a simple walk through business process to visually demonstrate Rules integration (a Rules call is made from the process) to decide the path to take in the business process.
Hope you enjoy it. :)