the future of the german business register
play

The Future Of The German Business Register Keno Kuhlmann Rolf Knig - PowerPoint PPT Presentation

The Future Of The German Business Register Keno Kuhlmann Rolf Knig Principal Consultant Head of Project Group AuRegis Projectmanager AuRegis Head of Working Group RegisSTAR Atos IT Solutions and Services GmbH Director of the Local Court


  1. The Future Of The German Business Register Keno Kuhlmann Rolf König Principal Consultant Head of Project Group AuRegis Projectmanager AuRegis Head of Working Group RegisSTAR Atos IT Solutions and Services GmbH Director of the Local Court Coesfeld,Germany

  2. The Situation The German Business Register  16 States (Länder)  116 Courts  2 Business Register Systems  RegisSTAR  Aureg

  3. The History 1997  Founding of the Developer Network RegisSTAR and Aureg 1999  First test run of RegisSTAR 2003  Implementation of RegisSTAR in North Rhine – Westfalia 2007  Implementation of RegisSTAR and Aureg in all States 2011  AUREG-States decide to join RegisSTAR 2014  Start of the Work on AuRegis

  4. The Challenge

  5. The Challenge Can you modernize the electronical Business Register System within a local court system with differing regulatory frameworks in varying IT-Infrastructures for all 16 states of Germany?

  6. Challenges  Data Migration from Aureg and RegisSTAR Sum: 5.046.477

  7. Additional Challenges  3 IT-Infrastructures Reference Environment 1: Oracle Stack • Reference Environment 2: Microsoft Stack • Reference Environment 3: „ eAkte as a Service“ •

  8. Additional Challenges  Service-Oriented Architecture (SoA)

  9. Additional Challenges  Building Software Components in cooperation with the German Land Registry • User Authorization Administration • Person Administration • Document Generation • Logging • Administration of Dates and Deadlines • Cost & Fee Processing • Allocation of Duties Administration

  10. Additional Challenges  Serving different File Management Systems  Accessibility (BITV 2.0)  Serving different Infrastructure Components

  11. The Solution

  12. Boundary Conditions Parallele operation of migrated and legacy Multiple Register and registers existing and computer evolving people speak neighboring different systems languages  Multiple Constantly evolving AuRegis evolving plattforms register

  13. Reasoning + Conclusion Embrace Moving target constant Flexibility changes Create a Enable Missunderstandings supporting Use all channels Communication environment Inlining of Use of common Minimize Reduce Friction requierements open source dependencies and technology web technology Early and Constant Precise project intensive Visibility of test Optimization of and testing Automated tests envolvement of results solution and quality targets future users Anticipate Avoid dead end Give good ideas Use vital Look ahead problems roads a chance momentum

  14. On project execution 2016 2017 2018 2018 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 1 2 3 4 5 6 7 Projektinitialisierung Projektplanung AuRegis Iteration 1 Konzeption Entwicklung FT Test ST Meilensteinprüfung MSP Iteration 2 Konzeption Entwicklung FT Test ST Meilensteinprüfung MSP Iteration 3 Konzeption Entwicklung FT Test ST Meilensteinprüfung MSP Projektabschluss Schlusstest ST Abnahmetest AT dabag Iteration 1 ST M dabag Iteration 2 ST M dabag Iteration 3 ST M ST M dabag Iteration 4 dabag Iteration 5 ST M dabag Abnahme Schluss-ST Abnahme dabag c Stand: 24.10.2017

  15. On Communication Customer and Provider share the communication over all phases of the life cicle • Mix of online and on site  Meetings meetings • Training on UML and common Language elaboration of des. & doc.  Requirements Design • Milestone include a week of Synchronisazion common evaluation • Service matter experts amoung Domain knowledge the programmers Test Implementation • Search, Messaging, Object Extend SoA wisely Store, etc. Monitor • Take appropiate Action

  16. On technology  SQL databases for register data  Java for serverside logic  HTML5/CSS3/JS in form of Angular for clients  Elasticsearch, RabbitMQ, Redis, Jinja2  Interfaces REST or massive language support  Stay close to actual development, timely updates

  17. On Technology Example OpenAPI Specification

  18. On technology example responsive design

  19. On technology example Elasticsearch Definition Flexibility on • data • structure • Tokenizer • Language • Filters • Synonyms • Relevance Register • data Keywords • Stopwords • Scalability Without need to change the core system Search Results

  20. On technology example Jinja2 Durch rechtskräftigen Beschluss des Amtsgerichts {{ m.txt(label='Ort des Insolvenzgericht') }} vom {{ m.dt(label='Beschlußdatum') }} {{ m.txt(label='Geschäftszeichen des Insolvenzgerichts') }} wurde die Eröffnung des Insolvenzverfahrens über das Vermögen der Gesellschaft mangels einer den Kosten des Verfahrens entsprechenden Masse abgewiesen. Created by user {{ m.cb(option='Die Gesellschaft ist hierdurch aufgelöst. Gemäß § 60 Abs. 1 GmbHG i.V. § 65 Abs. 1 GmbhG von Amtswegen eingetragen.' )}} Seamless integration Into AuRegis

  21. On technology Example Justice workspace

  22. Questions Thank you! Questions?

Recommend


More recommend