Business-driven development: Difference between revisions

Revision as of 20:49, 20 June 2006

Latest revision as of 13:54, 6 May 2024

(45 intermediate revisions by 30 users not shown)

Line 1:

{{Short description|Methodology in IT development}}

'''Business-Drivendriven Developmentdevelopment'''<ref>T. Mitra. [http://www.ibm.com/developerworks/library/ws-bdd/index.html "Business-driven development"]. IBM developerWorks article.</ref> is a meta-[[methodology]] for developing IT solutions that directly satisfy [[requirement|business requirements]]. This is achieved by adopting a model-driven approach that starts with the business strategy, requirements, and goals, and then refines and transforms them into an IT solution. The transformation is typicallypartially achieved by applying model transformations. Due to the alignment of the business layer and the IT layer, it is possible to propagate changes ofin the business (semi-)automatically to the IT systems. This leads to increased flexibility and shorter turnaround times when changing the business and adapting the IT systems.<ref>J. Koehler et al. [http://www.inf.mit.bme.hu/GT-VMT2006/ProceedingsGTVMT2006.pdf "The Role of Visual Modeling and Model Transformations in Business-driven Development"]. Proceedings of GT-VMT 2006, pp. 1–12, 2006.</ref>

Business-driven development goes further than the simple development of delivered requirements in that the implementing resource seeks to completely understand the business side during the iterative gathering and implementing of requirements and drives to, once acquiring that information, improve business processes itself during the development of the actual solution.

==references==

<references/>

[http://www-128.ibm.com/developerworks/webservices/library/ws-bdd/index.html] T. Mitra. Business-driven development. IBM developerWorks article.

The applicability of automatic model transformations to align business and IT has been criticized and partially replaced by [[agile software development|agile]] practices and methods such as [[behavior-driven development]] (BDD) and [[___domain-driven design]] (DDD).<ref>M. Fowler, Agile Guide, http://martinfowler.com/agile.html</ref>

[http://www.inf.mit.bme.hu/GT-VMT2006/ProceedingsGTVMT2006.pdf] J. Koehler et al. The Role of Visual Modeling and Model Transformations in Business-driven Development. Proceedings of GT-VMT 2006, pages 1-12, 2006.

==See also==

* [[Behavior-driven development]] (BDD)

* [[Business process automation]]

* [[Business process management]] (BPM)

* [[Domain-driven design]] (DDD)

* [[Domain-specific modeling]] (DSM)

* [[Model-driven engineering]] (MDE)

* [[Service-oriented architecture]] (SOA)

* [[Service-oriented modeling]] Framework (SOMF)

* [[Workflow]]

==References==

{{reflist}}

[[Category:Software development process]]