19. _Requirements for a project usually should not stipulate a specific algorithm or a programming language. 20. Requirements description usually should not include reasons why a requirement is essential. 21. It is not desirable to combine several different requirements as a single requirement. 22 Interviewing of users is not a good method for requirements elicitation. 23. -Validation of software requires customer assessment of the software, besides fulfilling formal requirements. 24. Software inspections may be performed even before execution of the software. 25. _In test-driven development, tests should be written immediately or shortly after writing the code, The answers must be clearly marked T/F along with question number