blob: cdc566ed5adb0ecc9ec7505d0c0ba3ba006683d8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
|
%%
%% This is file `bpfats3.tex',
%% generated with the docstrip utility.
%%
%% The original source files were:
%%
%% stepe.dtx (with options: `bpfats3')
%%
%% This work has been partially funded by the US government
%% and is not subject to copyright.
%%
%% This program is provided under the terms of the
%% LaTeX Project Public License distributed from CTAN
%% archives in directory macros/latex/base/lppl.txt.
%%
%% Author: Peter Wilson (CUA and NIST)
%% now at: peter.r.wilson@boeing.com
%%
\ProvidesFile{bpfats3.tex}[2002/01/23 ATS AE test purpose intro boilerplate]
\typeout{bpfats3.tex [2002/01/23 ATS AE test purpose intro boilerplate]}
Application element (AE) test purposes are implicitly derived
from the AP information requirements and are not explicitly documented
here. AE test purposes apply to the input specifications of both
preprocessr and postprocessor test cases. AE test purposes are implicitly
derived from the AP information requirements as follows:
\begin{itemize}
\item Application objects (see ISO 10303-\theAPpartno, 4.2):
a test purpose derived from an application object is a simple
statement of the object's name;
\item Application object attributes (see ISO 10303-\theAPpartno, 4.2):
test purposes derived from application object attributes are
statements of the application object name with a specific attribute name;
\item Application assertions (see ISO 10303-\theAPpartno, 4.3):
test purposes derived from application assertions are
statements describing the relationships between two application objects.
Application assertion test purposes address the directions of
relationships as well as the number (cardinality) of relationships.
\end{itemize}
They shall be interpreted as given in the
following statement:
the IUT shall preserve the semantic associated with the unique
application element from which the test purpose was implicitly derived.
This implies that the semantics of the application element are
preserved by the IUT between the input and output of a test,
according to the reference path specified by the mapping
\maptableorspec{}
defined in ISO 10303-\theAPpartno, 5.1.
\par
\endinput
%%
%% End of file `bpfats3.tex'.
|
