Difference between revisions of "Main Page"

From Team
Jump to: navigation, search
m
m
Line 37: Line 37:
 
* [http://www.sqaresources.com SQA Resources Home Page(Old)]
 
* [http://www.sqaresources.com SQA Resources Home Page(Old)]
 
* [http://blog.qaevangelist.com/?cat=10 Glossary of Terms/Definitions]
 
* [http://blog.qaevangelist.com/?cat=10 Glossary of Terms/Definitions]
* [[Overview| of Standard Operating Procedures]]
+
* [[Overview|Standard Operating Procedures Overview]]

Revision as of 05:37, 17 April 2013

Team Site for SQA²

Getting started

The first step on the road to exceeding your customer's expectations is to establish a process that will support your customers' unique goals and needs of their organization.

The Team at SQA² helps our business partners define and implement a more effective software quality-assurance process. We can demonstrate that a better software QA process leads not only to more satisfied customers, but also to shorten the time-to-market timelines while at the same time reducing costs for support and maintenance.


An effective software quality methodology incorporates:

  • PROCESS - Documented procedures to guide and support users of the methodology
  • PEOPLE - Management leadership; training and support for all participants
  • TOOLS - Used to support (not replace) the process

SQA² subscribes to the Context-Driven school of testing. There is no "one size fits all" approach to software QA methodology. Underpinning all our processes is the PDCA process developed by W. Edwards Deming in the 1950s. The continuous improvement process is best described by the diagram showing the PDCA feedback loop used at SQAR (shown right). The continuous process is described below:

  • PLAN - Design or revise business process components to improve results
  • DO - Implement the plan and measure its performance
  • CHECK - Assess the measurements and report the results to decision makers
  • ADJUST - Decide on changes needed to improve the process

See Also: