Re: Tools used to design application before the coding stage?
- From: "ernobe" <ernobe@xxxxxxxxx>
- Date: 28 Dec 2006 10:07:31 -0800
On Dec 27, 3:36 am, "Noozer" <dont.s...@xxxxxxx> wrote:
I'm an old school programmer. Most of my applications are designed as I
coded them. Needless to say, this approach just does not work in this day
and age.
Currently, before I start an application I jot down notes and layouts on
pads of paper, or in a text file on my PC. I go through several drafts of
task flow and application operation to develop a user interface. This leads
to many false starts, and a lot of disorganization.
Before coding even begins, what tools are being used these days to document
an application, the objects that it uses, program flow and user interface
development?
much has changed. Icons' innovative use of the success-failureFrom my perspective as an amateur Icon programmer, I think that nothing
mechanism, which allows processes to succeed with a null value, gives
it the flexibility often associated with assembly language. The bottom
line is that good documentation begins with knowing what your processes
are doing from the very beginning, and this can only be achieved at the
assembly level. Otherwise, documentation will just succeed at
describing what something is supposed to be doing, not at perceiving
what is actually happening. Take a look at Icon at:
www.cs.arizona.edu/icon/
.
- Prev by Date: Re: question about programming
- Next by Date: Re: question about programming
- Previous by thread: Re: Tools used to design application before the coding stage?
- Next by thread: question about programming
- Index(es):
Relevant Pages
|
Loading