Acceptance and installation is the phase in the software life cycle during which a software product is integrated into its operational environment and tested in this environment to ensure that it performs as required.
The two basic tasks- getting the software accepted and installing the software at the customer site.
Invent identification scheme for system versions plan when new system version is to be produced. Ensure that version management procedures and tools and properly applied. Plan and distribute new system releases.
1. Wrong : The specifications have been implemented incorrectly. This defect is a variance from customer / user specification. (correctly mentioned in specification but wrongly implemented)
2. Missing : A specified or wanted requirement is not in the built product. This can be a variance from specification, an indication that the specification was not implemented. ( given in specification but missed out in application)
3. Extra : A requirement incorporated into the product that was not specified. This is always a variance from specifications, but may the user of the product desire an attribute. (any thing that dissatisfies)
In bottom up integration, all modules are added or combined from lower level hierarchy to higher level hierarchy I.e., the lower level model is tested in isolation first, then the next set of higher level modules are tested with the previously tested lower modules.
Worker modules are grouped into builds and integrated.