English translation: to factor out / factoring out
Login or register (free and only takes a few minutes) to participate in this question.
You will also have access to many other tools and opportunities designed for those who have language-related jobs (or are passionate about them). Participation is free and the site has a strict confidentiality policy.
22:01 Nov 12, 2011
German to English translations [PRO] Tech/Engineering - IT (Information Technology)
German term or phrase:Ausfakturieren / Ausfakturierung
I have come across this term and can only guess what it may mean. I am not sure if it is IT-specific or if it can be used in other areas, and if so, whether the meaning/translation would still be the same?
The text I am translating is on the integration of components used in a specific project into future projects, i.e. their potential reusability.
An example of a sentence with "ausfakturieren":
"Der Entwickler ermittelt den Aufwand für die Maßnahmen, die ergriffen werden müssen, um die Voraussetzungen zu schaffen, damit die Komponente ausfakturiert werden kann."
Could it be analogue to "sorting" (as the components needs to be cleared of any project-specific parts and be suitable to be used in other projects?
Explanation: I strongly suspect that "ausfakturiert" was borrowed from English computer jargon, and is not a native German term. Consequently it would be most natural to let it pass back into English as "factored out".
Wikipedia defines abstraction as a practice in computer science, whereby details are factored out (i.e., abstracted away):
"Abstraction (computer science), a mechanism and practice to reduce and factor out details so that one can focus on a few concepts at a time"
In object-oriented programming, factoring out refers to the process of moving from detailed requirements to a well-abstracted set of components.
I would translate your full passage as follows:
"The developer determines the level of effort for the measures which must be taken to establish the requirements, so that the components may be factored out."
In other words, the developer is expected to estimate how much effort is involved in understanding the functional requirements so well, that those requirements can then form the basis for a properly abstracted software design.
-------------------------------------------------- Note added at 13 days (2011-11-26 04:08:49 GMT) Post-grading --------------------------------------------------
I hope this note does not come too late. The client's definition reinforces what I meant to say in this answer. So abstracted would still apply as an explanatory term. Looking back at Dr. Darakjian's peer comment, I see that his idea was "factored out (abstracted)". That's pretty good. If you want something more concise, either "factored out" or "abstracted" will convey the same idea.
I am not positive... on "abstracted". Just a thought. It may very well be that from the CS point of view, it is "factored out"...
Automatic update in 00:
Answers
3 hrs confidence: peer agreement (net): +2
to factor out / factoring out
Explanation: I strongly suspect that "ausfakturiert" was borrowed from English computer jargon, and is not a native German term. Consequently it would be most natural to let it pass back into English as "factored out".
Wikipedia defines abstraction as a practice in computer science, whereby details are factored out (i.e., abstracted away):
"Abstraction (computer science), a mechanism and practice to reduce and factor out details so that one can focus on a few concepts at a time"
In object-oriented programming, factoring out refers to the process of moving from detailed requirements to a well-abstracted set of components.
I would translate your full passage as follows:
"The developer determines the level of effort for the measures which must be taken to establish the requirements, so that the components may be factored out."
In other words, the developer is expected to estimate how much effort is involved in understanding the functional requirements so well, that those requirements can then form the basis for a properly abstracted software design.
-------------------------------------------------- Note added at 13 days (2011-11-26 04:08:49 GMT) Post-grading --------------------------------------------------
I hope this note does not come too late. The client's definition reinforces what I meant to say in this answer. So abstracted would still apply as an explanatory term. Looking back at Dr. Darakjian's peer comment, I see that his idea was "factored out (abstracted)". That's pretty good. If you want something more concise, either "factored out" or "abstracted" will convey the same idea.
Example sentence(s):
In object-oriented programming, reusable general classes are factored out from situation-specific requirements.
de>en Local time: 04:42 Specializes in field Native speaker of: English PRO pts in category: 12
Grading comment
Selected automatically based on peer agreement.
Notes to answerer
Asker: "dies bedeutet sinngemäß, dass Systemteile, die projektspezifisch entwickelt worden sind, generalisiert werden und in die „Plattform“ (=Baukasten, also Framework) übernommen werden, damit sie dort dann zukünftig auch für andere Projekte genutzt werden können."
Does the term "abstracted" still apply here? And if so, does it still have to be in brackets?
Asker: P.s. The definition was provided by the client.
The translation workplace 
peer agreement (net): +2
