SEPM ACTIVITY - 790,792,796

1234567891011121314151617181920
Across
  1. 7. A crucial aspect of software, especially in healthcare, where lives depend on it.
  2. 8. Parts of code in a control flow graph with no branches.
  3. 9. A type of software requirement that describes system services.
  4. 11. Checking requirements for validity and consistency.
  5. 13. A plan to address potential problems.
  6. 15. Making changes to software to fix defects or improve it.
  7. 16. Testing different instances of a software product daily.
  8. 17. Costs that are often more than 70% of total software expenses.
  9. 19. Estimating the cost of supporting the software product.
  10. 20. A measure of the number of independent paths in program code.
Down
  1. 1. The phase where the software built is given to the customer.
  2. 2. A document stating the agreed system requirements.
  3. 3. The process of formally documenting user and system needs.
  4. 4. Representation of code with nodes and edges.
  5. 5. Ensuring code can be easily modified during maintenance.
  6. 6. Analyzing potential problems to minimize their impact.
  7. 10. A method to calculate cyclomatic complexity: E - N + 2.
  8. 12. Constraints on the system from its operational area.
  9. 14. A risk strategy that deals with problems as they arise.
  10. 18. The foundation for software engineering.