What the Users Want

In software or systems analysis, there is a critical step which is called requirements analysis. It is a step that pertains to determining and confirming the needs, wants and the constraints of the whole project. It is essential to be clear and be detailed on this as this will dictate the goals of the project.

It is similar to building a house, the architect needs to solicit the needs and wants of the client and the restrictions to be considered in the design.

the classic humor on systems analysis

In finding an ICT solution for the teachers, it is a semblance of the same situation.

As an ICT Trainer when a request to design a solution comes from a sponsor, ahead of time I draw some courses that I perceive may be state-of-the-art or progressive in concept for my client. I scan what is around and underscore what may be considered as currently relevant. This is a very cautious preparation.

But after careful coordination with the actual course managers, these are the persons in-charge of the recipients of the training, my initial perceptions are not all correct. While it helps to exhibit I have prepared for my client, what is significant is the discussion with the course managers, asking the right questions and extracting their real requirements.

Along the way, I devise simple techniques to further collect data about the client or training participants. In circumspect, the reality more than often times, the users would have simpler requirements.