11 — Known Issues in the Proposal and Open Questions

Keep this list current. When a question is answered, move it to "Resolved" with the date and source.

Use-case review — 2026-10-31 (open, proposals)

Full review of all 162 cases records UR-Q01…10 with proposed respondents and affected cases: guardian data/purpose, participating TCAS rounds and rights, finance states, legal authority and appeal effects, cohort academic rules, clinical/safeguarding protocols, dorm/deposit/immigration, sports-school guardian exceptions, data retention/disclosure, and uncovered BA functions. No institutional answer has been inferred from another university's website. The proposed source/workflow changes must be checked against these answers before individual Development Approval. The canonical source now distinguishes conditional branches; cases with only review notes still require further specification as indicated in the report.

A. Known issues in TNSU_EDU_Proposal_281069_Stream.docx (v1.0, 27-10-2026)

Sections not yet written for TNSU (high impact)

§5 (5.1–5.3, ≈ p. 27–29) and §7 (7.1–7.3, ≈ p. 32) still contain leftover template text from another project. The team confirmed (2026-10-30) that the proposal was started from another project's document and this content was not removed. Ignore it completely. Treat these sections as missing: architecture, integrations, quality requirements, budget and service model. The TOC entry "6.1 ขอบเขตตามแพ็กเกจ" is a leftover from the same template.

Internal inconsistencies (low impact)

• Two different 12-module lists (§4.1 vs. §6.1). See 03-modules.md for the mapping.
• §6.2 says "5 main phases" but the table has 6.
• §3.2 table repeats the first row ("ระบบทะเบียนมหาวิทยาลัยทั่วไป") at the end.
• The architecture figure is captioned "ภาพที่ 5", which duplicates the finance workflow figure number (should be ภาพที่ 14).
• The TOC headings differ from the body (TOC "6.3 ปัจจัยความสำเร็จ" vs. body 6.3 = team, 6.4 = success factors).
• Stray "/" at the end of the §5 and §7 headings.

→ Suggest that the vendor fixes these before the proposal goes to the client.

A2. Known issues in the BA module structure (draw.io source TNSU_EDU 191069.drawio, received 2026-10-30)

• Duplicate numbering, confirmed in the source: SS 8.3 ×2, SS 14.3 ×2, SS 15.3 ×2. Docs renumber the second one to .4.
• Colours: UNI 1–6 are green, UNI 7–8 and all SS modules are pink. The file has no legend, so the meaning is still not stated.
• Settings that should be system-wide (fees, academic year, user permissions) sit under UNI-01 only.
• The overview page "module" shows only the 8 university modules under "ระบบการจัดการบริหารการศึกษา". Is the sports-school system meant to be a separate system, or is the overview not yet updated?
• ~~The image is low resolution~~: resolved 2026-10-30, the draw.io source was provided and the transcription matched it exactly.

A3. Gaps between the BA structure and the proposal (updated with the use cases, 2026-10-30)

The proposal promises these, but the BA chart has no module for them. The use cases (12-use-cases.md) now cover several of them:

A4. Use cases vs. BA chart (2026-10-30)

• In the use cases but not in the BA chart or proposal: graduate studies (GRAD), teaching practicum and internships (PRA), child safeguarding and safe sport (SAFE), PDPA consent (PRIV), facility booking (FAC), sports-science lab (LAB), external revenue courses (REV), regulatory reporting (RPT), official-information requests (W-20), military deferment (W-59), foreign students and ตม.30. Confirm these are in scope for this contract.
• In the BA chart but without a use case: SS-08 nutrition (menus, meal log, ingredients and food cost), SS-05.3 duty-teacher roster, SS-05.4 dorm maintenance requests, SS-03.4 lesson plans, SS-13.1 conduct points.
• LAB is moved to a separate contract, 2574+ (D-06, REL-09). Automatic cross-campus clearing is out of R1 (D-06). Ask what else R1 includes.
• The use cases reference documents not in this repo: "เล่ม 02 Workflow" (and presumably เล่ม 01…), the decision log (D-xx), release notes (REL-xx), the SoD list (SoD-01…18), constraint C-5, and the screen designs (A01…X01, Wxxx). Ask the team for them.
• W-63 is missing from the numbering.
• 18 items are marked [ต้องตรวจสอบ]. The list is in 12-use-cases.md.
• Code collision: UC module SCH (scholarships) vs. the BA sports-school branch. The docs code the BA branch as SS-xx.

B. Open questions for TNSU (resolve in Phase 1)

Scope

1. Exact module list and priority order for phased go-live. Which modules are in the first release?
2. ~~Legacy E-Education~~: answered. There is no legacy system (2026-10-30). Initial data (students, staff, curricula) will still need a one-off import [inferred]; see the B02 import-wizard screen.
3. Do university campuses also need the dorm module (mockups show university dorm booking)?
4. Alumni module depth (directory only, or engagement and services?).
5. AI Bot knowledge sources (regulations, handbooks, FAQs?) and which languages it must support.
6. AI Analytics: which predictions or analyses are expected (dropout risk, athlete performance, finance forecasts)?

Integrations

