Executable architecture
 | This article or section is in a state of significant expansion or restructuring. You are welcome to assist in its construction by editing it as well. If this article or section has not been edited in several days, please remove this template. If you are the editor who added this template and you are actively editing, please be sure to replace this template with {{in use}} during the active editing session. Click on the link for template parameters to use.
This article was last edited by Sidna (talk | contribs) 15 years ago. (Update timer) |
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.[1]
Implementations of EA include:
- Object Management Group's Model-driven architecture
- Object Management Group's Business Process Management Initiative
- Vanderbilt University's Model Integrated Computing (MIC)
See also
- Business Process Execution Language (BPEL)
- Business Process Management Initiative (BPMI)
- Business Process Modeling Language (BPMN)
- Model-driven architecture (MDA)
- Model-driven engineering (MDE)
- Object Management Group (OMG)
- Unified Process
- Universal Modeling Language (UML)
- Vanderbilt University