How neykandre/kpo-2025 works
Overall Repository Structure
– The root-level configuration/build scripts (build.gradle.kts, gradle/ wrapper files, etc.) which are common for managing builds.
– The “practice” directory that contains three independent projects: practise-1, practise-2, and practise-3.
Diagramming Each Practise Project
For each practise project, you want to capture its layered architecture. Although all three follow a similar domain (cars, engines, customers) theme, they evolve in complexity:
► Practise-1:
– Components:
• Application Entry (e.g., Main.java located in the “studying” package).
• Domain Classes (Car, Customer, Engine, FactoryAF, etc.).
– Interaction: The Main class orchestrates the creation and use of domain objects. The design is simple, focusing on basic instantiation and interaction among these objects.
► Practise-2:
– New Layers Introduced:
• Domain Layer: Now organized with subpackages like “domains” (Car, Customer, HandEngine, PedalEngine).
• Factory Layer: Separate packages for “factories” (HandCarFactory, PedalCarFactory) and “interfaces” (ICarFactory, IEngine, etc.) that illustrate the use of abstraction.
• Service Layer: Classes such as CarService, CustomerStorage, HseCarService encapsulate business logic.
• Parameter Classes: “params” package for engine configurations.
– Interaction: The Main class initiates processes that flow into the service layer, which in turn calls upon factory methods and interacts with domain objects.
► Practise-3:
– Added Complexity:
• Similar layered structure as practise-2 but includes configuration files (in the “config” directory) and resource management (under src/main/resources).
• Testing Support: A dedicated test directory with tests for the main application.
• Likely evolution towards a more production-like setup (e.g., the presence of an application.properties file and checkstyle configuration).
– Interaction: Beyond the standard layers (entry, domain, service, factory, params), indicate that configuration settings and tests play a role in the application’s behavior and quality assurance.