There's nothing I could add regarding the technical aspects of your project, beyond the excellent advice above.
On the other hand, there may be a few points to draw out concerning career advancement.
Wheterh you are in an organization or consulting, it can be very advatageous if the people for whom you're designing feel confident and comfortable, not just when all ends well, but throughout the whole process. You want your superiors/clients to say "He had it under control the whole time, we were never exposed to risks."
That means using the user-input / planning / sign-off / validation steps mentioned in other posts as, in fact, public banners advertising your project management competence. Get user input by distributing written invitations, with copies to management. Distribute your plan, with copies to management. Confirm the sign-off in writing, with copies to management. Etc. You might even start out by publishing your intended steps so people know what to expect.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||