Question

Bad requirements could cause project failure (for instance Washington state big IT project 1997).

1. List possible tools that helps avoiding ending with bad system requirements

2. List 6 characteristics for a good requirement

3. You are working on a voice recognition application to command an elevator. Write one functional and one non-functional requirement necessary for your application

4. Write a test case for each on the listed requirements

Answer 1

a.

When there are poor requirements, this can lead to poor designs and tests, which in turn will cause delays in development and testing. The requirements must be revised; hence, all of these delays contribute to a late project. Poor product quality can result from poor requirements in situations where key components are overlooked and left out all together. Testing is also prioritized to focus on what’s important. If the requirements are flawed or unclear, testing is not properly executed and will eventually lead to poor quality. To avoid poor requirements, it is highly vital that the analysis phase of the SDLC(SOFTWARE DEVELOPMENT LIFE CYCLE)  is thoroughly completed, without being overlooked.

b.

Here are top 6 characteristics of requirements:

• Complete
• Consistent
• Feasible
• Modifiable
• Unambiguous
• Testable