[ref001] Abran, Alain, James W. Moore, Pierre Bourque, and Robert Dupuis, eds. 2004. Guide to the Software Engineering Body of Knowledge, 2004 Version. Los Alamitos, CA: IEEE Computer Society Press.

[ref002] Akers, Doug. 2008. “Real Reuse for Requirements.” Methods & Tools 16(1):33–40.

[ref003] Alexander, Ian F., and Ljerka Beus-Dukic. 2009. Discovering Requirements: How to Specify Products and Services. Chichester, England: John Wiley & Sons Ltd.

[ref004] Alexander, Ian F., and Neil Maiden. 2004. Scenarios, Stories, Use Cases: Through the Systems Development Life-Cycle. Chichester, England: John Wiley & Sons Ltd.

[ref005] Alexander, Ian F., and Richard Stevens. 2002. Writing Better Requirements. London: Addison-Wesley.

[ref006] Ambler, Scott. 2005. The Elements of UML 2.0 Style. New York: Cambridge University Press.

[ref007] Anderson, Ross J. 2008. Security Engineering: A Guide to Building Dependable Distributed Systems, 2nd ed. Indianapolis, IN: Wiley Publishing, Inc.

[ref008] Arlow, Jim. 1998. “Use Cases, UML Visual Modeling and the Trivialisation of Business Requirements.” Requirements Engineering 3(2):150–152.

[ref009] Armour, Frank, and Granville Miller. 2001. Advanced Use Case Modeling: Software Systems. Boston: Addison-Wesley.

[ref010] Arnold, Robert S., and Shawn A. Bohner. 1996. Software Change Impact Analysis. Los Alamitos, CA: IEEE Computer Society Press.

[ref011] Basili, Victor R., and H. Dieter Rombach. 1988. “The TAME Project: Towards Improvement-Oriented Software Environments.” IEEE Transactions on Software Engineering. 14(6):758–773.

[ref012] Bass, Len, Paul Clements, and Rick Kazman. 1998. Software Architecture in Practice. Reading, MA: Addison-Wesley.

[ref013] Beatty, Joy, and Anthony Chen. 2012. Visual Models for Software Requirements. Redmond, WA: Microsoft Press.

[ref014] Beatty, Joy, and Remo Ferrari. 2011. “How to Evaluate and Select a Requirements Management Tool.” http://www.seilevel.com/wp-content/uploads/RequirementsManagementToolWhitepaper_1.pdf.

[ref015] Beck, Kent, et al. 2001. “Manifesto for Agile Software Development.” http://www.agilemanifesto.org.

[ref016] Beizer, Boris. 1999. “Best and Worst Testing Practices: A Baker’s Dozen.” Cutter IT Journal 12(2):32–38.

[ref017] Beyer, Hugh, and Karen Holtzblatt. 1998. Contextual Design: Defining Customer-Centered Systems. San Francisco, CA: Morgan Kaufmann Publishers, Inc.

[ref018] Blackburn, Joseph D., Gary D. Scudder, and Luk N. Van Wassenhove. 1996. “Improving Speed and Productivity of Software Development: A Global Survey of Software Developers.” IEEE Transactions on Software Engineering 22(12):875–885.

[ref019] Boehm, Barry W. 1981. Software Engineering Economics. Upper Saddle River, NJ: Prentice Hall.

[ref020] Boehm, Barry W. 1988. “A Spiral Model of Software Development and Enhancement.” IEEE Computer 21(5):61–72.

[ref021] Boehm, Barry W. 2000. “Requirements that Handle IKIWISI, COTS, and Rapid Change.” IEEE Computer 33(7):99–102.

[ref022] Boehm, Barry W., Chris Abts, A. Winsor Brown, Sunita Chulani, Bradford K. Clark, Ellis Horowitz, Ray Madachy, Donald J. Reifer, and Bert Steece. 2000. Software Cost Estimation with Cocomo II. Upper Saddle River, NJ: Prentice Hall PTR.

[ref023] Boehm, Barry W., and Philip N. Papaccio. 1988. “Understanding and Controlling Software Costs.” IEEE Transactions on Software Engineering 14(10):1462–1477.

[ref024] Boehm, Barry, and Richard Turner. 2004. Balancing Agility and Discipline: A Guide for the Perplexed. Boston: Addison-Wesley.

[ref025] Booch, Grady, James Rumbaugh, and Ivar Jacobson. 1999. The Unified Modeling Language User Guide. Reading, MA: Addison-Wesley.

[ref026] Box, George E. P., and Norman R. Draper. 1987. Empirical Model-Building and Response Surfaces. New York: John Wiley & Sons, Inc.

[ref027] Boyer, Jérôme, and Hafedh Mili. 2011. Agile Business Rule Development: Process, Architecture, and JRules Examples. Heidelberg, Germany: Springer.

[ref028] Bradshaw, Jeffrey M. 1997. Software Agents. Menlo Park, CA: The AAAI Press.

[ref029] Brijs, Bert. 2013. Business Analysis for Business Intelligence. Boca Raton, FL: CRC Press.

[ref030] Brooks, Frederick P., Jr. 1987. “No Silver Bullet: Essence and Accidents of Software Engineering.” IEEE Computer 20(4):10–19.

[ref031] Brosseau, Jim. 2010. “Software Quality Attributes: Following All the Steps.” http://www.clarrus.com/resources/articles/software-quality-attributes.

