References

Abelson, H., and G. Sussman. 1996. Structure and Interpretation of Computer Programs. 2nd ed. MIT Press.

Acme 2009. The Acme Project. http://www.cs.cmu.edu/~acme/.

Adventure Builder 2010. Java Adventure Builder Reference Application. https://adventurebuilder.dev.java.net/.

Agile Alliance. 2002a. “Manifesto for Agile Software Development.” http://www.agilemanifesto.org.

Agile Alliance. 2002b. Web site. http://www.agilealliance.org.

Agile Alliance. 2002c. “Principles Behind the Agile Manifesto.” http://www.agilemanifesto.org/principles.html.

Akerman, A., and J. Tyree. 2005. “Position on Ontology-based Architecture.” Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture (WICSA 2005). November 6–10, pp. 289–290.

Alexander, Christopher. 1979. The Timeless Way of Building. Oxford University Press.

Allen, R. J., and D. Garlan. 1997. “A Formal Basis for Architectural Connection.” ACM Transaction on Software Engineering and Methodology 6(3): 213–249.

Ambler, Scott W. 2006. “The Object Relational Impedance Mismatch.” http://www.agiledata.org/essays/impedanceMismatch.html.

Ambysoft. 2008. “Modeling and Documentation Practices on IT Projects Survey Results: July 2008.” http://www.ambysoft.com/surveys/modelingDocumentation2008.html.

Araujo, I., and M. Weiss. 2002. “Linking Patterns and Non-Functional Requirements.” Proceedings of the Pattern Languages of Programs Conference (PLoP 2002). Monticello, Illinois, September 8–12. Available at http://www.hillside.net/plop/plop2002/proceedings.html.

Atlantic. 1956. “Rhythm in My Blood.” The Atlantic Magazine, February 1956.

Avritzer, A., Y. Cai, and D. Paulish. 2008. “Coordination Implications of Software Architecture in a Global Software Development Project.” Proceedings of WICSA 2008, pp. 107–116.

Bach, Maurice. 1986. The Design of the UNIX Operating System. Prentice Hall.

Bachmann, Felix, and Paulo Merson. 2005. Experience Using the Web-Based Tool Wiki for Architecture Documentation. Carnegie Mellon University, Software Engineering Institute Technical Note CMU/SEI-2005-TN-041.

Barker, Richard. 1990. CASE Method: Entity Relationship Modelling. Addison-Wesley.

Bass, L., P. Clements, and R. Kazman. 2003. Software Architecture in Practice. 2nd ed. Addison-Wesley.

Beck, Kent. 2000. Extreme Programming Explained: Embrace Change. Addison-Wesley.

Beck, Kent, and Cynthia Andres. 2004. Extreme Programming Explained: Embrace Change. 2nd ed. Addison-Wesley.

Bianco, Phil, Rick Kotermanski, and Paulo Merson. 2007. Evaluating a Service-Oriented Architecture. Carnegie Mellon University, Software Engineering Institute Technical Report CMU/SEI-2007-TR-015.

Bianco, Phil, Grace Lewis, and Paulo Merson. 2008. Service Level Agreements in Service-Oriented Architecture Environment. Carnegie Mellon University, Software Engineering Institute Technical Note CMU/SEI-2008-TN-021.

Bloch, Joshua. 2006. “How to Design a Good API and Why It Matters.” http://www.infoq.com/presentations/effective-api-design.

Boehm, B., D. Port, A. Egyed, and M. Abi-Antoun. 1999. “The MBASE Life Cycle Architecture Milestone Package: No Architecture Is An Island.” 1st Working International Conference on Software Architecture.

Booch, Grady, James Rumbaugh, and Ivar Jacobson. 2005. The Unified Modeling Language User Guide. 2nd ed. Addison-Wesley.

Bosch, J. 2000. Design and Use of Software Architecture: Adopting and Evolving a Product Line Approach. Addison-Wesley.

Brooks, Jr., Frederick P. 1995. The Mythical Man-Month: Essays on Software Engineering. Anniv. ed. Addison-Wesley.

Buschmann, Frank, Regine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stal. 1996. Pattern-Oriented Software Architecture Volume 1: A System of Patterns. Wiley.

Buschmann, Frank, Kevlin Henney, and Douglas C. Schmidt. 2007a. Pattern-Oriented Software Architecture Volume 4: A Pattern Language for Distributed Computing. Wiley.

