Kamis, 19 Juni 2014

Requirement is There to be Changed

For a software engineer, like me, required to develop application based on the requirement. Every project comes with a requirement document so that the developed application could become the solution of the designated problem. Unfortunately, this was not the ideal world. In my experience, there was not perfect requirement. Every project I have ever finished, the requirement always changed at least once. For us, engineers, we upset when the requirement changed. It is a very tedious or annoying task when we need to change our code design from the very beginning. So, how do we do this?

In my opinion, the most responsible person of this requirement thing is of course the person that do the requirement analysis, in my experience, is the project officer. Even though, there is no 100% requirement analysis, the project officer need to give their full effort to get as near as 100%. 90% is already good in small-scale project. The larger the project scale, the harder to analyze the requirement. The more complete the requirement, the happier the engineers. The happier the engineers, the solution is obviously better.

For developers that work with people that capable of analyzing the requirement thoroughly, you are damn lucky. Obviously, this kind of people is scarce. I think, it is easier to find great engineers than great analyst. If the great developer is a tiny fraction of all developers, great analyst is tiny fraction of the great engineers. This is because the nature of analyst. If someone want to be a great analyst, they need to have the experience of developing an application. so that they know everything it needs to develop an application into a solution.

Me, as an engineer, has small portion on requirement analysis. The farthest I could do is to take the initiative to ask about the application A LOT and get used to requirement change. It is really annoying to change the requirement in the middle of a project, but it is inevitable. For me, it is very annoying to change my code design, but it is more annoying if my code is not becoming the solution of the problem. I cannot imagine if my coded application cannot help people to achieve more in their life. We, engineers, make solutions, not applications.  Engineer should focus on the solution. So, deal with it. :D. 

Tidak ada komentar:

Posting Komentar