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

Updates for VnV presentation class

parent 634b7b19
No related branches found
No related tags found
No related merge requests found
No preview for this file type
......@@ -81,8 +81,8 @@
\ei
\item Issues are due 2 days after being assigned
\ei
\item Reading week next week, no 741 classes
\item Work on your VnV plan during reading week
\item Go ahead and address the colleague created issues
\item Reading week next week, no 741 classes, work on VnV
\ei
\end{frame}
......
No preview for this file type
......@@ -157,7 +157,7 @@ Final Documentation & Dec 9\\
\ei
\item Proof of Concept Demonstrations (15 min)
\bi
\item Mon, Oct 26: Tiago, Mohamed, Xuanming, Parsa, Gaby
\item Mon, Oct 26: Mohamed, Xuanming, Parsa, Gaby
\item Mon, Nov 2: Sid, Shayan, Leila, Xingzhi, Liz
\item Thurs, Nov 12: Salah, John
\ei
......@@ -418,7 +418,8 @@ validity
\item Testing techniques simulate the dynamic environment
\item Includes syntax checking
\item Generally static testing is used in the requirements and design stage, where there is no code to execute
\item Document and code walkthroughs
\item Document and code walkthroughs (including
\href{https://en.wikipedia.org/wiki/Rubber_duck_debugging} {rubber duck debugging})
\item Document and code inspections
\end{itemize}
\end{itemize}
......
No preview for this file type
......@@ -51,20 +51,16 @@
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Administrative Details: Report Deadlines}
~\newline
\begin{tabular}{l l l}
System VnV Plan & Week 08 & Oct 28\\
MG + MIS & Week 10 & Nov 25\\
Final Documentation & Week 14 & Dec 9\\
\end {tabular}
\frametitle{Administrative Details}
\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
\item Colleague created SRS issues
\bi
\item Feedback will be given for ``teachable moments'' and ``mistakes''
\item Self-assign the issues created by your colleagues
\item Include the relevant commit hash when closing the issue
\item You should make the revisions sooner than later
\ei
\ei
\end{frame}
......@@ -72,21 +68,23 @@ Final Documentation & Week 14 & Dec 9\\
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Administrative Details: Presentations}
\frametitle{Administrative Details: Report Deadlines}
~\newline
\begin{tabular}{l l l}
Syst.\ VnV Present & Week 07 & Week of Oct 21\\
MG + MIS Syntax Present & Week 9 & Week of Nov 4\\
MIS Semantics Present & Week 11 & Week of Nov 18\\
Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
\begin{tabular}{l l}
%\textbf{SRS} & Oct 8\\
\textbf{System VnV Plan} & Oct 29\\
MG + MIS (Traditional) & Nov 19\\
Drasil Code and Report (Drasil) & Nov 19\\
Final Documentation & Dec 9\\
\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)
\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 for a written deliverable, please ask
\item You should inform your primary and secondary reviewers of the extension
\item Two days after each major deliverable, your GitHub issues will be due
%\item Domain expert code due 1 week after MIS deadline
\ei
\end{frame}
......@@ -94,43 +92,86 @@ Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Administrative Details: Presentation Schedule}
\frametitle{Admin Details: Presentation Schedule}
\bi
\item Syst V\&V Plan Present
\item Syst V\&V Plan Present (15 min)
\bi
\item \textbf{ Thurs, Oct 22: Ting-Yu, Mohamed, Naveen, Liz, Salah}
\ei
\item Proof of Concept Demonstrations (15 min)
\bi
\item \textbf{Monday: Deema, Peter}
\item \textbf{Thursday: Sharon, Ao}
\item \textbf{Mon, Oct 26: Mohamed, Xuanming, Parsa, Gaby}
\item Mon, Nov 2: Sid, Shayan, Leila, Xingzhi, Liz
\item Thurs, Nov 12: Salah, John
\ei
\item MG + MIS Syntax Present
\item MG Present (10 minutes)
\bi
\item Monday: Deema, Bo
\item Thursday: Sasha
\item Thurs, Nov 12: John, Tiago, Leila, Xuanming, Andrea
\ei
\item MIS Syntax + Semantics Present
\item MIS Present
\bi
\item Monday: Zhi, Peter
\item Thursday: Sharon, Ao
\item Mon, Nov 16: Shayan, Parsa, Gaby, Sid, Xingzhi
\ei
\item Unit VnV Plan or Impl.\ Present
\item Drasil Project Present (20 min each)
\bi
\item Monday: Bo, Sasha
\item Thursday: Zhi, Peter, Ao
\item Thurs, Nov 26: Andrea, Naveen, Ting-Yu
\ei
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Assigned ``Questioners''}
\frametitle{Presentation Schedule Continued}
\be
\item Deema: Bo, Sharon
\item Peter: Ao, Sasha
\ee
\bi
\item Test or Impl.\ Present (15 min each)
\bi
\item Mon, Nov 30: John, Salah, Liz, Xingzhi, Leila
\item Thurs, Dec 3: Shayan, Naveen, Sid, Gaby, Seyed
\item Mon, Dec 7: Ting-Yu, Xuanming, Mohamed, Andrea, Tiago
\ei
\item 4 presentations each
\item If you will miss a presentation, please trade with someone else
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle{Today's Presenters}
\bi
\item Ting-Yu
\item Mohamed
\item Naveen
\item Liz
\item Salah
\ei
\bi
\item Informal presentations (15 minutes), 1 or 2 topics from
\bi
\item \textbf{Specific} functional system test cases
\item \textbf{Specific} nonfunctional system test cases, such as
\bi
\item Performance profile
\item Usability testing
\ei
\item SRS verification plan
\item Automated testing and verification tools
\bi
\item Profiling tools
\item Continuous integration
\item Code coverage
\item Linters
\ei
\ei
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
......
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