Naming the pain in requirements engineering
暂无分享,去创建一个
G. Ruhe | M. Oivo | M. Felderer | R. Spínola | Marie-Therese Christiansson | R. Wieringa | T. Männistö | R. Prikladnicki | B. Penzenstadler | A. Vetrò | J. Vara | P. Mafra | A. Schekelmann | A. Tuzcu | M. Nayabi | S. Wagner | M. Kalinowski | T. Conte | D. Greer | Lassenius | Pfahl | S. Sen
[1] Stefan Wagner,et al. Analysing Text in Software Projects , 2016, The Art and Science of Analyzing Software Data.
[2] Michael Felderer,et al. Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil , 2016, SWQD.
[3] Christian Bird,et al. The Art and Science of Analyzing Software Data , 2015, ICSE 2015.
[4] Tayana Conte,et al. Naming the Pain in Requirements Engineering: Comparing Practices in Brazil and Germany , 2015, IEEE Software.
[5] Tayana Conte,et al. Towards Building Knowledge on Causes of Critical Requirements Engineering Problems , 2015, SEKE.
[6] Marjorie M. K. Hlava,et al. Beyond authorship: attribution, contribution, collaboration, and credit , 2015, Learn. Publ..
[7] Ruth Breu,et al. Improvement Methods for Software Requirement Specifications: A Mapping Study , 2014, 2014 9th International Conference on the Quality of Information and Communications Technology.
[8] Daniel Méndez Fernández,et al. In quest for requirements engineering oracles: dependent variables and measurements for (good) RE , 2014, EASE '14.
[9] Stefan Wagner,et al. Naming the pain in requirements engineering: design of a global family of surveys and first results from Germany , 2013, EASE '13.
[10] Guilherme Horta Travassos,et al. Evidence-Based Guidelines to Defect Causal Analysis , 2012, IEEE Software.
[11] Roel Wieringa,et al. Preliminary Survey on Empirical Research Practices in Requirements Engineering , 2012 .
[12] Genaína Nunes Rodrigues,et al. A systematic mapping study on creativity in requirements engineering , 2012, SAC '12.
[13] Stefan Wagner,et al. Field study on requirements engineering: Investigation of artefacts, project parameters, and execution strategies , 2012, Inf. Softw. Technol..
[14] Philippe Kruchten,et al. Using grounded theory to study the experience of software development , 2011, Empirical Software Engineering.
[15] Melanie Birks,et al. Grounded Theory: A Practical Guide , 2011, QMiP Bulletin.
[16] Fei Peng,et al. Why Requirements Engineering Fails: A Survey Report from China , 2010, 2010 18th IEEE International Requirements Engineering Conference.
[17] Abdul Azim Abdul Ghani,et al. Requirements Engineering Problems and Practices in Software Companies: An Industrial Survey , 2009, FGIT-ASEA.
[18] Klaas Sikkel,et al. A systematic mapping study on empirical evaluation of software requirements specifications techniques , 2009, 2009 3rd International Symposium on Empirical Software Engineering and Measurement.
[19] Karl Cox,et al. Empirical study of Sommerville and Sawyer's requirements engineering practices , 2009, IET Softw..
[20] Nannette P. Napier,et al. Combining Perceptions and Prescriptions in Requirements Engineering Process Assessment: An Industrial Case Study , 2009, IEEE Transactions on Software Engineering.
[21] Guilherme Horta Travassos,et al. Towards a Defect Prevention Based Process Improvement Approach , 2008, 2008 34th Euromicro Conference Software Engineering and Advanced Applications.
[22] Tony Gorschek,et al. A practitioner's guide to light weight software process assessment and improvement planning , 2008, J. Syst. Softw..
[23] Tetsuo Tamai,et al. How Does Requirements Quality Relate to Project Success or Failure? , 2007, 15th IEEE International Requirements Engineering Conference (RE 2007).
[24] D. Ross Jeffery,et al. An exploratory study of why organizations do not adopt CMMI , 2007, J. Syst. Softw..
[25] Betty H. C. Cheng,et al. Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).
[26] Natalia Juristo Juzgado,et al. Effectiveness of Requirements Elicitation Techniques: Empirical Results Derived from a Systematic Review , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).
[27] Daniela E. Damian,et al. An Empirical Study of the Complex Relationships between Requirements Engineering Processes and Other Processes that Lead to Payoffs in Productivity, Quality, and Risk Management , 2006, IEEE Transactions on Software Engineering.
[28] Karl Cox,et al. Requirements Engineering and Software Project Success: an industrial survey in Australia and the U.S , 2005, Australas. J. Inf. Syst..
[29] Austen Rainer,et al. Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis , 2003, Empirical Software Engineering.
[30] Bashar Nuseibeh,et al. Requirements engineering: a roadmap , 2000, ICSE '00.
[31] C. Brodsky. The Discovery of Grounded Theory: Strategies for Qualitative Research , 1968 .
[32] Ursula Faber,et al. Requirements Engineering A Good Practice Guide , 2016 .
[33] Daniel Méndez Fernández,et al. Naming the Pain in Requirements Engineering - NaPiRE-Report 2013 , 2013 .
[34] Chris Verhoef,et al. The rise and fall of the Chaos report figures , 2010, IEEE Software.
[35] P. Doody. State of the Practice , 2005, IEEE Softw..
[36] David N. Card,et al. Defect Analysis: Basic Techniques for Management and Learning , 2005, Adv. Comput..
[37] Heikki Kälviäinen,et al. A State-of-the-Practice Survey on Requirements Engineering in Small- and Medium-Sized Enterprises , 2000 .
[38] Steve Easterbrook,et al. Communication Problems in Requirements Engineering: A Field Study , 1996 .