| Both sides previous revision Previous revision | |
| dido:00-sip-ra:02-architectural-context:start [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:00-sip-ra:02-architectural-context:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 |
|---|
| [[dido:00-sip-ra:start|Return to Structured Information Processing Reference Architecture (SIP-RA) Request for Proposal]] | [[dido:00-sip-ra:start|Return to Structured Information Processing Reference Architecture (SIP-RA) Request for Proposal]] |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:m:mda|Model Driven Architecture (MDA)]] provides a set of guidelines for structuring specifications as [[dido:99_annexes:annex-b-terms-and-definitions:m:model|models]] and mappings. The MDA initiative and the standards that support it allow the same model, specifying business-system or application functionality and behaviour, to be realised on multiple platforms. MDA enables different applications to be integrated by explicitly relating their models. This facilitates integration and interoperability and supports system evolution and deployment choices as platform technologies change. The three primary goals of MDA are portability, interoperability, and reusability. | [[dido:99_annexes:annex-b-terms-and-definitions:m:mda|Model Driven Architecture (MDA)]] provides a set of guidelines for structuring specifications as [[dido:99_annexes:annex-b-terms-and-definitions:m:model|models]] and mappings. The MDA initiative and the standards that support it allow the same model, specifying business-system or application functionality and behavior, to be realized on multiple platforms. MDA enables different applications to be integrated by explicitly relating their models. This facilitates integration and interoperability and supports system evolution and deployment choices as platform technologies change. The three primary goals of MDA are portability, interoperability, and reusability. |
| |
| Portability of any subsystem is relative to the subsystems on which it depends. The collection of subsystems a given subsystem depends on is often loosely referred to as the platform that supports it. Standardised interfaces, application programming interfaces (APIs), and consistent usage patterns support portability and reusability across dependent subsystems. | Portability of any subsystem is relative to the subsystems on which it depends. The collection of subsystems a given subsystem depends on is often loosely referred to as the platform that supports it. Standardized interfaces, application programming interfaces (APIs), and consistent usage patterns support portability and reusability across dependent subsystems. |
| |
| MDA provides a pattern comprising a portable subsystem that uses one of multiple specific platform implementations. This pattern is repeatedly usable in the specification of systems. The five important concepts related to this pattern are: | MDA provides a pattern comprising a portable subsystem that uses one of multiple specific platform implementations. This pattern is repeatedly usable in the specification of systems. The five important concepts related to this pattern are: |
| ===== Model ===== | ===== Model ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:m:model|model]] represents a selected function, [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], behaviour, or meaning of an application or system for a defined purpose. A representation is formal when it is based on a language that has a well-defined form, meaning, or semantics, and possibly rules of analysis, inference, or proof for its constructs. The syntax may be graphical or textual. The semantics might be defined, more or less formally, in terms of things observed in the world being described, such as message sends, and replies, object states, and state changes, or by translating higher-level language constructs into other constructs with well-defined meanings. | A [[dido:99_annexes:annex-b-terms-and-definitions:m:model|model]] represents a selected function, [[dido:99_annexes:annex-b-terms-and-definitions:s:structure|structure]], behavior, or meaning of an application or system for a defined purpose. A representation is formal when it is based on a language that has a well-defined form, meaning, or semantics, and possibly rules of analysis, inference, or proof for its constructs. The syntax may be graphical or textual. The semantics might be defined, more or less formally, in terms of things observed in the world being described, such as message sends, and replies, object states, and state changes, or by translating higher-level language constructs into other constructs with well-defined meanings. |
| |
| The non-mandatory rules of inference specify which unstated properties can be deduced from the explicit statements in the model. In MDA, a representation that is not formal in this sense is not a model. Thus, a diagram with boxes, lines, and arrows that is not supported by definitions of the meanings of boxes, lines, and arrows is not a model. It is an informal diagram. | The non-mandatory rules of inference specify which unstated properties can be deduced from the explicit statements in the model. In MDA, a representation that is not formal in this sense is not a model. Thus, a diagram with boxes, lines, and arrows that is not supported by definitions of the meanings of boxes, lines, and arrows is not a model. It is an informal diagram. |
| ===== Platform Independent Model (PIM) ===== | ===== Platform Independent Model (PIM) ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] is a model of a subsystem that contains no information specific to the platform or the technology used to realise it. | A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_independent_model|Platform Independent Model (PIM)]] is a model of a subsystem that contains no information specific to the platform or the technology used to realize it. |
| |
| ===== Platform Specific Model (PSM) ===== | ===== Platform Specific Model (PSM) ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform Specific Model (PSM)]] is a model of a subsystem that includes information about the specific technology used in the realisation of that subsystem on a specific platform. A PSM includes platform-specific elements that are necessary to realise the subsystem. | A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_model|Platform Specific Model (PSM)]] is a model of a subsystem that includes information about the specific technology used in the realization of that subsystem on a specific platform. A PSM includes platform-specific elements that are necessary to realize the subsystem. |
| |
| ===== Mapping ===== | ===== Mapping ===== |