As a contractor I am putting together a proposal for an ex-employer and could use a little help.
I got stumped for a while with the justification when I asked myself:
What is a program’s purpose? Who does it serve?
This should govern the program. The desired information properly formatted and presented should dictate what’s required. This needs to be worked backwards instead of forwards as is traditional. The process should be styled to accommodate all consumers of the process. It should also be styled in a manner well documented to allow easy navigation and maintenance by others.
There are other considerations of course but one needs a specific overriding governance that mandates all else – the mission statement. And I'm trying to come up with selling points.
This work will take me into summer and be my last effort after 40 years of serving the aero/hydro/space industries (DEA HELP certified 1985 Brea, Ca). I have a blank check and a tooling department at my disposal for this endeavor. Their parts have gone to the deepest of oceans and are one of the most FWD items of Orion. I'd really like to do them right.
I'd like to hear what others use as their "Mission Statement". What governs your style of programming?
I'll be the first with "Get the boss off my "