Our final report for HARDENS must have the following characteristics:
[ ] it must be well-suited to fit into the document-centric
certification process used by the NRC and other similar
government agencies,
[ ] it must completely describe the framing for the project, the
technical work, the safety and correctness assurance case of
the RTS demonstrator, and the manner in which the document can
be read, the R&D can/should be reviewed, etc.
[ ] It must include all formal specifications and assurance
artifacts as nicely typeset, hyper-textual cross-referenced
appendix chapters.
In order to fulfill (1) above, the final report must be both:
[ ] a polished, high-quality, hyperlinked HTML webpage, or set of
webpages that compile into a single webpage, that contains the
entire report, includes its technical appendices, and
[ ] a polished, high-quality, hyperlinked PDF document that can be
printed on paper and, in that form, it just as easy to read
front-to-back and to follow cross-references therein.
In order to help certification actors review a model-based system and
its assurance case, we intend to provide a chapter in the report that
characterizes a workflow and set of best practices for such a review.
kiniry
commented
2 years ago
Our final report for HARDENS must have the following characteristics:
In order to fulfill (1) above, the final report must be both:
In order to help certification actors review a model-based system and its assurance case, we intend to provide a chapter in the report that characterizes a workflow and set of best practices for such a review.