Buschmann, Frank, Kevlin Henney, and Douglas C. Schmidt. 2007b. Pattern-Oriented Software Architecture Volume 5: On Patterns and Pattern Languages. Wiley.

Cataldo, M., P. Wagstrom, J. D. Herbsleb, and K. Carley. Forthcoming. “Identification of Coordination Requirements: Implications for the Design of Collaboration and Awareness Tools.” In Proceedings, Computer-Supported Cooperative Work.

Chen, Peter. 1976. “The Entity-Relationship Model: Toward a Unified View of Data.” ACM Transactions on Database Systems 1(1): 9–36.

Clements, Paul, and Linda Northrop. 2001. Software Product Lines: Practices and Patterns. Addison-Wesley.

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

Clements P., F. Bachmann, L. Bass, D. Garlan, J. Ivers, R. Little, R. Nord, and J. Stafford. 2003. Documenting Software Architectures: Views and Beyond. 1st ed. Addison-Wesley.

Cockburn, Alistair. 2000. Writing Effective Use Cases. Addison-Wesley.

Cockburn, Alistair. 2001. Crystal methodologies Web page. http://alistair.cockburn.us/crystal.

Cockburn, Alistair. 2002. Agile Software Development. Addison-Wesley.

Cockburn, Alistair. 2004. Crystal Clear: A Human-Powered Methodology for Small Teams. Addison-Wesley.

Conway, M. E. 1968. “How Do Committees Invent?” Datamation 14(4): 28–31.

Date, C. J. 1999. An Introduction to Database Systems. 7th ed. Addison-Wesley.

Date, C. J. 2003. An Introduction to Database Systems. 8th ed. Addison-Wesley.

de Boer, R. C., and R. Farenhorst. 2008. “In Search Of ‘Architectural Knowledge.’” 3rd Workshop on SHAring and Reusing architectural Knowledge (SHARK). Leipzig, Germany. May 13, pp. 71–78.

DeRemer, F., and H. J. Kron. 1976. “Programming-in-the-Large versus Programming-in-the-Small.” IEEE Transactions on Software Engineering, SAE 2(2): 80–86.

Dijkstra, E. W. 1968. “The Structure of the ‘T.H.E.’ Multiprogramming System.” Communications of the ACM 18(8): 453–457.

Dijkstra, E. W. 1972. “Notes on Structured Programming: On Program Families.” In Ole-Johan Dahl, ed., Structured Programming, pp. 39–41. Academic Press.

Dobrica, L., and E. Niemela. 2002. “A Survey on Software Architecture Analysis Methods,” IEEE Transactions on Software Engineering 28(7): 638–653.

DoDAF. 2007. U.S. Department of Defense Architecture Framework, version 1.5. http://www.defenselink.mil/cio-nii/docs/DoDAF_Volume_I.pdf.

Eeles, P., and P. Cripps. 2009. The Process of Software Architecting. Addison-Wesley.

Feiler, Peter H. 2007. Modeling of System Families. Carnegie Mellon University, Software Engineering Institute Technical Note CMU/SEI-2007-TN-047.

Feiler, Peter H., David Gluch, John Hudak, and Bruce Lewis. 2004. Embedded Systems Architecture Analysis Using SAE AADL. Carnegie Mellon University, Software Engineering Institute Technical Note CMU/SEI-2004-TN-005.

Feiler, Peter H., David P. Gluch, and John J. Hudak. 2006. The Architecture Analysis & Design Language (AADL): An Introduction. Carnegie Mellon University, Software Engineering Institute Technical Note CMU/SEI-2006-TN-011.

Feiler P., D. Gluch, K. Weiss, and K. Woodham. 2009. “Model-Based Software Quality Assurance with the Architecture Analysis and Design Language.” Proceedings of AIAA Infotech @Aerospace 2009, Seattle, Washington, April 6–9.

Flurry, G., and W. Vicknair. 2001. “The IBM Application Framework for e-business.” IBM Systems Journal 40(1): 8–24.

Fowler, Martin. 2002. Patterns of Enterprise Application Architecture. Addison-Wesley.

Fowler, Martin. 2003. UML Distilled: A Brief Guide to the Standard Object Modeling Language. Addison-Wesley.

Freeman, Eric, Susanne Hupfer, and Ken Arnold. 1999. JavaSpaces Principles, Patterns, and Practice. Prentice Hall.

Gamma, E., R. Helm, R. Johnson, and J. Vlissides. 1995. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley.

