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
fb8f55f1
Commit
fb8f55f1
authored
4 years ago
by
W. Spencer Smith
Browse files
Options
Downloads
Patches
Plain Diff
Revision to L05 - more details on presentations and SRS
parent
48c8521d
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/L05_ProgramFamilies/ProgramFamilies.pdf
+0
-0
0 additions, 0 deletions
Lectures/L05_ProgramFamilies/ProgramFamilies.pdf
Lectures/L05_ProgramFamilies/ProgramFamilies.tex
+142
-57
142 additions, 57 deletions
Lectures/L05_ProgramFamilies/ProgramFamilies.tex
with
142 additions
and
57 deletions
Lectures/L05_ProgramFamilies/ProgramFamilies.pdf
+
0
−
0
View file @
fb8f55f1
No preview for this file type
This diff is collapsed.
Click to expand it.
Lectures/L05_ProgramFamilies/ProgramFamilies.tex
+
142
−
57
View file @
fb8f55f1
...
...
@@ -83,24 +83,53 @@
\bi
%\item Problem statement should be clear on input and output
\item
Presentations
\bi
\item
VGA by default, ask if need adapter
\item
Can use my laptop, but track pad is difficult to use
\ei
%
\item Presentations
%
\bi
%
\item VGA by default, ask if need adapter
%
\item Can use my laptop, but track pad is difficult to use
%
\ei
% \item Do NOT reproduce all of the cas 741 repo in your repo, just the blank
% project template (moved to the top level)
%\item Use the same names as the original
%\item Delete example text from templates
\item
\href
{
https://gitlab.cas.mcmaster.ca/smiths/cas741/blob/master/Repos.xlsx
}{
Repos.xlsx
}
\item
Domain experts - volunteers?
\item
80 columns in tex files
\item
\href
{
https://gitlab.cas.mcmaster.ca/smiths/cas741/-/blob/master/BlankProjectTemplate/docs/ProblemStatement/ProbState-Checklist.pdf
}
{
Checklist for Problem Statement
}
\item
\href
{
https://gitlab.cas.mcmaster.ca/smiths/cas741/blob/master/Repos.xlsx
}
{
Repos.xlsx
}
\item
Primary reviewers (``Domain experts'') and secondary reviewers
\bi
\item
Ask at least one question after presentation
\item
By two days after each major deliverable, create at least 5 GitHub issues
\ei
%\item 80 columns in tex files
%\item Spell check
%\item Replace ``in order to'' by ``to''
%\item Use a \texttt{.gitignore} file
%\item Include the commit hash that closes the issue
%\item Close issues assigned to you
\item
CA template now updated
%\item CA template now updated
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Administrative Details: Presentations
}
\bi
\item
Presentations are about 20 minutes
\item
Informal
\item
To help you prepare your written document
\item
Questions from audience
\item
Grading out of 3
\bi
\item
Generate discussion, evidence of prior thought, organized 3/3
\item
Any element missing from above 2/3
\item
Any two elements missing from above 1/3
\item
No presentation 0/3
\ei
\ei
\end{frame}
...
...
@@ -111,10 +140,10 @@
\frametitle
{
Administrative Details: Report Deadlines
}
~
\newline
\begin{tabular}
{
l l l
}
\textbf
{
SRS
}
&
Week 06
&
Oct
7
\\
System VnV Plan
&
Week 08
&
Oct 28
\\
MG + MIS
&
Week 10
&
Nov 25
\\
Final Documentation
&
Week 14
&
Dec 9
\\
\textbf
{
SRS
}
&
Week 06
&
Oct
8
\\
%
System VnV Plan & Week 08 & Oct 28\\
%
MG + MIS & Week 10 & Nov 25\\
%
Final Documentation & Week 14 & Dec 9\\
\end
{
tabular
}
\bi
...
...
@@ -122,7 +151,7 @@ Final Documentation & Week 14 & Dec 9\\
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 Domain expert code due 1 week after MIS deadline
\ei
\end{frame}
...
...
@@ -134,19 +163,20 @@ Final Documentation & Week 14 & Dec 9\\
~
\newline
\begin{tabular}
{
l l l
}
\textbf
{
SRS Present
}
&
Week 05
&
Week of Sept
30
\\
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
\\
\textbf
{
SRS Present
}
&
Week 05
&
Week of Sept
28
\\
%
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\\
\end
{
tabular
}
\bi
\item
Informal presentations with the goal of improving everyone's written
deliverables
\item
D
omain expert
s
and secondary reviewers (and others) will ask questions
\item
Primary (d
omain expert
)
and secondary reviewers (and others) will ask questions
\ei
% Andrea cannot present on Oct 22
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
...
...
@@ -155,34 +185,69 @@ Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
\frametitle
{
Administrative Details: Presentation Schedule
}
\bi
\item
SRS
(or CA)
Present
\item
SRS Present
\bi
\item
\textbf
{
Monday: Deema, Sharon, Bo
}
\item
\textbf
{
Thursday: Sasha, Colin, Zhi
}
\item
\textbf
{
Monday: Mohamed, Andrea, Tiago, John, Salah
}
\item
\textbf
{
Thursday: Liz, Xingzhi, Leila, Shayan, Naveen
}
\item
\textbf
{
Monday: Sid, Gaby, Parsa, Ting-Yu, Xuanming
}
\ei
\item
Syst V
\&
V Plan Present
\bi
\item
Monday: Deema, Peter
\item
Thursday: Sharon, Ao
\ei
\item
MG + MIS Syntax Present
\bi
\item
Monday: Deema, Bo
\item
Thursday: Colin, Sasha
\ei
\item
MIS Syntax + Semantics Present
\bi
\item
Monday: Zhi, Peter
\item
Thursday: Sharon, Ao
% \item Syst V\&V Plan Present
% \bi
% \item Monday: Deema, Peter
% \item Thursday: Sharon, Ao
% \ei
% \item MG + MIS Syntax Present
% \bi
% \item Monday: Deema, Bo
% \item Thursday: Colin, Sasha
% \ei
% \item MIS Syntax + Semantics Present
% \bi
% \item Monday: Zhi, Peter
% \item Thursday: Sharon, Ao
% \ei
% \item Unit VnV Plan or Impl.\ Present
% \bi
% \item Monday: Bo, Sasha, Colin
% \item Thursday: Zhi, Peter, Ao
% \ei
\item
Primary and secondary reviewers given in Repos.xlsx file
\ei
\item
Unit VnV Plan or Impl.
\
Present
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
SRS Presentations
}
\bi
\item
Monday: Bo, Sasha, Colin
\item
Thursday: Zhi, Peter, Ao
\item
Draft Goal statements
\item
Draft Assumptions
\item
Draft Input and output variables (data constraints)
\item
Draft General Definitions and Theoretical models
\item
Draft Instanced models
\item
Questions
\ei
\end{frame}
\ei
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Examples
}
\bi
\item
\href
{
https://github.com/best-zhang-zhi/CAS741Project
}
{
Double Pendulum
}
\item
\href
{
https://github.com/icbicket/SpectrumImageAnalysisPy
}
{
SpectrumImageAnalysisPy
}
\item
\href
{
https://github.com/PeaWagon/Kaplan
}
{
Conformer Searching using
Evolutionary Computation
}
\item
\href
{
https://github.com/Ao99/MISEG
}
{
Medical Image Segmentation
}
\item
\href
{
https://github.com/caobo1994/FourierSeries
}
{
Fourier Series
}
\item
\href
{
https://github.com/sorainsm/library-of-lighting-models
}
{
Library of
Lighting Models
}
\item
\href
{
https://github.com/slimpotatoes/STEM
_
Moire
_
GPA
}
{
Scanning
Transmission Electron Microscopy
}
\item
\href
{
https://github.com/palmerst/cas741
_
sp
}
{
Chemical Speciation
}
\ei
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
...
...
@@ -191,6 +256,9 @@ Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
\frametitle
{
Questions?
}
\begin{itemize}
\item
Questions about SRS?
\item
Any questions on the
\href
{
https://gitlab.cas.mcmaster.ca/smiths/cas741/-/blob/master/BlankProjectTemplate/docs/SRS/SRS.pdf
}
{
SRS Template?
}
\item
Any questions on the
\href
{
https://gitlab.cas.mcmaster.ca/smiths/cas741/blob/master/BlankProjectTemplate/docs/SRS/SRS-Checklist.pdf
}
{
SRS Checklist?
}
...
...
@@ -200,25 +268,42 @@ Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Kreyman and Parnas Five Variable Model
}
\begin{itemize}
\item
See
\cite
{
KreymanAndParnas2002
}
\item
An alternative approach
\item
Unfortunately the numerical algorithm is not hidden in the requirements specification
\item
The analogy with real-time systems leads to some confusion
\end{itemize}
\end{frame}
% \begin{frame}
% \frametitle{Kreyman and Parnas Five Variable Model}
% \begin{itemize}
% \item See \cite{KreymanAndParnas2002}
% \item An alternative approach
% \item Unfortunately the numerical algorithm is not hidden in the requirements specification
% \item The analogy with real-time systems leads to some confusion
% \end{itemize}
% \end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% \begin{frame}
% \frametitle{Examples}
% \begin{itemize}
% \item \href{https://github.com/smiths/swhs} {Solar Water Heating System}
% \item
% \href{https://github.com/smiths/caseStudies/tree/master/CaseStudies/glass/docs/SRS}
% {GlassBR}
% \end{itemize}
% \end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Exampl
es
}
\frametitle
{
Software Requirements Activiti
es
}
\begin{itemize}
\item
\href
{
https://github.com/smiths/swhs
}
{
Solar Water Heating System
}
\item
\href
{
https://github.com/smiths/caseStudies/tree/master/CaseStudies/glass/docs/SRS
}
{
GlassBR
}
\item
A software requirement is a description of how the system should behave,
or of a system property or attribute
\item
Requirements should be abstract, unambiguous, complete, consistent,
modifiable, verifiable and traceable
\item
Requirements should express ``What'' not ``How''
\item
Formal versus informal specification
\item
Functional versus nonfunctional requirements
\item
Software requirements specification (SRS)
\item
Requirements template
\end{itemize}
\end{frame}
...
...
@@ -242,8 +327,8 @@ Unit VnV or Impl.\ Present & Week 12/13 & Week of Nov 28\\
\frametitle
{
Specification Qualities
}
\begin{itemize}
\item
The qualities we previously discussed (usability, maintainability,
reusability, verifiability etc.)
%
\item The qualities we previously discussed (usability, maintainability,
%
reusability, verifiability etc.)
\item
Clear, unambiguous, understandable
\item
Consistent
\item
Complete
...
...
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