Migrating a project from one technology to another technology happens only when your project is developed 5 to 10 years back with older technologies like Access, VB etc and wanted to change to new technologies like .Net, Java etc.Â
A project that is developed 5-10 years back, at that time based on the market requirements, Operating systems, configurations, technologies and its features etc based on these things application's were developed and the code behind the application might be complicated, application might not be that much user friendly.
When a porject is developing with new technologies, obviously everything will be changed allot, including OS, configuration, Technologies, new features in the application etc.
The documents that were developed for older version like requirements, SRS, Test Plan, etc might be used as a base documents, but the new version of document will be vary allot with the older version
Plz correct me if I am wrong
Above answer was rated as good by the following members: jimmy_vaswani
RE: Is it essential to create new Software requirement...
A migrated Project which is enhancement of the exisitng project. so It is not essential to create new SRS. we can make changes to the existing SRS as per the requirements.
or A migrated Project is a project which is conversion of application from envrionment to another environment. e.g. converting from .Net to java Environment.We need to check s/w and hardware requriements of the project
we can use the same SRS if there is no major change in the Requirements
RE: Is it essential to create new Software requirement...
Jayanthi I feel when we are talking about Migration Project then we have start with Requirement analysis and gap analysis document rather than convetional SRS. But we cant say no need to make SRS for new one infact we have to do all documentation starts from requirement analysis to Test cases and all.....
RE: Is it essential to create new Software requirement document,test planning report if it is a "Migrating Project"?Please share ur thought
It totally depends up on the project as how much of the existing functionality is goint to use for the migrating project if it's very less than we can go for updating or else we can go for new docs.
RE: Is it essential to create new Software requirement document,test planning report if it is a "Migrating Project"?Please share your thought
Migrating a project from one technology to another technology happens only when your project is developed 5 to 10 years back with older technologies like Access VB etc and wanted to change to new technologies like .Net Java etc.
A project that is developed 5-10 years back at that time based on the market requirements Operating systems configurations technologies and its features etc based on these things application's were developed and the code behind the application might be complicated application might not be that much user friendly.
When a porject is developing with new technologies obviously everything will be changed allot including OS configuration Technologies new features in the application etc.
The documents that were developed for older version like requirements SRS Test Plan etc might be used as a base documents but the new version of document will be vary allot with the older version
1 
0