SMART Requirements
This section discusses how to make your measurements more useful. Although the definition for “T” is a variation on the acronym's traditional definition, it is important to capture requirements that are SMART:
Specific – The description and purpose is clear and unambiguous.
Measurable – The requirement is quantifiable, observable, verifiable, and testable.
Attainable – The requirement is technically or operationally possible (for instance, 101% uptime is not).
Realizable – The requirement is possible to implement in the current context of the organization (for example, 50% uptime may not be realizable in a datacenter with no roof).
Traceable – The requirement can be linked back to the KBDs and linked forward to requirement ...
Get Buliding N1™ Grid Solutions Preparing, Architecting, and Implementing Service-Centric Data Centers now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
