Systems Analysis and Design
What you must know
The systems life cycle moves through analysis, design, development, testing, implementation and maintenance. Learn methods of fact-finding (interviews, questionnaires, observation, document analysis), feasibility (technical, economic, legal, operational), and design tools (DFDs, ER diagrams, flowcharts). Understand implementation strategies (direct, parallel, phased, pilot) and the purpose of documentation and evaluation.
Traps candidates fall into
- Confusing analysis (what is needed) with design (how it will work).
- Choosing direct changeover without noting risk - it is cheapest but riskiest.
- Forgetting to mention user involvement in fact-finding.
- Describing testing as a single step - it is planned and uses test data.
- Ignoring maintenance as part of the cycle.
Rule of thumb
Match implementation to risk: parallel is safest but doubles work; direct is fastest but riskiest; phased and pilot balance both.
Worked example
A school replaces its exam system. Fact-finding: interview staff, observe current process, review forms. Feasibility: cost, skills, legal data protection. Implement by pilot in one department to catch problems before full rollout.