|
| title |
img |
desc |
| Comprehensible Interaction |
/img/interact.png |
The interface to software should be clear, without surprises. Engineers working on the project should not be deciphering code. Documentation is implied as part of the system, enabling all users to understand the software package better. |
|
| title |
img |
desc |
| Straightforward Modification |
/img/tools.png |
Software should handle changes smoothly. Great software feels like it was designed for future changes. The documentation will instruct an engineer's strategy, removing ambiguity of how something works. |
|
| title |
img |
desc |
| Robust |
/img/robust.png |
Load spikes, accidental misuse, and business growth should not bring software crashing to the ground. Systems should be designed to handle faults gracefully. If there are errors, they should be reported clearly. |
|
| title |
img |
desc |
| Leveraged by Other Systems |
/img/leverage.png |
When software simply does its job, and does it well, it will be an asset to other systems. When software becomes convoluted, it will hinder other systems. |
|
|
