Business-driven development: Difference between revisions

Revision as of 18:19, 5 December 2012

Latest revision as of 13:54, 6 May 2024

(19 intermediate revisions by 13 users not shown)

Line 1:

{{Short description|Methodology in IT development}}

'''Business-driven development'''<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 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 both 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.

Business-driven development is a new Agile method that helps business analysts, developers, and testers the sharing of a common language that is reached through specifications with examples via a strong focus on business need.

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>

Business-driven development goes further than the simple development of delivered requirements in that the implementing resource seeks to both 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.

==See also==

* [[ServiceBehavior-driven Oriented Architecturedevelopment]] (SOABDD)

* [[Business Processprocess automation]]

* [[Business Processprocess Managementmanagement]] (BPM)

* [[Domain-Specificdriven Modelingdesign]] (DSMDDD)

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

* [[Model-driven Driven Engineeringengineering]] (MDE)

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

* [[Service-Orientedoriented Modelingmodeling]] Framework (SOMF)

* [[Workflow]]

* [[Eclipse Modeling Framework]] (EMF)

* [[Domain-Specific Modeling]] (DSM)

* [[Model Driven Engineering]] (MDE)

* [[Service-Oriented Modeling]] Framework (SOMF)

==References==

{{reflist}}

<references/>

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

[[Category:Software development process]]

[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.

==External links==

[ftp://ftp.informatik.uni-stuttgart.de/pub/library/medoc.ustuttgart_fi/DIP-2787/DIP-2787.pdf Automated generation of business processes that satisfy business goals (Master thesis, IBM, 2008)]

[[Category:Software development]]