| 翻訳と辞書 |
| Agile software development ： ウィキペディア英語版 |
Agile Software Development is a set of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.The ''Manifesto for Agile Software Development'', also known as the ''Agile Manifesto'', was first proclaimed in 2001, six years after "Agile Methodology" was originally introduced by the preeminent software engineers of the late 1980s and early 1990s. The Manifesto came out of the DSDM Consortium in 1994, although its roots go back to the mid 1980s at DuPont and works by James MartinMartin, James (1991). Rapid Application Development. Macmillan. ISBN 0-02-376775-8. and James Kerr et al.Kerr, James M.; Hunter, Richard (1993). Inside RAD: How to Build a Fully Functional System in 90 Days or Less. McGraw-Hill. ISBN 0-07-034223-7 p.3==History==Incremental software development methods trace back to 1957. In 1974, E. A. Edmonds wrote a paper that introduced an adaptive software development process.Note by Edmonds: I presented these ideas in London in 1970 and first submitted the paper to the Journal ''Computer Aided Design''. It was rejected with the comment "If you don't know what you are going to do before you start you shouldn't start"! Only then did I submit it to ''General Systems''. Concurrently and independently, the same methods were developed and deployed by the New York Telephone Company's Systems Development Center under the direction of Dan Gielan. In the early 1970s, Tom Gilb started publishing the concepts of evolutionary project management (EVO), which has evolved into ''competitive engineering''.(【引用サイトリンク】title=Evolutionary Project Management ) During the mid- to late 1970s, Gielan lectured extensively throughout the U.S. on this methodology, its practices, and its benefits.A collection of ''lightweight'' software development methods evolved in the mid-1990s in reaction to the perceived ''heavyweight'' waterfall-oriented methods, which critics called heavily regulated, regimented, and micro-managed; although some proponents of these lightweight methods contended that they were simply returning to earlier software practices.Gerald M. Weinberg, as quoted in These lightweight methods included: from 1994, unified process and dynamic systems development method (DSDM); from 1995, scrum; from 1996, crystal clear and extreme programming (aka "XP"); and from 1997, adaptive software development and feature-driven development. Although these originated before the publication of the Agile Manifesto in 2001, they are now collectively referred to as agile methods; and often abbreviated loosely as ''Agile'', with a capital ''A'', although this is progressively becoming deprecated.
Agile Software Development is a set of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.
The ''Manifesto for Agile Software Development'', also known as the ''Agile Manifesto'', was first proclaimed in 2001, six years after "Agile Methodology" was originally introduced by the preeminent software engineers of the late 1980s and early 1990s. The Manifesto came out of the DSDM Consortium in 1994, although its roots go back to the mid 1980s at DuPont and works by James Martin〔Martin, James (1991). Rapid Application Development. Macmillan. ISBN 0-02-376775-8.〕 and James Kerr et al.〔Kerr, James M.; Hunter, Richard (1993). Inside RAD: How to Build a Fully Functional System in 90 Days or Less. McGraw-Hill. ISBN 0-07-034223-7 p.3〕
==History==
Incremental software development methods trace back to 1957.〔 In 1974, E. A. Edmonds wrote a paper that introduced an adaptive software development process.〔Note by Edmonds: I presented these ideas in London in 1970 and first submitted the paper to the Journal ''Computer Aided Design''. It was rejected with the comment "If you don't know what you are going to do before you start you shouldn't start"! Only then did I submit it to ''General Systems''.〕 Concurrently and independently, the same methods were developed and deployed by the New York Telephone Company's Systems Development Center under the direction of Dan Gielan. In the early 1970s, Tom Gilb started publishing the concepts of evolutionary project management (EVO), which has evolved into ''competitive engineering''.〔(【引用サイトリンク】title=Evolutionary Project Management )〕 During the mid- to late 1970s, Gielan lectured extensively throughout the U.S. on this methodology, its practices, and its benefits.
A collection of ''lightweight'' software development methods evolved in the mid-1990s in reaction to the perceived ''heavyweight'' waterfall-oriented methods, which critics called heavily regulated, regimented, and micro-managed; although some proponents of these lightweight methods contended that they were simply returning to earlier software practices.〔Gerald M. Weinberg, as quoted in 〕 These lightweight methods included: from 1994, unified process and dynamic systems development method (DSDM); from 1995, scrum; from 1996, crystal clear and extreme programming (aka "XP"); and from 1997, adaptive software development and feature-driven development. Although these originated before the publication of the Agile Manifesto in 2001, they are now collectively referred to as agile methods; and often abbreviated loosely as ''Agile'', with a capital ''A'', although this is progressively becoming deprecated.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「Agile Software Development is a set of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.The ''Manifesto for Agile Software Development'', also known as the ''Agile Manifesto'', was first proclaimed in 2001, six years after "Agile Methodology" was originally introduced by the preeminent software engineers of the late 1980s and early 1990s. The Manifesto came out of the DSDM Consortium in 1994, although its roots go back to the mid 1980s at DuPont and works by James MartinMartin, James (1991). Rapid Application Development. Macmillan. ISBN 0-02-376775-8. and James Kerr et al.Kerr, James M.; Hunter, Richard (1993). Inside RAD: How to Build a Fully Functional System in 90 Days or Less. McGraw-Hill. ISBN 0-07-034223-7 p.3==History==Incremental software development methods trace back to 1957. In 1974, E. A. Edmonds wrote a paper that introduced an adaptive software development process.Note by Edmonds: I presented these ideas in London in 1970 and first submitted the paper to the Journal ''Computer Aided Design''. It was rejected with the comment "If you don't know what you are going to do before you start you shouldn't start"! Only then did I submit it to ''General Systems''. Concurrently and independently, the same methods were developed and deployed by the New York Telephone Company's Systems Development Center under the direction of Dan Gielan. In the early 1970s, Tom Gilb started publishing the concepts of evolutionary project management (EVO), which has evolved into ''competitive engineering''.(【引用サイトリンク】title=Evolutionary Project Management ) During the mid- to late 1970s, Gielan lectured extensively throughout the U.S. on this methodology, its practices, and its benefits.A collection of ''lightweight'' software development methods evolved in the mid-1990s in reaction to the perceived ''heavyweight'' waterfall-oriented methods, which critics called heavily regulated, regimented, and micro-managed; although some proponents of these lightweight methods contended that they were simply returning to earlier software practices.Gerald M. Weinberg, as quoted in These lightweight methods included: from 1994, unified process and dynamic systems development method (DSDM); from 1995, scrum; from 1996, crystal clear and extreme programming (aka "XP"); and from 1997, adaptive software development and feature-driven development. Although these originated before the publication of the Agile Manifesto in 2001, they are now collectively referred to as agile methods; and often abbreviated loosely as ''Agile'', with a capital ''A'', although this is progressively becoming deprecated.」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|