ib-ARM creates insight into applications by parsing production source code. It has a proprietory parser for each and every technology type within the application portfolio. Parsers analyze source code: identify and categorize every single language component and map out the inherent relationships between those components. The tool’s mapping engine connects semantic relationships between languages, technologies and platforms. The end result is a complete inventory and relationship map of every application element within the portfolio.
A by-product of the parsing process is the collection of application metrics including complexity (McCabe, Function Points), size (lines of code, expanded lines of code, statement counts, etc.) and quality (missing/orphan components, duplicates, dead code, etc.). The metrics are captured at the component level and rolled up to application subset, application and portfolio levels. The tool’s dashboard displays base metrics data, statistical analysis and comparison both in tabular and graphics format. This information is indispensible to application assessment and strategic planning.
ib-ARM: where Bottom-Up meets Top-Down
ib-ARM’s unique parsing technology (extensible parsing frame-work) allows any supplemental information with an electronic footprint to be processed. The tool’s repository is based on an extensible metamodel that allows the easy addition of new and additional information types. As a result, an existing Application Inventory that was perhaps created using a top-down approach and captured either in a commercial tool or a homegrown solution, (for a more detailed discussion of bottom-up vs. top-down see the APM White Paper) can be readily parsed into the ARM repository and matched up to the applications that are already there with all their parsed detail. This flexibility and extensibility allows ib-ARM to become an organization’s central tool solution for the implementation of Application Portfolio Management.
APM White Paper