Lectures/L13_ModularDesign/ModularDesign.tex

@@ -64,6 +64,7 @@
 \bi
 \item For the design documentation you do not have to use the MG and 
 MIS templates
+\item No lecture on Friday, March 21
 %\item GitHub issues
 %\bi
 % \item When closing issues give the hash for the corresponding commit
@@ -89,44 +90,44 @@ MIS templates
 \input{../Deadlines.tex}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\begin{frame}
-\frametitle{Feedback on SRS}
-\begin{itemize}
-\item
-\href{https://github.com/smiths/capTemplate/blob/main/docs/Checklists/SRS-Checklist.pdf}
-{SRS checklist}
-\begin{itemize}
-  \item Follow the template
-  \item Filename for SRS from template (new)
-  \item All symbols are in the table of contents
-  \item Project is given a name
-  \item Characteristics with courses and level (clarified)
-  \item Goal statements are functional (new)
-  \item Each assumption is used at least once
-  \item All chunks are used at least once (new)
-  \item IMs are referenced by requirements
-\end{itemize}
-\end{itemize}
-\end{frame}
+% \begin{frame}
+% \frametitle{Feedback on SRS}
+% \begin{itemize}
+% \item
+% \href{https://github.com/smiths/capTemplate/blob/main/docs/Checklists/SRS-Checklist.pdf}
+% {SRS checklist}
+% \begin{itemize}
+%   \item Follow the template
+%   \item Filename for SRS from template (new)
+%   \item All symbols are in the table of contents
+%   \item Project is given a name
+%   \item Characteristics with courses and level (clarified)
+%   \item Goal statements are functional (new)
+%   \item Each assumption is used at least once
+%   \item All chunks are used at least once (new)
+%   \item IMs are referenced by requirements
+% \end{itemize}
+% \end{itemize}
+% \end{frame}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
-\begin{frame}
-\frametitle{Feedback on SRS}
-\begin{itemize}
-\item
-\href{https://github.com/smiths/capTemplate/blob/main/docs/Checklists/Writing-Checklist.pdf}
-{Writing checklist}
-\begin{itemize}
-  \item Opening and closing ``quotes''
-  \item Periods that do not end sentences are followed by only one space
-  \item Long names in math mode use either mathit or text
-  \item Document is spell checked
-  \item Symbols formatted the same way in every context %inside and outside equations
-\end{itemize}
-\item Types information very helpful
-\end{itemize}
-\end{frame}
+% \begin{frame}
+% \frametitle{Feedback on SRS}
+% \begin{itemize}
+% \item
+% \href{https://github.com/smiths/capTemplate/blob/main/docs/Checklists/Writing-Checklist.pdf}
+% {Writing checklist}
+% \begin{itemize}
+%   \item Opening and closing ``quotes''
+%   \item Periods that do not end sentences are followed by only one space
+%   \item Long names in math mode use either mathit or text
+%   \item Document is spell checked
+%   \item Symbols formatted the same way in every context %inside and outside equations
+% \end{itemize}
+% \item Types information very helpful
+% \end{itemize}
+% \end{frame}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
@@ -242,12 +243,12 @@ MIS templates
 \begin{frame}
 \frametitle{SWHS MG Example}
 ~\\
-\href{https://github.com/smiths/swhs/tree/master/docs/Design/MG}
-{https://github.com/smiths/swhs/tree/master/docs/Design/MG}
+
+\href{https://github.com/smiths/swhs/blob/master/docs/Design/MG/PCM_MG.pdf} {Module Guide for Solare Water Heating System Incorporating Phase Change Material (PCM)} 
+
 \end{frame}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-
 \begin{frame}
 \frametitle{What is Design?}
 \begin{itemize}

Lectures/L15_MIS/MIS.tex

@@ -47,8 +47,8 @@
 \bi
 \item Administrative details
 \item Questions?
-%\item Finish previous day slides
-\item Module guide example
+%\item Module guide example
+\item Mathematical fundamentals
 \item MIS example
 \item Integration testing
 \item MIS overview
@@ -66,27 +66,12 @@
 \frametitle{Administrative Details}
 
 \bi
-% \item When developing your code, remember that your goal is for someone else to
-%   be able to compile and run it
-% \item Upcoming classes
-% \bi
-% \item L15 - Module Interface Specification
-% \item L16 - Math Review + MIS
-% \item L17 - POC + MG Presentations
-% \item L18 - MIS Presentations
-% \ei
-\item Friday's class in ITB/201
-\item Mathematical review
-\begin{itemize}
-  \item \cite{HoffmanAndStrooper1995}
-  \item \href{https://gitlab.cas.mcmaster.ca/smiths/cas741/-/tree/master/Lectures/MathReviewPlusExample} {Review Slides}
-  \item \href{https://gitlab.cas.mcmaster.ca/smiths/se2aa4_cs2me3/-/blob/master/MISFormat/MISFormat.pdf} {MIS Format}
-\end{itemize}
 \item Potential software for drawing figures
 \bi
 \item \href{https://app.diagrams.net/} {draw.io}
 \item \href{https://www.bu.edu/math/files/2013/08/tikzpgfmanual.pdf} {Tikz} 
 \ei
+%\item Go over final grading rubric, traceability Rev0 to Rev1
 \ei
 
 \end{frame}
@@ -140,10 +125,29 @@
 \begin{frame}
 \frametitle{Emphasis}
 \begin{itemize}
-\item Math notation (stoichiometry example on Friday)
-\item GUI modules (environment variables)
+\item Math notation
+\item Modules with external interaction (environment variables)
 \item Types of modules
 \item Abstract Data Types (graph example)
+\item Qualities of an interface
+\item Design patterns
+\begin{itemize}
+  \item Adapter (Wrapper) pattern
+  \item Strategy pattern
+\end{itemize}
+\end{itemize}
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Mathematical review}
+
+\begin{itemize}
+  \item Hoffman and Strooper (1995) \cite{HoffmanAndStrooper1995}
+  \item \href{https://gitlab.cas.mcmaster.ca/smiths/se2aa4_cs2me3/-/blob/master/MISFormat/MISFormat.pdf} {MIS Format}
+  \item \href{https://gitlab.cas.mcmaster.ca/smiths/cas741/-/tree/master/Lectures/MathReviewPlusExample} {Stoichiometry Example} %not a great approach, can tell by bad names
+  \item MoleculeT = seq[108] of $\mathbb{N}$
 \end{itemize}
 \end{frame}
 
@@ -166,7 +170,7 @@
 \frametitle{Solar Water Heating System Example}
 
 \bi
-\item \href{https://github.com/smiths/swhs}{https://github.com/smiths/swhs}
+\item \href{https://github.com/smiths/swhs/tree/master} {https://github.com/smiths/swhs/tree/master}
 \item Solve ODEs for temperature of water and PCM
 \item Solve for energy in water and PCM
 \item Generate plots
@@ -585,7 +589,7 @@ are isolated to their own access programs (like submodules). %    This, combined
 \frametitle{MIS Example: SWHS}
 
 \bi
-\item \href{https://github.com/smiths/swhs}{https://github.com/smiths/swhs}
+\item \href{https://github.com/smiths/swhs/tree/master}{https://github.com/smiths/swhs/tree/master}
 \item Has some constant values
 \item Input parameters
 \item Solve ODEs for temperature of water and PCM

Lectures/L16_MISContinued/MISContinued.tex

@@ -45,6 +45,7 @@
 \frametitle{MIS Continued}
 
 \bi
+\item ADD STRATEGY DESIGN PATTERN
 \item Administrative details
 \item Questions?
 \item Review: Records, Libraries, ADTs, Abstract Objects, Generic ADTs
@@ -94,6 +95,24 @@
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Emphasis}
+\begin{itemize}
+\item Math notation
+\item Modules with external interaction (environment variables)
+\item Types of modules
+\item Abstract Data Types
+\item Qualities of an interface
+\item Design patterns
+\begin{itemize}
+  \item Adapter (Wrapper) pattern
+  \item Strategy pattern
+\end{itemize}
+\end{itemize}
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 % \begin{frame}
 % \frametitle{Nonfunctional Requirements}
 % \begin{itemize}
@@ -1084,6 +1103,217 @@ where $a$, $b$ and $c$ are suitable constants
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Design Patterns}
+
+\begin{itemize}
+
+\item Christopher Alexander (1977, buildings/towns):
+\begin{itemize}
+\item ``Each pattern describes a problem which occurs over and over again in our
+  environment, and then describes the core of the solution to that problem, in
+  such a way that you can use this solution a million times over, without ever
+  doing it the same way.''
+\end{itemize}
+\item Design reuse (intended for OO)
+\item Solution for recurring problems
+\item Transferring knowledge from expert to novice
+%\item Provides language for communicating about design
+\item A design pattern is a recurring structure of communicating components that
+  solves a general design problem within a particular context
+\item Design patterns consist of multiple modules, but they do not constitute an
+  entire system architecture
+\end{itemize}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Adapter Design Pattern}
+
+\includegraphics[scale=0.7]{500px-AdapterPatternForWiki.jpg}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Adapter UML Diagram}
+% client uses target (follows targets interface)
+% client, adapter and adaptee appear as in previous slide
+\medskip
+\includegraphics[scale=0.7]{adapter_clip.pdf}
+
+\href{https://en.wikipedia.org/wiki/Adapter_pattern}
+{Wikipedia entry}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{SimUDuck Example}
+
+\bigskip
+
+\includegraphics[scale=0.74]{StratPat-SimUDuck.pdf}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Adding a Fly Method}
+
+\bigskip
+
+\includegraphics[scale=0.85]{StratPat-FlyMethod.pdf}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Rubber Duck Problem}
+
+\includegraphics[scale=0.7]{StratPat-RubberDuck.pdf}
+
+\structure{How to stop rubber ducks from flying?} %override to do nothing
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Rubber Duck Problem Continued}
+
+\bi
+\item Solve problem by overriding the fly() method to do nothing
+\item Not a good solution - think of the potential maintenance problems if we
+  add wooden decoys, which cannot fly, or quack - what about different quacks?
+\ei
+
+Which of the following are disadvantages of using inheritance to provide Duck
+behaviour?
+
+\begin{enumerate}[A.]
+\item Some code is duplicated across subclasses
+\item Runtime behaviour changes are difficult
+\item Difficult to gain knowledge of all duck behaviours
+\item Changes can unintentionally affect other ducks
+\item All of the above %answer
+\end{enumerate}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{How About an Interface?}
+
+\includegraphics[scale=0.75]{StratPat-Interface.pdf}
+
+Disadvantages of interface?
+
+\begin{enumerate}[A.]
+\item Maintenance nightmare - the different options for fly and quack are
+  duplicated everywhere %answer
+\item Ducks that have fly and quack are clearly shown
+\item All of the above
+\end{enumerate}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Information Hiding}
+
+How can the principle of information hiding help us?
+
+\begin{enumerate}[A.]
+\item Identify the aspects of the application that are likely to change and
+  separate them from what is unlikely to change
+\item Provide a means for part of the system to vary independently of the other
+  parts
+\item Prevent the program's user from knowing which ducks can fly and/or quack
+\item A and B %answer
+\item A, B and C
+\end{enumerate}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Separate Out Changeable Parts (Likely Changes)}
+
+\bigskip
+
+\includegraphics[scale=0.85]{StratPat-DuckBehaviours.pdf}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Implementing the Duck Behaviours}
+
+\bigskip
+
+\includegraphics[scale=0.66]{StratPat-ImpDuckBehaviours.pdf}
+
+\bi
+\item Program to an interface not an implementation (interface in the sense we have
+used it for MISes, not just a Java interface)
+\item Other modules can use these behaviours too
+\item Can add new behaviours without touching the original Duck class
+\ei
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{The Big Picture}
+
+\bigskip
+
+\includegraphics[scale=0.66]{StratPat-BigPicture.pdf}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Often Favour Composition over Inheritance}
+
+\bi
+\item Composition provides a ``has a'' relationship, as opposed to an ``is a''
+  relationship
+\item Composition provides greater flexibility
+\item Composition allows changing behaviour at runtime
+\item Many languages (like Java) do not allow multiple inheritance, but can have
+  multiple compositions
+\ei
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Strategy Pattern}
+
+Defines a family of algorithms, encapsulates each one, and makes them
+interchangeable.  Strategy lets the algorithm vary independently from the
+clients that use it.
+
+\includegraphics[scale=0.6]{Strategy1.png}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \begin{frame}[allowframebreaks]
 \frametitle{References}
 

Lectures/L19_AssuranceCase/AssuranceCase.tex

@@ -62,16 +62,26 @@
 
 \bi
 \item Draft participation grade
-\item When developing your code, remember that your goal is for someone else to be able to compile and run it
-\item Upcoming classes
-\bi
-\item L19 --- Assurance Cases
-\item L20 --- Artifact Generation
-\item L21 --- A Holistic Approach 
-\item L22 --- Drasil Presentations
-\item L23--24 --- Implementation/Testing Presentations
-\item L25 --- Discussion
-\ei
+\item Grades posted for domain expert issues
+\item When developing your code, remember that your goal is for someone else to
+be able to compile and run it
+\item If you project is non-research, you need to complete an extra to get
+access all potential marks on the final documentation
+\item Make sure I can find your extra 
+\begin{itemize}
+  \item Make sure \texttt{Repos.csv} is up to date
+  \item Put the extra in the correct spot according to \texttt{capTemplate}
+  \item Delete extras (and SRS files) you aren't using
+\end{itemize}
+% \item Upcoming classes
+% \bi
+% \item L19 --- Assurance Cases
+% \item L20 --- Artifact Generation
+% \item L21a--24 --- Implementation/Testing Presentations
+% \item L21b --- A Holistic Approach (not this year)
+%\item L22 --- Drasil Presentations
+%\item L25 --- Discussion
+% \ei
 \item No requirement to provide feedback to colleagues on final documentation
 \ei
 
@@ -79,6 +89,16 @@
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Course Evaluations}
+\begin{itemize}
+\item Course experience surveys will close on Tuesday, April 8, 2025 11:59 PM
+\item \url{https://mcmaster.bluera.com/mcmaster/}
+\end{itemize}
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \input{../Deadlines.tex}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -99,6 +119,32 @@
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Implementation/Final Presentations}
+\begin{itemize}
+\item Based on your implementation and testing
+\item You decide what to focus on
+\item If in doubt, ask
+\item Options
+\begin{itemize}
+  \item Demonstration
+  \item Summarize testing results
+  \item Usability test with the class (show of hands for data)
+  \item Code walkthrough with class
+  \item Usability survey with class
+  \item Technology overview
+  \begin{itemize}
+    \item CI/CD
+    \item Valgrind
+    \item Doxygen
+    \item etc.
+  \end{itemize}
+\end{itemize}
+\end{itemize}
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \begin{frame}
 \frametitle{Final Documentation}
 \begin{itemize}
@@ -113,10 +159,13 @@ requirement and trace it all the way to testing
 \ei
 \item Make it easy to see changes from Rev 0
 \bi
-\item \href{https://github.com/smiths/capTemplate/tree/main/docs/Reflection} {Reflection document}
+\item \href{https://github.com/smiths/capTemplate/blob/main/docs/ReflectAndTrace/ReflectAndTrace.pdf} {Reflection and traceability document}
 \item Closed issues in the issue tracker
 \item Specific explanation in Revision History
-\item Comments in tex file
+\item Summarize with a table, if possible
+\item Use \href{https://commandmasters.com/commands/latexdiff-common/}
+{latexdiff} between Rev0 and Rev1 documents, if necessary
+\item Comments in tex file (last resort)
 \ei
 \end{itemize}
 \end{frame}
@@ -126,6 +175,7 @@ requirement and trace it all the way to testing
 \begin{frame}
 \frametitle{Final Documentation}
 \begin{itemize}
+\item Faking a rational design process
 \item Problem Statement revised and improved
 \item Requirements Document revised and improved
 \item Design Documents revised and improved
@@ -137,36 +187,53 @@ requirement and trace it all the way to testing
 \item VnV Report
 \item Source Code
 \item Drasil projects no longer need to maintain the traditionally generated SRS
-\item \href{https://github.com/smiths/capTemplate/tree/main/docs/Reflection} {Reflection Document}
+\item \href{https://github.com/smiths/capTemplate/blob/main/docs/ReflectAndTrace/ReflectAndTrace.pdf} {Reflection Document}
 \end{itemize}
 \end{frame}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \begin{frame}
-\frametitle{Final Doc: Reflection}
+\frametitle{Final Doc: Reflect and Trace}
 \begin{itemize}
-\item Reflection document updated in
-\href{https://github.com/smiths/capTemplate/tree/main/docs/Reflection}
+\item Reflect and trace document in
+\href{https://github.com/smiths/capTemplate/blob/main/docs/ReflectAndTrace/ReflectAndTrace.pdf}
 {capTemplate repo}
 
-\item Summarize changes in response to feedback from reviewers,
-instructor, supervisor, users
+\item Summarize response to ALL feedback
+\item Each item of feedback should be treated separately
+\begin{itemize}
+  \item Identify source (reviewers, instructor, supervisor, users)
+  \item Give response
+  \item Summary of issue
+  \item Hyperlink to issue (if available)
+  \item Summary of change (include hyperlink if available)
+  \item Reasoning for not changing (include hyperlink if available)
+\end{itemize}
 \item Explain how you arrived at your final design and implementation
 \item Reflect on and justify your design decisions
-\item Ignore questions related to:
-\begin{itemize}
-  \item Hazard analysis
-  \item Economic considerations
 \end{itemize}
-\item How did your project management compare to your dev plan
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\begin{frame}
+\frametitle{Final Doc: Reflection Cont'd}
 \begin{itemize}
-  \item What went well? (continue)
-  \item What went wrong? (stop)
-  \item What would you do differently next time? (start)
-\end{itemize}
-% \item Applies the principles of equity and universal design to ensure equitable
-% treatment of all stakeholders
+  \item Ignore questions related to:
+  \begin{itemize}
+    \item Hazard analysis
+    \item Economic considerations
+    \item Feedback on capstone
+  \end{itemize}
+  \item How did actual project management compare to dev plan
+  \begin{itemize}
+    \item What went well? (continue)
+    \item What went wrong? (stop)
+    \item What would you do differently next time? (start)
+  \end{itemize}
+  % \item Applies the principles of equity and universal design to ensure equitable
+  % treatment of all stakeholders
 \end{itemize}
 \end{frame}
 
@@ -176,8 +243,10 @@ instructor, supervisor, users
 \frametitle{Final Project Quality}
 \begin{itemize}
 \item Installability - instructions given, makefiles etc to support, means to
-  validate the installation, required libraries are explicitly identified
-\item Learnability - instructions to get someone started using the software
+  validate the installation, required libraries are explicitly identified --
+  update README.md and INSTALL.md
+\item Learnability - instructions to get someone started using the software --
+give instructions on how to run the software, how to execute the tests
 \item Robustness - can the software handle garbage inputs reasonably
 \item Performance - measured if appropriate
 \item Usability - measured if appropriate
@@ -197,6 +266,7 @@ instructor, supervisor, users
 \item Use a ``light weight'' VM like docker
 \item Include installation instructions (INSTALL.txt)
 \item Include instructions so that someone else can run your tests cases
+\item Part of the evaluation of each project is to run it
 \ei
 
 \end{frame}
@@ -217,6 +287,30 @@ instructor, supervisor, users
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Extras}
+
+\begin{itemize}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/CodeWalkthroughs} {Code Walkthrough Report}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/CostAnalysisReport} {Cost Analysis Report} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/DesignThinking} {Design Thinking Report}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/FormalProof} {Formal Proof Report} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/GenderMagPersonas} {Gender Mag Personas Report}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/GreenComputing} {Green Computing Report} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/LiteratureReview} {Literature Review Report}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/NormansPrinciples} {Norman's Principles Report} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/PerformanceReport} {Performance Report} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/UsabilityTesting} {Usability Report} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/UserInstructionalVideo} {User Instructional Video}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/UserManual} {User Manual} --- see \href{https://gitlab.cas.mcmaster.ca/smiths/cas741/-/blob/master/ReferenceMaterial/UserManualPresentation.pdf?ref_type=heads} {slides} 
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/Wireframe} {Wireframe Report}
+  \item \href{https://github.com/smiths/capTemplate/tree/main/docs/Extras/Other} {Other}
+\end{itemize}
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \begin{frame}
 \frametitle{Unit VnV Plan}
 \begin{itemize}
@@ -320,8 +414,8 @@ instructor, supervisor, users
 \item
   \href{https://gitlab.cas.mcmaster.ca/courses/capstone/-/tree/main/SamplesOfStudentWork/VnVReport}
   {Capstone Sample reports}
-\item \href{https://github.com/smiths/swhs/tree/master/docs/VnVReport} 
-{Solar Water Heating System}
+\item \href{https://github.com/smiths/swhs/blob/master/docs/VnVReport/PCM_VVReport.pdf} 
+{Solar Water Heating System (PCM)}
 \item
   \href{https://github.com/smiths/capTemplate}
   {Follow given template}
@@ -343,8 +437,8 @@ instructor, supervisor, users
 \item Avoidance of hard-coded constants (other than maybe 0 and 1)
 \item Appropriate modularization
 \bi
-\item Generally follow module guide
-\item Show explicit traceability between MG modules and code files
+\item Follow module guide
+\item Show traceability between MG modules and code files
 \ei
 \item Consistent indentation
 \item Explicit identification of coding standards (see next slide)
@@ -369,14 +463,18 @@ instructor, supervisor, users
 \item \href{https://google.github.io/styleguide/cppguide.html}{C++}
 \item \href{https://google.github.io/styleguide/javaguide.html}{Java}
 \ei
-\item
-  \href{https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Coding_Style}{Mozilla
-    Developer Network}
-\item \href{http://homepages.inf.ed.ac.uk/dts/pm/Papers/nasa-c-style.pdf}{NASA C
+\item \href{https://ntrs.nasa.gov/citations/19950022400}{NASA C
     Style Guide}
 \ei
 %\item Your decisions on style may evolve over the project
 \item Important to be consistent
+\item Every code file should have a header with
+\begin{itemize}
+  \item Author(s)
+  \item Date
+  \item Purpose
+\end{itemize}
+
 \ei
 
 \end{frame}
@@ -400,6 +498,18 @@ instructor, supervisor, users
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
+\begin{frame}
+\frametitle{Final Grading Scheme}
+
+\bi
+\item Available on Avenue
+\item 60 possible grades, but out of 50
+\ei
+
+\end{frame}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
 \begin{frame}
 \frametitle{No License?}
 
@@ -620,7 +730,7 @@ instructor, supervisor, users
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 \begin{frame}
-\frametitle{Assurance Cases in Scientific Computing \cite{SmithEtAl2020,SmithEtAl2018_ICSEPoster}}
+\frametitle{Assurance Cases in Scientific Computing \cite{SmithEtAl2018_ICSEPoster,SmithEtAl2020}}
 
 \bi
 \item Assurance cases

Lectures/L20_ArtifactGen/ArtifactGen.tex

@@ -76,13 +76,13 @@
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
-\begin{frame}
-\frametitle{Course Evaluations}
-\begin{itemize}
-\item Course experience surveys will close on Wednesday, April 12, 2023 11:59 PM
-\item \url{https://mcmaster.bluera.com/mcmaster/}
-\end{itemize}
-\end{frame}
+% \begin{frame}
+% \frametitle{Course Evaluations}
+% \begin{itemize}
+% \item Course experience surveys will close on Wednesday, April 12, 2023 11:59 PM
+% \item \url{https://mcmaster.bluera.com/mcmaster/}
+% \end{itemize}
+% \end{frame}
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%