Difference between revisions of "Abstract Specification of PKC/Boundary"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
*The PKC system architecture specification must be future-proof and eliminate design dependencies on extant data storage, communication, and computation tools. | *The PKC system architecture specification must be future-proof and eliminate design dependencies on extant data storage, communication, and computation tools. | ||
*The abstract specification document must segregate logical specifications from implementation and be distributed alongside all deployed copies of the PKC's concrete implementation. | *The abstract specification document must segregate logical specifications from implementation and be distributed alongside all deployed copies of the PKC's concrete implementation. | ||
*All changes of PKC content should be version controlled and replicated with multiple copies. | |||
Revision as of 05:07, 29 March 2023
- The PKC system architecture specification must be future-proof and eliminate design dependencies on extant data storage, communication, and computation tools.
- The abstract specification document must segregate logical specifications from implementation and be distributed alongside all deployed copies of the PKC's concrete implementation.
- All changes of PKC content should be version controlled and replicated with multiple copies.