Library

Bibliography

Requirements Engineering

A bibliography of requirements engineering sources covering elicitation, specification, analysis, validation, and model-based practice.

Requirements Engineering Bibliography cover

No bibliography citations match that search.

A

  1. Adzic, G., Specification by Example, Shelter Island NY: Manning Publications Co., 2011.

  2. Alexander I.F., and L. Beus-Dukic, Discovering Requirements: How to Specify Products and Services, Chichester, England: John Wiley & Sons, 2007.

  3. Alexander I.F., and R. Stevens, Writing Better Requirements, London: Addison Wesley, 2002.

  4. Andriole, S., Managing Systems Requirements: Methods, Tools and Cases, New York: McGraw-Hill, 1996.

  5. Aurum, A. and C. Wohlin, (eds), Engineering and Managing Software Requirements, Springer, 2005.

B

  1. Berenbach, B., D.J. Paulish, J. Kazmeier, A. Rudolf, Software and Systems Requirements Engineering in Practice, New York: McGraw-Hill, 2009.

  2. Bittner, K., and I. Spence, Use Case Modelling, Boston, MA: Addison-Wesley, 2003.

  3. Bray I.K., An Introduction to Requirements Engineering, Boston, MA: Addison Wesley, 2002.

  4. Bron, J-Y., System Requirements Engineering: A SysML Supported Requirements Engineering Method, Wiley-ISTE, 2020.

  5. Buede, D.M. and W.D. Miller, The Engineering Design of Systems: Models and Methods, Wiley, 2006.

C

  1. Callahan, S., Putting Stories to Work, Melbourne, Australia: Pepperberg Press, 2016.

  2. Cockburn, A., Writing Effective Use Cases, Boston, MA: Addison-Wesley, 2002.

D

  1. Davis, A.M., Software Requirements: Analysis and Specification, Engelwood Cliffs, NJ: Prentice Hall International, 1990.

  2. Davis, A.M., Software Requirements: Objects, Functions and States, Engelwood Cliffs, N.J.: Prentice Hall International, 1993.

  3. Davis, A.M., Just Enough Requirements Management: Where Software Development Meets Marketing, New York, NY: Dorset House Publishing, 2005.

  4. Defense Systems Management College (DSMC), Systems Engineering Management Guide, Washington, D.C.: U.S. Government Printing Office, 1990.

  5. Dorfman, M. and R.H. Thayer, System and Software Requirements Engineering, IEEE Computer Society Press, 1990.

  6. Delligatti, L., SysML Distilled: A Brief Guide to the Systems Modeling Language, Pearson Education, 2010.

  7. Dori, D., Model-Based Systems Engineering with OPM and SysML, Springer, 2016.

E

  1. Eisner, H., Essentials of Project and Systems Engineering Management, New York: John Wiley & Sons, 2008.

F

  1. Ferdinandi, P.L., A Requirements Pattern: Succeeding in the Internet Economy, Boston, MA: Addison-Wesley, 2001.

  2. Fernandes, J. and R. Machado, Requirements in Engineering Projects, Switzerland, Springer, 2016.

  3. Fitchett, P. and J. Haslam, Writing Engineering Specifications, London, UK: Spon Press, 1988.

  4. Friedenhal, S., A. Moore, and P. Stein, A Practical Guide to SysML: The Systems Modelling Language, The MK/OMG Press, 2015.Hetherington, D. Simple SySML for Beginners: Using Sparx Enterprise Architect, Asatte Press, 2019.

G

  1. Gause, D. and G. Weinberg, Exploring Requirements: Quality Before Design, New York: Dorset House Publishing Company Incorporated, 1989.

  2. Gilb, T., Competitive Engineering: A Handbook For Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage, Butterworth-Heinemann, 2005.

  3. Goldsmith, R.F., Discovering Real Business Requirements for Software Project Success, Norwood, M.A: Artech House, 2004.

  4. Gottesdiener, E., Requirements by Collaboration: Workshops for Defining Needs, Reading, MA: Addison Wesley, 2002.

  5. Grady, J., Systems Requirements Analysis, New York: McGraw-Hill, 2006.

H

  1. Hass, K.B., D.J. Wessels, and K. Brennan, Getting it Right: Business Requirement Analysis Tools and Techniques, Vienna, VA: Management Concepts, 2008.

  2. Hatley, D.J., P. Hruschka, and I.A. Pirbhai, Process for System Architecture and Requirements Engineering, New York: Dorset House Publishing Company, 2000.

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

  4. Heap, G., J. Stanway and A. Windsor, A Structured Approach to Systems Development, London: McGraw-Hill Book Company, 1992.

  5. Hitchins, D., Putting Systems to Work, Chichester, England: John Wiley & Sons, 1992.

  6. Hood, C., S. Wiedemann, S. Fichtinger, and U. Pautz, Requirements Management: The Interface Between Requirements Development and All other Systems Engineering Processes, Oberhaching: Springer, 2008.

  7. Hooks, I.F. and K.A. Farry, Customer-centred Products: Creating Successful Products Through Smart Requirements Management, New York: AMACOM, 2001.

  8. Hossenlopp, R. and K.B. Hass, Unearthing Business Requirements: Elicitation Tools and Techniques, Vienna, VA: Management Concepts, 2008.

  9. Hull, E., K. Jackson, and J. Dick, Requirements Engineering, London: Springer, 2011.

  10. Holt, J., Systems Engineering Demystified: A Practitioner’s Handbook for Developing Complex Systems Using a Model-based Approach, Packt, 2021.

  11. Holt, J. and S. Perry, SysML for Systems Engineering: A Model-Based Approach, Institution of Engineering and Technology, 2013.

