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
Package Registry
Model registry
Operate
Environments
Terraform modules
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
Azam Mahdipour
cas741
Commits
2d84460b
Commit
2d84460b
authored
7 years ago
by
W. Spencer Smith
Browse files
Options
Downloads
Patches
Plain Diff
Removal of parts of L02 that were not completed during the lecture
parent
0ce385c9
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
Lectures/L02_GettingStarted/GettingStarted.pdf
+0
-0
0 additions, 0 deletions
Lectures/L02_GettingStarted/GettingStarted.pdf
Lectures/L02_GettingStarted/GettingStarted.tex
+0
-59
0 additions, 59 deletions
Lectures/L02_GettingStarted/GettingStarted.tex
with
0 additions
and
59 deletions
Lectures/L02_GettingStarted/GettingStarted.pdf
+
0
−
0
View file @
2d84460b
No preview for this file type
This diff is collapsed.
Click to expand it.
Lectures/L02_GettingStarted/GettingStarted.tex
+
0
−
59
View file @
2d84460b
...
...
@@ -358,65 +358,6 @@ First either init repo or clone (git init, git clone), then typical workflow is
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
SE For SC Literature
}
\begin
{
itemize
}
\item
CAS 741 process is document driven, adapted
from the waterfall model~
\cite
{
GhezziEtAl2003, VanVliet2000
}
\item
Many say a document driven process is not used by, nor suitable for,
scientific software.
\bi
\item
Scientific developers naturally use an agile
philosophy~
\cite
{
AckroydEtAl2008, CarverEtAl2007, EasterbrookAndJohns2009, Segal2005
}
,
\item
or an amethododical process~
\cite
{
Kelly2013
}
\item
or a knowledge acquisition driven process~
\cite
{
Kelly2015
}
.
\ei
\item
Scientists do not view rigid, process-heavy approaches,
favorably~
\cite
{
CarverEtAl2007
}
\item
Reports for each stage of development are counterproductive~
\cite
[p.~373]
{
Roache1998
}
\item
Up-front requirements are
impossible~
\cite
{
CarverEtAl2007, SegalAndMorris2008
}
\item
\structure
{
What are some arguments in favour of a rational document driven
process?
}
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
\frametitle
{
Counter Arguments
}
\begin
{
itemize
}
\item
Just because document driven is not used, does not mean it will not work
\item
Documentation provides many
benefits~
\cite
{
Parnas2010
}
:
\bi
\item
easier reuse of old designs
\item
better communication about requirements
\item
more useful design reviews
\item
easier integration of separately
written modules
\item
more effective code inspection
\item
more effective testing
\item
more efficient corrections and improvements.
\ei
\item
Actually faking a rational design process
\item
Too complex for up-front requirements sounds like an excuse
\bi
\item
Laws of physics/science slow to change
\item
Often simple design patterns
\item
Think program family, not individual member
\ei
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}
[allowframebreaks]
\frametitle
{
References
}
...
...
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