How Artifacts Support and Impede Requirements Communication
暂无分享,去创建一个
[1] Per Runeson,et al. Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.
[2] Björn Regnell,et al. Are you biting off more than you can chew? A case study on causes and effects of overscoping in large-scale software engineering , 2012, Inf. Softw. Technol..
[3] Bernd Brügge,et al. Software Cinema-Video-based Requirements Engineering , 2006, 14th IEEE International Requirements Engineering Conference (RE'06).
[4] Barbara Paech,et al. A proposal for enhancing user-developer communication in large IT projects , 2012, 2012 5th International Workshop on Co-operative and Human Aspects of Software Engineering (CHASE).
[5] Daniela E. Damian,et al. Information Brokers in Requirement-Dependency Social Networks , 2008, 2008 16th IEEE International Requirements Engineering Conference.
[6] Kenneth M. Anderson,et al. Using Open Hypermedia to Support Information Integration , 2001, OHS-7/SC-3/AH-3.
[7] C. Brodsky. The Discovery of Grounded Theory: Strategies for Qualitative Research , 1968 .
[8] Birgit Penzenstadler,et al. Artefact-based requirements engineering: the AMDiRE approach , 2014, Requirements Engineering.
[9] Björn Regnell,et al. Requirements are slipping through the gaps — A case study on causes & effects of communication gaps in large-scale software development , 2011, 2011 IEEE 19th International Requirements Engineering Conference.
[10] Thorsten Keuler,et al. A Non-invasive Approach to Trace Architecture Design, Requirements Specification and Agile Artifacts , 2014, 2014 23rd Australian Software Engineering Conference.
[11] Barbara Paech,et al. State of Practice of User-Developer Communication in Large-Scale IT Projects - Results of an Expert Interview Series , 2014, REFSQ.
[12] João Araújo,et al. Early aspects: a model for aspect-oriented requirements engineering , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.
[13] Helen Sharp,et al. The role of physical artefacts in agile software development: Two complementary perspectives , 2009, Interact. Comput..
[14] A. Strauss,et al. The discovery of grounded theory: strategies for qualitative research aldine de gruyter , 1968 .
[15] Daniela E. Damian,et al. Patterns of continuous requirements clarification , 2014, Requirements Engineering.
[16] Eya Ben Charrada,et al. Identifying outdated requirements based on source code changes , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).
[17] S.E. Sim,et al. Are Use Cases Beneficial for Developers Using Agile Requirements? , 2007, 2007 Fifth International Workshop on Comparative Evaluation in Requirements Engineering.
[18] Jörg Dörr,et al. What you need is what you get!: The vision of view-based requirements specifications , 2012, 2012 20th IEEE International Requirements Engineering Conference (RE).
[19] Ilka Philippow,et al. A Survey on Usage Scenarios for Requirements Traceability in Practice , 2013, REFSQ.
[20] S.J. Morris,et al. On Requirements Visualization , 2007, Second International Workshop on Requirements Engineering Visualization (REV 2007).
[21] Jane Huffman Hayes,et al. Improving requirements tracing via information retrieval , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..
[22] David Benyon,et al. How Stories Capture Interactions , 1999, INTERACT.
[23] Charles Wallace,et al. A tale of two projects: A pattern based comparison of communication strategies in student software development , 2013, 2013 IEEE Frontiers in Education Conference (FIE).
[24] JaatunMartin Gilje,et al. Agile Software Development , 2002, Comput. Sci. Educ..
[25] M. Murdocca,et al. $$L^p({\mathbb{R }}^n)$$Lp(Rn)-continuity of translation invariant anisotropic pseudodifferential operators: a necessary condition , 2012, 1210.0694.