%
% THIS FILE PRECEEDS ALL LATEX FILES, AND ESTABLISHES SEVERAL FREQUENTLY-USED
% MACRO'S AND COMMAND DEFINITIONS. IT DOES NOT SET THE SPECIFIC PAGE FORMAT
% OR STYLE PARAMETERS FOR EACH DOCUMENT TYPE. THERE ARE SPECIFIC HEADER FILES
% FOR EACH DOCUMENT TYPE WHICH DEAL WITH THOSE ISSUES.
%
\documentstyle [12pt]{article}
% \documentstyle{svma}  % Springer-Verlag Multi-Author format.
%
% *** LINE SPACING COMMANDS.
%
\newcommand {\hsp}  {\addtolength{\baselineskip}{.25\baselineskip}}
\newcommand {\nhsp} {\addtolength{\baselineskip}{-.2\baselineskip}}
\newcommand {\dsp}  {\addtolength{\baselineskip}{.5\baselineskip}}
\newcommand {\ssp}  {\addtolength{\baselineskip}{-.3333\baselineskip}}
\newcommand {\tsp}  {\addtolength{\baselineskip}{.75\baselineskip}}
\newcommand {\ntsp} {\addtolength{\baselineskip}{-.4286\baselineskip}}
\newcommand {\qsp}  {\addtolength{\baselineskip}{1.0\baselineskip}}
\newcommand {\nqsp} {\addtolength{\baselineskip}{-.5\baselineskip}}
%
% *** LINE AND PAGE SKIPPING COMMANDS.
%
\newcommand {\nsk}    {\vskip -.5cm}
\newcommand {\nhsk}   {\vskip -.25cm}
\newcommand {\hsk}    {\vskip .25cm}
\newcommand {\sk}     {\vskip .5cm}
\newcommand {\dsk}    {\vskip 1cm}
\newcommand {\tsk}    {\vskip 1.5cm}
\newcommand {\qsk}    {\vskip 2cm}
\newcommand {\nl}     {\newline}
\newcommand {\pg}     {\newpage}
\newcommand {\fvfill} {\vspace*{.1mm} \vfill \vspace*{.1mm} }
%
% *** TABLES AND LISTS.
%
\newcommand {\bt}  [1] {\begin{tabular}{#1}}
\newcommand {\et}      {\end{tabular}}
\newcommand {\bct} [1] {\begin{center} \begin{tabular}{#1}}
\newcommand {\ect}     {\end{tabular}  \end{center}}
\newcommand {\bd}      {\begin{description}}
\newcommand {\ed}      {\end{description}}
\newcommand {\be}      {\begin{enumerate}}
\newcommand {\ee}      {\end{enumerate}}
\newcommand {\nbe}     {\vspace*{-.25cm} \begin{enumerate}}
\newcommand {\nee}     {\vspace*{-.25cm} \end{enumerate}}
\newcommand {\bea}     {\begin{eqnarray*}}
\newcommand {\eea}     {\end{eqnarray*}}
\newcommand {\bean}    {\begin{eqnarray}}
\newcommand {\eean}    {\end{eqnarray}}
\newcommand {\nn}      {\nonumber}
%
\newcommand {\nsi} {\vspace*{-.35cm} \item}
\newcommand {\hsi} {\vspace*{.25cm} \item}
\newcommand {\si}  {\vspace*{.5cm} \item}
\newcommand {\ssi} {\vspace*{ 1cm} \item}
\newcommand {\vfi} {\vfill \item}
\newcommand {\dvfi} {\vfill \vspace*{.1cm} \vfill \item}
\newcommand {\pgq} {\vfill \begin{flushright} \arabic{enumi} \end{flushright} \hrule \newpage}
\newcommand {\pgi} {\pgq \item}
%
\newcommand {\bi}   {\item [$\bullet$]}
\newcommand {\nsbi}  {\vspace*{-.35cm} \item[$\bullet$]}
\newcommand {\hsbi}  {\vspace*{.25cm} \item[$\bullet$]}
\newcommand {\sbi}   {\vspace*{.5cm} \item[$\bullet$]}
\newcommand {\ssbi}  {\vspace*{1.0cm} \item[$\bullet$]}
%
\newcommand {\ti}   {\item [--]}
\newcommand {\nsti}  {\vspace*{-.35cm} \item[--]}
\newcommand {\hsti}  {\vspace*{.25cm} \item[--]}
\newcommand {\sti}   {\vspace*{.5cm} \item[--]}
\newcommand {\ssti}  {\vspace*{1cm} \item[--]}
%
\newcommand {\di}   {\item [$\cdot$]}
\newcommand {\nsdi}  {\vspace*{-.35cm} \item[$\cdot$]}
\newcommand {\hsdi}  {\vspace*{.25cm} \item[$\cdot$]}
\newcommand {\sdi}   {\vspace*{.5cm} \item[$\cdot$]}
\newcommand {\ssdi}  {\vspace*{1cm} \item[$\cdot$]}
%
% *** CENTERING, FONTS, AND CENTERED FONTS.
%
\newcommand {\bc}      {\begin{center}}
\newcommand {\ec}      {\end{center}}
\newcommand {\cl}      {\centerline}
%
\newcommand {\lbf}  [1] {\large \bf #1}
\newcommand {\Lbf}  [1] {\Large \bf #1}
\newcommand {\LLbf} [1] {\LARGE \bf #1}
\newcommand {\lsf}  [1] {\large \sf #1}
\newcommand {\Lsf}  [1] {\Large \sf #1}
\newcommand {\LLsf} [1] {\LARGE \sf #1}
%
\newcommand {\cbf}  [1] {\centerline {\bf #1}}
\newcommand {\clb}  [1] {\centerline {\large \bf #1}}
\newcommand {\cLb}  [1] {\centerline {\Large \bf #1}}
\newcommand {\cLLb} [1] {\centerline {\LARGE \bf #1}}
\newcommand {\csf}  [1] {\centerline {\sf #1}}
\newcommand {\cls}  [1] {\centerline {\large \sf #1}}
\newcommand {\cLs}  [1] {\centerline {\Large \sf #1}}
\newcommand {\cLLs} [1] {\centerline {\LARGE \sf #1}}
%
% *** SECTION HEADER COMMANDS.
%
\newcommand {\seca} [1] {\section {#1} \vspace*{-.2cm}}
\newcommand {\secb} [1] {\subsection {#1}\vspace*{-.4cm}}
\newcommand {\secc} [1] {\subsubsection {#1}\vspace*{-.6cm}}
\newcommand {\secd} [1] {\paragraph {#1 ~--}}
\newcommand {\sece} [1] {\subparagraph {#1}}
%
% *** OUTLINE LIST FORMATS
%
% \renewcommand{\labelenumi}{\alph{enumi})}
% \renewcommand{\labelenumii}{\arabic{enumii})}
% \renewcommand{\labelenumiii}{(\alph{enumiii})}
% \renewcommand{\labelenumiv}{\roman{enumiv}.}
%
% **** END OF TEXTOP.INC HEADER FILE. **** 1111111111
%


%\setlength{\topmargin}{-1.5cm}
\setlength{\topmargin}{-1.5cm}
%\setlength{\topmargin}{-3cm}
\setlength{\oddsidemargin}{0cm}
\setlength{\headheight}{0cm}
\setlength{\textheight}{24cm}
\setlength{\textwidth}{16.5cm}
\setlength{\topskip}{0cm}
\setlength{\parindent}{0cm}
\setlength{\parskip}{.2in}

\pagestyle{plain}
\bibstyle{plain}
\begin{document}
%---------------------------------------------------------------- Start Page 1
{\Large \bf CS-495~~~~~
\hfill{\LARGE \bf  SYLLABUS} 
\hfill  Fall 1998}
\sk
{\bf\hrule}
\sk
\begin{minipage}[t]{7cm}
{\bf INSTRUCTOR:~}
\hsk
Roger Kieckhafer
\\
211C Ferguson Hall
\\
Phone: 2--5004 or 2--2401
\\
Email: rogerk@cse.unl.edu
\\
Hours: T.B.A. % ----------------- OFFICE HOURS ??
\end{minipage}
\hfill
\begin{minipage}[t]{7cm}
\begin{flushright}
% -------------------------------- T.A. DATA ??
{\bf TA/GRADER:}
\hsk
Maher Ali
\\
Rm 2.1, ~501~Bldg.
\\
Phone: 2--0820
\\
Email: mali@cse.unl.edu
\\
Hours: T.B.A.
\end{flushright}
\end{minipage}
\sk

{\bf INTRODUCTION --}

DESCRIPTION:~ Students are organized into teams (typically 3--4
students per team) to undertake a substantial design project proposed
and supervised by the instructor. All teams are given a broadly
defined design problem containing aspects of both software and
hardware design. Projects are of sufficient complexity as to require
team members to partition and coordinate their efforts for successful
completion.  Written technical reports and oral presentations are
essential parts of this course.

FORMAL PREREQ:~ ALEC--200, ~EE--362, ~EE--476, ~CS--430.

OTHER PREREQ:~ Intelligence, Imagination, Ingenuity, Independence,
Tenacity, Communication Skills, Teamwork.

LECTURES:~ We will adhere to the published lecture schedule only for the 
first few weeks. After that, we will not meet on a regular basis. Rather,
the lecture time will be used for periodic progress meetings and
oral reports.

LABORATORIES:~ There is no fixed laboratory period. Rather, you may work
whenever the relevant laboratories and equipment are available.

ATTENDANCE:~ You are partially responsible for the progress of your
design team.  Contact your team members and the instructor {\em as
soon as practicable\/} if you have a legitimate reason for missing any
work (e.g. illness or death in the family).  {\em The sooner the
better!\/} In most cases, some requirements or deadlines can be
adjusted.

REFERENCES:~ Since this is a design course, there is no ``required''
text as such; however, 
%we have prescribed a Ashendon's {\em The
%Designer's Guide to VHDL\/} as a reference. VHDL is a powerful tool
%used in industry, and you may find it useful in your project.  Other
useful documentation may be provided by the instructor.  You
are expected to utilize the university libraries and/or the internet
for the bulk of your information needs.

%FEES:~ A \$20.00 lab fee will be charged to cover copyright fees,
%photocopying, and other materials.  All necessary laboratory materials
%will then be provided at no additional cost to you.

\pg
%---------------------------------------------------------------- Start Page 2
{\bf CLASS SCENARIO --}

DESIGN PROJECT:~ A major corporation in the computer field is seeking a
sub-contractor to design and build a particular subsystem for a larger
system.  Each team of students works for a different company, and each
company wants to be the chosen sub-contractor. Therefore, the teams
are in competition with each other.

You will be given a Request for Proposals (RFP) stating the subsystem
requirements.  You will also be provided with a set of ``in-house''
hardware and software tools.  Your task is to perform an initial
design of the subsystem in question, construct an engineering
prototype, test it, and make a convincing presentation to the customer.
Remember, you have competitors!

INSTRUCTOR'S ROLE:~ The instuctor will play the part of your ``Project
Manager''. As such, he is not directly involved in the design or
implementation of the project. Rather, his role is managerial and
advisory. You may assume that your project manager came up through the
engineering ranks and thus is (or was) a competent computer engineer.
However, in the last few years, his time has been consumed more by
management duties than by technical duties -- so he may be a bit
``rusty''.  Furthermore, your project manager has several other
projects also under his supervision, so he can not give complete
attention to yours.

Other faculty members may be asked to play the part of ``Customer 
Representatives'' at one or more points during the semester. Their
goal will be to protect the best interests of their own company.
They should be considered intelligent and well versed in the 
subsystem specification.

ACADEMIC HONESTY:~ Each team is  to work independently from the
other teams. Remember, {\em you are competitors\/}!  Any attempt at
sabotage, industrial espionage, or theft of intellectual
property will be grounds for the immediate awarding of an ``F'' for
the course and/or the filing of formal charges with the 
Judicial Affairs office.  Similarly, you may not plagiarize designs
from the published literature.  However, borrowing and adapting
{\em ideas\/} from the literature {\em is permitted\/} as long as you
properly credit the originators of those ideas.

Conversely, you are responsible to safeguard your own ``Proprietary
Information'' so it does not become ``public domain'' through
carelessness.  Thus, no other teams will be present for first two
reports.  However, all teams will be present for the final report.


\pg
%---------------------------------------------------------------- Start Page 3
{\bf GRADING POLICIES --}

GENERAL:~ There will be {\em no\/} homework, 1 Prerequisite Test (PT), and
3 project reports. Each project report will
have both a {\em Written\/} Component and an {\em Oral\/} Component.
Each report must be a ``stand-alone'' report which does
{\em not\/} assume familiarity with earlier reports.


EXPECTATIONS AND WEIGHTS:~ The graded components, and their respective
weights are listed below.
The grade for {\em each\/} project report will be based:
\be
\nsbi 50\% on the technical merit of the design\,\footnote{Remember: a good 
report can not disguise a bad design, but a bad report {\em can\/} 
disguise a good design.},
\bi 25\% on the quality and clarity of the written component,
\bi 25\% on the quality and clarity of the oral component.
\ee

\bd
\nsi [Prerequisite Test (10\%) -- ] A take-home test covering a broad range
of prerequisite knowledge. Due the $2^{nd}$ or $3^{rd}$ week of class. 

\item [Report 1: Project Proposal (20\%) -- ]
Approximately the $4^{th}$ to $5^{th}$ week of class, each team will
present to the {\em Project Manager\/} a proposal in which they show a
{\em clear understanding of the problem\/}, describe their general
approach, and discuss specific design issues and solution options.
The report should focus on high level ``architectural'' issues more
than on implementation details.

\item [Report 2: Progress Report (30\%) -- ] 
Approximately the $8^{th}$ to $10^{th}$ week of class, each team will
present to the {\em Project Manager\/} a report describing your {\em
progress to date\/}, options selected, deviations from the original
proposal, and plans for completing the project. By this time, only one
option should remain.  Also, implementation and testing plans should
be addressed in this report.

\item [Report 3: Final Proposal (40\%) -- ] 
During the last week of class (alias dead week\footnote{In accordance
with UNL Dead Week policies, you have now been informed in writing of
the nature and scope of this report prior to the eighth week of
classes.}) each team will present to {\em the Project Manager, the
Customer Representatives, and the rest of the class\/} a final
proposal, detailing the design, testing, and performance of the
project.  A demonstration may also be required.
\ed

\end{document}

