summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/tex/latex/iso10303/bpfap2.tex
blob: 33657bac07f7834a96b0709c1921d4a2d9138a3a (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
%%
%% This is file `bpfap2.tex',
%% generated with the docstrip utility.
%%
%% The original source files were:
%%
%% stepe.dtx  (with options: `bpfap2')
%% 
%%     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{bpfap2.tex}[2001/07/16 AP info boilerplate]
\typeout{bpfap2.tex [2001/07/16 AP info boilerplate]}

  The information requirements are specified as a set of
units of functionality, application objects, and
application assertions. These assertions pertain to
individual application objects and to relationships
between application objects. The information requirements
are defined using the terminology of the subject area of
this application protocol.

\begin{note}A graphical representation of the information
      requirements is given in \aref{;sarm}.\end{note}
\begin{note}The information requirements correspond to those of
      the activities identified as being within the scope of this
      application protocol in \aref{;saam}.\end{note}
\begin{note}The mapping \maptableorspec{}
      specified in~\ref{;smap} shows how the
      integrated  resources
      \ifaicinap and application interpreted constructs \fi
      are used to meet the information requirements of this
      application protocol. \end{note}

\endinput
%%
%% End of file `bpfap2.tex'.