| Both sides previous revision Previous revision | |
| public:99_annexes:annex-b-terms-and-definitions:m:model [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:m:model to public:99_annexes:annex-b-terms-and-definitions:m:model nick_dido | public:99_annexes:annex-b-terms-and-definitions:m:model [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| ====== Model ====== | ====== Model ====== |
| |
| [[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] | [[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]] |
| |
| ===== Discussion ===== | ===== Discussion ===== |
| A model provides a structured representation of selected aspects of a subject. A model does not reproduce the whole subject. It represents the aspects needed for a defined purpose, such as analysis, specification, communication, validation, implementation, or governance. | A model provides a structured representation of selected aspects of a subject. A model does not reproduce the whole subject. It represents the aspects needed for a defined purpose, such as analysis, specification, communication, validation, implementation, or governance. |
| |
| In the SIP-RA and FX Demo context, a model represents selected [[private:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], behavior, function, meaning, constraints, relationships, or transformations. Models support separation between conceptual, logical, and platform-specific concerns. A model becomes useful for architectural work when its notation, vocabulary, constraints, and interpretation rules make the represented subject sufficiently clear for review, comparison, mapping, or implementation. | In the SIP-RA and FX Demo context, a model represents selected [[public:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], behavior, function, meaning, constraints, relationships, or transformations. Models support separation between conceptual, logical, and platform-specific concerns. A model becomes useful for architectural work when its notation, vocabulary, constraints, and interpretation rules make the represented subject sufficiently clear for review, comparison, mapping, or implementation. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Source ===== | ===== Source ===== |
| |
| Derived from [[private:99_annexes:annex-b-terms-and-definitions:m:mda|Model Driven Architecture (MDA)]] usage and [[private:99_annexes:annex-b-terms-and-definitions:i:iso|ISO]] terminology practice. | Derived from [[public:99_annexes:annex-b-terms-and-definitions:m:mda|Model Driven Architecture (MDA)]] usage and [[public:99_annexes:annex-b-terms-and-definitions:i:iso|ISO]] terminology practice. |
| |
| ===== Note ===== | ===== Note ===== |
| ===== Example ===== | ===== Example ===== |
| |
| A [[private:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] represents selected structure and behavior of a subsystem without specifying the technology platform used to realize the subsystem. | A [[public:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] represents selected structure and behavior of a subsystem without specifying the technology platform used to realize the subsystem. |
| |
| ---- | ---- |