Project completed, developed and tested and even deployed on the client's end.
Now, the question rises!! What will be the lifetime of this software i.e how long will the user use the software without asking for any further upgrade?
With time the data in the back-end keep on increasing, the queries written for the system will take longer time to return the requested records.
Who can validate that system can withstand such future load or any other dependencies?
Mostly the support team is the first layer where it is reported about any issues which the software faces.
Then from the support team it gets articulated to the testing team.
On reproducing the error or investigating on the issue being faced. From here the manager is being notified.
The manager then bring it up in the group meeting with the developers, that's how the develop gets aware of the issue which wasn't able to visualize, the manager couldn't figure out at the time of design and development, the testing team missed it.
So, finally who can estimate the lifetime and take steps to extend it?
How he/she can gain this expertise?
1. Surveying the projects which has been deployed and used on the field.
2. Reading project analysis report and all.
BUT, in today's world there isn't any concept of one time build and delivered software as the world has accepted the rapid upgrading technique. Hence all this won't mean.
Though one should audit the limitation of the software system.
Now, the question rises!! What will be the lifetime of this software i.e how long will the user use the software without asking for any further upgrade?
With time the data in the back-end keep on increasing, the queries written for the system will take longer time to return the requested records.
Who can validate that system can withstand such future load or any other dependencies?
Mostly the support team is the first layer where it is reported about any issues which the software faces.
Then from the support team it gets articulated to the testing team.
On reproducing the error or investigating on the issue being faced. From here the manager is being notified.
The manager then bring it up in the group meeting with the developers, that's how the develop gets aware of the issue which wasn't able to visualize, the manager couldn't figure out at the time of design and development, the testing team missed it.
So, finally who can estimate the lifetime and take steps to extend it?
- An analyst who have experience in testing and have a track record of finding logical loopholes.
- An experienced project manager.
- Experienced developer or the one who can think/ figure out logical dependencies at code level.
How he/she can gain this expertise?
1. Surveying the projects which has been deployed and used on the field.
2. Reading project analysis report and all.
BUT, in today's world there isn't any concept of one time build and delivered software as the world has accepted the rapid upgrading technique. Hence all this won't mean.
Though one should audit the limitation of the software system.
