Technical Design vs. Implementation vs. Testing
-
We started getting requests to provide estimates for our development tasks, and I'm just wondering if there is a distinct breakdown into the technical design, implementation, and testing stages (from a developer's perspective) at other people's shops. If there is, I'd be curious to know what the ratios are (e.g. how much of the total development effort is spent on the technical design part, assuming you already have the preliminary specs?).
-
We started getting requests to provide estimates for our development tasks, and I'm just wondering if there is a distinct breakdown into the technical design, implementation, and testing stages (from a developer's perspective) at other people's shops. If there is, I'd be curious to know what the ratios are (e.g. how much of the total development effort is spent on the technical design part, assuming you already have the preliminary specs?).
Of course, you should divide your development task into several stages: preliminary/concept design (~15%), detailed design (~15%), implementation (55%) and unit test (~15%).
Welcome to www.softwaretree.net! You can find many excellent audio/video converter tools there!
-
We started getting requests to provide estimates for our development tasks, and I'm just wondering if there is a distinct breakdown into the technical design, implementation, and testing stages (from a developer's perspective) at other people's shops. If there is, I'd be curious to know what the ratios are (e.g. how much of the total development effort is spent on the technical design part, assuming you already have the preliminary specs?).
If you have the requirements documented and putting aside the management and other support activities. Technically the ration between System Design, Development and Testing is 25::50::25. The Development will include Unit Testing. This is a standard practice we follow for high level estimations... however the type of applications can make the ratio different.