Our Services

Software Quality Assurance Practices
SQ72 evaluate how a system performs in terms of responsiveness and stability under a particular workload based on real operating conditions. Performance tests are required to quantify and benchmark speed, robustness, reliability, and application scalability. Performance tests should be conducted as early as possible and should focus on software components such as web services, microservices and APIs.
The earlier the components of an application are tested, the sooner any performance anomalies can be detected which ultimately reduces the time and cost to fix them. Tests should also be conducted regularly so that performance trending data can be understood and factored into the engineering of the final software product.
We specialise in robust system and software application Performance Testing! We will performance benchmark your applications, ensuring that you have the right inputs to create the best possible end user experience, ensuring that your software is responsive to the needs of it’s intended audience at all times!
Software Quality Assurance Consulting Services
Software Quality Assurance (SQA) is not the same as Software Testing! Effective SQA prevents defects and is driven by the entire Organisation’s Culture! SQ72 is the only company to address effective software quality assurance through addressing the culture of the organization. A culture of quality excellence prevents 80% of software defects before they enter the coding process. It addresses the whole software value chain in the organization, Business and IT and therefore cannot be driven by the Test Team! A critical component in delivering near defect-free software releases is to ensure that all stakeholders, processes and policies work in an effective and efficient manner and have all been executed with the quality of the end product in mind. This requires effective quality gates throughout the entire software creation value process. This means regular and effective communication channels and a sense of maturity and ownership of quality from all stakeholders in order for the creation processes of quality software to happen seamlessly and automatically.



Quality Gates represent:
-
Formal Checklists
Formal checklists are used throughout the life of a project.
-
Formal Sign-off and Acceptance
Formal sign-off and acceptance occurs at each gate.
-
Quality and Integrity Assessment
Assessment of the quality and integrity of the product takes place.
-
Stakeholder Communication
Information is assured to be communicated to the correct stakeholders (i.e., deployment hands off to operations, etc.).
Some of the benefits of effective quality gates are:
-
Early Defect Detection and Resolution
Detection and resolution of defects as early as possible.
-
Defect Prevention
Prevention of most defects entering into the development and testing phases.
-
Reduction in Redevelopment and Retesting
Elimination of most redevelopment and retesting due to defects.
-
Quality Ownership
Greater understanding and ownership of quality from all teams and stakeholders.
-
Fewer Defects in Production
Fewer defects in production.
-
Reduced Service Desk Calls
Fewer calls logged to the service desk due to defects.
-
Shorter Time to Market
Shorter time to market for software changes.
-
Cost Reduction
Decrease in associated costs due to elimination of rework.
-
Better Quality Software
Better quality software builds released into production.
-
Improved Reporting
Improved levels of reporting to the business through effective quality practices.
-
Increased Confidence in Changes
Greater confidence in the ability to make quick software or infrastructure changes that does not impact the business or clients.
-
Effective Collaboration
Effective collaboration and communication across all stakeholders.

Quality Gates represent:
-
Formal Checklists
Formal checklists are used throughout the life of a project.
-
Formal Sign-off and Acceptance
Formal sign-off and acceptance occurs at each gate.
-
Quality and Integrity Assessment
Assessment of the quality and integrity of the product takes place.
-
Stakeholder Communication
Information is assured to be communicated to the correct stakeholders (i.e., deployment hands off to operations, etc.).

Some of the benefits of effective quality gates are:
-
Early Defect Detection and Resolution
Detection and resolution of defects as early as possible.
-
Defect Prevention
Prevention of most defects entering into the development and testing phases.
-
Reduction in Redevelopment and Retesting
Elimination of most redevelopment and retesting due to defects.
-
Quality Ownership
Greater understanding and ownership of quality from all teams and stakeholders.
-
Fewer Defects in Production
Fewer defects in production.
-
Reduced Service Desk Calls
Fewer calls logged to the service desk due to defects.
-
Shorter Time to Market
Shorter time to market for software changes.
-
Cost Reduction
Decrease in associated costs due to elimination of rework.
-
Better Quality Software
Better quality software builds released into production.
-
Improved Reporting
Improved levels of reporting to the business through effective quality practices.
-
Increased Confidence in Changes
Greater confidence in the ability to make quick software or infrastructure changes that does not impact the business or clients.
-
Effective Collaboration
Effective collaboration and communication across all stakeholders.
