Appendix E. References

It is amazing what can be accomplished when nobody cares about who gets the credit.

Robert Yates

Abowd, G., Bass, L., Clements, P., Kazman, R., Northrop, L., & Zamerski, A. (1996). Recommended Best Industrial Practices for Software Architecture Evaluation. (CMU/ SEI-96-TR-025). Pittsburgh: Software Engineering Institute, Carnegie Mellon University.

Abrams, M., & Helms, J. (2002, February). User Interface Markup Language (UIML) Specification, Version: 3.0.

Agile Alliance (2001a). Manifesto for Agile Software Development. www.agilealliance.org.

Agile Alliance (2001b). Principles: The Agile Alliance. www.agilealliance.org/principles.html.

Agile Databases. Groups.yahoo.com/group/agiledatabases.

Ambler, S. W. (2001a). The Object Primer 2nd Edition: The Application Developer's Guide to Object Orientation. New York: Cambridge University Press. www.ambysoft.com/theObjectPrimer.html.

Ambler, S. W. (2001b). Enterprise Unified Process Home Page. www.enterpriseunifiedprocess.info.

Ambler, S. W. (2001c). Agile Modeling Home Page. www.agilemodeling.com.

Ambler, S. W. (2002a). The Agile Data Home Page. www.agiledata.org.

Ambler, S. W. (2002b). Agile Modeling: Best Practices for the Unified Process and Extreme Programming. New York: John Wiley & Sons. www.ambysoft.com/agileModeling.html.

Ambler, S. W. (2002c). Different Projects Require Different Strategies. http://www.agiledata.org/essays/differentStrategies.html.

Ambler, S. W. (2002d). Refactoring for Fitness. Software Development. www.sdmagazine.com.

Ambler, S. W. (2003a). The Elements of UML Style. New York: Cambridge University Press. www.ambysoft.com/elementsUMLStyle.html.

Ambler, S. W. (2003b). Agile Database Techniques: Handbook for Agile DBAs. New York: John Wiley & Sons. www.ambysoft.com/agileDatabaseTechniques.html.

ANSI INCITS 345-2001, CIF. http://www.techstreet.com/cgi-bin/joint.cgi/incits/cgi-bin/detail?pro%0D%20duct_id5%0D%0D%20%20%20673198

Architectural reasoning; balancing genericity and specificity (n.d.) www.extra.research.philips.com/natlab/sysarch/ArchitecturalReasoningBook.pdf.

Assessing Web Site Usability from Server Log Files. (1999). White Paper, Microsoft Tec-Ed.

Atkinson, C., Bayer, J., Bunse, C., Kamsties, E., Laitenberger, O., Laqua, R., Muthig, D., Paech, B., Wust, J., & Zettel, J. (2002). Component-Based Product Line Engineering with UML. London: Pearson Education.

Bass, L., Clements, P., & Kazman, R. (1997). Software Architecture in Practice. Reading, MA: Addison-Wesley Publications.

Bass, L., John, B. E., & Kates, J. (2001, March). "Achieving Usability Through Software Architecture.@CQU: Technical Report Carnegie Mellon Software Engineering Institute CMU/SEI-2001-TR-005 ESC-TR-2001-005.

Beck, K. (2000). Extreme Programming Explained: Embrace Change. Reading, MA: Addison-Wesley Longman.

Beck, K., & Fowler, M. (2000). Planning Extreme Programming. Reading, MA: Addison-Wesley Publications.

Beedle, M., & Schwaber, K. (2001). Agile Software Development with SCRUM. Upper Saddle River, NJ: Prentice Hall, Inc.

Bevan, 1995.

Beyen, N. (1997). Quality and Usability: A New Framework.

Bosch, J. (2000). Design and Use of Software Architectures. Reading, MA: Addison-Wesley.

Bredemeyer, D. (2003c). Bredemeyer Web site. www.bredemeyer.com.

Bredemeyer, D. (n.d.) Architecture Definition. Bredmeyer Consulting. www.bredemeyer.com/pdf_files/ArchitectureDefinition.pdf.

Bredemeyer, D. (n.d.) Role of the Architect. Bredmeyer Consulting. www.bredemeyer.com/pdf_files/role.pdf.

