Merge pull request #72 from isaqb-org/Übersetzungen

Übersetzung in Englisch

docs/00b-basics/01-what-to-expect-of-this-module.adoc

@@ -12,8 +12,11 @@ Am Ende des Moduls {curriculum-short} kennen die Teilnehmenden die wesentlichen
 // tag::EN[]
 === What does the module “{curriculum-short}” convey?
 
-The module presents {curriculum-short} to the participants …
-At the end of the module, the participants know … and are able to …
-TODO
+While IT was long seen as the solution to many problems associated with climate change, it has now itself become the subject of optimisation considerations. Inefficient programming, often caused by the need for a fast time-to-market, has often been compensated for by ever faster hardware or more resources in the cloud. This path must be abandoned. The CO~2~ emissions caused by software must be consistently reduced.
+
+In the {curriculum-short} module, participants learn to take a holistic view of the topic of green software. This begins with an examination of the role of IT in halting climate change, an introduction to current regulations, a view of the requirements of various stakeholders and the identification of fields of action in companies. From there, we move on to measuring and monitoring CO~2~ emissions and energy consumption and on to the core topic of software development. This central topic area includes the energy efficiency of various software architectures and basic concepts used, energy-efficient data handling, optimised algorithms and also the influence and management of quality requirements in relation to energy efficiency. Another important component is the topic of the cloud, both in terms of provider selection and the possibilities for low-CO~2~ operation. Finally, options for improving energy efficiency in the development process are considered.
+
+At the end of the module {curriculum-short}, participants will know the key levers for reducing CO~2~ in IT. They will be able to assess the impact of software architecture and how architecture patterns and styles work. They know the pitfalls of data handling and can assess the impact of the selection of technical components. With regard to the cloud, participants know how to utilise the options offered there in terms of energy efficiency.
+
 // end::EN[]
 

docs/00b-basics/02-curriculum-structure-and-chronological-breakdown.adoc

@@ -26,7 +26,15 @@
 |===
 | Content
 | Recommended minimum duration (minutes)
-TODO
+| 1. Climate change, opportunities of digitalisation, role of IT, basic concepts | 60
+| 2. Principles, regulation and effects on companies | 60
+| 3. Quality | 60
+| 4. Measurement and monitoring | 150
+| 5. Software development | 75
+| 6. Software architecture | 150
+| 7. Operation | 105
+| 8. Energy-efficient development process | 60
+| |
 | Total | 720 (12h)
 
 |===

docs/00b-basics/04-prerequisites-for-this-training.adoc

@@ -13,7 +13,7 @@ Teilnehmerinnen und Teilnehmer **sollten** folgende Kenntnisse und/oder Erfahrun
 
 - Erste praktische Erfahrungen mit Performance Engineering
 - Erste praktische Erfahrung mit gängigen Cloud-Anbietern
-- Erste praktische Erfahrung mit CI/CD-Pipelines.
+- Erste praktische Erfahrung mit CI/CD-Pipelines
 
 // end::DE[]
 
@@ -22,10 +22,16 @@ Teilnehmerinnen und Teilnehmer **sollten** folgende Kenntnisse und/oder Erfahrun
 
 Participants **should** have the following prerequisite knowledge:
 
-- TODO
+- Practical experience in the design and development of small to medium-sized software systems
+- Knowledge of the life cycle of software systems
+- Dealing with quality requirements
+- Practical experience in monitoring software systems
+- Practical programming experience
 
 Knowledge in the following areas may be **helpful** for understanding some concepts:
 
-- TODO
+- First practical experience with performance engineering
+- First practical experience with common cloud providers
+- First practical experience with CI/CD pipelines
 
 // end::EN[]

docs/01-module-block-1/00-structure.adoc

@@ -8,7 +8,7 @@
 // end::DE[]
 
 // tag::EN[]
-== TODO
+== Climate change, opportunities of digitalisation, role of IT, basic concepts 
 // end::EN[]
 
 

docs/01-module-block-1/01-duration-terms.adoc

@@ -10,9 +10,10 @@ Klimawandel, Verbrauch von IT, Einsparungen durch IT, Einsparungen in IT, Nachha
 
 // tag::EN[]
 |===