[ref032] Brown, Norm. 1996. “Industrial-Strength Management Strategies.” IEEE Software 13(4):94–103.

[ref033] <collabname>Rules Group</collabname>. 2012. http://www.businessrulesgroup.org.

[ref034] Callele, David, Eric Neufeld, and Kevin Schneider. 2008. “Emotional Requirements.” IEEE Software 25(1):43–45.

[ref035] Caputo, Kim. 1998. CMM Implementation Guide: Choreographing Software Process Improvement. Reading, MA: Addison-Wesley.

[ref036] Carr, Marvin J., Suresh L. Konda, Ira Monarch, F. Carol Ulrich, and Clay F. Walker. 1993. Taxonomy-Based Risk Identification (CMU/ SEI-93-TR-6). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University.

[ref037] Cavano, J. P., and J. A. McCall. 1978. “A Framework for the Measurement of Software Quality.” ACM SIGSOFT Software Engineering Notes 3(5):133–139.

[ref038] Charette, Robert N. 1990. Applications Strategies for Risk Analysis. New York: McGraw-Hill.

[ref039] Chernak, Yuri. 2012. “Requirements Reuse: The State of the Practice.” In Proceedings of the 2012 IEEE International Conference on Software Science, Technology and Engineering, 46–53. Los Alamitos, CA: IEEE Computer Society Press.

[ref040] Chung, Lawrence, Kendra Cooper, and D.T. Huynh. 2001. “COTS-Aware Requirements Engineering Techniques.” In Proceedings of the 2001 Workshop on Embedded Software Technology (WEST’01).

[ref041] Cockburn, Alistair. 2001. Writing Effective Use Cases. Boston: Addison-Wesley.

[ref042] Cohen, Lou. 1995. Quality Function Deployment: How to Make QFD Work for You. Reading, MA: Addison-Wesley.

[ref043] Cohn, Mike. 2004. User Stories Applied: For Agile Software Development. Boston: Addison-Wesley.

[ref044] Cohn, Mike. 2005. Agile Estimating and Planning. Upper Saddle River, NJ: Prentice Hall.

[ref045] Cohn, Mike. 2010. Succeeding with Agile: Software Development Using Scrum. Upper Saddle River, NJ: Addison-Wesley.

[ref046] Collard, Ross. 1999. “Test Design.” Software Testing & Quality Engineering 1(4):30–37.

[ref047] <collabname>Colorado State University</collabname>. 2013. “Writing@CSU.” http://writing.colostate.edu/guides/guide.cfm?guideid=68.

[ref048] Constantine, Larry. 1998. “Prototyping from the User’s Viewpoint.” Software Development 6(11):51–57.

[ref049] Constantine, Larry L., and Lucy A. D. Lockwood. 1999. Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design. Reading, MA: Addison-Wesley.

[ref050] Cooper, Alan. 2004. The Inmates Are Running the Asylum: Why High-Tech Products Drive Us Crazy and How to Restore the Sanity. Indianapolis, IN: Sams Publishing.

[ref051] Covey, Stephen R. 2004. The 7 Habits of Highly Effective People. New York: Free Press.

[ref052] Davenport, Thomas H., ed. 2013. Enterprise Analytics: Optimize Performance, Process, and Decisions through Big Data. Upper Saddle River, NJ: Pearson Education, Inc.

[ref053] Davenport, Thomas H., Jeanne G. Harris, and Robert Morrison. 2010. Analytics at Work: Smarter Decisions, Better Results. Boston: Harvard Business Review Press.

[ref054] Davis, Alan M. 1993. Software Requirements: Objects, Functions, and States, Revised Edition. Englewood Cliffs, NJ: Prentice Hall PTR.

[ref055] Davis, Alan M. 1995. 201 Principles of Software Development. New York: McGraw-Hill.

[ref056] Davis, Alan M. 2005. Just Enough Requirements Management: Where Software Development Meets Marketing. New York: Dorset House Publishing.

[ref057] DeGrace, Peter, and Leslie Hulet Stahl. 1993. The Olduvai Imperative: CASE and the State of Software Engineering Practice. Englewood Cliffs, NJ: Yourdon Press/Prentice Hall.

[ref058] Dehlinger, Josh, and Robyn R. Lutz. 2008. “Supporting Requirements Reuse in Multi-Agent System Product Line Design and Evolution.” In Proceedings of the 24th IEEE International Conference on Software Maintenance, 207–216. Los Alamitos, CA: IEEE Computer Society Press.

[ref059] DeMarco, Tom. 1979. Structured Analysis and System Specification. Upper Saddle River, NJ: Prentice Hall PTR.

[ref060] DeMarco, Tom, and Timothy Lister. 1999. Peopleware: Productive Projects and Teams, 2nd ed. New York: Dorset House Publishing.

[ref061] Denne, Mark, and Jane Cleland-Huang. 2003. Software by Numbers: Low-Risk, High-Return Development. Santa Clara, CA: Sun Microsystems Press/Prentice Hall.

[ref062] Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Raleigh, NC: The Pragmatic Bookshelf.

[ref063] Devine, Tom. 2008. “Replacing a Legacy System.” http://www.richconsulting.com/our/pdfs/RichConsulting_ReplacingLegacy.pdf.

[ref064] Douglass, Bruce Powel. 2001. “Capturing Real-Time Requirements.” Embedded Systems Programming (November 2001). http://www.embedded.com/story/OEG20011016S0126.

