Source-derived document; review findings and open questions with the application owner.
Business Capability Map
In this document
Scope and interpretation
The supplied evidence supports a partial capability map for a reconstructed CardDemo mainframe estate. It describes artifacts, stated functions, and intended relationships rather than a semantically complete or operationally verified model. Evidence also conflicts on whether all identified artifacts execute together. E0001 E0010 E0017 E0018 E0020 E0021
Inference: The capability structure below separates customer-facing processing, control and decision capabilities, information management, and enabling operations because the evidence describes those concerns across CICS, batch, VSAM, DB2, IMS, MQ, JCL, and UNIX tooling. This grouping is an analytical organization, not an established architectural boundary. E0002 E0003 E0006 E0018 E0026 E0038
Customer and account management
- Account servicing: The system includes account update and account view transactions. `COACTUPC` handles CAUP, while `COACTVWC` retrieves and displays account and customer details. E0001 E0002
- Customer and card inquiry: Customer data and card cross-reference data are read from named VSAM KSDSs by `CBCUS01C` and `CBACT03C`. The complete inquiry scope and returned data are not established. E0020 E0021
- Account data extraction: `COACCT01` reads account records from `ACCTDAT`; the evidence does not establish whether this is an operational servicing capability, an extract, or both. E0022
- Customer and account maintenance: Records include customers, accounts, cards, and users, but complete layouts, ownership, relationships, and lifecycle rules remain unknown. E0004 E0009 E0021
Card, transaction, and payment processing
- Transaction capture: `COTRN02C.cbl` validates input and writes new transactions to the `TRANSACT` file. Failed validations are written to `DALYREJS`. E0007 E0008
- Account payment: The payment program uses `ACCTDAT` for lookup and balance validation and includes a confirmation journey; successful execution and posting semantics are not established. E0029
- Transaction-type management: An optional Transaction Type Management module maintains data in DB2 and VSAM. Its actual deployment and relationship to the main application remain uncertain. E0010
- Batch posting and file processing: Batch posting, transaction-file operations, and VSAM processing are described, including open, read, and close operations for `TRNXFILE`. E0024 E0031 E0038
- Interest, fees, and statements: Interest, fees, reports, and statements are identified as functions or information domains, but calculation rules, rates, timing, and production behavior are not established. E0002 E0003 E0041 E0042
Authorization, fraud, and decision management
- Transaction authorization: The evidence identifies authorization, approval, decline, acceptance, rejection, and limit-related rules. Complete decision logic, ownership, and return-code semantics are unknown. E0015 E0017 E0018 E0027
- Fraud handling: Fraud records and classifications are present, including an observed insert-versus-duplicate-key-update decision. Fraud criteria and the full processing flow are unknown. E0003 E0010
- Validation and rejection handling: Validation appears to precede processing, with rejected transaction input written to `DALYREJS`. Inference: This suggests a separation between accepted processing and rejection handling, but does not establish transactional boundaries or complete validation coverage. E0008 E0010 E0022
- Referential and duplicate control: Foreign-key restriction, duplicate handling, expiry, balance, and limit rules are described. Their implementation coverage and consistency across stores are unresolved. E0011 E0013 E0017
Access and security management
- User authentication and routing: `CC00` invokes `COSGN00C`; validated `ADMIN` credentials route to `COADM01C`, while validated non-`ADMIN` credentials route to `COMEN01C`. E0034 E0038
- User security administration: CardDemo manages `USRSEC`; add, update, and delete flows write, rewrite, or delete security records. E0016 E0017
- Authorization enforcement: RACF, `USRSEC`, and `DUSRSECJ` are identified as security-related artifacts. Enforcement, permissions, encryption, masking, auditing, and network boundaries are unknown. E0016 E0032 E0033 E0036
Reporting and information delivery
- Operational and business reporting: Reporting procedures, reports, statements, and paging are identified. `TRANREPT.prc` invokes `REPROC.prc`, but report definitions, consumers, schedules, and completeness are not established. E0025 E0042
- Data exchange and integration: Interfaces include CICS, BMS, commareas, VSAM, MQ, IMS, DB2, TDQs, FTP, sorting, and reporting tools. Contracts, transformations, keys, queues, and runtime compatibility remain unresolved. E0001 E0003 E0007 E0035 E0039 E0046
Platform and operational enablement
- Online transaction delivery: CICS programs, BMS maps, `XCTL` routing, and a CICS-region deployment context are identified; deployment and end-to-end runtime behavior are unverified. E0018 E0026 E0034 E0038
- Batch scheduling and execution: JCL invokes compilation, DB2-oriented builds, BMS processing, unloads, deletion programs, and batch jobs; Control-M and internal-reader submission are also identified. E0005 E0006 E0026 E0027 E0044
- Data administration and migration: Capabilities include VSAM loading and indexing, `REPRO`, imports or exports, migration, backups, GDGs, and date conversion through the CEEDAYS API. E0035 E0041 E0043 E0046
- Resilience and control: Waits, reruns, logging, rollback, abends, SQL handling, and error states are described. Monitoring, alerting, restart, disaster recovery, atomicity, and completion guarantees are unknown. E0015 E0031 E0039 E0045
Completeness boundary
Unknown: The supplied evidence does not establish a complete capability hierarchy, capability ownership, business outcomes, service levels, dependency sequencing, production status, or the boundaries between online, batch, optional, and reconstructed components. E0009 E0014 E0018 E0020 E0021 E0036 E0039
Harten analysis of AWS Samples CardDemo, a public demonstration application. The retained source content matches AWS revision 59cc6c2fd7ebd7ef7925cad552a01a4b8b6e4d5e. The documents describe source analysis and a proposed modernisation plan, not an implemented migration. No AWS endorsement is implied.
Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved. Apache 2.0 source licence · Amazon notice. Read the case study and source measurement.