## Sheet: Template Info # Sheet: Template Info ## 1. Document Metadata | Field | Value | |--------------------|------------------------------------------| | **Document ID** | [GAP: Missing data for Sheet: Template Info] | | **Version** | [GAP: Missing data for Sheet: Template Info] | | **Effective Date** | [GAP: Missing data for Sheet: Template Info] | | **Review Date** | [GAP: Missing data for Sheet: Template Info] | | **Owner** | [GAP: Missing data for Sheet: Template Info] | | **Classification** | [GAP: Missing data for Sheet: Template Info] | ## 2. Version History | Version | Date | Author | Changes | |---------|------------|-------------|-------------------------------------------| | [GAP: Missing data for Sheet: Template Info] | [GAP: Missing data for Sheet: Template Info] | [GAP: Missing data for Sheet: Template Info] | [GAP: Missing data for Sheet: Template Info] | ## 3. Purpose [GAP: Missing data for Sheet: Template Info] ## 4. Scope [GAP: Missing data for Sheet: Template Info] ## 5. References [GAP: Missing data for Sheet: Template Info] --- **Note:** All information above is based strictly on the provided context. No external or assumed data has been included. If additional metadata or template information is required, it must be supplied in the knowledge base or source documentation. ## Sheet: Scope Filters # Sheet: Scope Filters ## 1. Introduction This section defines the functional and technical boundaries (scope filters) for the system as derived from the provided requirements, architecture, and business process documentation. Scope filters clarify which features, data, and operations are explicitly included or excluded from the system, ensuring alignment with ISO-29148 requirements for system scope definition. --- ## 2. Functional Scope Filters ### 2.1 Included Functionality The system supports the following core functions: | Functionality Area | Included Features | Source Reference | |--------------------------|---------------------------------------------------------------------------------------------------------------------|----------------------------------| | Order Management | Single order creation via REST API, order detail retrieval, order cancellation (with refund and notification) | [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495], [KB-186b33d7-f985-455b-8117-0cd019912510] | | Payment Processing | Payment for individual orders (min 100 JPY, max 1,000,000 JPY per transaction), refund processing | [KB-186b33d7-f985-455b-8117-0cd019912510], [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] | | Notification Service | Notification (email) sent per order (no batch), cancellation/confirmation emails | [KB-05a9aed3-6a71-4c74-ac19-6bfec293268b], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | | Data Retrieval | Paginated order listing, search/filter by customer, order status | [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495], [KB-16181d30-2dd3-421e-bab0-939cd85255d2] | | Order Detail Aggregation | Order detail page fetches order, payment, and notification data in parallel | [KB-16181d30-2dd3-421e-bab0-939cd85255d2] | --- ### 2.2 Excluded Functionality (Out of Scope) The following features are explicitly excluded from the current system scope: | Excluded Feature/Operation | Rationale / Limitation Description | Source Reference | |-------------------------------------------|-----------------------------------------------------------------------------------------------------|----------------------------------| | Bulk/Batch Order Creation | No capability for bulk or batch order creation (e.g., via CSV upload, drag-and-drop, or batch form) | [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] | | CSV/File-Based Import | No endpoint or UI for uploading and processing order data from files (CSV, Excel, etc.) | [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] | | Batch Payment Processing | No batch payment API; each order requires an individual payment API call | [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] | | Batch Notification Processing | No bulk notification API; notifications are sent individually per order | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-06c5403a-d177-4525-b247-1d7ae37a86b8] | | Progress Tracking for Batch Operations | No mechanism to track progress of multi-item operations as batch operations do not exist | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | | Parallel Processing of Orders/Payments | All cross-service calls (order creation, payment, notification) are executed sequentially | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-150eb89c-77b0-415b-a547-3ed0502eec24] | | Retry/Circuit Breaker for Cross-Service | No retry or circuit breaker mechanisms for failed cross-service calls | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-150eb89c-77b0-415b-a547-3ed0502eec24] | | Batch Grouping/Traceability in Schema | No batch_id, csv_source, or bulk_import_group fields in orders schema; cannot trace batch imports | [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8], [KB-02c65582-456a-4ebf-b934-b7e08bd16081] | --- ## 3. Data Scope Filters | Data Area | Included Elements | Excluded Elements / Limitations | Source Reference | |---------------------|---------------------------------------------------------------|----------------------------------------------------------|----------------------------------| | Orders | Single order records, order items, status, payment reference | No batch/group import metadata (batch_id, csv_source, etc.) | [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8], [KB-02c65582-456a-4ebf-b934-b7e08bd16081] | | Payments | One-to-one with orders, amount, status, transaction_id | No batch/group payments; amount per transaction limited to 1,000,000 JPY | [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] | | Notifications | One-to-one with orders, per-order notification history | No bulk notification records or grouping | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-06c5403a-d177-4525-b247-1d7ae37a86b8] | --- ## 4. Technical Scope Filters | Technical Area | Included Capabilities | Excluded Capabilities / Limitations | Source Reference | |-----------------------------|------------------------------------------------------|-------------------------------------------------------------|----------------------------------| | API Interface | RESTful endpoints for single order/payment/notification| No endpoints for batch import, batch payment, or batch notification | [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] | | UI | Single order creation, order detail, search/filter | No CSV import UI, no drag-and-drop, no batch creation form | [KB-16181d30-2dd3-421e-bab0-939cd85255d2], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] | | Processing Model | Synchronous, sequential cross-service calls | No parallel or asynchronous processing for order flows | [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | | Error Handling | Error logging, status reversion to PENDING on failure | No retry, no circuit breaker, no batch error handling | [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | --- ## 5. Summary Table: Scope Filters | Area | Included Scope | Excluded Scope / Limitation | Source Reference | |------------------------|--------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------|----------------------------------| | Order Creation | Single order via API/UI | No bulk/batch order creation, no CSV/file import | [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] | | Payment Processing | Per-order payment, refund | No batch payment, max 1,000,000 JPY per transaction | [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6], [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] | | Notification Service | Per-order notification | No batch/bulk notification | [KB-06c5403a-d177-4525-b247-1d7ae37a86b8], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | | Data Model | No batch/group import fields in schema | Cannot trace or group orders by batch import | [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8], [KB-02c65582-456a-4ebf-b934-b7e08bd16081] | | Processing Model | Synchronous, sequential | No parallel, asynchronous, or queued processing | [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | | Progress Tracking | N/A | No progress tracking for batch operations | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] | | Error Handling | Log and revert status to PENDING | No retry, no circuit breaker, no batch error handling | [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-150eb89c-77b0-415b-a547-3ed0502eec24] | --- ## 6. Conclusion The above scope filters strictly define the system’s supported and unsupported features, data, and technical boundaries. Any requirements for bulk/batch processing, CSV/file import, batch payment/notification, or batch progress/error tracking are out of scope and would require significant architectural changes to implement. --- **References:** [KB-146a6a29-932f-485d-96d6-6a92ee610336] [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8] [KB-02c65582-456a-4ebf-b934-b7e08bd16081] [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf] [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] [KB-06c5403a-d177-4525-b247-1d7ae37a86b8] [KB-16181d30-2dd3-421e-bab0-939cd85255d2] [KB-186b33d7-f985-455b-8117-0cd019912510] [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495] [KB-150eb89c-77b0-415b-a547-3ed0502eec24] ## Sheet: Sections # Sheet: Sections This section provides a structured overview of the system's functional and non-functional requirements, constraints, and limitations, as required by ISO-29148. The content is derived exclusively from the provided context. --- ## 1. Functional Requirements ### 1.1 Order Management - **Single Order Creation Only:** The system supports creation of one order at a time via the REST API. There is no capability for bulk or batch order creation. [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] - **No CSV/File Import:** There is no endpoint or mechanism to upload and process order data from files (CSV, Excel, etc.). [KB-146a6a29-932f-485d-96d6-6a92ee610336] - **Order Listing:** Orders can be listed with pagination using `skip` and `limit` parameters. [KB-0e0f1dd0-0f46-4d13-a092-e3cdc6fdd205] - **Order Detail Retrieval:** Single order details can be retrieved by order ID. [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495] - **Order Cancellation:** Cancelling an order triggers both a refund via the Payment Service and a cancellation notification via the Notification Service. [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495], [KB-186b33d7-f985-455b-8117-0cd019912510] ### 1.2 Payment Processing - **One Transaction at a Time:** Payment processing is strictly one transaction per API call. No batch payment API exists. [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] - **Payment Limits:** Each payment must be between 100 JPY and 1,000,000 JPY. Payments above this threshold are rejected. [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] - **No Batch Payment Grouping:** Payments cannot be grouped or aggregated for batch processing due to a 1:1 unique constraint between order and payment. [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] - **API Endpoint:** Payments are processed via `POST /api/v1/payments` with a payload containing `order_id`, `amount`, and `currency`. [KB-1718c2d8-b71b-4113-9906-a6d9765958ff], [KB-186b33d7-f985-455b-8117-0cd019912510] ### 1.3 Notification Service - **No Bulk Notification:** Notifications are sent individually per order. There is no bulk notification capability; each notification requires a separate API call. [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-06c5403a-d177-4525-b247-1d7ae37a86b8] - **Rate Limiting:** Notification API is rate-limited to 10 requests per second. For example, sending notifications for 10,000 orders requires at least 1,000 seconds (~17 minutes). [KB-06c5403a-d177-4525-b247-1d7ae37a86b8], [KB-04a84995-0820-4319-9d26-c1582821058a] ### 1.4 Cross-Service Integration - **Sequential Processing:** All cross-service calls (Order → Payment → Notification) are executed sequentially. There is no parallel or asynchronous processing. [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf] - **No Retry or Circuit Breaker:** Failures in cross-service calls are logged, but there is no retry or circuit breaker mechanism. [KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-150eb89c-77b0-415b-a547-3ed0502eec24] --- ## 2. Data and Schema Constraints - **No Batch Tracking Columns:** The `orders` table does not include `batch_id`, `csv_source`, or `bulk_import_group` columns. There is no mechanism to track which orders belong to a batch import. [KB-0f930ddc-1f3a-4014-a015-49fe180f8d8] - **Payment Table Constraints:** The `payments` table enforces a 1:1 unique constraint with `order_id`, preventing batch grouping. [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] - **Order Amount Constraints:** Each order/payment must be within the defined minimum and maximum limits (100 JPY to 1,000,000 JPY). [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] --- ## 3. System Limitations | ID | Limitation | Impact Area | Severity | |---------|------------------------------------------------------------------------------------------------------|----------------------|------------| | LIM-001 | Order creation is single-entry only. No bulk or batch order creation capability exists. | Order Service | High | | LIM-002 | No CSV/file-based order import functionality. | Order Service | High | | LIM-003 | Payment processing handles one transaction at a time. No batch payment API exists. | Payment Service | High | | LIM-004 | Notifications are sent individually per order. No bulk notification capability exists. | Notification Service | Medium | | LIM-005 | Cross-service calls are sequential. No parallel processing of payment and notification. | All Services | Medium | | LIM-006 | No progress tracking for batch operations. No mechanism to track progress of multi-item operations. | All Services | Medium | [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] --- ## 4. Performance and Scalability Constraints - **Bulk Operations Not Supported:** Processing 10,000 orders requires 10,000 individual API calls, resulting in extremely slow throughput for large order volumes. [KB-150eb89c-77b0-415b-a547-3ed0502eec24] - **Sequential Service Calls:** Service invocation latency is the sum of save, payment, and notification times due to lack of parallelism. [KB-150eb89c-77b0-415b-a547-3ed0502eec24] --- ## 5. User Interface Constraints - **No Bulk Import UI:** The frontend does not provide any CSV upload, drag-and-drop, or batch creation form for orders. [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-16181d30-2dd3-421e-bab0-939cd85255d2] - **Bulk Import Banner:** The order management UI displays an amber warning indicating CSV import is not available, and the CSV Import button is disabled with the label “CSVインポート（未実装）” (“CSV Import (Not Implemented)”). [KB-16181d30-2dd3-421e-bab0-939cd85255d2] --- ## 6. Error Handling - **No Batch Error Handling:** If one item in a batch fails, there is no mechanism to continue processing the remainder or to provide a summary of failed items, as batch operations are not supported. [KB-04a84995-0820-4319-9d26-c1582821058a] --- ## 7. Summary Table of Key Constraints | Area | Constraint/Requirement | Reference | |-----------------------|---------------------------------------------------------------------------------------------------------|-------------------------------------------------------| | Order Creation | Single-entry only, no bulk or batch capability | [KB-146a6a29-932f-485d-96d6-6a92ee610336] | | File Import | No CSV/file-based order import functionality | [KB-146a6a29-932f-485d-96d6-6a92ee610336] | | Payment Processing | One transaction per API call, no batch payment, 100–1,000,000 JPY per transaction | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] | | Notification Service | No bulk notification, 10/sec rate limit | [KB-06c5403a-d177-4525-b247-1d7ae37a86b8] | | Cross-Service Calls | Sequential only, no retry/circuit breaker, no parallelism | [KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf] | | Data Model | No batch tracking columns in orders table, 1:1 order-payment constraint | [KB-0f930ddc-1f3a-4014-a015-49fe180f8d8], [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] | | UI | No bulk import UI, CSV import button disabled, warning banner shown | [KB-16181d30-2dd3-421e-bab0-939cd85255d2] | --- **End of Sheet: Sections**