\documentstyle[11pt,fullpage]{article}
\begin{document}
\include{epsf}
\thispagestyle{empty}
\title{{\LARGE\bf Object Design Document}}
\author{{\Large\it Authors} \\
\vspace*{2.5in} 
\mbox{} \\
{\Large Title of Project}
\vspace*{2.5in} 
\mbox{} \\
\date{\today}
}
\maketitle
\clearpage
\tableofcontents
\clearpage
%\bibliographystyle{plain}

%
% This section is an introduction to this document, basically an
% abstract of what is to follow in this document.
%

\section{Introduction}

%
% This section is basically exactly what was in the System Design with
% corrections,  modifications, or design changes added.
%
% Describe in detail the design of the system architecture.  Include what
% system topology will be used (layers, partitions, etc.) and what
% architectural framework will be used (client-server, interactive. etc.)
% Describe in detail the Data Stores (files or external database) which are
% used by the system.  Include BNF grammars or ER-diagrams were necessary.
% Describe the software control implementation of the system.
%

\section{System Architecture}
	\subsection{Topology}
	\subsection{Data Stores}
	\subsection{Software Control}

%
% This is basically exactly what was in the System Design with corrections,
% modifications, or design changes added.
%
% Describe the Graphical User Interface.  Include snapshots of sample screens
% as well as overall design decisions, and possibly a widget tree.  Describe
% how you GUI design will be implemented in the object-oriented framework,
% include references to the OMT models that will contain the information.
%

\section{GUI Description}

%
% For each object class completely describe the all aspects of the class.
% Include a data dictionary description of the class and all attributes of
% the class.  Show and describe all associations to other classes in an
% object model and text descriptions.
%
% Completely describe the dynamic behavior of the class, including diagram, and
% descriptions of each state.  Describe how the control will be implemented
% for the class.
%
% Completely describe the functional behavior of the class, including diagram,
% processing narrative, inputs, outputs, and algorithm to be used
% (in pseudo-code) for each operation of the class.
%
% Include any other information that is specific to the class and to
% implementation, such as data store formats (BNF grammars), global resources,
% optimization techniques, justification of why particular algorithms were
% chosen, etc.
%
% Once this description is completed for each class, the
% implementation WILL BE A SIMPLE 
% TRANSFORMATION of the pseudo-code and attribute definitions into C++ syntax.
%


\section{Class Name 1}
	\subsection{Attributes}
	\subsection{Associations}
	\subsection{Dynamic Behavior}
	\subsection{Operations}


\section{Class Name 2}
	\subsection{Attributes}
	\subsection{Associations}
	\subsection{Dynamic Behavior}
	\subsection{Operations}


\section{Class Name 3}
	\subsection{Attributes}
	\subsection{Associations}
	\subsection{Dynamic Behavior}
	\subsection{Operations}


%
% This section should contain the sources of any and all references to other
% group documents, articles, books, etc.  that you used in creating this
% document.  Those interested can replace this with a true bibliography.
% Please see the TA if you wish to learn how to create bibliographies.
%

\section{References}
	\subsection{Existing Software Documentation}
	\subsection{System Documentation}
	\subsection{Vendor Documents}
	\subsection{Technical References}

\end{document}