strictdoc
rdm
| strictdoc | rdm | |
|---|---|---|
| 1 | 2 | |
| 138 | 106 | |
| 2.9% | 0.9% | |
| 9.8 | 0.0 | |
| 4 days ago | over 1 year ago | |
| Python | Python | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
strictdoc
-
Ask HN: How do you keep track of software requirements and test them?
* https://github.com/strictdoc-project/strictdoc
Of course requirements can be linked to test cases and test execution reports, based on a defined and described process.
How to build test cases is another story.
rdm
-
Ask HN: How do you keep track of software requirements and test them?
Been working as a consultant and engineer on FDA regulated software for about 8 years now. I have seen strategies from startups to huge companies.
I have seen requirements captured in markdown files, spreadsheets, ticket management systems like Redmine, Pivotal, Jira, GitLab, Azure Devops, GitHub Issues, and home grown systems.
If I had to start a new medical device from scratch today, I would use Notion + https://github.com/innolitics/rdm to capture user needs, requirements, risks, and test cases. Let me know if there is interest and I can make some Notion templates public. I think the ability to easily edit relations without having to use IDs is nice. And the API makes it possible to dump it all to yaml, version control and generate documentation for e-signature when you need it. Add on top of that an easy place to author documentation, non-software engineer interoperability, discoverable SOPs, granular permissions, and I think you have a winning combination.
-
How We Develop AI for 510(k)-Cleared Devices
We've had somewhat of a hard time applying agile to IEC 62304, although it's not impossible.
This document has some useful tips:
AAMI TIR45:2012 (R2018) Guidance On The Use Of AGILE Practices In The Development Of Medical Device Software
Also, we have an open source offering that includes an IEC62304 compliant software plan. You can check this out here:
https://github.com/innolitics/rdm/blob/master/rdm/init_files...
What are some alternatives?
doorstop - Requirements management using version control.
paperetl - 📄 ⚙️ ETL processes for medical and scientific papers
ford - Automatically generates FORtran Documentation from comments within the code.
MkDocs - Project documentation with Markdown.
pdoc - API Documentation for Python Projects
wtfpython - What the f*ck Python? 😱
AutoDoc-ChatGPT - AutoDoc-ChatGPT is a Python script that leverages the power of ChatGPT model to automatically generate documentation for any programming language. With AutoDoc-ChatGPT, you can easily generate comprehensive documentation for your codebase.
pdoc - :snake: :arrow_right: :scroll: Auto-generate API documentation for Python projects
professional-programming - A collection of learning resources for curious software engineers
paperai - 📄 🤖 Semantic search and workflows for medical/scientific papers
sphinx - The Sphinx documentation generator