東華大學圖書館 |

Language: English

Help

回圖書館首頁

手機版館藏查詢

Back

Switch To: Labeled | MARC Mode | ISBD

Eliciting user requirements using ap...

Gonzales, Carol Kernitzki.

Linked to FindBook

Google Book

Amazon

博客來

Eliciting user requirements using appreciative inquiry.

Record Type:	Language materials, printed : Monograph/item
Title/Author:	Eliciting user requirements using appreciative inquiry./
Author:	Gonzales, Carol Kernitzki.
Description:	134 p.
Notes:	Source: Dissertation Abstracts International, Volume: 71-08, Section: B, page: 5091.
Contained By:	Dissertation Abstracts International71-08B.
Subject:	Information Technology. -
Online resource:	http://pqdd.sinica.edu.tw/twdaoapp/servlet/advanced?query=3416912
ISBN:	9781124111919

Eliciting user requirements using appreciative inquiry.
Gonzales, Carol Kernitzki.

Eliciting user requirements using appreciative inquiry. - 134 p.

Source: Dissertation Abstracts International, Volume: 71-08, Section: B, page: 5091.

Thesis (Ph.D.)--The Claremont Graduate University, 2010.

Many software development projects fail because they do not meet the needs of users, are over-budget, and abandoned. To address this problem, the user requirements elicitation process was modified based on principles of Appreciative Inquiry. Appreciative Inquiry, commonly used in organizational development, aims to build organizations, processes, or systems based on success stories using a hopeful vision for an ideal future.

ISBN: 9781124111919Subjects--Topical Terms:

1030799
Information Technology.

Eliciting user requirements using appreciative inquiry.
LDR:03509nam 2200313 4500 001 1399876
005 20110930095856.5
008 130515s2010 ||||||||||||||||| ||eng d
020 $a 9781124111919
035 $a (UMI)AAI3416912
035 $a AAI3416912
040 $a UMI $c UMI
100 1 $a Gonzales, Carol Kernitzki. $3 1678888
245 1 0 $a Eliciting user requirements using appreciative inquiry.
300 $a 134 p.
500 $a Source: Dissertation Abstracts International, Volume: 71-08, Section: B, page: 5091.
500 $a Adviser: Gondy Leroy.
502 $a Thesis (Ph.D.)--The Claremont Graduate University, 2010.
520 $a Many software development projects fail because they do not meet the needs of users, are over-budget, and abandoned. To address this problem, the user requirements elicitation process was modified based on principles of Appreciative Inquiry. Appreciative Inquiry, commonly used in organizational development, aims to build organizations, processes, or systems based on success stories using a hopeful vision for an ideal future.
520 $a Spanning five studies, Appreciative Inquiry was evaluated for its effectiveness with eliciting user requirements. In the first two cases, it was compared with traditional approaches with end-users and proxy-users. The third study was a quasi-experiment comparing the use of Appreciative Inquiry in different phases of in the software development cycle. The final two case studies combined all lessons learned using Appreciative Inquiry, with multiple case studies to gain additional understanding for the requirements gathered during various project phases. Each study evaluated the requirements gathered, developer and user attitudes, and the Appreciative Inquiry process itself. Requirements were evaluated for the quantity and their type regardless of whether they were implemented or not. Attitudes were evaluated for process feedback, as well as requirements and project commitment. The Appreciative Inquiry process was evaluated with differing groups, projects, and project phases to determine how and when it is best applied. Potentially interceding factors were also evaluated including: team effectiveness, emotional intelligence, perceived stress, the experience of the facilitator, and the development project type itself.
520 $a Appreciative Inquiry produced positive results for the participants, the requirements obtained, and the general requirements eliciting-process. Appreciative Inquiry demonstrated benefits to the requirements gathered by increasing the number of unique requirements as well as identifying more quality-based (nonfunctional) and forward-looking requirements. It worked well with defined projects, when there was time for participants to reflect on the thought-provoking questions, structured questions and extra time to facilitate the extraction and translation of requirements, and a knowledgeable interviewer. The participants (end-users and developers) expressed improved vision and confidence. End-users participated consistently with immediate buy-in and enthusiasm, especially those users who were technically-inhibited. Development teams expressed improved confidence, and improved user communication and understanding.
590 $a School code: 0047.
650 4 $a Information Technology. $3 1030799
650 4 $a Sociology, Organizational. $3 1018023
650 4 $a Information Science. $3 1017528
690 $a 0489
690 $a 0703
690 $a 0723
710 2 $a The Claremont Graduate University. $3 1017403
773 0 $t Dissertation Abstracts International $g 71-08B.
790 1 0 $a Leroy, Gondy, $e advisor
790 $a 0047
791 $a Ph.D.
792 $a 2010
856 4 0 $u http://pqdd.sinica.edu.tw/twdaoapp/servlet/advanced?query=3416912