BibSonomyburst/bibtex/5d142b0a63adf6da6867027297ccf403BibSonomy RSS feed for /bibtex/5d142b0a63adf6da6867027297ccf4032012-02-17T04:03:15+01:00http://www.bibsonomy.org/bibtex/23a8e3815d7b85873f84995e0cb1cf067/dblpdblp2009-03-23T00:00:00+01:00dblp <span class="authorEditorList"><a href="/author/Aranda">Jorge Aranda</a>, <a href="/author/Easterbrook">Steve M. Easterbrook</a>, and <a href="/author/Wilson">Greg Wilson</a> </span><em>RE, </em><em>page 39-48. </em><em>IEEE, </em>(<em>2007</em>)Mon Mar 23 00:00:00 CET 2009REconf/re/200739-48Requirements in the wild: How small companies do it.2007dblp dblphttp://www.bibsonomy.org/bibtex/2c3244caa4fce0f2f3b78b9abb247aa9e/mschubermschuber2008-07-22T15:52:59+02:002007 requirement software <span class="authorEditorList"><a href="/author/Aranda">J. Aranda</a>, <a href="/author/Easterbrook">S. Easterbrook</a>, and <a href="/author/Wilson">G. Wilson</a> </span><em>Requirements Engineering Conference, 2007. RE &#039;07. 15th IEEE International, </em><em>page 39-48. </em>(<em>2007</em>)Tue Jul 22 15:52:59 CEST 2008Requirements Engineering Conference, 2007. RE '07. 15th IEEE International39-48Requirements in the wild: How small companies do it20072007 requirement software Small companies form a large part of the software industry, but have mostly been overlooked by the requirements engineering research community. We know very little about the techniques these companies use to elicit and track requirements and about their contexts of operations. This paper presents preliminary results from an ongoing exploratory case study of requirements management in seven small companies, which found that (a) successful small companies exhibit a huge diversity of requirements practices that work well enough for their contexts; (b) these companies display strong cultural cohesion; (c) the principal of the company tends to retain control of the requirements processes long after other tasks have been delegated; and (d) the evidence rejects the simplistic view of a current "software crisis", as requirements errors for these companies, though problematic, are rarely catastrophic. We develop a number of hypotheses to explain these findings.Welcome to IEEE Xplore 2.0: Requirements in the wild: How small companies do ithttp://www.bibsonomy.org/bibtex/2b3756822eb487d407b99ffec63d3e3c7/neilernstneilernst2008-01-04T23:04:23+01:00requirements small <span class="authorEditorList"><a href="/author/Aranda">J. Aranda</a>, <a href="/author/Easterbrook">S. M. Easterbrook</a>, and <a href="/author/Wilson">G. Wilson</a> </span><em>International Conference on Requirements Engineering, </em><em>Delhi, India, </em>(<em>September 2007</em>)<em>Most innovative paper award . </em>Fri Jan 04 23:04:23 CET 2008Delhi, IndiaInternational Conference on Requirements EngineeringSeptemberMost innovative paper awardRequirements in the wild: How small companies do it2007requirements small Small companies form a large part of the software industry, but have mostly been overlooked by the requirements engineering research community. We know very little about the techniques these companies use to elicit and track requirements and about their contexts of operations. This paper presents preliminary results from an ongoing exploratory case study of requirements management in seven small companies, which found that (a) successful small companies exhibit a huge diversity of requirements practices that work well enough for their contexts; (b) these companies display strong cultural cohesion; (c) the principal of the company tends to retain control of the requirements processes long after other tasks have been delegated; and (d) the evidence rejects the simplistic view of a current “software crisis”, as requirements errors for these companies, though problematic, are rarely catastrophic. We develop a number of hypotheses to explain these findings.