Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cas741
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
W. Spencer Smith
cas741
Commits
1dfb2311
Commit
1dfb2311
authored
5 years ago
by
W. Spencer Smith
Browse files
Options
Downloads
Patches
Plain Diff
Updates for mathematical review lecture
parent
be55deee
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
Lectures/L17_MathReviewPlusExample/MathReviewPlusExample.pdf
+0
-0
0 additions, 0 deletions
Lectures/L17_MathReviewPlusExample/MathReviewPlusExample.pdf
Lectures/L17_MathReviewPlusExample/MathReviewPlusExample.tex
+43
-45
43 additions, 45 deletions
Lectures/L17_MathReviewPlusExample/MathReviewPlusExample.tex
with
43 additions
and
45 deletions
Lectures/L17_MathReviewPlusExample/MathReviewPlusExample.pdf
+
0
−
0
View file @
1dfb2311
No preview for this file type
This diff is collapsed.
Click to expand it.
Lectures/L17_MathReviewPlusExample/MathReviewPlusExample.tex
+
43
−
45
View file @
1dfb2311
...
...
@@ -68,16 +68,15 @@
\bi
\item
SRS grades on Avenue
\item
If follow feedback, final doc grades will be higher
\item
GitHub issues for colleagues
\item
GitHub issues for colleagues
for MG+MIS
\bi
\item
Assigned 1 colleague (see
\texttt
{
Repos.xlsx
}
in repo)
\item
Provide at least 3 issues on their MG
\item
Grading as before
\item
Due
by Thursday, Nov 8, 11:59 pm
\item
Due
within 2 days of being assigned the review issue
\ei
\item
MG marking scheme in Avenue
\item
MIS marking scheme in Avenue
\item
Updated MIS template in CAS 741 repo (soon)
\ei
\end{frame}
...
...
@@ -109,8 +108,7 @@ Final Documentation & Week 14 & Dec 9\\
~
\newline
\begin{tabular}
{
l l l
}
MG + MIS Syntax Present
&
Week 9
&
Week of Nov 4
\\
MIS Semantics Present
&
Week 11
&
Week of Nov 18
\\
\textbf
{
MIS Semantics Present
}
&
Week 11
&
Week of Nov 18
\\
Unit VnV or Impl.
\
Present
&
Week 12/13
&
Week of Nov 28
\\
\end
{
tabular
}
...
...
@@ -129,7 +127,7 @@ Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
\frametitle
{
Administrative Details: Presentation Schedule
}
\bi
\item
MIS Syntax + Semantics Present
\item
\textbf
{
MIS Syntax + Semantics Present
}
\bi
\item
Monday: Zhi, Peter,
\emph
{
Sasha
}
\item
Thursday: Sharon, Ao, ?
...
...
@@ -158,42 +156,42 @@ Room for more volunteers. :-)
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
%
\begin{frame}
\frametitle
{
SRS Feedback: Relationships Between Parts
}
%
\frametitle{SRS Feedback: Relationships Between Parts}
\begin{figure}
[H]
\includegraphics
[scale=0.59]
{
../Figures/RelationsBetweenTM
_
GD
_
IM
_
DD
_
A.pdf
}
\end{figure}
%
\begin{figure}[H]
%
\includegraphics[scale=0.59]{../Figures/RelationsBetweenTM_GD_IM_DD_A.pdf}
%
\end{figure}
\end{frame}
%
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
%
\begin{frame}
\frametitle
{
SRS Feedback
}
%
\frametitle{SRS Feedback}
\begin{itemize}
\item
\texttt
{
*.DS
\_
Store
}
should be in
\texttt
{
.gitignore
}
\item
\LaTeX
{}
and formatting rules
\begin{itemize}
\item
Variables are italic, everything else not, includes subscripts (link to
document)
\bi
\item
\href
{
https://physics.nist.gov/cuu/pdf/typefaces.pdf
}{
Conventions
}
\item
Watch out for implied multiplication
\ei
\item
Use BibTeX
\item
Use cross-referencing
\end{itemize}
\item
Grammar and writing rules
\begin{itemize}
\item
Acronyms expanded on first usage (not just in table of acronyms)
\item
``In order to'' should be ``to''
\end{itemize}
\end{itemize}
\end{frame}
%
\begin{itemize}
%
\item \texttt{*.DS\_Store} should be in \texttt{.gitignore}
%
\item \LaTeX{} and formatting rules
%
\begin{itemize}
%
\item Variables are italic, everything else not, includes subscripts (link to
%
document)
%
\bi
%
\item \href{https://physics.nist.gov/cuu/pdf/typefaces.pdf}{Conventions}
%
\item Watch out for implied multiplication
%
\ei
%
\item Use BibTeX
%
\item Use cross-referencing
%
\end{itemize}
%
\item Grammar and writing rules
%
\begin{itemize}
%
\item Acronyms expanded on first usage (not just in table of acronyms)
%
\item ``In order to'' should be ``to''
%
\end{itemize}
%
\end{itemize}
%
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
...
...
@@ -202,19 +200,19 @@ Room for more volunteers. :-)
\frametitle
{
SRS Feedback on Applying Template
}
\begin{itemize}
\item
Difference between physical and software constraints
\item
Properties of a correct solution means
\emph
{
additional
}
properties, not
a restating of the requirements (may be ``not applicable'' for your problem).
If you have a table of output constraints, then these are properties of a
correct solution.
%
\item Difference between physical and software constraints
%
\item Properties of a correct solution means \emph{additional} properties, not
%
a restating of the requirements (may be ``not applicable'' for your problem).
%
If you have a table of output constraints, then these are properties of a
%
correct solution.
\item
Assumptions have to be invoked somewhere
\item
``Referenced by'' implies that there is an explicit reference
\item
Think of traceability matrix, list of assumption invo
k
ations and list of
reference by fields as automatically generatable
\item
If you say the format of the output (plot, table etc), then your
requirement could be more abstract
\item
For families the notion of binding time should be introduced
\item
Think of families as a library, not as a single program
%
\item Think of traceability matrix, list of assumption invo
c
ations and list of
%
reference by fields as automatically generatable
%
\item If you say the format of the output (plot, table etc), then your
%
requirement could be more abstract
%
\item For families the notion of binding time should be introduced
%
\item Think of families as a library, not as a single program
\end{itemize}
\end{frame}
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment