Executable architecture: Difference between revisions

Revision as of 18:15, 7 July 2009

Revision as of 18:24, 7 July 2009

Line 1:

{{underconstruction}}

An '''Executable Architecture''' (EA), in general, is the description of a [[system architecture]] (including software and/or otherwise) 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><ref>Youssef, R., Kim, B., Pagotto, J., Vallerand, A., Lam, S., Pace, P., Pogue, C., Greenley, A., "Toward an Integrated Executable Architecture and M&S Based Analysis for Counter Terrorism and Homeland Security", RTO-MP-MSG-045, NATO OTAN, February 2007 [http://ftp.rta.nato.int/public//PubFullText/RTO/MP/RTO-MP-MSG-045///MP-MSG-045-07.pdf]</ref>

==Closely Related Subjects==

Line 15:

* [[Rational Rose]]

* [[Generic Modeling Environment]] (GME)

* [[ODERA]]

== See also ==

Line 23 ⟶ 24:

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

* [[Object Management Group]] (OMG)

* [[Semantic Web]]

* [[Unified Process]]

* [[Universal Modeling Language]] (UML)