Software Quality Assurance

Who is a Good Tester ?

2011-03-13T23:16:00.000-07:00

Who is a Good Tester? / Tips for a Good Tester

If you are a beginner in testing, you will definitely think what should be key points which must be followed to become a good tester or what could be tips. Here are few listed:

Clear Understanding of FRS

A tester should have clear understanding of functional and non functional requirements of Project /Software. If you know requirements, you will be confident while testing and it will save time as well.

Don’t Rely Only on Final Output

Don’t think that you have to only match FRS with software build by developer. You are not supposed to only find error but you may suggest some new functionality as well if you think so.

Always have Destructive Approach

Whenever you test, always see it from destructive point of view. Try to fine as much bugs as possible

Discussions with Developers

Through out testing, have discussions with developers so you may have clear understanding of each function. Never test on self assumptions; it may create problems in end.

Don’t Totally Rely on Developers

Sometimes, tester discusses only with coders and don’t check FRS in some cases. This is wrong. Developers may sometime mislead to safe themselves. In case of interface designing, consult written design specifications.

Don’t Underestimate

It is often seen that developers criticize tester as result of bugs tester find in their code. Sometimes, it may happen due to time pressures. Secondly, sometimes developers may take bugs personally. This is not good approach. QA team seems destructive but in fact hey are also constructors as they assure quality and deliver bug free application. If developers take it professionally, they should consider it good if tester find bugs. In the end, client will be happy if you provide bug free code.

So,

A good coder is one who appreciates Bugs and
A good tester is one who find bugs free of any pressures

Convince with Logic
Always convince developers with logics. If you are wrong, admit it and don’t take it personally.

Learn to deal with Time Pressures
Don’t get tensed when you have to meet deadlines. If time is short, you should test main functionalities first.

Remind Developers about P1, P2 Bugs

If Developers are not working on bugs having highest priority, remind them again and again. Ask tem to first fix P1 and P2 bugs. Always set priority of bugs carefully.

Don’t build personal biasness

Don’t have personal biasness with any developer. Testing is a profession, take it in positive way. If you get biased, you may not discuss things clearly.
Always go for Written Work

If you find any bug, log it on bug tracking software. Discuss with developer, if you have ambiguity. Sometimes, developers ask testers not to log bug .They ask to tell them orally. This is wrong. Always have written prove of your work. If you don’t log bug, things would not be systematic and it will be difficult to manage changes.

QA Team collaboration

If you have enough time, test your application on different platform and by different testers. Let testers discuss their testing result among themselves. QA team lead should compare results by both testers. It may also help in evaluation of QA team by giving them same application.

If you are testing on different platforms, assign it to multiple testers. Ask them to discuss bugs among themselves. This help in finding whether a bug is platform issue or it is a bug in code.

Enhancement Bugs

If you have enhancements in software, ask same testers to test which test its previous release. One who had tested it in previous release may better test enhancements.

Written By:

Madeeha Rashid

Upcoming posts

2010-08-08T01:30:00.000-07:00

Here I have listed upcoming posts. These are not the finalized topics but may be followed in this manner: You may suggest more.

Software Development life cycles

Current SDLCS

A look at Agile based SDLCS

CMMI

ISO Quality Standards

Microsoft SQA Framework

Google SQA Framework

Software Quality Attributes

Software Quality Models

Software Quality Metrics

Software Configuration Management

Software Project Management

Agile Software Project Management

Agile Project Management Tools

AGILE AND CMMI

Extreme Programing and Software Quality Assurance

SCRUM

SCRUM and SQA

RUP

CMMIL level 2

SQA is an umbrella activity

Software Requirements Engineering

SRS

FS

Inspections and Reviews

Software Design

Software Design Reviews and Inspections

Software Testing

Software Testing Life Cycle

Automated Software Testing Life Cycle

Testing Basics

Unit Testing

Unit Testing Framework

Unit Testing Tools

Functional Testing Tools

Regression testing

Performance Testing

Load Testing

Stress Testing

Usability Testing

User Acceptance Testing

System Testing

Beta Testing

Automated Testing

Automated Testing Tools

Open Source Testing Tools

Commercial Automated testing Tools

SQA Certifications

Automated Testing Tools Certifications

Project Management Certifications

