Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??


in my current project (not a web app, system programming and automation), we use the following way to develop, test and do the roll out.

CVS: will soon be replaced by Subversion

UML: we chose the Rational ones from IBM, and TopCased as an Eclipse plug in for the developers who don't have licenses for the Rational stuff (only for documenting).

Eclipse (from YOXOS) with EPIC for Perl support, an integrated CVS (soon SVN) client (is as easy as tortoise), perltidy for formatting, and a lot of eclipse templates. It wasn't easy for me to switch from emacs (my favorite editor) to eclipse, but using the same platform independent tool for all developers is a big pro in my eyes. We just evaluate Jazz which looks very interesting.

Coding Standards: we use a subset of "Perl Best Practices" (those parts which make sense) and several enhancements

Perl and add ons: to get a standard environment, we use pkgsrc for Perl, libraries and some applications

Packaging: we use RPM for Linux, InstallP for AIX (and soon MSI for windows) and developed a little tool who does the packaging for us. The roll out is done in several stages, from develop (2 servers) to test (8 servers), to acceptance/integration test and then into production (about 200 server). We use a lot of automatic tests for step one and two.

Perl-Modules: lot's of them, but a list of them might not be helpful for you :-)

Bugzilla: for Bugtracking, and the eclipse plug in mylin to use most of its features from eclipse.

Update: I forgot bugzilla, and fixed some spelling errors...

Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8."

In reply to Re: On the scaleability of Perl Development Practices by strat
in thread On the scaleability of Perl Development Practices by jdrago_999

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!
  • 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, 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?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others scrutinizing the Monastery: (3)
    As of 2018-05-25 23:16 GMT
    Find Nodes?
      Voting Booth?