3 ms·

I don't think it will be regulated any time soon. However: If or when it is regulated, it is likely that existing software development standards will be adapte

I don't think it will be regulated any time soon. However: If or when it is regulated, it is likely that existing software development standards will be adapted to ensure the presence of a safety case, adequate testing and so on and so forth. The vast majority of software projects don't have to comply with quality standards like these, so there is a dearth of open source software to help deal with e.g. requirements specifications and traceability. I'm taking a bit of a long term punt with my side project and am trying to implement a set of integrated open source tools tailored to the development of artificial intelligence applications (esp. machine vision), but with support for aerospace-style quality requirements such as (the truly excellent) SMC-S-012. High Integrity Artificial Intelligence:- https://github.com/wtpayne/hiai.git https://github.com/wtpayne/hiai.git It is still early days ... but I'm chipping away at it gradually...

arthur_pryor 9y ago
i'm totally out of my depth when it comes to practical experience with the things you're trying to do in that project (the closest i've come is dealing with medical device validation protocols at my previous software dev job). but i love the high-level goal you're going for here.
- w_t_payne 9y ago
  Two 'cool' objectives: 1. A build-system that does algorithm parameter tuning for me -- so I can incrementally improve the parameters overnight every night -- this is pretty much in place already -- just missing a motivating application to take it through the final few yards. 2. The ability to do NLP on requirements - initially for "linting" the requirements to encourage conformance to the sort of restricted natural language e.g. of the sort evangelised by Chris Rupp, but eventually to build a much more sophisticated understanding of the relationship between low level requirements and low level design (code). https://www.sophist.de/fileadmin/SOPHIST/Puplikationen/re6/Kapitel_10/Requirements_Templates_-_The_Blue_Print_of_your_Requirements_Rupp.pdf https://www.sophist.de/fileadmin/SOPHIST/Puplikationen/re6/K...
- deleted 9y ago
  [deleted]

arthur_pryor 9y ago

i'm totally out of my depth when it comes to practical experience with the things you're trying to do in that project (the closest i've come is dealing with medical device validation protocols at my previous software dev job). but i love the high-level goal you're going for here.

w_t_payne 9y ago
Two 'cool' objectives: 1. A build-system that does algorithm parameter tuning for me -- so I can incrementally improve the parameters overnight every night -- this is pretty much in place already -- just missing a motivating application to take it through the final few yards. 2. The ability to do NLP on requirements - initially for "linting" the requirements to encourage conformance to the sort of restricted natural language e.g. of the sort evangelised by Chris Rupp, but eventually to build a much more sophisticated understanding of the relationship between low level requirements and low level design (code). https://www.sophist.de/fileadmin/SOPHIST/Puplikationen/re6/Kapitel_10/Requirements_Templates_-_The_Blue_Print_of_your_Requirements_Rupp.pdf https://www.sophist.de/fileadmin/SOPHIST/Puplikationen/re6/K...
deleted 9y ago
[deleted]