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.
-
'Develop an abstraction layer to control the export processes regardless of the data delivery method used' ...is that good? My organ grinder is rusty...haven't used it in a while :)
I'm trying to exclude technical terms in the 'executive summary' type intro.
-
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.
Develop a single export method that allows any data delivery method to be used?
.\\axxx
-
Develop a single export method that allows any data delivery method to be used?
.\\axxx
It already allows any delivery mechanism to be used, but the UI has to be modified, so to speak: to add a new one to the 'switch' statement, and add code to parse the new delivery log etc.
-
It already allows any delivery mechanism to be used, but the UI has to be modified, so to speak: to add a new one to the 'switch' statement, and add code to parse the new delivery log etc.
err... I think that was help for your description...
Knowledge is knowing that the tomato is a fruit. Wisdom is not putting it in fruit salad!! Booger Mobile - Camp Quality esCarpade 2010
-
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.
Can everyone who is still learning their trade please take a moment to watch and recognise just how important it is to name, describe and document what you are doing. Anyone can code, but it's a special person who takes the time to code in a way that others can understand, and then document what they have done in order to help themselves and others down the line. You impress me, Mr Kelly. :thumbsup:
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
-
It already allows any delivery mechanism to be used, but the UI has to be modified, so to speak: to add a new one to the 'switch' statement, and add code to parse the new delivery log etc.
Brady Kelly wrote:
but the UI has to be modified...
Ah - well then, I suggest something along the lines of: "Synergiate a holistic implementology encapsulating a smoothifacatory front-end approach to data throughput wrt delivery preparatizasion." Dey luv dat stuff. :)
-
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.
-
Can everyone who is still learning their trade please take a moment to watch and recognise just how important it is to name, describe and document what you are doing. Anyone can code, but it's a special person who takes the time to code in a way that others can understand, and then document what they have done in order to help themselves and others down the line. You impress me, Mr Kelly. :thumbsup:
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
Chris Maunder wrote:
You impress me, Mr Kelly.
So what does he get? A platinum membership for free.
-
Can everyone who is still learning their trade please take a moment to watch and recognise just how important it is to name, describe and document what you are doing. Anyone can code, but it's a special person who takes the time to code in a way that others can understand, and then document what they have done in order to help themselves and others down the line. You impress me, Mr Kelly. :thumbsup:
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
Chris Maunder wrote:
You impress me, Mr Kelly.
Thank you. I hope my word choices also impressed the marker of the copyright law exam I wrote yesterday, and of the trademark law exam I write tomorrow.
-
err... I think that was help for your description...
Knowledge is knowing that the tomato is a fruit. Wisdom is not putting it in fruit salad!! Booger Mobile - Camp Quality esCarpade 2010
I know, but I was pointing out why the 'help' description, and my document, needs more detail.
-
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 think it needs the word "extensible". I think everything after "process" in your original is probably excess for summary level. If you want something closer to Execuspeak: "Develop a uniform, extensible, single-point-of-entry method of controlling delivery options in the data export process." Might be a little over the top. If you want it a little saner: "Develop an extensible method of controlling delivery options in the data export process." Which I kind of like.
_____________________________ Those who study history are doomed to watch others repeat it. -Scott M.
-
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.
A management summary? You've got it the wrong way around, and you're using techie lingo. Try { Ensure that various data-delivery systems work co-operatively in a _ controlled environment by implementing an overarching management system. } When talking to God, use the language of God -- shove a burning bush up his arse.
I wanna be a eunuchs developer! Pass me a bread knife!
-
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.
It does seem wordy. How about: Standardize data delivery for any export process regardless of delivery method.
-
Brady Kelly wrote:
but the UI has to be modified...
Ah - well then, I suggest something along the lines of: "Synergiate a holistic implementology encapsulating a smoothifacatory front-end approach to data throughput wrt delivery preparatizasion." Dey luv dat stuff. :)
-
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.
As one of the replies mentioned a factory and this bit sounds like one of the factory patterns (not certain TBH).
Brady Kelly wrote:
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.
{reaches for GOF, Design Patterns} *coughs* {too much dust} Abstract Factory: Provide an interface for creating families of related or dependent objects without specifying their concrete classes. Factory Method: Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses. ... depending on your implementation, this *could* be an abstract factory. In which case: An Abstract Factory to handle export data set from (details). ... but I may be oversimplifying.
"If you reward everyone, there will not be enough to go around, so you offer a reward to one in order to encourage everyone." Mei Yaochen in the 'Doing Battle' section of Sun Tzu's: Art of War. .
-
Can everyone who is still learning their trade please take a moment to watch and recognise just how important it is to name, describe and document what you are doing. Anyone can code, but it's a special person who takes the time to code in a way that others can understand, and then document what they have done in order to help themselves and others down the line. You impress me, Mr Kelly. :thumbsup:
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
I believe that's called craftmanship, an all too rare quality in our business at times.
Software Zen:
delete this; -
Can everyone who is still learning their trade please take a moment to watch and recognise just how important it is to name, describe and document what you are doing. Anyone can code, but it's a special person who takes the time to code in a way that others can understand, and then document what they have done in order to help themselves and others down the line. You impress me, Mr Kelly. :thumbsup:
cheers, Chris Maunder The Code Project Co-founder Microsoft C++ MVP
Amen, brother!
-
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.
"Control the data delivery task through a new, cohesive interface and [have it] deliver data using adapters." Then you could go into detail. "[have it]" may make it too wordy, but it seems to make sense with and without it. (On re-reading, maybe it is better without "have it" since the interface is not performing the delivery) You could also go with something more creative like.... "Control. Deliver. In Uniform." ..but that might be a little too creative :)
Erik Westermann - ArtOfBabel.com - Systems Integration Magazine
Contact Erik for consulting, development, or content creation at +1 416-809-1453 or via wWorkflow.net