Merge branch 'main' into studipsync

This commit is contained in:
Michael Chen 2022-05-10 21:45:42 +02:00
commit a7e092013a
No known key found for this signature in database
GPG Key ID: 1CBC7AA5671437BB
10 changed files with 506 additions and 0 deletions

View File

@ -0,0 +1,308 @@
Solution_Phase*_*.pdf
Solution_Phase*_*.zip
SpecialSession*_*.pdf
SpecialSession*_*.zip
*.result.txt
output.txt
## Core latex/pdflatex auxiliary files:
*.aux
*.lof
*.log
*.lot
*.fls
*.out
*.toc
*.fmt
*.fot
*.cb
*.cb2
.*.lb
## Intermediate documents:
*.dvi
*.xdv
*-converted-to.*
# these rules might exclude image files for figures etc.
# *.ps
# *.eps
# *.pdf
## Generated if empty string is given at "Please type another file name for output:"
.pdf
## Bibliography auxiliary files (bibtex/biblatex/biber):
*.bbl
*.bcf
*.blg
*-blx.aux
*-blx.bib
*.run.xml
## Build tool auxiliary files:
*.fdb_latexmk
*.synctex
*.synctex(busy)
*.synctex.gz
*.synctex.gz(busy)
*.pdfsync
## Build tool directories for auxiliary files
# latexrun
latex.out/
## Auxiliary and intermediate files from other packages:
# algorithms
*.alg
*.loa
# achemso
acs-*.bib
# amsthm
*.thm
# beamer
*.nav
*.pre
*.snm
*.vrb
# changes
*.soc
# comment
*.cut
# cprotect
*.cpt
# elsarticle (documentclass of Elsevier journals)
*.spl
# endnotes
*.ent
# fixme
*.lox
# feynmf/feynmp
*.mf
*.mp
*.t[1-9]
*.t[1-9][0-9]
*.tfm
#(r)(e)ledmac/(r)(e)ledpar
*.end
*.?end
*.[1-9]
*.[1-9][0-9]
*.[1-9][0-9][0-9]
*.[1-9]R
*.[1-9][0-9]R
*.[1-9][0-9][0-9]R
*.eledsec[1-9]
*.eledsec[1-9]R
*.eledsec[1-9][0-9]
*.eledsec[1-9][0-9]R
*.eledsec[1-9][0-9][0-9]
*.eledsec[1-9][0-9][0-9]R
# glossaries
*.acn
*.acr
*.glg
*.glo
*.gls
*.glsdefs
*.lzo
*.lzs
*.slg
*.slo
*.sls
# uncomment this for glossaries-extra (will ignore makeindex's style files!)
# *.ist
# gnuplot
*.gnuplot
*.table
# gnuplottex
*-gnuplottex-*
# gregoriotex
*.gaux
*.glog
*.gtex
# htlatex
*.4ct
*.4tc
*.idv
*.lg
*.trc
*.xref
# hyperref
*.brf
# knitr
*-concordance.tex
# TODO Uncomment the next line if you use knitr and want to ignore its generated tikz files
# *.tikz
*-tikzDictionary
# listings
*.lol
# luatexja-ruby
*.ltjruby
# makeidx
*.idx
*.ilg
*.ind
# minitoc
*.maf
*.mlf
*.mlt
*.mtc[0-9]*
*.slf[0-9]*
*.slt[0-9]*
*.stc[0-9]*
# minted
_minted*
*.pyg
# morewrites
*.mw
# newpax
*.newpax
# nomencl
*.nlg
*.nlo
*.nls
# pax
*.pax
# pdfpcnotes
*.pdfpc
# sagetex
*.sagetex.sage
*.sagetex.py
*.sagetex.scmd
# scrwfile
*.wrt
# svg
svg-inkscape/
# sympy
*.sout
*.sympy
sympy-plots-for-*.tex/
# pdfcomment
*.upa
*.upb
# pythontex
*.pytxcode
pythontex-files-*/
# tcolorbox
*.listing
# thmtools
*.loe
# TikZ & PGF
*.dpth
*.md5
*.auxlock
# titletoc
*.ptc
# todonotes
*.tdo
# vhistory
*.hst
*.ver
# easy-todo
*.lod
# xcolor
*.xcp
# xmpincl
*.xmpi
# xindy
*.xdy
# xypic precompiled matrices and outlines
*.xyc
*.xyd
# endfloat
*.ttt
*.fff
# Latexian
TSWLatexianTemp*
## Editors:
# WinEdt
*.bak
*.sav
# Texpad
.texpadtmp
# LyX
*.lyx~
# Kile
*.backup
# gummi
.*.swp
# KBibTeX
*~[0-9]*
# TeXnicCenter
*.tps
# auto folder when using emacs and auctex
./auto/*
*.el
# expex forward references with \gathertags
*-tags.tex
# standalone packages
*.sta
# Makeindex log files
*.lpz
# xwatermark package
*.xwm
# REVTeX puts footnotes in the bibliography by default, unless the nofootinbib
# option is specified. Footnotes are the stored in a file with suffix Notes.bib.
# Uncomment the next line to have this generated file ignored.
#*Notes.bib

View File

@ -0,0 +1,21 @@
phase = 01
version = 1
name = MichaelChen
solutionname = SpecialSession$(phase)_$(name)
target = $(solutionname)_V$(version).zip
package = $(solutionname).pdf
latexmkflags =
.PHONY : all dev
all : $(target)
dev : latexmkflags = -pvc
dev : all
$(target) : $(package)
zip -FSr $(target) $(package)
%.pdf : %.tex
latexmk -jobname="$*" $(latexmkflags) -pdf $<

View File

@ -0,0 +1,159 @@
\documentclass[a4paper]{scrreprt}
\usepackage[left=4cm,bottom=3cm,top=3cm,right=4cm,nohead,nofoot]{geometry}
\usepackage{graphicx}
\usepackage{tabularx}
\usepackage{listings}
\usepackage{enumitem}
\usepackage{subcaption}
\usepackage{amsmath}
\usepackage{float}
\usepackage{fancyvrb} % for "\Verb" macro
\usepackage{hyperref}
\usepackage{csquotes}
\usepackage[acronym]{glossaries}
\usepackage{pgf}
\usepackage{tikz}
\usetikzlibrary{arrows,automata}
\newacronym{svm}{SVM}{support-vector machine}
\newacronym{nb}{NB}{naive Bayes}
\newacronym{roc}{ROC}{receiver operating characteristic}
\usepackage{xparse}
\usepackage{multirow}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\setlength{\textfloatsep}{16pt}
\renewcommand{\labelenumi}{\alph{enumi})}
\renewcommand{\labelenumii}{\arabic{enumii}) }
\newcommand{\baseinfo}[5]{
\begin{center}
\begin{tabular}{p{15cm}r}
\vspace{-4.5pt}{ \Large \bfseries #1} & \multirow{2}{*}{} \\[0.4cm]
#2 & \\[0.5cm]
\end{tabular}
\end{center}
\vspace{-18pt}\hrule\vspace{6pt}
\begin{tabular}{ll}
\textbf{Name:} & #4\\
\textbf{Group:} & #5\\
\end{tabular}
\vspace{4pt}\hrule\vspace{2pt}
\footnotesize \textbf{Software Testing} \hfil - \hfil Summer 2022 \hfil - \hfil #3 \hfil - \hfil Sibylle Schupp / Sascha Lehmann \hfil \\
}
\newcounter{question}
\NewDocumentEnvironment{question}{m o}{%
\addtocounter{question}{1}%
\paragraph{\textcolor{red}{Task~\arabic{question}} - #1\hfill\IfNoValueTF{#2}{}{[#2 P]}}
\leavevmode\\%
}{%
\vskip 1em%
}
\NewDocumentEnvironment{answer}{}{%
\vspace{6pt}
\leavevmode\\
\textit{Answer:}\\[-0.25cm]
{\color{red}\rule{\textwidth}{0.4mm}}
}{%
\leavevmode\\
{\color{red}\rule{\textwidth}{0.4mm}}
}
\newcommand{\projectinfo}[5]{
\baseinfo{Special Session #1 - Submission Sheet}{#2}{#3}{#4}{#5}
}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\def\name{Michael Chen}
\def\group{Group 01 (fastjson)}
\begin{document}
\projectinfo{1}{Software Testing - Introduction Write-Up\small}{\today}{\name}{\group}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%%% Task 1 %%%
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{question}{Analysis Task (for the given introduction text)}[0]
\begin{enumerate}[topsep=0pt, leftmargin=*]
\item Read the provided \textit{Introduction} carefully.
\item Summarize the main contributions of the paper as depicted in / conceived from the \textit{Introduction}.
\begin{answer}
\begin{enumerate}
\item Introduction 1:
Email spam and malware is a major problem, therefore the study compares the performance of three different supervised machine learning based spam classification algorithms. The main contribution of this paper is the review of the the performance of those algorithms using six different performance metrics. This paper identified \gls{svm} models as the most reliable means of email filtering.
\item Introduction 2:
This paper introduces a sorting algorithm with a runtime and space complexity of $\mathcal{O}(n)$.
\end{enumerate}
\end{answer}
\item Come up with two title suggestions that appropriately describe the (conceived) topic of the paper.
\begin{answer}
\begin{enumerate}
\item Introduction 1:
\enquote{Comprehensive Study on Supervised Machine Learning Models for Email Spam Filtering}
\item Introduction 2:
\enquote{Linear Complexity Integer Sorting Algorithm}
\end{enumerate}
\end{answer}
\item When you are done with a) - c), ask the supervisor for the actual title and topic of the paper.
\begin{answer}
\begin{enumerate}
\item Introduction 1:
The actual title is \enquote{Analysis and result of classification algorithm on email classification}.
\item Introduction ":
The actual title is \enquote{Darksort: A New Linear Sorting Algorithm}.
\end{enumerate}
\end{answer}
\item What are the main shortcomings of the \textit{Introduction} in its given form?
\begin{answer}
\begin{enumerate}
\item Introduction 1:
The introduction of this paper is not as bad as I expected it to be, given the task question. The introduction well outlines the environment and use case of email communication and establishes the rationale of why the paper is important right now and why it should be of interest to research. The introduction also mentions prior research of several \gls{nb} models that will be compared with the new research. The methodology is also outlined (the different performance metrics that are applied). The main shortcomings that I could identify are the following:
\begin{enumerate}
\item The introduction should end with the statement that summarizes the main idea of the entire research.
\item The introduction is also missing an outline of how the paper is structured. After reading the introduction the reader is left without a guide on how to navigate the paper.
\item There should not be any full URL citations in the introduction, and generally not in the paper, rather as a citation reference in the bibliography.
\item There are multiple unexpanded acronyms of the different \gls{nb} models and the \gls{roc} curve.
\item There are some phrases that are not formal language such as \enquote{waste of time} and \enquote{such huge spam}.
\item The word email and some others is used very inconsistently. Just because other formats of the word were introduced it does not mean that you should switch between those so much.
\item Many consecutive sentences start with the same word, specifically \enquote{it} and \enquote{email}.
\item There are some spacing and formatting issues: email with wrong spacing \enquote{e-~mail}, missing Oxford commas like \enquote{NB, NBT, BN and DTNB}, bad citations \enquote{(Nilam et al.,2017~)}, the word \enquote{f~measure} should be \enquote{F-score}, and multiple occurrences of inconsistent multiple whitespace fillers.
\end{enumerate}
\item Introduction 2:
\begin{enumerate}
\item The research context is missing entirely. The introduction should mention existing sorting algorithms.
\item The importance of sorting algorithms must be highlighted, as a better complexity class for sorting algorithms could immensely help in scaling some performance critical applications.
\item There is no need to introduce \enquote{Darksort} in upper and lower case.
\item Sentences should mostly be self contained and not refer to other sentences from three sentences earlier: \enquote{It is an integer sorting algorithm}.
\item The outline of the paper structure is missing entirely.
\item The first sentence is informal and should rather refer to the author in plural form: \enquote{we propose a new sorting algorithm}.
\end{enumerate}
\end{enumerate}
\end{answer}
\item Make suggestions on how to improve the \textit{Introduction}. Which improvements would you prioritize, and why?
\begin{answer}
\begin{enumerate}
\item Introduction 1:
Obviously, the highest priortiy should be in fixing \textit{all} formatting and spacing issues. The second highest priority should be fixing the informal language and the repeating sentence starts. Finally, I would add the missing outline of the paper layout as this helps any reader understand and navigate the research paper more quickly and effectively.
\item Introduction 2:
First, I would work on actually writing an introduction into the research context. While most readers will know what a sorting algorithm is, even if very brief, an introduction should not omit this entirely. Breakthroughs in sorting complexity can have a great impact on other research in many different fields of study and this should also be highlighted. After this we should actually work on a paper structure outline and a description of the methods used in this paper to analyze the new algorithm.
\end{enumerate}
\end{answer}
\end{enumerate}
\end{question}
\end{document}

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.