<?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="Software architecture description - Page 10 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=software_architecture_description&amp;p=9">1.Previous</a><br />
<a accesskey="3" href="page.php?w=software_architecture_description&amp;p=11">3.Next</a>
</p>
<p>of elements (and therefore three kinds of views):<br/>
*processing: how the data is transformed;<br/>
*data: information that is used and transformed;<br/>
*connecting: glue holding the other elements together;</p>

<p>Perry and Wolf identified four objectives or uses for architecture descriptions (called "architecture specifications" in their paper):<br/>
*prescribe architectural constraints without overspecifying solutions<br/>
*separate aesthetics from engineering<br/>
*express different aspects of the architecture each in an appropriate manner<br/></p><p>
<a accesskey="1" href="page.php?w=software_architecture_description&amp;p=9">1.Previous</a><br />
<a accesskey="3" href="page.php?w=software_architecture_description&amp;p=11">3.Next</a>
</p>

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

</card>
</wml>
