How gims-inc/dummy_banking_sys works
Main Components
• Core Banking System (Engine): Represented by your current C code (sys.c) that handles essential banking operations and file interactions.
• API Layer (Planned): A component that will later expose banking functionalities programmatically. Although not yet implemented, include it to show how it will interface with the core banking system.
• User Interfaces (Future Enhancements):
– Terminal UI: The initial UI which will use command-line interactions.
– Desktop UI: A planned graphical user interface for desktop applications.
– Web UI: An additional planned UI using web technologies.
• Data Handling/Storage: Even though simple file handling is in place, include a component for data storage representing how file handling is used to persist banking data.
Architectural Patterns and Design Principles
• Separation of Concerns: Clearly distinguish between the UI components, the API layer, business logic (Core Banking Engine), and the data persistence mechanisms.
• Modularity: Highlight that the system is being developed in branches where each branch will tackle a specific programming aspect (e.g., one branch for file handling improvements, another for dynamic linking).
Technologies and Frameworks
– Standard C libraries for file handling and terminal operations.
– Possible GUI frameworks for the desktop UI.
– Web frameworks/servers (or interfacing with them) for the eventual web UI.
• Mention any build tools or compilation techniques, if applicable, especially when you retain multiple branches focusing on different C concepts (like dynamic linking).