Semiant Traceability

What tools shall Semiant integrate with?

Like any team member, a virtual quality assistant has to access data. Semiant will access the same tools that the other team members use. The question is: What tools are relevant, and which are the most important tools? Which tool shall we integrate with first?

Please help us to answer this question in this poll. And please read on to find out what Semiant would use the integration for.

Integrate with Data Sources

The primary use case for integration is to access data sources. Semiant will analyze the integrated data source to extract glossary terms. This will also allow to establish traceability between the glossary terms and the “items” in that specification.

What exactly an item is depends on the integrated tool. In a classical requirements management tool (Polarion, Jama, etc.), this would be an individual requirement. In a document system or Wiki (Confluence, Google Docs), this could be a sentence, a paragraph or section.

Integration for Other Use Cases

Eventually, we need integrations for other use cases. For instance, Semiant might integration with a task management system to communicate with users. This could be anything like build-in collaboration, which many tools provide. But it could also be an external collaboration platform, like Slack.

Any other thoughts?

If you have an important use case or integration need that is not covered here, then please reach out by using the contact button at the bottom of this page. Also, check out our 2021 roadmap.

Image Source: FreePic


The Key to Compliance is Traceability – Would You Like to Automate it?

Traceability has many benefits in product development. It is also mandatory for regulatory compliance, no matter whether you build cars, trains, planes, medical devices, industrial tech. There are very few exceptions.

Please fill out our 30-second-survey below. Thanks!

Traceability in product development is everywhere:

  • From regulatory compliance documents to your system description
  • Between user requirements and system requirements
  • Between requirements of any kind and tests
  • Traceability between risks and functions
  • … and many more

A Glossary is a First Step

Semiant, our automated quality assistant, already provides you with traceability between glossary terms and requirements. This is already useful for compliance activities:

  • Regulatory compliance requires a controlled vocabulary and a common language, which Semiant helps you establish.
  • The Glossary provides traceability between glossary term and requirements relating to the term.
  • Last, it provides traceability between terms, e.g. generalizations or associations between terms.

Risks of Not Having an up to Date Traceability

For products that require functional safety compliance, not having a sound traceability can lead to serious problems:

  • Missing or incorrect traceability can lead to a rejected audit, leading to delays in product launch and expensive rework.
  • In case of accident that involve your product, there will be an investigation. Gaps in your traceability could lead to heavy fines, even prison for executives or bankruptcy for the organization.

As an example, consider the cost of the Boeing 737-MAX disaster: Hundreds of people died, thousands of planes grounded for over a year, loss of sales, and a heavily damaged reputation. The investigation uncovered neglect of fulfilling regulatory requirements.

Would you Like to Automate Compliance Activities Related to Traceability?

Traceability is useful beyond compliance. However, creating and maintaining traceability is tedious. That’s why we are exploring how Semiant could help you with this.

We prepared a one-question survey below. We’d love to hear whether any of these ideas resonates, or whether you have even better ideas.

Survey not showing? Open on separate page >>

Photo by JJ Ying on Unsplash