Have you described the alternate environment in which your Perl programs will live? Is it going to build on top of your existing infrastructure are are you requesting a bunch of UNIX boxes? The boss needs to know that one 'cos he isn't going to buy new hardware for the hell of it.

Have you listed the set of software that you would want to deploy? Are we talking Apache/mod_perl or are you sticking with IIS? If you are trying something new, can you assure him that the software can be administered?

Have you listed the positive points that your idea has over the alternate idea? Having done most of it is a plus point but is it prepared to the level where someone else can take over from you during the maintenance phase.

In short, you need a business case and a strategy.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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