ISIS3510-Seccion-3-Grupo-32 / Documentation

0 stars 0 forks source link

Class Diagram #4

Closed JMarts32 closed 1 year ago

JMarts32 commented 1 year ago

The classes that are going to be used in the app might be defined in a diagram. This diagram is going to be an image in the wiki

JMarts32 commented 1 year ago

I propose the following diagram. This is only regarding the frontend that is going to be developed in Swift and Flutter.

Image

jfpatino01 commented 1 year ago

I would move reports to the left and move police crime reports under another class, maybe with them as inherting from a main class containing all reports. This is because the users should access all reports, possibly only the statistics, regardless of if they made it or not. Also, I think reports and police crime reports should include locations and so should hte itinerary and trip, this way the app only requests information that is useful locally as to deal with possible memory issues and also reduce amount of data loaded at a time.

JMarts32 commented 1 year ago

Corrected version Image