Channels ▼


Putting Pattern Analytics Into Programming

Perforce Software has announced Insights, an analytics solution designed to reveal valuable information on code and software development inside projects.

Built into Perforce products, Insights reveals information that isn't available in bug tracking or traditional work planning tools. The product enables development teams to measure their performance so they can tune and optimize their delivery pipelines.

Insights gathers metrics and presents them in ways that are meaningful to developers, team leads, and QA and release managers. For example, while a burn-down chart might show user stories only as closed, Insights assesses and displays the cost of code stability related to the closure.

NOTE: Insights is ready to consume data from other tools and/or publish it to third-party reporting tools through standard integration mechanisms — the browser-based user interface is customizable to individual customer needs.

What Developer Does What?

Insights works to provide an overview across a series of projects, deep-dive views of single projects, and "hot spot" reports such as most edited files or top contributors across the repository. A standalone server dashboard provides performance metrics for systems administrators monitoring the overarching Perforce versioning service.

"We worked side by side with our customers to design a tool that reveals the data they need to truly understand their development processes and release cycles," said Mark Warren, marketing director at Perforce.

Perforce insists that Insights Stability Index is a "pragmatic measure" of the stability of code in a project, analyzing the Raise and Fix rates for bugs, the amount of code that is changing in a project, and the amount of code that changes repeatedly. Tracking the index trend across a project's lifetime shows if stability goals will be met prior to release or if there is an unexpected destabilization in projects where stability is a priority.

Related Reading

More Insights

Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.