System Analyst Certifications

Software Quality Control

2010-06-09T02:20:00.000-07:00

There is a clear distinction between Software Quality Control and Software Quality Assurance. Software Quality Control is a set of activities or set of procedures which come into play to check the acutal quality of the product. We may also define Software Quality Control" activity or a procedure used as a tool / metod to predict the quality of the product".

A very common and good example of Software Quality Control is Software Testing activity. Software Testing is used to determine possible bugs / defects present in an application. So through Software Quality Control we check the product of quality using some tesing methods.

Software Quality Control is the set of procedures used by organizations (1) to ensure that a software product will meet its quality goals at the best value to the customer, and (2) to continually improve the organization’s ability to produce software products in the future. [Wikipedia]

Software Quality Control Methods
Testing
Rome laboratory Software framework
Goal Question Metric Paradigm
Risk Management Model
The Plan-Do-Check-Action Model of Quality Control
Total Software Quality Control
Spiral Model Of Software Development

What is Software Quality Assurance?

2010-05-11T00:48:00.000-07:00

The term Software Quailty Assurance is widely used in the Software Industry and IT / cs Academia. SQA is a broader term it may be defined as the set of rules / procedures in action to monitor the conformance to the organizagtion wide laid down process for assuring quality. These are set of methods or techniques used to control the process of software Development. So it is to check and monitor to see the conformance of processes defined by a specific organization for developing a software product / service.
According to the wikipedia we may define it as: Software quality assurance (SQA) consists of a means of monitoring the software engineering processes and methods used to ensure quality. The methods by which this is accomplished are many and varied, and may include ensuring conformance to one or more standards, such as ISO 9000 or a model such as CMMI.

Software Qualiyt Assurance includes following but not limited to:

Laying out agreed upon Procdeures and Standards

Conformance to the :-

Software Requirements Engineering
Software Requirements Management
Software Requiremetns Specification
Software Design
Software Coding
Software Testing
Software Configuration Management

There are done under specific standard or Method i.e. CMMI or ISO or even orgianztion specified methods and procedures.

Conformance is done through following:

Review of different artifacts in different phases of SDLC
Inspections of different artifacts in different phases of SDLC.

What is Software Quality?

2010-05-03T04:48:00.000-07:00

Software Quality

Software Quality is some what a difficult term to be explained. But here I shall try to explain it in simple words. From a user perspective Software Quality may be defined as the product which full fills all the implicit and explicit requirements i.e. Functional and Non functional Requirements as per specifications. Ideally it may be termed as the Software with zero defects after it is delivered to the customer.

In the context of software engineering, software quality measures how well software is designed (quality of design), and how well the software conforms to that design (quality of conformance),[1] although there are several different definitions.

What is Tetsing?

2010-05-03T04:25:00.000-07:00

According to web definition the act of subjecting to experimental test in order to determine how well something works; "they agreed to end the testing of atomic weapons"
Now we talk about Testing in terms of Software. There are various definitions available for Software Testing. According to my knowledge and experience Software Testing may be defined as the process of removing all the possible bugs and defects before it is delivered to the end use / client. Testing is a way to make a quality check on the product being developed. It is a part of Software Development Life Cycle phases.
Software Testing may also be defined as the process in which we check that whether the software product conforms to specifications as told be the customer. Software Testing is a part of Quality Control activities.
From Wikipedia it says about testing as : Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted.

The correct and accurate definition of Software Testing is that it is the process which checks / predicts for any possible bugs / defects. Debugging is the separate thing which involves the process of removing bugs from the software.

Another good definition available for Testing is as: "Testing is the process of identifying defects, where a defect is any variance between actual and expected results."

References:
http://en.wikipedia.org/wiki/Software_testing
http://www.sqatester.com/bugsfixes/whatistesting.htm

post QA RELATED TOPICS

2009-02-18T21:47:00.000-08:00

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING.
YOU ARE WELCOME TO MAKE ANY NEW POST HERE.

Web Testing

2008-08-07T23:12:00.001-07:00

