-
Notifications
You must be signed in to change notification settings - Fork 9
/
interface.tex
28 lines (19 loc) · 1.23 KB
/
interface.tex
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
\subsubsection{Interface}
\label{sec:Interface}
The \sbol{Interface} class (shown in \ref{uml:interface}) is a way of explicitly specifying the interface of a \sbol{Component}.
\begin{figure}[ht]
\begin{center}
\includegraphics[scale=0.6]{uml/interface}
\caption[]{Diagram of the \sbol{Interface} class and its associated properties.}
\label{uml:interface}
\end{center}
\end{figure}
\subparagraph{The \sbolheading{input} property}
\label{sec:input}
An \sbol{Interface} MAY have any number of \sbol{input} properties, each of type \sbol{IRI}, that MUST reference a \sbol{Feature} object in the same \sbol{Component}.
\subparagraph{The \sbolheading{output} property}
\label{sec:output}
An \sbol{Interface} MAY have any number of \sbol{output} properties, each of type \sbol{IRI}, that MUST reference a \sbol{Feature} object in the same \sbol{Component}.
\subparagraph{The \sbolheading{nondirectional} property}
\label{sec:nondirectional}
An \sbol{Interface} MAY have any number of \sbol{nondirectional} properties, each of type \sbol{IRI}, that MUST reference a \sbol{Feature} object in the same \sbol{Component}. Note that nondirectional can imply both bidirectional as well as situations where there are no flows (for instance -- a physical interface).