In embedded systems, especially where functional safety and compliance (ISO 26262, DO-178C, IEC 61508, etc.) are key, verifying that the code actually implements the requirements is critical, and time-consuming.

This new “shift left” approach allows teams to catch issues before running tests, and even detect issues that traditional testing might miss entirely.

In addition, this solution can identify automatically traceability between code and requirements. It can thus auto-generate traceability reports for compliance audits.

Here’s a short demo (Google Drive): https://drive.google.com/file/d/1Bvgw1pdr0HN-0kkXEhvGs0DHTetrsy0W/view?usp=sharing

This solution can be highly relevant for safety teams, compliance owners, quality managers, and product development teams, especially those working on functional safety.

What do you think of this new AI-powered software verification approach?

Comments URL: https://news.ycombinator.com/item?id=44175029

Points: 2

# Comments: 0

Here is an example feature map for the Spot robot SDK from Boston Dynamics with 100k lines of code: https://product-map.ai/app/public?url=https://github.com/bos...

Do you know about bela.live? I learned that it also creates C4 diagrams from code using AI.

I'm building a tool to help developers understand legacy code by identifying with AI the features implemented in the code, and then displaying these features on a map along with their hierarchy and traceability to code. It's a visual feature-first approach to document software.

Link: https://product-map.ai/

I would love to hear your thoughts about it!

I built ProductMap AI, a tool that automatically identifies features implemented in source code and organizes them in a visual hierarchy. The goal is to help developers quickly understand poorly documented codebases.

Link: https://product-map.ai/

I’d love feedback from the HN community! Let me know what you think. Would this be useful for you?

Comments URL: https://news.ycombinator.com/item?id=43429882

Points: 5

# Comments: 0

Existing traceability solutions are either difficult to use or incapable of scaling

I’ve spent the last twenty years of my life trying to help engineers connect their data across different software applications. I’ve seen many different solutions, and I’ve implemented several myself. The harsh reality is that none of the existing solutions are good enough. Either the user experience for engineers is terrible, or the approach cannot be applicable to enough applications.

Even though software applications to manage requirements, tests, and software are not designed to be interoperable, they have one thing in common: they are all accessed through a Web browser. It would be a shame not to take advantage of that. Web browsers have something powerful called extensions, which can augment existing Web pages and Web applications. The most popular Web browser extensions are used to block ads (e.g. AdBlock Plus), save passwords securely (1Password), check spelling (e.g. Grammarly), invert the color scheme of web pages to reduce eye strain (e.g. Dark Reader), and more. Why not use Web browser extensions to help engineers manage cross-domain aspects such as traceability?

Our solution uses a Web browser extension to provide a new in-app user experience such that engineers can have additional traceability features within their favorite software applications. With one click, they can select an information item as a link source in one app, and with just another click, they can select another information item as a link target in another app.

We use Web browsers daily to navigate between linked Web pages. Now we can use a Web browser extension to navigate between linked information items.