How altitude80ai/awscarddemo works
Project Type and Core Architecture
This is a Mainframe-based Credit Card Management System with both online (CICS-based) and batch processing components. The architecture should be represented as a multi-tier mainframe application system.
Main Components
a. User Interface Layer:
• BMS (Basic Mapping Support) screens
• Main entry points (CC00, CM00, CA00 transactions)
• Screens by User and Admin functions
b. Application Layer:
• COBOL Programs (divided into Online and Batch)
• Transaction Processing Components
• Security/Authentication Components
c. Data Layer:
• VSAM Files
• File Organizations (KSDS, etc.)
• Data Relationships
[Top Level]
User Access Layer
• Online Interface (CICS)
• User Functions
• Admin Functions
• Batch Interface (JCL)
[Middle Level]
Application Processing Layer
• Online Programs
• Transaction Management
• Account Management
• Card Management
• User Management
• Batch Programs
• Transaction Processing
• Interest Calculation
• Statement Generation
• Common Components
• Security Services
[Bottom Level]
Data Storage Layer
• Master Files
• Customer (CUSTDATA)
• Account (ACCTDATA)
• Card (CARDDATA)
• Transaction Files
• Daily Transactions
• History
• Reference Data
• Security
• Configuration
Key Relationships to Highlight
• Flow from CICS transactions through BMS maps to COBOL programs
• Batch job dependencies
• Demonstrate data access patterns
• Security validation flows
Additional Technical Details
• Technology annotations:
• COBOL
• CICS
• VSAM
• JCL
• RACF
• File formats (FB, VSAM KSDS)
• Record lengths where significant
Processing Flows
• User transaction flow
• Batch processing sequence
• Statement generation process
• Security validation
Integration Points
Planned future integration points:
• DB2 interface
• IMS connections
• FTP/SFTP interfaces
• Message queue integration
• Distributed application interfaces