BS 7925-1 PDF

Home  /   BS 7925-1 PDF

This BS article has very limited content, and this standard has now been superseded by ISO/IEC/IEEE – so what little is here, is obsolete anyway . Find the most up-to-date version of BS at Engineering Purchase your copy of BS as a PDF download or hard copy directly from the official BSI Shop. All BSI British Standards available online in.

Author: Fenrira Jugal
Country: Myanmar
Language: English (Spanish)
Genre: Relationship
Published (Last): 16 November 2009
Pages: 484
PDF File Size: 16.52 Mb
ePub File Size: 14.85 Mb
ISBN: 120-3-18668-400-7
Downloads: 72977
Price: Free* [*Free Regsitration Required]
Uploader: Zujind

The process of combining component s into larger assemblies. See structural test case design. A static analysis technique that derives a symbolic expression for program path s. A test case design technique for a component in which test cases are designed to execute statement s. A test tool that compares the actual output s produced by the software under test with the expected output s for that test case.

A sequence of one or more consecutive, executable statements containing no branches. Testing whether the system is compatible with other systems with which it should communicate. The result of a decision which therefore determines the control flow alternative taken. An analysis method that determines which parts of the software have been executed covered by the test case suite and which parts have not been executed and therefore may require additional attention.

A description of a component ‘s function in terms of its output values for specified input values under specified precondition s.

The templates support the three primary test 792-1 levels of Part 2, and the standard also includes mapping to other existing standards. 7952-1 percentage of boundary values of the component’s equivalence classes which have been exercised by a test case suite. A Linear Code Sequence And Jump, consisting of the following three items conventionally identified by line numbers in a source code listing: Standard Number BS A test case design technique for a component in which test cases are designed which include representatives of boundary values.

ISO/IEC 29119

A minimal software item for which a separate specification is available. Totalagreement will rarely, if ever, be achieved in compiling a document of this nature. Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements. A record of the test planning process detailing the degree of tester indedendencethe test environmentthe test case design techniques and test measurement techniques to be used, and the rationale for their choice.


International Organization for Standardization. All standards are subject to revision, and parties to agreements based upon this Standard are encouraged to investigate the possibility of applying the most recent edition of the standards listed below.

In compiling this glossary the committee has sought the views and comments of as broad a spectrum of opinion as possible in industry, commerce and government bodies and organisations, with the aim of producing a standard which would gain acceptance in as wide a field as possible.

BS – Software testing. Vocabulary

Archived from the original on 8 February The behaviour predicted by the specification of an object under specified conditions. A test case design technique in which test cases are designed to execute state transitions.

Find Similar Items This product falls into the following categories.

The method used to perform the actual test executione. They are also called black-box testing techniques.

The first executable statement within a component. A skeletal or special-purpose implementation of a software module, used to develop or test a component that calls or is otherwise dependent on it.

Simulated or actual operational testing at an in-house site not otherwise involved with the software developers. Explicit use of et al.

They are also called white-box testing techniques. After [ IEEE ,dob ]. A meta language used to formally describe the syntax of a language.

The document that describes in detail the characteristics of the product with regard to its intended capability. The degree to which software conforms to its specification.

The percentage of combinations of all branch condition outcomes in every decision that have been exercised by a test case suite. Part 4 provides standard definitions of software test design techniques also known as test case design techniques or test methods and corresponding coverage measures that can be used during the test design and implementation processes defined in Part 2.


A series which appears to be random but is in fact generated according to some prearranged sequence. A conditional transfer of control from any statement to any other statement in a componentor an unconditional transfer of control from any statement to any other statement in the component except the next statementor when a component has more than one entry pointa transfer of control to an entry point of the component.

Testing whether the system meets its specified objectives for maintainability.

The process of confirming that a system or component complies with its specified requirements and is acceptable for operational use. A review of requirements, designs or code characterized by the author of the object under review guiding the progression of the review. Data processing – Vocabulary – Part The degree, expressed as a percentage, to which a specified coverage item has been exercised by a test case suite. Coverage measures based on the internal structure of the component.

A test case design technique in which the test case suite comprises all combinations of input values and precondition s for component variables.

A variable whether stored within a component or outside it that is written to by the component. A set of input s, execution precondition s, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. The processing of a test case suite by the software under test, producing an outcome. Retrieved from ” https: Testing of those requirements that do not relate to functionality. Determination of the c orrectness of the products of software development with respect to the user needs and requirements.

These techniques are base on the functional specification of the system under test. A criterion for determining when planned testing is complete, defined in terms of a test measurement technique.

Click to learn more.