Has your software grown over many years, does the knowledge sit in just a few people's heads, and does every change feel risky? Or are you facing a decision – further development, porting, a takeover or a new service provider – and need a sound basis for it? We take an independent look at your code and architecture and tell you clearly where your software stands and what needs to be done first.
When a Review Pays Off
- Bugs are piling up, and fixes cause new bugs.
- New features take longer and longer.
- You are taking over software from another team or service provider.
- You are planning a port, for example from .NET Framework to current .NET or from C++ to C#.
- You need to demonstrate security, for example under the Cyber Resilience Act.
What We Review
You choose what you need – individually or as a complete package.
Code Review
We read the code critically: readability, error handling, duplicate code, concurrency, handling of memory and resources. We work with C#/.NET, C++, WPF, LabVIEW and the programming interfaces of AutoCAD, BricsCAD and Revit.
Architecture Review
We examine the structure, modules and dependencies: is the software extensible, testable and portable? How cleanly are the user interface, logic, data storage and the connection to devices or controllers separated?
Test Coverage
We measure which parts are covered by tests and assess whether the important processes are among them. A high percentage alone says little – what matters is whether the risky areas are tested.
Static Analysis
We examine the code with analysis tools such as the Roslyn analysers for .NET, SonarQube, Cppcheck or clang-tidy. We review the results, weed out false positives and, if you wish, integrate the analysis permanently into your build.
Security Review
We look for components with known vulnerabilities, passwords and keys in the code, unvalidated input, overly broad permissions and missing encryption. For web components, we follow the OWASP Top 10.
Data Protection in the Code
Where does your software process personal data, who has access, and how is it deleted? We add this perspective on request – find out more under Data Protection and Secure Software Development.
How a Review Works
- Initial consultation: We clarify the goal, scope and questions and agree on what should be available at the end.
- Access: You give us access to the source code and documentation, under a non-disclosure agreement and on your own systems if you wish.
- Analysis: We review using tools and by hand and talk to your developers if anything is unclear.
- Report and discussion: We present the results and answer your questions.
- Implementation, if you wish: We fix the findings ourselves or support your team in doing so.
What You Receive
A report you can work with: findings ranked by urgency, each with an example from your code, a rationale and a recommendation. In addition, an estimate of the effort so that you can plan and decide. Where tests are missing, we show which ones should be written first – if you wish, we take care of building them as part of our test automation service.
Our review does not replace a penetration test by specialist providers. If one is planned, it helps you prepare for it in a targeted way.
From Our Projects
Before a customer approved the porting of an AutoCAD add-on that had grown over more than twelve years, we analysed the architecture and code and derived a cost-effectiveness analysis from them. For a measuring instrument manufacturer, we examined LabVIEW software that had grown over time for weak points and safeguarded it with unit tests. You can find both examples in our case studies and among our projects.
You can find all our quality and security services in the overview.
Your Next Step
Briefly describe your software and your question. We will propose a suitable scope for the review.
kununu