<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Domain-specific multimodeling - Page 8 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Domain-specific_multimodeling&amp;p=7">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Domain-specific_multimodeling&amp;p=9">3.Next</a>
</p>
<p>when the user hits the update button. Finally, the Form DSL is used to describe the visual appearance of the form. Although the three languages are tailored for different things, they can not be separated entirely. The user interface invokes a certain application logic and this application logic manipulates the data of the application. This is an example of non-orthogonal concerns. The languages overlap because the concerns that they represent cannot be separated entirely. Let us examine these three languages in a <a href="page.php?w=Top-down_and_bottom-up_design">bottom-up</a></p><p>
<a accesskey="1" href="page.php?w=Domain-specific_multimodeling&amp;p=7">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Domain-specific_multimodeling&amp;p=9">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
