20:30 Mar 2, 2002 |
German to English translations [PRO] Tech/Engineering - Computers: Software / software | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Ulrike Lieder (X) Local time: 11:45 | ||||||
Grading comment
|
Summary of answers provided | ||||
---|---|---|---|---|
4 +6 | change/update history |
| ||
4 +1 | back-updated documentation ... |
| ||
4 | emphasising the historical aspects |
| ||
4 | to catalogue |
|
emphasising the historical aspects Explanation: historisiend does not mean recording history - it means doing a documentation does is strongly led by the historical aspects |
| |
Login to enter a peer comment (or grade) |
to catalogue Explanation: short and sweet |
| |
Login to enter a peer comment (or grade) |
change/update history Explanation: This is a somewhat liberal take on your sentence, but the German is truly awful. As I understand your sentence, it refers to logging all changes/updates to the code in order to document them (which is good programming practice). "Change history" is a term frequently found in programming environments. My suggestion would be s.th. along the lines of change/update history to comply with all documentation requirements (I'd also use requirements rather than obligations for ...pflichten) HTH |
| |
Grading comment
| ||