Think like a Detective!
Before you write a single line of code, you must understand the problem. Analysis is all about finding out exactly what the user needs the program to do.
How do we gather information?
We use several methods to study the current system and define the requirements for the new one:
📊 Questionnaires
Handed out to many people to get a wide range of opinions quickly.
🎙️ Interviews
One-on-one talks with the manager or main user to get deep details.
👀 Observation
Watching how the current system (or manual way) works in real life.
📑 Document Sampling
Looking at the existing paper forms or files to see what data is collected.
The Goal: Requirements Specification
By the end of the Analysis stage, the developer creates a document that answers these key questions:
Inputs: What data will the user type in? (e.g., Age, Name, Price)
Processing: What calculations or logic are needed? (e.g., Price * 0.2)
Outputs: What will the screen display or the printer print?
Hardware: Does it need a touchscreen? A barcode scanner?
Software: Which OS or language will be used?
Remember: If you get the Analysis wrong, the whole project will fail—even if your code is perfect!