Garlan, D., and M. Shaw. 1993. “An Introduction to Software Architecture.” In V. Ambriola and G. Tortora, eds., Advances in Software Engineering and Knowledge Engineering, vol. 2. World Scientific.

Garlan, D., R. Allen, and J. Ockerbloom. 1995. “Architectural Mismatch or Why It’s So Hard to Build Systems out of Existing Parts.” Proceedings of 17th Int. Conf. on Software Engineering, Seattle, Wash., April 24–28.

Garlan, D., and D. Perry. 1995. “Introduction to the Special Issue on Software Architecture.” IEEE Transactions on Software Engineering 21(4): 269–274.

Garlan, David, and Bradley Schmerl. 2006. “Architecture-driven Modeling and Analysis.” Proceedings of the 11th Australian Workshop on Safety Related Programmable Systems (SCS’06), Melbourne, Australia.

Garland, Jeff, and Richard Anthony. 2003. Large-Scale Software Architecture: A Practical Guide Using UML. Wiley.

Gelernter, D. 1985. “Generative Communication in Linda.” ACM Trans. Program. Lang. Syst. 7, 1 (Jan. 1985), pp. 80–112.

Goethert, W., and J. Siviy. 2004. Applications of the Indicator Template for Measurement and Analysis. Carnegie Mellon University, Software Engineering Institute Technical Note CMU/SEI-2004-TN-024.

Gorton, I. 2006. Essential Software Architecture. Springer.

Hämäläinen, N., and J. Markkula. 2007. “Quality Evaluation Question Framework for Assessing the Quality of Architecture Documentation.” In the CD proceedings of E. Berki, J. Nummenmaa, M. Ross, and G. Staples, eds., Software Quality Meets Work-Life Quality. International BCS Conference on Software Quality Management—SQM 2007. Tampere, Finland, August 1–2.

Hansson, Jörgen, and Peter H. Feiler. 2008. “Enforcement of Quality Attributes for Net-centric Systems through Modeling and Validation with Architecture Description Languages.” Proceedings of 4th International Congress on Embedded Real-Time Systems, January.

Harel, David, and Michael Politi. 1998. Modeling Reactive Systems with Statecharts: The Statemate Approach. McGraw-Hill.

Harvey, Miles. 2000. The Island of Lost Maps: A True Story of Cartographic Crime. Random House.

Hoare, C. A. R. 1985. Communicating Sequential Processes. Prentice Hall.

Hoffman, D. M., and D. M. Weiss, eds. 2001. Software Fundamentals: Collected Papers by David L. Parnas. Addison-Wesley.

Hofmeister, C., R. Nord, and D. Soni. 2000. Applied Software Architecture. Addison-Wesley.

Hohpe, Gregor, and Bobby Wolff. 2003. Enterprise Integration Patterns. Addison-Wesley.

Hughart, Barry. 1984. Bridge of Birds: A Novel of an Ancient China That Never Was. Random House.

Humphrey, Watts S. 1989. Managing the Software Process. Addison-Wesley.

IBM. 2004. Rational Unified Process. http://www-306.ibm.com/software/awdtools/rup/.

IEEE 1471. 2000. IEEE Product No.: SH94869-TBR: Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Standard No. 1471-2000. Available at http://shop.ieee.org/store/.

IEEE 1516.1. 2000. IEEE Standard No.: 1516-1-2000: Standard for Modeling and Simulation (M&S)—High Level Architecture (HLA)—Federated Interface Specification. IEEE Product No.: SS94883-TBR. Available at http://shop.ieee.org/store/.

ISO/IEC 10746-2. 1996. Information Technology—Open Distributed Processing—Reference Model: Foundations. Available at http://www.iso.org/iso/catalogue_detail.htm?csnumber=18836.

ISO 15704. 2000. Industrial Automation Systems—Requirements for Enterprise-Reference Architectures and Methodologies. Available at http://www.iso.org/iso/catalogue_detail.htm?csnumber=28777.

ISO/IEC 42010. 2007. Systems and Software Engineering—Recommended Practice for Architectural Description of Software-Intensive Systems. (Identical to ANSI/IEEE Std 1471-2000). http://www.iso-architecture.org/ieee-1471/.

ISO/IEC CD TR 24748. 2007. Systems and Software Engineering—Life Cycle Management—Guide for Life Cycle Management.

ISO/IEC 12207. 2008. Systems and Software Engineering—Software Life Cycle Processes. 2008.

ISO/IEC WD2 42010. 2008. Systems and Software Engineering—Architectural Description. Working draft dated 1 March 2008. http://www.iso-architecture.org/ieee-1471/docs/ISO-IEC-WD2v1-42010.pdf.

ISO/IEC CD1 42010. 2009. Recommended Practice for Architectural Description of Software-Intensive Systems—ANSI/IEEE Std 1471 :: ISO/IEC 42010. http://www.iso-architecture.org/ieee-1471/.

Iverson, K. E. 1987. “A Dictionary of APL.” APL Quote Quad 18(1): 5.

Jackson, Michael. 1995. Software Requirements and Specifications: A Lexicon of Practice Principles and Prejudices. Addison-Wesley.

Jackson, Michael. 2000. Problem Frames: Analysing & Structuring Software Development Problems. Addison-Wesley.

Jacobson, I. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley.

Jazayeri, Mehdi, Alexander Ran, and Frank van der Linden. 2000. Software Architecture for Product Families: Principles and Practice. Addison-Wesley.

Kiczales, G., J. Lamping, A. Mendhekar, C. Maeda, C. Lopes, J. M. Loingtier, and J. Irwin. 1997. “Aspect-Oriented Programming.” Proceedings of the European Conference on Object-Oriented Programming (ECOOP). Published as Lecture Notes in Computer Science, Number 1241. Springer Verlag, pp. 220–242.

Kircher, Michael, and Prashant Jain, 2004. Pattern-Oriented Software Architecture Volume 3: Patterns for Resource Management. Wiley.

Komiya, S. 1994. “A Model for the Recording and Reuse of Software Design Decisions and Decision Rationale.” Third International Conference on Software Reuse: Advances in Software Reusability. Rio de Janeiro, Brazil, November 1–4, pp. 200–201.

Kruchten, Philippe. 1995. “The 4+1 View Model of Architecture.” IEEE Software 12(6): 42–50.

Kruchten, Philippe. 2004. “An Ontology of Architectural Design Decisions in Software Intensive Systems.” Proceedings of the 2nd Groningen Workshop on Software Variability, Groningen, The Netherlands, December 2–3, pp. 54–61.

Kruchten, Philippe. 2009. “Documentation of Software Architecture from a Knowledge Management Perspective—Design Representation.” In Software Architecture Knowledge Management, ed. M. Ali Babar, T. Dingsøyr, P. Lago, and H. van Vliet, pp. 39–57. Springer Verlag.

Kruchten, P., P. Lago, and H. van Vliet. 2006. “Building Up and Reasoning about Architectural Knowledge.” In QoSA: Quality of Software Architecture. Published as Lecture Notes in Computer Science, Number 4214, ed. C. Hofmeister, pp. 43–58. Springer Verlag.

Kylmäkoski, Roope. 2003. “Efficient Authoring of Software Documentation Using RaPiD7.” Proceedings of the 25th International Conference on Software Engineering, Portland, Oregon, May 3–10.

Laddad, Ramnivas. 2008. AspectJ in Action. Manning.

Lewis, Bruce A., and Peter H. Feiler. 2008. “Multi-Dimensional Model Based Development for Performance Critical Computer Systems Using the AADL.” Proceedings of 4th International Congress on Embedded Real-Time Systems, January.

Liskov, B. 1987. “Data Abstraction and Hierarchy.” OOPSLA’87: Conference on Object Oriented Programming Systems, Languages and Applications. Orlando. Also available as SigPlan Notices 23(5): 17–34.

Louridas, P., and P. Loucopoulos. 2000. “A Generic Model for Reflective Design.” TOSEM 9: 199–237.

Martin, James, and Clive Finkelstein. 1981. Information Engineering. Technical Report. Savant Institute.

Medvidovic, N., and R. N. Taylor. 1997. “A Framework for Classifying and Comparing Architecture Description Languages.” Proceedings of the 6th European Software Engineering Conference together with FSE4, pp. 60–76.

Microsoft Developer Network. 2002. Using .NET to Implement Sun Microsystems’ Java Pet Store J2EE BluePrint Application. http://msdn2.microsoft.com/en-us/library/ms954626.aspx.

Moyers, Bill. 1989. A World of Ideas, ed. Betty Sue Flowers. Doubleday.