[ref065] Dyché, Jill. 2012. “The 7 Steps in Big Data Delivery.” http://www.networkworld.com/news/tech/2012/071112-big-data-delivery-260813.html.

[ref066] Engblom, Jakob. 2007. “Using Simulation Tools For Embedded Systems Software Development: Part I.” Embedded Systems Programming (May 2007). http://www.embedded.com/design/real-time-and-performance/4007090/Using-simulation-tools-for-embedded-systems-software-development-Part-1.

[ref067] Ericson II, Clifton A. 2005. Hazard Analysis Techniques for System Safety. Hoboken, NJ: John Wiley & Sons, Inc.

[ref068] Ericson II, Clifton A. 2011. Fault Tree Analysis Primer. Charleston, NC: CreateSpace.

[ref069] Ericson II, Clifton A. 2012. Hazard Analysis Primer. Charleston, NC: CreateSpace.

[ref070] Fagan, Michael E. 1976. “Design and Code Inspections to Reduce Errors in Program Development.” IBM Systems Journal 15(3):182–211.

[ref071] Ferdinandi, Patricia L. 2002. A Requirements Pattern: Succeeding in the Internet Economy. Boston: Addison-Wesley.

[ref072] Firesmith, Donald. 2004. “Specifying Reusable Security Requirements.” Journal of Object Technology 3(1):61–75.

[ref073] Fisher, Roger, William Ury, and Bruce Patton. 2011. Getting to Yes: Negotiating Agreement Without Giving In. New York: Penguin Books.

[ref074] Florence, Al. 2002. “Reducing Risks Through Proper Specification of Software Requirements.” CrossTalk 15(4):13–15.

[ref075] Fowler, Martin. 1999. Refactoring: Improving the Design of Existing Code. Reading, MA: Addison-Wesley.

[ref076] Fowler, Martin. 2003. UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3rd ed. Boston: Addison-Wesley.

[ref077] Franks, Bill. 2012. Taming the Big Data Tidal Wave: Finding Opportunities in Huge Data Streams with Advanced Analytics. Hoboken, NJ: John Wiley & Sons, Inc.

[ref078] Frye, Colleen. 2009. “New Requirements Definition Tools Focus on Chronic Flaws.” TechTarget. http://searchsoftwarequality.techtarget.com/news/1354455/New-requirements-definition-tools-focus-on-chronic-flaws.

[ref079] <collabname>GAO (Government Accounting Office)</collabname>. 2004. “Stronger Management Practices Are Needed to Improve DOD’s Software-Intensive Weapon Acquisitions.” GAO-04-393, http://www.gao.gov/products/GAO-04-393.

[ref080] Garmahis, Michael. 2009. “Top 20 Wireframe Tools.” http://garmahis.com/reviews/wireframe-tools.

[ref081] Gause, Donald C., and Brian Lawrence. 1999. “User-Driven Design.” Software Testing & Quality Engineering 1(1):22–28.

[ref082] Gause, Donald C., and Gerald M. Weinberg. 1989. Exploring Requirements: Quality Before Design. New York: Dorset House Publishing.

[ref083] Gilb, Tom. 1988. Principles of Software Engineering Management. Harlow, England: Addison-Wesley.

[ref084] Gilb, Tom. 1997. “Quantifying the Qualitative: How to Avoid Vague Requirements by Clear Specification Language.” Requirenautics Quarterly 12:9–13.

[ref085] Gilb, Tom. 2005. Competitive Engineering: A Handbook for Systems Engineering, Requirements Engineering, and Software Engineering Using Planguage. Oxford, England: Elsevier Butterworth-Heinemann.

[ref086] Gilb, Tom. 2007. “Requirements for Outsourcing.” Methods and Tools (Winter 2007).

[ref087] Gilb, Tom, and Kai Gilb. 2011. “User Stories: A Skeptical View.” Agile Record 6:52–54.

[ref088] Gilb, Tom, and Dorothy Graham. 1993. Software Inspection. Wokingham, England: Addison-Wesley.

[ref089] Glass, Robert L. 1992. Building Quality Software. Englewood Cliffs, NJ: Prentice Hall.

[ref090] Gomaa, Hassan. 2004. Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures. Boston: Addison-Wesley.

[ref091] Gorman, Mary, and Ellen Gottesdiener. 2011. “It’s the Goal, Not the Role: The Value of Business Analysis in Scrum.” http://www.stickyminds.com/s.asp?F=S16902_COL_2.

[ref092] Gottesdiener, Ellen. 2001. “Decide How to Decide.” Software Development 9(1):65–70.

[ref093] Gottesdiener, Ellen. 2002. Requirements by Collaboration: Workshops for Defining Needs. Boston: Addison-Wesley.

[ref094] Gottesdiener, Ellen. 2005. The Software Requirements Memory Jogger. Salem, NH: Goal/QPC.

[ref095] Gottesdiener, Ellen. 2009. “Agile Business Analysis in Flow: The Work of the Agile Analyst (Part II).” http://ebgconsulting.com/Pubs/Articles.

[ref096] Grady, Robert B. 1999. “An Economic Release Decision Model: Insights into Software Project Management.” In Proceedings of the Applications of Software Measurement Conference, 227–239. Orange Park, FL: Software Quality Engineering.

[ref097] Grady, Robert B., and Tom Van Slack. 1994. “Key Lessons in Achieving Widespread Inspection Use.” IEEE Software 11(4):46–57.

