The Components of QUIBIF

  • Team-Model especially for Integration-Project teams
  • Process-Model especially for Integration-projects
  • Questionnaire and Checklists

QUIBIQ Business Integration Framework: QUIBIF

Integration projects are different from classical application development:

  • crossing by definition system bounderies and therefore, usually also corporate responsibilities
  • Less coding and more assembling and configuring single components (Schemata, Maps, Workflows etc.)
  • higher importance of rapid-prototyping and testing of individual components before completion of the overall solution
  • High degree of imponderabilities particularly at the start of the project
  • High pressure on standardization leading to adaptation expenditure with sides involved

Accordingly, project methods from developing applications cannot be transferred to the integration projects no matter if classic or even agile. Therefore, we developed the QUIBIQ Business Integration Framework (QUIBIF) on the basis of over 14 years of experience out of more than 400 integration projects.

QUIBIF is our project methodology especially for integration projects which makes sure that also complicated integration scenarios can be implemented successfully:

  • in time
  • in scope and
  • in budget

QUIBIF guarantees a systematic and at the same time agile approach


QUIBIF provides an appropriate, systematic and at the same time agile approach specifically for integration scenarios

  • Specific team structures  
  • Differentiated project plan outlines
  • Tools and checklists for every important step and milestone

Specific implementation process model


The implementation process model of QUIBIF is composed cyclically of the following project phases:

  • End-to-End-understanding of the mapped business processes  
    This serves the purpose of understanding the goals which should be achieved with the integration scenario
  • Mapping of processes to IT- components
    Provisional assumptions are made here to differentiate what function is provided from which system - It is possible to make chances at a later time
  • Deriving integrated requirements
    Specially developed Onboarding-Documents are used to determine the binding of each selected system and each process step in deriving the integration requirements
  • Integration architecture - development
    Based on the best practice experiences from various integration projects we developed the optimal integration architecture for the given and future possible scenarios
  • Integration project planning
    The planning of integration projects has to comply with the specific characteristics of integration projects (see above) thus, allowing for: 
    • Inclusion of all stakeholders
    • Living documents - fully transparent for all participants
    • Informed decisions on adapting to or deviating from standards
    • Prioritization of prototypical tasks : e.g. technical proof of cutting from system A to system B, fulfillment of performance requirements with planned quantity structure etc.
    • Building enough backlog for the development team, since frequent delays are to be expected due to missing/late customer provided information
    • Extensive unit and component testing during the development
  • Implementation
    The QUIBIQ Codex offers a specific guidance for implementing Integration solutions
  • Integration Tests
    Specific guidance for End-To-End testing to ensure the quality of an integration solutions
  • Deployment
    Extensive experiences with automated deployments also within heterogeneous infrastructures
  • Review
    quantitative and qualitative assessment of achieving the objectives by the solution thus evaluating the overall project success.

QUIBIF guarantees a systematic and at the same time agile approach


QUIBIF provides an appropriate, systematic and at the same time agile approach specifically for integration scenarios

  • Specific team structures  
  • Differentiated project plan outlines
  • Tools and checklists for every important step and milestone

Specific implementation process model


The implementation process model of QUIBIF is composed cyclically of the following project phases:

  • End-to-End-understanding of the mapped business processes  
    This serves the purpose of understanding the goals which should be achieved with the integration scenario
  • Mapping of processes to IT- components
    Provisional assumptions are made here to differentiate what function is provided from which system - It is possible to make chances at a later time
  • Deriving integrated requirements
    Specially developed Onboarding-Documents are used to determine the binding of each selected system and each process step in deriving the integration requirements
  • Integration architecture - development
    Based on the best practice experiences from various integration projects we developed the optimal integration architecture for the given and future possible scenarios
  • Integration project planning
    The planning of integration projects has to comply with the specific characteristics of integration projects (see above) thus, allowing for: 
    • Inclusion of all stakeholders
    • Living documents - fully transparent for all participants
    • Informed decisions on adapting to or deviating from standards
    • Prioritization of prototypical tasks : e.g. technical proof of cutting from system A to system B, fulfillment of performance requirements with planned quantity structure etc.
    • Building enough backlog for the development team, since frequent delays are to be expected due to missing/late customer provided information
    • Extensive unit and component testing during the development
  • Implementation
    The QUIBIQ Codex offers a specific guidance for implementing Integration solutions
  • Integration Tests
    Specific guidance for End-To-End testing to ensure the quality of an integration solutions
  • Deployment
    Extensive experiences with automated deployments also within heterogeneous infrastructures
  • Review
    quantitative and qualitative assessment of achieving the objectives by the solution thus evaluating the overall project success.
© 2017 QUIBIQ GmbH · AGB und Nutzungsbedingungen