Skip to main content

Severity vs. Priority



Severity  vs. Priority:
Severity - “Seriousness of a Defect”
  • Showstopper – the most serious concern like a system crash, Corrupted data etc.
  • Critical – A significant concern (broken functionality without a workaround).
  • Major – A concern due to broken functionality but has a Workaround.
  • Minor – A lesser concern (broken functionality with a workaround).
  • Trivial – An insignificant concern (cosmetic).
Priority - “Importance of a Defect”

  • Urgent – Highly visible and/or stops all project efforts
  • High – Stops some project efforts (and no workaround exists)
  • Medium – Slows project efforts (but a workaround exists)
  • Low – Barely visible and/or does not affect project efforts
Severity
Priority
Severity is used to determine the IMPACT of the defect on the application.
Priority is used to signify the LEVEL OF URGENCY of fixing the defect
It’s like Effect of defect on application
It’s like how soon the defect has to be fixed.
It is defined by Software Tester
Initially defined by Tester and Finalized by Project/Tech Manager
Ranges from Show stopper to Cosmetic defect
Ranges from Urgent to Low

Defect Categorization

Category
Definition
Example
High Severity
High Priority
A bug that corrupts the database, A bug results in 404 Error etc
Lift stops at 34th floor instead of 30th floor
High Severity
Low Priority
Application crashes due to weird testing, Crashes after 4000 sessions due to improper maintenance.
Banking site expiry screen
Low Severity
High Priority
Client names and Designations are placed one for the other, Blunder spelling mistakes etc
 Switching on the fan switches the lights as well.
Low Severity
Low Priority
Grammatical errors, Alignment issues, Some cosmetic issues are examples.
 ABC.com is shown as abc.com.

Comments

Post a Comment

We appreciate your valuable Suggestions/Feedback

Popular posts from this blog

Brief Overview of RPA

Brief Overview of RPA:     §   In short, it’s a way for machines to replace human workers in regular activities done across the organization.     §   It works on both Front End & Back End applications/operations.     §   BOT provides Virtual automation agents , it acts like MIMIC HUMANS .     §   BOT ’s available in Clouds/Servers     §   BOT is nothing but a configurable software set up, works only on rule-based triggers     §   It automates Non-Value –added works     §   It is a Sub Domain of BPMS (Business Process Management Software)
2 comments
Read more

RPA Life Cycle

RPA Life Cycle: It is similar to software development life cycle with some minor changes. Technically, we called it as ‘ Life Cycle of a Bot’   Analysis:           ·     RPA Cycle begins from ‘ Analysis ’ phase.           ·     In this, Business Team & RPA Strategist/Architect identifies business process to automate           ·     After finalizing feasibility on process, implement plan of work (which includes documentation, Resources count & Time  ...) Development:          ·       Dev. Team starts working on requirements wrt to Environment.          ·       We called this phase as ‘ Bot Development ’          ·       Based on Tool selection , Limited/No coding is required ...
Post a Comment
Read more

RPA Implementation Approach

RPA Implementation Approach: 1. Tool Selection o     Based on user requirements, features available in tools, you’ve to select TOOL from mentioned above         2. Process Prioritization o     After successful section of Tool, you’ve to consolidate & prioritize the all processes in current operation. Let’s start automating lowest first and most important to next
Post a Comment
Read more