[ref098] Graham, Dorothy. 2002. “Requirements and Testing: Seven Missing-Link Myths.” IEEE Software 19(5):15–17.

[ref099] Grochow, Jerrold M. 2012. “IT Planning for Business Analytics.” International Institute for Analytics Brief.

[ref100] Ham, Gary A. 1998. “Four Roads to Use Case Discovery: There Is a Use (and a Case) for Each One.” CrossTalk 11(12):17–19.

[ref101] Hammer, Michael, and Graham Champy. 2006. Reengineering the Corporation: A Manifesto for Business Revolution. New York: HarperCollins.

[ref102] Hardy, Terry L. 2011. Essential Questions in System Safety: A Guide for Safety Decision Makers. Bloomington, IN: AuthorHouse.

[ref103] Harmon, Paul. 2007. Business Process Change: A Guide for Business Managers and BPM and Six Sigma Professionals, 2nd ed. Burlington, MA: Morgan Kaufmann Publishers, Inc.

[ref104] Harrington, H. James. 1991. Business Process Improvement: The Breakthrough Strategy for Total Quality, Productivity, and Competitiveness. New York: McGraw-Hill.

[ref105] Haskins, B., J. Stecklein, D. Brandon, G. Moroney, R. Lovell, and J. Dabney. 2004. “Error Cost Escalation through the Project Life Cycle.” In Proceedings of the 14th Annual International Symposium of INCOSE. Toulouse, France. International Council on Systems Engineering.

[ref106] Hatley, Derek, Peter Hruschka, and Imtiaz Pirbhai. 2000. Process for System Architecture and Requirements Engineering. New York: Dorset House Publishing.

[ref107] Herrmann, Debra S. 1999. Software Safety and Reliability: Techniques, Approaches, and Standards of Key Industrial Sectors. Los Alamitos, CA: IEEE Computer Society Press.

[ref108] Hoffman, Cecilie, and Rebecca Burgess. 2009. “Use and Profit from Peer Reviews on Business Requirements Documents.” Business Analyst Times (September–December 2009).

[ref109] Hofmann, Hubert F., and Franz Lehner. 2001. “Requirements Engineering as a Success Factor in Software Projects.” IEEE Software 18(4):58–66.

[ref110] Hooks, Ivy F., and Kristin A. Farry. 2001. Customer-Centered Products: Creating Successful Products Through Smart Requirements Management. New York: AMACOM.

[ref111] Hsia, Pei, David Kung, and Chris Sell. 1997. “Software Requirements and Acceptance Testing.” In Annals of Software Engineering. 3:291–317.

[ref112] Humphrey, Watts S. 1989. Managing the Software Process. Reading, MA: Addison-Wesley.

[ref113] <collabname>IEEE</collabname>. 1998. “IEEE Std 1061-1998: IEEE Standard for a Software Quality Metrics Methodology.” Los Alamitos, CA: IEEE Computer Society Press.

[ref114] <collabname>IFPUG</collabname>. 2010. Function Point Counting Practices Manual, Version 4.3.1. Princeton Junction, NJ: International Function Point Users Group.

[ref115] <collabname>IIBA</collabname>. 2009. A Guide to the Business Analysis Body of Knowledge (BABOK Guide), Version 2.0. Toronto: International Institute of Business Analysis.

[ref116] <collabname>IIBA</collabname>. 2010. IIBA Business Analysis Self-Assessment. Toronto: International Institute of Business Analysis.

[ref117] <collabname>IIBA</collabname>. 2011. IIBA Business Analysis Competency Model, Version 3.0. Toronto: International Institute of Business Analysis.

[ref118] <collabname>IIBA</collabname>. 2013. IIBA Agile Extension to the BABOK Guide, Version 1.0. Toronto: International Institute of Business Analysis.

[ref119] Imhoff, Claudia. 2005. “Charting a Smooth Course to BI Implementation.” Intelligent Solutions, Inc. http://www.sas.com/reg/wp/corp/3529.

[ref120] <collabname>INCOSE</collabname>. 2010. “INCOSE Requirements Management Tools Survey.” http://www.incose.org/productspubs/products/rmsurvey.aspx.

[ref121] <collabname>International Institute for Analytics</collabname>. 2013. “Analytics 3.0.” International Institute for Analytics. http://iianalytics.com/a3.

[ref122] <collabname>ISO/IEC</collabname>. 2007. “ISO/IEC 25030:2007, Software engineering—Software product Quality Requirements and Evaluation (SQuaRE)—Quality Requirements.” Geneva, Switzerland: International Organization for Standardization.

[ref123] <collabname>ISO/IEC</collabname>. 2011. “ISO/IEC 25010:2011, Systems and software engineering—Systems and software Quality Requirements and Evaluation (SQuaRE)—System and software quality models.” Geneva, Switzerland: International Organization for Standardization.

[ref124] <collabname>ISO/IEC/IEEE</collabname>. 2011. “ISO/IEC/IEEE 29148:2011(E), Systems and software engineering—Life cycle processes—Requirements engineering.” Geneva, Switzerland: International Organization for Standardization.

[ref125] Jacobson, Ivar, Grady Booch, and James Rumbaugh. 1999. The Unified Software Development Process. Reading, MA: Addison-Wesley.

[ref126] Jacobson, Ivar, Magnus Christerson, Patrik Jonsson, and Gunnar Övergaard. 1992. Object-Oriented Software Engineering: A Use Case Driven Approach. Harlow, England: Addison-Wesley.

