Stage 1 — Problem Scoping
Before you build anything, you have to know what you are building it for. This first stage sounds like the easy one. It is the one projects most often get wrong.
1What problem scoping is
Tap a stage to stand on it, or press play and watch the work go round. Drag sideways to turn.
It answers: What are we trying to solve, and for whom?
2Getting the problem clear
A vague problem gives a useless project. “Help farmers” is not a problem you can build for. Keep asking questions until the sentence is small enough to act on:
- Who has this problem? Farmers — which farmers, growing what?
- What exactly goes wrong for them? Their crop gets a disease and they notice too late.
- Where and when does it happen? In the field, during the growing season.
- Why is solving it worth the effort? An early warning saves the harvest.
A doctor who does not ask
3Parameters
Parameters are the things that affect the problem. For the crop-disease project: the type of crop, the season, rainfall, the soil, how old the plant is. Listing them now matters, because in the next stage these are exactly the things you will go and collect data about.
4From the board papers
(A) To collect data (B) To understand the aim and objective of the project (C) To train the model (D) To process dataCBSE AI Class X textbook, Unit 1
▶Show the answer
(B). The problem statement is what tells everyone what the project is for. Collecting and processing data come later, and they are done because of what the problem statement says.
5Check yourself
Which of these is a properly scoped problem?
In problem scoping, what are parameters?