principles:principle_of_least_surprise
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| principles:principle_of_least_surprise [2021-05-11 22:19] – old revision restored (2021-03-25 15:43) 95.216.157.239 | principles:principle_of_least_surprise [2021-05-11 22:19] – old revision restored (2021-03-25 15:43) 95.216.157.239 | ||
|---|---|---|---|
| Line 43: | Line 43: | ||
| ==== Generalizations ==== | ==== Generalizations ==== | ||
| - | |||
| - | * [[Easy to Use and Hard to Misuse]] (EUHM): A module is easy to use if there is no surprise in how it works. | ||
| ==== Specializations ==== | ==== Specializations ==== | ||
| Line 52: | Line 50: | ||
| ==== Complementary Principles ==== | ==== Complementary Principles ==== | ||
| - | * [[Fail Fast]] (FF): FF is about what a module should do in the case of error. PLS on the other hand is about how the module should behave normally. Furthermore it normally is not a surprise that a module fails when there is an error but a module that doesn' | + | * [[principles:Fail Fast]] (FF): FF is about what a module should do in the case of error. PLS on the other hand is about how the module should behave normally. Furthermore it normally is not a surprise that a module fails when there is an error but a module that doesn' |
| - | * [[Model Principle]] (MP): PLS is mainly about how module identifier and module behavior relate to each other. MP tells that modules named according to the model are least surprising. | + | * [[principles:Postel' |
| - | * [[Uniformity Principle]] (UP): When applying PLS, UP should also be considered for naming modules. | + | |
| ==== Principle Collections ==== | ==== Principle Collections ==== | ||
principles/principle_of_least_surprise.txt · Last modified: 2021-10-18 22:15 by christian