Agile Model Driven Development
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Agile Model Driven Development" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Agile Model Driven Development|concern=Non-notable term}} ~~~~Timestamp: 20090718220313 22:03, 18 July 2009 (UTC) Administrators: delete |
Agile Model Driven Development (AMDD) is the AGILE version of Model Driven Development. It operates trough initially defining only basic high level architecture and requirements, with details being filled out on the way, often trough Storm Modelling. [1][2]
It is the logical opposite of BDUF methodology, which strives to perfect the design before starting on any form of implementation.
References
 | This software-engineering-related article is a stub. You can help Wikipedia by expanding it. |