-| Duration: 60 min | Practice time: 0 min
+| Duration: 60 min | Practice time: none
 |===
 
 === Terms and Principles
-Consumption of ICT, Savings through ICT, Sustainability, CO2, CO2 equivalents, Negative externalities, Watts, Joules, Efficiency, Effectiveness
+Climate change, consumption of IT, savings through IT, savings in IT, sustainability, CO~2~, CO~2~-equivalents, negative external effects, watts, joules, efficiency, effectiveness
+
 // end::EN[]

docs/01-module-block-1/02-learning-goals.adoc

@@ -33,5 +33,34 @@ Die Teilnehmenden kennen die Handlungsfelder zum Einsparen von CO~2~:
 // end::DE[]
 
 // tag::EN[]
-TODO
+
+[[LG-1-1]]
+==== LG 1-1: Global challenges of climate change
+
+Participants are familiar with the global challenges of climate change. They know the increasing energy and resource requirements of IT and their main drivers. They can explain why IT must also address the issue of resource and energy efficiency.
+
+[[LG-1-2]]
+==== LG 1-2: Possibilities for saving energy through digitalisation
+
+Participants know the possibilities for saving energy and CO~2~ through digitalisation. They know the sectors that particularly benefit from digitalisation. The difference between savings in IT and through IT is known.
+
+[[LG-1-3]]
+==== LG 1-3: Categorise and quantify the energy consumption of IT and name its drivers
+
+Participants can quantify the energy consumption of information technology, categorise it in relation to other sectors and name the main drivers. They are familiar with trends and developments in IT and key levers.
+
+[[LG-1-4]]
+==== LG 1-4: Basic concepts
+
+Participants can categorise terms such as sustainability, energy efficiency, negative external effect, carbon footprint and carbon handprint. Important key figures and physical units such as CO~2~, CO~2~ equivalents, watts, joules and their meaning are understood.
+
+[[LG-1-5]]
+==== LG 1-5: Fields of action
+
+The participants know the fields of action for saving CO~2~:
+
+* Energy efficiency - Consume as little energy as possible.
+* Hardware efficiency - Use as little hardware as possible.
+* CO~2~ emission efficiency - Consume energy when and where it is generated in the "greenest" way.
+
 // end::EN[]

docs/02-module-block-2/00-structure.adoc

@@ -7,7 +7,7 @@
 // end::DE[]
 
 // tag::EN[]
-== TODO
+== Principles, regulation and effects on companies
 // end::EN[]
 
 include::01-duration-terms.adoc[{include_configuration}]

docs/02-module-block-2/01-duration-terms.adoc

@@ -10,11 +10,11 @@ Energieeffizienz, Zertifizierungen (z. B. Blauer Engel, TCO), Regulatorische Anf
 
 // tag::EN[]
 |===
-| Duration: 60 min | Practice time: 0 min
+| Duration: 60 min | Practice time: none
 |===
 
 === Terms and Principles
-Energy efficiency, Certifications (e. g. Blue Angel, TCO), Policy requirements (e. g. CRSD), Greenhouse Gas Protocol
+Energy efficiency, certifications (e.g. Blue Angel, TCO), regulatory requirements (e.g. CSRD, ESD), Greenhouse Gas Protocol (GHG Protocol)
 
 // end::EN[]
 

docs/02-module-block-2/02-learning-goals.adoc

@@ -24,5 +24,25 @@ Die Teilnehmenden kennen die Anforderungen der verschiedenen Stakeholder an ener
 // end::DE[]
 
 // tag::EN[]
