I am just about to start designing a new module for our integration service, and it occurs to me that the hardest part of designing anything is actually starting.
I find that once I get going, it all seems to flow, but any interruption is usually fatal to the current work.
It is these interruptions that lead to aspects of the design being missed completely, or misunderstood - which will inevitably come back to get you in QA...
So my advice to you all is to make sure you can do significant sections of the design with minimum interruptions.
My preferred approach is to start with a template document that contains the various sections that need completing.
Once I have this, I will work on a section at a time. If any graphics are required in any of the sections, such as process flows, they should be left and completed later.
I always do the process flows and graphical work after I have completed the bulk of the design to make sure everything ties up nicely.
It's easy to change text to cater for modifications to the design, but going away and updating a raft of process flows is annoyingly laborious...
For example, I have completed the bulk of the document now for the design of the new module, but have yet to complete the process flows.
Anyway, back to the salt mines...
No comments:
Post a Comment