Build version id :

What happens in the Real scenario if u r working on Production issues or Enhancement project then after some issues/ bugs gets fixed then these fixes has to be club together and applied on the Application.

For Example :

Build version id can be written as :

Release 31 or Release 32 just like that .


Software version id:

U all know Microsoft .Net technology software what happen to the release .

in the Begening .Net 1.1 came

Then .Net 2.0

Then .Net 3.0 comes these release are kown as Software version id.


Rgds

Nitin K Verma

Software Version id : best example is QTP 9.0 9.2 9.5 and current one 10 version and another example is Microsoft 98 2000 NT XP Vista

Whenever some changes are added to the existing functionality of application a new pattern will be generated and the new application is termed as new version.
(Compare the window OS or QTP with their version and changes added to them in release after release)


Build Version id generally in development life cycle you wont develop all the modules with in a month and release the project instead development will be done module after module for the sake the management will decide when will be the build dates some companies take 1 month to 3 months to release first build and it depends on project duration so Module 1 will be developed and release it to testing team to test the application and on second release module 2 will developed after and integrate it with Module 1(along fixing the issues found in release one) that how the all the modules will be developed and release to test team till all the modules are developed.

so first release is termed as Build 1 and second release will be termed as Build 2 and so on.