%-----------------------------------------------------------------------
%
%
%
%	Mark Dennehy
%
%-----------------------------------------------------------------------
%
%	.tex
%-----------------
%	$Date: 2001/09/20 15:55:28 $
%	$Revision: 1.1.1.1 $
%	$State: Exp $
%
%-----------------------------------------------------------------------

\documentclass[11pt,twoside,a4paper]{scrartcl}
%\documentclass[11pt,twoside,a4paper,draft]{scrartcl}

\usepackage{scrpage}
\usepackage{acronym}
\usepackage{charter}
\usepackage{euler}
\usepackage{rcs}
\usepackage[rflt]{floatflt}
\usepackage{picins}
\usepackage[dvips]{graphicx}
\usepackage[dvips]{color}
\usepackage{booktabs}
\usepackage[light,all]{draftcopy}

\RCS $Revision: 1.1.1.1 $
\RCS $Author: dennehym $
\RCS $Date: 2001/09/20 15:55:28 $
\RCS $Header: /storage/CVS/RCMS/docs/RCMS.tex,v 1.1.1.1 2001/09/20 15:55:28 dennehym Exp $
\RCS $Locker:  $
\RCS $RCSfile: RCMS.tex,v $
\RCS $Source: /storage/CVS/RCMS/docs/RCMS.tex,v $
\RCS $State: Exp $

\author{Mark Dennehy
%\\[5mm]
%\includegraphics[width=1in]{Graphics/TCD_wbg.eps}
}

\subject{Rifle Club Management System}
\title{Design Brief}

\titlehead{\sf Dublin University Rifle Club\\
\includegraphics[width=0.8in]{Graphics/DURC_Logo.eps}\\[10mm]
\tiny
Version~\RCSRevision\\
Date :~\RCSDate\\
Filename :~\RCSSource\\
Status :~\RCSState
}

\renewcommand{\headfont}{\normalfont \sf}

%\renewcommand{\acffont}[1]{\textsf{#1}}
\renewcommand{\acsfont}[1]{\textbf{\textsf{#1}}}

\bibliographystyle{alpha}

\definecolor{Heading}{gray}{0.50}
\definecolor{mygrey}{gray}{0.8}
\definecolor{ltgrey}{gray}{0.8}
\definecolor{midgrey}{gray}{0.5}
\definecolor{dkgrey}{gray}{0.2}

\renewpagestyle{headings}{%
	(\textwidth,0pt)%
	{\textcolor{Heading}{\headmark}\hfill}%
	{\hfill\textcolor{Heading}{\headmark}}%
	{\hfill\textcolor{Heading}{\headmark}\hfill}%
	(\textwidth,1pt)}%
	{%
	(\textwidth,1pt)%
	{\hfill\pagemark\hfill}%
	{\hfill\pagemark\hfill}%
	{\hfill\pagemark\hfill}%
	(\textwidth,0pt)}



\topmargin -0.5in
\evensidemargin -0.5in
\oddsidemargin -0.5in
\textwidth 7.25in
%\textwidth 7in
\textheight 9.5in
\footskip 0.75in



%-----------------------------------------------------------------------
\begin{document}

\maketitle

\tableofcontents

\listoffigures

\pagenumbering{arabic}

\pagestyle{headings}


%-----------------------------------------------------------------------
\addsec{Executive Summary}

The Club at present suffers from an excessive amount of
paperwork, duplication and a lack of support information.
The nature of the information the Club maintains makes it
particularly suitable to computerisation. Hence, this design
was created for a system to maintain Club data and provide
operational and decision-making support information. It has
been named \textsf{\textbf{R.C.M.S.}}, for \textbf{\sf R}ifle
\textbf{\sf C}lub \textbf{\sf M}anagement \textbf{\sf
S}ystem.

%-----------------------------------------------------------------------
\section{General Architecture}

The Club gathers a large amount of information on its
member's progress during the year. The best means for
maintaining a store of this data is to place it in a
database. SQL databases have had thousands of man-years of
work invested in their design and implementation.
Capitalising on this is an obvious choice. Hence, an SQL
database called PostgreSQL has been selected and installed on
the club webserver,\textsf{durc.tcd.ie}; libraries to use
this database from several languages have also been
installed.

This gives a single repository for all Club data. A single
program could concievably be written to produce all required
reports for Club use, but this approach has many
disadvantages.
\begin{enumerate}
\item A large program will take longer to write
\item A large complex program will have more problems and
bugs
\item A large program may not encompass all the reports
needed, and adding to it to generate further reports will
require the programmer to become familiar with the program
thus making adding reports a difficult task.
\end{enumerate}

A single program can often be easier for novice
users as they only have to learn to use one program. However,
this is outweighed by the inflexibility of a monolithic
approach. Further, most users will be Range Officers who will
only have to use the system to generate Range Officer Reports
and that can be handled by a single program which can call
other programs for assistance.

Thus the architecture is as follows;
\begin{itemize}
\item All information stored in an SQL database
\item Several small programs, each of which produces a single
report, and which can be used by other programs.
\item Output should be in \LaTeX~ format since this allows
for output in printed format, acrobat or web-based formats,
and only requires a simple text file to do so.
\item A single program should be available to produce an RO
report with a great deal of work done on the user interface.
However, it should be possible to use this program from a
standard dumb terminal so the interface should have two
modes; text (curses) based and graphical.
\end{itemize}

Thus we have a large group of utility programs and a single
large RO Report program.

\section{Data}

The data is stored in a single SQL database with the
following tables.

\input{Tables.tex}


%-----------------------------------------------------------------------
\end{document}
