Use fuzzy forecasting when historical data are scarce but experience knowledge is available, because the method tolerates imperfect data¶
Design Method · All design methods
Evidence · no claims cited
Description¶
The article recommends fuzzy time series forecasting where accurate historical data are hard to obtain, because experience knowledge can be used "from thevery beginning until theend of the whole forecasting process". The authors state that "the requirement for thehistorical data is not very strict": the same model could be built from gathered experience about enrollment development even without the data. This makes the method suitable for planning contexts with limited records.
Design Implications¶
Context¶
Requirements¶
- Access to experience knowledge from persons acquainted with the phenomenon being forecast, or sufficient historical data to derive the fuzzy logical relationships.
Constraints¶
- The stated advantage is demonstrated for one university's enrollment forecasting case.
Target Learners¶
- higher education planners working with incomplete enrollment records
Target Learning Objectives¶
- enrollment forecasting under imperfect historical data
Claims¶
Related Methods¶
Related Principles¶
Examples¶
-
Key Sources¶
- Song, Qiang; Chissom, Brad S. (1991). Forecasting Enrollments with Fuzzy Time Series. https://eric.ed.gov/?id=ED340733
Page metadata
| Field | Value |
|---|---|
type |
method |
id |
fuzzy-forecasting-when-historical-data-requirements-are-loose |
title |
Use fuzzy forecasting when historical data are scarce but experience knowledge is available, because the method tolerates imperfect data |
description |
The article recommends fuzzy time series forecasting where accurate historical data are hard to obtain, because experience knowledge can be used "from thevery beginning until theend of the whole forecasting process". |
status |
review |
generated |
by process:wiki-ingest on 2026-09-26 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — song-1991 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.