12:12 Feb 10, 2004 |
French to English translations [PRO] Tech/Engineering - Computers: Software | |||||||
---|---|---|---|---|---|---|---|
|
| ||||||
| Selected response from: Charlie Bavington Local time: 17:09 | ||||||
Grading comment
|
Summary of answers provided | ||||
---|---|---|---|---|
4 +2 | business critical errors |
| ||
4 +1 | critical bugs |
| ||
5 | bugs |
| ||
4 | (all) jamming/blocking anomalies |
| ||
5 -1 | fatal errors |
| ||
1 | errors that cause the computer to hang up |
|
errors that cause the computer to hang up Explanation: ...would be my interpretation (though not based on any specialist knowledge of this field) as for 'base [de données] gelée / ouverte', they must be talking about 'freezing' and 'opening' databases of errors encountered; presumably the former is used only in development, while the latter is maintained once the system is up and running. Hope this helps to give you a few leads in the right direction! |
| |
Login to enter a peer comment (or grade) |
(all) jamming/blocking anomalies Explanation: depending on context. Computing & IT French |
| |
Login to enter a peer comment (or grade) |
fatal errors Explanation: <<fatal error - An error that causes the system or application program to crash - that is, to fail abruptly with no hope of recovery>> [Microsoft Press Computer Dictionary] Functional Handover is therefore now complete, the Functional Handover punch list closed and the Maintenance punch list opened. |
| |
Login to enter a peer comment (or grade) |
critical bugs Explanation: I come across this term regularly, and this is how I usually translate it. |
| |
Login to enter a peer comment (or grade) |
bugs Explanation: "Anomalies bloquantes" is the sort of phrase someone who doesn't understand software or isn't famliar with the terminology uses (and who charges by the word or is trying to impress his idiot superiors - see Dilbert). To use any other word or phrase (fatal error, anomalies that cause hangs, ...) imply that *only* fatal errors were fixed while the other problems detected (crossed-data, erroneous file pointers, etc.) that don't hang the system were not fixed. |
| |
Login to enter a peer comment (or grade) |
business critical errors Explanation: We're talking about Functional Acceptance testing here, i.e does the system/software perform the *business* functionality that the users require. An "anomalie bloquant" in this context, which is not a particularly IT term, really, means an error in the system which prevents the business user from doing their job properly. It does NOT mean that the system crashes, hangs, or starts spewing out steam from the CPU ! What it means is that the system does not do what it is supposed to, and, moreover, there is no way to get round the problem (e.g. by using a different and more convulted sequence of transactions). Hence the error is "bloquant", and the users cannot do their job. You may use whatever term you wish to describe this situation - the above is my preferred term and I usually find that people understand what it means :-) ! -------------------------------------------------- Note added at 1 hr 7 mins (2004-02-10 13:19:21 GMT) -------------------------------------------------- For the second part: \"Functional acceptance testing is now complete, and the (acceptance testing) error log is now closed (or frozen if you prefer). A maintenance (or support) error log has now been opened. i.e. any future errors noticed will be recorded under support and maintenance, not accpetance testing. |
| |
Grading comment
| ||