CHAPTER 3 – Requirements Change

--Originally published at Newbie Programmer

When you think that the work is done, everything is perfect, and you are enjoying your payment check, then the client calls you, because they have a great idea, and you have to help them because the customer is always right, and you have to learn that the world is In constant change, then you have to change your software product, don’t matter if the product is perfect, the change is inevitable, you will discover new problems and better ways to find the solution.

8307719578_8897a33667_z

Photo by Chris Pantazis

This technology was perfect, but the times change

Thanks to the use cases is easier to improve adding the new functions that the customer wants, to rewrite the requirements, and to make paths. The main path that is the normal scenario of the application but is better to have alternate paths to add steps to the normal scenario or provide different ways to reach the ending condition, even tough the ways are different they share the same user goal.

This chapter Is important to learn, sometimes we think that the first version of our product is perfect, but we live in times of change, and the change help us to know problems that we didn’t know we have, or better solutions, if we don’t care about changes we will fail in the future.