Register now or log in to join your professional community.
Key Performance Indicators (KPIs) are a great tool for software development and quality management. By closely monitoring relevant KPIs, the managers can ensure high productivity and business performance.
1- Defects management: During software production, defects management procedures and Defects removal efficiency (DRE) should be measured to achieve a quality software production.
2- Bugs management: During and after implementation of software, bugs removal efficiency should be measured. This is easily measured by the percentage of bugs reported by clients/Users
3-Quality management: Measuring of Quality Assurance (QA) Personnel as a % of the Total Number of Application Developers and Measuring of Test Coverage % of Software Specifications
4-customer demand management: In order to achieve quality software production, percentage measurement of Users Requested features should be put in place.
5-workforce Time Allocation: There are two KPIs to workforce time allocation,1- measuring time of time ration design to development2- and measuring of average man-hour per software lines of code.
6-Workforce Effectiveness: Measuring of Time Spent Re-Developing Applications due to Source Code Loss, as a % of Total Time Spent on Applications.
1) Process: Testing is a process rather that a single activity - there are a serious activities involved.
2) All life cycle activities: Process that takes place throughout the SDLC.
3) Both static and dynamic - Software code is executed do demonstrate the results of running tests (often called dynamic testing) we can also test and find defects without executing code. This is called static testing.
4) Planning: Activities tatke place before and after test execution. We need to manage the testing activities.
5) Preparation: We need to choose what esting we'll do, by selecting test conditions and designing test cases.
6) Evaluation; As well as executing the tests, we must check the results and evaluate the software under test and the completion criteria, which help us decide whether we have finished testing and whether the software product has passed the tests.
7) Demonstrate that software products are fit for purpose: One way judging the quality of a product is by how fit it is for its purpose.
8) Detect defects: Finding the defects helps us understand the risks associated with putting the software into operational use, and fixing the defect imporves the quality of the products. However, identifying defects has another benefit. With root cause analysis, they also hep us improve the development processes and make fewer mistakes in future work.
Actually there are many,
for example you can use
1- Early bug detection
2- Real Bug detection
3- Out of testing cycle bug reporting