Web Testing:
During testing the websites the following scenarios should be considered.
Functionality
Performance
Usability
Server side interface
Client side compatibility
Security
Testing Functionality: In testing the functionality of the web sites the following should be tested.
Links
Internal links
External links
Mail links
Broken links
Form
Field validation
Functional chart
Error message for wrong input
Optional and mandatory fields
Database
Testing will be done on the database intergrity
Cookies
Testing will be done on the client system side, on the temporary internet files.
Performance : Performance testing can be applied to understand the web site's scalability, or to benchmark the performance in the environment of third party products such as servers and middleware for potential purchase.
Connection Speed
Connected over various networks like Dial Up, ISDN
Load
What is the no. of users per time?
Check for peak loads & how system behaves.
Large amount of data accessed by user.
Stress
Continuous load
Performance of memory, cpu, file handling etc.
Usability:
Usability testing is the process by which the human-computer interaction characteristics of a system are measured, and weaknesses are identified for correction.
Usability can be defined as the degree to which a given piece of software assists the person sitting at the keyboard to accomplish a task, as opposed to becoming an additional impediment to such accomplishment. The broad goal of usable systems is often assessed using several criteria:
Ease of learning
Navigation
Subjective user satisfaction
General appearance
Server Side Interface:
In web testing the server side interface should be tested. This is done byVerify that communication is done properly.Compatibility of server with software, hardware, network and database should be tested.The client side compatibility is also tested in various platforms, using various browsers etc.
Security:
The primary reason for testing the security of an web is to identify potential vulnerabilities and subsequently repair them.
The following types of testing are described in this section:
Network Scanning
Vulnerability Scanning
Password Cracking
Log Review
Integrity Checkers
Virus Detection

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

Performance Testing

2008-08-07T23:09:00.001-07:00

Performance Testing:
Performance testing is a rigorous usability evaluation of a working system under realistic conditions to identify usability problems and to compare measures such as success rate, task time and user satisfaction with requirements.
The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression testing.
To conduct performance testing is to engage in a carefully controlled process of measurement and analysis. Ideally, the software under test is already stable enough so that this process can proceed smoothly.A clearly defined set of expectations is essential for meaningful performance testing.For example, for a Web application, you need to know at least two things:
expected load in terms of concurrent users or HTTP connections
acceptable response time
Load Testing:
Load testing is usually defined as the process of exercising the system under test by feeding it the largest tasks it can operate with. Load testing is sometimes called volume testing, or longevity/endurance testing
Examples of volume testing:
testing a word processor by editing a very large document
testing a printer by sending it a very large job
testing a mail server with thousands of users mailboxes
Examples of longivity/endurance testing:
testing a client-server application by running the client in a loop against the server over an extended period of time
Goals of load testing:
expose bugs that do not surface in cursory testing, such as memory management bugs, memory leaks, buffer overflows, etc.
ensure that the application meets the performance baseline established during performance testing. This is done by running regression tests against the application at a specified maximum load.
Although performance testing and load testing can seen similar, their goals are different. On one hand, performance testing uses load testing techniques and tools for measurement and benchmarking purposes and uses various load levels whereas load testing operates at a predefined load level, the highest load that the system can accept while still functioning properly.
Stress Testing:
Stress testing is a form of testing that is used to determine the stability of a given system or entity. This is designed to test the software with abnormal situations. Stress testing attempts to find the limits at which the system will fail through abnormal quantity or frequency of inputs.
Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it (in which case it is sometimes called negative testing). The main purpose behind this madness is to make sure that the system fails and recovers gracefully -- this quality is known as recoverability.
Stress testing does not break the system but instead it allows observing how the system reacts to failure. Stress testing observes for the following.
Does it save its state or does it crash suddenly?
Does it just hang and freeze or does it fail gracefully?
Is it able to recover from the last good state on restart? Etc.

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

Compatability Testing

2008-08-07T23:06:00.000-07:00

Compatability Testing:
A Testing to ensure compatibility of an application or Web site with different browsers, OS and hardware platforms. Different versions, configurations, display resolutions, and Internet connect speeds all can impact the behavior of the product and introduce costly and embarrassing bugs. We test for compatibility using real test environments. That is testing how will the system performs in the particular software, hardware or network environment. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.

