On Streamlining Compliance of Haskell projects with NASA requirements

Hi,

In case it's of interest to anyone here, I'm writing to share "Towards
Streamlining Auditing for Compliance with Requirements in Open-source
Software at NASA", a paper we presented at the AIAA/IEEE Conference on
Digital Avionics Systems (DASC) last September.

The paper can be accessed here: https://ntrs.nasa.gov/citations/20250006564

The paper talks about how we are leveraging automated tools to comply with
NASA Software Engineering requirements in the Copilot project. The process
we follow with Copilot is the same for the Ogma project, so the tools are
usable there too. Some of the details discussed (e.g., traceability from
issues to code, steps towards issue assignment, review and closure) are
public on our Github pages (https://github.com/Copilot-Language/copilot,
https://github.com/nasa/ogma).

Both Copilot and Ogma are written in Haskell, and I've been posting
progress updates on both regularly

The gist of the paper is that we can put together git + github data to
check if we are doing things minimally right. We can't check for all
software engineering requirements, but we can perform many useful checks
automatically.

While this is a bit tangential, I hope this gives you an idea of how
rigorous we have to be when developing Copilot and Ogma and the process we
need to make sure these Haskell projects can be used in flight.

If you have any comments, feel free to write to me directly at
[email protected] or via the discussions in the Copilot repo:
https://github.com/Copilot-Language/copilot/discussions .

Happy Haskelling!

Ivan

_______________________________________________
Haskell-Cafe mailing list -- [email protected]
To (un)subscribe, modify options or view archives go to:
Only members subscribed via the mailman list are allowed to post.