The document discusses quality assurance methods at REC Group including system integration, verification, and management tools. It describes responsibilities for customizing products, defining test approaches and plans, executing module, integration and system tests, and using test automation tools like Python and C++. It also outlines competencies in integration, verification, and skills in technologies like Java, Perl, and mobile standards.
9. Quality first!
Acceptance criteria definition - example
Weekly criteria
KPI’s – as defined by customer + REC internal
Test report covering feature to be released given week
Test scope: at least 30% of system requirements covered by test cases, 100% of features to be released in given week
Major release criteria
Summary of KPI’s, performed on delivery + clear statement about KPI’s for major release
Test coverage: 60% of system requirements covered by test cases, 100% of features
Review of test report performed by Customer
Acceptance tests, performed on selected test cases – the scope must be defined before implementation starts, details to
be confirmed at least 4 weeks before milestone. REC will provide compliance statement, considering available reources.
Exceptions
Introduced into release statement
The list of missing/not executed tests should be provided. For all the cases PL’s should be awared at least 4 weeks before
milestone