smyalygames/checklist-tester
1
0
Fork 0
mirror of https://github.com/smyalygames/checklist-tester.git synced 2025-05-18 14:34:12 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

feat(proposal): write the bullet points of introduction in sentences

Browse Source
This commit is contained in:
Anthony 2024-02-21 15:07:48 +00:00
parent dfc3bb645a
commit 85d4d808a4
2 changed files with 69 additions and 38 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
pub/proposal/proposal.pdf
View File

Binary file not shown.

107
pub/proposal/proposal.tex
View File

@ -40,7 +40,7 @@
\begin{document}
% Title Page and contents
\begin{titlepage}
\clearpage\maketitle
\clearpage\maketitle
\thispagestyle{empty}
\end{titlepage}
@ -49,47 +49,78 @@
\section{Context}
\subsection{Introduction}
\subsubsection*{Context}
\begin{itemize}
\item Designing Emergency Checklists is difficult
\item Procedures in checklists must be tested in simulators~\cite{nasa-design},
which usually means trained pilots test it, as the tests need
to work consistently~\cite{manifesto} (making sure it's not lengthy,
concise and gets critical procedures)
\lfcomment{Testing for what? What's the baseline? I guess you will need some kind of evidence/argument that demonstrates that with and without the checklist results are markedly different. }
\item Checklists are usually carried out in high
workload environments, especially emergency ones
\end{itemize}
%\begin{itemize}
% \item Designing Emergency Checklists is difficult
% \item Procedures in checklists must be tested in simulators~\cite{nasa-design},
% which usually means trained pilots test it, as the tests need
% to work consistently~\cite{manifesto} (making sure it's not lengthy,
% concise and gets critical procedures)
% \lfcomment{Testing for what? What's the baseline? I guess you will need some kind of evidence/argument that demonstrates that with and without the checklist results are markedly different. }
% \item Checklists are usually carried out in high
% workload environments, especially emergency ones
%\end{itemize}
Designing aviation checklists is difficult and requires time
to test them in simulators and the real world.~\cite{nasa-design}
The simulators require trained pilots to test them to make
sure that they work consistently~\cite{manifesto}, which tests
that the procedures in the checklist are concise, achieves the goal
of the critical procedure, and will not take too long to complete.
These checklists are also carried out in high workload environments,
and this workload is elevated if an emergency were to occur.
\subsubsection*{Problem}
\begin{itemize}
\item Testing procedures in checklists are often neglected~\cite{nasa-design}
\item There are some checklists that may not be fit
for certain scenarios - e.g. ditching (water landing)
checklist for US Airways Flight 1549 assumed at least one engine
was running~\cite{AWE1549}, but in this scenario, there were none
\lfcomment{What check lists and what scenarios?}
\item Some checklists may make pilots \enquote{stuck}
- not widely implemented, could be fixed with \enquote{opt out} points.
e.g. US Airways 1549, plane below 3000ft, could have skip to
later in the checklist to something like turn on APU, otherwise plane
will have limited control~\cite{AWE1549}.
\lfcomment{Yes, or might make them ignore the checklist. What criteria does that?}
\item Checklists may take too long to carry out - Swissair 111
\lfcomment{Yes. See Checklist manifesto test}
\end{itemize}
%\begin{itemize}
% \item Testing procedures in checklists are often neglected~\cite{nasa-design}
% \item There are some checklists that may not be fit
% for certain scenarios - e.g. ditching (water landing)
% checklist for US Airways Flight 1549 assumed at least one engine
% was running~\cite{AWE1549}, but in this scenario, there were none
% \lfcomment{What check lists and what scenarios?}
% \item Some checklists may make pilots \enquote{stuck}
% - not widely implemented, could be fixed with \enquote{opt out} points.
% e.g. US Airways 1549, plane below 3000ft, could have skip to
% later in the checklist to something like turn on APU, otherwise plane
% will have limited control~\cite{AWE1549}.
% \lfcomment{Yes, or might make them ignore the checklist. What criteria does that?}
% \item Checklists may take too long to carry out - Swissair 111
% \lfcomment{Yes. See Checklist manifesto test}
%\end{itemize}
Testing procedures in checklists is often neglected by designers.~\cite{nasa-design}
This is shown as there are certain checklists that are not fit for
certain scenarios. An example of this is the checklist for ditching (water landing)
which would have been applicable to use on US Airways Flight 1549. This checklist
assumed that at least one engine was running~\cite{AWE1549}, but this flight lost
both of their engines, and if this checklist was used, it could have ended in
an incident that could have resulted in people losing their lives.
If occurrences like happened more frequently, this could result in
pilots losing their trust in checklists, which could result in pilots
not using them, when they are designed to aid in situations where
they missing a critical step could be detrimental to the safety of
everyone onboard the aircraft.~\cite{manifesto}
\subsubsection*{Rationale}
\begin{itemize}
\item Test checklists in a simulated environment
to find flaws in checklist for things like
\begin{itemize}
\item Can be done in an amount of time that will not endanger aircraft
\item Provides reproducible results
\item Procedures will not endanger aircraft or crew further (Crew referring to Checklist Manifesto with the cargo door blowout)
\end{itemize}
\lfcomment{Again, explain testing against what}
\item Results in being able to see where to improve checklists
\end{itemize}
%\begin{itemize}
% \item Test checklists in a simulated environment
% to find flaws in checklist for things like
% \begin{itemize}
% \item Can be done in an amount of time that will not endanger aircraft
% \item Provides reproducible results
% \item Procedures will not endanger aircraft or crew further (Crew referring to Checklist Manifesto with the cargo door blowout)
% \end{itemize}
% \lfcomment{Again, explain testing against what}
% \item Results in being able to see where to improve checklists
%\end{itemize}
Therefore, to aid designers in testing checklists, this project
will create a tester for checklists to find flaws in checklists
by using simulators without the need of trained crew. This will
test that the procedures in the checklist can be done in a reasonable
amount of time that will not endanger the aircraft and that the procedures
will have reproducible results for the given goal of the checklist.
With this, the results can be used to show areas of improvement in
the checklist.
\lfcomment{On CL book, Ch1 is about nature of where CL work best; Ch2 explains what a CL is and isn't; Ch3 you can ignore, it talks about checklist for unknown/unexpected scenarios (advanced CL) in building; Ch4 he discussed CL with chefs; Ch5 talks about CL failures and why; \textbf{Ch6 is about Boeing's CL ``factory''}; Ch7 and 8 are about applying the CL he came up with, here you get the examples of test/baseline criteria for CL; Ch9 he explains it in his own practice (this is daunting read)!.}
\subsection{Key Background Sources}