Requirements engineering: In search of the dependent variables

Davis, 2006, Good requirements practices are neither necessary nor sufficient, Requirements Engineering, 11, 1, 10.1007/s00766-004-0206-4

Ahern, 2003

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.

SCAMPI-ADT, Standard CMMI Appraisal Method for Process Improvement (Scampi) Version1.1 (CMU/SEI-2001-Hb-001), Carnegie Mellon – SEI, Pittsburgh, 2001, p. 245.

El Emam, 1998

SPICE-DT, SPICE, 2003, Available from: <http://www.sqi.gu.edu.au/spice/>.

V.R. Basili, Quantitative Evaluation of Software Methodology, University of Maryland, College Park, Maryland, Technical report TR-1519, 1985.

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.

Calvo-Manzano Villalón, 2002, Experiences in the application of software process improvement in SMEs, Software Quality Journal, 10, 261, 10.1023/A:1021638523413

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.

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.

REAIMS, 2003, Available from: <http://www.comp.lancs.ac.uk/computing/research/cseg/projects/reaims/index.html/>.

Sommerville, 1999

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.

El Emam, 1999

Kotonya, 1998

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: <http://www.bth.se/fou/Forskinfo.nsf/>. 2003, pp. 101–112.

Wieringa, 2004, Guest Editors’ introduction: RE’03: practical requirements engineering solutions, IEEE Software, 21, 16, 10.1109/MS.2004.1270756

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.

K. Agusa, et al., Verification of requirements description, in: The Proceedings of Twelfth Hawaii International Conference on System Science, Los Alamitos, CA, 1979.

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.

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.

Forsberg, 1997, System engineering overview, 44

Standish Group, The Chaos Report, 1995, Available from: www.standishgroup.com.

Perloff, 2004

Boehm, 1976, Software engineering, IEEE Transactions on Computers, 25, 1226, 10.1109/TC.1976.1674590

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.

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.

IEEE, Recommended Practice for Software Requirements Specifications (Standard 830-1984), IEEE Press, New York, NY, 1984.

A. Hunter, B. Nuseibeh, Analyzing inconsistent specifications, in The Proceedings of IEEE International Symposium on Requirements Engineering, Los Alamitos, CA, 1997, pp. 78–86.

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.

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.

Boehm, 2000

Jones, 1997

Albrecht, 1983, Software function, source lines of code, and development effort prediction, IEEE Transactions Software Engineering, SE-9, 639, 10.1109/TSE.1983.235271

Rakitin, 2001

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.

Porter, 1995, Comparing detection methods for software requirements inspections: a replicated experiment, IEEE Transactions on Software Engineering, 21, 563, 10.1109/32.391380

Shull, 2000, How perspective-based reading can improve requirements inspections, Computer, 33, 73, 10.1109/2.869376

Ross, 2001

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.

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.

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.

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.

Kotler, 2001

Lehmann, 2002

Mintzberg, 1998

Weber, 2003, Requirements engineering in automotive development: experiences and challenges, IEEE Software, 20, 16, 10.1109/MS.2003.1159025

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.

Saaty, 2001

Leffingwell, 2000

Davis, 2003, The art of requirements triage, IEEE Computer, 36, 42, 10.1109/MC.2003.1185216

Simmons, 2004, Requirements triage: what can we learn from a medical approach?, IEEE Software, 21, 86, 10.1109/MS.2004.25

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.

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.

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.

Carlshamre, 2002, Release planning in market-driven software product development: provoking an understanding, Requirements Engineering, 7, 139, 10.1007/s007660200010

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: <http://www.bth.se/fou/Forskinfo.nsf/>, 2003, pp. 47–56.

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.

Zairi, 1999

Hill, 1999

Davis, 1988, A strategy for comparing alternative software development life cycle models, IEEE Transactions on Software Engineering, 14, 1453, 10.1109/32.6190

Kotler, 2002

Davis, 1998, A strategy for comparing alternative software development life cycle models, IEEE Transactions on Software Engineering, 14, 1453, 10.1109/32.6190

Gorchels, 2000

Teece, 2000

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.

1994

Lam, 1998, A case-study of requirements reuse through product families, Annals of Software Engineering, 5, 253, 10.1023/A:1018912105115

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.

Stern, 1998

Cooper, 2001

Bleistein, 2004, Modeling business strategy in e-business systems requirements engineering, 617, 10.1007/978-3-540-30466-1_57

Bleistein, 2006, Validating strategic alignment of organizational IT requirements using goal modeling and problem diagrams, Journal of Systems and Software, 79, 362, 10.1016/j.jss.2005.04.033

Rosenberg, 1982

Davis, 2005

Gorschek, 2006, Requirements abstraction model, Requirements Engineering, 11, 79, 10.1007/s00766-005-0020-7

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.