Software Developement ?
Add Your Thoughts Please ?
Software Development – A Narrow view!
Well before you wonder about what is “Narrow View”, Let me explain why I call it a “Narrow View”, it’s just because I am writing / documenting my own experiences.
According to me any software developed twice is well fit. I just mean iterative development will make our customer smile. Don’t ask me, “How about any software developed more than twice”
Everyone knows about iterative development, but what I am talking about is – After you finish a development life cycle, restart the life cycle.
This will help you to achieve a better quality, than what you had previously. There are many problems like cost estimation to this model of development, let me explain how we can go about this…
1) Cost estimation
a. After you estimate as per your existing process you should hike it by 50%, That should include the below
i. Cost
ii. Time
iii. 50 % hike of cost and time would contribute to the second cycle, where you would have less number of employees – since it is the second cycle. Rethink on the last point when you do the cost estimation.
2) Bugs
a. Bugs, well, all software’s would have this. Clear all the bugs before you start with any changes.
3) Changes
a. Make it a rule, when you accept a “change history” – complete it before you get a new “change history”
4) How about cycle 2?
a. Inform the customer, even though the project is to finish – you would start a fresh cycle to give him a better quality.
I am an infant in understanding the software methodologies, but hope this way – I should make any software development work well.
Comments Please ?
Well before you wonder about what is “Narrow View”, Let me explain why I call it a “Narrow View”, it’s just because I am writing / documenting my own experiences.
According to me any software developed twice is well fit. I just mean iterative development will make our customer smile. Don’t ask me, “How about any software developed more than twice”
Everyone knows about iterative development, but what I am talking about is – After you finish a development life cycle, restart the life cycle.
This will help you to achieve a better quality, than what you had previously. There are many problems like cost estimation to this model of development, let me explain how we can go about this…
1) Cost estimation
a. After you estimate as per your existing process you should hike it by 50%, That should include the below
i. Cost
ii. Time
iii. 50 % hike of cost and time would contribute to the second cycle, where you would have less number of employees – since it is the second cycle. Rethink on the last point when you do the cost estimation.
2) Bugs
a. Bugs, well, all software’s would have this. Clear all the bugs before you start with any changes.
3) Changes
a. Make it a rule, when you accept a “change history” – complete it before you get a new “change history”
4) How about cycle 2?
a. Inform the customer, even though the project is to finish – you would start a fresh cycle to give him a better quality.
I am an infant in understanding the software methodologies, but hope this way – I should make any software development work well.
Comments Please ?
| Tweet |
|
|
