Compusult is committed to delivering quality products and services to all our clients. In this respect, we have implemented an in-house Software Quality Assurance (SQA) program that meets the requirements of the CAN/CSA-Q396.1.1 standard for the development of systems, software and related documentation used in critical applications. Our staff have also been trained in and have previous project experience with the IEEE guidelines.
Compusult’s quality policy is to undertake and complete projects in accordance with the requirements of CAN/CSA-Q396.1.1, IEEE, ISO, and other related specifications. Compusult establishes and maintains a program for quality control based on these standards for each project. This encompasses every aspect of the supply, installation and testing of all custom and commercial hardware and software needed to provide the required functionality and performance. The following deliverables are typically produced as a result of Quality Assurance procedures:
- Project Plan - Project team organization; work breakdown structure; phase and task schedule; change control plan; documentation summary; review and reporting plan.
- Project Quality Assurance Plan - Outlines the project team responsibilities; purpose of documentation with respect to QA; standards, practices and conventions; reviews and audits; configuration management; problem reporting; tools, techniques and methodologies; code control; media control; and supplier control.
- System Requirements Specification - A description, in terms that can be understood by the client and system developers, of the needs and expectations with respect to the system, functions that it must provide, performance that must be attained, interfaces that must be supplied, and constraints within which it must be developed.
- High-Level Design - System overview; design methodologies employed; design view; general design aspects; system component decomposition; and attribute descriptions.
- Detailed Design - Detailed documentation of system and data architecture; functions; hardware and software components; dependencies; resources; interfaces; processing.
- Unit Tests - Procedures for verifying and validating the correct operation and functionality of individual system components, as per the system design.
- Integration Tests - Procedures for verifying and validating the correct functionality and interoperability of integrated system components.
- Acceptance Test Plan - The philosophy and approach to acceptance testing for the system; formal sign-off procedures; Requirements Traceability Matrix (RTM); timing of acceptance testing; appendices with test procedures for Integration Testing, Acceptance Testing, and Operational Evaluation following system delivery and acceptance.
- User’s Manual - A reference document for system users concerning access and usage procedures; user interface; functions; etc.