Transcript OHIM new way of managing projects – Quality improvements

27/06/07
IT Development
OHIM new way of managing
projects – Quality improvements
Eamonn Kelly
OHIM new way of managing projects –
Quality improvements
IT Development
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.
OHIM new way of managing projects –
Quality improvements
IT Development
OHIM adapts V Model incorporating 6 Quality Gates
QMD
IT DEVELOPMENT
EXTERNAL DEVELOPERS
EXTERNAL DEVELOPERS
IT DEVELOPMENT
QMD/KEY USERS
Regression Tests
BUSINESS CASE
COMPLETED
NO
YES
6
5
Release Testing
YES
REQUIREMENTS
4
COMPLETED
NO
OHIM User
Acceptance Testing
2
3
YES
SYSTEM REQUIREMENTS
COMPLETED
NO
System (Unit & Integration) Testing
YES
SYSTEM DESIGN
COMPLETED
NO
Interface Testing
1
COMPONENT DESIGN
YES
NO
COMPLETED
Component Testing
OHIM new way of managing projects –
Quality improvements
IT Development
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
OHIM new way of managing projects –
Quality improvements
IT Development
• 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
OHIM new way of managing projects –
Quality improvements
IT Development
THANK YOU