FBCM
Function-Based Configuration Management
“A revolutionary approach to software versioning that transcends traditional file-level version control.”
The Traditional Challenge
Traditional version control systems like SCCS, Git, and VCS track changes at the file level. Each modification creates a new version of an entire file, regardless of how small the change.
This linear approach forces developers to branch code, merge conflicts, and maintain multiple codebases—creating complexity that grows exponentially with team size.
Because changes are not linear, there's no need to branch code. There is only one codebase.
The FBCM Philosophy
A Fundamental Shift in Perspective
Traditional Approach
- Files are versioned
- Changes tracked linearly
- Branches multiply
- Merge conflicts inevitable
Function-Based Approach
- Features are versioned
- Lines of code grouped by purpose
- Single codebase
- True parallel development
Function-based configuration management views software not as a collection of files, but as a set of features working together. Each feature comprises specific lines of code, tagged and tracked as a cohesive unit.
How Function-Based CM Works
Tag Code Lines
Individual lines of code are tagged to implement a specific feature or function.
Define Feature Sets
Software or documents become collections of features, each with its own lifecycle.
Compose Builds
Select which features to include or exclude for any particular build or release.
Deploy Flexibly
Create any combination of features and fixes without branching or merging.
Key Benefits
Unlimited Build Flexibility
Compose any combination of features and fixes for each release without branching constraints.
Non-Linear Development
Changes to files don't follow a linear path—features evolve independently on their own timelines.
Single Codebase
Eliminate the complexity of multiple branches—maintain just one authoritative source of truth.
Parallel Collaboration
Multiple developers work on the same files simultaneously without impacting each other's features.
Supporting Diverse Feature Lifecycles
Every feature has its own development lifecycle—some short, some long. FBCM accommodates this natural variability without forcing artificial synchronisation points.
Quick Fix
2-3 daysCritical bug resolved and deployed rapidly
Minor Enhancement
2-4 weeksSmall feature with limited scope
Standard Feature
2-3 monthsTypical development cycle for new functionality
Major Initiative
6-12 monthsLong-term strategic feature development
Who Benefits from FBCM
For Architects
Cleaner system design without branching complexity. Focus on features and intent rather than file management.
For Release Managers
Unprecedented flexibility in build composition. Create exactly the release you need, every time.
For Developers
True parallel development with reduced conflicts. Work on the same files without stepping on toes.
Get in touch
We use cookies to ensure that we give you the best experience on our website. By continuing to browse, we assume that you consent to receiving all cookies on this website. Learn more