I

  1. International Council on Systems Engineering (INCOSE), INCOSE-TP-2010-004-04, Guide to Writing Requirements, 2024.

  2. International Institute for Business Analysis, A Guide to the Business Analysis Body of Knowledge® (BABOK® Guide), Version 3, 2015.

  3. ISO/IEC/IEEE 29148 Systems and Software Engineering—Lifecycle Processes —Requirements Engineering, 2018.

J

  1. Jackson, M., Software Requirements and Specifications: A Lexicon of Software Practice, Principles and Prejudices, Reading, M.A.: Addison Wesley, 1995.

  2. Jonasson, H., Determining Project Requirements, Second Edition: Mastering the BABOK® and the CBAP® Exam, Auerbach Publications, 2012

K

  1. Kossmann, M., Requirements Management: How to Ensure You Achieve What You Need From Your Projects, Gower, 2013.

  2. Kotonya, G. and I. Sommerville, Requirements Engineering: Processes and Techniques, West Sussex, England: John Wiley & Sons, 2000.

  3. Kulak, D. and E. Guiney, Use Cases: Requirements in Context, Boston, MA: Addison-Wesley, 2004.

L

  1. Laplante, P.A., Requirements Engineering for Software and Systems, Boca Raton, FL: CRC Press, 2014.

  2. Larson, E. and R. Larson, Practitioner’s Guide to Requirements Engineering—Part 1: Requirements Planning, Minneapolis, MN: Watermark Learning Publications, 2009.

  3. Leffingwell, D., and D. Widrig, Managing Software Requirements: A Unified Approach, Reading, M.A.: Addison-Wesley, 2000.

  4. Leffingwell, D., Agile Software Requirements: Lean requirements Practices for Teams, Programs, and the Enterprise, Reading, MA: Addison-Wesley, 2011.

  5. Loucopoulos, P., and V. Karakostas, New York: McGraw-Hill, 1995.

  6. Lutowski, R., Software Requirements: Encapsulation, Quality, and Reuse, Boca Raton, FL: Taylor and Francis, 2005.

M

  1. Macaulay, L., Requirements Engineering, London, England: Springer, 1996.

  2. Maier, M. and E. Rechtin, The Art of Systems Architecting, Boca Raton, F.L.: CRC Press, 2009.

  3. Martin, J., Systems Engineering Guidebook: A Process for Developing Systems and Products, Boca Raton, F.L.: CRC Press, 1997.

  4. Mate J.L., and A. Silva (editors), Requirements Engineering for Sociotechnical Systems, Hershey, PA: Information Science Publishing, 2005.

  5. Micouin, P., Modell-based Systems Engineering: Fundamentals and Methods, Wiley, 2014.

P

  1. Pohl, K., Requirements Engineering: Fundamentals, Principles, and Techniques, Heidelberg: Springer-Verlag, 2010.

  2. Pohl, K., Requirements Engineering Fundamentals, Santa Barbara CA: Rocky Nook, 2011.

  3. Pohl, K., and C. Rupp, Requirements Engineering: Fundamentals, Principles, and Techniques, Heidelberg: Springer-Verlag, 2011.

  4. Purdy, D., A Guide to Writing Successful Engineering Specifications, New York: McGraw-Hill, 1991.

R

  1. Rinzler, B., Telling Stories: A Short Path to Writing Better Software Requirements, Wiley, 2009.

  2. Robertson S., and J. Robertson, Requirements-led Project Management, Boston: Addison-Wesley, 2005.

  3. Robertson S., and J. Robertson, Mastering the Requirements Process, Harlow, England: Addison-Wesley, 2013.

  4. Ryan, M.J., “An Improved Taxonomy for Major Needs and Requirements Artefacts”, INCOSE International Symposium IS2013, June 2013.

  5. Ryan, M.J. and L.S. Wheatcraft, “On a Cohesive Set of Requirements Engineering Terms”, Systems Engineering, 2017.

  6. Ryan, M.J., Requirements Practice in Conceptual Design, Artech House, 2026.

S

  1. Sommerville, I., and P. Sawyer, Requirements Engineering, Chichester: England, John Wiley & Sons, 1997.

  2. Sage, A. and J. Armstrong, Introduction to Systems Engineering, New York: John Wiley & Sons, 2000.

T

  1. Thayer, R.H. and M. Dorfman (editors), Software Requirements Engineering, Los Alamitos, CA: IEEE Computer Society Press, 1997.

V

  1. van Lamsweerde, A., Requirements Engineering: From System Goals to UML Models to Software Specifications, Chichester, England: John Wiley & Sons, 2009.

  2. Vitech Corporation, A Primer for Model-based Systems Engineering, Second Edition, 2011.

W

  1. Wheatcraft, L.S., M.J. Ryan and Katz, T.E., INCOSE Needs and Requirements Manual: Needs, Requirements, Verification, Validation Across the Lifecycle, Wiley, 2024.

  2. Wheatcraft L.S., M.J. Ryan and J. Dick, “On the Use of Attributes to Manage Requirements”, Volume 19, Issue 5, September 2016, pp. 448–458.

  3. Wiegers, K.E. and J. Beatty, Software Requirements, Redmond, WA: Microsoft Press, 2013.

  4. Wieringa, R., Requirements Engineering: Frameworks for Understanding, Wiley, 1996.

  5. Withall, S., Software Requirements Patterns (Best Practices), Redmond, MA: Microsoft Press, 2007.

Y

  1. Young, R., Effective Requirements Practices, Boston, M.A.: Addison-Wesley, 2001.

  2. Young, R., The Requirements Engineering Handbook, Norwood, M.A, Artech House, 2004.

  3. Young, R., Project Requirements: A Guide to Best Practices, Vienna VA: Management Concepts, 2006.