How karanpateldev/capstone-project works
• Modules for gesture- or motion-based interactions: air_canvas_ml.py (likely handling a machine-learning-based drawing canvas) and air_piano.py (which probably interprets gestures to simulate a piano).
• Modules hinting at various input methods: eye_control.py (suggesting eye-tracking controls), keyboard.py (indicating standard keyboard inputs), and vb_control.py (which may refer to volume or virtual button controls).
• A primary app entry point: app.py, which likely integrates these modules.
• windows.py may be handling windowed UI elements, and the assets folder would provide supporting media or resources.
Main Actors and Their Goals
• User/Operator – The primary actor who interacts with the system.
• (Potentially) External Modules or Devices – In case any hardware (e.g., cameras or sensors for eye control/gesture detection) is assumed.
Use Cases Based on the Functional Modules
• “Interact with Air Canvas”: Represented by air_canvas_ml.py, this use case likely covers drawing actions, perhaps with gesture detection and ML interpretation.
• “Play Air Piano”: Latest from air_piano.py, where the user performs music actions in the air.
• “Control via Eye Tracking”: Covered by eye_control.py; the user interacts with the UI or navigates content using eye movements.
• “Keyboard Input Handling”: Provided by keyboard.py, allowing classic keyboard interactions.
• “VB/Virtual Button Control”: From vb_control.py, where the user manipulates virtual controls.
• “Window Management”: Managed by windows.py, perhaps displaying different UI windows or panels.
• “Application Orchestration”: Managed by app.py, which ties these modules together.
Relationships
• For each use case (depicted as ovals), show associations (lines) from the User to the relevant use cases. For example, the User “initiates” the Air Canvas, Air Piano, and Eye Tracking use cases.
• If a use case depends on input from another module (for example, window management might be a supporting system for the other functionalities), use the "include" or "extend" relationships as needed to indicate dependency.