優先順序與嚴重級

標籤：des   style   io   strong   for   ar   工作   line   

Q. What’s the difference between priority and severity?

Answer:
“Priority” is associated with scheduling, and “severity” is associated with standards.
“Priority” means something is afforded or deserves prior attention; a precedence
established by order of importance (or urgency). “Severity” is the state or quality of

being severe; severe implies adherence to rigorous standards or high principles and

often suggests harshness; severe is marked by or requires strict adherence to
rigorous standards or high principles, e.g. a severe code of behavior. The words
priority and severity do come up in bug tracking. A variety of commercial, problemtracking/
management software tools are available. These tools, with the detailed
input of software test engineers, give the team complete information so developers
can understand the bug, get an idea of its ‘severity’, reproduce it and fix it. The fixes
are based on project ‘priorities’ and ‘severity’ of bugs. The ‘severity’ of a problem is

defined in accordance to the customer’s risk assessment and recorded in their
selected tracking tool. A buggy software can ‘severely’ affect schedules, which, in
turn can lead to a reassessment and renegotiation of ‘priorities’.

翻譯：

問：優先順序和嚴重性之間的區別是什嗎？

回答：“優先順序”與計劃有關，嚴重性與標準有關。“優先順序”是指需要或值得優先注意的，按重要性（或緊迫性）建立的一種先後順序。“嚴重性”指的是嚴重的狀態或性質；嚴重性意味著堅持嚴格的標準或較高的原則，常常暗指嚴厲性。嚴重性的特徵是需要嚴格遵守嚴格的標準或原則，如嚴格的管理辦法。

優先順序和嚴重性出現在缺陷追蹤中，我們可以看到各種不同的商業、缺陷追蹤或管理工具。有軟體測試工程師詳細的輸入，這些工具能給予團隊完整的資訊，因此開發人員可以理解缺陷，知道缺陷的嚴重程度，重現並修複它。這些修複缺陷的工作就是基於項目缺陷的優先順序和嚴重性。嚴重性指根據使用者的風險評估進行定義，並記錄在使用者選擇的缺陷跟蹤工具上。一個軟體漏洞會嚴重影響計劃，反過來，計劃改變也會導致優先順序的重新定義和評估。