August 30, 2006

Explain Quality Assurance (QA).

Quality Assurance (QA) involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.

Bookmark this Blog to your Favorites

11 Comments:

Anonymous Anonymous said...

it is sweet simple & important question

1:47 PM  
Anonymous Anonymous said...

really gr8 stuff..... pls keep it going

12:40 AM  
Blogger Siddharth Rathod said...

A very good initiative.......
Nice stuff Jerry........Keep it going.

11:34 AM  
Anonymous Anonymous said...

Nice stuff Jerry..pz plz keep it going

10:40 AM  
Anonymous Anonymous said...

What is the role of QA in all the phases of SDLC?

8:13 PM  
Blogger Jerry Ruban said...

QA role in SDLC,

1) Requirement Analysis:-
In this phase the QA team study the requirement and analyse if anything is required before designing takes place.

2) Designing:-
In this phase it will be decided who can access and who should not access the utilities.Based on that the design is done.

3)Coding:-
Here they will check whether the coding is simple and give more functionality.

4)Testing :-
Here they will check whether it is running in all the environment and sort out the errors.

5)Implementation:-
Here they will verify whether it is getting implements without making any errors majorly.

6)Maintenance:-
In this phase they will check whether it is done on regular basis.

12:28 PM  
Blogger KennyG said...

My take on Jerry's bullets:
1. reqs - QA verifies their language, testability, narrowness/scope (are they high-level business reqs or the lowest level before design). If there are multiple levels of requirements(business analysis level down to functional level), the lower levels have to comport to the higher levels.

2. design - do the designs do what the requirements require; are they complete? Do they do more, if so, why? Is a requirement incomplete, if so, it is a req defect and must be corrected. Are there unit tests in the low level designs?

3. coding - does code follow coding standards as specified in reqs. Does code do what the design specifies? Were unit tests conducted before inspections occurred?

4. test - is the test group working from requirements, do the tests map to requirements so that a defect is traced to a requirement? So that the test group can know when all requirements are met?

5. implementation - does the project manager know that the right code is released? (version control/CM) Is it released completely and correctly? Is this verifiable?

6. Maintenance - are defects logged , does the project management decide which defects to add to future releases, and is this decision-making tracked? Also maintenance goes through all of the above stages again.

7. Metrics - project management should track how well the project did in terms of completion on time and on budget and manpower. Also they should know how many defects were found and if/when they were corrected.

These things are less important in small systems with minor outcomes in the event of failures. They are far more important for software that helps airplanes navigate over mountainous regions, and software that controls millions of dollars.

9:50 PM  
Blogger Unknown said...

Its really good article. Can anyone post the difference between - QA and QC ?

I just came to know after working 3 year as QA engineer that what we are doing is suppose to be QC-quality control then Quality assurance.

Thanks,
LightningSky

http://tricktesting.blogspot.com

4:23 PM  
Anonymous Anonymous said...

Hi, I do think this is a great blog. I stumbledupon it ;)
I am going to return yet again since I bookmarked it.
Money and freedom is the greatest way to change, may
you be rich and continue to guide other people.


my page - page next

9:45 PM  
Anonymous Anonymous said...

Unquestionably believe that that you stated. Your favourite
reason seemed to be on the web the easiest thing to have in mind of.

I say to you, I certainly get annoyed even as people consider
issues that they plainly do not understand about.
You managed to hit the nail upon the top as well as outlined out the whole thing without having
side-effects , other people can take a signal. Will likely be back to get more.

Thank you

Also visit my site - page next

9:24 AM  
Anonymous testwithus said...

SWIFT Interview questions on

http://testwithus.blogspot.in/p/swift.html

For selenium solution visit
http://testwithus.blogspot.in/p/blog-page.html


For QTP interview questions

http://testwithus.blogspot.in/p/qtp-questions.html


www.searchyourpolicy.com



11:02 AM  

Post a Comment

Subscribe to Post Comments [Atom]

<< Home