vFunction announced the availability of vFunction Continuous Modernization Manager (CMM), a tool for continuously monitoring, detecting and fixing application architecture shift issues before they lead to technical debt collapse.
vFunction CMM enables software architects to detect and troubleshoot application architecture anomalies, define architectural baselines, and set thresholds. The vFunction CMM joins the vFunction Assessment Hub and vFunction Modernization Hub as the company’s newest application modernization platform products.
“Application architects today lack the architectural observability, visibility, and tooling to understand, track, and manage architectural technical debt as it develops and grows over time,”
said Moti Rafalin, Founder and CEO, vFunction.
“vFunction Continuous Modernization Manager allows architects to shift left into the ongoing software development lifecycle from an architectural perspective to manage, monitor, and fix application architecture anomalies on an iterative, continuous basis before they erupt into bigger problems”
he continued.
The latest version of the vFunction Modernization Hub also adds collaboration capabilities to make it easier for architects and modernization teams to work together. New analytics also identify the highest technical debt classes to focus refactoring priorities. The vFunction Assessment Hub has added a new multi-application assessment dashboard to analyze technical debt across a broad portfolio of applications.
“We are excited to be working with vFunction to monitor our applications to detect and fix issues before they result in more serious consequences. A key part of a strategic modernization strategy is to not only transform current monoliths but prevent future monoliths from forming”,
said Martin Lavigne, R&D Lead, Trend Micro.
vFunction Continuous Modernization Manager observes Java and .NET applications and services to first baseline the architecture, set baselines, and monitor for architectural drift and erosion to detect critical architectural anomalies including:
–New Dead Code Found: vFunction will detect new dead code in applications indicating that new, unnecessary code has surfaced in the application or the baseline architecture drifted and existing class or resource dependencies were changed.
–New Service Introduced: Based on the observed baseline service topology, when a new service has been detected vFunction will identify and alert that a new domain or major architectural event has occurred.
–New Common Classes Found: Building a stable, shared common library is a critical modernization best practice to reduce duplicate code and dependencies. Newly identified common classes can be added to a common library to prevent further technical debt from building up.
–Service Exclusivity Dropped: vFunction measures and baselines service exclusivity to determine the percentage of independent classes and resources of a service, alerting when new dependencies are introduced that expand architectural technical debt.
–New High-Debt Classes Identified: vFunction identifies the highest technical debt classes that are the highest contributors to application complexity. A “high-debt” class score is determined by its dependents, dependencies, and size and pinpoints a critical software component that should be refactored or re-architected.
Users will be notified of changes in the architecture through Slack, email, and vFunction Notifications Center. Through vFunction Continuous Modernization Manager, architects will be able to configure schedules for learning, analysis and the option to configure baseline measurements.
