APPENDIX X2
BIBLIOGRAPHY
X2.1 Resource Material
The following literature was used in the development of this practice guide:
Alexander, I. F., and Beus-Dukic, L. 2009. Discovering Requirements: How to Specify Products and Services. New York: Wiley.
Ambler, S. 2005. The Elements of UML (2.0) Style. Cambridge: University Press.
Beatty, J., and Chen, A. 2012. Visual Models for Software Requirements (Developer Best Practices). Redmond, WA: Microsoft Press.
Beatty, J., and Wiegers, K. 2013. Software Requirements, 3rd ed. Redmond, WA: Microsoft Press.
Blais, S. 2011. Business Analysis: Best Practices for Success. New York: ILL.
Cadle, J. Paul, D., and Turner, P. 2010. Business Analysis Technique: 72 Essential Tools. Swindon, UK: British Informatics Society Limited (BISL). Accessed April 8, 2010, http://bcs.org/upload/pdf/business-analysis-techniques_pdf
Carkenord, B. A. 2008. Seven Steps to Mastering Business Analysis. Fort Lauderdale, FL: J. Ross Publishing.
Davis, A. M. 2005. Just Enough Requirements Management: Where Software Development Meets Marketing. New York: Dorset House Publishing.
Frisendal, T. 2012. Design Thinking Business Analysis: Business Concept Mapping Applied. New York: Springer.
Gause, D. C., and Weinberg, G. M. 1990. Are Your Lights On? How to Figure Out What the Problem REALLY Is. New York: Dorset House Publishing.
Gottesdiener, E. 2002. Requirements by Collaboration: Workshops for Defining Needs. Boston: Addison-Wesley Professional.
Gottesdiener, E., and Gorman, M. 2012. Discover to Deliver: Agile Product Planning and Analysis. Sudbury, MA: EBG Consulting, Inc.
Gottesdiener, E. 2005. The Software Requirements Memory Jogger: A Pocket Guide to Help Software and Business Teams Develop and Manage Requirements. Salem, NH: Goal/QPC Inc.
Hass, K. B., Wessels, D., and Brennan, K. 2007. Getting It Right: Business Requirement Analysis Tools and Techniques. Vienna, VA: Management Concepts.
Hohman, L. 1997. Journey of the Software Professional: A Sociology of Software Development. Upper Saddle River, NJ: Prentice Hall Computer.
Jonasson, H. 2012. Determining Project Requirements: Mastering the BABOK® and the CBAP® Exam. 2nd ed. Boca Raton, FL: Auerbach Publications.
Kulak, D., and Guiney, E. 2000. Use Cases: Requirements in Context. New York: ACM Press.
Larson, E., and Larson, R. The Practitioners Guide to Requirements Management. 2nd ed. Minneapolis, MN: Watermark Learning.
Leffingwell, D. and Widrig, D. W. 2003. Managing Software Requirements: A Use Case Approach. 2nd ed. Boston: Addison-Wesley Professional.
Lieberman, B. A. 2006. The Art of Software Modeling. Boca Raton, FL: Auerbach Publications.
McConnell, S. 1996. Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press.
Miller, R. E. 2009. The Quest for Software Requirements. Milwaukee, WI: Maven Mark Books.
Paul, D., Yeates, D., and Cadle, J., Eds. 2010. Business Analysis. 2nd ed. Swindon, UK: British Informatics Society Limited (BISL). Accessed April 8, 2010, http://www.bcs.org/upload/pdf/business-analysis2.pdf
Podeswa, H. 2008. The Business Analyst's Handbook. Boston: Cengage Learning PTR.
Rackham, N. 1988. SPIN Selling. New York: McGraw-Hill.
Robertson, S. and Robertson, J. 2005. Mastering the Requirements Process: Getting Requirements Right. 3rd ed. Boston: Addison-Wesley Professional.
Ross, R. G., and Lam, S. W. 2011. Building Business Solutions: Business Analysis with Business Rules. Houston, TX: Business Rules Solutions, LLC
Schneider, G., and Winters, J. Applying Use Cases, A Practical Guide. Upper Saddle River, NJ: Pearson Education.
Thayer, R. H., and Dorfman, M. 1990. System and Software Requirements Engineering. Washington, DC: IEEE Computer Society Press.
Weinberg, G. B. 1986. Becoming a Technical Leader. New York: Dorset House Publishing.
Weinberg, G. M., and Gauss, D. C. 1989. Exploring Requirements: Quality Before Design. New York: Dorset House.
Wiegers, K. 2005. More About Software Requirements: Thorny Issues and Practical Advice (Developer Best Practices). Redmond, WA: Microsoft Press, 2005.
X2.2 Suggested Additional Reading Materials
The following are suggested additional reading material:
Alexander I. F., and Beus-Dukic L. 2009. Discovering Requirements: How to Specify Products and Services. New York: Wiley.
Bernard M. 2012. Key Performance Indicators (KPI): The 75 Measures Every Manager Needs to Know. New York: FT Publishing/Pearson.
Cadle, J. Turner, P., and Paul, D. 2010. Business Analysis Techniques: 72 Essential Tools For Success Author. Swindon, UK: British Computer Society.
Cohn, M. 2006. Agile Estimating and Planning. Upper Saddle River, NJ: Pearson Education.
Cohn, M. 2009. Succeeding with Agile: Software Development Using Scrum. Essex, UK: Addison-Wesley Professional.
Crispin, L., and Gregory, J. 1009. Agile Testing: A Practical Guide for Testers and Agile Teams. Upper Saddle River, NJ: Pearson Education.
Davis, A. M. 2005. Just Enough Requirements Management: Where Software Development Meets Marketing. New York: Dorset House.
Denne, M., and Cleland-Huang, J. 2004. Software by Numbers: Low-Risk, High-Return Development. Upper Saddle River, NJ: Prentice Hall Professional.
Gilb, T. 2005. Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Oxford: Elsevier Butterworth-Heinemann.
Hubbard, D. 2014. How To Measure Anything. 3rd ed. Hoboken, NJ: Wiley.
Kulak, D. and Guiney, E. 2000. Use Cases: Requirements in Context. New York: ACM Press.
Paul, D., Yeates, D., and Cadle, J. (Eds.). 2006. Business Analysis. Swindon, UK: British Computer Society.
Robertson, S., and Robertson, J. C. 2004. Requirements-Led Project Management: Discovering David's Slingshot. Essex, UK: Addison-Wesley Professional.
Rumbaugh, J., Jacobson, I., and Booch, G. 2004. The Unified Modeling Language Reference Manual. 2nd ed. Essex, UK: Addison-Wesley Professional.
Wake, B. 2003. INVEST in Good Stories, and SMART Tasks. Retrieved from http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/
Young, R, R. 2001. Effective Requirements Practices. Essex, UK: Addison-Wesley Professional.