Which of the following is NOT a typical challenge in RAD-based development?

In Rapid Application Development (RAD), several challenges are commonly faced due to the nature of its iterative and incremental approach. One such challenge involves postponing risk assessments until development is complete. In RAD, the emphasis is on rapid prototyping and user feedback, which often leads to a less formal approach to risk assessment early in the process. This can result in risks being identified and addressed only after significant development work has already occurred, potentially leading to issues that could have been mitigated earlier.

Time-boxing the development process is a typical characteristic of RAD; it helps maintain a rapid pace but can also lead to challenges in managing scope and quality if not handled effectively. Similarly, not having a complete requirements specification is another challenge because RAD focuses on flexible and evolving user requirements over fixed initial specifications. Re-usable test scripts for regression testing can also be a challenge as the dynamic nature of RAD might lead to continuously changing functionality, making it difficult to maintain effective test scripts consistently.

Understanding these factors is critical for those involved in RAD projects, as they directly impact the project's success and the quality of the final product.