|
Software QA/Testing Technical FAQs
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
What is the difference between efficient and effective?
"Efficient" means having a high ratio of output to input; which means working or producing with a minimum of waste. For example, "An efficient engine saves gas." Or, "An efficient test engineer saves time".
"Effective", on the other hand, means producing or capable of producing an intended result, or having a striking effect. For example, "For rapid long-distance transportation, the jet engine is more effective than a witch's broomstick". Or, "For developing software test procedures, engineers specializing in software testing are more effective than engineers who are generalists".
How effective can we implement six sigma principles in
a very large software services organization?
Answer1:
Effective way of implementing sixsigma.
there are quite a few things one needs
1. management buyin
2. dedicated team both drivers as well as adopters
3. training
4. culture building - if you have a pro process
culture, life is easy
5. sustained effort over a period towards
transforming, people, thoughts and actions
Personally technical content is never a challenge, but
adoption is a challenge.
Answer2:
"Six sigma" is a combination of process recommendations and
mathematical model. The name "six sigma" reflects the notion of
reducing variation so much that errors -- events out of tolerance --
are six standard deviations from a desired mean. The mathematics are at
the core of the process implementation.
The problem is that software is not hardware. Software defects are
designed in, not the result of manufacturing variation.
The other side of six sigma is the drive for continuous improvement.
You don't need the six sigma math for this and the concept has been
around long before the six sigma movement.
To improve anything, you need some type of indicator of its current
state and a way to tell that it is improved. Plus determination to
improve it. Management support helps.
Answer3:
There are different methodologies adopted in sixsigma.
However, it is commonly referenced from the variance
based approach. If you are trying to look at sixsigma
from that, for software services, fundamentally the
measurement system should be reliable - industry has
not reached the maturity level of manufacturing
industry where it fits to a T. The differences between SW and
HW/manufacturing industry is slightly difficult to
address.
There are some areas you can adopt sixsigma in its
full statistical form(eg in-process error rate,
productivity improvements etc), some areas are
difficult.
The narrower the problem area is, the better it gets
even in software services to address adopting the
statistical method.
There are methodologies that have a bundle of
tools,along with statistical techniques, are used on
the full SDLC.
A generic observation is ,SS helps if we look for
proper fitment of methodology for the purpose. Else
doubts creep in
What stage of bug fixing is the most cost effective?
Bug prevention techniques (i.e. inspections, peer design reviews, and walk-throughs) are more cost effective than bug detection.
What is Defect Life Cycle.?
Answer1:
Defect life cycle is....different stages after a defect is identified.
New (When defect is identified)
Accepted (when Development team and QA team accepts it's a Bug)
In Progress (when a person is working to resolve the issue-defect)
Resolved (once the defect resolved)
Completed (Some one who can take up the responsibly Team lead)
Closed/reopened (Retested by TE and he will update the Status of the bug)
Answer2:
Defect Life Cycle is nothing but the various phases a Bug undergoes after it
is raised or reported.
A general Interview answer can be given as:
1. New or Opened
2. Assinged
3. Fixed
4. Tested
5. Closed.
What is the difference between a software bug and software defect?
"Software bug" is nonspecific; it means an inexplicable defect, error, flaw, mistake, failure, fault, or unwanted behavior of a computer program. Other terms, e.g. "software defect", or "software failure", are more specific.
While the word "bug" has been a part of engineering jargon for many-many decades; many-many decades ago even Thomas Edison, the great inventor, wrote about a "bug" - today there are many who believe the word "bug" is a reference to insects that caused malfunctions in early electromechanical computers.
Part:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
| 