How deepika5555/selfielessactsapplication works
File structure
• Top-level files:
• cont1.py – script #1, contains business logic for “scenario 1”
• cont1_data.db – SQLite DB backing cont1.py
• cont2.py – script #2, separate flow for “scenario 2”
• cont2_data.db – SQLite DB backing cont2.py
• generic.py – shared library of common functions
• No frontend or network layers, no external services, no build scripts. This is purely a two‐module Python app with per‐module databases.
README for additional insights
• The README only gives the project name. You must rely on the file layout to infer that cont1.py and cont2.py are standalone processes, both reusing common code in generic.py and persisting data locally.
Diagramming recommendations
– Use rectangles for code components (label: “cont1.py”, “cont2.py”, “generic.py”)
• From cont1.py → generic.py (import/shared code)
• From cont2.py → generic.py
• From cont1.py → cont1_data.db (read/write)
• From cont2.py → cont2_data.db
• Shared library (generic.py) in another (e.g., green)
• Data stores (DB files) in a third (e.g., orange)
Detail
– Capture the SQLite connection as part of contX.py’s responsibilities