Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

Comment on

( #3333=superdoc: print w/ replies, xml ) Need Help??
I mostly write unattended jobs that shunt information around a relational database or two. For systems of this type, I generally start with a data model - either a new one, or I sketch out the existing structure. When I have a suitable data model, the processing steps required generally become obvious.

After that, it is a case of looking for areas of commonality in the process, and factoring these out as subroutines, utility modules and classes.

I think design becomes more of an issue with interactive systems, because of the potentially large number of states and transitions. I still start with the data model, but I might sketch state transition or process flow diagrams. Then I start coding, pretty much the way you described, blocking out the program structure first, and filling in the subroutines and methods later.

In my experience, software design doesn't change when a team is involved. But the practice of coding is severely impacted. When you get several people working on related code, individual productivity takes a hit, and you have to get more organised about testing, source code management, release control etc.


In reply to Re: Software design -- The confussion of buzzwords by sandfly
in thread Software design -- The confussion of buzzwords by zzspectrez

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • 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, 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
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.
  • Log In?
    Username:
    Password:

    What's my password?
    Create A New User
    Chatterbox?
    and the web crawler heard nothing...

    How do I use this? | Other CB clients
    Other Users?
    Others having an uproarious good time at the Monastery: (12)
    As of 2015-07-08 08:52 GMT
    Sections?
    Information?
    Find Nodes?
    Leftovers?
      Voting Booth?

      The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









      Results (98 votes), past polls