Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use Case Diagram #5

Open
BrouthenKamel opened this issue Dec 1, 2023 · 2 comments
Open

Use Case Diagram #5

BrouthenKamel opened this issue Dec 1, 2023 · 2 comments
Assignees
@mmal3k

Comments

@BrouthenKamel
Copy link
Contributor

Description

Finalize the UCD by including low-abstracted level cases

Outcome

Final UCD
@BrouthenKamel BrouthenKamel self-assigned this Dec 1, 2023
@BrouthenKamel BrouthenKamel moved this to 🆕 New in ISE Project Tracking Dec 1, 2023
@BrouthenKamel BrouthenKamel moved this from 🆕 New to 🔥 Sprint Backlog in ISE Project Tracking Dec 1, 2023
@BrouthenKamel BrouthenKamel moved this from 🔥 Sprint Backlog to 🏗 In progress in ISE Project Tracking Dec 2, 2023
@BrouthenKamel
Copy link
Contributor Author

@mmal3k , @Mahdifellah Diagrams tool

@BrouthenKamel BrouthenKamel moved this from 🏗 In progress to 👀 In review in ISE Project Tracking Dec 4, 2023
@BrouthenKamel BrouthenKamel moved this from 👀 In review to 🔖 Ready in ISE Project Tracking Dec 7, 2023
@BrouthenKamel
Copy link
Contributor Author

Suggested update

Since we will account for AI extraction, there might be a need to account for a new actor Uploader

Reasoning

The pipeline of the PDF indexing:

  1. Local/Remote PDF uploading
  2. PDF AI Extraction
  3. Elastic Search Indexing

Hence, the major argument is concerning error handling, while having three layers of operations on PDFs, it will be essential to separate the processing responsibility and error detection and handling.

Why an actor and not a controller? ( Not 100% sure)
I think it can be seen as a separate service to get the PDF as text given its local/remote location

@4zz0u4k 4zz0u4k moved this from 🔖 Ready to 👀 In review in ISE Project Tracking Dec 11, 2023
@BrouthenKamel BrouthenKamel moved this from 👀 In review to 🔖 Ready in ISE Project Tracking Dec 18, 2023
@BrouthenKamel BrouthenKamel moved this from 🔖 Ready to ✅ Done in ISE Project Tracking Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmal3k mmal3k

Labels
None yet
Projects
ISE Project Tracking
Status: ✅ Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@BrouthenKamel @Mahdifellah @mmal3k