Skip to content
Snippets Groups Projects
Commit b206f197 authored by W. Spencer Smith's avatar W. Spencer Smith
Browse files

Addition of information hiding examples to lecture slides

parent 1df39696
No related branches found
No related tags found
No related merge requests found
No preview for this file type
......@@ -1205,6 +1205,53 @@ AC2 & M2\\
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Appendix: Information Hiding Examples}
\begin{itemize}
\item
\href{https://gitlab.cas.mcmaster.ca/smiths/pub/-/blob/master/HoffmanAndStrooper1995.pdf}
{Hoffman and Strooper (1995)} textbook on software development: The running
example is of a symbol table. A very complete example. There is a complete
chapter on the module guide in the text. It is well explained there.
\item
\href{https://gitlab.cas.mcmaster.ca/smiths/pub/-/blob/master/ParnasEtAl1984.pdf}
{Parnas Et Al (1984) ``The Module Structure of Complex Systems'' }: This
example is right back to the source. The example focuses on the A7E military
fighter jet.
\item
\href{https://gitlab.cas.mcmaster.ca/smiths/pub/-/blob/master/Parnas1979.pdf
}{Parnas (1979) ``Designing Software For Ease of Extension and Contraction''}
\item \href{http://www.cas.mcmaster.ca/~mohrens/maze.pdf} {von Mohrenschildt
(2005) ``The Maze Tracing Robot A Sample Specification''}: This is a small
and complete example.
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Appendix Cont'd: Information Hiding Examples}
\begin{itemize}
\item
\href{https://github.com/smiths/swhs/blob/master/docs/Design/MG/PCM_MG.pdf}
{Jegatheesan and MacLachlan (2018), Module Guide for Solar Water Heating
Systems Incorporating Phase Change Material}
\item
\href{https://github.com/XingzhiMac/CAS741-Proj/blob/master/docs/Design/MG/MG.pdf}
{Liu (2020) Module Guide for Radio Signal Strength Calculator}
\item Key points
\bi
\item One module, one secret
\item Secrets are often nouns (data structure, algorithm, hardware, etc.)
\item Secrets are sometimes phrased with ``How to …''
\item Secrets ideally will have a one to one mapping with the anticipated
changes for the software
\ei
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[allowframebreaks]
\frametitle{References}
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment