Greetings, I have set out to work on a comprehensive security playbook manager for my home network.
I got started by working on OO automata code using Markov chains to look through bind logs for domain name that were clearly generated by an algorithm (a way to stretch my new found muscles before tackling harder problems
such as the client server idea I have for collecting logs all over the network).

I used module-starter to build the module skeleton. I am almost done with that module but I have no idea how I should package it with everything else.

Should I create a new module named something like "Sec::reporting::tools::automata" and put everything in there but then what will I do if I need to create another submodule named "Sec::whatever::somethingelse"?

Should I just move things around, create folders and update the MANIFEST file accordingly? I dont know whether my folder structure should show any kind of hierarchy between more important modules (such as the one that will orchestrate log normalization then reporting) and more specialized ones (such as the one I'm almost done working on).

My goal is to, once I have the infrastructure laid down upload it to CPAN but I would like it to be as organized and easy to use as possible

Thank you for your time, I eagerly await any advice from more advanced members of this community.

In reply to Module Architecture by QuillMeantTen

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!
  • 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:
    & &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.