Mediaspace scheduled maintenance: Aug 25, 2026 07:00 - 12:00 AM. During this time, videos will be temporarily unavailable. Check status updates.

Lecture

Star Aware Software for Cyber-Physical Systems

Description

This lecture by the instructor delves into the concept of cyber-physical systems, emphasizing the need for software to be physically aware to ensure system functionality. The discussion covers the challenges of wireless communication, sensor fusion, and environmental impacts on software design, highlighting the importance of addressing real-world properties in system development.

Official source

Related concepts (24)

Functional specification

A functional specification (also, functional spec, specs, functional specifications document (FSD), functional requirements specification) in systems engineering and software development is a document that specifies the functions that a system or component must perform (often part of a requirements specification) (ISO/IEC/IEEE 24765-2010). The documentation typically describes what is needed by the system user as well as requested properties of inputs and outputs (e.g. of the software system).

Non-functional requirement

In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviours. They are contrasted with functional requirements that define specific behavior or functions. The plan for implementing functional requirements is detailed in the system design. The plan for implementing non-functional requirements is detailed in the system architecture, because they are usually architecturally significant requirements.

Reliability engineering

Reliability engineering is a sub-discipline of systems engineering that emphasizes the ability of equipment to function without failure. Reliability describes the ability of a system or component to function under stated conditions for a specified period of time. Reliability is closely related to availability, which is typically described as the ability of a component or system to function at a specified moment or interval of time. The reliability function is theoretically defined as the probability of success at time t, which is denoted R(t).

Functional requirement

In software engineering and systems engineering, a functional requirement defines a function of a system or its component, where a function is described as a summary (or specification or statement) of behavior between inputs and outputs. Functional requirements may involve calculations, technical details, data manipulation and processing, and other specific functionality that define what a system is supposed to accomplish. Behavioral requirements describe all the cases where the system uses the functional requirements, these are captured in use cases.

Software quality

In the context of software engineering, software quality refers to two related but distinct notions: Software's functional quality reflects how well it complies with or conforms to a given design, based on functional requirements or specifications. That attribute can also be described as the fitness for purpose of a piece of software or how it compares to competitors in the marketplace as a worthwhile product. It is the degree to which the correct software was produced.

Related lectures (21)

Software Engineering: Methods and Tools

Explores software engineering complexity, UML, DSL, design patterns, agile development, and introduces the Arcimboldo tool.

Programming Bugs: Understanding, Fixing, and Preventing

Explores programming challenges, debugging techniques, software testing, and security practices in software development.

Robust Design: Trade-off Management in Mechanical Development

Emphasizes the importance of managing trade-offs for product robustness in mechanical design, using Multi-objective Monotonicity Analysis for quantitative analysis and systematic redesign efforts.

Validated-Aware Software

Explores validated-aware software for continuous system validation in safety-critical environments, emphasizing the importance of anticipatory real-time assurance and semantic-level validation.

From Tests to Proof