[ref127] Jarke, Matthias. 1998. “Requirements Tracing.” Communications of the ACM 41(12):32–36.

[ref128] Jeffries, Ron, Ann Anderson, and Chet Hendrickson. 2001. Extreme Programming Installed. Boston: Addison-Wesley.

[ref129] Johnson, Jeff. 2010. Designing with the Mind in Mind: Simple Guide to Understanding User Interface Design Rules. San Francisco, CA: Morgan Kaufmann Publishers, Inc.

[ref130] Jones, Capers. 1994. Assessment and Control of Software Risks. Englewood Cliffs, NJ: Prentice Hall PTR.

[ref131] Jones, Capers. 1996a. “Strategies for Managing Requirements Creep.” IEEE Computer 29(6):92–94.

[ref132] Jones, Capers. 1996b. Applied Software Measurement, 2nd ed. New York: McGraw-Hill.

[ref133] Jones, Capers. 2006. “Social and Technical Reasons for Software Project Failures.” CrossTalk 19(6):4–9.

[ref134] Jung, Ho-Won. 1998. “Optimizing Value and Cost in Requirements Analysis.” IEEE Software 15(4):74–78.

[ref135] Karlsson, Joachim, and Kevin Ryan. 1997. “A Cost-Value Approach for Prioritizing Requirements.” IEEE Software 14(5):67–74.

[ref136] Kavi, Krishna M., Robert Akl, and Ali R. Hurson. 2009. “Real-Time Systems: An Introduction and the State-of-the-Art.” Wiley Encyclopedia of Computer Science and Engineering, 2369–2377.

[ref137] Keil, Mark, and Erran Carmel. 1995. “Customer-Developer Links in Software Development.” Communications of the ACM 38(5):33–44.

[ref138] Kelly, John C., Joseph S. Sherif, and Jonathon Hops. 1992. “An Analysis of Defect Densities Found During Software Inspections.” Journal of Systems and Software 17(2):111–117.

[ref139] Kerth, Norman L. 2001. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing.

[ref140] Kleidermacher, David, and Mike Kleidermacher. 2012. Embedded Systems Security: Practical Methods for Safe and Secure Software and Systems Development. Waltham, MA: Elsevier Inc.

[ref141] Koopman, Philip. 2010. Better Embedded Systems Software. Pittsburgh, PA: Drumnadrochit Press.

[ref142] Kosman, Robert J. 1997. “A Two-Step Methodology to Reduce Requirement Defects.” In Annals of Software Engineering. 3:477–494.

[ref143] Kovitz, Benjamin L. 1999. Practical Software Requirements: A Manual of Content and Style. Greenwich, CT: Manning Publications Co.

[ref144] Krug, Steve. 2006. Don’t Make Me Think: A Common Sense Approach to Web Usability, 2nd ed. Berkeley, CA: New Riders Publishing.

[ref145] Kukreja, Nupul, Sheetal Swaroop Payyavula, Barry Boehm, and Srinivas Padmanabhuni. 2012. “Selecting an Appropriate Framework for Value-Based Requirements Prioritization: A Case Study.” In Proceedings of the 20th IEEE International Requirements Engineering Conference, 303–308. Los Alamitos, CA: IEEE Computer Society Press.

[ref146] Kulak, Daryl, and Eamonn Guiney. 2004. Use Cases: Requirements in Context, 2nd ed. Boston: Addison-Wesley.

[ref147] Larman, Craig. 1998. “The Use Case Model: What Are the Processes?” Java Report 3(8):62–72.

[ref148] Larman, Craig. 2004. Agile and Iterative Development: A Manager’s Guide. Boston: Addison-Wesley.

[ref149] Larman, Craig, and Victor R. Basili. 2003. “Iterative and Incremental Development: A Brief History.” IEEE Computer 36(6):47–56.

[ref150] Lauesen, Soren. 2002. Software Requirements: Styles and Techniques. London: Addison-Wesley.

[ref151] Lavi, Jonah Z., and Joseph Kudish. 2005. Systems Modeling & Requirements Specification Using ECSAM: An Analysis Method for Embedded and Computer-Based Systems. New York: Dorset House Publishing.

[ref152] Lawlis, Patricia K., Kathryn E. Mark, Deborah A. Thomas, and Terry Courtheyn. 2001. “A Formal Process for Evaluating COTS Software Products.” IEEE Computer 34(5):58–63.

[ref153] Lawrence, Brian. 1996. “Unresolved Ambiguity.” American Programmer 9(5):17–22.

[ref154] Lawrence, Brian. 1997. “Requirements Happens…” American Programmer 10(4):3–9.

[ref155] Lazar, Jonathan. 2001. User-Centered Web Development. Sudbury, MA: Jones and Bartlett Publishers.

[ref156] Leffingwell, Dean. 1997. “Calculating the Return on Investment from More Effective Requirements Management.” American Programmer 10(4):13–16.

[ref157] Leffingwell, Dean. 2011. Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise. Upper Saddle River, NJ: Addison-Wesley.

[ref158] Leffingwell, Dean, and Don Widrig. 2000. Managing Software Requirements: A Unified Approach. Reading, MA: Addison-Wesley.

[ref159] Leishman, Theron R., and David A. Cook. 2002. “Requirements Risks Can Drown Software Projects.” CrossTalk 15(4):4–8.

