Help with a Description.
-
I'm moving on from asking for help with mere names, and am now seeking help with a description. This design task is so instinctive to me, and so seldom fixed in text, I am lost. I have an export process which culminates in a prepared data set being delivered to a target system. Currently, passing control to the delivery agent is hardcoded, as all agents are quite different. I need to wrap all agents in a shared interface and make this interop easier to extend etc. This is the best text for my design goal I have so far: "Develop a uniform method of controlling the data delivery task in any export process regardless of the data delivery method used." It's understandable to me, but something isn't quite right.
-
I'm moving on from asking for help with mere names, and am now seeking help with a description. This design task is so instinctive to me, and so seldom fixed in text, I am lost. I have an export process which culminates in a prepared data set being delivered to a target system. Currently, passing control to the delivery agent is hardcoded, as all agents are quite different. I need to wrap all agents in a shared interface and make this interop easier to extend etc. This is the best text for my design goal I have so far: "Develop a uniform method of controlling the data delivery task in any export process regardless of the data delivery method used." It's understandable to me, but something isn't quite right.
If you're expecting execs to read your description then inclusion of at least one "going forward" is obligatory, a "trending sideways" never goes astray and if you can get an "at the end of the day" in there somewhere you may find yourself being frog-marched into a corner office on the top floor.
Multi famam, conscientiam pauci verentur.(Pliny)
-
If you're expecting execs to read your description then inclusion of at least one "going forward" is obligatory, a "trending sideways" never goes astray and if you can get an "at the end of the day" in there somewhere you may find yourself being frog-marched into a corner office on the top floor.
Multi famam, conscientiam pauci verentur.(Pliny)
On the other hand some execs might prefer "I'm going to rewrite the sucker in order to reduce maintenance costs, OK"
Multi famam, conscientiam pauci verentur.(Pliny)
-
I'm moving on from asking for help with mere names, and am now seeking help with a description. This design task is so instinctive to me, and so seldom fixed in text, I am lost. I have an export process which culminates in a prepared data set being delivered to a target system. Currently, passing control to the delivery agent is hardcoded, as all agents are quite different. I need to wrap all agents in a shared interface and make this interop easier to extend etc. This is the best text for my design goal I have so far: "Develop a uniform method of controlling the data delivery task in any export process regardless of the data delivery method used." It's understandable to me, but something isn't quite right.
I'm not certain if you wanted someone to put that description into a more end-user-friendly description or if you were looking for someone to expand it to completely encapsulate the rest of what it does. I found myself a bit lost in your description of the process above, but I'll try a stab at the executive summary "dumbification": "Develop a mechanism to easily allow the addition of new export formats to the user interface." Part of that is derived from comments you made later in the string, so I hope I managed to fully tackle the issue at hand. If not, well, glean from it what you can and make the rest up :-D.