You searched for: slight (Italienska - Engelska)

perhaps there is a slight resemblance in their appearances.
perhaps there is a slight resemblance in their appearances.

over the last 35 years the sun has shown a slight cooling trend.
over the last 35 years the sun has shown a slight cooling trend.

there was a slight problem with the drainage in the shower, it was slow.
there was a slight problem with the drainage in the shower, it was slow.

the only slight downside is the street noise but you are in the centre of a city.
the only slight downside is the street noise but you are in the centre of a city.

and it’s just a matter of a slight alteration in our perception to see it.
and it’s just a matter of a slight alteration in our perception to see it.

in the last 35 years of global warming, the sun has shown a slight cooling trend.
in the last 35 years of global warming, the sun has shown a slight cooling trend.

but there is a slight increase in wheat-corn-barley, accompanied with a dramatic decrease in less common crops.
but there is a slight increase in wheat-corn-barley, accompanied with a dramatic decrease in less common crops.

a ottobre, poco prima di compiere sei anni, ebbi l’opportunità di vedere due dei maestri in azione ad hatcher: aaron slight e scott doohan.
in october 1991, just before my sixth birthday, i had the opportunity to see two of the masters in action at hatcher’s: aaron slight and scott doohan.

g1 insignificant / irrilevante an error would cause operational inconvenience, additional future effort for a system update, no chance of injury, and/or minor cost. g2 slight / lieve an error would cause secondary operational requirement (e.g., a goal) degradation, a minor but required system update, chance of minor injury, and/or marginal cost. g3 serius / serio an error would cause primary operational requirement degradation, a major system update, chance of moderate/serious injury, and/or critical cost. g4 deadly / mortale an error would cause operational failure, chance of serious injury or death, extreme cost and/or loss of any operational critical function. categoria descrizione p1 rare / raro the requirements, design, and implementation are simple and mature; and the requirements have little to no bearing on overall system accuracy and performance, are well defined, allocatable, measurable, and testable. p2 not very frequent / poco frequente the requirements, design, and/or implementation are only somewhat complex, with few interfaces and overall size; and the requirements indicate relaxed, but not negligible, accuracy and precision, have some bearing upon overall system performance but are well defined, allocatable, measurable, and testable. p3 frequent / frequente the requirements, design, or implementation are moderately coupled and complex, have clearly defined interfaces, and moderately large overall size; or the requirements indicate moderate accuracy and precision, or moderate stress conditions, and have a definite bearing on overall system performance or the requirements are not well documented or may be difficult to allocate, measure, or test. p4 inevitable / inevitabile the requirements, design, or implementation are tightly coupled, complex, have numerous interfaces, and a large overall size; or the requirements indicate extreme accuracy and precision, or extreme stress conditions, and definitely will effect overall system performance; or the requirements are ambiguous or unstable or cannot be easily allocated, measured, or tested.
uni en iso 17025