A common development challenge is accurately scoping the amount of effort required when creating new applications. This can occur when an application’s requirements are first being designed, or even before. Since one of the most frequently-overlooked capabilities of service virtualization is the ability to rapidly prototype and test the impact of new services directly from initial user stories, I’m going to address that today.
At the very beginning of an application’s lifecycle, there comes a time when the team meets to discuss what the code should do. Often, there are many questions surrounding the feasibility of a new application, and the burden falls on the developer to indicate whether something is possible and to scope the level of effort required.