Software Development

5. Writes the programs. Keeps backup copies of the programs.
7. Testing to ensure that the software works correctly within the overall system environment. This may involve testing how the software integrates with other software.
8. Forms project team. Supervises project team.
9. The process of designing a product so that it can be used by everyone, regardless of age or ability.
11. An iterative software development approach that emphasizes flexibility, collaboration, and frequent user feedback.
13. Testing to ensure that the software functions correctly as a whole system.
14. Visual representations that provide a clear way of communicating the software solution.
16. A method of expressing algorithms using a combination of programming code and plain language.
18. The process of creating software solutions to meet specific requirements or solve problems.
19. Technologies that provide features to aid the use of software specifically for people with impairments or disabilities.
20. An assessment of the viability and practicality of a proposed software solution.
21. Technologies that help people with disabilities, but may also be used by non-disabled individuals.

1. A design approach that prioritizes the needs of the user, involving them at every stage of the design process.
2. A type of software testing where source code is accessible by the tester.
3. The overall perception, preferences, and emotions of users before, during, and after using the software.
4. Designs the software to meet the specification. Produces design documentation.
6. A staged or linear software development approach where each stage is completed before moving to the next.
9. Testing carried out during the implementation stage to test individual units or components of the software.
10. A table created to list all the data that the software will use, including data types and storage requirements.
12. A type of software testing where the source code is not accessible by the tester.
15. Testing carried out by end-users to verify that the software meets their requirements.
17. A table created to list the name, type, and length of each variable used in the software.