# State of tooling for formal verification

**URL:** <https://sel4.discourse.group/t/state-of-tooling-for-formal-verification/483>\
**Category:** Verification\
**Created:** [February 21, 2022, 3:25am UTC](https://sel4.discourse.group/t/state-of-tooling-for-formal-verification/483 "2022-02-21T03:25:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lazycandle55](https://yyz2.discourse-cdn.com/free1/user_avatar/sel4.discourse.group/lazycandle55/32/51_2.png) [@lazycandle55](https://sel4.discourse.group/u/lazycandle55)\
**Post date:** [February 21, 2022, 3:25am UTC](https://sel4.discourse.group/t/state-of-tooling-for-formal-verification/483/1 "2022-02-21T03:25:58Z")

</div>

How do you think the tooling for performing proof engineering compares to all the tooling that exists for software development – code editors and IDE’s, language servers enabling code completion and refactoring, debuggers, etc? Or are they the same tools?

I’m curious if there is a need for better tooling to support this work or if it is similar to software development.

---

<div class="post-metadata">

**Author:** ![gerwin.klein](https://yyz2.discourse-cdn.com/free1/user_avatar/sel4.discourse.group/gerwin.klein/32/46_2.png) [@gerwin.klein](https://sel4.discourse.group/u/gerwin.klein)\
**Post date:** [February 21, 2022, 3:41am UTC](https://sel4.discourse.group/t/state-of-tooling-for-formal-verification/483/2 "2022-02-21T03:41:01Z")

</div>

They are overlapping but different. I’ve given a few talks about this over the years, but I don’t think there are any slides public. A lot of the standard software engineering tooling is useful and used (version control, IDEs, code completion etc; we use all of these on a daily basis), but a lot more could be done in proof refactoring, proof repair, proof recommendation. Needs more research, but it’s also a fairly active area of research.