\subsubsection{Network} \label{network} A \network is specified by the following definitions:\\ (1) It is any communication link between any hardware components. \\ (2) It is used to simulate message scheduling.\\ \begin{center} Standard attributes \end{center} $Name$: It is the unique name of entity \network.\\ $Network_{-}type$: It is the technique of taking into account the communication.\\ \begin{center} Legality rules \end{center} (L1) The network name must not be empty.\\ (L2) The network name must be valid identifier.\\ (L3) The $Network_{-}type$ is mandatory. \\ \begin{center} Annexes \end{center} (A1) The $Network_{-}type$ techniques \cite{Bounded1} \cite{Li99} \cite{Daniel03} \cite{Emmi11} is in fact the way to characterize delay when we consider the network. We distinguish:\\ \indent \indent (A11) $Bounded_{-}Delay$: In this case, the delay is bounded. It is an effective search prioritization strategy for concurrent programs that handles both statically-known and dynamically-created tasks. The sending of message is characterized by a bounded time.\\ \indent \indent (A12) $Jitter_{-}Delay$: In this case, the delay is a function of jitter. The sending of message is characterized by an bounded interval (max and min).\\ \indent \indent (A13) $Parametric_{-}Delay$: In this case, the delay is parametric. The user may define its own delay.\\ \begin{center} Implementation \end{center} The figure \ref{dtd_network} gives the DTD of entity \network. \begin{figure}{} \begin{lstlisting}{} \end{lstlisting} \caption{The DTD of entity $Network$} \label{dtd_network} \end{figure} \begin{center} Example \end{center} The figure \ref{Network_example} gives an example of entity \network described using Cheddar ADL. The type of \network in this case is $BOUNDED_-DELAY$. \begin{figure}{} \begin{lstlisting}{} NETWORK_OBJECT_TYPE a_network BOUNDED_DELAY \end{lstlisting} \caption{An example of \network description} \label{Network_example} \end{figure}