Nii, H. P. 1986. “Blackboard Systems.” AI Magazine 7(3): 38–53 and 7(4): 82–107.

Nygaard, K., and O.-J. Dahl. 1981. “The Development of the SIMULA Language.” In History of Programming Languages, ed. R. Wexelblat, pp. 439–493. Academic Press.

Object Management Group. 2009. Modeling and Analysis of Real-Time Embedded Systems (MARTE). http://www.omgmarte.org.

Palmer, Stephen, and John Felsing. 2002. A Practical Guide to Feature-Driven Development. Prentice Hall.

Parnas, D. L. 1971. “Information Distribution Aspects of Design Methodology.” Proceedings of the 1971 IFIP Congress. North Holland Publishing.

Parnas, D. L. 1972. “On the Criteria to Be Used in Decomposing Systems into Modules.” Communications of the ACM 15(12): 1053–1058.

Parnas, D. L. 1974. “On a ‘Buzzword’: Hierarchical Structure.” Proceedings of the IFIP Congress ’74, pp. 336–339.

Parnas, D. L. 1996. “Why Software Jewels Are Rare.” Computer 29(2), February, pp. 57–60.

Parnas, D. L., and D. M. Weiss. 1985. “Active Design Reviews: Principles and Practices.” 8th International Conference on Software Engineering, pp. 215–222. Reprinted in Software Fundamentals: Collected Papers by David L. Parnas, ed. D. Hoffman and D. Weiss. Addison-Wesley.

Parnas, D. L., and P. C. Clements. 1986. “A Rational Design Process: How and Why to Fake It.” IEEE Transactions in Software Engineering SE-12(2): 251–257.

Parnas, D., P. Clements, and D. Weiss. 2001. “The Modular Structure of Complex Systems.” Reprinted in Software Fundamentals: Collected Papers by David L. Parnas, ed. D. Hoffman and D. Weiss. Addison-Wesley.

Parnas, David L., and H. Wuerges. 2001. “Response in Undesired Events in Software Systems.” In Software Fundamentals: Collected Papers by David L. Parnas, ed. D. Hoffman and D. Weiss. Addison-Wesley.

Paulish, D. J. 2002. Architecture-Centric Software Project Management: A Practical Guide. Addison-Wesley.

Perry, D. E., and A. L. Wolf. 1992. “Foundations for the Study of Software Architecture.” Software Engineering Notes 17(2): 40–52.

Ponniah, Paulraj. 2007. Data Modeling Fundamentals. Wiley.

Prieto-Diaz, R., and J. M. Neighbors. 1986. “Module Interconnection Languages.” The Journal of Systems and Software 6(4): 307–334.

Rozanski, N., and E. Woods. 2005. Software Systems Architecture. Addison-Wesley.

Rugina, Ana-Elena, Karama Kanoun, Mohamed Kaaniche, and Peter Feiler. 2008. “Software Dependability Modeling using an Industry-Standard Architecture Description Language.” Proceedings of 4th International Congress on Embedded Real-Time Systems, January 2008.

SAE. 2004/2009. SAE International, Avionics Systems Division AS-2C Subcommittee: Standard Document SAE AS-5506A. Nov. 2004, rev. Jan 2009. Avionics Architecture Description Language Standard.

SAE. 2006. SAE International, Avionics Systems Division AS-2C Subcommittee. Annex Document AS-5506/1. June 2006. SAE Architecture Analysis & Design Language (AADL) Annex Volume 1: Graphical AADL Notation, AADL Meta-Model and Interchange Formats, Language Compliance and Application Program Interface.

SAE. 2010. AADL Standard Web site. http://www.aadl.info.

SARA. 2002. Final Report of the Software Architecture Review and Assessment (SARA) Group, version 1.0. http://philippe.kruchten.com/architecture/SARAv1.pdf.

Scaffidi, Christopher, and Mary Shaw. 2007. “Developing Confidence in Software through Credentials and Low-Ceremony Evidence.” International Workshop on Living with Uncertainties at the 23rd IEEE/ACM International Conference on Automated Software Engineering (ASE 2007), Atlanta, Georgia, November 2007.

Schmidt, D., M. Stal, H. Rohnert, and F. Buschmann. 2000. Pattern-Oriented Software Architecture Volume 2: Patterns for Concurrent and Networked Objects. Wiley.

Schwaber, Ken. 2001. Agile Software Development with Scrum. Prentice Hall.