-TODO
+
+[[LG-2-1]]
+==== LG 2-1: Regulation
+
+Participants know the regulatory framework and the requirements it contains for saving CO~2~. They know the existing certifications, such as the Blue Angel, and can use them appropriately in their work. Participants are familiar with standards such as ESG (Environmental Social Governance) and CSRD (Corporate Sustainability Reporting Directive) and their effects and consequences for companies.
+
+[[LG-2-2]]
+==== LG 2-2: Greenhouse Gas Protocol
+
+Participants are familiar with the Greenhouse Gas Protocol (GHP). They are able to explain the scopes and assign emissions to the scopes. They can explain which scopes are affected when operating software in the cloud or on premise. Participants are familiar with ISO 14064-1 as a derivation of the Greenhouse Gas Protocol.
+
+[[LG-2-3]]
+==== LG 2-3: Energy efficiency in the company
+
+The participants know the motivation for placing green software in the company and the arguments and addressees for successfully anchoring it in the company. They can set sensible targets for the reduction of greenhouse gases for companies. Participants can explain what requirements third parties have along the value chain and how these affect their own company.
+
+[[LG-2-4]]
+==== LG 2-4: Stakeholders and prioritization
+
+Participants know the requirements of the various stakeholders for energy-efficient software and the resulting fields of action. They know the areas with the greatest leverage for reducing greenhouse gases and can prioritize measures accordingly. Participants can classify different software systems and recognize the costs and benefits of optimization.
+
 // end::EN[]

docs/03-module-block-3/01-duration-terms.adoc

@@ -11,11 +11,11 @@ Qualitätsmodell, Qualitätsszenarien, Qualitätsziele, ISO 25010
 
 // tag::EN[]
 |===
-| Duration: XXX 30 | Practice time: 15 min
+| Duration: 45 min | Practice time: 15 min
 |===
 
 === Terms and Principles
-quality model, quality goal, szenario, ISO 25010
+Quality model, quality scenarios, quality objectives, ISO 25010
 
 // end::EN[]
 

docs/03-module-block-3/02-learning-goals.adoc

@@ -7,17 +7,18 @@ Die Teilnehmenden kennen unterschiedliche Qualitätsmodelle und können Qualitä
 
 [[LZ-3-2]]
 ==== LZ 3-2: Wechselwirkungen zwischen Qualitätsattributen
-Die Teilnehmenden kennen die positiven und negativen Wechselwirkungen zwischen Qualitätsattributen im Bereich der Energieeffizienz mit anderen Qualitätsattributen. Auf Basis dieser Erkenntnisse können sie Qualitätsanforderungen erkennen, die miteinander in Konflikt stehen und Lösungsalternativen erarbeiten, um Konflikte zu abzuschwächen.
-Insbesondere werden die Qualitätsmerkmale Elastizität und Skalierbarkeit, Modularität bzw. Resilienz detaillierter diskutiert, so dass die Teilnehmenden den Einfluss auf Energieeffizienz bewerten können.
+Die Teilnehmenden kennen die positiven und negativen Wechselwirkungen zwischen Qualitätsattributen im Bereich der Energieeffizienz mit anderen Qualitätsattributen. Auf Basis dieser Erkenntnisse können sie Qualitätsanforderungen erkennen, die miteinander in Konflikt stehen und Lösungsalternativen erarbeiten, um Konflikte zu abzuschwächen. Insbesondere werden die Qualitätsmerkmale Elastizität und Skalierbarkeit, Modularität bzw. Resilienz detaillierter diskutiert, so dass die Teilnehmenden den Einfluss auf Energieeffizienz bewerten können.
 
 // end::DE[]
 
 // tag::EN[]
+
 [[LG-3-1]]
-==== LG 3-1: TBD
-tbd.
+==== LG 3-1: Quality models and energy efficiency
+Participants are familiar with different quality models and can describe quality attributes relating to energy efficiency and categorise them in the quality models. In addition, participants are able to formulate quality scenarios for quality attributes in the area of energy efficiency. Depending on the intended use and the quantity structure of the application, they can consciously decide whether the quality criteria are used only for the application or for the optimisation of the development process.
 
 [[LG-3-2]]
-==== LG 3-2: TBD
-tbd.
+==== LG 3-2: Interactions between quality attributes
+Participants know the positive and negative interactions between quality attributes in the area of energy efficiency and other quality attributes. Based on this knowledge, they can recognise quality requirements that conflict with each other and develop alternative solutions to mitigate conflicts. In particular, the quality attributes of elasticity and scalability, modularity and resilience are discussed in more detail so that participants can assess their influence on energy efficiency.
+
 // end::EN[]

docs/04-module-block-4/01-duration-terms.adoc

