This phase requires the software definition of the top level system layout. Controllers, and Major view elements link models. API not specified. This allows all system components to be worked on independent of others, parallelism of the project begins.
\\\\
No requirements are satisfied at the end of this phase, it is the initial set up to allow for all requirements to be satisfied by the system.
\\\\
\hspace*{1cm}\textbf{Phase 2} Project demo: \\
The proof of concept for the system should be completed, this includes file reading and viewing. Mock view should be shown, not all view elements are required for this phase.
\\\\
Requirements Satisfied by this phase:
\begin{itemize}
\item 2.2.1, 2.2.2, 2.2.3, 2.2.4, 3.1.1
\end{itemize}
\textbf{Phase 3} Recompletion of old system: \\
As the old system is a base level for what is needed for the new system, all functionality of the old system should belong to the new system upon phase completion.
\textbf{Phase 4} Addition of frame injection and sprite spreadsheet exports: \\
These two tasks are to be done in parallel and mark a new revision of the software, the system may be released at this time, however there are still more features to complete. Error handling must be completed at this phase.
\textbf{Phase 5} Addition of all additional features that make the system complete: \\
Tasks such as frame injection and editing of images with overlays are to be completed in this phase. On completion the product is to be released as completed.
The developers are starting the software from scratch. The system as-is will be understood completely by the development team before the Code is started. Since there is no Code Migration directly, please refer to the project \href{run:../../ProjectSchedule/3X_Example.gan}{Gantt Chart} for more information on deadlines for implementation of the new system.
\subsubsection{Users}
Users of the current system will be able to just as easily use the new system. The new system will load any gif, and image type that the current system utilizes so there is no need to undergo any file conversions from the old to new system. The system will require no back-up on the user end as all user data is simply the images and GIFs they use.
\subsection{Risks}
\subsubsection{Developer Based}
%Risk One
Image Handling. Probability High. With game developers in mind we need to manipulate animations into sprite spreadsheets. This requires a large amount of knowledge in a field we are un-familiar with when using code to complete such a task so we can just. Thus we need to learn about this topic to complete the project goals.
\\
%Risk Two
\textbf{Time Management.}
\\ Probability High. All members of the team have a full engineering course load of 6 courses. With this in mind we have to ensure all courses are completed at a level considered subjectively good to each member. Thus time management can due to distractions from other parts of academia.
\\
%Risk Three
\textbf{File Conversion.}
\\ Probability High. The project is to take in all standard image files for GIF frame injection. Thus all image types must be converted to a standard format, before use.
\\
%Risk Four
\textbf{Frame Injection of images of a different format.}
\\ On frame injection a different sized image may be specified, these images need scaling options for the GIF or the frame to be allotted by the system. This task will be one of the most difficult issues to face, as it is a sub system of its own.
\subsubsection{User Based}
%Risk One
\textbf{Loading in files that have loadable extensions but whose data is not relevant to the system.}
\\ Probability Moderate. This risk pertains to users loading files that are not supported by the system, this issue can occur from either a file with different data having a readable extension or specifying a non-supported file type. The system must handle these inputs.
\\
%Risk Two
\textbf{File corruption.}
\\ Probability Low. Loading files whose data is corrupted, causes the user to be dis-satisfied with the system, even though this risk is not controlled by the system directly.
\subsection{Costs}
This project is being developed by a group of students for McMaster's 3XA3
course and has zero cost except for time. This is also a mandated constraint. Each group member's time has been
