An empirical study identifying high perceived value requirements engineering practices

Advances in Information Systems Development: Bridging the Gap Between Academia and Industry

Volumn 1, Issue , 2006, Pages 731-743

  Niazi, Mahmood ^a,b   Cox, Karl A ^a,b   Verner, June M ^a,b  

^a CSIRO   (Australia)

^b UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

EID: 84874021083     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1007/978-0-387-36402-5_63     Document Type: Conference Paper

References (22)

1. Sommerville I, Sawyer P (1997) Requirements Engineering - A good Practice Guide. Wiley
2. Neill CJ, Laplante PA (2003) Requirements Engineering: State of the Practice. IEEE Software November/December, pp 40-45
3. Hall T, Beecham S, Rainer A (2002) Requirements Problems in Twelve Software Companies: An Empirical Analysis. IEE Proc Software, pp 153-160
4. Davis A, Hickey A (2002) Requirements Researchers: Do We Practice What We Preach? Requirements Engineering Journal, vol 7, pp 107-111
5. Wiegers KE (2003) Software Requirements, Second Edition. Microsoft Press, Redmond WA
6. Sommerville I, Jane R (2005) An Empirical Study of Industrial Requirements Engineering Process Assessment and Improvement. ACM Transactions on Software Engineering and Methodology, vol 14, no 1, pp 85-117
7. Sommerville I, Sawyer P, Viller S (1997) Requirements Process Improvement Through the Phased Introduction of Good Practice. Software ProcessImprovement and Practice, vol 3, pp 19-34
8. Sommerville I, Sawyer P, Villcr S (1998) Improving the Requirements Process. Fourth International Workshop on Requirements Engineering: Foundation of Software Quality, pp 71-84
9. Niazi M, Shastry S (2003) Role of Requirements Engineering in Software Development Process: An empirical study. IEEE International Multi-Topic Conference (INMIC03), pp 402-407
10. Rainer A, Hall T (2002) Key Success Factors for Implementing Software Process Improvement: a Maturity-Based Analysis. Journal of Systems & Software, vol 62, pp 71-84
11. Niazi M, Wilson D, Zowghi D (2005) A Maturity Model for the Implementation of Software Process Improvement: An empirical study. Journal of Systems and Software, vol 74, no 2, pp 155-172
12. Niazi M, Wilson D, Zowghi D (2005) A Framework for Assisting the Design of Effective Software Process Improvement Implementation Strategies. Accepted for publication: Journal of Systems and Software
13. Verner J, M EW (2005) In-house Software Development: What Software Project Management Practices Lead to Success? IEEE Software, vol 22, no 1, pp 86-93
14. Verner J, Cox K, Bleistein S, Cerpa N (2005) Requirements Engineering and Software Project Success: An Industrial Survey in Australia and the US. Australian Journal of Information Systems (to appear Sept 2005)
15. Jackson M (1995) Software Requirements and Specifications. AddisonWesley/ACM Press
16. Luftman J, Maclean E (2004) Key Issues for IT Executives. MIS Quarterly Executive, vol 3, pp 89-104
17. Alexander I, Maiden NE (2004) Scenarios, Stories, Use Cases. Wiley
18. Carroll JE (1995) Scenario-Based Design: Envisioning Work and Technology in System Development. Wiley
19. Kamsties E, Hormann K, Schlich M (1998) Requirements Engineering in Small and Medium Enterprises. Requirements Engineering, vol 3, no 2, pp 84-90
20. Briand L, Wust J, Lounis H (2001) Replicated Case Studies for Investigating Quality Factors in Object Oriented Designs. Empirical Software Engineering, vol 6, no 1, pp 11-58
21. Niazi M (2005) An Instrument to Measure the Maturity of Requirements Engineering Process. PROFES. Oulu Finland
22. Regnell B, Runeson P, Thelin T (2000) Are the Perspectives Really Different-Further Experimentation on Scenario-Based Reading of Requirements. Empirical Software Engineering, vol 5, no 4, pp 331-356