Presentation of the implementation of the configuration and integration of business and infrastructure software to protect resources and ensure availability and integrity.
Define and maintain descriptions and relationships among key resources and capabilities required to deliver IT-enabled services. Include collecting configuration information, establishing baselines, verifying and auditing configuration information, and updating the configuration repository.
The configuration and integration management model defined here, consider when the effect of cumulative customizations and configurations (including minor changes that were not subjected to formal design specifications) requires a high-level reassessment of the solution and associated functionality.
The model ensure the interoperability of solution components with supporting tests, preferably automated and supports the employment, as appropriate, of code inspection, of test-driven development practices, of automated testing of continuous integration regarding all the changes developed on software components.
The pipelining component approach is implemented for each feature development that can require the evolution of one or several source codes regarding one or several IT components (eg applicative software, system image, infrastructure setting, deployable system).
A pipeline execution regarding a component evolution can generate a cascade of impacts through Team level > Domain level > Architecture level > System level > Production level.
Each IT component that can be released and deployed like a IT system should be “pipelinable”, so can be processed by a full build/test/deploy pipeline managed via the continuous integration (CI) chain and through the continuous delivery (CD) chain.
The CYBNITY branching strategy model supporting the CYBNITY software coding, build and delivery is implemented with several branching strategies.
Main branch of the repository regarding a software component perimeter (e.g software system, infrastructure element, software library) in which exist the latest stable code of production delivered (e.g MASTER environment as last stable version delivered to final users).
Practices and usage rules requirements: