Blog Archives

The ultimate objective of this activity is Completion, the extent to which all desired characteristics of the digital thread have been realized. As a metric, Completion is strongly correlated with project Schedule, but it is also an indicator of project Risk. Completed segments of the digital thread represent a reduced technical risk of unexpected problems

While Complexity may be a confusing concept, Activity has clearer correlations with cost and schedule. In this post, I will illustrate some of the ways in which systems engineering activity can be calculated and displayed using Syndeia to query the digital thread for our UGV02 project. Figure 1 displays the number of inter-model relations created

The consideration of complexity concerning digital threads is a matter of both good and bad news. The literature on digital complexity metrics is rich with detailed algorithms for graphs and software code, many already available in Python and Gremlin libraries applicable to our demonstration example. On the other hand, the relevance of these to project

While this blog series focuses on the general concept of critical metrics for digital threads, we will illustrate these with actual examples. Commercial and open-source tools are available now to put these ideas into practice. For our example, we need a set of Data Sources, a Data Consumer to calculate and display the critical metrics,

One great promise of Digital Threads is that project managers can obtain a concise, real-time view of the state of system development. But there have been few examples of what this would look like and how it would be derived. In particular, we need to define critical metrics that the project managers can understand and

TestRail From Gurock is a test management solution and accessible through the Syndeia Cloud REST API. In this notebook, we demonstrate how to navigate through the multilevel TestRail data model to obtain artifact data at any level. A TestRail Repository contains TestRail Projects, which map to Containers in the Syndeia data model A TestRail Project

In Part 6 of this series, we described Syndeia Cloud REST API calls to non-Configuration-Managed (non-CM or regular) DOORS NextGen (DNG) projects. DNG projects that are CM-enabled require users to navigate through several additional levels of Components, Streams, and Baselines to access all the data in the project. Components are contained within Projects; each Component

A key benefit of the Syndeia digital thread platform is that it enables the user to retrieve data from all the federated repositories through a single interface, the Syndeia Cloud REST API. Several Jupyter notebooks released with Syndeia 3.5 each focus on a specific repository type. This post will cover non-Configuration-Managed (non-CM or regular) DOORS

A key benefit of the Syndeia digital thread platform is that it enables the user to retrieve data from all the federated repositories through a single interface, the Syndeia Cloud REST API. This and the next several Jupyter notebooks released with Syndeia 3.5 will each focus on a specific repository type. This post will cover

One of the principal benefits of a digital thread platform such as Syndeia is that it gives project leaders a holistic real-time view of the entire modeling effort. By combining Syndeia data requests with data science analytics, users can monitor and document progress quantitatively. In Part 4 of this series, we review a new Jupyter