@@ -10,10 +10,11 @@ Software Carbon Intensity (SCI), Business Metriken, Proxy-Metriken, Energieeffiz
 
 // tag::EN[]
 |===
-| Duration: 60 Min | Practice time: 30 min
+| Duration: 90 Min | Practice time: 60 min
 |===
 
 === Terms and Principles
+Software Carbon Intensity (SCI), business metrics, proxy metrics, energy efficiency, categories of measurement methods, measurement tools
 
 // end::EN[]
 

docs/04-module-block-4/02-learning-goals.adoc

@@ -3,9 +3,8 @@
 // tag::DE[]
 
 [[LZ-4-1]]
-==== LZ 4-1: Ressourcen in Relation zur erbrachten Leistung bringen
-Die Teilnehmenden sind in der Lage, Ressourcen in Relation zur erbrachten Leistung zu bringen
-(Business Metrik). Sie kennen als Metrik den ISO-Standard Software Carbon Intensity (SCI) und verstehen, wie dieser als Business Metrik genutzt werden kann.
+==== LZ 4-1: Ressourcen in Relation zur erbrachten Leistung bringen
+Die Teilnehmenden sind in der Lage, Ressourcen in Relation zur erbrachten Leistung zu bringen (Business Metrik). Sie kennen als Metrik den ISO-Standard Software Carbon Intensity (SCI) und verstehen, wie dieser als Business Metrik genutzt werden kann.
 
 [[LZ-4-2]]
 ==== LZ 4-2: Messverfahren und Messwerkzeuge
@@ -43,12 +42,43 @@ Die Teilnehmenden verstehen, dass die Messungen möglichst einfach und leichtgew
 // end::DE[]
 
 // tag::EN[]
+
 [[LG-4-1]]
-==== LG 4-1: TBD
-tbd.
+==== LG 4-1: Relating resources to the work performed
+Participants are able to relate resources to the service provided (business metric). They are familiar with the ISO standard Software Carbon Intensity (SCI) as a metric and understand how it can be used as a business metric.
 
 [[LG-4-2]]
-==== LG 4-2: TBD
-tbd.
+==== LG 4-2: Measurement methods and tools
+Participants know different categories of measurement methods and their areas of application. They understand how to combine tools from the different categories for an analysis.
+Categories include, for example:
+
+* Hardware measurement tools. Measure consumption directly on the hardware.
+* Full-stack measurement tools. Measure all components of an application such as consumption per Docker container, network.
+* Programming language-specific measurement tools. Provide "whitebox" measurements within an application.
+* Measurement tools for web applications. Provide information about the network load generated by a page request, among other things.
+* Carbon footprint tools from cloud providers. In cloud environments, energy consumption cannot be measured directly. Instead, you have to rely on tools provided by the provider or other estimation methods. Participants are familiar with the functionality and limitations of these tools (inaccuracy, relative data, necessary authorisations in the cloud console) as well as the challenges of comparing managed services with pure VMs.
+
+[[LG-4-3]]
+==== LG 4-3: Measurement methodology
+The participants know the methodological procedure for measuring energy consumption and CO~2~ intensity. They understand that it is generally not possible to evaluate/measure absolute consumption very precisely (especially in the cloud), but how to analyse trends instead. They know proxy metrics for CO~2~ intensity.
+
+Participants know how to set up meaningful scenarios for measuring energy efficiency.
+
+* They know criteria for designing the scenarios (e.g. common processes, prioritisation according to frequency of use).
+* They know which interfaces to use depending on the objective of the measurement (end-to-end scenarios, using APIs, etc.).
+* They know tools for creating such scenarios.
+* They can deal adequately with measurement inaccuracies (e.g. running scenarios multiple times, interpreting deviations).
+
+Participants understand that the procedure for measuring energy efficiency is related to the procedure for measuring performance. Participants understand how to proceed systematically in order to narrow down consumption hotspots.
+
+[[LG-4-4]]
+==== LG 4-4: Integrating energy efficiency measurements into the development process
+Participants know how to integrate energy efficiency measurements into the development process. They know how to integrate the measurements into the CI/CD pipeline. They understand how to find a good balance for the frequency of the measurements - on the one hand (negative) trends should be recognised quickly, on the other hand the measurement itself also consumes energy.
+
+Participants understand that the measurements must be as simple and lightweight as possible for developers to use in order to increase acceptance. They understand that energy efficiency measurements compete with quick feedback from the build. You understand that the following points are also important for acceptance:
+
+* Creating the scenarios for the measurement must be easy. It is advantageous to use tools that are already established in the project (e.g. frameworks for creating end-to-end tests)
+* The presentation of the measurement results must be clear, easy and quick to understand. In particular, the most important results such as trends or significant deviations in consumption must be directly recognisable.
+
 // end::EN[]
 

