## Sheet: Template Info Sheet: Template Info ==================== [GAP: Missing data for Sheet: Template Info] ## Sheet: Scope Filters # Sheet: Scope Filters ## 1. Purpose This section defines the explicit boundaries and constraints (“scope filters”) for the order management and related services, as required by ISO/IEC/IEEE 29148. Scope filters clarify what is and is not included in the system’s functional and technical scope, based strictly on current system capabilities and architectural limitations. --- ## 2. Functional Scope Filters ### 2.1 Order Creation | Limitation ID | Description | Impact Area | Severity | |---------------|----------------------------------------------------------------------------------------------------------|-----------------|----------| | LIM-001 | Order creation is single-entry only. No bulk or batch order creation capability exists. Orders can only be created one at a time via the REST API. | Order Service | High | | LIM-002 | No CSV/file-based order import functionality. There is no endpoint or mechanism to upload and process order data from files (CSV, Excel, etc.). | Order Service | High | **References:** [KB-146a6a29-932f-485d-96d6-6a92ee610336] [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] --- ### 2.2 Payment Processing | Limitation ID | Description | Impact Area | Severity | |---------------|-------------------------------------------------------------------------------------------------------------|--------------------|----------| | LIM-003 | Payment processing handles one transaction at a time. No batch payment API exists. Each order requires an individual payment API call. | Payment Service | High | | DD-PAY-LIM-003| Maximum amount per transaction is 1,000,000 JPY. This limit applies to each individual order. High-value orders are rejected. | Payment Service | Medium | **References:** [KB-146a6a29-932f-485d-96d6-6a92ee610336] [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] [KB-186b33d7-f985-455b-8117-0cd019912510] --- ### 2.3 Notification Processing | Limitation ID | Description | Impact Area | Severity | |---------------|-------------------------------------------------------------------------------------------------------------|-----------------------|----------| | LIM-004 | Notifications are sent individually per order. No bulk notification capability exists. Each notification requires a separate API call. | Notification Service | Medium | | LIM-006 | No progress tracking for batch operations. The system has no mechanism to track progress of multi-item operations because no batch operations exist. | All Services | Medium | **References:** [KB-146a6a29-932f-485d-96d6-6a92ee610336] [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] [KB-06c5403a-d177-4525-b247-1d7ae37a86b8] --- ### 2.4 Cross-Service and Performance Constraints | Limitation ID | Description | Impact Area | Severity | |---------------|-------------------------------------------------------------------------------------------------------------|---------------------|----------| | LIM-005 | Cross-service calls are sequential. Order creation flow (Order → Payment → Notification) executes sequentially. No parallel processing of payment and notification. | All Services | Medium | | DD-LIM-003 | Service calls are sequential. Payment and notification are executed one after another, not in parallel. | Order Processing | High | | DD-LIM-004 | No retry or circuit breaker mechanism. If the payment service is down, the operation fails immediately. | All Services | High | **References:** [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a] [KB-150eb89c-77b0-415b-a547-3ed0502eec24] [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf] --- ## 3. Data Model and Schema Constraints | Constraint ID | Description | Impact Area | Severity | |---------------|-------------------------------------------------------------------------------------------------------------|-----------------|----------| | SCHEMA-001 | No batch_id, csv_source, or bulk_import_group columns in orders table. Cannot track which orders belong to a batch import. | Data Model | High | | PAY-001 | Payment table enforces 1:1 uniqueness between order and payment. Batch grouping is not possible. | Payment Service | High | **References:** [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8] [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] [KB-02c65582-456a-4ebf-b934-b7e08bd16081] --- ## 4. Out-of-Scope Features The following features are explicitly out of scope for the current system: - Bulk or batch order creation (including CSV import, drag-and-drop, or batch forms) - Batch payment processing (no aggregation of multiple orders into a single transaction) - Bulk notification (no multi-recipient or group notification API) - Progress tracking for batch operations (no real-time batch status or error reporting) - Parallel or asynchronous processing of order, payment, or notification flows **References:** [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] [KB-146a6a29-932f-485d-96d6-6a92ee610336] [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6] [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8] --- ## 5. Summary Table: Scope Filters | Area | In Scope | Out of Scope | |---------------------|--------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------| | Order Creation | Single order via REST API | Bulk/batch order creation, CSV/file import, batch group tracking | | Payment Processing | One payment per order, max 1,000,000 JPY per transaction | Batch payment, payment aggregation, parallel payment processing | | Notification | One notification per order | Bulk notification, group notification, parallel/asynchronous notification | | Data Model | Order, payment, notification tables (no batch/group columns) | Batch_id, csv_source, bulk_import_group, or any batch-tracking field | | Progress Tracking | N/A (no batch operations supported) | Batch progress bars, real-time batch error reporting | | Error Handling | Per-transaction error logging | Batch error handling, partial batch success/failure reporting | **References:** [KB-146a6a29-932f-485d-96d6-6a92ee610336] [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f] [KB-10744011-e9ca-48b5-ac6d-4f9f-3627b7e6] [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8] [KB-02c65582-456a-4ebf-b934-b7e08bd16081] --- ## 6. Conclusion All requirements, features, and enhancements that would require batch, bulk, or parallel processing are outside the current system’s scope and will require significant architectural changes to implement. These scope filters must be strictly enforced for all migration, development, and integration activities. --- ## Sheet: Sections # Sheet: Sections ## 1. Functional and Constraint Requirements ### 1.1 Order Creation and Import - **Single-Entry Only:** The current system supports only individual order creation via REST API. There is no capability for bulk or batch order creation. Each order must be created one at a time ([KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c], [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], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]). - **UI Limitation:** The frontend displays a disabled CSV Import button with the label “CSVインポート（未実装）” and a BulkImportBanner warning indicating CSV import is not available ([KB-16181d30-2dd3-421e-bab0-939cd85255d2]). - **Client-Side Aggregation:** Dashboard statistics are computed in the browser due to lack of backend list-all endpoints ([KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-017cfb36-bd85-4935-a73e-91861c478baa]). - **No Real-Time Updates:** The system uses polling; WebSocket-based real-time updates are not implemented ([KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-017cfb36-bd85-4935-a73e-91861c478baa]). ### 1.2 Payment Processing - **No Batch Payment API:** Payment processing is strictly one transaction at a time. Each order requires an individual payment API call ([KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6]). - **Transaction Amount Limit:** Maximum amount per transaction is 1,000,000 JPY. This limit applies to individual orders; high-value orders exceeding this limit are rejected ([KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6]). - **No Aggregated Payment:** There is no mechanism to combine multiple orders into a single transaction ([KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6]). - **1:1 Unique Constraint:** The payment table enforces a unique constraint on order_id, preventing batch grouping ([KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6]). ### 1.3 Notification Processing - **No Bulk Notification:** Notifications are sent individually per order. Each notification requires a separate API call ([KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-06c5403a-d177-4525-b247-1d7ae37a86b8]). - **Rate Limiting:** Notification Service is rate-limited to 10 requests per second. Sending 10,000 notifications requires at least 1,000 seconds (~17 minutes) ([KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-06c5403a-d177-4525-b247-1d7ae37a86b8], [KB-04a84995-0820-4319-9d26-c1582821058a]). - **No Progress Tracking:** There is no mechanism to track progress of multi-item operations, as batch operations do not exist ([KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a]). ### 1.4 Processing Flow - **Sequential Execution:** All cross-service calls (Order → Payment → Notification) are executed sequentially, not in parallel. The overall latency is the sum of each step ([KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-150eb89c-77b0-415b-a547-3ed0502eec24]). - **No Retry or Circuit Breaker:** Failures in cross-service calls are logged but not retried. There is no circuit breaker mechanism ([KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-150eb89c-77b0-415b-a547-3ed0502eec24]). ### 1.5 Data Model and Schema Constraints - **No Batch Tracking Fields:** The orders table lacks batch_id, csv_source, and bulk_import_group fields. There is no mechanism to track which orders belong to a batch import ([KB-02c65582-456a-4ffe-8f7b-7d37af08e656], [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8]). - **Payment Table Constraints:** Payment table enforces a unique constraint on order_id, preventing batch payment grouping ([KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2]). - **No CSV Row Mapping:** There is no import_row_number field for mapping CSV rows to orders ([KB-02c65582-456a-4ffe-8f7b-7d37af08e656]). ## 2. Impact and Severity | 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. No endpoint or mechanism to upload files. | 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 ops. | All Services | Medium | ([KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a]) ## 3. Architectural and Technical Constraints - **REST API Only:** All inter-service communication is synchronous REST over HTTP. No message broker or asynchronous channels are present ([KB-0d7daadd-e958-4592-900a-55db91f8aa55]). - **Timeouts:** Payment service calls timeout after 30 seconds; notification/webhook calls timeout after 10 seconds ([KB-0d7daadd-e958-4592-900a-55db91f8aa55]). - **No Bulk Import UI:** No CSV upload, drag-and-drop, or batch creation form exists in the frontend ([KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-16181d30-2dd3-421e-bab0-939cd85255d2]). - **N+1 API Pattern:** Payments and notifications pages use N+1 query pattern due to missing list-all endpoints ([KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-017cfb36-bd85-4935-a73e-91861c478baa]). ## 4. Performance and Reliability - **Bulk Operations Are Extremely Slow:** Processing 10,000 orders requires 10,000 API calls. Due to sequential execution and rate limits, bulk operations are extremely slow ([KB-150eb89c-77b0-415b-a547-3ed0502eec24], [KB-04a84995-0820-4319-9d26-c1582821058a]). - **No Error Handling for Batch:** If one item in a batch fails, there is no mechanism to continue processing remaining items ([KB-04a84995-0820-4319-9d26-c1582821058a]). - **No Retry:** Failed API calls are not retried; errors are logged ([KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-150eb89c-77b0-415b-a547-3ed0502eec24]). ## 5. Summary Table of Key Constraints | Constraint Area | Limitation Description | Reference(s) | |------------------------|--------------------------------------------------------------------------------------------------|---------------------------------------------------------| | Order Creation | Only single-entry order creation; no batch/bulk capability | [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c] | | CSV Import | No CSV/file import endpoint or UI; batch tracking fields missing | [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-16181d30-2dd3-421e-bab0-939cd85255d2], [KB-02c65582-456a-4ffe-8f7b-7d37af08e656] | | Payment Processing | No batch payment API; max 1,000,000 JPY per transaction; 1:1 order/payment constraint | [KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6], [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2] | | Notification | No bulk notification; rate limit 10/sec; sequential execution | [KB-06c5403a-d177-4525-b247-1d7ae37a86b8], [KB-04a84995-0820-4319-9d26-c1582821058a] | | Progress Tracking | No batch progress tracking; no batch error handling | [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-04a84995-0820-4319-9d26-c1582821058a] | | Parallel Processing | All operations are sequential; no parallel or queue-based processing | [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-150eb89c-77b0-415b-a547-3ed0502eec24] | | Error Handling | No retry or circuit breaker; errors logged only | [KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-150eb89c-77b0-415b-a547-3ed0502eec24] | ## 6. [GAP: Missing data for Sheet: Sections] If additional requirements or constraints are needed for this section, please provide further context.