-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathcourseoutline-example.tex
130 lines (104 loc) · 4.23 KB
/
courseoutline-example.tex
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
%
% Copyright (c) 2014, Jonathan Anderson <[email protected]>.
% All rights reserved.
%
% Redistribution and use in source and binary forms, with or without
% modification, are permitted provided that the following conditions are met:
%
% 1. Redistributions of source code must retain the above copyright notice,
% this list of conditions and the following disclaimer.
%
% 2. Redistributions in binary form must reproduce the above copyright notice,
% this list of conditions and the following disclaimer in the documentation
% and/or other materials provided with the distribution.
%
% THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
% AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
% IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
% ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
% LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
% CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
% SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
% INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
% CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
% ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
% POSSIBILITY OF SUCH DAMAGE.
%
%
% The courseoutline class currently accepts two options:
%
% - engineering: Use the names "Engineering", "Faculty of Engineering", etc.
% in the relevant places and emit the Faculty's policy on
% academic integrity ("Like Professional Engineers...").
% - safelabs: Don't emit a "Lab Safety" section even if a lab slot is
% declared with \lab{}{}. This is intended for use with
% computer labs (not electrical, structural, chemical labs).
%
\documentclass[engineering]{courseoutline}
\coursename{Fundamentals of Widgets}
\coursenumber{1000}
\courseterm{Fall 2014}
\prerequisites{MATH1000}
\officialdescription{
Engineering 1000 Fundamentals of Widgets provides first-year students
with introductory exposure to the analysis and design of widgets.
Topics include widget geometry, statics, dynamics and the application
of electricity to non-conductive widgets.
}
%\fulldescription{a longer, perhaps less official, description}
\website{http://www.engr.mun.ca/teaching/ENGI1000}
%\communication{Distance learning / web submission details}
\instructor{Your name}
\email{[email protected]}
\phone{864-1234}
\office{EN1234}
\officehours{Tue 15:00--16:00}
\ta{Ingrid M Engineer (\href{[email protected]}{imeng})}
\lecture{MWF}{15:00}{15:50}{EN-1054}
\lab{W}{10:00}{11:50}{EN-3000/3029}
\tutorial{F}{9:00}{9:50}{EN-3000/3029}
\acceditationunits{
46 Combined Educational Hours.
Focus: 100\% Engineering Science.
}
\credithours{3}
\labhours{2}
\labtimes{At least four 2-hour sessions per semester}
\otherrequirements{Tutorial one hour per week}
\begin{document}
\maketitle
\section{Major Topics}
\begin{itemize}
\item Widget fundamentals
\item Widget analysis
\item Widgets and society
\item Advanced widget design
\end{itemize}
\section{Learning Outcomes}
Upon successful completion of this course, the student will be able to:
\begin{enumerate}
\item explain the theoretical foundations of widgets,
\item analyze the design and application of a standard widget,
\item design simple widgets,
\item synthesize widget specifications and
\item evaluate the fitness of a widget for a specification.
\end{enumerate}
\section{Assessment}
Assignments will be given \dots
Written evaluation will take place in October and during the final exam
weeks (8--17~Dec).
The month of November should largely be used for project work.
\vspace{1em}
\begin{tabular}{llr}
\head{Assignments (5/6)} & & 10\% \\
\qquad Assignment 0 & 15 September & \\
\qquad Assignment 1 & 22 September & \\
\qquad Assignment 2 & 29 September & \\
\qquad Assignment 3 & 6 October & \\
\head{Quiz} & 3 October & 5\% \\
\head{Midterm exam} & 17 October & 15\% \\
\head{Project} & 1 December & 20\% \\
\head{Final Exam} & & 50\%
\end{tabular}
\boilerplate
\end{document}