Non-Functional Requirements

The non-functional requirements for CAS 3.0 are (original list by Bill Thompson):

• easy to install and configure
• helpful error reporting
• fail-fast when error or mis configured
• secure out of the box
• continuous operation (no chronic memory leaks)
• throughput (known throughput per memory/cpu)