Below is the list of correct/incorrect examples of software process activities that help predict changes and make the software being developed more resilient to change. 1. Recording of requirements rational so that the reason why a requirement is included is known. This helps future change. 2. Requirements tractability that shows dependencies between requirements and between the requirements and the design/code of the system. 3. Design modeling where the design model documents the structure of the software. 4. Code refactoring that improve code quality and so makes it more amenable to change.