\item[F9:] Report to the user or maintainer when a source has been changed
too much for successful crawling.
- This requirement was also present in the original requirements and hasn't
+ This requirement was also present in the original requirements and has not
changed. When the crawler fails to crawl a source, this can be due to any
reason, a message is sent to the people using the program so that they can
edit or remove the faulty crawler. This is a crucial component because the
\begin{figure}[H]
\label{appoverview}
\centering
- \scalebox{0.7}{
- \digraph[]{graph111}{
- rankdir=LR;
- node [shape="rectangle",fontsize=10,nodesep=0.7,ranksep=0.75,width=1];
- User -> System
- User -> Source
- System -> Crawler
- Crawler -> Source
- }
- }
+ \includegraphics[width=\linewidth]{appoverview.eps}
+ \strut\\
\caption{Overview of the application}
\end{figure}
+
\subsection{Frontend}
\subsubsection{General description}
The frontend is a web interface to the backend applications that allow the user
server periodically calls the XML output from the backend to process it.
\begin{figure}[H]
- \caption{The landing page of the frontend}
\label{frontendfront}
\includegraphics[scale=0.75,natheight=160,natwidth=657]{frontendfront.png}
+ \caption{The landing page of the frontend}
\end{figure}
\subsubsection{Edit/Remove crawler}
become highlighted and by doing this for several entries the program will have
enough information to crawl the feed as shown in Figure~\ref{addcrawl}
-\begin{figure}
- \label{addcrawl}
- \caption{Example of a pattern in the add crawler component}
+\begin{figure}[H]
+ \label{frontendfront}
+ \includegraphics[width=0.7\linewidth,natheight=1298,natwidth=584]{crawlerpattern.png}
+ \caption{A pattern selection of three entries}
\end{figure}
\subsubsection{Test crawler}