Modernization of a Public-Sector Administrative Procedure
Requirements engineering and test management for a business-critical administrative procedure
AI Product Ownership with Hands-on PoC Practice
Business-oriented use-case prioritization, AI requirements engineering, evaluation, and guardrails – combined with delivery experience and practical RAG, LLM, and workflow validation.
Legacy -> Web
Migration from Oracle Forms/Reports to modern web architecture
MVP
Definition and prioritization of product-oriented scope
API-first
Functional preparation for React, Spring Boot, and OpenAPI
Public Sector
Digital administration with high traceability requirements
Modernization of a business-critical administrative procedure by replacing an Oracle Forms and Oracle Reports landscape with a modern web architecture. My focus is on requirements management, process analysis, MVP shaping, and quality assurance at the intersection of business stakeholders, engineering, architecture, and testing.
My role
Test Manager / Requirements Engineer / MVP Co-Lead
Tech Stack
React · Spring Boot · OpenAPI · Oracle Forms
Challenge
A business-critical legacy procedure has to move into a modern web architecture without losing domain-specific edge cases, regulatory requirements, traceability, or usability. At the same time, the MVP needs clear boundaries, testable requirements, and a durable quality strategy.
Solution
I support the functional shaping of the MVP through requirements engineering, process analysis, and close coordination with business stakeholders, engineering, architecture, and quality assurance. This includes user stories, acceptance criteria, gap analysis, business validation rules, risk-based test cases, and preparation of an API-first target architecture based on React, Spring Boot, and OpenAPI.
Project context
- Modernization of a business-critical administrative reimbursement procedure
- Replacement of an Oracle Forms and Oracle Reports landscape with a modern web architecture
- Public-sector environment with strong requirements around regulation, traceability, and accessibility
Project scope
- Requirements management and functional documentation of existing business processes
- Derivation of requirements from legacy systems and existing domain logic
- Creation and prioritization of user stories, acceptance criteria, and MVP scope
- Modeling of process logic, validation rules, edge cases, and regulatory requirements
- Definition of test strategy, test concept, and risk-based test cases for the MVP
- Interface role between business stakeholders, engineering, architecture, and quality assurance
Impact
- Analyzed existing business processes and derived durable requirements from legacy systems
- Created and prioritized user stories, acceptance criteria, and MVP scope
- Modeled domain logic, validation rules, and edge cases for digital application workflows
- Defined test strategy, test concept, and risk-based test cases for the MVP
- Acted as an interface between business stakeholders, engineering, architecture, and QA
- Covered accessibility, traceability, and regulatory requirements in a public-sector context
System Flow
Core Components
- React frontend and Spring Boot backend
- OpenAPI-based interface contracts
- Requirements, test, and traceability artifacts
- Reporting through Jasper Reports
Hard Decisions
- Protect domain continuity before replacing technology
- Define MVP scope together with testability
- Describe interfaces API-first
Guardrails
- Anonymize customer-specific details in public material
- Test regulatory edge cases and traceability explicitly
- Compare legacy and target behavior based on risk