docs/05-module-block-5/01-duration-terms.adoc

@@ -4,17 +4,16 @@
 |===
 
 === Begriffe und Konzepte
-Programmiersprachen, Ahead-of-Time und Just-in-Time Compilierung, Bytecode, Maschine Code, 
-Garbage-Collection, Datenstrukturen, Algorithmen, Rechnerische Komplexität, Caching, Datenbanksysteme, Datenmodelle
+Programmiersprachen, Ahead-of-Time und Just-in-Time Compilierung, Bytecode, Maschine Code, Garbage-Collection, Datenstrukturen, Algorithmen, Rechnerische Komplexität, Caching, Datenbanksysteme, Datenmodelle
 
 // end::DE[]
 
 // tag::EN[]
 |===
-| Duration: 90 min | Practice time: 60 min
+| Duration: 75 min | Practice time: none
 |===
 
 === Terms and Principles
-TODO
+Programming languages, ahead-of-time and just-in-time compilation, bytecode, machine code, garbage collection, data structures, algorithms, computational complexity, caching, database systems, data models
 
 // end::EN[]

docs/05-module-block-5/02-learning-goals.adoc

@@ -18,17 +18,18 @@ Die Teilnehmenden kennen das Prinzip der rechnerischen Komplexität und können
 // end::DE[]
 
 // tag::EN[]
+
 [[LG-5-1]]
-==== LG 5-1: TODO
-TODO
+==== LG 5-1: Energy efficiency in software development
+Participants know the procedures and limits for optimising programs. They can distinguish sensible starting points from less worthwhile goals. Participants are familiar with the energy efficiency of various programming languages and can assess the areas of application for which they are suitable. They can evaluate the runtime behaviour and development speed of programming languages and make the right choice based on the requirements. They also understand the differences between ahead-of-time and just-in-time compilation, bytecode and machine code and the conflicting goals of garbage collectors. 
 
 [[LG-5-2]]
-==== LG 5-2: TODO
-TODO
-
+==== LG 5-2: Data handling
+Participants know methods for handling large amounts of data. They can assess data structures and operations on these data structures in terms of energy efficiency and make the right selection based on the given requirements. Participants know the pitfalls of using database systems and can avoid them. They are able to evaluate and optimally select different approaches for mapping relationships between entities on the basis of business requirements and quality requirements.
+ 
 [[LG-5-3]]
-==== LG 5-3: TODO
-TODO
+==== LG 5-3: Optimisations
+Participants are familiar with the principle of computational complexity and can evaluate and select algorithms in terms of their runtime and energy efficiency. They can use caches in connection with energy efficiency, know how they work (e.g. cache replacement) as well as the advantages and disadvantages. They know the possibilities and limitations of tools for detecting energy code smells.
 
 // end::EN[]
 

docs/06-module-block-6/01-duration-terms.adoc

@@ -4,16 +4,16 @@
 |===
 
 === Begriffe und Konzepte
-Monolith, Microservices, Serverless, Inter-Prozess-Kommunikation, Datenbanken
+Architekturstile, Monolith, Microservices, Serverless, Inter-Prozess-Kommunikation, Datenbanken, Green IT Pattern
 
 // end::DE[]
 
 // tag::EN[]
 |===
-| Duration: 90 min | Practice time: 30 min
+| Duration: 90 min | Practice time: 60 min
 |===
 
 === Terms and Principles
-monolith, microservices, serverless, communication, databases
+Architecture styles, monolith, microservices, serverless, inter-process communication, databases, green IT patterns
 
 // end::EN[]