This back and forth process of updating first one object, then a different one, then yet another, is typical of the NAV development process much of the time. Exceptions are those cases where either the task is so simple we think of everything the first time through, or the cases where we create a completely documented, full-featured design before any development starts (but nobody thinks of everything, there are always changes; our challenge is to keep the changes under control).
An advantage to the more flexible approach we are following is that it allows us to view (and share with others) intermediate versions of the application as it is developed. Design issues can be addressed as they come up and overlooked features that can be considered midstream. Two downsides are the very real possibility of scope creep (the project growing uncontrollably) and poorly organized code. Scope creep can be controlled by good project management. If the first pass through results in poorly organized code, then a thoughtful refactoring is appropriate, cleaning up the code while retaining the design.