How arthurdelannoyazerty/beanartist works
Main Architectural Components
a. Model Layer (fr.eseo.pdlo.projet.artiste.modele)
• Core domain objects (Forme, Coordonnees)
• Interfaces (Coloriable, Remplissable)
b. View Layer (fr.eseo.pdlo.projet.artiste.vue)
• UI components (PanneauDessin, PanneauBarreOutils, PanneauBarreEtat)
c. Controller Layer (fr.eseo.pdlo.projet.artiste.controleur)
• This in the middle
• Actions (ActionChoisirCouleur, ActionChoisirForme, etc.)
• Tools (OutilForme and its implementations)
Specific Components
Model Layer:
• Forme (abstract class)
• Coordonnees
• Interfaces (Coloriable, Remplissable)
View Layer:
• Main UI panels (PanneauDessin, PanneauBarreOutils, PanneauBarreEtat)
• VueForme hierarchy
Controller Layer:
• Actions package (ActionChoisirCouleur, ActionEffacer, etc.)
• Outils package (OutilForme, OutilLigne, etc.)
Additional Elements
• A main entry point (EtreUnArtiste class)
• Utility classes (StoreNames)
• Test components in a separate section (if needed)
Flow Indicators
Main interaction flows:
• User input → Controller
• Controller → Model updates
• Model changes → View updates
• View rendering → User display
Notes
Notes for:
• Design patterns used
• Key architectural decisions
• Important dependencies
• Event handling mechanisms
• Grouping related components together
• Using straight lines for connections
• Maintaining consistent spacing
• Adding clear labels
• Using appropriate abstraction level (not showing every method)
This system design should effectively communicate the application's architecture while highlighting the MVC pattern and the relationships between different components of this drawing application.