Thr Session SEE-20260326_142225-Meeting Recording

0:02

S… Speaker 2 (Thr Session SEE-20260326_142225-Meeting Recording)

Okay, Bismillah ar-Rahman ar-Rahim. I hope that slide is shared. If you have a voice note, yes, you can say yes. There is no sound. Okay. The last topic on the last topic was that we had a last metric and that was defect density. And the defect density was this. How many defects are?

0:45

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

but the density of the size is not defined so the size is assumed that we take requirements so if we identify the density of the defect on the requirement we identify as the number of defects identified per requirement so total defects to total requirements we divide the total defects to total requirements which is the same as the same as the defects per requirements so the defects will be up

1:16

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

requirements will be below 30 defects upon 5 requirements is equal to 6. In one requirement, there will be 6 defects. In 5 requirements, there will be 30 defects. In the upcoming project, there will be 10 requirements. So, expectedly, 60 defects are expected. You don't need to be exact 60. So, if it is more than 60, it looks like 5 defects.

1:44

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

This means that the testing is good. And if there are a lot of different defects in 60, then the testing is good. The testing is good. The maximum defects are good. The question is that this is a table. If I ask you, total defects per test case?

2:15

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

so since test cases were executed 65 and total defects were 30 so defects per test case means that 30 per 65 so we divide 30 to 65 so we know that in one test case there are so many defects expected now let's assume that in the upcoming project any test cases executed at the moment there are so many defects

2:48

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

So this is rough calculation. It is estimated. It is not actually. So we have estimated level here. Okay? We have covered up. After this, defect removal efficiency. The number of defects found during QA testing. The number of tests found during QA testing.

3:24

S… Speaker 2 (Thr Session SEE-20260326_142225-Meeting Recording)

plus by the end user number of defect defined QA testing which is technically there are errors and errors plus customer defined so divide so this figure can be for example defect removal efficiency is ratio check how much work is done if you have a table

4:08

S… Speaker 2 (Thr Session SEE-20260326_142225-Meeting Recording)

It's 30 and it's 90 seconds. During alpha and beta testing, it's been told. Suppose, it's an assumption situation. During the development and QA testing, we have identified 100 defects. I will oblique error. It's actually errors. When it's in the software house, it's errors.

4:55

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

But because defects can be calculated then you can say it.

5:00

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

After the QA testing, during alpha beta testing, end user client identified 40 defects.

5:21

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

...remove to remove. Because these are also errors. But we have to identify ourselves. Our QA team has to identify ourselves. Who has to identify ourselves? Client has to identify ourselves. What did he say? Defect removal efficiency. Total number of defects during testing was 100. And 100 plus 40. Total. Now there is a new total.

5:46

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

After deployment, how can we be 140? So, hundred upon 140 into hundred seventy-one percent. We have seventy-one percent. We have seventy-one percent. We have seventy-one percent. We have seventy-one percent. We have seventy-one percent. We have seventy-one percent. So, if we have zero, we have guess what we have to do. If we have zero, we have guess what we have to do. If we have zero, we have guess what we have to do. If we have zero, we have guess what we have to do. If we have zero, we have to guess what we have to do. If we have zero, we have to guess what we have to do. If we have zero, we have to guess what we have to do. If we have zero, we have to guess what we have to do. If we have zero, we have to guess what we have to do.

6:25

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

Nine intellectuals. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. I don't know. In case defect removal efficiency zero کا مطلب یہ ہے کہ سارے errors ہم successfully during development نکالنے میں کامجاب ہو گئے اور customer side سے zero defect discover ہوا. تو پھر کیا بن جائے گا hundred upon hundred.

7:17

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

To defect removal efficiency? 1. So, we will be 100% defect removal. This means that we will be 100% defect removal. Okay? How many people will be able to raise their hands? They will be able to connect. One, two, three people will be. Three people will be. How many people will be able to raise their hands?

7:53

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-10-10

8:28

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

For example, assumption is that suppose that we can get 100 defects in this case. We can get errors in this case. This is actually errors in this case. 100 errors in this case. After the QA testing, during alpha monitor testing, end user, client identified 40.

9:16

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

Total. So 40% our leakage is, our nakaam is. Okay? Here 71% from the previous matrix we have been working on. And here we have 40% nakaam. Okay? There are defects by priority. This is critical defects, high defects, medium defects and low defects.

9:54

S… Speaker 2 (Thr Session SEE-20260326_142225-Meeting Recording)

This is a simple ratio.

10:00

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

So critical defects, divide by total and divide. Now three figures have been given. Six critical, total defects have been given 30. So 60 divided by 30. This is 10 medium, high. This is 10 divided by 30. This is medium, 6 divided by 30. So this has been given a ratio complete. And low defects, 8 divided by 30. So these percentages have been given. So our work is done.

10:46

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

So there is something serious wrong.

11:03

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

So that we identify them. Okay? Let's go. Last track is maintenance. Maintenance is the main thing. This is the small matrix. Maintenance is the main reason. Maintenance is the main reason. Change is the main reason. There are three possibilities. One reason is due to change.

11:33

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

A reason due to addition of requirement. A change due to delete of requirement. Now it says that MT is the total number of modules. So modules, if you take a module, if you take a module, if you take a module, if you take a module, it is minus. The number of modules in the current lease that have been changed are FC. And the total number of modules,

12:09

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

that have been added, FA, or total number of modules from the preceding list that were deleted in the current release, which is FDA. Total minus these three changes. Total divided by total. So, with this one, our maintenance index is the name of the maturity index. What is the maturity index?

12:45

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

maturity index 1. So this means that we first time it was so accurate. Now it's change. Now it's requirement to add. Now it's delete. This is best case scenario. MT minus 0 divided by MT. So this total divided by total 1 answer. Here is your first chapter complete.

13:14

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

Okay, this is related question. Now, one small thing I want to share with the web matrices. First, I want to open the web matrices and mobile matrices. This document I want to share with you. Just for learnability. We have a slide for the next slide.

14:20

S… Speaker 2 (Thr Session SEE-20260326_142225-Meeting Recording)

Okay, this is there.

14:39

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

The first matrix is thumb reach matrix. You can see how much distance it is. Second is touch target size matrix.

15:16

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

foreign foreign foreign foreign

16:17

S… Speaker 2 (Thr Session SEE-20260326_142225-Meeting Recording)

this is

16:18

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

and target value be a bit about it. That's how it should be. This is just inspiration for you to see and understand it. And when you do this assignment, you can clear the picture. You can collect data. You can collect data. You can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation. Then you can put on this equation.

16:46

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

data collect کیا. Soil testing کے context میں. پہلے data collect کیا. Data کے بعد matrices میں values put on کی. تو ہمیں سمجھ میں آنا شروع ہو گیا. اسی طرح آپ کو assignment دوں گا. وہ web کا. تو web کے آپ پہلے parameters calculate کریں گے. اس کے بعد ہم matrices خود ہی بنانا سیکھ جائیں گے انشاءاللہ. اس کے بعد اگلا جو chapter پڑھیں گے. ہم اس کے اندر matrices بنانا سیکھیں گے. تو پھر ہم اس سے بہت سارے drive matrices کر سکیں گے انشاءاللہ.

17:13

S… Speaker 3 (Thr Session SEE-20260326_142225-Meeting Recording)

Thank you.

17:45

S… Speaker 1 (Thr Session SEE-20260326_142225-Meeting Recording)

This recording will be another recording. Stop recording.

Thr Session SEE-20260326_142225-Meeting Recording

Povzetek

Vprašaj AI o tem transkriptu