independence of testing:Separation of responsibilities,which encourages the accomplishment of objective testing.After DO-178b infeasible path:A path that cannot be exercised by any set of possible input values informal review:A review not based on a formal(documented)procedure input:A variable (whether stored within a component or outside)that is read by a component. input domain:The set from which valid input values can be selected.See also domain. input value:An instance of an input.See also input. inspection:A typ eview that relies on visual examination of docum nents to deted velon ent standards and non-conformance to higher level documentation The most formal review technigue and therefore always based on a documented procedure.[After IEEE 610,IEEE 1028]See also peer review. inspection leader:See moderator inspector:See reviewer. installability:The of the vare product to be installed in a specified installability testing:The process of testing the installability of a software product.See also portability testing. installation guide:Supplied instructions on any suitable media,which guides the installer through the installation process.This may be a manual guide,step-by-step procedure, installation wizard,or any other similar process description. installation pplied softwar on an suitable media ich leads the installe the installation process.provides tallation results,and prompts for options instrumentation:The insertion of additional code into the program in order to collect information about program behavior during execution,e.g.for measuring code coverage. instrumenter:A software tool used to carry out instrumentation. of a smoke test to decide if the componen system is ready iled an Instanc testing An intake test is typically carrie out at the start of the test execution phase.See also smoke test integration:The process of combining components or systems into larger assemblies integration testing:Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems.See also component integration lesting,system integration testing. integration testing in the large:See system integration testing. integration testing in the small:See component integration testing. interface testing:An integration test type that is concerned with testing the interfaces between components or systems. interoperability:The capability of the software product to interact with one or more specified components or systems.[After ISO 9126]See also finctionality. 21 independence of testing: Separation of responsibilities, which encourages the accomplishment of objective testing. [After DO-178b] infeasible path: A path that cannot be exercised by any set of possible input values. informal review: A review not based on a formal (documented) procedure. input: A variable (whether stored within a component or outside) that is read by a component. input domain: The set from which valid input values can be selected. See also domain. input value: An instance of an input. See also input. inspection: A type of peer review that relies on visual examination of documents to detect defects, e.g. violations of development standards and non-conformance to higher level documentation. The most formal review technique and therefore always based on a documented procedure. [After IEEE 610, IEEE 1028] See also peer review. inspection leader: See moderator. inspector: See reviewer. installability: The capability of the software product to be installed in a specified environment [ISO 9126]. See also portability. installability testing: The process of testing the installability of a software product. See also portability testing. installation guide: Supplied instructions on any suitable media, which guides the installer through the installation process. This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description. installation wizard: Supplied software on any suitable media, which leads the installer through the installation process. It normally runs the installation process, provides feedback on installation results, and prompts for options. instrumentation: The insertion of additional code into the program in order to collect information about program behavior during execution, e.g. for measuring code coverage. instrumenter: A software tool used to carry out instrumentation. intake test: A special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake test is typically carried out at the start of the test execution phase. See also smoke test. integration: The process of combining components or systems into larger assemblies. integration testing: Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing, system integration testing. integration testing in the large: See system integration testing. integration testing in the small: See component integration testing. interface testing: An integration test type that is concerned with testing the interfaces between components or systems. interoperability: The capability of the software product to interact with one or more specified components or systems. [After ISO 9126] See also functionality