%% LyX 1.1 created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}

\makeatletter


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% LyX specific LaTeX commands.
\providecommand{\LyX}{L\kern-.1667em\lower.25em\hbox{Y}\kern-.125emX\@}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Textclass specific LaTeX commands.
 \usepackage{verbatim}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% User specified LaTeX commands.
\usepackage[T1]{fontenc}
\usepackage[latin1]{inputenc}

\makeatletter

\makeatother

\begin{document}


\subsection{Detailed Use Case Description}


\subsubsection{Use Case Name}

\begin{comment}
A brief description. Usually a paragraph or less. 
\end{comment}

\subsubsection{Actors}

\begin{comment}
A list of the actors who communicate with this use case.
\end{comment}

\subsubsection{Priority}

\begin{comment}
How important is this use case to the project?
\end{comment}

\subsubsection{Status}

\begin{comment}
At what point are we in developing this use case?
\end{comment}

\subsubsection{Preconditions}

\begin{comment}
A list of conditions that must be true before the use case starts.
\end{comment}

\subsubsection{Postconditions}

\begin{comment}
A list of conditions that must be true when the use case ends, no matter which
scenario is executed.
\end{comment}

\subsubsection{Extension Points}

\begin{comment}
If the use case has extension points, list them here.
\end{comment}

\subsubsection{``Used'' Use Cases}

\begin{comment}
If the use case uses other use cases, list them here.
\end{comment}

\subsubsection{Flow of Events}

\begin{comment}
This could be a basic path and alternative paths, or the primary scenario.
\begin{enumerate}
\item Preconditions 
\item Main Flow
\item Subflows (if applicable)
\item Alternative Flows
\end{enumerate}
\end{comment}

\subsubsection{Activity Diagram}

\begin{comment}
An activity diagram of the flow of events, or some significant or complex part
of the flow of events.
\end{comment}

\subsubsection{User Interface}

\begin{comment}
For systems that interface with people, include a description of the user interface,
possibly using storyboards.
\end{comment}

\subsubsection{Secondary Scenarios}

\begin{comment}
If alternatives and exceptions are not shown in the flow of events, scenarios
should be listed here, and a brief description may be included.
\end{comment}

\subsubsection{Sequence Diagrams}

\begin{comment}
If you do not have separate documents for scenarios, you might include sequence
diagrams for them here.
\end{comment}

\subsubsection{Subordinate Use Cases}

\begin{comment}
If the use case has subordinate use cases, show them here. Or you could include
a use case diagram for the subordinate use case. Or both. Also tell what subsystem
is responsible for this subordinate use case.
\end{comment}

\subsubsection{View of Participating Classes}

\begin{comment}
A collaboration showing all the classes whose objects interact to implement
this use case. You also can show interfaces to the use case here and which of
the classes implement the interfaces.
\end{comment}

\subsubsection{Other Artifacts}

\begin{comment}
This can include references to the subsystem the use case belongs to, an analysis
model, adesign model, code, or test plans.
\end{comment}

\subsubsection{Other Requirements}

\begin{comment}
This section is where you can put nonfunctional requirements affecting the use
case.

\end{comment}
\end{document}
