How yarnisar54321/isad_project works
Step 1: Identify the Project Type and Purpose
• “ManageProductList” is a NetBeans-based Java Swing desktop application (an “ASMS” per README) whose primary goal is to let users log in, view and modify a product list, and save changes to local files.
Step 2: Analyze the File Structure
• src/javaapplication21
• Main.java – application entry point, wires up UI & controller
• ManageProductListBoundary.java – main Swing window presenting the product list and action buttons
• Login.java – authentication dialog
• ControlStock.java – business logic (CRUD operations plus file I/O)
• RoundedButton.java – custom JButton subclass for styled controls
• product_list.txt & product_data.dat – flat‐file data stores
• nbproject/, build.xml, out/, build/ – NetBeans project metadata and build outputs
Step 3: Inspect README for Additional Clues
• README simply labels the project “ASMS” (Academic Software Management System). No further architectural guidance is provided, so we infer a single-tier desktop MVC style.
Step 4: Define Main Components and Their Roles
a. Presentation Layer (UI)
– ManageProductListBoundary (main window)
– Login (security gate)
– RoundedButton (UI widget extension)
b. Controller / Business Logic
– ControlStock (handles add/edit/delete/search, encapsulates file I/O)
c. Application Bootstrap
– Main (instantiates ControlStock and UI, injects dependencies)
d. Data Persistence
– product_list.txt & product_data.dat (local flat-file storage)
Create three horizontal tiers
• Top (UI) – blue rectangles
• Middle (Business Logic) – green rectangle
Components
– Blue Rectangle: ManageProductListBoundary
– Blue Rectangle: Login
– Blue Rectangle: RoundedButton
– Green Rectangle: ControlStock
– Light-blue Rectangle: Main (entry point)