Re: Application Design "Process"

Tech-Archive recommends: Fix windows errors by optimizing your registry

<Paul Bruneau> wrote in message
news:vo5481p568puaetkod16jsnd1jfv2fuv40@xxxxxxxxxx
> Good Morning everyone,
>
> I'm having a dandy time learning VB, and have finished tweaking the hell\
> out of the old "Hello World" beginners program.
> Now I am approaching something far more significant, I have a question
> that will save bundles of time. Why reinvent the wheel, so to speak.
>
> Is there a common "step-process" to building an application to satisfy the
> "Wish List" someone else may have?
>
> Clearly conversation happens, but I have spent my life among senior
> managers
> and know that these "Wish List" requirements will change. The only way to
> avoid
> headaches would be to have prospective customers to sign-off on elements
> of
> an application as they evolve.
>
> I have found, borrowed, liberated, and even begged learning books on
> programming but have yet to find anything suggesting the order in which
> stuff
> needs to be addressed when producing an application for someone else.
>
> How does an independent programmer document this evolution?
>

I'm not clear what you are asking. Are you asking about the fundamental
process of designing an application architecture? Or are you asking about
how to deal with clients who keep changing what they want? Of course the two
are related - good architecture, which consists largely of keeping the
various parts of the program as independent of each other as possible, will
make it a lot easier to make changes when the Client from Hades requests yet
another modification!


--
Peter Aitken

Remove the crap from my email address before using.


.