Skip to content

Commit

Permalink
SRS update. -Rob
Browse files Browse the repository at this point in the history
  • Loading branch information
GorrieXIV committed Oct 7, 2015
1 parent aa3eda0 commit 481e18e
Show file tree
Hide file tree
Showing 2 changed files with 13 additions and 2 deletions.
Binary file modified Documentation/Geant4-GPUSRS.pdf
Binary file not shown.
15 changes: 13 additions & 2 deletions Documentation/Geant4-GPUSRS.tex
Original file line number Diff line number Diff line change
Expand Up @@ -275,7 +275,7 @@ \subsubsection{Style Requirements}
{Created October 6, 2015}

% ----------------------------- Sub Section ----------------------------- %
\subsection{Usability and Humanity Requirements}}\label{ReqType_Usabil} % Rob
\subsection{Usability and Humanity Requirements}\label{ReqType_Usabil} % Rob

\subsubsection{Ease of Use Requirements}
\requirement
Expand Down Expand Up @@ -511,7 +511,7 @@ \subsubsection{Products That Can Be Copied}
NA\\

% ----------------------------- Sub Section ----------------------------- %
\subsection{New Problems} % Stuart
\subsection{New Problems}\label{SubSec_NewProbs} % Stuart
\subsubsection{Effects on the Current Environment}
The new product will be designed as an opt-in addition to the existing product. That is, unless manually changed by the user, the program will execute identically as before, running on the CPU. The motivation for this is to ensure compatibility, as the programming environment for GP-GPU programming is restricted to certain hardware. The current environment will not be affected by the changes unless the user specifically decides to use them.

Expand Down Expand Up @@ -556,6 +556,15 @@ \subsection{Migration to the New Product} % Victor
% ----------------------------- Sub Section ----------------------------- %
\subsection{Risks} % Rob

Because our software has research based aspirations and goals, some traditional risks are less catastrophic to the success of the project, but are still risks nonetheless. The following may pose to be potential risks:\\

\begin{itemize}
\item Excessive schedule pressure
\item Technical/Resource limitations
\item Inadequate measurements
\item Optimistic time constraints
\end{itemize}

% ----------------------------- Sub Section ----------------------------- %
\subsection{Costs} % Stuart
All software used in the project is open-source and/or available for free. Existing hardware will be used for development, so there are no associated monetary costs.\\
Expand All @@ -575,5 +584,7 @@ \subsection{Waiting Room} % Victor

% ----------------------------- Sub Section ----------------------------- %
\subsection{Ideas for Solutions} % Rob
Some solutions to a few potential problems have been breifly mentioned in the above section (see \ref{SubSec_NewProbs}). Outside of those, we can resolve usability issues with a well-written user manual, which will explain how to download the software (or for previous GEANT4 users, how to upgrade). We can also provide documentation which can distinguish if a certain user's machine is eligible for the software. \\
Additionally, in terms of organizational and production problems that may arise, we will schedule meetings with both our group and our supervisors. We can utilize well known software development procedures (such as an Agile strategy) to ease the managerial work required for development of the product to run smoothly.\\

\end{document}

0 comments on commit 481e18e

Please sign in to comment.