[ref160] Leveson, Nancy. 1995. Safeware: System Safety and Computers. Reading, MA: Addison-Wesley.

[ref161] Lilly, Susan. 2000. “How to Avoid Use-Case Pitfalls.” Software Development 8(1):40–44.

[ref162] Martin, Johnny, and W. T. Tsai. 1990. “N-fold Inspection: A Requirements Analysis Technique.” Communications of the ACM 33(2):225–232.

[ref163] Mavin, Alistair, Philip Wilkinson, Adrian Harwood, and Mark Novak. 2009. “EARS (Easy Approach to Requirements Syntax).” In Proceedings of the 17th International Conference on Requirements Engineering, 317–322. Los Alamitos, CA: IEEE Computer Society Press.

[ref164] McConnell, Steve. 1996. Rapid Development: Taming Wild Software Schedules. Redmond, WA: Microsoft Press.

[ref165] McConnell, Steve. 1997. “Managing Outsourced Projects.” Software Development 5(12):80, 78–79.

[ref166] McConnell, Steve. 1998. Software Project Survival Guide. Redmond, WA: Microsoft Press.

[ref167] McConnell, Steve. 2004. Code Complete: A Practical Handbook of Software Construction, 2nd ed. Redmond, WA: Microsoft Press.

[ref168] McConnell, Steve. 2006. Software Estimation: Demystifying the Black Art. Redmond, WA: Microsoft Press.

[ref169] McGraw, Karen L., and Karan Harbison. 1997. User-Centered Requirements: The Scenario-Based Engineering Process. Mahwah, NJ: Lawrence Erlbaum Associates.

[ref170] Miller, Roxanne E. 2009. The Quest for Software Requirements. Milwaukee, WI: MavenMark Books.

[ref171] Moore, Geoffrey A. 2002. Crossing the Chasm: Marketing and Selling High-Tech Products to Mainstream Customers. New York: HarperBusiness.

[ref172] Morgan, Matthew. 2009. “Requirements Definition for Outsourced Teams.” Business Analyst Times. http://www.batimes.com/articles/requirements-definition-for-outsourced-teams.html.

[ref173] Morgan, Tony. 2002. Business Rules and Information Systems: Aligning IT with Business Goals. Boston: Addison-Wesley.

[ref174] Musa, John D. 1996. “Software-Reliability-Engineered Testing.” IEEE Computer 29(11):61–68.

[ref175] Musa, John D. 1999. Software Reliability Engineering. New York: McGraw-Hill.

[ref176] <collabname>NASA</collabname>. 2009. “NPR 7150.2A: NASA Software Engineering Requirements.” http://nodis3.gsfc.nasa.gov/displayDir.cfm?Internal_ID=N_PR_7150_002A_&page_name=AppendixA.

[ref177] Nejmeh, Brian A., and Ian Thomas. 2002. “Business-Driven Product Planning Using Feature Vectors and Increments.” IEEE Software 19(6):34–42.

[ref178] Nelsen, E. Dale. 1990. “System Engineering and Requirement Allocation.” In System and Software Requirements Engineering, Richard H. Thayer and Merlin Dorfman, eds. Los Alamitos, CA: IEEE Computer Society Press.

[ref179] Nielsen, Jakob. 2000. Designing Web Usability. Indianapolis, IN: New Riders Publishing.

[ref180] <collabname>OMG</collabname>. 2011. Business Process Model and Notation (BPMN) version 2.0. Object Management Group. http://www.omg.org/spec/BPMN/2.0.

[ref181] Pardee, William J. 1996. To Satisfy & Delight Your Customer: How to Manage for Customer Value. New York: Dorset House Publishing.

[ref182] Patel, T., and James Taylor. 2010. “Business Analytics 101: Unlock the Business Intelligence Hidden in Company Databases.” http://www.sas.com/resources/whitepaper/wp_28372.pdf.

[ref183] Patterson, Kelly, Joseph Grenny, Ron McMillan, and Al Switzler. 2011. Crucial Conversations: Tools for Talking When Stakes are High, 2nd ed. New York: McGraw-Hill.

[ref184] Peterson, Gary. 2002. “Risqué Requirements.” CrossTalk 15(4):31.

[ref185] Pichler, Roman. 2010. Agile Product Management with Scrum: Creating Products that Customers Love. Upper Saddle River, NJ: Addison-Wesley.

[ref186] <collabname>PMI</collabname>. 2013. A Guide to the Project Management Body of Knowledge: PMBOK Guide, 5th ed. Newtown Square, PA: Project Management Institute.

[ref187] Podeswa, Howard. 2009. The Business Analyst’s Handbook. Boston: Course Technology.

[ref188] Podeswa, Howard. 2010. UML for the IT Business Analyst: A Practical Guide to Requirements Gathering Using the Unified Modeling Language, 2nd ed. Boston: Course Technology.

[ref189] Porter, Adam A., Lawrence G. Votta, Jr., and Victor R. Basili. 1995. “Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment.” IEEE Transactions on Software Engineering 21(6):563–575.

[ref190] Porter-Roth, Bud. 2002. Request for Proposal: A Guide to Effective RFP Development. Boston: Addison-Wesley.

[ref191] Poston, Robert M. 1996. Automating Specification-Based Software Testing. Los Alamitos, CA: IEEE Computer Society Press.

