head	1.1;
access;
symbols;
locks
	lacey:1.1; strict;
comment	@% @;


1.1
date	92.10.25.17.57.25;	author lacey;	state Exp;
branches;
next	;


desc
@Database subsystem.
@


1.1
log
@Initial revision
@
text
@%*****************************************************************************
% Remember, you need to be as detailed as possible in the description
% of the modules in order to facilitate the coding task. Do not leave any 
% room for ambiguity.
%*****************************************************************************
%
% For each module and major submodule complete the following
% section and subsections
%
\subsection{Graphical User Interface}

% 
% Include a data flow diagram for this module
%
\subsubsection{Data Flow Diagram}

%
% Include a Structure Chart for this module
%
\subsubsection{Structure Chart}

%
% Include a processing narrative for this module
%
\subsubsection{Narrative}

%
% Include a PDL pseudocode description for this module
%
\subsubsection{PDL Description}

%
% Include a description of the interfaces for this module.
% This should include a list of data elements passed between
% modules.  The data elements described here should either be
% described in the next subsection or in the relevant owner's
% data dictionary
%
\subsubsection{Internal Interfaces}

%
% Include a data dictionary for this module.  The format should be:
%  
% Name: (this is the name of the data item)
% Aliases: (this is a list of aliases, if any)
% Where Used/ How Used: (this is a paired list of where the item is
%     used and how it is used
% Description: (this is a demarco description of the data item)
%
\subsubsection{Data Dictionary}


@
