Difference between revisions of "Abstract Specification of PKC/Process"

From PKC
Jump to navigation Jump to search
(Created page with "*Systematically distinguishing between logical and implementation requirements in the architectural requirements document. *Adhering to the methodology outlined in "Specifying Systems" to manage content knowledge regarding correctness verification. *Developing an abstract specification document that segregates logical specifications from implementation. *Distributing the abstract specification document alongside all deployed copies of the PKC's concrete implementation.")
 
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
*Systematically distinguishing between logical and implementation requirements in the architectural requirements document.
*A data flow that resembles the [[REPL|Read-Evaluate-Print-Loop(REPL)]] mechanism to recursively refine data content.
*Adhering to the methodology outlined in "Specifying Systems" to manage content knowledge regarding correctness verification.
*Encode all data content references in terms of [[Logic Model]] textual mark up with [[hyperlink]]s.
*Developing an abstract specification document that segregates logical specifications from implementation.
*The main data content of this project only relates to the abstract specification of [[PKC]].
*Distributing the abstract specification document alongside all deployed copies of the PKC's concrete implementation.
*Submit the updated data content to a sufficiently redundant data storage service during process execution.

Latest revision as of 05:30, 29 March 2023

  • A data flow that resembles the Read-Evaluate-Print-Loop(REPL) mechanism to recursively refine data content.
  • Encode all data content references in terms of Logic Model textual mark up with hyperlinks.
  • The main data content of this project only relates to the abstract specification of PKC.
  • Submit the updated data content to a sufficiently redundant data storage service during process execution.