Chapter X: Two-Level Aspect Weaving to Support Evolution in Model-Driven Software

An important step in solving a problem is to choose the nota-tion. It should be done carefully. The time we spend now on choosing the notation may be well repaid by the time we save later avoiding hesitation and confusion. Moreover, choosing the notation carefully, we have to think sharply of the ele-ments of the problem which must be denoted. Thus, choosing a suitable notation may contribute essentially to understand-ing the problem. (Polya, 1957) Since the inception of the software industry, models have been a bene-ficial tool for managing complexity. In fact, the first commercial software package that was sold independent of a hardware manufacturer was an appli-cation for constructing flow chart models, i.e., ADR’s AUTOFLOW (ADR, 2002). In numerous disciplines, models are constructed to assist in the un-derstanding of the essential characteristics of some instance from a particular domain. Mechanical engineers, architects, computer scientists, and many other professionals create models to provide projected views over an entity that has been abstracted from the real-world. As tools for creative explora-tion, even children erect models of real-world structures using Legos, Tinker Toys, and other similar materials