Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Disaster Recovery Plan
Source: ISO
Source reference: https://www.iso.org/standard/75106.html
Additional information: A Disaster Recovery Plan (DRP) is a documented and structured approach that outlines the strategies, processes, and procedures to be followed in the event of a disaster or significant disruption that impacts an organization's IT infrastructure, systems, and data. The primary goal of a DRP is to minimize the impact of the disaster, recover critical systems and data, and restore normal operations as quickly and efficiently as possible.
Example: Title: Disaster Recovery Plan Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/DisasterRecoveryPlanGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:DisasterRecoveryPlanGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024730
dct:title: Architecture Decision Record about Application of Disaster Recovery Plan
eira:adr_context: The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons.
eira:adr_decision: The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how.
eira:adr_status: [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)]
eira:adr_consecuences: The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture.
|
|
dct:modified | 2024-01-28 |
dct:identifier | ADR-20230606091024730 |
dct:title | Architecture Decision Record about Application of Disaster Recovery Plan |
skos:example | Title: Disaster Recovery Plan Architecture Decision Record (ADR) |
eira:adr_context | The context explains why we need to make a decision. It also describes the alternatives along with the pros and cons. |
eira:adr_decision | The decision describes the justification for why the particular solution was accepted. It has more emphasis on the why rather than the how. |
eira:adr_status | [Proposed (under review)|Accepted (approved and ready for implementation)|Superseded (superseded by another decision)] |
eira:adr_consecuences | The consequences section contains information about the overall impact of an architectural decision. Every decision has trade-offs. That’s why it’s crucial to include the analysis to provide a clear picture. |
eira:concept | eira:ArchitectureBuildingBlock |
eira:definitionSource | ISO |
eira:definitionSourceReference | https://www.iso.org/standard/75106.html |
skos:note | A Disaster Recovery Plan (DRP) is a documented and structured approach that outlines the strategies, processes, and procedures to be followed in the event of a disaster or significant disruption that impacts an organization's IT infrastructure, systems, and data. The primary goal of a DRP is to minimize the impact of the disaster, recover critical systems and data, and restore normal operations as quickly and efficiently as possible. |
eira:PURI | http://data.europa.eu/dr8/DisasterRecoveryPlanGoal |
dct:type | eira:DisasterRecoveryPlanGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Disaster Recovery Plan |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |