The Agile Modeling (AM) Method

Menu

Agile Modeling References

  • Agile Alliance (2001a). Manifesto for Agile Software Development. agilemanifesto.org
  • Agile Alliance (2001b). Principles: The Agile Alliance. agilemanifesto.org/principles.html
  • Ambler, S.W. (1995). The Object Primer: Application Developer’s Guide to Object Orientation. New York: Cambridge University Press.
  • Ambler, S.W. (1997). Building Object Applications That Work: Your Step-By-Step Handbook for Developing Robust Systems with Object Technology. New York: Cambridge University Press.
  • Ambler, S. W. (1998). Process Patterns – Building Large-Scale Systems Using Object Technology. New York: Cambridge University Press.
  • Ambler, S. W. (1999). More Process Patterns – Delivering Large-Scale Systems Using Object Technology. New York: Cambridge University Press.
  • Ambler, S.W. (2001a). The Object Primer 2nd Edition: The Application Developer’s Guide to Object Orientation. New York: Cambridge University Press.
  • Ambler, S.W. (2001b). Enterprise Unified Process White Paper.
  • Ambler, S.W. (2001c). Agile Modeling Home Page. AgileModeling.com
  • Ambler, S.W. (2001d). The Design of a Robust Persistence Layer.
  • Ambler, S.W. (2001e). Mapping Objects to a Relational Database.
  • Ambler, S.W. (2001f). Agile Modeling Mailing List Instructions.
  • Ambler, S.W. (2002). Agile Modeling: Effective Practices for XP and RUP. New York: John Wiley & Sons.
  • Ambler, S.W. (2004). The Object Primer 3rd Edition: Agile Model Driven Development with UML 2. New York: Cambridge University Press. Ambysoft.com/books/theObjectPrimer.html
  • Ambler, S.W. & Constantine, L.L. (2000a). The Unified Process Inception Phase. Gilroy, CA: CMP Books.
  • Ambler, S.W. & Constantine, L.L. (2000b). The Unified Process Elaboration Phase. Gilroy, CA: CMP Books.
  • Ambler, S.W. & Constantine, L.L. (2000c).The Unified Process Construction Phase. Gilroy, CA: CMP Books.
  • Ambler, S.W. & Constantine, L.L. (2002).The Unified Process Transition and Production Phases. Gilroy, CA: CMP Books.
  • Bass, L., Clements, P., & Kazman, R. (1998). Software Architecture in Practice. Reading, MA: Addison Wesley Longman, Inc.
  • Beck, K. (2000). Extreme Programming Explained – Embrace Change. Reading, MA: Addison Wesley Longman, Inc.
  • Beck, K. and Cunningham, W. (1989). A Laboratory for Teaching Object-Oriented Thinking. Proceedings of OOPSLA’89, pp. 1-6.
  • Beck, K. & Fowler, M. (2001). Planning Extreme Programming. Boston, MA: Addison Wesley.
  • Beedle, M. & Schwaber, K. (2001). Agile Software Development With SCRUM. Upper Saddle River, New Jersey: Prentice Hall, Inc.
  • Bennett, D. (1997). Designing Hard Software: The Essential Tasks. Greenwich, CT: Manning Publications Co.
  • Boehm, B.W. (1988). A Spiral Model Of Software Development And Enhancement. IEEE Computer, pp. 61-72, 21(5).
  • Bremer, M. (1999). UnTechnical Writing: How to Write About Technical Subjects and Products So Anyone Can Understand. Concord, CA: UnTechnical Press.
  • Brooks, F.P. (1995). The Mythical Man Month: Essays on Software Engineering Anniversary Edition. Reading, MA: Addison Wesley Publishing Company.
  • Brown, W.J., McCormick, H.W. III, & Thomas, S.W. (2000). AntiPatterns in Project Management. New York: John Wiley & Sons Ltd.
  • Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., & Stal, M. (1996). A Systems of Patterns: Pattern-Oriented Software Architecture. New York: John Wiley & Sons Ltd.
  • Christel, M.G. & Kang, K.C. (1992). Issues in Requirements Elicitation. Software Engineering Institute (SEI) Technical Report CMU/SEI-92-TR-12. www.sei.cmu.edu
  • Coad, P., Lefebvre, E., & DeLuca, J. (1999). Java Modeling in Color with UML: Enterprise Components and Process. Upper Saddle River, New Jersey: Prentice Hall, Inc.
  • Cockburn, A. (1998). Surviving Object-Oriented Projects: A Manager’s Guide. Reading, MA: Addison Wesley Longman, Inc.
  • Cockburn, A. (2001a). Writing Effective Use Cases. Boston: Addison Wesley.
  • Cockburn, A. (2001b). Crystal Clear: A Human-Powered Software Development Methodology for Small Teams. http://members.aol.com/humansandt/crystal/clear/
  • Cockburn, A. (2001c). Characterizing People as Non-Linear, First-Order Components in Software Development. members.aol.com/humansandt/papers/nonlinear/nonlinear.htm
  • Cockburn, A. (2002). Agile Software Development. Reading, MA: Addison Wesley Longman, Inc.
  • Constantine, L.L., and Lockwood, L. A. D. (1999). Software For Use: A Practical Guide to the Models and Methods of Usage-Centered Design. New York: ACM Press.
  • Coplien, J. and Harrison, N. (2001). Organizational Patterns Site. www.bell-labs.com/cgi-user/OrgPatterns/OrgPatterns
  • Davis, A.M. (1995). 201 Principles of Software Development. New York: McGraw Hill Inc.
  • Douglass, B.P. (1999). Doing Hard Time: Developing Real-Time Systems With UML, Objects, Frameworks, and Patterns. Reading, MA: Addison Wesley Longman, Inc.
  • D’Souza, D. F., Wills, A.C. (1999). Objects, Components, and Frameworks with UML: The Catalysis Approach. Reading, MA: Addison Wesley Longman, Inc.
  • Evans, G. (2001). Palm Sized Process: Point of Sale Gets Agile. Software Development, September 2001.
  • Fowler, M. (1997). Analysis Patterns: Reusable Object Models. Menlo Park, California: Addison Wesley Longman, Inc
  • Fowler, M. (1999). Refactoring: Improving the Design of Existing Code. Menlo Park, California: Addison Wesley Longman, Inc.
  • Fowler, M. (2001a). The New Methodology. www.martinfowler.com/articles/newMethodology.html
  • Fowler, M. (2001b). Is Design Dead? www.martinfowler.com/articles/designDead.html
  • Fowler, M. & Scott, K. (1999). UML Distilled Second Edition: Applying the Standard Object Modeling Language. Reading, MA: Addison Wesley Longman, Inc.
  • Gane, C., Sarson, T. (1979). Structured Systems Analysis: Tools and Techniques. Englewood Cliffs, New Jersey: Prentice Hall, Inc.
  • Gamma, E.; Helm, R.; Johnson, R.; and Vlissides, J. (1995). Design Patterns: Elements of Reusable Object-Oriented Software. Reading, Massachusetts: Addison-Wesley Publishing Company.
  • Gilb, T. & Graham, D. (1993). Software Inspection. Harrow, England: Addison Wesley Longman Limited.
  • Graham, I.; Henderson-Sellers, B.; and Younessi, H. (1997). The OPEN Process Specification. New York: ACM Press Books.
  • Greenbaum, J. & Kyng, M. editors (1991). Design At Work: Cooperative Design of Computer Systems. Hillsdale, New Jersey: Lawrence Erlbaum Associates, Publishers.
  • Halpin, T.A. (2001). Information Modeling and Relational Databases: From Conceptual Analysis to Logical Design. San Francisco: Morgan Kaufmann Publishers
  • Highsmith, J.A. III (2000). Adaptive Software Development: A Collaborative Approach to Managing Complex Systems. New York: Dorset House Publishing.
  • Hohmann, L. (1996). Journey of the Software Professional: The Sociology of Computer Programming. Upper Saddle River, NJ: Prentice Hall PTR.
  • Hunt, A. & Thomas, D. (2000). The Pragmatic Programmer: From Journeyman to Master. Reading, MA: Addison Wesley Longman, Inc.
  • Jacobson, I., Booch, G., & Rumbaugh, J., (1999). The Unified Software Development Process. Reading, MA: Addison Wesley Longman, Inc.
  • Jeffries, R., Anderson, A., and Hendrickson, C. (2001). Extreme Programming Installed. Boston: Addison-Wesley.
  • Jeffries, R. (2000a). Business Analysis in Extreme Programming. www.xprogramming.com/xpmag/BizAnalysis.htm
  • Jeffries, R. (2001a). Essential XP: Card, Conversation, Confirmation. www.xprogramming.com/xpmag/expCardConversationConfirmation.htm
  • Jeffries, R. (2001b). Essential XP: Documentation. www.xprogramming.com/xpmag/expDocumentationInXp.htm
  • Jeffries, R. (2001c). Natural XP: Documentation. www.xprogramming.com/xpmag/natural.htm
  • Jeffries, R. (2001d). Essential XP: Emergent Design. www.xprogramming.com/xpmag/expEmergentDesign.htm
  • Jeffries, R. (2001e). Much Ado About Nothing: Documentation. www.xprogramming.com/xpmag/FussAboutDocumentation.htm
  • Kerievsky, J. (2001). Patterns and XP. Extreme Programming Examined. pp. 207-220, Eds. Succi, G. & Marchesi, M., Boston, MA: Addison Wesley
  • Kerth, N. (2001). Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing.
  • Kruchten, P. (2000). The Rational Unified Process 2nd Edition: An Introduction. Reading, MA: Addison Wesley Longman, Inc.
  • Larman, C. (2002). Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and the Unified Process . Upper Saddle River, NJ: Prentice Hall PTR.
  • Linthicum, D.S. (2000). Enterprise Application Integration. Reading, MA: Addison Wesley Longman, Inc.
  • Martin, R.C. (2001). The Process.
  • Martin, R.C. (2002). On Analysis. www.agilealliance.com/articles/martinrobertconanalys
  • Mayhew, D.J. (1992). Principles and Guidelines in Software User Interface Design. Englewood Cliffs NJ: Prentice Hall.
  • McConnell, S. (1993). Code Complete: A Practical Handbook of Software Construction. Redmond, WA: Microsoft Press.
  • Microsoft Corporation (1995). The Windows Interface Guidelines for Software Design: An Application Design Guide. Redmond, WA: Microsoft Press.
  • Microsoft Corporation (2001). The Microsoft Solutions Framework (MSF). www.microsoft.com/business/services/mcsmsf.asp
  • Naiburg, E.J.& Maksimchuk, R.A. (2001). UML for Database Design. Boston: Addison Wesley.
  • Newkirk J. & Martin, R.C. (2001). Extreme Programming in Practice. Boston: Addison Wesley.
  • Object Management Group (2001a). The Unified Modeling Language (UML) Specification. www.omg.org/technology/documents/formal/uml.htm
  • Object Management Group (2001b). Model Drive Architecture (MDA). ftp.omg.org/pub/docs/ormsc/01-07-01.pdf.
  • Page-Jones, M. (1988). Practical Guide to Structured Systems Design 2/e. Upper Saddle River, NJ: Prentice-Hall , Inc.
  • Page-Jones, M. (2000). Fundamentals of Object-Oriented Design in UML. New York: Dorset-House Publishing.
  • Raskin, J. (2000). The Humane Interface: New Directions for Designing Interactive Systems. Reading, MA: Addison Wesley.
  • Rational Corporation (2001). Rational Unified Process Home Page. http://www.rational.com/products/rup/index.jsp
  • Reingruber, M.C. & Gregory, W.W. (1994). The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models. New York: John Wiley & Sons, Inc
  • Roman, E., Ambler, S.W., Jewell, T., & Marinescu, F. (2002). Mastering Enterprise Java Beans, 2/e . New York: John Wiley & Sons.
  • Rosenberg, D and Scott, K. (1999). Use Case Driven Object Modeling With UML: A Practical Approach. Reading, MA: Addison Wesley Longman, Inc.
  • Ross, R.G. (1997). The Business Rule Book, 2nd Ed. Houston, Texas: Business Rules Solutions, Inc.
  • Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., Lorensen, W. (1991). Object-Oriented Modeling and Design. Englewood Cliffs, New Jersey: Prentice Hall, Inc.
  • Rumbaugh, J., Jacobson, I. & Booch, G., (1999). The Unified Modeling Language Reference Manual. Reading, MA: Addison Wesley Longman, Inc.
  • Software Engineering Institute. (1995). The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, MA: Addison-Wesley Publishing Company, Inc.
  • Stapleton, J. (1997). DSDM: Dynamic Systems Development Method. Harlow, England: Addison Wesley.
  • Vermeulen, A., Ambler, S.W., Bumgardner, G., Metz, E., Misfeldt, T., Shur, J., & Thompson, P. (2000). The Elements of Java Style. New York: Cambridge University Press.
  • Wake, W.C. (2002). Extreme Programming Explored. Boston, MA: Addison Wesley.
  • Warmer, J. & Kleppe, A. (1999). The Object Constraint Language: Precise Modeling With UML. Reading, MA: Addison Wesley Longman, Inc.
  • Weiss, E. H. (1991). How To Write Usable User Documentation. Phoenix, AZ: The Oryx Press.
  • Wells, J.D. (2001). Extreme Programming: A Gentle Introduction. http://www.extremeprogramming.org
  • Wiegers, K. (1999). Software Requirements. Redmond, WA: Microsoft Press.
  • Wilkinson, N.M. (1995). Using CRC Cards: An Informal Approach to Object-Oriented Development. New York: Cambridge University Press.
  • Williams, L., Kessler, R.R., Cunningham, W., & Jeffries, R. (2000). Strengthening the Case for Pair Programming. IEEE Software, July/August 2000, pp19-25
  • Wills, A. (2002). Dispersed Agile Software Development and Dispersed eXtreme Programming. http://www.fastnloose.org/cgi-bin/wiki.pl/dad/
  • Xerox (2001). Aspect-Oriented Programming. http://www.parc.xerox.com/csl/projects/aop/
  • Yourdon, E. (1989). Modern Structured Analysis. Upper Saddle River, NJ: Prentice-Hall , Inc.
  • Yourdon, E. (1997). Death March: The Complete Software Developer’s Guide to Surviving “Mission Impossible” Projects. Upper Saddle River, NJ: Prentice-Hall , Inc.