Across
- 1. Adding new functionality to existing code is ___ ____
- 6. A software change starts with a change ______
- 8. A change can be a minor inconvenience or a critical threat, and that is the ____
- 10. Change where we add new functionality
- 14. Changes to an entire system have a _____ impact
- 15. The process of identifying where in the code a particular concept is located is _____ ______
- 17. A change that if not implemented in advance leads to much code to redo is a _____ requirement
- 19. Getting ready for a software change implementation
- 22. A characteristic of a software change is the _____ value
- 24. Changes to more than one part of the code has a ______ impact
- 25. Change for emergency fixes and routine debugging
- 26. A phase of software change where we figure out how to implement the change
- 27. Guaranteeing the correctness of a software change
- 28. A phase of software change where we implement the change
- 29. Where we organize potential software changes into categories (e.g., minor problem, fatal application error)
- 30. A change that is a quick fix is also knowns as a ____
Down
- 2. Changing the structure of software without changing behavior
- 3. The set of classes identified in concept location is the ____ ____
- 4. Change where we remove obsolete functionality
- 5. Change that makes the software faster
- 7. An initiation issue where we have an irrelevant request the we delete
- 9. Performing a software change implementation
- 11. Changes inside an individual method has a _____ impact
- 12. Change where we replace existing functionality
- 13. An initiation issue with project team or technology barriers
- 16. Determine the impact of a potential change before it occurs is _____ _____
- 18. Change for new hardware and system software
- 20. A phase of software change where the requirements are specified
- 21. An initiation issue with more than one way to interpret the change request
- 23. Cleaning up after a software change implementation