Comparison of Traditional Application Development Time to
BAP
Using BAP one can drastically reduce the
complexity of design and development for software applications. Time savings
are directly related to the complexity of the Application to be developed.
Compared to the traditional methods, using BAP,
the more complex a project, the higher will be the time and cost savings.
Following example shows the time spent on different aspects of a 24 months
one-man project, using the traditional method versus BAP
|
Development Time comparison chart |
|
|
Traditional |
BAP |
|
Item |
Development stage |
No. of months |
No. of months |
| 1 |
Software Requirements
Consideration Documents |
1 |
1 |
| 2 |
(Detailed) Software
Requirements Documents |
3 |
Combined into 3 months |
| 3 |
Software Design Document |
1 |
| 4 |
Coding, QC and Unit testing |
15 |
1 |
| 5 |
Acceptance & QA |
3 |
1 |
| 6 |
Software Delivery and
Deployment |
1 |
1 |
| |
Total Number of Months |
24 |
7 |
A time saving of 17 months over a one man project. Please note that the items #
2 & 3 are combined into one activity due to the nature of the "Developer"
program in BAP.