Embedded systems are an important component of today's technologies and enable a wide variety of applications in diverse fields such as industry, automation, medical technology, automotive, and aerospace. These systems are designed to perform specific functions while adhering to required quality standards and are frequently integrated into larger systems or products. Establishing effective processes for requirements gathering and management is crucial for the success of an embedded system project.<\/p>\n
Article: Requirements Engineering and Management for Embedded Systems<\/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 People claim visible and invisible territories for themselves. Those who violate these boundaries are perceived as unpleasant or even threatening. These \u2013 often unintentional \u2013 territorial violations repeatedly lead to serious conflicts or disruptive friction in project work. A certain sensitivity to the territorial claims of our fellow human beings is therefore advantageous.<\/p>\n Article: Protecting project territories<\/a><\/strong><\/p>\n There's a key question when it comes to project success: How do successful teams emerge? This article provides answers that can be clearly derived from a systemic view of a team. It will become evident that one attitude and two skills are of particular importance. Unfortunately, these attitudes and skills don't simply appear out of thin air. Those who discover, practice, and internalize them in teamwork will be richly rewarded.<\/p>\n Article: Good Teams<\/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 Why did Corona hit us so hard? How do we get out of this crisis? To find answers to these questions, a few systemic considerations about survival are worthwhile. The exciting thing about systemic considerations is that we can apply them to many of the questions we're currently racking our brains over. Now things will get a little theoretical first, and then dramatic \u2013 with hope for a happy ending.<\/p>\n Article: Out of the dead end<\/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 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: How to correctly apply design patterns in practice<\/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 \u201e"What do I do if I don't have an answer to an employee's question or a solution to a problem?" Is it acceptable for a project manager to be perplexed or without a solution? Will they still be taken seriously? My answer: Yes, of course, if\u2026 And that "if" is what we'll be discussing today.<\/p>\n Article: Leading through process and communication skills<\/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 \u201e"We don't have problems, we have challenges." You've certainly heard this sentence before, or something very similar. I'll take it a step further, because these days you have to top what's already been said to drown out the constant background noise of clever platitudes. That's why I'm writing this sentence out loud, so it goes straight to your consciousness via your optic nerves: PROBLEMS ARE HIDDEN RESOURCES. Why is that?<\/p>\n Article: Problems are resources<\/a><\/strong><\/p>\n Who likes conflict? But if we take a realistic look at the world, or even just at our relationships with others, we realize that conflict is a part of life. It's a natural phenomenon of human coexistence and stems from the simple fact that people have different\u2014sometimes very different\u2014experiences, sensitivities, and needs. If we look closely, we find that the problem isn't the causes of the conflict, but rather how we deal with conflict situations.<\/p>\n Conference proceedings script: Conflicts as an opportunity (<\/span>ESE Congress 2017, PDF)<\/span><\/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 Presentation: Requirements \u2013 A checklist for maturity (ESE Kongress 2017, PDF)<\/a><\/strong><\/p>\n Conference proceedings script: Requirements \u2013 A checklist for maturity (PDF)<\/a><\/strong> Today I'm going to introduce you to a miracle cure that will save you a lot of energy, time, and money in your projects. At the same time, it motivates your employees. The application of this miracle cure has a lot to do with the letter W, as in miracle. The best part? It costs nothing, and you're all familiar with it.<\/p>\n Article: Asking the right questions for project success<\/a><\/strong><\/p>\n Episode 51:<\/strong>\u00a0<\/a>Why good teams don't fall from the sky\u00a0<\/strong>(12\/2021)<\/p>\n Episode 50:<\/a>\u00a0Out of the dead end: More flexibility, less optimization<\/strong>\u00a0(04\/2021)<\/p>\n Episode 49:<\/a><\/strong>\u00a0Managing crises through professional project management<\/strong>\u00a0(04\/2020)<\/p>\n Episode 48:<\/a>\u00a0What does project responsibility mean here?<\/strong>\u00a0(02\/2019)<\/p>\n Episode 47:\u00a0<\/strong><\/a>Misunderstanding, the loyal project companion<\/strong>\u00a0(05\/2019)<\/p>\n Episode 46:<\/a>\u00a0Leading through process and communication competence<\/strong>\u00a0(02\/2019)<\/p>\n Episode 45:<\/a>\u00a0Discover hidden resources, uncover concealed profits<\/strong>\u00a0(02\/2018)<\/p>\n Episode 44:<\/a>\u00a0What is crucial in decision-making?\u00a0<\/strong>(10\/2017)<\/p>\n Episode 43:<\/a>\u00a0Needs as a source of success and failure\u00a0<\/strong>(07\/2017)<\/p>\n Episode 42<\/a>:<\/strong> How differences enrich projects\u00a0<\/strong>(05\/2017)<\/p>\n Episode 4x<\/a>Asking the right questions leads to project success\u00a0<\/strong>(03\/2017)<\/p>\n Episode 41:<\/a>\u00a0Illusions and their impact on project work<\/strong>\u00a0(01\/2017)<\/p>\n Episode 40:<\/a>\u00a0Protect project territories<\/strong>\u00a0(10\/2016)<\/p>\n Episode 39:<\/a>\u00a0The essence of good project management<\/strong>\u00a0(08\/2016)<\/p>\n Episode 38:<\/a>\u00a0Project success through emotional culture<\/strong>\u00a0(03\/2016)<\/p>\n Episode 37:<\/a>\u00a0Hi, how did your project go?<\/strong>\u00a0(02\/2016)<\/p>\n Episode 36:<\/a>\u00a0Failed projects are a matter of luck.\u00a0<\/strong>(12\/2015)<\/p>\n Episode 35:<\/a>\u00a0How to better cope with project frustration\u00a0<\/strong>(10\/2015)<\/p>\n Episode 34:<\/a>\u00a0Systemic principles in project management\u00a0<\/strong>(02\/2015)<\/p>\n Episode 33:<\/a>\u00a0Realism instead of clairvoyance\u00a0<\/strong>(04\/2015)<\/p>\n Episode 32:<\/a>\u00a0Leading through process and communication competence<\/strong>\u00a0(10\/2014)<\/p>\n Episode 31:<\/a>\u00a0Project management between naivety and self-deception<\/strong>\u00a0(05\/2014)<\/p>\n Episode 30:<\/a>\u00a0What makes a good project manager<\/strong>\u00a0(02\/2014)<\/p>\nDesign for test and design for safety \u2013 Tailor-made software architecture<\/h3>\n
Protecting project territories: From dogs, cats, project managers, and bosses<\/h3>\n
Why good teams don't fall from the sky<\/h3>\n
Software development reimagined<\/h3>\n
Out of the dead end: More flexibility, less optimization<\/h3>\n
Embedded Software Redesign Guide<\/h3>\n
Interview: Clean Code and the ideal workflow for an embedded project<\/h3>\n
Applying Design Patterns Correctly in Practice<\/h3>\n
Save development time with design patterns<\/h3>\n
Quality requirements for embedded software<\/h3>\n
Leading through process and communication competence<\/h3>\n
Development processes as the basis of modern software development<\/h3>\n
Discover hidden resources, uncover concealed profits<\/h3>\n
Using conflicts as an opportunity<\/h3>\n
Requirements \u2013 A checklist for maturity<\/h3>\n
\n<\/a><\/p>\nAsking the right questions leads to project success<\/h3>\n
Food for thought<\/a>\u00a0On the topic of "The human side of project success":<\/h3>\n