Case SPA U14: Custom UIs and Logic, One Core System? How Software Platform Anatomy Enables Scalable Variants 💲

Category 4: UI, Channels & Customer Experience Series

Title: Rethinking Requirements – How the ICMG Software Platform Anatomy Makes Lending Systems Change-Ready

Key Variables Impacted: UI, Rule, Function, Data, Network

Perspectives Covered: Strategy, Business Process, System, Component Specification, Implementation, Operations

Custom Screens. Custom Logic. One Core System.

Your platform serves dozens of institutional clients. Each has:

• A different onboarding screen.

• Custom eligibility rules.

• Branded dashboards.

• Specialized workflows for approval or document upload.

Yet underneath, it’s the same product.

When it’s time for a platform release:

• One client’s change breaks another’s UI.

• A shared component fails due to unexpected variant behavior.

• QA spends weeks revalidating every permutation.

The goal is reusability—but the result is regression fatigue. The problem? Variant behavior isn’t modeled—only coded.

Why Conventional SDLC Approaches Fail

Problems Across the Platform

• UI Breaks During Shared Deployments: A global CSS or JavaScript change breaks branding for one client, layout for another.

• Inconsistent Logic Across Channels: Web and mobile versions behave differently—sometimes even across devices for the same client.

• Confusion About What Changed and Why: Teams struggle to trace whether a UI bug is from a shared rule change, a custom function, or platform behavior.

• Overtesting, Yet Undercoverage: Testers retest everything—because they don’t know what’s safe to ignore.

Root Causes

1. No UI-to-Rule Mapping: Variant-specific screens are not tied to the logic they trigger—no formal modeling of interdependencies.

2. Hardcoded Branches: Client-specific logic is conditionally scattered across code rather than managed as components.

3. Function-UI Coupling: UI and logic evolve together in silos, making separation difficult during releases.

4. Lack of Multi-Variable Coordination: UI changes aren’t aligned with related rule, data, and network elements.

   
   

Applying the ICMG Software Platform Anatomy (Project Edition)

With ICMG, UI variants aren’t just handled—they’re modeled.

• Components are scoped by Rule, Function, UI, and Network variables.

• Cross-channel behavior is governed, not improvised.

• Shared and custom elements are traceable—architecturally.

Instead of testing everything every time, you test what the model tells you actually changed.

Strategy Perspective

Business Driver:Deliver tailored customer experiences per client without compromising platform stability.

Strategic Intent:Support scalable customizations through traceable, governed architecture—not ad hoc exceptions.

5. Business Process Perspective

Processes Impacted:

• Customer Onboarding

• Loan Eligibility Display

• Document Upload & Verification

• Application Tracking

• Client-Specific Dashboard Workflows

Observation:Even if the underlying process is common, its UI logic and flow may differ per client. ICMG ensures these differences are architected, not just coded.

System / Subsystem Perspective (by Variable)

Variable Sub Systems	Subsystems Involved
UI Sub Systems	Onboarding UI, Mobile Dashboard, Branding Renderer
Rule Sub Systems	EligibilityEngine, DisplayControlRuleMapper
Function Sub Systems	ApplicationProgressService, CustomFormLogicHandler
Data Sub Systems	ClientProfileDataStore, UIContentTemplateRepo
Network Sub Systems	BrandingCDN, FormSubmissionAPI, VariantSyncManager

Observation:Multiple variables influence UI behavior—ICMG enables change-aware modeling across them all.

Component Specification Perspective

a) Single-Variable Component Impact

Variable Sub System Components	Component Name	Role
UI Sub System Components	VariantOnboarding.vue	Displays client-specific onboarding steps
Rule Sub System Components	DisplayControlRules	Controls UI visibility by client config
Function Sub System Components	StatusBarLogicHandler	Drives dashboard progress indicators
Network Sub System Components	ThemeAssetCDNConnector	Delivers branding assets to UI

b) Multi-Variable Component Impact

Variable Sub System Components	Component Name	Role
UI + Rule Sub System Components	FormVariantResolver	Determines which form fields to show based on rules
UI + Function Sub System Components	DashboardTileController	Dynamically renders sections based on customer logic
UI + Network Sub System Components	RemoteThemeApplier	Pulls theme variants based on client ID from external store

Observation:Instead of cloning UI modules for each client, ICMG supports variant logic through traceable components.

Implementation Perspective (Mapped by Component)

Component	Implementation Task
VariantOnboarding.vue	Build component to accept config-driven step ordering and visibility flags
DisplayControlRules	Define rule-to-client mappings and update rule metadata versioning
FormVariantResolver	Model all field-level dependencies for custom client flows
RemoteThemeApplier	Configure and cache client-specific themes from CDN with fallback logic
DashboardTileController	Implement logic to toggle tiles based on rule + function component interaction mappings

Observation:Implementation becomes precise and targeted—variant impact is no longer hidden or guesswork.

Operations Perspective (Linked to Business Processes)

Business Process	Operational Validation Activities
Onboarding	Validate flow and UI elements per client config
Client Dashboard Experience	Confirm tile availability and data accuracy against business rules
Branding Delivery	Check theme loading speed, fallback behavior, and channel-specific rendering

Observation:Operations validate what matters per client—not platform-wide regressions every time.

Cascading Impact of the Change

Level	Example Impact
Strategy	Enables multi-client customization without platform instability
Process	Onboarding, eligibility, and tracking UIs behave per client expectations
System / Subsystem	Shared subsystems coordinate via traceable rule, data, and UI logic
Component Specification	UI logic modularized and versioned across clients
Implementation	Developer tasks scoped to the variant component, not monolithic redesigns
Operations	Support teams manage fewer surprises and more predictable validation
Cross-Variable Effects	UI changes understood and governed across rule, data, and network dependencies

Scalable UI Customization Needs Modeled Architecture

Supporting unique client logic and design shouldn't feel like threading needles across brittle modules.

With ICMG Software Platform Anatomy:

• UI behavior is governed across architecture variables.

• Logic is modeled, not duplicated.

• Customization becomes a platform strength—not a testing burden.

Need to scale your platform without cloning UIs and logic per client?

Explore the ICMG Fast Track Rating and Software Select Program]to deliver customer-specific experiences at scale—without platform fatigue.

Because platform stability and client customization aren’t opposites—if your architecture knows how to support both.