Question: Bad requirements could cause project failure (for instance Washington state big IT project 1997). List possible tools that helps avoiding ending with bad system requirements
Bad requirements could cause project failure (for instance Washington state big IT project 1997).
- List possible tools that helps avoiding ending with bad system requirements
- List 6 characteristics for a good requirement
- You are working on a voice recognition application to command an elevator. Write one functional and one non-functional requirement necessary for your application
- Write a test case for each on the listed requirements
Step by Step Solution
There are 3 Steps involved in it
Get step-by-step solutions from verified subject matter experts
