Professional practice
Systematic examination of software, data and process structures using technical and scientific criteria.
Methodical approach to technical analysis
Analysis and assessment form the core of technical expert work. Complex facts are examined on a technically traceable, evidence-based and methodically disclosed basis using appropriate methods from software engineering, systems analysis and Data Science.
Focus of the analysis
- Structural and functional examination of software architectures.
- Analysis of data models, interfaces and process flows.
- Collection and interpretation of technical metrics such as complexity, performance and data quality.
- Requirements-to-actual-state comparison against documented technical or professional requirements.
- Identification of technical risks, weaknesses and improvement potential.
Assessment criteria
Assessment criteria are defined before the conclusion is drawn. Functional properties can be considered alongside maintainability, security, efficiency, documentation and architectural quality. Where useful, technically justified options are described with their criteria, risks and limitations without pre-empting the responsible decision.
The evidence chain is kept visible: technical question → subject and system state → sources and data → method and criteria → finding → counter-hypotheses → interpretation → professional assessment → limitations and revision triggers.
Typical applications
- Software-project assessment in acceptance or dispute contexts.
- Analysis of complex IT systems, data platforms and integration architectures.
- Examination of machine-learning or AI components for quality and traceability.
- Technical audit of processes, interfaces and system states.
Reporting
The report documents criteria, measurements, findings, relevant alternative explanations and statement boundaries. A successful test, build or reproduced system state establishes only the documented technical finding under the examined conditions; it does not automatically establish acceptance, approval, legal permissibility or complete suitability.
Example scope of an assessment
- Examination of software architecture, source code and data structures.
- Evaluation of technical metrics and quality indicators.
- Assessment of processes, interfaces and documentation quality.
- Report with findings, professional assessment, limitations and technically justified options.
Indicative fee range: approximately €1,000–€3,000 net, depending on scope, system size and depth of analysis. The amount is for orientation only and is not a binding offer.
Related technical knowledge
Constructed case study: technical analysis and assessment
From a defined technical question through evidence and counter-hypotheses to a bounded professional assessment.
Constructed examination scenario: This is a methodological example, not a real mandate, a real court appointment or a report of actual findings.
Diagnosis – define system state and evidence
Establish the subject of examination, version, available data and the technical question. Separate observed symptoms from possible causes.
Objectives – set the assessment criteria
Define requirements, measurement criteria, tolerances and the technical properties that will be compared against the observed system state.
Analysis – collect reproducible findings
Use suitable software, data or systems-analysis methods and document measurements, sources, assumptions and alternative explanations.
Expert synthesis – assess against the reference
Separate finding, interpretation and professional assessment. State technical options and limitations without pre-empting the responsible management or legal decision.
Methodological inspiration: Nicolai Andler, Tools für Projektmanagement, Workshops und Consulting – Kompendium der wichtigsten Techniken und Methoden, 6th revised and expanded edition, Publicis, Erlangen, 2015, ISBN 978-3-89578-453-8. The examination sequence and expert synthesis used here are independently formulated for technical expert work.
Initial technical classification of an enquiry
Before accepting an assignment, the technical question, subject of examination, available records, potential conflicts of interest and the required scope are reviewed. An individual non-binding proposal can then be prepared.
Contact Mathias Ellmann