nies. All rights reserved. Any use is subject to the Terms of Use as given at the website. Capacity and Quality Tradeoffs Capacity and Quality Tradeoffs it was created for use by software developers, it is valuable in the design of any sys- tem where attributes required or desired by users must be turned into engineering specifications. IEEE-1992 defines a set of attributes that might be important to users, including availability, efficiency, flexibility, integrity, interoperability, reliability, robustness, and usability. It is important to have the customer or customer representative define each of these terms as they apply to the product or service. The goal is to create a verifiable set of attributes that define quality to the customer. If possible, these attributes should be quantifiable; if not, then it is valuable at least to obtain the customer's priorities and preferences. In addition, IEEE-1992 defines a set of attributes that are important to de- velopers or engineers. These include portability, reusability, and testability. Once we have defined these attributes, we can create a requirements specification. A requirement is a document that defines a condition or capability needed by a user to solve a problem or achieve an objective or a condition or capability that must be achieved by a system or system component to satisfy a contract, standard, specification, or other formally imposed document. It is valuable to prepare two versions of a requirements document, a requirements statement and a requirements specification. The requirements statement is more gen- eral, written SO that the customer and nontechnical executives can follow it. The re- quirements specification is designed for engineers. The two should be coordinated care- fully so that they are consistent, and engineers designing or implementing the system should be comfortable with both documents. It has been found that engineers who un- derstand the system from the customer's perspective do a better job at technical design. A high-quality requi