How iqbalabhipraya/tubes_oop works
Project type and purpose
• This is a small, monolithic Java application scaffolded for VS Code.
• Its purpose is to manage “travel packages” (group vs. individual) and associate them with customers.
File structure
• Top-level folders:
• .vscode – VS Code settings (editor config)
• src – Java source files
• bin – compiled .class files
• Key source classes in src:
• App.java – the entry point (main method)
• PackageManagement.java – core service/manager for package operations
• TravelPackage.java – abstract/base domain class
• GroupPackage.java & IndividualPackage.java – concrete domain subclasses
• Customer.java – domain model for a customer
README for additional insights
• No external frameworks or databases are mentioned.
• Default build: Java compiler outputs .class files to bin.
• Dependency management is VS Code’s built-in Java support (no Maven/Gradle).
a. Main components
1) User/CLI layer
– A developer or script invokes the App class via java -cp bin App
2) Presentation / Entry Point (App)
– Parses input (hard-coded or via args/console)
– Delegates to PackageManagement
3) Service Layer (PackageManagement)
– Business logic: create/read/update/delete travel packages and assign customers
4) Domain Layer
– TravelPackage (abstract)
– GroupPackage, IndividualPackage
– Customer
5) Data Storage (in-memory)
– A simple List or Map inside PackageManagement (no external DB)
6) VS Code & Build Subsystem
– .vscode settings for folder layout
– bin folder for compiled code
b. Relationships & interactions
• The User/CLI calls App.main()
• App → calls methods on PackageManagement
• PackageManagement → instantiates/manages domain objects (Customer, TravelPackage variants)
• Domain objects hold state; PackageManagement stores them in an in-memory collection
c. Architectural patterns & design principles
• Layered architecture: Presentation → Service → Domain → (Persistence)
• Polymorphism/inheritance in domain model (TravelPackage subclasses)
• Single responsibility: each class has one focused role
d. Technologies & libraries
• Java SE (no external frameworks)
• VS Code Java extension (shown in .vscode)
• Built-in Java Collections (List, Map) for in-memory storage
Essential architectural elements
• Every class as part of the domain layer
• Flow: User → App → Service → Domain → Storage
• Inheritance between TravelPackage and its subclasses
• VS Code build cycle: src → [javac] → bin