The purpose of compatibility testing is to reveal issues related to the product’s interaction with other software as well as hardware. The product compatibility is evaluated by first identifying the hardware/software/browser components that the product is designed to support. Then a hardware/software/browser matrix is designed that indicates the configurations on which the product will be tested. Then, with input from the client, a testing script is designed that will be sufficient to evaluate compatibility between the product and the hardware/software/browser matrix. Finally, the script is executed against the matrix, and any anomalies are investigated to determine exactly where the incompatibility lies.
Some typical compatibility tests include testing your application:
On various client hardware configurations
Using different memory sizes and hard drive space
On various Operating Systems
In different network environments
With different printers and peripherals (i.e. zip drives, USB’s, etc.)

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

Regression Testing

2008-08-07T23:05:00.001-07:00

Regression Testing:
A Regression testing is testing the module in which a bug was identified earlier along with the impacted areas to ensure that this fix has not introduced any further defects.
The purpose of regression testing is to ensure that previously detected and fixed issues really are fixed, they do not reappear, and new issues are not introduced into the program as a result of the changes made to fix the issues.
Regression testing also referred to as verification testing, is initiated after a programmer has attempted to fix a recognized problem or has added source code to a program that may have inadvertently introduced errors. It is a quality control measure to ensure that the newly modified code still complies with its specified requirements and that unmodified code has not been affected by the maintenance activity.
Regression Testing is in general a black box testing strategy where test case execution of previously written test cases, that has exposed bugs, is done to check whether previously fixed faults have reemerged. In a test suite, all the tests that has caused bug are written and are re-tested whenever changes are made to the program to fix any bug. But this is a tedious process as after every compilation it is difficult to go through the process of retesting all the test cases repeatedly. To make this process simpler regression testing is automated using some testing tools.
Typically regression testing should be performed on a daily basis. Once an issue in the defect
tracking database has been fixed it is reassigned back for final resolution. Now it can be either reopens the issue, if it has not been satisfactorily addressed, or close the issue if it has, indeed, been fixed.

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

Functionality Testing

2008-08-07T23:03:00.000-07:00

Functionality Testing:

Functional testing is validating an application or web site, conforms to its specifications and correctly performs all its required functions.
This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product's user interface, database management, security, installation, networking, etc.
The purpose of functionality testing is to reveal issues concerning the product’s functionality and conformance to user requirement.
The first step in functionality testing is to become familiar with the program itself, and with the program’s desired behavior. For this the tester should have clear idea about the documentation such as the program’s functional specification or user manual. Once a program’s expected functionality has been defined, test cases or test procedures can be created that exercise the program in order to test actual behavior against expected behavior. Testing the program’s functionality then involves the execution of any test cases that have been created. Certain portions of a functionality testing effort can also be automated, depends on several factors, and should be discussed with a qualified engineer.
Range checking- minimum and maximum values should not be exceeded (invalid values should not be accepted)
Check whether numeric fields accept only numeric values
Check ‘online Help’ feature (including buttons to open Help feature)
Check ‘Print’ feature
Check ‘Open file’ feature (must open correct file extensions and incorrect file type should give error messages)
Check ‘Graph’ features
If there are logins, enter invalid login information for each field
Check for error messages for clarity and whether they come up when they are supposed to.
In the presence of a database, check all connections through application are valid when accessing data (error messages like “could not connect to database” should not appear.
Modify data files (like add extra special characters) to make sure the application gives correct error messages
For administrative features make sure only administrators of application may access the features
Check by adding duplicate records
Delete all records to check whether such an action does not crash the application
Check for compatibility using MS Office application (like copy and paste)
Click all buttons to make sure all of them are functioning appropriately
Click ‘save’ feature (should not be able to overwrite existing file without permission), should save to correct directory, must create correct extension)
Check options/settings
Check international units are converted correctly
Make sure no spellings are incorrect
Check for valid date formats
Make sure windows are properly minimized, maximized and resized
Check whether keyboard shortcuts are working properly
Check that right mouse clicks show correct pop up menus
If hardware/software keys are present check if the application works as intended with and without execution of keys.

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

Techniques in Black Box Testing

2008-08-07T23:00:00.000-07:00

Techniques In BlackBox:

Black box testing attempts to derive sets of inputs that will fully exercise all the functional requirements of a system. It is not an alternative to white box testing. This type of testing attempts to find errors in the following categories:

