This is a term I recognize from my undergraduate days, and it doesn't come from computers. It's a term from behavioristic psychology. It's used to describe the process of converting a general description of a behavior which may include reference to an internal state of an organism (e.g. an emotion) to a specific description of actions, or operations, which the organism perfoms that give evidence of its internal state ("The rat is scared of getting shocked" becomes "the rat resisted being pushed off the platform onto the electrically wired grid to the point of hanging by its claws to the plunger which was forcing it off the platform"). When you write code, you are operationalizing a technical specification. So, it's accurate, but we didn't need to import new terms from psychobabble, we have enough babble of our own :laugh:

Brilliant, thank you both.

The links look very similar, but It never ends up displaying the ad to verify visually.

HA!!! :laugh:

The class could have a ServiceName property (or public readonly string) that the installer can use. When instantiating each service the underlying property could be set appropriately. I'm at the point now where I have a database table containing service configuration; the EXE reads it to find out what services it should run, loads the DLLs, instantiates the appropriate classes with their names and descriptions and such, and runs them. To create a new service I need only derive a class with the method it should execute, add a row to the configuration, and uninstall/reinstall the EXE. Each service is in its own DLL; the EXE needn't be recompiled.

Thanks!