Predicting good requirements for in-house development projects

ABSTRACT

We surveyed software practitioners regarding software development practices used during recent projects. Five categories of questions broadly related to requirements were asked: the sponsor, customer/users, requirements issues, the project manager and project management, and the development process. Relationships between project factors and good requirements were investigated. We developed requirements prediction equations by dividing our response data into two data sets. Using binary logistic regression on each set we tested the equations developed. Such analysis provides us with insight into which variables are significant predictors of good requirements. The best predictors were 1) the customers/users had a high level of confidence in the development team, with 2) risks were controlled and managed by the project manager.

REFERENCES

• 1: Tom Addison , Seema Vallabh, Controlling software project risks: an empirical study of methods used by experienced project managers, Proceedings of the 2002 annual research conference of the South African institute of computer scientists and information technologists on Enablement through technology, September 16-18, 2002, Port Elizabeth, South Africa
• 2: Sergio Bandinelli , Elisabetta Di Nitto , Alfonso Fuggetta, Supporting Cooperation in the SPADE-1 Environment, IEEE Transactions on Software Engineering, v.22 n.12, p.841-865, December 1996 [doi>10.1109/32.553634 ]
• 3: Barry W. Boehm, Software Engineering Economics, Prentice Hall PTR, Upper Saddle River, NJ, 1981
• 4: Barry W. Boehm, Software Risk Management: Principles and Practices, IEEE Software, v.8 n.1, p.32-41, January 1991 [doi>10.1109/52.62930 ]
• 5: Barry Boehm , Victor R. Basili, Software Defect Reduction Top 10 List, Computer, v.34 n.1, p.135-137, January 2001 [doi>10.1109/2.962984 ]
• 6: Frederick P. Brooks, Jr., The Mythical Man-Month: Essays on Softw, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1978
• 7: Carl Clavedetscher, Point: User Involvement Key to Success, IEEE Software, v.15 n.2, p.30, March 1998
• 8: M. Davis , Didar Zowghi, Good requirements practices are neither necessary nor sufficient, Requirements Engineering, v.11 n.1, p.1-3, December 2005 [doi>10.1007/s00766-004-0206-4]
• 9: DeMarco T. and T. Lister (2003), Waltzing With Bears, Dorset House Publishing New York NY.
• 10: Tom DeMarco , Timothy Lister, Peopleware: productive projects and teams, Dorset House Publishing Co., Inc., New York, NY, 1987
• 11: Donald C. Gause , Gerald M. Weinberg, Exploring Requirements: Quality Before Design, Dorset House Publishing Co., Inc., New York, NY, 1989
• 12: Robert L. Glass, How not to prepare for a consulting assignment, and other ugly consultancy truths, Communications of the ACM, v.41 n.12, p.11-13, Dec. 1998 [doi>10.1145/290133.290137]
• 13: Robert L. Glass, Frequently Forgotten Fundamental Facts about Software Engineering, IEEE Software, v.18 n.3, p.112-111, May 2001 [doi>10.1109/MS.2001.922739]
• 14: Jackson, M. (2001), Problem Frames, Addison Wesley.
• 15: Capers Jones, Assessment and control of software risks, Yourdon Press, Upper Saddle River, NJ, 1994
• 16: Capers Jones, Strategies for managing requirements creep, Computer, v.29 n.6, p.92-94, June 1996 [doi>10.1109/2.507640 ]
• 17: Mark Keil , Paul E. Cule , Kalle Lyytinen , Roy C. Schmidt, A framework for identifying software project risks, Communications of the ACM, v.41 n.11, p.76-83, Nov. 1998 [doi>10.1145/287831.287843]
• 18: Benjamin L. Kovitz, Practical software requirements: a manual of content and style, Manning Publications Co., Greenwich, CT, 1998
• 19: Dean Leffingwell , Don Widrig, Managing software requirements: a unified approach, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 20: Steve McConnell, Rapid Development: Taming Wild Software Schedules, Microsoft Press, Redmond, WA, 1996
• 21: James D. McKeen , Tor Guimaraes, Successful strategies for user participation in systems development, Journal of Management Information Systems, v.14 n.2, p.133-150, September 1997
• 22: Tony Moynihan, How Experienced Project Managers Assess Risk, IEEE Software, v.14 n.3, p.35-41, May 1997 [doi>10.1109/52.589229 ]
• 23: Colin J. Neill , Phillip A. Laplante, Requirements Engineering: The State of the Practice, IEEE Software, v.20 n.6, p.40-45, November 2003 [doi>10.1109/MS.2003.1241365]
• 24: John S. Osmundson , James B. Michael , Martin J. Machniak , Mary A. Grossman, Quality management metrics for software development, Information and Management, v.40 n.8, p.799-812, September 2003 [doi>10.1016/S0378-7206(02)00114-3]
• 25: Paulk, M., B. Curtis, M. Chrissis, C. Webster (1993) Capability Maturity Model for Software, Technical Report, CMU/SEI-93-TR-024, Software Engineering Institute, Carnegie Mellon.
• 26: Roger S. Pressman, Software Engineering: A Practitioner's Approach, McGraw-Hill Higher Education, 2000
• 27: Procaccino, J.D., Verner, J. M., and M. Darter, "Toward Predicting Software Development Success from the Perspective of Practitioners: An Exploratory Bayesian Model" to appear in JIT.
• 28: Robertson J. and Robertson S. (2000), "Requirements Management: A Cinderella Story", Requirements Engineering Journal, 5 (2), pp134--136.
• 29: Vital Roy , Benoit A. Aubert, A dream project turns nightmare: how flawless software never got implemented, Annals of cases on information technology, IGI Publishing, Hershey, PA, 2003
• 30: Schmidt, R., Lyytinen, K., Keil, M., and Cule, P., (2001) "Identifying Software Project Risks: An International Delphi Study", Journal of Management Information Systems, Spring, Vol 17, No 4, pp 5--36.
• 31: Standish Group (1999), "Chaos: A Recipe for Success", Standish Group International.
• 32: Buford D. Tackett , Buddy Van Doren, Process Control for Error-Free Software: A Software Success Story, IEEE Software, v.16 n.3, p.24-29, May 1999 [doi>10.1109/52.765783 ]
• 33: Verner J. M. and Evanco W. M. (2003), "An Investigation into Software Process Knowledge" in Managing Software Engineering Knowledge, (eds) A. Aurum, R. Jeffery, C. Wohlin and M. Handzic, Springer-Verlag, pp29--47.
• 34: June M. Verner , William M. Evanco, In-House Software Development: What Project Management Practices Lead to Success?, IEEE Software, v.22 n.1, p.86-93, January 2005 [doi>10.1109/MS.2005.12]
• 35: Verner J. M, Cox. K. Bleistein S and Cerpa N. (2004) "Requirements Engineering and Software Project Success: An Industrial Survey in Australia and the U.S. Australia Journal of Information Systesm Vol 13, No 1 pp225--238.
• 36: Verner, J. M., Overmyer, S. P. and McCain, K.W. (1999) In the 25 years since the mythical man-month what have we learned about project management?, Information and Software Technology. 41(14): 1021--1026.
• 37: Karl Eugene Wiegers, Software Requirements, Microsoft Press, Redmond, WA, 2003
• 38: Roel Wieringa , Christof Ebert, Guest Editors' Introduction: RE'03--Practical Requirements Engineering Solutions, IEEE Software, v.21 n.2, p.16-18, March 2004 [doi>10.1109/MS.2004.1270756]

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.1 Requirements/Specifications

General Terms:
Management

Keywords:
management, prediction, requirements, risk management