Defining a requirements process improvement model

Software Quality Journal

Volumn 13, Issue 3, 2005, Pages 247-279

  Beecham, Sarah ^a   Hall, Tracy ^a   Rainer, Austen ^a  

^a UNIVERSITY OF HERTFORDSHIRE   (United Kingdom)

Author keywords

Goal question metric; RE process improvement; Requirements engineering (RE); Requirements engineering process; Software Capability Maturity Model (SW CMM); Software process improvement

Indexed keywords

COMPUTER AIDED SOFTWARE ENGINEERING; SEEBECK EFFECT; SOFTWARE DESIGN;

GOAL-QUESTION-METRIC; PROCESS IMPROVEMENT; REQUIREMENTS ENGINEERING PROCESS; SOFTWARE CAPABILITY MATURITY MODELS; SOFTWARE PROCESS IMPROVEMENT;

REQUIREMENTS ENGINEERING;

EID: 23744501762     PISSN: 09639314     EISSN: 15731367     Source Type: Journal    
DOI: 10.1007/s11219-005-1752-9     Document Type: Article

References (76)

1. Arisholm, E. and Sjoberg, D.I.K. 2000. Towards a framework for empirical assessment of changeability decay, Journal of Systems and Software (53): 3-14.
2. Basili, V.R. 1995. Measurement frameworks, Software Quality Assurance and Measurement: A Worldwide Perspective, eds. N. Fenton, R. Whitty and Y. Iizuka. London, International Thomson Computer Press.
3. Basili, V.R. and Rombach, H.D. 1988. The tame project: Towards improvement-oriented software environments, IEEE Transactions on Software Engineering 14(6): 758-773.
4. Beecham, S., Hall, T., Britton, C., Cottee, M., and Rainer, A. 2005. Using an expert panel to validate a requirements software process improvement model, Journal of Systems and Software (Accepted and In press).
5. Beecham, S., Hall, T., and Rainer, A., 2003a. Building a Requirements Process Improvement Model, Hatfield, University of Hertfordshire.
6. Beecham, S., Hall, T., and Rainer, A. 2003b. Defining a Requirements Process Improvement Model, Hatfield, University of Hertfordshire.
7. Beecham, S., Hall, T., and Rainer, A. 2003c. Software process improvement problems in 12 software companies: An empirical analysis, Empirical Software Engineering 8(1): 7-42.
8. Beecham, S., Hall, T., and Rainer, A. 2004. Developing a RE Process Improvement Model, EuroSPI 2004, Trondheim, Norway.
9. Boehm, B. 2001. Using Win-Win for Requirements Negotiation: A Mini Tutorial, Imperial College, London.
10. Britton, C. 2000. Object-Oriented System Development: A Gentle Introduction, London, McGraw-Hill, New York.
11. Brodman, J.G. and Johnson, D.L. 1994. What Small Businesses and Small Organisations Say About the CMM. 16th International Conference on Software Engineering, Sorrento, Italy, IEEE.
12. Burnstein, I., Suwannasart, T., and Carlson, C. 1996. Developing a testing maturity model, Part II. CrossTalk The Journal of Defense Software Engineering.
13. Christie, A.M. 1999. Simulation in support of CMM-based process improvement, Journal of Systems and Software 46(2-3): 107-112.
14. CMMI 2001. Capability Maturity Model®. Integration (CMMI SM), Version 1.1, Software Engineering Institute.
15. Cresswell, J. 1998. Quality Inquiry and Research Design: Choosing Among Five Traditions. Sage Publications, Thousand Oaks.
16. Curtis, B., Hefley, W.E., Miller, S., and Konrad, M. 1995. People capability maturity model. Pittsburgh, PA, Software Engineering Institute, Carnegie Mellon University.
17. Daskalantonakis, M.K. 1994. Achieving higher sei levels, IEEE Software 11(4).
18. David, A. 2000. Models implementation: A state of the art, European Journal of operational Research 134: 459-480.
19. Davis, A. 1988. A taxonomy for the Early stages of the software development life cycle, Journal of Systems and Software 297-311.
20. Davis, A., Overmyer, S., Jordan, K., Caruso, J., Dandashi, F., Dinh, A., Kincaid, G., Ledeboer, G., Reynolds, P., Sitaram, P., Ta, A., and Theofanos, M. 1993. Identifying and measuring quality in a software requirements specification, In Proceedings of the First International Software Metrics Symposium.
21. Deming, W.E. 1982. Quality, Productivity, and Competitive Position. Cambridge, MA, Massachusetts Institute of Technology Center for Advanced Engineering Study.
22. Dooley, K., Subra A., and Anderson, J. 2001. Maturity and its impact on new product development project performance, Research in Engineering Design 13(1): 23-29.
23. Dorfman, M. and Thayer, R.H. 1997. Software Engineering, IEEE Computer, Los Alamitos, CA. Society Press.
24. El Emam, K. and Madhavji, N.H. 1995a. A Field Study of Requirements Engineering Practices in Information Systems Development. Second IEEE International Symposium on Requirements Engineering, IEEE Computer Society Press.
25. El Emam, K. and Madhavji, N.H. 1995b. The Reliability of Measuring Organizational Maturity, John Wiley & Sons.
26. El Emam, K., Quintin S., and Madhavji, N.H. 1996. User participation in the requirements engineering process: An empirical study, Requirements Engineering Journal 1(1): 4-26.
27. Fayad, M.E. 1997. Software development process: A necessary evil, Communications of the ACM 40(9): 101-103.
28. Gause, D.C. and Weinberg, G.M. 1989. Exploring Requirements: Quality Before Design, New York, NY, Dorset House Publishing.
29. Gilb, T. 1996. Level 6: Why we can't get there from here, IEEE Software 13(1): 97-98, 103.
30. Gross, D. and Yu, E. 2001. From non-functional requirements to design through patterns, Requirements Engineering (6): 18-36.
31. Hackos, J.T. 1997. From theory to practice: Using the information process maturity model as a tool for strategic planning, Technical Communication (44): 369-381.
32. Hall, T., Beecham, S. and Rainer, A. 2002a. Requirements Problems in Twelve Software Companies: An Empirical Analysis. EASE 2002, 6th International Conference on Empirical Assessment and Evaluation in Software Engineering, Keele University, Staffordshire, UK.
33. Hall, T., Beecham, S., and Rainer, A. 2002b. Requirements Problems in Twelve Software Companies: An Empirical Analysis. IEE Proceedings for Software.
34. Hayes, W. and Zubrow, D. 1995. Moving on Up: Data and Experience Doing CMM-Based Process Improvement, Pittsburgh, Carnegie Mellon University.
35. Hofmann, H.F. and Lehner, F. 2001. Requirements engineering as a success factor in software projects, IEEE Software: 58-66.
36. Humphrey, W.S. 1989. Managing the Software Process. Addison-Wesley Publishing Company, Inc, Reading, Massachusetts, USA.
37. Humphrey, W.S. 1997. Introduction to the Personal Software. Process, Addison-Wesley, Reading, M.A.
38. Humphrey, W.S. 2000. Introduction to the Team Software Process, Addison-Wesley, Reading, M.A.
39. Humphrey, W.S. 2002. Three process perspectives: organizations, teams, and people, Annuls of Software Engineering 14: 39-72.
40. Ibanez, M. and Rempp, H. 1996. European User Survey Analysis, ESPITI Project Report. 2003.
41. IEEE 1998. IEEE guide to software requirements specification, IEEE Standard. Piscataway, N.J., IEEE Press. pp. 830-1998.
42. IEEE 1999. IEEE Standards Software Engineering, 1999 Edition. Volume One: Customer and Terminology Standards. New York, USA, The Institute of Electrical and Electronics Engineers, Inc.
43. Jalote, P. 1997. An Integrated Approach to Software Engineering: Second edition, New York, Springer-Verlag.
44. Lauesen, S. and O. Vinter 2001. Preventing requirement defects: An experiment in process improvement, Requirements Engineering Journal 6(1): 37-50.
45. Lindland, O.V., Sindre, G., and Solvberg, A. 1994. Understanding quality in conceptual modeling, IEEE Software 11 (2): 42-49.
46. Loucopoulos, P. and V. Karakostas 1995. System Requirements Engineering, London, UK, McGraw-Hill Book Company Europe.
47. Lubars, M., Potts, C., and Richter, C. 1993. A review of the state of the practice in requirements modeling, In Proceedings of the IEEE International Symposium on Requirements Engineering, San Diego, CA.
48. Madhavji, N.H. 1991. The process cycle, Software Engineering Journal 6(5): 234-242.
49. McFeeley, B. 1996. IDEAL: A User's Guide for Software Process Improvement. Pittsburgh, PE, USA, Software Engineering Instutute, Carnegie Mellon University.
50. Moynihan, T. 2000. Coping with requirements-uncertainty: The theories-of-action of experienced IS/software project managers, Journal of Systems and Software (53): 99-109.
51. Neissink, F., Clerc, V., and Vliet, H. 2002. The IT Service Capability Maturity Model. Utrecht, Software Engineering Research Centre: 127.
52. Ngwenyama, O. and Neilsen, P. 2003. Competing values in software process improvement: an assumption analysis of cmm from an organizational culture perspective, IEEE Transactions on Engineering Management 50(1): 100-112.
53. Paulk, M.C. and Chrissis, M.B. 2000. The November 1999 High Maturity Workshop. Carnegie Mellon Uni, Software Engineering Institute.
54. Paulk, M.C., Weber, C.V., Curtis, B., and Chrissis, M.B. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process. Reading, Massachusetts, Addison Wesley Longman, Inc.
55. Perry, D.E., Staudenmayer, N.A., and Votta, L.G. 1994. People, organizations and process improvement, IEEE Software 11 (4): 36-45.
56. Peters, J. and Pedrycz, W. 2000. Software Engineering: An Engineering Approach, John Wiley & Sons, New York.
57. Pfleeger, S.L. 1995. Maturity, models, and goals: How to build a metrics plan, Journal of Systems and Software 31(2): 143-155.
58. Potter, N. and Sakry, M. 2001. Practical CMM, Software Development. 2002.
59. Pressman, R. 2001. Software Engineering 5th Edition, McGraw Hill.
60. Reifer, D.J. 2000. The CMMI: it's formidable, Journal of Systems and Software 50: 97-98.
61. Rifkin, S. 2001. Why Software Process Innovations Are Not Adopted. IEEE Software.
62. Robertson, S. and Robertson, J. 1999. Mastering the Requirements Process, Addison-Wesley.
63. Rogoway, P. 1998. How to Reap the Business Benefit from SPI: Adding SPICE while preserving the CMM (Motorola), SPI NEWSPAPER. European Software Process Improvement. SPI and Assessments. 2003.
64. Rossi, S. 1999. Moving Towards Modelling Oriented Software Process Engineering: A Shift from Descriptive, to Prescriptive Process Modelling. International Conference on Product Focused Software Process Improvement, Oulu, Finland, Technical Research Centre of Finland ESPOO 1999.
65. Sawyer, P., Sommerville, I., and Viller, S. 1997. Requirements process improvement through the phased introduction of good practice, Software. Process Improvement and Practice 3(1).
66. SEI 1996. A Description of the Systems Engineering Capability Maturity Model Appraisal Method Version 1.1. Pittsburgh, USA, Software Engineering Institute, Carnegie Mellon University.
67. SEI 2002. Process maturity profile of the software community, Software Engineering Institute. Pittsburgh, PA, Carnegie-Mellon Univ.
68. Solingen, R.V. and Berghout, E. 1999. The Goal/Question/Metric Method: A Practical Guide for Quality Improvement of Software Development, Maidenhead, UK, McGraw-Hill Publishing Company.
69. Sommerville, I. 2001. Software Engineering, Wokingham, Addison-Wesley Publishing Company.
70. Sommerville, I. and Sawyer, P. 1997. Requirements Engineering A Good Practice Guide, Chichester, John Wiley & Sons Ltd.
71. StandishGroup 1995. Chaos Report.
72. Thayer, R.H. and Dorfman, M. 1990. System and Software Requirements Engineering, Los Alamitos, CA, IEEE Computer Society Press.
73. Watkins, R. and Neal, M. 1994. Why and how of requirements tracing, IEEE Software(July): 104-106.
74. Wiegers, K. 1998a. Molding the CMM to your organization, Software Development 6(5).
75. Wiegers, K. 1998b. Read my lips: No new models!, IEEE Software 15(5).
76. Yu, E.S.K. and Mylopoulos, J. 1997. Modelling Organizational Issues for Enterprise Integration, International Conference on Enterprise Integration and Modelling Technology, Turin, Italy.