Executable architecture
 | This article or section is undergoing 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 actively editing this article or section, you can replace this template with {{in use|5 minutes}}.
This article was last edited by Sidna (talk | contribs) 16 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][2]
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
Implementations of EA include:
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