306:
36:
to find their common and variable parts. It is a model of wider business context for the system. The term was coined in the early 1980s by James
Neighbors. Domain analysis is the first phase of
285:
219:
Neighbors, J.M. "The Draco
Approach to Constructing Software from Reusable Components". IEEE Transactions on Software Engineering, SE-10(5), September 1984.
347:
260:
Frakes, W.B. and Kyo Kang, (2005), "Software Reuse
Research: Status and Future", IEEE Transactions on Software Engineering, 31(7), July, pp. 529-536.
129:
Several domain analysis techniques have been identified, proposed and developed due to the diversity of goals, domains, and involved processes.
150:
371:
248:
141:
340:
33:
282:
91:
232:
333:
176:
137:
83:
52:
210:. Technical Report 160, Department of Information and Computer Sciences, University of California, Irvine, 1980.
366:
186:
181:
107:
79:
99:
313:
103:
17:
114:
166:
155:
95:
37:
118:
244:
269:
B. Hjørland, H. Albrechtsen, "Toward a New
Horizon in Information Science: Domain-Analysis",
134:
289:
236:
205:
317:
41:
360:
171:
48:
305:
87:
145:
75:
in a domain. Several methodologies for domain analysis have been proposed.
229:
29:
72:
78:
The products, or "artifacts", of a domain analysis are sometimes
228:
Dennis de
Champeaux, Douglas Lea, and Penelope Faure (1993).
98:
can use these models as a basis for the implementation of
321:
271:
Journal of the
American Society for Information Science
106:. This approach to domain analysis is sometimes called
117:, the term "domain analysis" was suggested in 1995 by
283:Birger Hjørland's definition of domain analysis
154:Model Oriented Domain Analysis and Engineering
40:. It is a key method for realizing systematic
341:
8:
133:DARE: Domain Analysis and Reuse Environment
348:
334:
197:
207:Software Construction using Components
28:, is the process of analyzing related
7:
302:
300:
273:, No. 6, vol. 46 (1995), pp. 400-425
241:Object-Oriented System Development
14:
304:
142:Feature-Oriented Domain Analysis
1:
320:. You can help Knowledge by
92:entity-relationship diagrams
71:, which describe all of the
51:using methodologies such as
82:(e.g. represented with the
388:
372:Software engineering stubs
299:
177:Product Family Engineering
149:IDEF0 for Domain Analysis
125:Domain analysis techniques
84:Unified Modeling Language
53:domain specific languages
47:Domain analysis produces
187:Model-driven engineering
182:Domain-specific language
108:model-driven engineering
316:-related article is a
100:software architectures
80:object-oriented models
69:generic architectures
26:product line analysis
314:software-engineering
121:and H. Albrechtsen.
18:software engineering
115:information science
96:Software developers
288:2011-11-05 at the
235:2016-03-03 at the
167:Domain engineering
38:domain engineering
329:
328:
90:represented with
379:
350:
343:
336:
308:
301:
292:
280:
274:
267:
261:
258:
252:
226:
220:
217:
211:
204:Neighbors, J.M.
202:
387:
386:
382:
381:
380:
378:
377:
376:
367:Software design
357:
356:
355:
354:
297:
295:
290:Wayback Machine
281:
277:
268:
264:
259:
255:
237:Wayback Machine
230:Domain Analysis
227:
223:
218:
214:
203:
199:
195:
163:
127:
119:Birger Hjørland
65:facet templates
22:domain analysis
12:
11:
5:
385:
383:
375:
374:
369:
359:
358:
353:
352:
345:
338:
330:
327:
326:
309:
294:
293:
275:
262:
253:
239:, chapter 13,
221:
212:
196:
194:
191:
190:
189:
184:
179:
174:
169:
162:
159:
158:
157:
152:
147:
139:
126:
123:
57:feature tables
42:software reuse
13:
10:
9:
6:
4:
3:
2:
384:
373:
370:
368:
365:
364:
362:
351:
346:
344:
339:
337:
332:
331:
325:
323:
319:
315:
310:
307:
303:
298:
291:
287:
284:
279:
276:
272:
266:
263:
257:
254:
250:
249:0-201-56355-X
246:
243:. Rahul Wis.
242:
238:
234:
231:
225:
222:
216:
213:
209:
208:
201:
198:
192:
188:
185:
183:
180:
178:
175:
173:
172:Feature Model
170:
168:
165:
164:
160:
156:
153:
151:
148:
146:
143:
140:
138:
135:
132:
131:
130:
124:
122:
120:
116:
111:
109:
105:
101:
97:
93:
89:
85:
81:
76:
74:
70:
66:
62:
58:
54:
50:
49:domain models
45:
43:
39:
35:
32:systems in a
31:
27:
23:
19:
322:expanding it
311:
296:
278:
270:
265:
256:
240:
224:
215:
206:
200:
128:
112:
104:applications
77:
68:
64:
61:facet tables
60:
56:
46:
25:
21:
15:
88:data models
361:Categories
193:References
86:(UML)) or
286:Archived
233:Archived
161:See also
30:software
94:(ERD).
73:systems
247:
144:(FODA)
67:, and
34:domain
312:This
24:, or
318:stub
245:ISBN
102:and
113:In
16:In
363::
136:,
110:.
63:,
59:,
55:,
44:.
20:,
349:e
342:t
335:v
324:.
251:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.