ABSTRACT
This chapter examines the classes and families for constraints on the product that need to be specified for purposes of resilience. It aims to apply these constraints as acceptance criteria and Definition of Done attainment. When possible, new systems under development should take advantage of any existing standardized enterprise tools to implement specific features and functions—for example, single sign-on, cryptographic libraries, and common definitions of databases and data structures for internal uses. Manageability features require designers and developers to build software as highly cohesive and loosely coupled. Nonfunctional requirements (NFRs) are the quality, security, and resiliency aspects of software that only show up in software specifications when they’re deliberately added. Manageability encompasses several other areas of NFRs but is focused on easing the ability for support personnel to manage the application. Privacy is related to security in that many privacy controls are implemented as security controls, but privacy also includes non-security aspects of data collection and use.
