B
Local University Department Transition Curriculum Design
2.85
Derivation Chain
Step 1
Local university restructuring and Dong-eui University personnel changes
→
Step 2
Designing new departments after mergers and closures
→
Step 3
Automation tool for new department curriculum design
Problem
When local private universities merge or create departments amid enrollment reductions, curriculum design takes 3-5 professors over 6 months or more. Designing curricula disconnected from industry demand leads to lower employment rates, creating a vicious cycle of repeated disadvantages in Ministry of Education evaluations. Especially when creating interdisciplinary departments like AI and data science, the lack of expertise among existing faculty results in low curriculum quality.
Solution
Based on industry demand data (job posting keyword analysis, NCS job competency maps) and benchmarking of similar departments at other universities, automatically generates a draft semester-by-semester curriculum (required/elective courses, credit allocation, practical training weight) when department goals are entered. Includes optimization of faculty expertise and course matching.
NUMR-V Scores
NUMR-V Scoring System
| N Novelty | 1-5 | How uncommon the service is in market context. |
| U Urgency | 1-5 | How urgently users need this problem solved now. |
| M Market | 1-5 | Market size and growth potential from proxy indicators. |
| R Realizability | 1-5 | Buildability for a small team with realistic constraints. |
| V Validation | 1-5 | Validation signal quality from competition and demand data. |
N=.15 U=.20 M=.15 R=.30 V=.20
Feasibility (70%)
Data Availability
20.4/25
Feasibility Breakdown
| Tech Complexity | / 40 | Difficulty of core implementation stack. |
| Data Availability | / 25 | Practical availability and cost of required data. |
| MVP Timeline | / 20 | Expected time to ship a usable MVP. |
| API Bonus | / 15 | Bonus for viable public API leverage. |
Market Validation (56/100)
Validation Breakdown
| Competition | / 20 | Signal quality from competitor landscape. |
| Market Demand | / 20 | Demand proxies from search and mention patterns. |
| Timing | / 20 | Fit with current shifts in tech, behavior, and regulation. |
| Revenue Signals | / 15 | Reference evidence for monetization viability. |
| Pick-Axe Fit | / 15 | How well the concept serves participants in a trend. |
| Solo Buildability | / 10 | Practicality for lean-team implementation. |
Technical Requirements
Data Pipeline [medium]
Backend [medium]
Frontend [low]