The speci?¬?cations don??™t need to be particularly
formal or be based on some known speci?¬?cation language. Actually, models
made without any restrictions lead modelers to capture the domain in a manner
they see as most effective. Inspecting how they want to approach the problem
and using alternative views immediately reveal the approach they see as most
???natural.??? In this sense, you should never underestimate presentation slides,
drawing tools, or whiteboards. They are great for making speci?¬?cations that
map closer to the problem domain??”but often poor for any automation like
reuse, checking, sharing, analysis, generation, and so on.
. Patterns: If a company has an established collection of patterns, they may
describe domain concepts or reveal common structures within the problem
domain. Domain-speci?¬?c patterns may also be available elsewhere that are
representative of the problem domain under examination. Here, pattern
matching can be applied to check the ingredients of a pattern and pattern
recognition to detect underlying patterns.
. Target environment and its interfaces: Existing libraries, component frameworks,
and interfaces were often made to raise the level of abstraction??”but with
limited guidance and automation for their use. Inspecting them shows how the
applications and features are to be built and which services are already available.
Pages:
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419