John Rushby
4 references under this name, matched as it is written. Somebody else may write under it too, and the same person may appear here spelled another way.
This description was written by a machine and published without a person checking it. It is what the agent made of this grouping, and not a statement anybody has stood behind.
John Rushby
What a regulator should accept as evidence, developed over sixteen years: formal methods and the certification of critical systems, partitioning in avionics architectures as the concrete case, just-in-time certification, and software verification and system assurance. The argument is about certification rather than proof -- of the corpus's three answers to whether formal methods pay, this is the one that treats the certifier as the audience.
Software Verification and System Assurance
John Rushby (2009) · 2009 Seventh IEEE International Conference on Software Engineering and Formal Methods · IEEE
Just-in-Time Certification
John Rushby (2007) · 12th IEEE International Conference on Engineering Complex Computer Systems (ICECCS 2007)
Partitioning in avionics architectures: Requirements, mechanisms, and assurance
John Rushby (1999) · NASA Langley Research Center
Formal Methods and the Certification of Critical Systems
John Rushby (1993) · SRI International, Computer Science Laboratory