Administrator: Add English DGB 3 translation

2026-09-11T17:50:49Z

Add English DGB 3 translation

Neue Seite

{{DISPLAYTITLE:DGB 3: Cloud-based Systems}}
← [[DGB 3. Klasse/en|Digital Literacy – Year 3]]

Cloud storage, e-mail, online calendars, learning platforms and collaboratively edited documents appear simple on the user's device, while data and services actually run on remote servers. This enables synchronisation and collaboration but also creates dependencies, access-control questions and responsibilities for data protection.

== Curriculum reference ==

{| class="wikitable"
! Area !! Classification
|-
| '''Competence area''' || Information
|-
| '''Perspectives''' || T, G, I
|-
| '''Focus''' || Understanding and critically evaluating cloud-based systems
|-
| '''Competence''' || Explain cloud-based systems at a basic technical level and consider server location, privacy, data security, sharing, dependencies and responsible use.
|}

== Learning objectives ==

Students can:

* distinguish local from cloud-based storage;
* explain how data is stored and retrieved on remote servers via the internet;
* name typical cloud applications used in everyday life, school and work;
* explain synchronisation and version history;
* distinguish sharing links, roles and access permissions;
* consider server location and provider responsibility;
* identify privacy and data-security risks;
* describe dependence on connectivity and provider availability;
* use cloud services with deliberate file organisation, permissions and backups.

== Learning content ==

=== Basic idea of cloud systems ===

A cloud service provides storage or computing functions on remote infrastructure. The user accesses the service over a network rather than relying only on files stored on the local device.

=== How cloud systems work ===

A client connects to a provider's servers, authenticates where required and sends or retrieves data. Replication, synchronisation and distributed infrastructure may be used behind the scenes.

=== Applications in everyday life, school and work ===

Cloud services include file storage, e-mail, calendars, learning platforms, collaborative documents and web applications. Their value often comes from access across devices and shared work.

=== Benefits ===

Advantages can include availability from different devices, easier collaboration, version history and central backup functions. These benefits depend on correct configuration and a reliable provider.

=== Limits and dependencies ===

Internet outages, service disruptions, account problems or provider changes can block access. Important work may therefore require additional local or independent copies.

=== Server location ===

The physical or legal location of servers can affect which rules, contracts and data-protection requirements apply. Users may not always know where every copy of a file is stored.

=== Privacy and data protection ===

Cloud use may involve personal or school-related information. Data minimisation, suitable services and careful permissions are especially important for sensitive content.

=== Data security and protection ===

Strong authentication, multi-factor authentication where available, encrypted connections, updates and backups reduce risk. Sharing settings should be reviewed regularly.

=== Responsible everyday use ===

Clear file names, folder structures, version control and least-necessary access rights make cloud collaboration safer and easier to manage.

== Classroom activities ==

=== Trace the path of a file ===

Draw the route from a local device to a cloud service and back.

'''Expected outcome:''' A labelled client–network–server diagram.

=== Compare local and cloud storage ===

Evaluate access, collaboration, privacy, resilience and cost.

'''Expected outcome:''' A comparison table.

=== Check sharing permissions ===

Use prepared examples to distinguish private, link-only, read, comment and edit access.

'''Expected outcome:''' A permission plan.

=== Assess privacy scenarios ===

Decide which types of data are suitable for a given school cloud scenario and which require extra protection.

'''Expected outcome:''' A reasoned decision.

=== Consider server location ===

Explain why server location and contractual responsibility may matter.

'''Expected outcome:''' A short analysis.

=== Identify security gaps ===

Find weak passwords, public links or missing backups in a fictional setup and correct them.

'''Expected outcome:''' A security checklist.

=== Plan cloud collaboration ===

Design a folder structure, naming rule, access roles and backup method for a group project.

'''Expected outcome:''' A collaboration plan.

=== Discuss stakeholder perspectives ===

Compare the interests of users, school, provider and data-protection authority.

'''Expected outcome:''' A stakeholder map.

=== Evaluate a cloud service ===

Use agreed criteria to assess one service or a fictional service description.

'''Expected outcome:''' A criteria-based recommendation.

=== Reflect on dependence ===

Explain what would happen to a project during an internet or provider outage and how to prepare.

'''Expected outcome:''' A resilience plan.

== Self-check ==

* I can distinguish local and cloud storage.
* I can explain the basic client–server idea behind cloud services.
* I can use permissions deliberately.
* I consider privacy, security and server responsibility.
* I understand synchronisation and version history.
* I can plan backups and alternatives for important data.

== See also ==

* [[DGB 3: Informations- und Datensuche/en|Independent Information and Data Search]]
* [[DGB 3: Veroeffentlichung und Schutz/en|Publishing and Protecting Information]]
* [[DGB 3: Viren und Schadsoftware/en|Viruses and Malware]]

[[Kategorie:Digitale Grundbildung]]
[[Kategorie:DGB 3]]

DGB 3: Cloudbasierte Systeme/en - Versionsgeschichte

Administrator: Add English DGB 3 translation