SEI. 2010. “Defining Software Architecture.” http://www.sei.cmu.edu/architecture/start/definitions.cfm.

Shaw, Mary. 1990. “Elements of a Design Language for Software Architecture.” Position Paper for IEEE Design Automation Workshop. January 1990. Unpaginated.

Shaw, Mary. 1991. “Heterogeneous Design Idioms for Software Architecture.” Proceedings of the 6th International Workshop on Software Specification and Design, Como, Italy, October 25–26, 1991, pp. 158–165.

Shaw, Mary. 1995. “Making Choices: A Comparison of Styles for Software Architecture.” IEEE Software, Special Issue on Software Architecture 12(6): 27–41.

Shaw, Mary. 1996a. “Truth vs. Knowledge: The Difference Between What a Component Does and What We Know it Does.” Proceedings of the 8th International Workshop on Software Specification and Design, pp. 181–185.

Shaw, Mary. 1996b. “Procedure Calls Are the Assembly Language of Software Interconnection: Connectors Deserve First Class Status.” In Studies of Software Design, Proceedings of a 1993 Workshop, ed. D. A. Lamb; published as Lecture Notes in Computer Science No. 1978, pp. 17–32. Springer Verlag.

Shaw, M., and D. Garlan. 1996. Software Architecture: Perspectives on an Emerging Discipline. Prentice Hall.

Smith, C., and L. Williams. 2002. Performance Solutions: A Practical Guide for Creating Responsive, Scalable Software. Addison-Wesley.

Smith, John Miles, and Diane C. P. Smith. 1977. “Database Abstractions: Aggregation and Generalization.” ACM Transactions on Database Systems 2 (2).

Snyder, A. 1986. “Encapsulaton and Inheritance in Object-Oriented Programming Languages.” In Proceedings of the Conferences on Object-Oriented Programming Systems, Languages, and Applications (OOPSLA’86), ed. Norman K. Meyerowitz, pp. 38–45. Available as SIGPLAN Notices 21(11), November.

Soni, D., R. L. Nord, and C. Hofmeister. 1995. “Software Architecture in Industrial Applications.” Proceedings of the 17th International Conferences on Software Engineering, pp. 196–207.

Spivey, J. M. 1988. The Z Notation: A Reference Manual. 2nd ed. Available at http://spivey.oriel.ox.ac.uk/mike/zrm/.

Stafford, J. A., and A. L. Wolf. 2001. “Software Architecture.” In Component-Based Software Engineering: Putting the Pieces Together, ed. G. T. Heineman and W. T. Council. Addison-Wesley.

Steward, Donald. 1981. “Design Structure System: A Method for Managing the Design of Complex Systems.” IEEE Transactions on Engineering Management 28(33): 71–74.

Szyperski, C. 1998. Component Software: Beyond Object-Oriented Programming. Addison-Wesley.

Taylor, R. N., N. Medvidovic, and E. M. Dashofy. 2009. Software Architecture: Foundations, Theory, and Practice. Wiley.

TOGAF. 2010. The Open Group Architecture Framework, version 9. http://www.opengroup.org/architecture/togaf9-doc/arch/.

Trachtenberg, Marvin, and Isabelle Hyman. 1986. Architecture: From Prehistory to Post-Modernism/The Western Tradition. Prentice Hall.

Urdangarin, R., P. Fernandes, A. Avritzer, and D. Paulish. 2008. “Experiences with Agile Practices in the Global Studio Project.” IEEE International Conference on Global Software Engineering (ICGSE), Bangalore, India, August 17–20, pp. 77–86.

Weeks, Edward, and Emily Flint, eds. 1957. “Emily Dickinson’s Letters.” In Jubilee: One Hundred Years of the Atlantic. Little, Brown and Company.

Wikipedia. 2010a. “Architectural style.” http://en.wikipedia.org/wiki/Architectural_style.

Wikipedia. 2010b. “Representational State Transfer.” http://en.wikipedia.org/wiki/REST.

Wikipedia. 2010c. “Wiki.” http://en.wikipedia.org/wiki/Wiki.

Wright, Tim. 2003. “Flying Like the Birds.” AOPA Pilot. June 2003: 81–89. Also available at http://roman-hartmann.de/html/flying_like_the_birds.html.

Yahoo!. 2010. Pipes Web site. http://pipes.yahoo.com/pipes/.

Zachman, J. A. 1987. “A Framework for Information Systems Architecture.” IBM Systems Journal 26(3).