Adopting an analyst’s approach to gathering system requirements.
Summary
Business analysts often reverse-engineer requirements by evaluating existing technology, and determining how important the problems it was designed to solve are to their own organisation. Business analysts facilitate large, business-critical projects on a regular basis, so researching and learning from their latest strategies and best practices, and the ways in which they can be replicated for your own objectives, is a worthwhile exercise. Even if you have prior experience of CAFM requirements gathering, or are switching from existing software you helped implement, the market – and the technology available – is likely to have moved on since then. By approaching the task of gathering requirements from the perspective of a business analyst, you can borrow from their range of tried and tested methodologies, resulting in a better- organised, more efficient process, with clear timelines and justification for your activities – a solid foundation for your project. There are four types of CSF: A business analyst often needs to carry out a GAP analysis, which reveals the difference between where the organisation is today and where it wants to be tomorrow, and uncovers any obstacles preventing this potential from being achieved.