[ref192] Potter, Neil S., and Mary E. Sakry. 2002. Making Process Improvement Work: A Concise Action Guide for Software Managers and Practitioners. Boston: Addison-Wesley.

[ref193] Pugh, Ken. 2011. Lean-Agile Acceptance Test-Driven Development: Better Software Through Collaboration. Upper Saddle River, NJ: Addison-Wesley.

[ref194] Putnam, Lawrence H., and Ware Myers. 1997. Industrial Strength Software: Effective Management Using Measurement. Los Alamitos, CA: IEEE Computer Society Press.

[ref195] Radice, Ronald A. 2002. High Quality Low Cost Software Inspections. Andover, MA: Paradoxicon Publishing.

[ref196] Ramesh, Bala, Curtis Stubbs, Timothy Powers, and Michael Edwards. 1995. “Lessons Learned from Implementing Requirements Traceability.” CrossTalk 8(4):11–15, 20.

[ref197] Rettig, Marc. 1994. “Prototyping for Tiny Fingers.” Communications of the ACM 37(4):21–27.

[ref198] Rierson, Leanna. 2013. Developing Safety-Critical Software: A Practical Guide for Aviation Software and DO-178C Compliance. Boca Raton, FL: CRC Press.

[ref199] Robertson, James. 2002. “Eureka! Why Analysts Should Invent Requirements.” IEEE Software 19(4):20–22.

[ref200] Robertson, James, and Suzanne Robertson. 1994. Complete Systems Analysis: The Workbook, the Textbook, the Answers. New York: Dorset House Publishing.

[ref201] Robertson, Suzanne, and James Robertson. 2013. Mastering the Requirements Process: Getting Requirements Right, 3rd ed. Upper Saddle River, NJ: Addison-Wesley.

[ref202] Rose-Coutré, Robert. 2007. “Capturing Implied Requirements.” http://www.stickyminds.com/s.asp?F=S12998_ART_2.

[ref203] Ross, Ronald G. 1997. The Business Rule Book: Classifying, Defining, and Modeling Rules, Version 4.0, 2nd ed. Houston: Business Rule Solutions, LLC.

[ref204] Ross, Ronald G. 2001. “The Business Rules Classification Scheme.” DataToKnowledge Newsletter 29(5).

[ref205] Ross, Ronald G., and Gladys S. W. Lam. 2011. Building Business Solutions: Business Analysis with Business Rules. Houston: Business Rule Solutions, LLC.

[ref206] Rothman, Johanna. 2000. Reflections Newsletter 3(1).

[ref207] Royce, Winston. 1970. “Managing the Development of Large Software Systems.” In Proceedings of IEEE WESCON 26, 1–9.

[ref208] Rozanski, Nick, and Eoin Woods. 2005. Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. Upper Saddle River, NJ: Pearson Education, Inc.

[ref209] Rubin, Jeffrey, and Dana Chisnell. 2008. Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests, 2nd ed. Indianapolis, IN: Wiley Publishing, Inc.

[ref210] Scalable Systems. 2008. “How Big is Your Data?” http://www.scalable-systems.com/whitepaper/Scalable_WhitePaper_Big_Data.pdf.

[ref211] Schneider, G. Michael, Johnny Martin, and W. T. Tsai. 1992. “An Experimental Study of Fault Detection in User Requirements Documents.” ACM Transactions on Software Engineering and Methodology 1(2):188–204.

[ref212] Schonberger, Richard. J. 2008. Best Practices in Lean Six Sigma Process Improvement: A Deeper Look. Hoboken, NJ: John Wiley & Sons, Inc.

[ref213] Schwaber, Ken. 2004. Agile Project Management with Scrum. Redmond, WA: Microsoft Press.

[ref214] Schwarz, Roger. 2002. The Skilled Facilitator: A Comprehensive Resource for Consultants, Facilitators, Managers, Trainers, and Coaches. San Francisco, CA: Jossey-Bass.

[ref215] <collabname>Seilevel</collabname>. 2011. “Seilevel Requirements Management Tool Evaluation Results.” http://www.seilevel.com/wp-content/uploads/2011/09/Seilevel-RequirementsManagementToolEvalResults2.xls.

[ref216] <collabname>Seilevel</collabname>. 2012. “Seilevel Project Assessment.” http://www.seilevel.com/wp-content/uploads/Project_Assessments_Template.xls.

[ref217] Sharp, Alec, and Patrick McDermott. 2008. Workflow Modeling: Tools for Process Improvement and Application Development. Norwood, Massachusetts: Artec, Inc.

[ref218] Shehata, Mohammed S., Armin Eberlein, and H. James Hoover. 2002. “Requirements Reuse and Feature Interaction Management.” In Proceedings of the 15th International Conference on Software & Systems Engineering and their Applications. Paris.

[ref219] Shull, F., V. Basili, B. Boehm., A. W. Brown, A. Costa, M. Lindvall, D. Port, I. Rus, R. Tesoriero, and M. Zelkowitz. 2002. “What We Have Learned About Fighting Defects.” In Proceedings of the Eighth IEEE Symposium on Software Metrics, 249–258. Ottawa, Canada. IEEE Computer Society Press.

[ref220] Sibbet, David. 1994. Effective Facilitation: Achieving Results with Groups. San Francisco, CA: The Grove Consultants International.

[ref221] Simmons, Erik. 2001. “From Requirements to Release Criteria: Specifying, Demonstrating, and Monitoring Product Quality.” In Proceedings of the 2001 Pacific Northwest Software Quality Conference, 155–165. Portland, OR: Pacific Northwest Software Quality Conference.

