Requirements engineering: In search of the dependent variables

Information and Software Technology

Volumn 50, Issue 1-2, 2008, Pages 67-75

  Gorschek, Tony ^a   Davis, Alan M ^b  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^b UNIVERSITY OF COLORADO   (United States)

Author keywords

Dependent variables; Organizational perspective; Process improvement; Product focus; Product management; Project focus; Project management; Requirements engineering; Requirements process

Indexed keywords

PROCESS CONTROL; PROJECT MANAGEMENT; QUALITY ASSURANCE; SOFTWARE ENGINEERING;

DEPENDENT VARIABLES; ORGANIZATIONAL PERSPECTIVES; PROCESS IMPROVEMENT; QUALITY ASSESSMENT; REQUIREMENTS PROCESSES; SOFTWARE REQUIREMENTS SPECIFICATION (SRS);

REQUIREMENTS ENGINEERING;

EID: 36549080013     PISSN: 09505849     EISSN: None     Source Type: Journal    
DOI: 10.1016/j.infsof.2007.10.003     Document Type: Article

References (78)

1. Davis A.M., and Zowghi D. Good requirements practices are neither necessary nor sufficient. Requirements Engineering 11 1 (2006) 1-3
2. Ahern D.M., Clouse A., and Turner R. CMMI Distilled: A Practical Introduction to Integrated Process Improvement (2003), Addison-Wesley, Boston
3. CMMI-PDT, Capability maturity model integration (CMMI), Version 1.1, in: CMMI for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing Version 1.1 (CMMI-SE/SW/IPPD/SS, V1.1), Pittsburgh, 2002.
4. SCAMPI-ADT, Standard CMMI Appraisal Method for Process Improvement (Scampi) Version1.1 (CMU/SEI-2001-Hb-001), Carnegie Mellon - SEI, Pittsburgh, 2001, p. 245.
5. El Emam K., Drouin J.-N., and Melo W. SPICE: The Theory and Practice of Software Process Improvement and Capability Determination (1998), IEEE, Los Alamitos CA
6. SPICE-DT, SPICE, 2003, Available from: .
7. V.R. Basili, Quantitative Evaluation of Software Methodology, University of Maryland, College Park, Maryland, Technical report TR-1519, 1985.
8. V.R. Basili, F.E. McGarry, R. Pajerski, M.V. Zelkowitz, Lessons learned from 25 years of process improvement: the rise and fall of the Nasa Software Engineering Laboratory, in: The Proceedings of 24th International Conference on Software Engineering (ICSE02), Orlando, 2002, pp. 69-79.
9. Calvo-Manzano Villalón J.A., Cuevas Agusti{dotless}́n G., San Feliu Gilabert T., De Amescua Seco A., Garci{dotless}́a Sánchez L., and Pérez Cota M. Experiences in the application of software process improvement in SMEs. Software Quality Journal 10 (2002) 261-273
10. J.D. Herbsleb, D.R. Goldenson, A systematic survey of CMM experience and results, in: The Proceedings of the 18th International Conference on Software Engineering, Los Alamitos, CA, 1996, pp. 323-330.
11. K. Kautz, H.W. Hansen, K. Thaysen, Applying and Adjusting a software process improvement model in practice: the use of the ideal model in a small software enterprise, in: The Proceedings of the 2000 International Conference on Software Engineering, Los Alamitos, CA, 2000, pp. 626-633.
12. REAIMS, 2003, Available from: .
13. Sommerville I., and Sawyer P. Requirements Engineering: A Good Practice Guide (1999), John Wiley & Sons, Chichester UK
14. L. Scott, R. Jeffery, L. Carvalho, J. D'Ambra, P. Rutherford, Practical software process improvement - the impact project, in: The Proceedings of the Australian Software Engineering Conference, Los Alamitos, CA, 2001, pp. 182-189.
15. El Emam K.E., and Madhavji N.H.E. Elements of Software Process Assessment & Improvement (1999), Wiley-IEEE, Los Alamitos, CA
16. Kotonya G., and Sommerville I. Requirements Engineering: Processes and Techniques (1998), John Wiley, New York
17. T. Gorschek, M. Svahnberg, K. Tejle, Introduction and application of a lightweight requirements engineering process evaluation method, in: The Proceedings of the Ninth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'03), Essen, Germany, Available from: . 2003, pp. 101-112.
18. Wieringa R., and Ebert C. Guest Editors' introduction: RE'03: practical requirements engineering solutions. IEEE Software 21 (2004) 16-18
19. L. Karlsson, Å. Dahlstedt, J. Natt och Dag, B. Regnell, A. Persson, Challenges in market-driven requirements engineering - an industrial interview study, in: The Proceedings of the Eighth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'02), Essen, Germany, 2003, pp. 101-112.
20. K. Agusa, et al., Verification of requirements description, in: The Proceedings of Twelfth Hawaii International Conference on System Science, Los Alamitos, CA, 1979.
21. A. Davis, S. Overmyer, K. Jordan, J. Caruso, F. Dandashi, A. Dinh, G. Kincaid, G. Ledeboer, P. Reynolds, P. Sitaram, A. Ta, M. Theofanos, Identifying and measuring quality in a software requirements specification, in: The Proceedings of First International Software Metrics Symposium, Los Alamitos, CA, 1993, pp. 141-152.
22. K. Yue, What does it mean to say that a specification is complete? in: The Proceedings of Fourth International Workshop on Software Specification and Design, Los Alamitos, CA, 1987.
23. Forsberg K., and Mooz H. System engineering overview. In: Thayer R.H., Dorfman M., and Davis A.M. (Eds). Software Requirements Engineering. second ed. (1997), IEEE, Los Alamitos, CA 44-72
24. Standish Group, The Chaos Report, 1995, Available from: www.standishgroup.com.
25. Perloff J.M. Microeconomics. Third ed. (2004), Pearson Addison Wesley, Boston
26. Boehm B. Software engineering. IEEE Transactions on Computers 25 (1976) 1226-1241
27. M. Alford, I. Burns, R-Nets: a graph model for real-time software requirements, in: The Proceedings of Symposium on Computer Software Engineering, New York, NY, 1976, pp. 97-108.
28. P. Zave, R. Yeh, Executable requirements for embedded systems, in: The Proceedings of Fifth IEEE International Conference on Software Engineering, Los Alamitos, CA, 1981, pp. 295-304.
29. IEEE, Recommended Practice for Software Requirements Specifications (Standard 830-1984), IEEE Press, New York, NY, 1984.
30. A. Hunter, B. Nuseibeh, Analyzing inconsistent specifications, in The Proceedings of IEEE International Symposium on Requirements Engineering, Los Alamitos, CA, 1997, pp. 78-86.
31. D. Zowghi, V. Gervasi, The three C's of requirements: consistency, completeness, and correctness, in: The Proceedings of International Workshop on Requirements Engineering: Foundations for Software Quality, Essen, 2002, pp. 155-164.
32. B. Kovitz, Ambiguity and what to do about it, in: The Proceedings of Tenth International IEEE Conference on Requirements Engineering, Los Alamitos, CA, 2002, p. 213.
33. Boehm B.W. Software Cost Estimation with Cocomo II (2000), NJ, Prentice Hall, Upper Saddle River
34. Jones C. Applied Software Measurement: Assuring Productivity and Quality. second ed. (1997), McGraw-Hill, New York
35. Albrecht A.J., and Gaffney J.E. Software function, source lines of code, and development effort prediction. IEEE Transactions Software Engineering SE-9 (1983) 639-647
36. Rakitin S.R. Software Verification and Validation for Practitioners and Managers. second ed. (2001), Artech House, Boston, MA
37. O. Laitenberger, T. Beil, T. Schwinn, An industrial case study to examine a non-traditional inspection implementation for requirements specifications, in: The Proceedings of the Eighth IEEE Symposium on Software Metrics, Los Alamitos, CA, 2002, pp. 97-106.
38. Porter A.A., Votta L.G.J., and Basili V.R. Comparing detection methods for software requirements inspections: a replicated experiment. IEEE Transactions on Software Engineering 21 (1995) 563-576
39. Shull F., Rus I., and Basili V. How perspective-based reading can improve requirements inspections. Computer 33 (2000) 73-79
40. Ross S.A., Westerfield R., and Jordan B.D. Essentials of Corporate Finance. Third ed. (2001), McGraw-Hill, Boston
41. V. Basili, D. Weiss, Evaluation of a software requirements document by analysis of change data, in: The Proceedings of International Conference on Software Engineering, Los Alamitos, CA, 1981, pp. 314-323.
42. K. El Emam, D. Holtje, N.H. Madhavji, Causal analysis of the requirements change process for a large system, in: The Proceedings of International Conference on Software Maintenance, Los Alamitos, CA, 1997, pp. 214-221.
43. S.D.P. Harker, K.D. Eason, J.E. Dobson, The change and evolution of requirements as a challenge to the practice of software engineering, in: The Proceedings of IEEE International Symposium on Requirements Engineering, Los Alamitos, CA, 1993, pp. 266-272.
44. W. Lam, V. Shankararaman, G. Saward, Managing requirements change: a dissection of management issues, in: The Proceedings of Fifth International Workshop on Requirements Engineering: Foundations for Software Quality, Heidelberg, 1999, pp. 19-32.
45. Kotler P., and Armstrong G. Principles of Marketing. Ninth ed. (2001), Prentice Hall, Upper Saddle River NJ
46. Lehmann D.R., and Winer R.S. Product Management. Third ed. (2002), McGraw-Hill, Boston
47. Mintzberg H., Ahlstrand B.W., and Lampel J. Strategy Safari: A Guided Tour through the Wilds of Strategic Management (1998), Free Press, New York, NY
48. Weber M., and Weisbrod J. Requirements engineering in automotive development: experiences and challenges. IEEE Software 20 (2003) 16-24
49. B. Regnell, L. Karlsson, M. Host, An analytical model for requirements selection quality evaluation in product software development, in: The Proceedings of the 11th International Conference on Requirements Engineering, Los Alamitos, CA, 2003, pp. 254-263.
50. Saaty T.L., and Vargas L.G. Models, Methods, Concepts & Applications of the Analytic Hierarchy Process (2001), Kluwer Academic Publishers, Boston, MA
51. Leffingwell D., and Widrig D. Managing Software Requirements: A Unified Approach (2000), Addison-Wesley, Reading, MA
52. Davis A.M. The art of requirements triage. IEEE Computer 36 (2003) 42-49
53. Simmons E. Requirements triage: what can we learn from a medical approach?. IEEE Software 21 (2004) 86-88
54. M.S. Feather, T. Menzies, Converging on the optimal attainment of requirements, in: The Proceedings of IEEE Joint International Conference on Requirements Engineering, Los Alamitos, CA, 2002, pp. 263-270.
55. I. Hoh, D. Olson, T. Rodgers, A requirements negotiation model based on multi-criteria analysis, in: The Proceedings of Fifth IEEE International Symposium on Requirements Engineering, Los Alamitos, CA, 2001, pp. 312-313.
56. L. Karlsson, P. Berander, B. Regnell, C. Wohlin, Requirements prioritisation: an experiment on exhaustive pair-wise comparisons versus planning game partitioning, in: The Proceedings of the 8th International Conference on Empirical Assessment in Software Engineering (EASE 2004) - (in: proceedings of ICSE 2004), Los Alamitos, 2004, pp. 145-154.
57. Carlshamre P. Release planning in market-driven software product development: provoking an understanding. Requirements Engineering 7 (2002) 139-151
58. L. Karlsson, B. Regnell, J. Karlsson, S. Olsson, Post-release analysis of requirements selection quality - an industrial case study, in: The Proceedings of the Ninth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'03), Essen, Germany. Available from: , 2003, pp. 47-56.
59. T.J. Redling, A methodology for developing new product line requirements through gap analysis, in: The Proceedings of 22nd Digital Avionics Systems Conference, Indianapolis, 2003, pp. 10.A.1-101-11.
60. Zairi M. Best Practice: Process Innovation Management (1999), Butterworth-Heinemann, Oxford, Boston
61. Hill N., Brierley J., and MacDougall R. How to Measure Customer Satisfaction (1999), Brookfield, Gower, Aldershot
62. Davis A., Bersoff E., and Comer E. A strategy for comparing alternative software development life cycle models. IEEE Transactions on Software Engineering 14 (1988) 1453-1461
63. Kotler P., Armstrong G., Saunders J., and Wong V. Principles of Marketing. Third European ed. (2002), Prentice Hall, Harlow, England, New York
64. Davis A., Bersoff E., and Comer E. A strategy for comparing alternative software development life cycle models. IEEE Transactions on Software Engineering 14 (1998) 1453-1461
65. Gorchels L. The Product Manager's Handbook: The Complete Product Management Resource. second ed. (2000), NTC Business Books, Lincolnwood, Ill
66. Teece D.J. Managing Intellectual Capital: Organizational, Strategic, and Policy Dimensions (2000), Oxford University Press, New York, Oxford
67. T. Sasaki, A. Nagata, R. Toyama, T. Hirata, K. Hasegawa, Coevolution of patent strategy and product strategy, in: The Proceedings of Portland International Conference on Management of Engineering and Technology PICMET'01, Los Alamitos, CA, 2001, pp. 481-484.
68. In: Jirotka M., and Goguen J. (Eds). Requirements Engineering: Social and Technical Issues (1994), Academic Press, London, UK
69. Lam W. A case-study of requirements reuse through product families. Annals of Software Engineering 5 (1998) 253-277
70. K. Schmid, A comprehensive product line scoping approach and its validation, in: The Proceedings of the 24th International Conference on Software Engineering, New York, 2002, pp. 593-603.
71. Stern C.W., and Stalk G. Boston Consulting Group Perspectives on Strategy: From the Boston Consulting Group (1998), J. Wiley, New York
72. Cooper R.G., Edgett S.J., and Kleinschmidt E.J. Portfolio Management for New Products. second ed. (2001), Perseus Pub., Cambridge, MA
73. Bleistein S., Cox K., and Verner J. Modeling business strategy in e-business systems requirements engineering. In: Wang S., Tanaka K., Zhou S., et al. (Eds). Lecture Notes in Computer Science (2004), Springer-Verlag 617-628
74. Bleistein S., Cox K., and Verner J. Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams. Journal of Systems and Software 79 3 (2006) 362-378 (March
75. Rosenberg N. Inside the Black Box: Technology and Economics (1982), Cambridge University Press, Cambridge, MA
76. Davis A.M. Just Enough Requirements Management: Where Software Development Meets Marketing (2005), Dorset House Publ., New York, NY
77. Gorschek T., and Wohlin C. Requirements abstraction model. Requirements Engineering 11 1 (2006) 79-101 March
78. D. Damian, J. Chisan, L. Vaidyanathsamy, Y. Pal, An industrial case study of the impact of requirements engineering on downstream development, in: Proceedings. 2003 International Symposium on Empirical Software Engineering, 2003, pp. 40-49.