References

Alcatel-Lucent. 1999. “Lucent’s record-breaking reliability continues to lead the industry according to latest quality report.” Alcatel-Lucent Press Releases. June 2. http://www.alcatel-lucent.com/wps/portal/NewsReleases/DetailLucent?LMSG_CABINET=Docs_and_Resource_Ctr&LMSG_CONTENT_FILE=News_Releases_LU_1999/LU_News_Article_007318.xml (accessed May 15, 2008).

Bass, L., P. Clements, and R. Kazman. 2003. Software Architecture in Practice, Second Edition. Boston, MA: Addison-Wesley.

Blaauw, G., and F. Brooks. 1997. Computer Architecture: Concepts and Evolution. Boston, MA: Addison-Wesley.

Booch, G., J. Rumbaugh, and I. Jacobson. 1999. The UML Modeling Language User Guide. Boston, MA: Addison-Wesley.

Brooks, F. 1995. The Mythical Man-Month. Boston, MA: Addison-Wesley.

Carney, D. L., et al. 1985. “The 5ESS switching system: Architectural overview.” AT&T Technical Journal, vol. 64, no. 6, p. 1339.

Clements, P., et al. 2003. Documenting Software Architectures: Views and Beyond. Boston, MA: Addison-Wesley.

Clements, P., R. Kazman, and M. Klein. 2002. Evaluating Software Architectures. Boston: Addison-Wesley.

Conway, M. 1968. “How do committees invent.” Datamation, vol. 14, no. 4.

Courtois, P. J. 1977. Decomposability: Queuing and Computer Systems. New York, NY: Academic Press.

Dijkstra, E. W. 1968. “Co-operating sequential processes.” Programming Languages. Ed. F. Genuys. New York, NY: Academic Press.

Garlan, D., and D. Perry. 1995. “Introduction to the special issue on software architecture.” IEEE Transactions on Software Engineering, vol. 21, no. 4.

Grinter, R. E. 1999. “Systems architecture: Product designing and social engineering.” Proceedings of ACM Conference on Work Activities Coordination and Collaboration (WACC ’99). 11–18. San Francisco, CA.

Hanmer, R. 2001. “Call processing.” Pattern Languages of Programming (PLoP). Monticello, IL. http://hillside.net/plop/plop2001/accepted_submissions/PLoP2001/rhanmer0/PLoP2001_rhanmer0_1.pdf.

Hoffman, D., and D. Weiss. 2000. Software Fundamentals: Collected Papers by David L. Parnas. Boston, MA: Addison-Wesley.

IEEE. 2000. “Recommended practice for architectural description of software intensive systems.” Std 1471. Los Alamitos, CA: IEEE.

Klein, John. 2005. “How does the architect’s role change as the software ages?” Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA). Washington, DC: IEEE Computer Society.

Maranzano, J., et al. 2005. “Architecture reviews: Practice and experience.” IEEE Software, March/April 2005.

Parnas, David L. 1974. “On a buzzword: Hierarchical structure.” Proceedings of IFIP Congress. Amsterdam, North Holland. [Reprinted as Chapter 9 in Hoffman and Weiss (2000).]

Waldo, J. 2006. “On system design.” OOPLSA ’06. October 22–26. Portland, OR.

Weiss, D., and C. T. R. Lai. 1999. Software Product Line Engineering. Boston, MA: Addison-Wesley.

Get Beautiful Architecture now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.