EN 
DE Read on!
Embedded Software Redesign: Table of Contents
- Part I – The Decision
- Part II – Reverse Engineering: Untying Gordian Knots
- Part III – Refactoring: From Old to New
- Part IV – Reengineering: The journey is the destination
- Information Pool: Book Recommendations
- Information Pool: Tools and Web Tips
Part I: The Decision
At our events on the topic Software Redesign for Embedded Developers It quickly became clear from the discussions and contributions of the participants how pressing this issue is for many companies.
Software has evolved over decades under the constraints of real-time requirements, memory optimization, cost optimization, and project pressure, becoming increasingly complex. Now, many development teams are reaching the limits of familiar methods and procedures. It's no exaggeration to say they are searching for a breakthrough to restore order to the chaos.
We want to support you with our trend guide "Embedded Software Redesign".
Image 1: MicroJones polishes M2C2 after successful redesign
Balances, loans and interest on software quality accounts
The software dilemma can be vividly described using an analogy. Every development team has three quality accounts:
- the documentation account
- the architecture/source code account
- the process account
If everything has gone according to plan, these accounts will be well-funded. The documentation allows for quick orientation within the architecture and source code, and new employees can quickly familiarize themselves with the system. The software's architecture and source code can be extended easily and rapidly. The process ensures a smooth workflow from requirements gathering to commissioning at the customer's site.
Image 2: Embedded Software Redesign – Software Quality
Software quality accounts
A fairytale! Unfortunately, that's exactly what it is. A fairytale that's often told but rarely lived. Reality usually looks quite different and is more reminiscent of an action thriller: A few gifted "freaks" build a prototype. If there are customers for it, the software developer can always program everything "cleanly." But the customer wants more, something different, and faster. So the prototype is quickly "upgraded" into a product, and a few additional functions are hastily added. The team is well-coordinated, and the documentation is mostly stored in their heads. The architecture isn't optimal, but it still offers some room for more functionality. The process resembles virtuoso juggling of files and tools.
From the outset, the quality accounts are sparsely funded. Increasing complexity, the loss of key personnel, or team expansion quickly necessitate taking out loans to cope with project pressures. Despite good intentions, documentation is neglected, even though functionality has grown significantly. The architecture can only be expanded through dubious tricks and increasingly resembles a house of cards, threatening to collapse at the slightest breeze. The process largely consists of frantically patching things up instead of systematic approaches.
And as is the way with loans: interest accrues. After a short time, no one can keep track of the software anymore. More and more contortions and firefighting are required to stabilize it. The veterans are completely overwhelmed, and the newcomers are groping in the dark, eagerly but without much of a plan. Management is driving the developers with the outsourcing whip. In our scenario, the interest translates to lost time, lost quality, lost customers, lost money, no motivation—and frustration!
Dangerous loans
What is your account balance?
In our experience, savings accounts are usually depleted much faster than people realize. Don't let it get that far. The best approach is to avoid debt in the first place. The following measures are suitable for "debt repayment":
- Reverse Engineering improves the documentation
- Refactoring ensures a scalable software architecture and extensible source code
- Reengineering This leads to the necessary process adjustments.
In short: the 3 R's of software redesign!
Intensive care unit or pathology department.
Before you embark on your journey back to virtue and debt-free living with the help of the 3 R's, you should ask yourself the following question: Is all the effort worthwhile? Even if it sounds morbid, you need to find out if you…
- to keep the software alive,
- only want to reuse the usable parts,
- to dissect a software corpse in order to learn something for the future, or
- Bury everything and make a fresh start.
At least some members of the team undoubtedly have the nagging feeling that things can't continue as they are. However, any decision should be based on facts that make the situation tangible. This will also bring less sensitive individuals on board – especially management, who tend to view the matter through a more detached, business-oriented lens.
One thing must be clear from the outset: Building up quality accounts is an investment that initially comes at the expense of other accounts – such as productivity or profit. However, the interest we then receive on our quality accounts will soon recoup this investment in the form of shorter project durations and lower costs.
Download the complete trend guide as a PDF:
Embedded Software Redesign – German version
Embedded Software Redesign – English Version
MicroConsult supports you with training and coaching on all aspects of embedded software.design:
Requirements Engineering and Requirements Management for Embedded Systems
Software quality: Methods for successful project implementation
Software architectures for embedded systems and real-time systems
Embedded software design and patterns with C
UML basics and introduction to model-based software development
Object-oriented software development with C++ - the path to clean code
Object-oriented software development with C# – the path to clean code
Design patterns (not only) for embedded systems
Software erosion: causes, effects and measures
Training & coaching on the topics of our portfolio can be found here. here.
Furthermore, there is the possibility to explore the topic area Embedded Software Redesign also in tailor-made workshops to address. They are tailored to the specific needs of tasks, projects, teams, and roles.
Get in touch with us! Contact form
Download the complete trend guide
