\documentstyle[11pt,fullpage]{report}
\title{{\LARGE\bf Final Report for Project Name}}
\author{{\Large\it Student 1\thanks{Project Manager}, Student 2, Student 3, Student 4} \\
{\Large Department of Computer Science} \\
{\Large Michigan State University} \\
\mbox{} \\
{\Large Customer: CustomerName, Company}
\vspace*{2.5in} 
\mbox{} \\
{\Large Software Engineering Capstone, CPS479} \\
{\Large Instructor: Dr.~B.~Cheng} \\
{\Large Teaching Assistant: E.~Y.~Wang} \\
\vspace*{2.5in}
\mbox{} \\
{\Large Spring 1996}
\date{}
}
\begin{document}
%\thispagestyle{empty}
\maketitle
\setcounter{page}{3}
\pagenumbering{roman}
\tableofcontents
\clearpage
\setcounter{page}{1}
\pagenumbering{arabic}

%
% Describe the project. Much of the text from the intro from other docs
% can be used.
%
\chapter{Project Description}

%
% What is the motivation for your particular project? What phase of
% software engineering does it facilitate?
%
\section{Motivation}

%
% Briefly describe the major components of your system.
%
\section{Overview of System Design}

%
% Describe specific techniques that were learned from the class and applied
% to the project.  Below are just a few examples of text that can
% be included in this section. Feel free to add more sections are you
% feel necessary.
%
\chapter{Techniques Learned and Applied}
\section{Methods and Processes}
\section{Tools}

%
% conclusions and future work
%
\chapter{Conclusions and Future Investigations}

%
% Describe functionality that does not work completely in your system.
% Explain why you were not able to completely implement the respective
% features. You may include shortcomings of the system as you have
% determined from testing.
%
\section{Functionality Limitations}

%
% What are the limitations of the system? (Why do they exist?)
%
\subsection{System Limitations}

%
% What are the properties of the system that make it
% usable?
%
\subsection{Properties Facilitating System Use}

%
% If you had it to do all over again, what would you do differently?
%
\section{Reflections of Project}

%
%
%
% Describe extensions to your project that you might have incorporated
% into your system if given enough time. 
%
\section{Future Investigations}
\appendix
\chapter{Changes and Addendums to Deliverables}
%
% Use whichever sections apply to your project. Make sure that you make 
% references to specific section and page numbers in this part of the text. 
% (Remember, the scenario is if you were given your project as a maintenance
% project next term, what information and how much detail would
% you need to modify the project.)
%
%
\section{Requirements Analysis}
\section{System Design}
\section{Object Design}
%
%
\def\thesection{\arabic{section}}
\chapter{User Manual}
%
% NOTE: Make sure that you incorporate all the changes that were
% made to the first draft of the user manual.
%
% Purpose of tool, scope.  Also, describe any assumptions
% you may be making about the abilities of the user.
% (i.e. Does the user need a Ph.D. in Astrophysics
% with a Masters in Quantum Mechanics to run your
% tool or can a regular bum that thinks computers
% are evil use it?)
%
%
\section{Introduction}
\subsection{Hardware Requirements}
\subsection{Software Requirements}

%
% Include Online help facilities.  Describe what each
% feature of the system is.  Describe fully what
% different options/selections will provide to the user.
% For instance, describe what each button allows the
% user to do.  btw, you can change the name of the section
% if you like.  If there are special languages that the
% user must know for input into the system, include 
% the description of that language here.
%
\section{Functionality Description}
%\input{functional}

%
% Provide a simple tutorial that includes a
% generic scenario for using the system.  Provide
% screen dumps, etc.  Make sure that this tutorial
% is representative of the types of operations found in
% a typical session.  As with the previous section,
% you can change the name if you find another more
% appropriate.
%
\section{User Scenarios}
%\input{scenarios}

%
% Provide a description of the steps needed to 
% install the system.  This should include any
% details not mentioned in the introduction (i.e.
% environment setup, etc.)
%
\section{Installation Procedure}

%\input{installation}
%
% You know the drill
%
\section{References}


%
% HINT!!!!:  Think about the worst user manual you've
% ever encountered.  Consider what you didn't like
% about it; was it missing something, was it redundant,
% was it incorrect?  After you've thought about these
% characteristics that you found unappealing, write
% the document with the intent of not emulating the
% worst manual you've ever seen.  ^^^  
%
% 
%
\end{document}