diff --git a/docs/00b-basics/01-what-to-expect-of-this-module.adoc b/docs/00b-basics/01-what-to-expect-of-this-module.adoc index 2ea31c8..44bdc2c 100644 --- a/docs/00b-basics/01-what-to-expect-of-this-module.adoc +++ b/docs/00b-basics/01-what-to-expect-of-this-module.adoc @@ -4,8 +4,8 @@ // tag::EN[] === What does the module “{curriculum-short}” convey? -Embedded systems are computer systems that are integrated in a larger (often -mechatronic) system, via which they interact with the physical environment +Embedded systems are computer systems that are integrated in a larger +cyber-physical system, via which they interact with the physical environment through sensors and actuators. As the requirements concerning the functionality and the quality characteristics of these systems are increasing, the size and the complexity of embedded systems software grows considerably. diff --git a/docs/01-system-development/02-learning-goals.adoc b/docs/01-system-development/02-learning-goals.adoc index 82aa5f7..b29dbd6 100644 --- a/docs/01-system-development/02-learning-goals.adoc +++ b/docs/01-system-development/02-learning-goals.adoc @@ -67,9 +67,9 @@ for example with SysML or FAS <>.. [[LG-1-3]] -==== LG 1-3: Modelling and analysis of technical system architectures +==== LG 1-3: Modeling and analysis of technical system architectures -Participants understand the systematic approach to modelling and analysis of +Participants understand the systematic approach to modeling and analysis of technical system architectures: * Analyze the impact factors, like quality requirements, organizational diff --git a/docs/02-software-development/02-learning-goals.adoc b/docs/02-software-development/02-learning-goals.adoc index 071cc16..86d7df8 100644 --- a/docs/02-software-development/02-learning-goals.adoc +++ b/docs/02-software-development/02-learning-goals.adoc @@ -7,28 +7,28 @@ [[LG-2-1]] -==== LG 2-1: Modelling software for embedded systems +==== LG 2-1: Modeling software for embedded systems -Participants know different approaches for modelling software for embedded +Participants know different approaches for modeling software for embedded systems. They understand the basic concepts, strengths and weaknesses of these approaches: -* UML as a general purpose modelling language +* UML as a general purpose modeling language * UML profiles to adapt UML to a specific domain (e.g., MARTE as a UML profile - for modelling real-time systems) + for modeling real-time systems) * Graphical and textual domain specific languages (e.g., AADL) -* State machines for modelling reactive systems +* State machines for modeling reactive systems -* Modelling data- and signal-flows (e.g., function block diagrams) +* Modeling data- and signal-flows (e.g., function block diagrams) Participants understand how models can be used for analyzing the software, for examples with regards to failures (e.g., FTA / FMEA), schedulability, error propagation, and latency. -Participants are able to select a suitable modelling approach based on the +Participants are able to select a suitable modeling approach based on the requirements and boundary conditions of the system under development. diff --git a/docs/05-adaptability/02-learning-goals.adoc b/docs/05-adaptability/02-learning-goals.adoc index ed43315..c264496 100644 --- a/docs/05-adaptability/02-learning-goals.adoc +++ b/docs/05-adaptability/02-learning-goals.adoc @@ -25,7 +25,7 @@ Participants know high level approaches to adaptability and variability such as the 150%-model, 80%-model, product platforms or product lines. [[LG-5-2]] -==== LG 5-2: Modelling variability in the architecture +==== LG 5-2: Modeling variability in the architecture Participants understand how the separation between functional architectures and technical architectures can support adaptability and variability by allowing