2.1.3 Mapping to Reference Models
The purpose of this section is to highlight any products and technologies that are relevant to the baseline architecture.
If they are relevant, this section may either provide references to the relevant documentation that has been produced separately by the domains or provide the necessary information.
If the relevant product(s) and technology(s) are described in other documentation, in terms of quality criteria, this section should make clear:
• The relevant products and technologies documentation
• Context around any such relevant products and technologies documentation; e.g., validity, ownership, purpose
• Any deviance from existing products and technologies and the reasons why
• Any assumptions regarding the products and technologies, or their documentation
If the relevant product(s) and technology(s) are not described in other documentation, in terms of quality criteria, this section should make clear:
• Any domain-specific, other domain-specific, or xxxx enterprise architecture-level products and technologies that have been used to help define the current architecture
• Any deviance from existing products and technologies and the reasons why
• Any assumptions regarding the products and technologies, or their documentation
Value
Using reference models can reduce the cost and time of developing a solution by reducing complexity, increasing reuse, improving communication, enhancing governance and improving compliance.
mandatory section
Yes
risk type
Cost
Time
Quality
Security
Risk owner
Architecture
Dependent Section