feat: 🗃️ Backup state of CDC
This commit is contained in:
parent
cb7800d2ae
commit
d515d62c1e
GPG Key ID:
84D3DF1528A84511
BIN
OCRudoku_first_defense.pdf
(Stored with Git LFS)
BIN
OCRudoku_first_defense.pdf
(Stored with Git LFS)
Binary file not shown.
9
main.tex
9
main.tex
@ -30,13 +30,16 @@
|
||||
|
||||
\input{sections/introduction/introduction}
|
||||
|
||||
\section{Membres du projet}
|
||||
\section{Project Members}
|
||||
\input{sections/membres-projet/membres-projet}
|
||||
\newpage
|
||||
|
||||
|
||||
\section{Répartition des tâches}
|
||||
\section{Task Allocation}
|
||||
\input{sections/repartition-des-taches/repartition-des-taches}
|
||||
\newpage
|
||||
|
||||
\section{Technical Section}
|
||||
\input{sections/partie-technique/partie-technique}
|
||||
|
||||
|
||||
\end{document}
|
||||
|
||||
2
sections/partie-technique/partie-technique.tex
Normal file
2
sections/partie-technique/partie-technique.tex
Normal file
@ -0,0 +1,2 @@
|
||||
This section aims to explain each part of the project from a technical perspective. It includes the libraries used, the various applications related to the project, how the project is built, and more.
|
||||
|
||||
@ -0,0 +1 @@
|
||||
Should be completed by Lilia.
|
||||
@ -0,0 +1,14 @@
|
||||
% Please add the following required packages to your document preamble:
|
||||
% \usepackage[table,xcdraw]{xcolor}
|
||||
% Beamer presentation requires \usepackage{colortbl} instead of \usepackage[table,xcdraw]{xcolor}
|
||||
\begin{table}[H]
|
||||
\begin{tabular}{|l|l|l|}
|
||||
\hline
|
||||
\rowcolor[HTML]{9B9B9B}
|
||||
Task & Current Progress & Expected Progress \\ \hline
|
||||
Image Management & \cellcolor[HTML]{F8A102}50\% & \cellcolor[HTML]{F8A102}70\% \\ \hline
|
||||
OCR/AI & 50\% & X\% \\ \hline
|
||||
Git & \cellcolor[HTML]{32CB00}100\% & \cellcolor[HTML]{32CB00}100\% \\ \hline
|
||||
GUI & \cellcolor[HTML]{32CB00}70\% & \cellcolor[HTML]{32CB00}70\% \\ \hline
|
||||
\end{tabular}
|
||||
\end{table}
|
||||
@ -0,0 +1 @@
|
||||
Should be completed by Lilian
|
||||
@ -0,0 +1,5 @@
|
||||
Our project management relies on rigorous organization structured around agile methods and continuous monitoring, ensuring optimal coordination and the achievement of our objectives. We have chosen to implement the SAFe (Scaled Agile Framework) methodology\footnote{For more information, we encourage you to visit the official SAFe website: https://scaledagileframework.com/}, which is particularly suited for large teams and complex projects but also adaptable for smaller teams like ours working on mid-sized projects. SAFe enables us to prioritize in a structured way, foster cross-team collaboration, and quickly adapt to changes, thereby ensuring alignment between strategic goals and operational tasks. Additionally, it provides a week-by-week overview of completed tasks, those that faced challenges, and more. This approach helps us better estimate the time required for specific tasks and assign them to the most suitable team member based on their skills and availability for that week.
|
||||
|
||||
To maintain smooth communication and steady progress, we hold weekly meetings with all team members. These sessions allow everyone to share updates, identify obstacles, and align on common objectives, fostering complete transparency and collective alignment. Furthermore, each week, new goals and tasks are set, a process essential for reassessing priorities and adjusting actions based on the current project needs. This also helps break down work into manageable stages, making progress measurable and simplifying performance evaluation. These weekly meetings are typically held on Zoom. For direct communication between two team members, we use Discord, which allows us to organize discussions within themed channels.
|
||||
|
||||
Finally, to maximize responsiveness, we hold five-minute micro-meetings each day as needed. These brief check-ins allow us to quickly address any blocking issues, clarify specific questions, or coordinate immediate actions without disrupting ongoing workflows. Through this rigorous yet flexible organization, we ensure that the project progresses under optimal conditions, allowing each team member to contribute effectively within a clear and collaborative framework.
|
||||
@ -0,0 +1,7 @@
|
||||
Our project management includes a rigorous organization of our Git repository, based on the use of Git-flow and conventional commits, ensuring effective collaboration and optimal traceability of code changes.
|
||||
|
||||
The Git-flow strategy provides a clear branching structure that streamlines development and code integration, even in an environment with multiple contributors working simultaneously. With Git-flow, we maintain distinct branches for each development stage. Once a feature is completed, it is merged into the development branch via pull requests, following thorough verification and code review.
|
||||
|
||||
Additionally, we implement the conventional commit convention to name commits in a consistent and descriptive way. This standardizes commit message formatting, making them more readable and valuable for project tracking. Each message follows a specific structure, enabling quick understanding of the purpose and context of each change. This approach also facilitates the automatic generation of changelogs by easily identifying added features or bug fixes.
|
||||
|
||||
The combination of Git-flow and conventional commit creates a well-organized and readable Git environment where each contributor knows precisely where and how to integrate their changes. This setup promotes better collaboration, minimizes errors, and ensures a rigorous management of our code’s lifecycle. Thanks to this organization, we have encountered only two conflicts since the beginning of our code’s lifecycle, a remarkably low number compared to other projects.
|
||||
@ -3,46 +3,49 @@ Below is the task allocation for the first project review:
|
||||
% \usepackage[table,xcdraw]{xcolor}
|
||||
% Beamer presentation requires \usepackage{colortbl} instead of \usepackage[table,xcdraw]{xcolor}
|
||||
\begin{table}[H]
|
||||
\begin{tabular}{llll}
|
||||
Task / Member & Lilian & Luca & Louis \\
|
||||
\begin{tabular}{|l|l|l|l|}
|
||||
\hline
|
||||
Task / Member & Lilian & Luca & Louis \\ \hline
|
||||
\rowcolor[HTML]{C0C0C0}
|
||||
Image Management & & & \\
|
||||
Preprocessing & Principal & Secondary & \\
|
||||
Rotation & Secondary & & Principal \\
|
||||
Segmentation & Principal & & Secondary \\
|
||||
Image Management & & & \\ \hline
|
||||
Preprocessing & Principal & Secondary & \\ \hline
|
||||
Rotation & Secondary & & Principal \\ \hline
|
||||
Segmentation & Principal & & Secondary \\ \hline
|
||||
\rowcolor[HTML]{C0C0C0}
|
||||
OCR & & & \\
|
||||
Neural Network & Principal & & Secondary \\
|
||||
Image Bank Management & & Principal & Secondary \\
|
||||
Training Management & Secondary & Principal & \\
|
||||
OCR & & & \\ \hline
|
||||
Neural Network & Principal & & Secondary \\ \hline
|
||||
Image Bank Management & & Principal & Secondary \\ \hline
|
||||
Training Management & Secondary & Principal & \\ \hline
|
||||
\rowcolor[HTML]{C0C0C0}
|
||||
Project Management & & & \\
|
||||
Establishing Work Methods & Principal & & Secondary \\
|
||||
Task Assignment & Secondary & & Principal \\
|
||||
Project Management & & & \\ \hline
|
||||
Establishing Work Methods & Principal & & Secondary \\ \hline
|
||||
Task Assignment & Secondary & & Principal \\ \hline
|
||||
\rowcolor[HTML]{C0C0C0}
|
||||
Git & & & \\
|
||||
Repository Setup & Principal & Secondary & \\
|
||||
Access Management & & Principal & Secondary \\
|
||||
Git Security Management & & Secondary & Principal \\
|
||||
CI/CD Management & & & Principal \\
|
||||
P2P Checking & Principal & Principal & Principal \\
|
||||
Git & & & \\ \hline
|
||||
Repository Setup & Principal & Secondary & \\ \hline
|
||||
Access Management & & Principal & Secondary \\ \hline
|
||||
Git Security Management & & Secondary & Principal \\ \hline
|
||||
CI/CD Management & & & Principal \\ \hline
|
||||
P2P Checking & Principal & Principal & Principal \\ \hline
|
||||
\rowcolor[HTML]{C0C0C0}
|
||||
Other & & & \\
|
||||
Report Writing & & Secondary & Principal \\
|
||||
Solver Creation & & Principal & \\
|
||||
GUI Implementation & Secondary & Principal &
|
||||
Other & & & \\ \hline
|
||||
Report Writing & & Secondary & Principal \\ \hline
|
||||
Solver Creation & & Principal & \\ \hline
|
||||
GUI Implementation & Secondary & Principal & \\ \hline
|
||||
\end{tabular}
|
||||
\end{table}
|
||||
|
||||
\newpage
|
||||
|
||||
\subsection{Image Management}
|
||||
\input{sections/repartition-des-taches/gestion-de-l-image/gestion-de-l-image}
|
||||
|
||||
\subsection{OCR}
|
||||
\include{sections/repartition-des-taches/OCR/ocr}
|
||||
\input{sections/repartition-des-taches/OCR/ocr}
|
||||
|
||||
\subsection{Project Management}
|
||||
\include{sections/repartition-des-taches/gestion-du-projet/gestion-du-projet}
|
||||
\input{sections/repartition-des-taches/gestion-du-projet/gestion-du-projet}
|
||||
|
||||
\subsection{Git}
|
||||
\include{sections/repartition-des-taches/git/git}
|
||||
\subsection{Other}
|
||||
\include{sections/repartition-des-taches/autre/autre}
|
||||
\input{sections/repartition-des-taches/git/git}
|
||||
|
||||
\subsection{Progress Status}
|
||||
\input{sections/repartition-des-taches/etat-avancement/etat-avancement}
|
||||
Loading…
x
Reference in New Issue
Block a user