Defect Management

-
Defect management is a process to identify the defect of the software. The Development team needs a defect management tool so that they can find defect easily and at a very early stage of process because as soon as the defect is detected the cost of fixing it will be low, but if the defect is detected in the later stage of development process then the cost of fixing that defect will be more. Defect management will work as a backbone to developing a team in finding the defect in the early stage in a very easy way. 

Defect management process:  

 Identification:​ 
This will be the first step to identify the defect in the process this can be done by the testing team and sometimes the customer can also tell you about the defect.  
Categorization:​ ​
After the defect is registered, then it passes to the desired person then checks it and categorize it that what type of defect it is and then move to the next step.  
Prioritization:​ 
According to the type of defect or severity of the defect. These defects are a set of priorities for fixing it accordingly. It can handle through a formal channel or an individual team member who is working on defect can set its own priorities for fixing defects.  
Assignment:​  
As soon as the priorities are decided by a formal channel defect is assigned to a developer to fix it.  
Resolution:​ 
The developer fixes the defect and places it in the same place from where it was identified.  
Verification:​ 
As soon as the defect is fixed, the tester team verifies that defect is actually fixing and working in the smoothest way or not.  
Closure:​  
Once it is fixed and resolved it is marked as a closed case.  
Management Reporting:​ 
This provided at regular intervals which helps management to know which work is done and which work is going on and when it will be done.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more