Share Focus Mode

3460:480 F21 Software Change

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