incorrect or missing functions
interface errors
errors in data structures or external database access
performance errors and
Initialization and termination errors.
Test are designed to answer the following questions:
How is the function's validity tested?
What classes of input will make good test cases?
Is the system particularly sensitive to certain input values?
How are the boundaries of a data class isolated?
What data rates and data volume can the system tolerate?
What effect will specific combinations of data have on system operation?
White box testing should be performed early in the testing process, while black box testing tends to be applied during later stages. Test cases should be derived which
reduce the number of additional test cases that must be designed to achieve reasonable testing, and
tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.
Equivalence Partitioning This method divides the input domain of a program into classes of data from which test cases can be derived. Equivalence partitioning strives to define a test case that uncovers classes of errors and thereby reduces the number of test cases needed. It is based on an evaluation of equivalence classes for an input condition. An equivalence class represents a set of valid or invalid states for input conditions.
Equivalence classes may be defined according to the following guidelines:
If an input condition specifies a range, one valid and two invalid equivalence classes are defined.
If an input condition requires a specific value, then one valid and two invalid equivalence classes are defined.
If an input condition specifies a member of a set, then one valid and one invalid equivalence class are defined.
If an input condition is boolean, then one valid and one invalid equivalence class are defined.
Boundary Value Analysis This method leads to a selection of test cases that exercise boundary values. It complements equivalence partitioning since it selects test cases at the edges of a class. Rather than focusing on input conditions solely, BVA derives test cases from the output domain also. BVA guidelines include:
For input ranges bounded by a and b, test cases should include values a and b and just above and just below a and b respectively.
If an input condition specifies a number of values, test cases should be developed to exercise the minimum and maximum numbers and values just above and below these limits.
Apply guidelines 1 and 2 to the output.
If internal data structures have prescribed boundaries, a test case should be designed to exercise the data structure at its boundary.
Cause Effect Graphic Techniques :Cause-effect graphing is a technique that provides a concise representation of logical conditions and corresponding actions. There are four steps:
Causes (input conditions) and effects (actions) are listed for a module and an identifier is assigned to each.
A cause-effect graph is developed.

The graph is converted to a decision table.
Decision table rules are converted to test cases.

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

BLACK BOX TESTING

2008-08-07T22:56:00.000-07:00

Black-box Testing:

This treats the system as a "black-box", so it doesn't use knowledge of the internal structure explicitly. It is usually described as focusing on testing functional requirements. Synonyms for black-box include: behavioral, functional, opaque-box, and closed-box.Black Box Testing is testing without knowledge of the internal workings of the item being tested. For example, when black box testing is applied to software engineering, the tester would only know the "legal" inputs and what the expected outputs should be, but has no idea how the program actually arrives at those outputs.

It is because of this that black box testing can be considered testing with respect to the specifications, no other knowledge of the program is necessary. For this reason, the tester and the programmer can be independent of one another, avoiding programmer bias toward his own work.

The so-called ``functionality testing'' is central to most testing exercises. Its primary objective is to assess whether the program does what it is supposed to do, i.e. it should meet user specified requirements. There are different approaches to functionality testing. One is the testing of each program feature or function in sequence. The other is to test module by module, i.e. each function where it is called first.

Advantages:

More effective on larger units of code than glass box testing
Tester needs no knowledge of implementation, including specific programming languages
Tester and programmer are independent of each other
Tests are done from a user's point of view
Test cases can be designed as soon as the specifications are complete

Disadvantages

Only a small number of possible inputs can actually be tested, to test every possible input stream would take nearly forever
Without clear and concise specifications, test cases are hard to design
There may be unnecessary repetition of test inputs if the tester is not informed of test cases the programmer has already tried
May leave many program paths untested
Cannot be directed toward specific segments of code which may be very complex (and therefore more error prone)
Most testing related research has been directed toward glass box testing

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

What is SQA

2008-07-30T23:13:00.000-07:00

some useful links for SQA.

1. http://www.swqual.com/
2. http://www.techinterviews.com/?p=134
3. http://www.sqa.net/
4. www.rspa.com/spi/SQA.html
5. www.sqa.org.uk/sqa
6. www. secure.sqa.org.uk
7.www.softwareqatest.com\
8. satc.gsfc.nasa.gov/assure/agbsec3.txt
9. www.qaiworldwide.org
10. www.sqazone.net/ - 21k

