For a list of Products we need to start a Re-Writing Project or we start a full new project 

• check Business Architecture
  • What
    • ​Here we add a lot of Enterprise and Software knowledge 
    • The Analysts  have here the power as they are the voice for the business 
  • How
    • Business current working  
    • Business current issues and requests
    • Business added Values and Risks of possible options
    • Guide Business in selection of the option 
  • Delivery
    • Business accepted option 
    • Setup Roadmap 

 

• check Enterprise architecture 
  • What
    • Here we check the current option with the colleagues
    • check setup and implementation and guidelines constraint
  • How
    • Business Risks and Added Value 
    • Technical Risks and Added Value 
    • Enterprise Risks and Added Value 
    • Enterprise setup of the decision 
  • Delivery 
    • Schema of implementation of the project in the Enterprise 
    • Schema of communication with projects / businesses and deliveries 
    • Guidelines for the software / project team 

 

• check Software architecture 
  • What
    • listing stakeholders and dependencies
    • System implanting into the enterprise 
  • How 
    • listing Technical and business requirements 
    • listing stakeholders and dependencies 
      • Transversal use of components ( re-use - SOLID ) 
    • Build Roadmap
      • Plans on Platform and Server Level 
      • communication with the other stakeholders/ dependencies 
  • Delivery 
    • Roadmap 
    • Guidelines 
    • Onboarding lists for the dependencies
    • onboarding documentation for the stakeholders

 

• Communication with application Architect 
  • What
    • Tech lead or application Architect of the project team will take over here and will create the InfraReq's, releases and technical decisions within the created Architectures.
  • How
    • collaboration with 2 weekly follow-up moments
  • Why
    • For some projects the analyses are delivered in a Agile way, what means that sometimes analysis sequences question the current architecture 
    • The use of Transversal components have their own Roadmap on changes and implementations so also upon that level we need to have our own Roadmap  

Fiscal Landscape 

• a Generic Payment project
  
• a Fiscal project generating Fiscal documents
  
• a Fiscal project that connects internal and External projects together for payments of Commissions

Transversal Landscape 

• Document Forwarding and management system 
• servicebus use 

Fraud Control 

• follow up of the rewrite of the main Fraud control application 
• follow up of the rewrite of the Fraud control enrichment of the data 

Small Common library to enable Identification of the Issuer of an OAuth Token and use the correct Tenant Information to work further with the application using the 'Tenant' information 

• An UserToken is always delivered from 1 IDP ( Issuer ) 
• A Tenant has 
  • a dedicated Database Connection 
  • a Tenant Name 
  • a list of trusted IDP's 
• using this mix of information this library helps the developer to retrieve the Tenant information using the Issue of the UserToken and the Tenant information given by accessing the application.
• Authentication and authorization are not the goal of this library 
  
  

Small Common library to validate Iban values. 

The Code is generated by the Finance Team, Second line support and updates are also followed up by them.
The documentation and examples should enable First line support and initial use of the library.

For a secured Project that is running outside the Riziv/Inami environment we need to set up a connection method towards an internal hosted project 
* WebApi
* Riziv-KeyCloak ( needed for this call )
* application running JWT - AFDS upon Environment

For the needed new version of the VTIM application I'm asked to make the Application Architecture. 

For Artikel 192 I'm asked to make the Application Architecture