1.

What Can Be Done If Requirements Are Changing Continuously?

Answer»

A common problem and a major headache.

It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch. If the code is well commented and well documented this makes changes easier for the developers. Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes. Be sure that customers and MANAGEMENT understand the scheduling impacts, inherent risks, and COSTS of significant requirements changes. Design some FLEXIBILITY into test cases (this is not easily done; the BEST bet might be to minimize the detail in the test cases, or set up only higher-level generic-type test plans)

A common problem and a major headache.

It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch. If the code is well commented and well documented this makes changes easier for the developers. Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes. Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant requirements changes. Design some flexibility into test cases (this is not easily done; the best bet might be to minimize the detail in the test cases, or set up only higher-level generic-type test plans)



Discussion

No Comment Found