Software Quality Assurance

Def 1

The correct definition of Software Quality Assurance goes something like:- The function of software quality that assures that the standards, processes, and procedures are appropriate for the project and are correctly implemented. This definition is taken from Software Definitions at NASA .

The problem with this, and similar, definitions for commercial SQA practitioners are:-
It tells us little about what SQA is other than repeating the definition. That is, it uses the defined terms “assures” and “software”.

Def 2

Abbreviated as SQA, and also called software assurance, it is a level of confidence that software is free from vulnerabilities, either intentionally designed into the software or inserted at anytime during its lifecycle, and that the software functions in the intended manner.

Soruce : http://www.webopedia.com/TERM/S/Software_Quality_Assurance.html

Def 3

Concepts and Definitions

Software Quality Assurance (SQA) is defined as a planned andsystematic approach to the evaluation of the quality of andadherence to software product standards, processes, andprocedures. SQA includes the process of assuring thatstandards and procedures are established and are followedthroughout the software acquisition life cycle. Compliancewith agreed-upon standards and procedures is evaluatedthrough process monitoring, product evaluation, and audits.Software development and control processes should includequality assurance approval points, where an SQA evaluationof the product may be done in relation to the applicablestandards.

Def 3
A very good link for SQA People for basic understanding.
http://www.swqual.com/newsletter/vol2/no1/vol2no1.html

You are welcome to add more into this topic.

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

SQA JOBS

2008-07-30T22:58:00.000-07:00

USEFUL !!

SQA is one of the most highly paid profession in Software Engineering careers.

Why SQA is rapidly growing profession ??? These are the some of the jobs avialable round the world for SQA people.

QA / Test Automation & Methodologies Man
DC, Washington, DC
$115,000 per year

Senior Associate-QA
India, GurgaonHaryana
Not specified

Test Engineer
California, Santa Barbara
$55-70K per year

QA Tester (Rational Tools and Mortgage e
North Carolina, Charlotte
Not specified

Sr QA Engineer (Software)
California, Foster City
Not specified

Sr. Performance Test Engineer
New Jersey, Jersey City
Not specified

QA Engineer
Texas, Dallas
$45 per hour

Senior API / SDK Test Engineer - CBUMARS
Maryland, Lanham
$100,000

Software Engineer in Test
California, Palo Alto
Not specified

GCCS Integration Tester/Field Tech
Massachusetts, Bedford
Not specified

Sr. Software Engineer in Test
California, Palo Alto
Not specified

Software Quality Assurance Engineer (web
California, Berkeley
$80,000 per year

QA Engineer
Texas, Austin
Not specified

Software Test Engineer - STE061108QAJ
Washington, Redmond
Not specified

SOFTWARE TEST ENGR SR
Wisconsin, Milwaukee
$DOE per year

Quality Engineer
Texas, Austin
$DOE

Manager of Quality Assurance
Wisconsin, Milwaukee
Not specified

Arch Rock QA Test Lead
California, San Francisco
Not specified

Software Quality Assurance Analyst
California, Truckee
Not specified

Tele. Int./Senior Software Test Eng
Washington, Bothell
$DOE per year

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

WELCOME ALL

2008-07-30T22:04:00.000-07:00

Dear All,

All Virtual University Instructors from Department of Computer Science are welcome to this foum for thier active participation in SE related topics especially in Software Quality Assurance.

SQA IS KEY TO THE PRDUCT SUCCESS AS WELL AS ORGANIZATION LONG LASTING

Software Quality Assurance

2008-07-30T21:41:00.000-07:00

Hi, fellows !!!

This is my newest blog for Software Quality Assurance. SQA is one of the most important field in Software Engineering Domain. Software Quality Assurance itself is a vast filed to study and explor.

Without SQA Department a Software Company can earn a business for a short time but not for a long time. So now a dasys organizations are focusing more on Software Quality Assurance to deliver High Quality products and services to the customers.

The purpose of this blog is to have a forum where we all can share our views, experiences, latest updates in SQA fields. One can show his / her research work in this area. We will be populating it with all SQA areas i.e. Reviews, Inspections, Testing / Automated Testing , Configuration Management, Six Sigma, Software Process Focus, CMMI and much more related.