Learn English – Expression for an ‘end-to-end product development process’

There are some phases in Software Developing.

1. Pre-alpha refers to everything that is prior to testing.
2. Alpha is when the product is ready to go through the first phase of testing. It's not exactly true that Alpha means only internal testing, or at least this mainly refers to proprietary software. In Open Source softwares, Alpha versions might be publicly available. There might be several Alpha versions.
3. Beta is the second phase in testing. Its focus is not to implement features anymore, (it is called feature complete), but rather to improve its user-friendliness. Everything is taken care by beta-testers that are "usually customers or prospective customers of the organization that develops the software, willing to test the software without charge, often receiving the final software free of charge or for a reduced price."

About other names being used, here's some info:

Other Greek letters, such as gamma and delta, are sometimes used to indicate versions that are substantially complete, but still undergoing testing, with omega or zenith used to indicate final testing versions that are believed to be relatively bug-free, ready for production.

You can read more about this here.

About the origins of this usage, I found a page written by Jeff Atwood, where he writes:

But where did these terms originate? There's an uncited Wikipedia section that claims the alpha and beta monikers came, as did so many other things, from the golden days of IBM:

The term beta test comes from an IBM hardware product test convention, dating back to punched card tabulating and sorting machines. Hardware first went through an alpha test for preliminary functionality and small scale manufacturing feasibility. Then came a beta test, by people or groups other than the developers, to verify that the hardware correctly performed the functions it was supposed to, and that it could be manufactured at scales necessary for the market. And finally, a c test to verify final safety. With the advent of programmable computers and the first shareable software programs, IBM used the same terminology for testing software. As other companies began developing software for their own use, and for distribution to others, the terminology stuck -- and is now part of our common vocabulary.

In common usage, infrastructure often is used unqualified to refer to good physical conditions in a community (as, for example, "Our town has the infrastructure to support your robot factory!"), although it implies little or nothing about tax, economic, and labor conditions. Of course one can also say "Their infrastructure is awful!"; that is, "good" is not an inherent quality of infrastructure.

Note, infrastructure is "The basic facilities, services and installations needed for the functioning of a community or society."

Regarding linguee.com, their "About" page clearly says, "there is no other technology anywhere else in the world that compares with Linguee", so obviously you should keep using it. :) They also assert that the translations they provide (which, if I understand correctly, are in this case English to German) are human-made (or at least human-moderated). In comparing the English and German, it seems that the connotation you suggested for the German word (i.e. "conditions necessary for a business idea to work out") do not hold up in these translations; for example, "worst imaginable conditions" going to "denkbar schlechten Rahmenbedingungen".