Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Big-Data Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Big Data Architecture is a framework or blueprint that outlines the design, components, and processes required to handle and analyze large volumes of data. It encompasses the infrastructure, tools, and methodologies used to capture, store, process, and analyze diverse and complex data sets in a scalable and efficient manner.
Example: Title: Big Data Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Big-DataArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Big-DataArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/Big-DataArchitectureGoal
dct:title: Architecture Decision Record about Big-Data Architecture
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 | http://data.europa.eu/dr8/Big-DataArchitectureGoal |
dct:title | Architecture Decision Record about Big-Data Architecture |
skos:example | Title: Big Data 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/IEC/IEEE 42010:2022 |
eira:definitionSourceReference | https://www.iso.org/standard/74393.html |
skos:note | Big Data Architecture is a framework or blueprint that outlines the design, components, and processes required to handle and analyze large volumes of data. It encompasses the infrastructure, tools, and methodologies used to capture, store, process, and analyze diverse and complex data sets in a scalable and efficient manner. |
eira:PURI | http://data.europa.eu/dr8/Big-DataArchitectureGoal |
dct:type | eira:Big-DataArchitectureGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Big-Data Architecture |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |