{"text_format":"2","workbook":"xlsx","n_sheets":2,"sheets":["Document","Metadata"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Document","index":0,"n_rows":17,"n_cols":2,"rows_kept":17,"cut":false,"hidden":false,"merged":[]}
["Section","Content"]
["Sheet: Template Info","Sheet: Template Info\n====================\n\n[GAP: Missing data for Sheet: Template Info]"]
["Sheet: Scope Filters","# Sheet: Scope Filters"]
["1. Overview","This section defines the explicit scope filters for the system, describing the boundaries and limitations of included and excluded features, operations, and data domains. Scope filters are critical to ensure alignment with business requirements, technical constraints, and regulatory compliance. All content below is strictly derived from the provided context.\n\n---"]
["2. Functional Scope Filters","### 2.1 Included Functionalities\n\nThe following functionalities are within the system scope:\n\n- **Single Order Creation:** The system supports creation of one order at a time via REST API or management UI. Each order must specify customer information (name, email) and order details (item, quantity, unit price). The total amount is auto-calculated from line items. [KB-0e0f1dd0-0f46-4d13-a092-e3cdc6fdd205]\n- **Order Listing and Detail Retrieval:** Orders can be listed with pagination (skip, limit), and individual order details can be retrieved. [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495]\n- **Order Status Management:** Order status can be updated, and cancellation triggers refund and notification workflows. [KB-0972bd0e-7d3f-4b2c-a364-813e023a3495]\n- **Payment Processing:** Each order is processed with a dedicated payment transaction. [KB-05a9aed3-6a71-4c74-ac19-6bfec293268b]\n- **Notification Service:** Notifications (e.g., confirmation emails) are sent per order. [KB-05a9aed3-6a71-4c74-ac19-6bfec293268b]\n\n---\n\n### 2.2 Excluded Functionalities\n\nThe following are explicitly out of scope:\n\n| Limitation ID | Description                                                                                                      | Impact Area          | Severity |\n|---------------|------------------------------------------------------------------------------------------------------------------|----------------------|----------|\n| LIM-001       | **No bulk or batch order creation.** Orders can only be created one at a time via the REST API.                  | Order Service        | High     |\n| LIM-002       | **No CSV/file-based order import.** There is no endpoint or mechanism to upload and process order data from files.| Order Service        | High     |\n| LIM-003       | **No batch payment API.** Each order requires an individual payment API call.                                     | Payment Service      | High     |\n| LIM-004       | **No bulk notification capability.** Each notification requires a separate API call.                              | Notification Service | Medium   |\n| LIM-005       | **No parallel or queue-based processing.** All cross-service calls (Order → Payment → Notification) are sequential.| All Services         | Medium   |\n| LIM-006       | **No progress tracking for batch operations.** No mechanism exists to track progress of multi-item operations.    | All Services         | Medium   |\n\n[KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-0f930ddc-1f3e-4014-a015-49fe1808f8d8], [KB-04a84995-0820-4319-9d26-c1582821058a], [KB-150eb89c-77b0-415b-a547-3ed0502eec24]\n\n---"]
["3. Data Scope Filters","### 3.1 Included Data\n\n- **Order Data:** Each order record includes customer information (name, email), order items (product name, quantity, unit price), and calculated total amount. [KB-0e0f1dd0-0f46-4d13-a092-e3cdc6fdd205]\n- **Payment Data:** Each payment is linked 1:1 with an order (unique order_id), amount (min 100 JPY, max 1,000,000 JPY), currency (JPY), and transaction details. [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2]\n- **Notification Data:** Notification records are maintained per order. [KB-05a9aed3-6a71-4c74-ac19-6bfec293268b]\n\n### 3.2 Excluded Data\n\n- **Batch/Group Import Metadata:** No batch_id, csv_source, or bulk_import_group columns exist in the orders schema. There is no mechanism to track which orders belong to a batch import. [KB-0f930ddc-1f3e-4014-a015-49fe1808f8d8], [KB-02c65582-456a-4ebf-b934-b7e08bd16081]\n- **CSV Row Mapping:** No import_row_number or related mapping exists. [KB-02c65582-456a-4ebf-b934-b7e08bd16081]\n\n---"]
["4. Technical and Architectural Scope Filters","- **Synchronous REST Only:** All inter-service communication is synchronous REST over HTTP. No message broker, event bus, or asynchronous channel is present. [KB-0d7daadd-e958-4592-900a-55db91f8aa55]\n- **No Real-Time Updates:** The system does not support real-time updates (e.g., via WebSocket); polling is required for dashboard/statistics. [KB-017cfb36-bd85-4935-a73e-91861c478baa]\n- **No Internationalization:** The system is single-language (Japanese); no i18n framework is implemented. [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]\n\n---"]
["5. Regulatory and Security Scope Filters","- **PHI Handling:** All error responses in production must not contain PHI, stack traces, SQL queries, internal file paths, server names, or framework version information. [KB-10300d8a-a98a-4726-9be3-3957c2fe7bf4], [KB-140ca7f3-3348-4419-b06b-89561882a35e]\n- **Transaction Limits:** Payment transactions are limited to a maximum of 1,000,000 JPY per order. [KB-01305cb3-d331-4b4b-ba02-69ada467b41d], [KB-11739ab0-b209-41e4-b73e-7d7e0c4338b2]\n- **No Bulk Export for PHI:** No bulk export or batch download of PHI is supported. [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]\n\n---"]
["6. Out-of-Scope Features","The following features are not supported and require architectural changes for future inclusion:\n\n- Bulk or batch order creation (CSV upload, drag-and-drop, batch form)\n- Batch payment processing or payment aggregation\n- Bulk notification sending\n- Progress tracking for batch operations\n- Real-time dashboard/statistics updates\n- Internationalization (multi-language support)\n- Batch error handling and partial failure recovery\n\n[KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c], [KB-04a84995-0820-4319-9d26-c1582821058a], [KB-0f930ddc-1f3e-4014-a015-49fe1808f8d8]\n\n---"]
["7. Summary Table: Scope Filters","| Area                    | Included Scope                                               | Excluded Scope (Out-of-Scope)                                                                                      | Reference(s)                                   |\n|-------------------------|-------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------|------------------------------------------------|\n| Order Creation          | Single order via API/UI                                     | Bulk/batch order creation, CSV/file import                                                                         | [KB-146a6a29-932f-485d-96d6-6a92ee610336]      |\n| Payment Processing      | One payment per order, max 1,000,000 JPY                    | Batch payment, payment aggregation                                                                                 | [KB-01305cb3-d331-4b4b-ba02-69ada467b41d]      |\n| Notification Service    | Per-order notification                                      | Bulk notification, notification batching                                                                           | [KB-05a9aed3-6a71-4c74-ac19-6bfec293268b]      |\n| Data Model              | Order, payment, notification data                           | Batch/group import metadata, CSV row mapping                                                                       | [KB-0f930ddc-1f3e-4014-a015-49fe1808f8d8]      |\n| Technical Architecture  | Synchronous REST, polling for updates                       | Message broker, event bus, async processing, real-time updates                                                     | [KB-0d7daadd-e958-4592-900a-55db91f8aa55]      |\n| Internationalization    | Japanese only                                               | Multi-language/i18n                                                                                                | [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]      |\n| Security                | PHI-safe error responses, transaction amount limits         | PHI in errors, bulk PHI export                                                                                     | [KB-10300d8a-a98a-4726-9be3-3957c2fe7bf4]      |\n| Batch Operations        | Not supported                                               | Progress tracking, error handling, partial failure recovery for batch operations                                   | [KB-04a84995-0820-4319-9d26-c1582821058a]      |\n\n---"]
["8. Gaps","No additional scope filters are defined beyond the above. Any requirements not explicitly included are considered out of scope unless otherwise stated.\n\n---\n\n**End of Sheet: Scope Filters**"]
["Sheet: Sections","# Sheet: Sections\n\nThis section provides a structured overview of the system's requirements, constraints, and limitations as they pertain to order management, payment processing, and notification services. All content is derived strictly from the provided knowledge base context.\n\n---"]
["1. Functional and Non-Functional Requirements","### 1.1 Order Management Functional Requirements\n\n| ID     | Requirement                                                                                             | Priority |\n|--------|--------------------------------------------------------------------------------------------------------|----------|\n| FR-001 | Ability to create a single order specifying customer information (name, email) and order details (item, quantity, unit price). | P1       |\n| FR-002 | Automatic calculation of total order amount as the sum of (quantity × unit price) for all items.        | P1       |\n| FR-003 | Ability to retrieve a paginated list of orders (parameters: skip, limit).                              | P1       |\n\n*Source: [KB-0e0f1dd0-0f46-4d13-a092-e3cdc6fdd205]*\n\n### 1.2 Payment Processing Functional Requirements\n\n- Payment processing is performed per order. Each order requires an individual API call to the Payment Service.\n- Payment amount per transaction must be between 100 JPY and 1,000,000 JPY.\n- No batch payment API exists; aggregation of multiple orders into a single payment transaction is not supported.\n- Payment API endpoint: `POST /api/v1/payments` with payload `{\"order_id\": N, \"amount\": N.N, \"currency\": \"JPY\"}`.\n- On payment failure, the order status is reverted to \"pending\".\n\n*Source: [KB-1718c2d8-b71b-4113-9906-a6d9765958ff], [KB-186b33d7-f985-455b-8117-0cd019912510], [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6], [KB-11739ab0-b209-41e4-b73e-4046f368bb23]*\n\n### 1.3 Notification Service Functional Requirements\n\n- Notification Service processes one notification per API call; bulk notification is not supported.\n- Notification API endpoint: `POST /api/v1/notifications/email` (one email per request).\n- Notification rate limit: 10 requests per second.\n- For 10,000 orders, notification delivery will take at least 1,000 seconds (~17 minutes).\n\n*Source: [KB-05a9aed3-6a71-4c74-ac19-6bfec293268b], [KB-06c5403a-d177-4525-b247-1d7ae37a86b8], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-04a84995-0820-4319-9d26-c1582821058a], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]*\n\n---"]
["2. System Constraints and Limitations","### 2.1 Order Creation and Import\n\n| ID      | Limitation                                                                                                   | Impact Area    | Severity |\n|---------|-------------------------------------------------------------------------------------------------------------|----------------|----------|\n| LIM-001 | Only single order creation is supported. No bulk or batch order creation capability exists.                  | Order Service  | High     |\n| LIM-002 | No CSV/file-based order import functionality. No endpoint or mechanism to upload and process order data from files. | Order Service  | High     |\n\n*Source: [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-05b70fbd-4026-4ac9-b1e2-e21dabe7da5c], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f], [KB-16181d30-2dd3-421e-bab0-939cd85255d2]*\n\n### 2.2 Payment Processing\n\n| ID      | Limitation                                                                                                   | Impact Area       | Severity |\n|---------|-------------------------------------------------------------------------------------------------------------|-------------------|----------|\n| LIM-003 | Payment processing is strictly one transaction at a time. No batch payment API exists.                       | Payment Service   | High     |\n| DD-PAY-LIM-002 | No aggregation of amounts. Multiple orders cannot be combined into a single payment transaction.      | Payment Service   | High     |\n| DD-PAY-LIM-003 | Maximum of 1,000,000 JPY per transaction. This applies to individual orders; high-value orders are rejected. | Payment Service   | Medium   |\n| DD-PAY-LIM-004 | 1:1 unique constraint prevents batch payment grouping.                                                | Payment Service   | Medium   |\n\n*Source: [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-10744011-e9ca-48b5-ac6d-4f9f3627b7e6], [KB-11739ab0-b209-41e4-b73e-4046f368bb23]*\n\n### 2.3 Notification Processing\n\n| ID      | Limitation                                                                                                   | Impact Area            | Severity |\n|---------|-------------------------------------------------------------------------------------------------------------|------------------------|----------|\n| LIM-004 | Notifications are sent individually per order. No bulk notification capability exists.                       | Notification Service   | Medium   |\n| LIM-005 | Cross-service calls are sequential. Payment and notification are executed one after another, not in parallel.| All Services           | Medium   |\n| LIM-006 | No progress tracking for batch operations, as no batch operations exist.                                     | All Services           | Medium   |\n\n*Source: [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-04a84995-0820-4319-c1582821058a]*\n\n### 2.4 Performance and Scalability\n\n- For 10,000 orders, 10,000 individual API calls are required for both payment and notification processing, resulting in extremely slow bulk order processing.\n- Service-to-service calls are strictly sequential (Order → Payment → Notification). There is no parallel or queue-based processing.\n- No retry or circuit breaker mechanisms are implemented for cross-service calls; failures are logged but not retried.\n- No mechanism exists to continue processing remaining items in a batch if one fails, as batch operations are not supported.\n\n*Source: [KB-150eb89c-77b0-415b-a547-3ed0502eec24], [KB-033639ab-c6f8-4f72-a373-bf76d05dd6cf], [KB-04a84995-0820-4319-c1582821058a], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]*\n\n### 2.5 Data Model Constraints\n\n- The orders table does not have a batch_id, csv_source, or bulk_import_group column. There is no mechanism to track which orders belong to a batch import.\n- The payments table enforces a 1:1 unique constraint on order_id, preventing batch payment grouping.\n\n*Source: [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8], [KB-11739ab0-b209-41e4-b73e-4046f368bb23], [KB-02c65582-456a-4ffe-8f7b-7e08bd16081]*\n\n---"]
["3. User Interface and Experience","- The order management UI displays a warning banner indicating that CSV import is not available.\n- The CSV Import button is disabled and labeled as \"CSV Import (Not Implemented)\".\n- Users can only create orders one at a time via the form; no drag-and-drop or batch creation is available.\n\n*Source: [KB-16181d30-2dd3-421e-bab0-939cd85255d2], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]*\n\n---"]
["4. Summary Table of Key Limitations","| Area                 | Limitation Description                                                                                   | Severity |\n|----------------------|---------------------------------------------------------------------------------------------------------|----------|\n| Order Creation       | No bulk or batch order creation; only single order creation supported                                   | High     |\n| File Import          | No CSV/file-based order import functionality                                                            | High     |\n| Payment Processing   | No batch payment API; one transaction per order; no aggregation; 1:1 order-payment constraint           | High     |\n| Notification         | No bulk notification; one notification per API call; rate-limited to 10/sec                             | Medium   |\n| Processing Pattern   | All cross-service calls are sequential; no parallel or queue-based processing                           | Medium   |\n| Error Handling       | No retry/circuit breaker for cross-service calls; failures are logged but not retried                   | Medium   |\n| Progress Tracking    | No progress tracking for batch operations (since batch operations are not supported)                    | Medium   |\n| Data Model           | No batch_id/csv_source/bulk_import_group in orders table; cannot track batch imports                    | High     |\n\n*Source: [KB-146a6a29-932f-485d-96d6-6a92ee610336], [KB-0a7d4d64-4d48-4214-94eb-2f3f278ec66a], [KB-0f930ddc-1f3a-4014-a015-49fe1808f8d8], [KB-11739ab0-b209-41e4-b73e-4046f368bb23], [KB-02c65582-456a-4ffe-8f7b-7e08bd16081], [KB-16181d30-2dd3-421e-bab0-939cd85255d2], [KB-0a36efdc-f63e-4c6b-8191-220e34d8af3f]*\n\n---"]
["5. Compliance with ISO/IEC/IEEE 29148:2018","This section addresses the requirements for system and software requirements specification as mandated by ISO-29148, including:\n\n- Explicit statement of functional and non-functional requirements\n- Clear identification of system constraints and limitations\n- Use of structured tables for traceability and clarity\n- No assumptions or unstated requirements; all content is strictly evidence-based\n\n---\n\n**End of Sheet: Sections**"]

{"sheet":"Metadata","index":1,"n_rows":7,"n_cols":2,"rows_kept":7,"cut":false,"hidden":false,"merged":[]}
["Property","Value"]
["document_id","1bde97d2-a40f-44a5-9493-6b37adfedcf9"]
["tenant_id","28aa3971-48af-4f2a-aa73-9e4f89fbfba4"]
["kb_project_id","None"]
["document_type","markdown"]
["is_stale","False"]
["generated_at","2026-03-25T03:37:55.794479+00:00"]