I've found that often number of features is a red herring in the quality of software. I wrote much more about that in
Document-centric vs. Workflow-centric design, where I expounded on the differences between process-centric projects and document or object centric projects.
The central idea of my root meditation is that making your features make sense together is more important, and often far more important, than the number of identifiable independent features.
A sensible task flow is important in a generic menu-driven application centered around a document object. It's more important in designing and developing software for more specific work flows. Indeed, it's often the most important factor. It's my opinion that in many cases the process should be the central theme in the design of software, and my rationale I hope is made clear in my other node.
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.