Bredemeyer, D. (n.d.) Role of the Architect. Bredmeyer Consulting. www.bredemeyer.com/pdf_files/ArchitectRole.pdf.

Brooks, F. P. (1975). Mythical Man Month. Reading, MA: Addison-Wesley.

Brooks, F. P. (1995). The Mythical Man Month: Essays on Software Engineering, Anniversary Edition. Reading, MA: Addison-Wesley.

Burrows, P. (2001). Field and Data Validation with N-Tier Architecture.

Buschmann, F., et al. (1996). Pattern-Oriented Software Architecture. New York: John Wiley & Sons.

Carnegie Mellon Software Engineering Institute. (2003). Capability Maturity Models. www.sei.cmu.edu/managing/managing.html.

Clements, P., Kazman, R., & Klein, M. (2002). Evaluating Software Architectures. Reading, MA: Addison-Wesley.

Clements, P., & Northrop, L. (2001). Software Product Lines: Practices and Patterns. Reading, MA: Addison-Wesley.

Cockburn, A. (1997, December). Surviving Object-Oriented Projects (The Agile Series for Software Developers). Reading, MA: Addison-Wesley.

Cockburn, A. (2001, December). Agile Software Development. Reading, MA: Addison-Wesley.

Cockburn, A. (2002). Agile Software Development. Reading, MA: Addison-Wesley Longman.

Connecticut Object Oriented Users Group. (n.d.) Presentation by Pramod Sadalage, Thoughtworks, Chief Data Architect. www.cooug.org.

Constantine, L. Can UML and Unified Process Meet?

Constantine, L. (2001). Process Agility and Software Usability: Toward Lightweight Usage-Centered Design.

Constantine, L. L., & Lockwood, L. A. D. (1999). Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design. New York: ACM Press.

Fowler, M. (2001a). Is Design Dead? www.martinfowler.com/articles/designDead.html.

Gamma, E., Helm, R., Johnson, R., & Vlissides, J. (1995, January) Design Patterns: Elements of Reusable Object-Oriented Software. Reading, MA: Addison-Wesley.

Gane, C., & Sarson, T. (1979). Structured Systems Analysis: Tools and Techniques. Englewood Cliffs, NJ: Prentice Hall, Inc.

Garlan & Perry. (1992, April). Guest editorial to the IEEE Transactions on Software Engineering.

Hay, D. C. (2003). Requirements Analysis: From Business Views to Architecture. Upper Saddle River, NJ: Prentice Hall, Inc.

Herzum, P., & Sims, O. (2000). Business Component Factory: A Comprehensive Overview of Component-Based Development for the Enterprise. New York: John Wiley & Sons.

Hofmeister, C., Nord, R., & Soni, D. (1999). Applied Software Architecture. Reading, MA: Addison-Wesley.

IBM Ease of Use: Out-of-box experience section. http://www-3.ibm.com/ibm/easy/eou_ext.nsf/Publish/1534

IESE PuLSE (Product Line Software Engineering Method.) (n.d.) www.iese.fhg.de/PuLSE.

ISO/DIS 9241 11 Ergonomic requirements for office work with visual display terminals (VDTs) Part 11: Guidance on usability.

Jacobson, I., Griss, M., & Jonsson, P. (1997). Software Reuse: Architecture, Process, and Organization for Business Success. New York: ACM Press.

Jacobssen, I, Booch, G., & Rumbaugh, J. (1998). The Unified Software Development Process. Reading, MA: Addison-Wesley.

Jeffries, R., Anderson, A., & Hendrickson, C. (2001). Extreme Programming Installed. Reading, MA: Addison-Wesley.

Jones, O. D., Beyen, N., & Thomas, C. (n.d.) Handbook of User-Centered Design, Telematics. Applications Project IE 2016 INUSE European Usability Support Centers.

Kerievsky, J. (2001). Patterns and XP: Extreme Programming Examined. Succi, G., & Marchesi, M., eds. Reading, MA: Addison-Wesley, pp. 207 220.

Kruchten, P. (1999, February). The Archictects: The Software Architecture Team. Proceedings of the First Working IFIP Conference on Software Architecture.

Kruchten, P. (2000). The Rational Unified Process: An Introduction, 2nd Edition. Reading, MA: Addison-Wesley Longman.

