1. OHIM new way of managing projects – Quality improvements
27/06/07
IT Development
OHIM new way of managing projects – Quality improvements
Eamonn Kelly

2. OHIM new way of managing projects – Quality improvements
Industry standard model adopted.
Standard Processes to ensure
Review of Requirements documentation to obtain knowledge of desired end product
Systematic procedures to validate test procedures
Test procedures confirm alignment to business requirements.
Industry standard model used for quality assurance of products – this covers more than just the testing process.
Why have we adopted the V Model – robust and established method.
How does that work in Quality Assurance within IT Development:-
Left hand side of the V Model:
Reviews and understands:-
the Business case to understand desired end product required by the business.
System specificationa and design to understand the system design, integration and configuration requirements.
Reviews the use cases to ensure they reflect the contents of the software design
Reviews the content of the test and launch plans to ensure compliance to OHIM QA test standards, security requirements, etc.
Right Hand side of the V Model:
Reviews the results of the external developer’s test results align to the requirements
Replicate the external developers test plan in the OHIM environment
Create the QA test plan with the use cases
Create the QA test scenarios
Create robot – simulate the user and simulate many users to make the stress testing.

3. OHIM new way of managing projects – Quality improvements
OHIM adapts V Model incorporating 6 Quality Gates
Quality Gate 1: Test Plan reflects Use Case & Requirements
First make review of use case and test plan to ensure they are adequate and consistent without discrepancies.
To identify any abnormal pre-conditions (requirement of functionality of a field within the application) and post-conditions (does the new application reflect the functionality requirements).
Feedback to QMD with conclusions on the review.
Review test plan from external developer, which should follow the standard test plan structure required by the OHIM QA, which are detailed in a requirements document provided to the external developer.
Quality Gate 2: System Tests Satisfactory
Test the launch plan for the instalation – not just testing the application, but how it integrates with other systems.
Receive the test results from the external developing company and review the percentage of successful tests performed. Error percentage tolerances established to guide as to acceptance criteria.
Within the OHIM test environment, execute all the test plans sent by the external development to validate their results, plus OHIM’s QA own test procedure, with emphasis on security, technical, eg. functionality of fields to ensure their adequate processing and control of data.
Provides the confirmation to proceed to UAT stage.
Pre-UAT performed by QMD
Quality Gate 3: OHIM Tests Satisfactory
Provides confirmation to proceed with UAT with Key Users
Quality Gate 4: UAT Satisfactory
UAT performed by Key Users
Provides the confirmation to proceed to implement into production environment.
Quality Gate 5: Release Test Results Satisfactory
Post implementation review process:
Meet with IT PRoduction to ensure stable environment
Feedback from IT Production reporting successful implementation
Correction Actions for any issues relating to implementation to ensure quality of product.
Quality Gate 6: Delivered solution reflect Business Case Requirements
Review the original requirements of the business case to ensure the application/product delivered aligns to the original requirements.

4. OHIM new way of managing projects – Quality improvements
The 6 Quality Gates
1: Test Plan Reflects Use Case & requirements
2: System Test Results Satisfactory
3: OHIM Test Results Satisfactory
4: UAT Results Satisfactory
5: Release Test Results Satisfactory
6: Delivered solution reflect Business Case Requirements
Quality Gate 1: Test Plan reflects Use Case & Requirements
First make review of use case and test plan to ensure they are adequate and consistent without discrepancies.
To identify any abnormal pre-conditions (requirement of functionality of a field within the application) and post-conditions (does the new application reflect the functionality requirements).
Feedback to QMD with conclusions on the review.
Review test plan from external developer, which should follow the standard test plan structure required by the OHIM QA, which are detailed in a requirements document provided to the external developer.
Quality Gate 2: System Tests Satisfactory
Test the launch plan for the instalation – not just testing the application, but how it integrates with other systems.
Receive the test results from the external developing company and review the percentage of successful tests performed. Error percentage tolerances established to guide as to acceptance criteria.
Within the OHIM test environment, execute all the test plans sent by the external development to validate their results, plus OHIM’s QA own test procedure, with emphasis on security, technical, eg. functionality of fields to ensure their adequate processing and control of data.
Provides the confirmation to proceed to UAT stage.
Pre-UAT performed by QMD
Quality Gate 3: OHIM Tests Satisfactory
Provides confirmation to proceed with UAT with Key Users
Quality Gate 4: UAT Satisfactory
UAT performed by Key Users
Provides the confirmation to proceed to implement into production environment.
Quality Gate 5: Release Test Results Satisfactory
Post implementation review process:
Meet with IT PRoduction to ensure stable environment
Feedback from IT Production reporting successful implementation
Correction Actions for any issues relating to implementation to ensure quality of product.
Quality Gate 6: Delivered solution reflect Business Case Requirements
Review the original requirements of the business case to ensure the application/product delivered aligns to the original requirements.

5. OHIM new way of managing projects – Quality improvements
Quality Assurance is not just about testing!!!!
To improve and ensure the quality of the applications developed and implemented
To ensure all applications are implemented which are in line with user requirements and fit for purpose.
Respects standards to ensure the maintainability of the application.
Quality of Code
Quality of documentation
Security compliance
Monitor and improve system and application performance

6. OHIM new way of managing projects – Quality improvements
T H A N K Y O U