217:
114:
Another example would be a concept like "Process" having "Identifier", "Name", "Start date", "End date" and "Kind" attributes and holding an association with the "Employee" (the responsible) that started it.
139:, design pattern that provides an interface to a type of database or other persistent mechanism, and offers data operations to application calls without exposing database details
60:
because they are communicated across the tiers in a multi-tiered system, while the real work of the application is done in the business tier and does not move across the tiers.
85:
107:
For example, a "Manager" would be a business object where its attributes can be "Name", "Second name", "Age", "Area", "Country" and it could hold a
254:
196:
180:
170:
160:
72:, which typically end in objects managing or executing behaviours, a business object usually does nothing itself but holds a set of
127:, design pattern that stores object data in memory in relational databases, with functions to insert, update, and delete records
273:
133:, a field within information technology that provides decision support and business-critical information based on data
278:
247:
108:
69:
53:
77:
35:
145:, design pattern where an object carries aggregated data between processes to reduce the number of calls
130:
124:
81:
142:
240:
96:
136:
57:
88:
with other business objects, weaving a map of objects representing the business relationships.
176:
166:
156:
73:
42:
224:
192:
20:
201:
46:
267:
92:
24:
216:
38:
175:
Rockford Lhotka, Expert One-on-One Visual Basic .NET Business
Objects,
19:"Business objects" redirects here. For the software company, see
111:
with its employees (a collection of "Employee" instances).
95:
where business objects do not have behaviour is called an
228:
155:
Rockford Lhotka, Visual Basic 6.0 Business
Objects,
16:Entity within a multi-tiered software application
41:application that works in conjunction with the
248:
165:Rockford Lhotka, Expert C# Business Objects,
8:
255:
241:
7:
213:
211:
227:. You can help Knowledge (XXG) by
14:
215:
68:Whereas a program may implement
23:. For the concept in law, see
1:
223:This computing article is a
193:A definition of domain model
295:
210:
52:Business objects separate
49:layers to transport data.
18:
274:Programming constructs
34:is an entity within a
131:Business intelligence
125:Active record pattern
143:Data transfer object
202:Anemic Domain Model
97:anemic domain model
137:Data access object
74:instance variables
236:
235:
286:
257:
250:
243:
219:
212:
204:by Martin Fowler
80:, also known as
294:
293:
289:
288:
287:
285:
284:
283:
279:Computing stubs
264:
263:
262:
261:
208:
189:
152:
121:
109:1-n association
105:
66:
32:business object
28:
25:Business entity
21:BusinessObjects
17:
12:
11:
5:
292:
290:
282:
281:
276:
266:
265:
260:
259:
252:
245:
237:
234:
233:
220:
206:
205:
199:
188:
187:External links
185:
184:
183:
173:
163:
151:
148:
147:
146:
140:
134:
128:
120:
117:
104:
101:
65:
62:
47:business logic
15:
13:
10:
9:
6:
4:
3:
2:
291:
280:
277:
275:
272:
271:
269:
258:
253:
251:
246:
244:
239:
238:
232:
230:
226:
221:
218:
214:
209:
203:
200:
198:
197:Martin Fowler
194:
191:
190:
186:
182:
181:1-59059-145-3
178:
174:
172:
171:1-59059-344-8
168:
164:
162:
161:1-86100-107-X
158:
154:
153:
149:
144:
141:
138:
135:
132:
129:
126:
123:
122:
118:
116:
112:
110:
102:
100:
98:
94:
89:
87:
83:
79:
75:
71:
63:
61:
59:
55:
50:
48:
44:
40:
37:
33:
26:
22:
229:expanding it
222:
207:
113:
106:
93:domain model
90:
86:associations
67:
51:
36:multi-tiered
31:
29:
43:data access
268:Categories
150:References
82:attributes
78:properties
58:behaviour
119:See also
103:Examples
64:Function
39:software
70:classes
179:
169:
159:
84:, and
56:from
54:state
225:stub
177:ISBN
167:ISBN
157:ISBN
45:and
195:by
76:or
270::
99:.
91:A
30:A
256:e
249:t
242:v
231:.
27:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