Krutchen, P. (1995, November). The 4 + 1 View Model of Architecture. IEEE Software, pp. 42 50.

Krutchen P., Thompson C., Bell D., Devlin J., Booch G., Royce W., Marasco, Reitman M., Ohniec W., & Schonberg A. (n.d.) 4+1 View Model: Rational, Hughes Aircraft, and Alcatel.

Lozoic, N. v. (2003). Newsletter.

Mackinnon, T., Freeman, S., & Craig, P. (n.d.) Endo-Testing: Unit Testing with Mock Objects. www.connextra.com/about/xp_approach.htm.

Macleod, M., Bowden, R., Beyan, N., & Curson, I. (1997). The MUSiC Performance Measurement Method. Behaviour and Information Technology, 16, pp. 279 293.

Malveau, R., & Mowbray, T. J. (2001). Software Architect Bootcamp. Upper Saddle River, NJ: Prentice Hall, Inc.

Marco, D. (2000). Meta Data Repository: A Full Lifecycle Guide. New York: John Wiley & Sons.

McBreen, P. (2001, August). Software Craftmanship: The New Imperative. Reading, MA: Addison-Wesley.

McGovern, J., Kagle, C., Bothner, P., Linn, J., & Nagarajan, V. (2003, September). XQuery: Kick Start. Indianapolis: Sam's Publishing.

McGovern, J., Tyagi, S., Stevens, M., & Mathew, S. (2003). Java Web Services Architecture. San Francisco: Morgan-Kaufmann.

Merriam-Webster's 10th Collegiate Dictionary. New York: Merriam-Webster.

Microsoft Windows 2000 Server. Redmond, WA: Microsoft Press.

Microsoft.NET Architecture.

Moriarty, T. (2001, April). To Unify Architecture with Methodology: The Rational Unified Process Meets the Zachman Information Systems Architecture. Intelligent Enterprise. www.intelligententerprise.com/010416/metaprise1_2.html.

Morris, C., & Ferguson, C. (1993, March). How Architecture Wins Technology Wars, Harvard Business Review.

Object Management Group. (2001a). The Unified Modeling Language (UML) Specification. www.omg.org/technology/documents/formal/uml.htm.

Object Management Group (2001b). Model Driven Architecture (MDA). ftp.omg.org/pub/docs/ormsc/01-07-01.pdf.

Orr, K. (2001, July). One Minute Methodology. New York: Dorset House.

Ozsu, M. T., & Valduriez, C. (1999, January). Principles of Distributed Database Systems. Upper Saddle River, NJ: Prentice Hall, Inc.

Palmer, S. R., & Felsing, J. M. (2002). A Practical Guide to Feature-Driven Development. Upper Saddle River, NJ: Prentice Hall PTR.

Pérez-Quiñones, M. A. (2002). A Software Architecture Approach to a User Interface Software Course, Manuel A., D Sc.

Rational Corporation. (2003). Rational Unified Process Home Page. www.rational.com/products/rup/index.jsp.

Schwaber, K., Beedle, M., & Martin, R. (2001). Agile Software Development with SCRUM. Upper Saddle River, NJ: Prentice Hall, Inc.

The SEI Product Line Practice Initiative. (n.d.) www.sei.cmu.edu/plp.

Service Oriented Architecture Concepts. (2001). Talking Blocks. www.talkingblocks.com/resources.htm.

Stapleton, J. (2003). DSDM: Business Focused Development. Harlow, England: Addison-Wesley.

Stevens, M. (2002). Multi-Grained Services. www.developer.com/article.php/114661.

System Architecting. (n.d.) www.extra.research.philips.com/natlab/sysarch/SystemArchitectureBook.pdf.

Weiss, D., & Lai, C. (1999). Software Product-Line Engineering: A Family-Based Software Development Process. Reading, MA: Addison Wesley.

Wells, D. (n.d.) XP and Databases. www.extremeprogramming.org/stories/testdb.html.

Yourdon, E. (1989). Modern Structured Analysis. Upper Saddle River, NJ: Prentice-Hall, Inc.

ZIFA. (2003). The Zachman Institute for Framework Advancement. www.zifa.com.