74 lines
5.5 KiB
TeX
74 lines
5.5 KiB
TeX
|
\section{Introduction} \label{sec:introduction}
|
||
|
|
This section will introduce the project: background, motives, aims, goals, and success criteria.
|
||
|
|
The section will end with this report structure.
|
||
|
|
|
||
|
|
\subsection{Project Background}
|
||
|
|
There are many automated tasks that being done manually.
|
||
|
|
If those tasks can be done automatically, a lot of productivity could be gained from as human doing those tasks can do tasks that only humans can.
|
||
|
|
|
||
|
|
This project aims to provide a software platform, where users with no experience in machine learning, data analysis could create machine learning models to process their data.
|
||
|
|
In this project, the platform will be scoped to image classification.
|
||
|
|
As an easy-to-use platform needs to be able to handle: image uploads, processing, and verification; model creation, management, and expansion; and image classification.
|
||
|
|
|
||
|
|
% This report will do a brief analysis of current image classification systems, followed by an overview of the design of the system, and implementation details. The report will finish with analysis of legal, ethical and societal issues, and evaluation of results, and objectives.
|
||
|
|
|
||
|
|
\subsection{Project Motivations}
|
||
|
|
|
||
|
|
Currently, there are many classification tasks that are being done manually.
|
||
|
|
Thousands of man-hours are used to classify images, this task can be automated.
|
||
|
|
There are a few easy-to-use image classification systems that require low to no knowledge of image classification.
|
||
|
|
This project aims to fill that role and provide a complete image classification service.
|
||
|
|
While still been user-friendly, where a user who has never done any kind of user classification still could get good results, by simply using this service.
|
||
|
|
|
||
|
|
\subsection{Project Aim}
|
||
|
|
The project aims to create an easy-to-use software platform, where users can create image classification models without having prior knowledge about machine learning.
|
||
|
|
The user should only need to upload the images and confirm, and the system should be able to perform all the steps necessary to create and manage the machine learning model.
|
||
|
|
|
||
|
|
\subsection{Project Objectives}
|
||
|
|
This project will have two different objectives.
|
||
|
|
Primary objectives are objectives that are required for the project to be considered a success.
|
||
|
|
Secondary objectives are objectives that are not required for the project to be considered a success, but they would provide a better experience for the user of the service.
|
||
|
|
|
||
|
|
This project's primary objectives are to design and implement:
|
||
|
|
\begin{itemize}
|
||
|
|
\item a system to upload images that will be assigned to a model
|
||
|
|
\item a system to automatically create and train models.
|
||
|
|
\item a platform where users can manage their models.
|
||
|
|
% \item a system to automatically expand and reduce models without fully retraining the models.
|
||
|
|
\item a system to automatically expand models without fully retraining the models.
|
||
|
|
\item an Application Programming Interface(API) that users can interact programmatically with the service.
|
||
|
|
\end{itemize}
|
||
|
|
|
||
|
|
This project's secondary objectives are to:
|
||
|
|
\begin{itemize}
|
||
|
|
% \item Create a system to automatically to merge modules to increase efficiency.
|
||
|
|
\item Create a system to distribute the load of training the model among multiple servers.
|
||
|
|
\end{itemize}
|
||
|
|
|
||
|
|
\subsection{Success Criteria}
|
||
|
|
As it was mentioned before, the project can be considered a success when the primary objectives have been completed.
|
||
|
|
|
||
|
|
Therefore, the success criteria of this project can be defined as:
|
||
|
|
|
||
|
|
\begin{itemize}
|
||
|
|
\item A user can upload images, train a model on those images, and evaluate images using a user interface.
|
||
|
|
\item A user can perform the same tasks, via the API service.
|
||
|
|
\end{itemize}
|
||
|
|
|
||
|
|
\subsection{Project Structure}
|
||
|
|
The report on the project shows the development and designs stages of the project. With each section addressing a part of the design and development process.
|
||
|
|
|
||
|
|
\renewcommand*{\arraystretch}{2}
|
||
|
|
\begin{longtable}{p{7cm} p{8cm}}
|
||
|
|
\hyperref[sec:introduction]{Introduction} & The introduction section will do a brief introduction of the project and its objectives. \\
|
||
|
|
\hyperref[sec:lit-tech-review]{Literature and Technical Review} & The Literature and Technical Review section will introduce some current existing projects that are similar to this one, and introduce some technologies that can be used to implement this project. \\
|
||
|
|
\hyperref[sec:sanr]{Service Analysis and Requirements} & This section will analyse the project requirements. The section will define design requirements that the service will need to implement to be able to achieve the goals that were set up. \\
|
||
|
|
\hyperref[sec:sd]{Service Design} & This section will discuss how a service could be designed that it matches the requirements of the service. \\
|
||
|
|
\hyperref[sec:sd]{Service Implementation} & Information on how the design of the system was turned into software is in this section. \\
|
||
|
|
\hyperref[sec:lsec]{Legal, Societal, Ethical, Professional Considerations} & This section will cover potential legal, societal, ethical and professional, issues that might arise from the service and how they are mitigated. \\
|
||
|
|
\hyperref[sec:se]{Service Evaluation} & In this section, the model will be tested and the results of the tests will be analysed. \\
|
||
|
|
\hyperref[sec:crpo]{Critical Review of Project Outcomes} & In this section, will compare the project goals with what was achieved. Then, according to the results, the project will either be deemed successful or not.
|
||
|
|
|
||
|
|
\end{longtable}
|
||
|
|
\pagebreak
|