Software quality is unfortunately still too often reduced to the formula: "As long as it works!" But anyone with experience working with software that has evolved over years knows the unpleasant consequences of this one-sided view. Precisely because software can be quickly changed and expanded over a long period, its quality must be given special attention.<\/p>\n
Expertise: Software quality is both the means and the goal of successful software development.<\/strong><\/a><\/strong><\/p>\n In today's interconnected world, embedded systems are ubiquitous \u2013 from automobiles and industrial controls to IoT devices. But with increasing connectivity, security risks also rise. Cyberattacks, data leaks, and insecure implementations can have serious consequences. So how can security risks be minimized and robust systems developed? The answer lies in solid security foundations.<\/p>\n Article: Security challenges for embedded systems<\/strong><\/a><\/p>\n Fields marked with\u00a0make<\/em>\u00a0it easier for developers to integrate Test-Driven Development into embedded projects \u2013 without the complexity of Google Test, without time-consuming porting, and free to download.<\/p>\n Article: wogtest is the innovative MicroConsult solution for embedded software testing<\/a><\/strong><\/p>\n Black-box tests using white-box metrics do not result in gray-box tests. However, each of the three fulfills an important function in defining the end of the test and minimizing the number of necessary software tests.<\/p>\n Post: Test ended well, all is well.<\/a><\/strong><\/p>\n Our everyday lives are now seamlessly integrated with interconnected devices and systems. Whether using a smartphone to find the fastest route, reading the newspaper on a tablet while relaxing on the sofa, or controlling smart heating via a smartphone app, these systems make our lives more comfortable. However, this increased comfort also necessitates stricter security and safety requirements, which the developers of such systems must meet. This is especially true for autonomous driving \u2013 where sound safety concepts are of paramount importance.<\/p>\n Article: Design for Test and Design for Safety<\/a><\/strong><\/p>\n Every year, new and even more powerful microcontroller architectures are announced. This paves the way for increasingly convenient and even autonomous transportation devices for our everyday lives. Besides the increased computing power \u2013 MIPS per watt \u2013 the enormous demands on safety and security are one of the biggest challenges.<\/p>\n Article: Trends in microelectronics<\/a><\/strong><\/p>\n The rapid growth of the Internet of Things, the 5G network, artificial intelligence and cloud or edge computing has a major impact on the development of embedded software.<\/p>\n Part 1: How multicore, safety & security aspects are changing today's software projects<\/a><\/strong><\/p>\n Part 2: Avoiding typical errors with comprehensive software requirements<\/a><\/strong><\/p>\n Part 3: Software Architecture<\/a><\/strong><\/p>\n What goals, requirements, and guidelines serve as the basis for a shared understanding of the cybersecurity perspective in the development of road vehicles? How are the processes defined and the risks managed in accordance with ISO 31000?<\/p>\n Article: A common language for cybersecurity<\/a><\/strong><\/p>\n Test-Driven Development (TDD) is the implementation of the test-first approach in component testing and involves writing unit test cases before the actual implementation. Adherence to just three rules and a few tricks for dealing with the target hardware bottleneck makes TDD possible even for embedded systems.<\/p>\n Article: Test-Driven Development of Embedded Systems<\/a><\/strong><\/p>\n Many agile development frameworks emphasize the test-first approach, which, regardless of the test level, is based on starting with testing as the first step towards the actual implementation of functionality: testing at a point when one is still focused on the "what" and the "how" is still pending. Test-Driven Development (TDD) is the implementation of the test-first approach in component testing and means writing unit test cases before the actual implementation. Adherence to just three rules and a few tricks for dealing with the target hardware bottleneck also make TDD possible for embedded systems.<\/p>\n Presentation slides: Test-First = Test first, think later (ESE 2019, PDF)<\/a><\/strong><\/p>\n Conference proceedings script: Test-First = Test first, think later (ESE 2019, PDF)<\/a><\/strong><\/p>\n The Armv8-M architecture brings fundamental security to Cortex-M devices, thus enabling greater protection for IoT systems. But how does the \u201cSecure Exception Priority Boosting\u201d feature perform in practice?<\/p>\n Article: More design flexibility through Secure Exception Priority Boosting<\/a><\/strong><\/p>\n Sometimes simply extending old code isn't enough: a complete overhaul is needed. This series of articles describes the process of embedded software redesign and explains the concepts of reverse engineering, refactoring, and reengineering.<\/p>\n Article: Embedded Software Redesign Guide<\/a><\/strong><\/p>\n In object-oriented software architecture and design, as well as in object-oriented programming (OOP) as a structured software development methodology, similar tasks and problems repeatedly arise. The use of reusable design patterns (proven solution templates) can prevent repetitive software programming efforts.<\/p>\n Article: Clean Code and the ideal workflow for an embedded project<\/a><\/strong><\/p>\n Just as dragons plagued humans and threatened their lives in ancient myths, today technically unsafe systems pose a source of danger. The crucial difference: while dragons belong to the realm of fables, technical systems as potential sources of danger are part of our everyday lives.<\/p>\n Article: Taming the Dragon \u2013 Secure Software from the Start<\/a><\/strong><\/p>\n Design patterns are solutions for frequently recurring tasks in object-oriented software design. In this sense, they play a similar role to the multiplication tables, which one learns by heart to avoid having to recalculate the results of frequently occurring arithmetic problems every time.<\/p>\n Article: How to correctly apply design patterns in practice<\/a><\/strong><\/p>\n In a highly interconnected world, it is advisable to effectively protect applications against cyberattacks. This requires optimal encryption of data and communication channels. However, the cryptographic algorithms used in software do not always reliably protect devices directly exposed to attacks. A turnkey solution offers a potential way to better protect information.<\/p>\n Article: Secure IoT smart grids through modular hardware security<\/a><\/strong><\/p>\n In object-oriented software architecture and design, as well as in object-oriented programming (OOP) as a structured software development methodology, similar tasks and problems repeatedly arise. The use of reusable design patterns (proven solution templates) can prevent repetitive software programming efforts.<\/p>\n Article: Saving development time with design patterns<\/a><\/strong><\/p>\n Capturing and managing requirements is a key to project success. Embedded software functionality is easier to describe in requirements than quality attributes. However, quality attributes cannot simply be "tested in" at the end. The more abstract they are, the more complex and time-consuming they are to define. What challenges does this pose for a project?<\/p>\n Article: Quality Requirements Part 1 \u2013 Requirements and Myths<\/a><\/strong><\/p>\n Article: Quality Requirements Part 2 \u2013 The Recording Method<\/a><\/strong><\/p>\n Article: Quality Requirements Part 3 \u2013 A Data Collection Example<\/a><\/strong><\/p>\n Lectures, articles, and books constantly emphasize that code quality is a crucial factor in a project's success. Therefore, there are ongoing attempts to introduce regulations that improve code quality. However, the code delivered by many developers is anything but elegant. One approach to ensuring code quality is the use of programming guidelines.<\/p>\n Article: Programming guidelines \u2013 curse or blessing?<\/a><\/strong><\/p>\n Capturing and managing requirements is a key to project success. Embedded software functionality is easier to describe in requirements than quality attributes. However, quality attributes cannot simply be "tested in" at the end. The more abstract they are, the more complex and time-consuming they are to define. What challenges does this pose for a project?<\/p>\n Presentation: Quality requirements for embedded software, ESE 2018 (PDF)<\/a><\/strong><\/p>\n In professional software engineering, the development and process steps prior to software implementation are essential. Terms like software analysis and software design, or high-level software design and detailed software design from development processes (for example, the V-Model XT or the industry-specific V-Model Automotive), represent precisely this.<\/p>\n Article: Development processes as the basis of modern software development<\/a><\/strong><\/p>\n The Internet of Things (IoT) is multiplying the risks of hacking attacks, as every network-connected device is a potential entry point. Peter Siwon, Business Development Manager at MicroConsult, and Michael Schnelle, Consultant at Mixed Mode, describe the biggest risks and explain protection strategies in this interview.<\/p>\n Article: Security in the IoT<\/a><\/strong><\/p>\n Capturing and managing requirements is a key to successful projects. Whether in a traditional or agile process environment, professional requirements engineering and management for embedded and real-time systems shortens your project timelines and saves on development and maintenance costs. Take on this challenge!<\/p>\n Article: Requirements Engineering and Management<\/a><\/strong><\/p>\n A holistic approach and a thorough understanding of the details are essential when it comes to creating functionally safe systems. Software integrity can be achieved through structured and targeted methods and techniques.<\/p>\n Article: Functional safety through structure and processes<\/a><\/strong><\/p>\n Software and hardware developers appreciate the Safety Management Unit of the Aurix microcontrollers as an independent unit for error handling.<\/p>\n Article: Safety concepts for Aurix<\/a><\/strong><\/p>\n Successful embedded software is usually developed over a long period. During this process, relationships may occasionally be introduced into the code that don't belong there. Over time, the software deviates increasingly from the planned architecture \u2013 software erosion is well underway.<\/p>\n Article: Indications of impending software erosion<\/a><\/strong><\/p>\n Adding security to existing embedded systems is not only costly but also methodologically flawed. Instead, security should be an integral part of the development process. The only question is which methods and concepts should be used to achieve security. Secure Design Patterns for software aim to demonstrate widely accepted and relevant solutions.<\/p>\n Presentation \u2013 Secure Design Patterns, ESE Congress 2017 (PDF)<\/a><\/strong><\/p>\n The operational reliability of software-intensive embedded systems is closely linked to protection against unauthorized access or targeted attacks. The necessary measures pose significant challenges for both software and hardware developers.<\/p>\n Article: Safety & Security Methods<\/a><\/strong><\/p>\n The demands placed on safety-relevant control systems are constantly increasing. Multicore architectures are best suited to handle these tasks and are therefore being offered and used more frequently. Article: Safety and Security in Multicore Systems<\/a><\/strong><\/p>\n Many technological success stories are based on the evolutionary principle of emergent properties. This states that by networking units into a system, this system generates new properties and capabilities that did not previously exist and were possibly unpredictable.<\/p>\n Technical knowledge: The Internet of Things (IoT)<\/a><\/strong><\/p>\n Safety and security describe different properties of embedded software systems. However, a closer look reveals how closely the operational reliability of software-intensive embedded systems is linked to protection against unauthorized access or targeted attacks. The necessary measures pose significant challenges for both software and hardware developers.<\/p>\nSecurity challenges for embedded systems<\/h3>\n
Simple and clever: wogtest is the innovative MicroConsult solution for embedded software testing.<\/h3>\n
Test ended well, all is well.<\/h3>\n
Design for test and design for safety \u2013 Tailor-made software architecture<\/h3>\n
Trends in microelectronics: New perspectives and requirements for mobile devices<\/h3>\n
Software development reimagined<\/h3>\n
A common language for cybersecurity<\/h3>\n
TDD \u2013 Test-Driven Development of Embedded Systems<\/h3>\n
Test-First = Test first, think later? \u2013 Test-Driven Development of Embedded Systems<\/h3>\n
More design flexibility through Secure Exception Priority Boosting<\/h3>\n
Embedded Software Redesign Guide<\/h3>\n
Interview: Clean Code and the ideal workflow for an embedded project<\/h3>\n
Secure software from the start \u2013 developers under time pressure<\/h3>\n
Applying Design Patterns Correctly in Practice<\/h3>\n
Secure IoT smart grids through modular hardware security<\/h3>\n
Save development time with design patterns<\/h3>\n
Quality requirements for embedded software<\/h3>\n
Programming guidelines \u2013 curse or blessing?<\/h3>\n
Quality requirements for embedded software: The art of watertight quality requirements<\/h3>\n
Development processes as the basis of modern software development<\/h3>\n
IoT security: "The biggest risk is the human element"<\/h3>\n
Requirements engineering and management<\/h3>\n
Functional safety: Mitigating systematic errors through structure and processes<\/h3>\n
Safety concepts for Aurix microcontrollers<\/h3>\n
Warning signs of impending software erosion and what you can do about it<\/h3>\n
Secure Design Patterns<\/h3>\n
Safety & Security: Relying on known and proven methods<\/h3>\n
Safety and security in multicore systems: How to successfully implement them<\/h3>\n
\n<\/strong><\/p>\nThe Internet of Things \u2013 a breeding ground for new opportunities and risks<\/h3>\n
Trend Guide \u201eEmbedded Safety & Security\u201c<\/h3>\n