Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Installability
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: Installability in software architecture refers to the design and characteristics of a software system that enable easy and efficient installation, configuration, and deployment onto target environments. An installable software architecture aims to simplify the installation process for end-users or system administrators, reducing the time, effort, and potential errors involved in setting up and configuring the system.
Example: Title: Installability Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/InstallabilityGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:InstallabilityGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024766
dct:title: Architecture Decision Record about Installability
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-20230606091024766 |
dct:title | Architecture Decision Record about Installability |
skos:example | Title: Installability 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 | Installability in software architecture refers to the design and characteristics of a software system that enable easy and efficient installation, configuration, and deployment onto target environments. An installable software architecture aims to simplify the installation process for end-users or system administrators, reducing the time, effort, and potential errors involved in setting up and configuring the system. |
eira:PURI | http://data.europa.eu/dr8/InstallabilityGoal |
dct:type | eira:InstallabilityGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the Installability |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |