I like to start by simply writing down what a user will need to do and in what order.
I start with a list of everything that will appear on a given screen, basically a screenshot in plain text. This will tell you what has to happen before the screen loads (pull customer info, pull past transactions etc).
Next I make a list of all the options(actions) the user will have (write sale to db, conduct search etc).
At this point I can start figuring out the basic flow of the program and what functions I will need. Notice that through all of this I have not done anything technical. Now I should have enough info to start creating a technical spec for any language I need to work with.
Sometimes this will seem like an over simplified approach but it can expose some basic design issues/assumptions that I might not have thought of right away.
mr greywolf
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.