[ref222] Smith, Larry W. 2000. “Project Clarity Through Stakeholder Analysis.” CrossTalk 13(12):4–9.

[ref223] Sommerville, Ian, and Pete Sawyer. 1997. Requirements Engineering: A Good Practice Guide. Chichester, England: John Wiley & Sons Ltd.

[ref224] Sorensen, Reed. 1999. “CCB—An Acronym for ‘Chocolate Chip Brownies’? A Tutorial on Control Boards.” CrossTalk 12(3):3–6.

[ref225] <collabname>The Standish Group</collabname>. 2009. “Chaos Summary 2009.” West Yarmouth, MA: The Standish Group International, Inc.

[ref226] Stevens, Richard, Peter Brook, Ken Jackson, and Stuart Arnold. 1998. Systems Engineering: Coping with Complexity. London: Prentice Hall.

[ref227] Taylor, James. 2012. “Decision Discovery for a Major Business Function.” International Institute for Analytics Research Brief.

[ref228] Taylor, James. 2013. “Using Decision Discovery to Manage Analytic Project Requirements.” International Institute for Analytics Research Brief.

[ref229] Thayer, Richard H. 2002. “Software System Engineering: A Tutorial.” IEEE Computer 35(4):68–73.

[ref230] Thomas, Steven. 2008. “Agile Change Management.” http://itsadeliverything.com/agile-change-management.

[ref231] Thompson, Bruce, and Karl Wiegers. 1995. “Creative Client/ Server for Evolving Enterprises.” Software Development 3(2):34–44.

[ref232] Van Veenendaal, Erik P. W. M. 1999. “Practical Quality Assurance for Embedded Software.” Software Quality Professional 1(3):7–18.

[ref233] Voas, Jeffrey. 1999. “Protecting Against What? The Achilles Heel of Information Assurance.” IEEE Software 16(1):28–29.

[ref234] Volere. 2013. “Requirements Tools.” http://www.volere.co.uk/tools.htm.

[ref235] von Halle, Barbara. 2002. Business Rules Applied: Building Better Systems Using the Business Rules Approach. New York: John Wiley & Sons, Inc.

[ref236] von Halle, Barbara, and Larry Goldberg. 2010. The Decision Model: A Business Logic Framework Linking Business and Technology. Boca Raton, FL: Auerbach Publications.

[ref237] Wallace, Dolores R., and Laura M. Ippolito. 1997. “Verifying and Validating Software Requirements Specifications.” In Software Requirements Engineering, 2nd ed., Richard H. Thayer and Merlin Dorfman, eds., 389–404. Los Alamitos, CA: IEEE Computer Society Press.

[ref238] Wasserman, Anthony I. 1985. “Extending State Transition Diagrams for the Specification of Human-Computer Interaction.” IEEE Transactions on Software Engineering SE-11(8):699–713.

[ref239] Weinberg, Gerald M. 1995. “Just Say No! Improving the Requirements Process.” American Programmer 8(10):19–23.

[ref240] Wiegers, Karl E. 1996. Creating a Software Engineering Culture. New York: Dorset House Publishing.

[ref241] Wiegers, Karl E. 1998a. “The Seven Deadly Sins of Software Reviews.” Software Development 6(3):44–47.

[ref242] Wiegers, Karl E. 1998b. “Improve Your Process With Online ‘Good Practices’.” Software Development 6(12):45–50.

[ref243] Wiegers, Karl E. 1999. “Software Process Improvement in Web Time.” IEEE Software 16(4):78–86.

[ref244] Wiegers, Karl E. 2000. “The Habits of Effective Analysts.” Software Development 8(10):62–65.

[ref245] Wiegers, Karl E. 2002. Peer Reviews in Software: A Practical Guide. Boston: Addison-Wesley.

[ref246] Wiegers, Karl E. 2003. “See You in Court.” Software Development 11(1):36–40.

[ref247] Wiegers, Karl E. 2006. More About Software Requirements: Thorny Issues and Practical Advice. Redmond, WA: Microsoft Press.

[ref248] Wiegers, Karl E. 2007. Practical Project Initiation: A Handbook with Tools. Redmond, WA: Microsoft Press.

[ref249] Wiegers, Karl E. 2011. Pearls from Sand: How Small Encounters Lead to Powerful Lessons. New York: Morgan James Publishing.

[ref250] Wiley, Bill. 2000. Essential System Requirements: A Practical Guide to Event-Driven Methods. Reading, MA: Addison-Wesley.

[ref251] Williams, Ray C., Julie A. Walker, and Audrey J. Dorofee. 1997. “Putting Risk Management into Practice.” IEEE Software 14(3):75–82.

[ref252] Wilson, Peter B. 1995. “Testable Requirements—An Alternative Sizing Measure.” The Journal of the Quality Assurance Institute 9(4):3–11.

[ref253] Withall, Stephen. 2007. Software Requirement Patterns. Redmond, WA: Microsoft Press.

[ref254] Wood, Jane, and Denise Silver. 1995. Joint Application Development, 2nd ed. New York: John Wiley & Sons, Inc.

[ref255] Young, Ralph R. 2001. Effective Requirements Practices. Boston: Addison-Wesley.

[ref256] Young, Ralph R. 2004. The Requirements Engineering Handbook. Norwood, MA: Artech House.