1. ~~กยศ. integration~~: partly answered. Use cases operate through the กยศ. DSL portal (portal-assist, W-48, W-119, W-133). Is any API or file exchange expected?
2. DGA: which document types need DGA e-signature vs. internal signing? (No use case mentions DGA.)
3. Payment-gateway provider (bank?). Use cases assume Thai QR with bank callback or statement reconciliation (W-51). Is credit card still in scope?
4. Other systems: HR / personnel, budget / finance ERP (GFMIS export is in W-116), LMS product, national education databases for sports schools?

Identity and access

1. ~~Authentication~~: partly answered. ThaID or e-mail + OTP for applicants, guardians and alumni; MFA for staff (W-142); SSO at enrolment (W-44). Which identity provider?
2. ~~Parent linking~~: answered in W-127, W-128 and W-160 (relation types, verification levels, consent for adult students).
3. Can staff belong to several units? (Use cases have delegation and acting roles, W-123, but do not say.)

Non-functional and operations

1. ~~Database engine~~: answered, SQL Server (2026-10-30). Still open: version / edition and where it runs.

14a. Hosting (government cloud vs. on-premises), data residency, and the AI-provider constraints that follow from them.

1. Availability, performance and retention targets. Peak concurrent users during registration.
2. Mobile approach: native vs. cross-platform vs. PWA (use cases mention LIFF/PWA for parents). App-store publishing under whose account?
3. ~~Notification channels~~: answered in W-36 (in-app, LINE, e-mail, SMS).

Commercial

1. Budget and pricing model for TNSU (§7 has not been written).
2. Maintenance SLA levels.

From the BA draw.io file (2026-10-30)

1. Which campuses offer which programmes? The org tree puts faculties under each campus, but the curriculum list is not split by campus.
2. In sports schools, is sport type (ชนิดกีฬา) really under grade level (ระดับชั้น), or a separate dimension (a student has one grade and one sport)?
3. Are the English and Thai names of each graduate programme the same programme (we paired them)?
4. Do sports schools also use the curriculum-creation and course-offering flows, or only the university?

From the use cases

1. Which use cases are in R1? Is there a release plan per module?
2. Are GRAD, PRA, SAFE, FAC, LAB and REV in this contract (LAB is already moved to 2574+)?
3. Resolve the 18 [ต้องตรวจสอบ] items with the relevant offices (registrar, legal, medical, sports science).

C. Resolved

• 2026-10-30: Proposal §5 and §7 content is leftover template text from another project and is not TNSU scope. Source: the team member who prepared the proposal.
• 2026-10-30: No legacy system. The proposal's "ระบบเดิม E-Education" does not exist; the build is greenfield. Source: project owner.
• 2026-10-30: Tech stack decided (ADR-0001): Vue/Nuxt.js, Go Stream Framework, RustFS, Redis, Harbor, ArgoCD, Rancher, K8s, OpenSearch, Grafana. Source: project owner.
• 2026-10-30: Database = SQL Server, because the customer already uses SQL Server. Queues use RabbitMQ as a consequence. Source: review of tracker task T-302 by ทิว.
• 2026-10-30: Policy values (fees, rules, thresholds, limits) are set by the university or lecturers through configuration, not by the project team. The 18 "[ต้องตรวจสอบ]" items that are values become configurable settings. Source: project owner.
• 2026-10-30: Approach agreed: draft Role and Security Matrices now (done: 13, 14); data model designed module by module after research; sitemap and mockups later on request; integrations specified with the module that needs them. Source: project owner.
• 2026-10-30: BA source file received (TNSU_EDU 191069.drawio): replaces the low-resolution image; adds the organisation structure, the curriculum list and two process flows. Source: project owner.
• 2026-10-30: Graduate studies are in scope: the curriculum list has master's and doctoral programmes (so use-case module GRAD applies). Source: BA draw.io.
• 2026-10-30: Parent/guardian linking and verification, adult-student consent, and notification channels are defined in the use cases (W-127, W-128, W-160, W-36). Source: use_cases/UC1-Explorer.dc.html.

• 2026-10-30: Internal Use cases editor: project owner selected shared diagram storage and a table catalog in the tracker. Editable diagrams are separate discovery drafts; the source explorer remains authoritative for behaviour. See 12-use-cases.md.

• 2026-10-30: Tracker channel tabs are preliminary and may overlap. Confirm actual Frontend/Backoffice screens and integration contracts during sitemap/integration design; actor participation or a named system is evidence for a navigation tag, not approval of product UI/API scope.

• 2026-10-30: Owner requires per-use-case human approval before an agent implements TNSU product behaviour. Approval applies only to the reviewed source and diagram revision; edits/rollback require confirmation again. Reviewer name/time/note and history are recorded in the internal tracker. This does not approve any use case automatically or settle open business rules in the source.

• 2026-10-30 planning clarification: Hosting is still open. Task T-303 now defines the decision process, outputs and five recipient-specific questions (T303-Q1–T303-Q5) covering mandate/authority, inventory, capacity, recovery/access and acquisition/operations ownership. Refer to preparation task briefs. Neither brief enrichment nor preliminary trade-offs choose a hosting provider.