Change cases were introduced in the book Designing Hard Software by Douglas W. Bennett. Bennett does a good job of identifying categories of change cases. Even if some of the specific examples seem a little outdated, the concepts translate quite readily into problems being faced by systems under development today. What's missing is any indication of what the content of the change case should be, and how they should then be used in the evaluation of a software system architecture and design. This presentation is based on the author's experiences in multiple consulting engagements. It answers the question of what the content of a change case should be and how that content can be used throughout the course of architecture development. It discusses how change cases relate to the ATAM growth scenarios and how they can be employed in the development and assessment of software system architectures.