Executable architecture: Difference between revisions

Revision as of 18:02, 7 July 2009

Revision as of 18:11, 7 July 2009

Line 1:

{{underconstruction}}

An '''Executable Architecture''' (EA), in general, is the description of a [[system architecture]] in a [[formal]] [[notation]] together with the tools (e.g. [[compilers]]/[[translators]]) that allow the automatic or semi-automatic generation of artifacts (e.g. Capability Gap Analysis (CGA), [[Models]], SW Stubs, MSDL) from that notation and which are used in the analysis, refinement, and/or the implementation of the architecture described.<ref>Pawlowski, Tom, "Executable Architecture", [[MITRE]], 2004 [http://www.mitre.org/news/events/tech04/briefings/729.pdf]</ref><ref>Garcia, Johnny, "Executable architecture analysis modeling", ISBN:1-56555-314-4, 2007 [http://portal.acm.org/citation.cfm?id=1404840]</ref>

Implementations of '''EA''' include:

==Closely Related Subjects==

* [[Object Management Group]]'s [[Model-driven architecture]]

* [[Object Management Group]]'s [[Business Process Management Initiative]]

* [[Vanderbilt University]]'s Model Integrated Computing (MIC)

== Implementations of '''EA''' include:==

* [[Rational Rose]]

* Generic Modeling Environment (GME)

== See also ==

* [[Business Process Execution Language]] (BPEL)

* [[Business Process Management Initiative]] (BPMI)