Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the UserInterface
Source: ISO/IEC/IEEE 42010:2022
Source reference: https://www.iso.org/standard/74393.html
Additional information: the user interface (UI) refers to the visual and interactive elements of a software system that allow users to interact with and control the system. It encompasses the design and presentation of screens, menus, buttons, forms, and other visual components that users engage with to perform tasks and access information within the system.
Example: Title: User Interface Architecture Decision Record (ADR)
LOST view: Digital Solution Architecture Decisions Catalogue view
Identifier: http://data.europa.eu/dr8/egovera/UserInterfaceGoal
EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal
ABB name: egovera:UserInterfaceGoal
EIRA concept: eira:ArchitectureBuildingBlock
Last modification: 2023-07-06
dct:identifier: ADR-20230606091024717
dct:title: Architecture Decision Record about UserInterface
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-20230606091024717 |
dct:title | Architecture Decision Record about UserInterface |
skos:example | Title: User Interface 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 | the user interface (UI) refers to the visual and interactive elements of a software system that allow users to interact with and control the system. It encompasses the design and presentation of screens, menus, buttons, forms, and other visual components that users engage with to perform tasks and access information within the system. |
eira:PURI | http://data.europa.eu/dr8/UserInterfaceGoal |
dct:type | eira:UserInterfaceGoal |
skos:definition | Architecture Decision Record from where you should specialise the ADR SBBs regarding the UserInterface |
eira:view | Digital Solution Architecture Decisions Catalogue view |
eira:eifLayer | N/A |
skos:broader | http://data.europa.eu/dr8/DigitalSolutionArchitectureDecisionGoal |