R & D IN SOFTWARE
Across
- 4. Improving software to make it faster, more efficient, or more reliable.
- 11. Planning how the software will look, work, and be organized.
- 12. The introduction of new ideas, methods, or technologies to improve software.
- 13. Repeating development steps to improve the product over time.
- 15. An early version of a software product used to test ideas and functions.
- 16. The ability of software to handle growth in users, data, or workload.
- 19. A specific function or capability offered by the software.
- 20. Checking that the software was built according to requirements and specifications.
Down
- 1. Making the software available for users to access and use.
- 2. Confirming that the software meets user needs and intended goals.
- 3. Written information that explains how software works or how to use it.
- 5. Turning plans and designs into actual working code.
- 6. The process of checking software to find errors and verify that it works correctly.
- 7. A need or condition that the software must satisfy.
- 8. Examining information, needs, or problems before designing a solution.
- 9. Updating and fixing software after it has been released.
- 10. A step-by-step set of instructions used to solve a problem.
- 14. The process of creating, building, and improving software products.
- 17. A mistake or error in software that causes incorrect behavior.
- 18. The process of studying a problem, collecting information, and exploring possible solutions.