What are we looking at?
Before we build or improve anything, why must we first understand exactly what we want?
Systems analysis, in plain language
Every day we deal with many systems: transport, education, information systems, governance and even biological systems. Understanding and improving any of them is impossible without “analysis”. Systems analysis means a second, deeper and more structured look at what exists, so that we understand better, design better and finally decide better.
More precisely, systems analysis is a process for understanding a system’s structure, components, relations, goals and limits. Suppose we want to improve a city’s transport. Before any plan or proposal we must know who plays a part in this system, what its main components are, what the inputs and outputs are, what its purpose is, and where it is inefficient. Without this first understanding, any action can lead to a wrong design or a misplaced decision. Analysis is the introduction to every successful design.
Why are requirements so important?
Knowing the requirements means knowing what the system must do, what users expect, what limits exist, and which goals must be met. If these aren’t analysed properly there are two serious risks: the design won’t match the real need, and later the cost of redesign, stakeholder dissatisfaction and project failure rises. That is why I think requirements analysis is a kind of “insurance for project success”.
What does the analyst do here?
The systems analyst is a bridge between users, designers and decision-makers. They must listen (hear the user’s need), ask questions (uncover hidden assumptions), document (write needs precisely) and analyse (what matters most, where the conflicts are). But the job isn’t just collecting information; it is building a shared mental model among all stakeholders.