Difference between revisions of "PKC Workflow/Software"
Jump to navigation
Jump to search
(→Notes) |
|||
| Line 18: | Line 18: | ||
=== Notes === | === Notes === | ||
[[Video:Tackling Concurrency Bugs with TLA+" by Hillel Wayne]][https://www.youtube.com/watch?v=_9B__0S21y8] | [[Video:Tackling Concurrency Bugs with TLA+" by Hillel Wayne]][https://www.youtube.com/watch?v=_9B__0S21y8] | ||
Unit test cannot fix the problem of potential bugs because the complexity of a system is high. | |||
Unit test cannot fix the problem | |||
Latest revision as of 14:34, 19 July 2021
TLA+
Introduction
TLA+ is a high-level language for modeling programs and systems--especially concurrent and distributed ones. It's based on the idea that the best way to describe things precisely is with simple mathematics. TLA+ and its tools are useful for eliminating fundamental design errors, which are hard to find and expensive to correct in code. [1]
- Since not all system can be modeled by a function, like an operating system, a program can be modeled by its behavior.
- A program's execution can be represented by a behavior
- A behavior is a sequence of states.
- A state is an assignment of values to variables.
- A program is modeled by a set of behaviors.
Application on PKC
To model the PKC system, a set of variables to represent state and the constraints are required in order to check its liveness and safety.
Workflow
- Download TLA+
- Define safety and liveness properties
- Run TLA+ to check whether the system fits the invariants.
Notes
Video:Tackling Concurrency Bugs with TLA+" by Hillel Wayne[1] Unit test cannot fix the problem of potential bugs because the complexity of a system is high.