Updates to Assurance Case lecture - mostly admin details

Lectures/L22_AssuranceCase/AssuranceCase.tex

@@ -43,11 +43,13 @@
 
 \bi
 \item Administrative details
-%\item Feedback on MG
+  % \item Feedback on MG
+\item Make
 \item Final documentation
 \item Questions?
 \item License and copyright
 \item Assurance cases
+\item Course Evaluations
 \ei
 \end{frame}
 
@@ -59,20 +61,12 @@
 \bi
 \item Course evaluation
 \bi
-\item Thurs, Nov 22, 10:00 am to Thurs, Dec 6, 11:59 pm
+\item Thurs, Nov 21, 10:00 am to Thurs, Dec 5, 11:59 pm
 \item \url{https://evals.mcmaster.ca}
-\ei
-\item No class on Friday, Nov 30
-\item GitHub issues for colleagues
-\bi
-\item Assigned 1 colleague (see \texttt{Repos.xlsx} in repo)
-\item Provide at least 5 issues on their MIS
-\item Grading as before
-\item Due by Friday, Nov 30, 11:59 pm
+\item Time to complete during class today
 \ei
 \item Today is the last ``lecture''
-\item Next week and following for presentations
-%\item Following Tuesday for Discussion
+\item Next week for presentations (technically one day past the end of term)
 \ei
 
 \end{frame}
@@ -80,23 +74,43 @@
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \begin{frame}
-\frametitle{Administrative Details: Deadlines}
+\frametitle{Administrative Details: Report Deadlines}
 ~\newline
 \begin{tabular}{l l l}
-\textbf{MIS} & Week 11 & Nov 23\\
-Unit VnV or Impl.\ Present & Week 12, 13 & Wed, Nov 28, Dec 5\\
-Unit VnV Plan & Week 13 & Dec 3\\
-Final Doc & Week 14 & Dec 10\\
+Final Documentation & Week 14 & Dec 9\\
 \end {tabular}
 
-\begin{itemize}
-\item Roll Unit VnV Plan into Final Documentation?
-\item Git issues for Final Documentation?
-\end{itemize}
+\bi
+\item The written deliverables will be graded based on the repo contents as of
+11:59 pm of the due date
+\item If you need an extension, please ask
+\item Two days after each major deliverable, your GitHub issues will be due
+\item Domain expert code due 1 week after MIS deadline (after assigned issue by
+  project owner)
+\ei
 
 \end{frame}
 
-%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Administrative Details: Presentations}
+
+~\newline
+\begin{tabular}{l l l}
+Unit VnV or Impl.\ Present & Week 13 & Week of Dec 2\\
+\end {tabular}
+
+\bi
+\item Informal presentations with the goal of improving everyone's written
+  deliverables
+\item Domain experts and secondary reviewers (and others) will ask questions
+  (listed in Repos.xlsx file)
+\ei
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \begin{frame}
 \frametitle{Administrative Details: Presentation Schedule}
@@ -104,10 +118,22 @@ Final Doc & Week 14 & Dec 10\\
 \bi
 \item Unit VnV Plan or Impl.\ Present
 \bi
-\item Wednesday (Nov 28): Brooks, Vajiheh
-\item Wednesday (Dec 5): Olu, Karol
+\item Monday: Bo, Sasha, ?
+\item Thursday: Zhi, Peter, Ao
 \ei
-\item Can present anything related to the implementation or testing
+\ei
+
+Optional presentation in italics.\\
+Room for more volunteers.  :-)
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Administrative Details: Unit VnV or Impl.\ Present}
+
+Can present anything related to the implementation or testing
 \bi
 \item Code
 \item Tools used
@@ -117,7 +143,6 @@ Final Doc & Week 14 & Dec 10\\
 \item As always it is fine to show work in progress
 \item Good to bring questions to the class
 \ei
-\ei
 
 \end{frame}
 
@@ -139,6 +164,20 @@ Final Doc & Week 14 & Dec 10\\
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Make}
+\begin{itemize}
+\item
+  \href{https://gitlab.cas.mcmaster.ca/smiths/se3xa3/blob/master/Labs/L12/Lab12.pdf}
+  {Tutorial on Make, with links}
+\item
+  \href{https://github.com/smiths/caseStudies/blob/master/CaseStudies/glass/src/Python/Makefile}
+  {Example Makefile for GlassBR}
+\end{itemize}
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \begin{frame}
 \frametitle{Unit VnV Plan}
 \begin{itemize}
@@ -151,7 +190,7 @@ Final Doc & Week 14 & Dec 10\\
 \item Non-testing based verification (if planned)
 \item Unit test cases for each module - from black box and white box
 \item Performance tests for individual modules
-  \item Evidence that all modules are considered
+\item Evidence that all modules are considered
 \end{itemize}
 \end{frame}
 
@@ -279,6 +318,8 @@ Final Doc & Week 14 & Dec 10\\
   not on the rational for test case selection, but on the results.
 \item If your test plan does not match what you are now testing, edit your test
   plan to ``fake'' a rational design process.
+\item If your test report is not complete, because there is not time for all of
+  the tests, explain this in your report
 \end{itemize}
 \end{frame}
 
@@ -354,7 +395,8 @@ Final Doc & Week 14 & Dec 10\\
   \href{https://github.com/palmerst/CS-4ZP6/tree/master}{2D Physics Based Game}
   (Uses doxygen)
 \item
-  \href{https://gitlab.cas.mcmaster.ca/smiths/cas741/tree/master/BlankProjectTemplate/Doc/TestReport}{Follow given template}
+  \href{https://gitlab.cas.mcmaster.ca/smiths/cas741/tree/master/BlankProjectTemplate/Doc/TestReport}
+  {Follow given template}
 \item Examples are not perfect
 \item Examples are intended to give you ideas, not to be strictly followed
 \item You can modify/extend the test report template as appropriate
@@ -368,7 +410,7 @@ Final Doc & Week 14 & Dec 10\\
 \frametitle{Questions?}
 \begin{itemize}
 \item Questions about MIS documentation?
-\item Questions about implementation presentations?
+\item Questions about implementation?
 \end{itemize}
 \end{frame}