Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:99_annexes:annex-b-terms-and-definitions:m:mda [2026/07/11 11:14] – removed - external edit (Unknown date) 127.0.0.1 | dido:99_annexes:annex-b-terms-and-definitions:m:mda [2026/07/11 11:14] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Model Driven Architecture (MDA) ====== | ||
| + | |||
| + | [[dido: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | Model Driven Architecture (MDA) is an OMG architectural approach that organizes system specification around models and mappings between models. MDA separates the specification of system functionality from the specification of implementation technology. This separation supports portability, | ||
| + | |||
| + | In the SIP-RA and FX Demo context, MDA provides the architectural framing for distinguishing conceptual, logical, platform-independent, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | *an architectural approach that separates system functionality from implementation technology through models and mappings* | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | MDA uses models to describe systems at different levels of abstraction. A [[dido: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A SIP-RA conceptual model identifies architectural concepts and relationships. A platform-independent model refines those concepts without selecting a specific technology. A platform-specific model realizes those concepts using selected technologies, | ||
| + | |||
| + | --- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||