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 . BS – 2. Standard for Software Component Testing. Working Draft Date: 28 April produced by the. British Computer Society Specialist Interest. This paper covers both the development of BS and compliance with the finished standard. The process used to produce BS is described by.
|Published (Last):||1 June 2014|
|PDF File Size:||14.21 Mb|
|ePub File Size:||11.52 Mb|
|Price:||Free* [*Free Regsitration Required]|
For the purposes of these coverage calculations a definition-use pair is defined as a simple subpath between a definition of a variable and a use of that variable and coverage is calculated using the formula: This Standard excludes a number of areas of software testing, for example: Learn more about the cookies we use and how to change your settings.
The objective of this Standard bz to enable the measurement and comparison of testing performed on software components. Cost-benefit data from a large-scale experiment on reinspection of a software requirements document.
BS 2 The Software Component Testing Standard – Technische Informationsbibliothek (TIB)
Other test case design techniques may be used that are not listed in this clause. Each cause is expressed as a condition, which is either true of false i. This Standard does not prescribe test completion criteria as it is designed to be used in a variety of software development environments and application domains. Branch Condition Coverage uses a model of 79225-2 component described in clause 3.
Coverage items are Boolean operand values within decision conditions. Take the smart route to manage medical device compliance. A test case may exercise any number of transitions.
Branch Condition Coverage is only defined for components with one entry point. Component Test Specification, Component Test Execution, and Component Test Recording may however, on any one iteration, be carried out for a hs of the test cases associated with a component. Statement testing uses a model of the source code which identifies statements as either executable or non-executable.
Because the interpretation of and name for the lowest level is imprecise, the term “component” has been chosen rather than other common synonyms such as “unit”, “module”, or “program” to avoid confusion with these more common terms and remain compatible with them.
The input distribution normal, uniform, etc. Any alternative techniques used shall satisfy these criteria: BS Standard for Software Component Testing Hs objective of this Standard is to enable the measurement and comparison of testing performed on software components.
Branch testing requires a model of the source code which identifies decisions and decision outcomes.
Test cases may also be designed to test that invalid output values cannot be induced. Data Flow Testing uses a model of the interactions between parts of a component connected by the flow of ba as well as the flow of control. The most important attribute of this Standard is that it must be possible to say whether or not it has been followed in a particular case i. Test cases are designed to exercise valid transitions between states.
For single transitions, the coverage metric is the percentage of all valid transitions exercised during test. If techniques not described explicitly in this clause are used they shall comply with the ‘Other Testing Techniques’ clause 3. The actual outcome shall be recorded. No coverage measure is defined for random testing. At the time of publication, the edition was valid. Cause-Effect Graphing uses a model of the logical relationships between causes and effects for the component.
The input and output values are derived from the specification of the component’s behaviour. A working party was formed in January with a more formal constitution.
University of Hong Kong. Coverage items are decision outcomes. The control flow model for the component is derived and the location and category of variable occurrences on it identified.
Only appropriate techniques 77925-2 be chosen and these will vary according to the software development environments and application domains. Find Similar Items This product falls into the following categories. Modified Condition Decision Coverage. This Standard does not prescribe who does the testing. This measure is defined with respect to the traversal of the set of subpaths from each variable definition to every p-use of that definition.
There are many challenges in software testing, and it would be easy to try and address too many areas, so the standard is deliberately limited in scope to cover only the lowest level of independently testable software. The syntax is represented as a number of rules each of which defines the possible means of production of a symbol in terms of sequences of, iterations of, or selections between other symbols. Branch Condition Combination Coverage is only defined for components with one entry point.
Test cases with valid and invalid syntax 79255-2 designed from the formally defined syntax of the inputs to the bd. Standard Number BS Boundary Value Analysis uses a model of the component that partitions the input and output values of the component into a number of ordered sets with identifiable boundaries.
Coverage items are rules, where each rule represents a unique possible combination of inputs to the component that have been expressed as Booleans. Course reserves Setting up a course reserve Form for setting up a course reserve. The previous edition was working draft 3. Test cases may also be designed to test that invalid output boundary values cannot be induced.
Reading desks and facilities Computer workstations Printing — photocopying — scanning Wireless LAN Interactive whiteboards Study cubicles Workstation for the blind and visually impaired. This is bd as n – 1 switch coverage. Decision Coverage is only defined for components with one entry point. Test cases shall be designed to exercise executable statements. Coverage items are unique combinations of the set of Boolean operand values within each decision condition.
On the determination of an appropriate time for ending the software testing process.