Project restructuring is the act of rearranging your integration or system testing project members by turning existing directories into projects, or adding or removing projects from the hierarchy.
Many reasons exist for why sites decide to restructure projects; the following are a few:
Whenever you restructure a project, you will need to change the makefiles, the build process, and all automated jobs to reflect the changes you have made.
You will need to apply the changes to both the integration testing project hierarchy and the system testing project hierarchy. Update the integration testing project hierarchy first, then apply the change to your system testing project hierarchy by checking out any new projects, then updating to bring in the changes.
Additionally, when you restructure a project, you will need to perform an update and also rebuild the project hierarchy to ensure the integrity of your application. For the integration testing project, your usual short test suite should suffice. For the system testing project, your SQE team will probably need to retest your application.