It's a good question ... and I'm not sure I know a book that really helps you with this stage of your professional development.
A junior programmer can write one module to specifications, a software architect can design a whole large application, but this is intermediate: the design stage of a medium-sized project.
One way to look at this is, how do you know when you are ready to start actually coding. I think a complete project plan should
1) list milestones
2) Describe them in enough details that you can make a time estimate for each, to within a factor of two
3) identify the major risks for the project ... normally you perform firs the task that is most likely to fail.
By coincidence, I've just written a message board. (Like you, I had good reasons for not using something off the shelf.) I'd be happy to send you a copy of my project plan - email me at chrishmorris at uk2 dot net.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||