Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Service-Oriented Architecture
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: SOA is an architecture that focuses on organizing software systems as a collection of reusable services. These services are well-defined, self-contained modules that communicate with each other using standardized interfaces. SOA promotes interoperability, flexibility, and reusability of services across multiple applications.
Example: Title: Service-Oriented Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/Service-OrientedArchitectureGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:Service-OrientedArchitectureGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-08-20
dct:identifier: http://data.europa.eu/dr8/egovera/Service-OrientedArchitectureGoal
dct:title: Architecture Decision Record about Service-Oriented 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/Service-OrientedArchitectureGoal |
dct:title | Architecture Decision Record about Service-Oriented Architecture |
skos:example | Title: Service-Oriented 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 | SOA is an architecture that focuses on organizing software systems as a collection of reusable services. These services are well-defined, self-contained modules that communicate with each other using standardized interfaces. SOA promotes interoperability, flexibility, and reusability of services across multiple applications. |
eira:PURI | http://data.europa.eu/dr8/Service-OrientedArchitectureGoal |
dct:type | eira:Service-OrientedArchitectureGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Service-Oriented Architecture |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |