The codebase was delivered via OneDrive, resulting in a confusing nested structure. Here's what currently exists:
ddec/
├── .claude/ # Claude Code session data (ignore)
├── CLAUDE.md # AI assistant guidance file
├── readme.md # Project overview
├── ddec-client/ # Empty - C++ client code not yet received
├── ddec-web/
│ ├── DATABASE/ # Database files (IMPORTANT)
│ │ ├── DDEC_MTU_2025_12_26.bak # SQL Server backup with actual data (76MB)
│ │ ├── DDEC-KEYCLOAK.bak # Keycloak database backup (27MB)
│ │ ├── DDEC Table Schema.sql # SQL Server DDL scripts
│ │ ├── KEYCLOAK_Schema.sql # Keycloak schema
│ │ ├── ER Daigram Full.pdf # Entity relationship diagram
│ │ └── Screen_with_table_mapping.xlsx
│ └── OneDrive_1_1-21-2026/ # Original delivery folder (confusing name)
│ ├── DDEC-WEB/
│ │ ├── Application and jobs source code/
│ │ │ └── SourceCode/
│ │ │ ├── ddec-qre/ # QRE Framework (REQUIRED)
│ │ │ └── ddec-web/ # DDEC Web Application (REQUIRED)
│ │ ├── KeyCloak Installation guideline and authorization docs/
│ │ ├── Supporting Technical Documents/
│ │ └── Technology Stack/
│ ├── Deliverables/ # Various delivery documents
│ ├── DRS-COMM/ # Unknown - possibly communication docs
│ └── Infrastructure Architecture and Server Info/
| Folder | Purpose |
|---|---|
DATABASE/ |
SQL Server backups and schema files - contains actual data |
ddec-qre/ |
QRE 2.0 Framework - proprietary mainframe emulation layer |
ddec-web/ |
DDEC Web Application source code |
| Folder | Purpose |
|---|---|
KeyCloak Installation guideline... |
Authentication setup docs |
Supporting Technical Documents/ |
Build and deployment guides |
Technology Stack/ |
Infrastructure documentation |
| Folder | Purpose |
|---|---|
Deliverables/ |
Delivery tracking documents |
DRS-COMM/ |
Communication/correspondence |
Infrastructure Architecture... |
Server configuration docs |
Reorganize to this cleaner structure:
ddec/
├── docs/ # All documentation
│ ├── keycloak/ # Keycloak setup guides
│ ├── technical/ # Technical documents
│ └── infrastructure/ # Server/architecture docs
├── database/ # Database files
│ ├── backups/ # .bak files
│ ├── schemas/ # .sql DDL files
│ └── diagrams/ # ER diagrams
├── src/ # Source code
│ ├── ddec-qre/ # QRE Framework
│ │ ├── qre2-parent/ # 9 core modules
│ │ └── qre2-mvs-parent/ # 5 MVS modules
│ └── ddec-web/ # DDEC Web Application
├── archive/ # Non-essential files
│ ├── deliverables/
│ └── correspondence/
├── CLAUDE.md
├── readme.md
├── FOLDER_STRUCTURE.md # This file
├── APPLICATION_GUIDE.md # How the app works
└── DEPENDENCIES.md # Dependency documentation
To reorganize (run from ddec/ root):
# Create new structure
mkdir -p docs/{keycloak,technical,infrastructure}
mkdir -p database/{backups,schemas,diagrams}
mkdir -p src
mkdir -p archive/{deliverables,correspondence}
# Move database files
mv "ddec-web/DATABASE/"*.bak database/backups/
mv "ddec-web/DATABASE/"*.sql database/schemas/
mv "ddec-web/DATABASE/"*.pdf database/diagrams/
mv "ddec-web/DATABASE/"*.xlsx database/diagrams/
# Move source code
mv "ddec-web/OneDrive_1_1-21-2026/DDEC-WEB/Application and jobs source code/SourceCode/ddec-qre" src/
mv "ddec-web/OneDrive_1_1-21-2026/DDEC-WEB/Application and jobs source code/SourceCode/ddec-web" src/
# Move documentation
mv "ddec-web/OneDrive_1_1-21-2026/DDEC-WEB/KeyCloak Installation guideline and authorization docs/"* docs/keycloak/
mv "ddec-web/OneDrive_1_1-21-2026/DDEC-WEB/Supporting Technical Documents/"* docs/technical/
mv "ddec-web/OneDrive_1_1-21-2026/DDEC-WEB/Technology Stack/"* docs/infrastructure/
mv "ddec-web/OneDrive_1_1-21-2026/Infrastructure Architecture and Server Info/"* docs/infrastructure/
# Archive non-essential
mv "ddec-web/OneDrive_1_1-21-2026/Deliverables/"* archive/deliverables/
mv "ddec-web/OneDrive_1_1-21-2026/DRS-COMM/"* archive/correspondence/
# Clean up empty OneDrive folders
rm -rf "ddec-web/OneDrive_1_1-21-2026"
rm -rf "ddec-web/DATABASE"
The QRE Framework has 14 modules split across two parent POMs:
| Module | Purpose |
|---|---|
| qre2-test | Test utilities and support classes |
| qre2-core | Core framework - data types, configuration |
| qre2-core-test | Integration test support |
| qre2-data | Database access layer, JDBC utilities |
| qre2-file | File I/O for flat files, VSAM emulation |
| qre2-cobol | COBOL data type support |
| qre2-web | Web MVC framework, screen rendering |
| qre2-batch-core | Batch job framework |
| Module | Purpose |
|---|---|
| qre2-batch-korn | Korn shell script support for batch |
| qre2-ims | IMS transaction manager emulation |
| qre2-mvs-starter | Spring Boot starter for MVS apps |
| qre2-mvs-starter-ims | IMS-specific Spring Boot starter |
Modules must be built in this order:
src/ddec-qre/qre2-parent - Core QRE frameworksrc/ddec-qre/qre2-mvs-parent - MVS/IMS extensionssrc/ddec-web - DDEC application# From src/ directory
cd ddec-qre/qre2-parent && mvn clean install
cd ../qre2-mvs-parent && mvn clean install
cd ../../ddec-web && mvn clean package -Pweb