95:
is a common cross-cutting concern, being used in many other parts of the program other than the particular module(s) that actually log the data. Since changes to the logging code can affect other sections, it could introduce
58:
Usually the code can be separated into logical sections, each addressing separate concerns, and so it hides the need for a given section to know particular information addressed by a different section. This leads to a
42:
interaction or as specific as performing a primitive calculation, depending on the level of conversation between developers and the program being discussed.
239:
254:
220:
119:
164:
202:
71:" to describe the mentality behind this modularization, which allows the programmer to reduce the complexity of the system being
79:". Sometimes the chosen module divisions do not allow for one concern to be completely separated from another, resulting in
107:
76:
60:
20:
137:
113:
68:
217:
184:
132:
88:
80:
84:
180:
92:
64:
194:
188:
198:
142:
35:
27:
161:
224:
168:
248:
97:
75:. Two different concerns that intermingle in the same section of code are called "
122:, treating concerns and their interaction as constructs of their own standing
72:
39:
34:
is a particular set of information that has an effect on the code of a
103:
Paradigms that specifically address the issue of concern separation:
16:
Information that has an effect on the code of a computer program
193:, New York, NY, USA: Springer-Verlag New York, Inc., pp.
145:, a unit of work to accomplish an improvement in a data system
43:
216:
Mendhekar, Anurag, Gregor
Kiczales, and John Lamping.
190:
Selected writings on
Computing: A Personal Perspective
50:
to describe the sectioning of conceptual information.
218:"RG: A Case-Study For Aspect-Oriented Programming"
38:. A concern can be as general as the details of
8:
240:Concerns in Rails, by DHH, the Rails creator
227:Xerox Palo Alto Research Center. Feb 1997.
154:
7:
120:Aspect-oriented software development
185:"On the role of scientific thought"
116:, describing concerns as functions
14:
100:in the operation of the program.
255:Software engineering terminology
187:, in Dijkstra, Edsger W. (ed.),
110:, describing concerns as objects
1:
108:Object-oriented programming
271:
18:
21:Concern (disambiguation)
138:Separation of concerns
114:Functional programming
91:to different degrees.
89:cross-cutting concerns
81:cross-cutting concerns
69:separation of concerns
162:Concern Spaces at IBM
133:Cross-cutting concern
87:address the issue of
85:programming paradigms
19:For other uses, see
181:Dijkstra, Edsger W.
223:2007-09-08 at the
167:2008-01-22 at the
65:Edsger W. Dijkstra
143:Issue (computers)
67:coined the term "
262:
228:
214:
208:
207:
177:
171:
159:
36:computer program
28:computer science
270:
269:
265:
264:
263:
261:
260:
259:
245:
244:
236:
231:
225:Wayback Machine
215:
211:
205:
179:
178:
174:
169:Wayback Machine
160:
156:
152:
129:
56:
24:
17:
12:
11:
5:
268:
266:
258:
257:
247:
246:
243:
242:
235:
234:External links
232:
230:
229:
209:
203:
172:
153:
151:
148:
147:
146:
140:
135:
128:
125:
124:
123:
117:
111:
83:. The various
77:highly coupled
55:
52:
46:uses the term
15:
13:
10:
9:
6:
4:
3:
2:
267:
256:
253:
252:
250:
241:
238:
237:
233:
226:
222:
219:
213:
210:
206:
204:0-387-90652-5
200:
196:
192:
191:
186:
182:
176:
173:
170:
166:
163:
158:
155:
149:
144:
141:
139:
136:
134:
131:
130:
126:
121:
118:
115:
112:
109:
106:
105:
104:
101:
99:
94:
90:
86:
82:
78:
74:
70:
66:
62:
53:
51:
49:
48:concern space
45:
41:
37:
33:
29:
22:
212:
189:
175:
157:
102:
93:Data logging
57:
47:
31:
25:
150:References
63:program.
249:Category
221:Archived
183:(1982),
165:Archived
127:See also
73:designed
54:Overview
40:database
61:modular
32:concern
201:
195:60–66
199:ISBN
98:bugs
30:, a
44:IBM
26:In
251::
197:,
23:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.