TECHNICAL ASSESSMENT
IT Expert for Legacy and Custom Software
Independent, traceable technical assessments for companies, clients, software providers and legal counsel – with a particular focus on long-established custom software.
WHEN IS AN ASSESSMENT USEFUL?
When technical questions become the basis for decisions.
With long-established software, it is often not immediately clear whether a problem is caused by a technical defect, a changed requirement, missing documentation or the system structure that has evolved over many years. A structured technical investigation creates a traceable basis for further decisions.
Delivered functionality
Which functions are actually available, and how do they compare with documented or agreed requirements?
Documentation
Are structure, functions, interfaces and technical relationships sufficiently understandable to a qualified third party?
Maintainability
Which technical dependencies, outdated components or critical areas make changes and reliable operation more difficult?
Effort
Are development, remediation or modernization efforts technically plausible, and which risks affect the estimate?
EXPERT SERVICES
From technical investigation to a clear assessment.
Technical software analysis
Investigation of the current software state.
- Source code and architecture
- Databases and data access
- Interfaces and dependencies
- Technology and operational risks
Target / actual comparison
Traceable comparison of requirements and delivered functionality.
- Functional scope
- Requirements documentation
- Identifiable deviations
- Technical classification
Documentation review
Assessment of existing technical documentation in the context of the system under review.
- System and program description
- Schnittstellen
- Data structures
- Traceability
Technical opinion
Structured presentation of the evidence basis, findings and professional assessment.
- Private expert report
- Technical second opinion
- Plausibility review
- Modernization assessment
APPROACH
Technical findings. Meaning. Assessment. Recommendation.
Technical details are not presented in isolation. What matters is what a finding means for operations, contractual performance, maintainability or an upcoming investment decision.
Question
Clearly define the subject of the review and the technical questions to be answered.
Evidence basis
Record the software state, source code, documentation and other evidence.
Investigation
Examine relevant functions, structures, dependencies and technical facts.
Assessment
Clearly separate findings from assumptions and professional assessment.
Report
Document results in a traceable way that non-technical decision-makers can understand.
Discussion
Explain results and answer outstanding technical questions in a structured manner.
PRACTICAL EXPERIENCE
Long-established software from a developer and leadership perspective.
I have been developing and taking responsibility for software solutions since 1987. A significant part of my career has involved specialized POS and industry systems that had to be continuously developed and kept reliable in day-to-day operations over many years. This experience forms the basis of my current specialization in legacy and custom software.
Transparency regarding expert status
Services are provided as an independent IT expert. I am currently not publicly appointed and sworn by a German Chamber of Industry and Commerce (IHK).
FOR IT LAWYERS
Competency profile as PDF.
The two-page profile summarizes use cases, approach and technical focus areas for IT-law mandates.
INITIAL ASSESSMENT
Which technical question needs to be answered?
In an initial conversation, we clarify the subject of the review, available documentation and whether an independent technical investigation can be carried out meaningfully.