{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,10,21]],"date-time":"2025-10-21T00:44:56Z","timestamp":1761007496238,"version":"build-2065373602"},"reference-count":54,"publisher":"Wiley","issue":"1","license":[{"start":{"date-parts":[[2009,6,1]],"date-time":"2009-06-01T00:00:00Z","timestamp":1243814400000},"content-version":"vor","delay-in-days":517,"URL":"http:\/\/onlinelibrary.wiley.com\/termsAndConditions#vor"}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["Proc of Assoc for Info"],"published-print":{"date-parts":[[2008,1]]},"abstract":"<jats:title>Abstract<\/jats:title><jats:p>This paper provides an overview of the existing research on information behavior (IB) in the practice of software requirements engineering (RE) and the research which, although it does not refer to IB or to RE by name, addresses the concepts and theories of one within the framework of the other. The paper begins with operational definitions of the terms \u201crequirements,\u201d \u201crequirements engineering,\u201d \u201cinformation behavior,\u201d and \u201cinformation behavior in requirements engineering\u201d to set the framework for this analysis. A number of authors have written extensively on theories of IB. Similarly, although perhaps less well known to those in the Library and Information Science (LIS) community, many terms exist for the field and practices of software requirements elicitation, documentation and maintenance, herein referred to as RE. Although RE is still a relatively young field, having emerged from computer science and software engineering in only the past 20\u201030 years, research in the field is diverse and growing. However, little research has taken place specifically on IB in RE. In some cases, research on IB and RE progresses on parallel paths, even utilizing the same terminology, without a recognition of the other community's work. The paper follows the operational definitions with a review of the collective set of literature covering IB in RE and that which reflects IB in RE but does not label it as such. The next section includes a discussion of what the reviewed literature reveals about the state of research and practice in this area, and the paper concludes with suggestions for future research.<\/jats:p>","DOI":"10.1002\/meet.2008.1450450273","type":"journal-article","created":{"date-parts":[[2009,6,3]],"date-time":"2009-06-03T09:48:20Z","timestamp":1244022500000},"page":"1-11","source":"Crossref","is-referenced-by-count":0,"title":["Information behavior in requirements engineering: An initial review of the research"],"prefix":"10.1002","volume":"45","author":[{"given":"Mike","family":"Alexander","sequence":"first","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"311","published-online":{"date-parts":[[2009,6,3]]},"reference":[{"issue":"4","key":"e_1_2_6_2_1","first-page":"225","article-title":"Institutional circuitry: Thinking about the forms and uses of information","volume":"14","author":"Agre Philip E.","year":"1995","journal-title":"Information, Technology and Libraries"},{"key":"e_1_2_6_3_1","first-page":"266","volume-title":"Proceedings of the 14th IEEE international requirements engineering conference (RE'06)","author":"Akkermans H.","year":"2006"},{"key":"e_1_2_6_4_1","doi-asserted-by":"publisher","DOI":"10.1108\/EUM0000000006518"},{"key":"e_1_2_6_5_1","first-page":"44","volume-title":"Theories of information behavior","author":"Belkin Nicholas J.","year":"2005"},{"volume-title":"The mythical man\u2010month: Essays on software engineering","year":"1995","author":"Brooks Frederick P.","key":"e_1_2_6_6_1"},{"key":"e_1_2_6_7_1","first-page":"285","volume-title":"2007 future of software engineering (May 23\u201325, 2007). International conference on software engineering","author":"Cheng B. H.","year":"2007"},{"volume-title":"Writing effective use cases","year":"2000","author":"Cockburn Alistair.","key":"e_1_2_6_8_1"},{"volume-title":"About face 2.0: The essentials of interaction design","year":"2003","author":"Cooper Alan","key":"e_1_2_6_9_1"},{"key":"e_1_2_6_10_1","first-page":"171","volume-title":"Annual review of information science and technology","author":"Davenport Elisabeth","year":"2002"},{"key":"e_1_2_6_11_1","doi-asserted-by":"publisher","DOI":"10.2307\/4132312"},{"key":"e_1_2_6_12_1","doi-asserted-by":"publisher","DOI":"10.1145\/602421.602458"},{"volume-title":"Theories of information behavior","year":"2005","author":"Fisher Karen E.","key":"e_1_2_6_13_1"},{"key":"e_1_2_6_14_1","doi-asserted-by":"publisher","DOI":"10.1007\/s007660050016"},{"key":"e_1_2_6_15_1","doi-asserted-by":"publisher","DOI":"10.1007\/s00766-004-0204-6"},{"volume-title":"Principles of software engineering management","year":"1988","author":"Gilb Tom.","key":"e_1_2_6_16_1"},{"key":"e_1_2_6_17_1","doi-asserted-by":"publisher","DOI":"10.1068\/a34197"},{"key":"e_1_2_6_18_1","unstructured":"Goguen Jospeh A.(1992).Requirements engineering as the reconciliation of technical and social issues.Tech report. Cambridge UK: Centre for Requirements and Foundations Oxford University Computing Lab."},{"volume-title":"Requirements by collaboration: Workshops for defining needs","year":"2002","author":"Gottesdiener Ellen.","key":"e_1_2_6_19_1"},{"key":"e_1_2_6_20_1","doi-asserted-by":"publisher","DOI":"10.1007\/s00766-004-0196-2"},{"key":"e_1_2_6_21_1","doi-asserted-by":"publisher","DOI":"10.1049\/ip-sen:20020694"},{"key":"e_1_2_6_22_1","doi-asserted-by":"publisher","DOI":"10.1002\/asi.20620"},{"volume-title":"Customer\u2010centered products: Creating successful products through smart requirements management","year":"2001","author":"Hooks Ivy F.","key":"e_1_2_6_23_1"},{"issue":"3","key":"e_1_2_6_24_1","article-title":"Managing tacit knowledge in organizations","volume":"8","author":"Irick Michael L.","year":"2007","journal-title":"Journal of Knowledge Management Practice"},{"key":"e_1_2_6_25_1","unstructured":"JESSE. Listserv discussion on information behavior December 1999. Retrieved 11\/26\/2007 fromhttp:\/\/listserv.utk.edu\/cgi\u2010bin\/wa?A1=ind9912&L=iesse."},{"key":"e_1_2_6_26_1","doi-asserted-by":"publisher","DOI":"10.1002\/(SICI)1097-4571(199106)42:5<361::AID-ASI6>3.0.CO;2-#"},{"key":"e_1_2_6_27_1","doi-asserted-by":"publisher","DOI":"10.1109\/RE.2007.55"},{"volume-title":"The usability engineering lifecycle: A practitioner's handbook for user interface design","year":"1999","author":"Mayhew Deborah J.","key":"e_1_2_6_28_1"},{"key":"e_1_2_6_29_1","first-page":"43","volume-title":"Annual Review of Information Science and Technology","author":"Pettigrew Karen","year":"2001"},{"key":"e_1_2_6_30_1","doi-asserted-by":"publisher","DOI":"10.7208\/chicago\/9780226668253.001.0001"},{"key":"e_1_2_6_31_1","doi-asserted-by":"publisher","DOI":"10.1145\/958160.958198"},{"volume-title":"Mastering the requirements process","year":"2006","author":"Robertson Suzanne","key":"e_1_2_6_32_1"},{"key":"e_1_2_6_33_1","doi-asserted-by":"publisher","DOI":"10.1108\/09593840210444773"},{"key":"e_1_2_6_34_1","doi-asserted-by":"publisher","DOI":"10.1007\/s00766-007-0043-3"},{"key":"e_1_2_6_35_1","doi-asserted-by":"publisher","DOI":"10.1086\/517840"},{"key":"e_1_2_6_36_1","unstructured":"Seilevel.(2007a). Messageboard discussion on requirements professionals' titles July 2007. Retrieved 11\/26\/2007 fromhttp:\/\/requirements.seilevel.com\/messageboard\/showthread.php?t=607."},{"key":"e_1_2_6_37_1","unstructured":"Seilevel.(2007b). Messageboard discussion on the use of academic sources of requirements information September 2007. Retrieved 11\/29\/2007 fromhttp:\/\/requirements.seilevel.com\/messageboard\/showthread.php?t=668."},{"key":"e_1_2_6_38_1","doi-asserted-by":"publisher","DOI":"10.1109\/52.268951"},{"volume-title":"New directions in human information behavior","year":"2005","author":"Spink Amanda","key":"e_1_2_6_39_1"},{"key":"e_1_2_6_40_1","unstructured":"Standish Group. (1994). CHAOS report. Retrieved 11\/27\/2007 fromhttp:\/\/www.standishgroup.com\/sampleresearch\/chaos 1994 2.php."},{"key":"e_1_2_6_41_1","doi-asserted-by":"publisher","DOI":"10.1007\/BF01236426"},{"key":"e_1_2_6_42_1","doi-asserted-by":"publisher","DOI":"10.1108\/00220410510578023"},{"key":"e_1_2_6_43_1","doi-asserted-by":"publisher","DOI":"10.5860\/crl_29_03_178"},{"key":"e_1_2_6_44_1","doi-asserted-by":"publisher","DOI":"10.1145\/310930.310984"},{"key":"e_1_2_6_45_1","first-page":"328","volume-title":"Theories of information behavior","author":"Tuominen Kimmo","year":"2005"},{"issue":"2","key":"e_1_2_6_46_1","article-title":"Bridging information requirements and information needs assessment: Do scenarios and vignettes provide a link?","volume":"6","author":"Urquhart Christine.","year":"2001","journal-title":"Information Research"},{"issue":"3","key":"e_1_2_6_47_1","article-title":"The role of motivation and risk behaviour in software development success","volume":"7","author":"Walsh Kenneth R.","year":"2002","journal-title":"Information Research"},{"issue":"1","key":"e_1_2_6_48_1","first-page":"139","article-title":"Communities of practice: The organizational frontier","volume":"78","author":"Wenger Etienne C.","year":"2000","journal-title":"Harvard Business Review"},{"volume-title":"Software requirements: Practical techniques for gathering and managing requirements throughout the product development cycle","year":"2003","author":"Wiegers Karl Eugene.","key":"e_1_2_6_49_1"},{"volume-title":"More about software requirements: Thorny issues and practical advice","year":"2006","author":"Wiegers Karl Eugene.","key":"e_1_2_6_50_1"},{"volume-title":"Essential system requirements: A practical guide to event\u2010driven methods","year":"2000","author":"Wiley Bill.","key":"e_1_2_6_51_1"},{"key":"e_1_2_6_52_1","doi-asserted-by":"publisher","DOI":"10.1016\/S0306-4573(97)00028-9"},{"key":"e_1_2_6_53_1","doi-asserted-by":"publisher","DOI":"10.28945\/576"},{"issue":"12","key":"e_1_2_6_54_1","first-page":"4","article-title":"Twelve requirements basics for project success","volume":"19","author":"Young Ralph R.","year":"2006","journal-title":"CrossTalk"},{"volume-title":"Death march: The complete software developer's guide to surviving \u201dmission impossible\u201dprojects","year":"1999","author":"Yourdon Edward.","key":"e_1_2_6_55_1"}],"container-title":["Proceedings of the American Society for Information Science and Technology"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/api.wiley.com\/onlinelibrary\/tdm\/v1\/articles\/10.1002%2Fmeet.2008.1450450273","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/api.wiley.com\/onlinelibrary\/tdm\/v1\/articles\/10.1002%2Fmeet.2008.1450450273","content-type":"application\/pdf","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/asistdl.onlinelibrary.wiley.com\/doi\/pdf\/10.1002\/meet.2008.1450450273","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,10,20]],"date-time":"2025-10-20T13:39:21Z","timestamp":1760967561000},"score":1,"resource":{"primary":{"URL":"https:\/\/asistdl.onlinelibrary.wiley.com\/doi\/10.1002\/meet.2008.1450450273"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2008,1]]},"references-count":54,"journal-issue":{"issue":"1","published-print":{"date-parts":[[2008,1]]}},"alternative-id":["10.1002\/meet.2008.1450450273"],"URL":"https:\/\/doi.org\/10.1002\/meet.2008.1450450273","archive":["Portico"],"relation":{},"ISSN":["0044-7870","1550-8390"],"issn-type":[{"type":"print","value":"0044-7870"},{"type":"electronic","value":"1550-8390"}],"subject":[],"published":{"date-parts":[[2008,1]]}}}