spk-logo-white-text-short2
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Metrics, Metrics, Metrics in PTC Integrity: Part 1

Written by SPK Blog Post
Published on January 29, 2015

In any type of Requirements management or development system, the ability to track metrics on what is being done is an important component of knowing where you are in your delivery cycle. This article will be the kick off in a series of articles that will discuss how we can create, track and use various types of metrics to manage your delivery cycle in PTC Integrity.

First of all we will talk about trace relationship reporting in PTC Integrity. Trace relationships are used in PTC Integrity to link document content to other document content, either inside or outside a given document domain.  The diagram below describes the trace relationships between the main three document domains that handle input, requirements and design content.

SPK_Documents_and_Traces

Input will “Decompose to” one or more requirements which in turn are “Satisfied by” the design.  These are referred to as forward or downstream relationships. Likewise, the design “Satisfies” one or more requirements, the requirement “Decomposes from” the input in what is generally referred to as a backwards or upstream relationship.  It is also possible to laterally within the same document type using peer traces like “Is Related to”.

Traceability metrics are about ensuring content items from the various documents are properly traced through the documents.  Out of the box PTC Integrity, to ensure full traceability, counts back traces.  For example, how many Requirement content items are related back to Input content items.  Typically this type of tracing is recorded on the document item itself through a series of special fields as shown below.

SPK_MKS_Test_Manager

The computations stored in these fields are the results of the metrics trigger that comes with the out of the box solutions from PTC.  Solutions like the ALM solution or the Med Device solution.  This trigger is scheduled to perform calculations on items contained within active projects within PTC Integrity.  By default it is scheduled to run on a daily basis, but that can be adjusted to be daily, weekly or monthly.

SPK_MKS_ALM

In my next article I will show how you can use these metrics to create a simple report to demonstrate how this metrics can be used to determine the state of a project in PTC Integrity.

Next Steps:

Latest White Papers

A Checklist for Reducing Time to Market in Engineering

A Checklist for Reducing Time to Market in Engineering

Product teams all have the same goal: produce high-quality products and reduce time to market. Achieving these goals simultaneously can be difficult, but your team doesn’t have to sacrifice one for the other. Learn how in this eBook.What You Will Learn In this eBook,...

Related Resources

Replacing IBM DOORS: Which Path Is Right?

Replacing IBM DOORS: Which Path Is Right?

Legacy IBM DOORS remains a mature requirements management platform, particularly for complex and regulated engineering programs. It provides structured specifications, baselines, electronic signatures, change management, and multi-level traceability.  However,...

How Product Teams Can Measure AI Coding ROI

How Product Teams Can Measure AI Coding ROI

Key Takeaways AI adoption alone does not prove ROI. Teams must measure how AI coding tools impact development speed, software quality, engineering capacity, and overall costs. Developer time saved must translate into business value. Tracking recovered hours,...

Forward Deployed Engineers vs. Consultants: What’s the Difference?

Forward Deployed Engineers vs. Consultants: What’s the Difference?

Key Takeaways Consultants, professional services, and managed services serve different purposes. Consultants provide strategic guidance, professional services focus on implementation, and managed services support ongoing operations. Forward Deployed Engineers (FDEs)...