Lesson 2: Requirements Analysis and Planning

The first step in any project is understanding what users need. This can involve interviews, surveys, or observing tasks to gather functional and non-functional requirements. For example, if building a mobile banking app, requirements might include "allow users to view account balance" or "send notifications for transactions." Clear requirements prevent misunderstandings later on. Always document requirements carefully in words (like user stories) or simple diagrams.

After gathering information, developers write it down in a formal way. Common tools include use-case diagrams (showing how users interact with the system) or user stories ("As a user, I want…"). A software specification might list all functions in detail. This plan acts like a contract: everyone (clients, developers) reviews it before coding. In exams, you may need to draft a small use-case or explain the purpose of a requirements document.