Separating Application Logic from Architectural Concerns - Beyond Object Services and Frameworks</HEAD> <BODY> <h2>Separating Application Logic from Architectural Concerns - Beyond Object Services and Frameworks</h2> <h3> <B>Author: </B> Z. Wang<br> </h3> <P> Proceedings of the Workshop on Compositional Software Architectures, January, 1998. <p> Download the <a href="/afs/cs.cmu.edu/project/compose/ftp/monterey.ps">Postscript</a> or <a href="/afs/cs.cmu.edu/project/compose/ftp/pdf/monterey.pdf">PDF</a> <H2>Abstract</H2> Application logic refers to the encoding of domain business logic and architectural concerns refer to common non-business requirements on the system, for example, security, transaction, performance, scalability etc. It has been widely recognized that separating application logic from architectural concerns can greatly help reduce the development cost and make the system easier to evolve. Current state of practice relies on object services and frameworks. In this paper we argue why these technologies are not sufficient and propose a new approach based on architecture unification. <hr> <p> <font size="2">Brought to you by <a href="http://www.cs.cmu.edu/~Compose/"><font size="2">Composable Software Systems Research Group</font></a><font size="2"> in the </font><a href="http://www.cs.cmu.edu/SCS-HOME.html"><font size="2">School of Computer Science</font></a><font size="2"> at </font><a href="http://www.cmu.edu"><font size="2">Carnegie Mellon University</font></a><font size="2">. </font></p> <font size="2">[Last modified 18-Feb-1999.<br> Mail suggestions to the </font><a href="mailto:compose@cs.cmu.edu"><font size="2">Maintainer</font></a><font size="2">.] </font> </body> </html>