How abekek/numa-rdma-cse341 works
Main Components
a. User Interface Components:
• Property Manager Interface – handles property visits, new lease recordings (including tenant creation), and move outs.
• Tenant Interface – includes login/registration, personal data viewing/updating, lease management (for payments and tenant operations).
• NUMA Manager Interface – for property creation (with back-end PL/SQL calls to populate apartments and amenities), editing, and rent adjustments.
• Business Manager Interface – for retrieving various statistics about the overall system, apartments, and tenants.
b. Application Core/Business Logic:
• Java classes under the “alk224” package (MainMenu.java, BusMngrMenu.java, NUMAMngrMenu.java, PropMngMenu.java, TenantMenu.java) represent the core of the system logic.
• They implement the business rules and interface workflows.
c. Data Generation Component:
• The “datagen” folder contains code (DataGen.java) and scripts (run.sh, makefile) for generating random/mock data. This might be used during deployment or testing.
d. Database Interaction/Management:
• The project uses a relational database accessed via the ojdbc8.jar (the Oracle JDBC driver).
• SQL and PL/SQL scripts stored under “other/sql” and “other/plsql” handle table creation and population, as well as certain back-end procedures.
e. External Dependencies:
• The Oracle JDBC driver (ojdbc8.jar) and any encryption libraries for SHA-256 (as mentioned in the README for tenant password encryption).
Relationships and Interactions
• The UI components serve as the front end for different user roles. Each interface triggers underlying Java methods that enforce business rules.
• Between the business logic and the database, there is a well-defined interaction layer (using JDBC) to execute SQL/PLSQL operations such as tenant registration, lease creation, and property updates.
• The data generation component interacts primarily with the database via the provided scripts and might be executed separately to populate or refresh data.
• The PL/SQL scripts add an extra layer where stored procedures are invoked from the Java logic (especially in the NUMA Manager Interface when adding a new property).
Architectural Patterns
• Separation of Concerns: Splitting the project into interface modules (UI), business logic (Java classes), and data handling (database scripts and JDBC integration).
• Use of External Data Generation Tools: The datagen scripts indicate a decoupled process for managing sample/seed data.
Relevant Technologies, Frameworks, and Libraries
• Java/JAR execution (MainMenu.jar)
• Oracle JDBC driver (ojdbc8.jar)
• PL/SQL procedures and SQL scripts for database operations
• Shell scripting for compiling and running the program (run.sh, makefile)
• SHA-256 for encryption (used during tenant registration/login)
Essential Elements
• How data flows from user interaction to backend processing.
• How each module interacts with the central database.
• How the data generation module is used to seed the database.
• Optionally, include brief notation on any important design patterns (e.g., layered architecture) that are evident.