Definition: Architecture Decision Record from where you should specialise the ADR SBBs regarding the Internazionalization and Localization Source: ISO/IEC/IEEE 42010:2022 Source reference: https://www.iso.org/standard/74393.html Additional information: The decision of internationalization and localization in IT architecture refers to the process of designing software applications that can be adapted to different languages, cultures, and regions. Internationalization involves creating software that can handle different character sets, date and time formats, and other cultural differences. Localization involves adapting the software to a specific language and culture, including translating text, adjusting graphics, and modifying functionality to meet local requirements. This concept is important for companies that operate in multiple countries and need to provide software that can be used by people with different backgrounds and languages. Example: Internationalization and Localization: Decision: Building support for multiple languages and cultural adaptations into the software system. Rationale: Internationalization and localization enable the organization to reach a broader global market, cater to diverse customer preferences, and provide a localized user experience, leading to increased customer satisfaction and market penetration. LOST view: Digital Solution Architecture Decisions Catalogue view Identifier: http://data.europa.eu/dr8/egovera/InternazionalizationAndLocalizationGoal EIRA traceability: eira:DigitalSolutionArchitectureDecisionGoal ABB name: egovera:InternazionalizationAndLocalizationGoal EIRA concept: eira:ArchitectureBuildingBlock Last modification: 2023-06-15 dct:identifier: ADR-20230515180947623 dct:title: Architecture Decision Record about Internazionalization and Localization 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.