blocks|key|749699|text|业务对象通常被认为是表示实体的类，例如Book或Store。在Java或.NET中，类由所谓的setter和getter组成，即设置或获取这些属性的方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|749700|另一方面，业务逻辑是与这些属性一起工作的程序的一部分，即这本书是如何销售的。业务逻辑层使用业务对象来访问数据库。|749701|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well, a Business Object is generally considered to be a class that represents an Entity, e.g. a Book or a Store. Such a class has certain properties like price, colour, width, isbn number etc. In Java or .NET, it consists of so-called setters and getters, i.e. methods that set or get those properies.

The Business Logic on the other hand is that part of a program that works with that properties, i.e. how is this book sold. The business logic layer uses the business objects in order to access the database.

blocks|key|3874777|text|这很简单|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3874778|系统中表示系统期望与之交互的人类世界对象的每个实体都是一个业务对象。|3874779|围绕操作业务对象的系统中的人类世界逻辑是业务逻辑。|3874780|这与对象和逻辑是实现细节的一部分相反。|3874781|例如，在多层交易系统中，订单/交易将是业务对象，但心跳将是实现细节。|3874782|对流的订单/交易对象进行编码的逻辑将是实现细节，而在交易到达时将订单状态更改为“已完成”的逻辑是业务逻辑。|3874783|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

This is easy

Every entity in the system, representing the human-world object which the system is expected to interact with is a business object.

The human-world logic in the system around manipulating business objects is a business logic.

This is opposed to the objects and logic being part of the implementation details.

For example in the multi-tier trading system order/trade will be business objects, but heartbeat will be implementation detail.

The logic of encoding order/trade objects for streaming will be implementation detail, while the logic of changing the order state to 'completed' once trade arrives is a business logic.

blocks|key|2466707|text|嘿，吞噬，当我开始开发的时候，我也遇到了这个术语的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2466708|基本上，使用“业务”一词的唯一原因是因为术语是在商业软件的上下文中开发的。因此，从这个意义上说，假设软件是为商业目的而构建的……与艺术、美学或创造性的目的相反。|2466709|因此，业务对象是现实世界中“业务”对象的简单代码表示。因此，您可能有一个Product+Class或Employee+Class。|2466710|业务逻辑是应用程序中特定于软件设计目标的“业务”的逻辑。所以，像税务计算，或产品如何与客户相关的事情...诸如此类的。|2466711|请注意，业务对象或业务逻辑的概念不适用于视频游戏开发或艺术开发。|2466712|它也不适用于一些框架或libraire，例如or或单元测试库，因为它们是可重用的组件，并不特定于任何“业务”。|2466713|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

hey devoured, I had trouble with this terminology when I started developing too.

Basically, the only reason the word "business" is used, is because the terminology developed within the context of commercial software. So in this sense, it is assumed that the software is been built for business purposes... as opposed to say, artistic, aesthetic, or creative purposes.

So, business objects are simple code representation of real world "business" objects. So, you might have a Product Class, or a Employee Class.

Business logic, is logic within the application that is specific to the "business" the software was designed for. So, things like tax calculations, or how products related to customers... that kind of thing.

Note that the idea of Business objects or Business logic would not apply to video game development, or artistic development.

It also wouldn't apply to some frameworks, or libraires, like ORMS or unit testing libraries, as an example, because they are reusable components which are not specific to any "business".

blocks|key|749765|text|在传统的3层编程中，你有三个逻辑层或层。你有一个表示层，它是用户界面，最底层是数据库层。中间层是业务对象层。如上所述，业务对象应该被抽象，因为站点可能根本不是关于业务的。它是一个抽象层，可以更容易地更改表示层或切换到不同的数据源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|749766|如果您的用户界面级别后面没有或只有很少的代码。它使设计人员更容易与程序员合作。设计师可以改变网站的外观和感觉，而程序员不必对使网站工作的代码进行实质性的重写。使用业务对象层，您可以完成站点的繁重列表。在业务对象不知道数据库层是XML还是关系数据库的情况下，调用数据库层。然后，业务对象层将更新对UI层的响应。通常，使用的示例是针对银行交易的。在用户界面中，客户输入他想要从他的储蓄账户转账到他的支票账户的金额。|749767|业务对象层将包含银行的业务规则。这意味着它将检查用户储蓄帐户的余额，并确保要转账的金额不超过帐户的余额。业务层将包含实际计算储蓄帐户和支票帐户的新余额的类，并且它将警告数据库层更新数据库。|749768|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

In traditional 3 tier programming you have three logical layers or tiers. You have a presentation layer which is the User Interface, the bottom layer would be the database layer. The middle layer would be the business objects layer. As pointed out above the business objects should be abstracted in that the site might not be about business at all. It is a layer of abstraction that makes it easier to make changes to the presentation layer or to switch to a different data source.

If your user interface level has no or very little code behind it. It makes it easier for designers to work with programmers. The designers can change the look and feel of the site without the programmers having to do a substantial rewrite of the code that makes that site work. With the business objects layer you do the heavy listing of the site. You make calls into the database layer without the business object knowing whether your database layer is in XML or relational database. And the business object layer then would update a response to the UI layer.
Typically the example used is for a bank transaction. In the user interface a client enters the amount he would like to transfer from his savings account to his checking account.

The business object layer will contain the business rules for the bank . That means it will check the balance of the users savings account and make sure the amount to transfer does not exceed the balance of the account. The business layer will contain the classes that actually calculate the new balances for both the savings account and the checking account and it will alert the database layer to update the database.

blocks|key|749788|text|业务对象的定义很难在搜索引擎上获得，因为它会告诉您business+Objects是一家被SAP收购的公司。但这并不是大多数人想要的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|749789|业务对象是对业务场景进行业务逻辑建模的封装.|749790|例如:在采购领域:有一个完整的需要执行的活动列表。从费用分析到产品信息请求，再到为协商期限生成合同。因此，在这个特定的场景中，可以将像RFI+(请求信息)这样的文档视为RFI业务对象的实例(它将具有与验证等流程相关的所有逻辑)。|749791|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

A definition of a business object is difficult to get on the search engine as it will tell you that Business Objects is a company acquired by SAP. But that is not what most people look for.

A business object is the the encapsulation of business logic model a business scenario.

For eg: In procurement domain : there is a whole list of activities that need to be performed.
From Spend Analysis to Requesting of Information for the products to Generating the contract for the negotiated term. So in this particular scenario , a document like RFI (Request for information ) can be considered to be a instance of a RFI Business Object (It will have all the logic related to process like validation etc).

blocks|key|3874948|text|SAP系列业务对象不同于oracle核心设计模式中与应用服务层交互的业务对象。是的，业务对象确实与复合实体一起工作，但它具有业务逻辑，它可以携带业务状态，一些易于调整的方法，它们是业务信息的载体，具有可交换的动态和跨应用层或域的特性，但在不同的上下文中，它有不同的详细指定名称，例如，我们可以说，...it格式的web服务请求是一个业务对象，它与数据实体不同|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3874949|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

SAP series business object is different with the business object inside the oracle'core design pattern which interact with application service layer ... yes, business object does work with composite entity , but it has business logic , it can carry business state , some easy adjust methods and they are business info carrier with exchangeable the dynamic states and cross among application tiers or domains , but when at different context , it has different detailed specified name , for example, we can say web service request is a business object in xml format ...it is not the same as data entity

blocks|key|3874969|text|业务对象：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3874970|class+User+{
++++long+id;
++++String+fullNames;
++++int+age;
}

class+Book+{
++++long+id;
++++String+bookTitle;
}

class+Sales+{
++++long+id;
++++long+userID;
++++long+bookID;
}|code-block|syntax|javascript|3874971|业务逻辑：|3874972|class+BookSalesController+{
++++private+User+user+=+new+User();
++++private+Book+book+=+new+Book();
++++private+Sales+sale+=+null;

++++public+Sale+sale(long+saleID)+{
++++++++String+query+=+"SELECT+*+FROM+Sales+s+WHERE+s.id+=+:saleID";
++++++++....
++++++++....+execute+the+query

++++++++//+Assuming+we+have+our+Result+Set+here+by+now

++++++++if+(rs.next())+{
++++++++++++sale+=+new+Sales(rs.getString("User+Names"));
++++++++++++sale.setUserID(rs.getLong(userID));
++++++++++++sale.setBookID(rs.getLong(bookID));
++++++++}

++++++++return+sale;
++++}
}|3874973|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Business Object:

<pre><code>class User {
 long id;
 String fullNames;
 int age;
}

class Book {
 long id;
 String bookTitle;
}

class Sales {
 long id;
 long userID;
 long bookID;
}
</code></pre>

Business Logic:

<pre><code>class BookSalesController {
 private User user = new User();
 private Book book = new Book();
 private Sales sale = null;

 public Sale sale(long saleID) {
 String query = "SELECT * FROM Sales s WHERE s.id = :saleID";
 ....
 .... execute the query

 // Assuming we have our Result Set here by now

 if (rs.next()) {
 sale = new Sales(rs.getString("User Names"));
 sale.setUserID(rs.getLong(userID));
 sale.setBookID(rs.getLong(bookID));
 }

 return sale;
 }
}
</code></pre>

When reading, I keep seeing references to what they call <code>Business Objects</code>. I've looked up on Wikipedia and such but I keep not getting what a <code>Business Object</code> is.

Is there any easy explanation of what it is for someone that doesn't know a thing about software architecture and such?

Also, what is <code>Business Logic</code>?

What are Business Objects and what is Business Logic?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在阅读时，我不断地看到他们所谓的Business Objects的引用。我查过维基百科之类的，但我一直不明白什么是Business Object。对于对软件架构之类一无所知的人来说，有什么简单的解释吗？另外，什么是Business Logic

问什么是业务对象，什么是业务逻辑？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问什么是业务对象，什么是业务逻辑？EN