Application name for project maintenance tasks implementation

Question

There was a discussion (windows service or task scheduler) about maintaining projects. Personally I prefer a console application on task scheduler. I wonder what is the best thing to call such applications? The last team I took part in used the title JobMachine, but is there a more appropriate name for such an application?

Answer 1

I'm not aware of any conventions for what you call an application or component; but here's some food for thought...

• Give it a name that makes sense to the people who will be using it - a bit like the user centered design principle of always talking in the users language.
• Descriptive names are good (think self documenting), although you don't want something that's too long if you can help it.

If the component is truly difficult to quantify into a name that matches its purpose (such as if it's purpose is complicated and not easily explained) then you still have some options:

• Give it an "identity" via a unique (and completely meaningless) name - preferably something that won't make it's users cringe: "Fred", "TheObliterator" - I'm not saying these examples are't cringe material:)
• A name based on a metaphor related to it's purpose; for example, if the program deals with moving files have a think about (interesting) things related to moving, i.e.: Scotty and Teleportation a-la Star Trek.
• A name based on an acronym: TASTE (Terrific Application Scheduling TEchnology), or, BLOAT (Bi-directional Logarithmic Object and Application Transponder).

At the end of the day the name must be cool: either because it simply states what the app's all about (a sort of understated coolness) or sheer unbridled in-your-face coolness.