OHIM new way of managing projects – Quality improvements

Slides:



Advertisements
Similar presentations
Building a Knowledge Management System as a Life Cycle
Advertisements

Configuration Management
Software Quality Assurance Plan
A centre of expertise in digital information managementwww.ukoln.ac.uk UKOLN is supported by: UKOLN Workshop For NEMLAC: QA For Web Sites Brian Kelly UKOLN.
A centre of expertise in digital information managementwww.ukoln.ac.uk UKOLN is supported by: UKOLN/TechDis Workshop For RSC South East: QA For Web Sites.
IT Web Application Audit Principles Presented by: James Ritchie, CISA, CISSP….
Justin Walsh FOCI Program Manager Industrial Security Field Operations.
Chapter © 2009 Pearson Education, Inc. Publishing as Prentice Hall.
Chapter © 2009 Pearson Education, Inc. Publishing as Prentice Hall.
Improving IT Governance Through Formal Change Management
Software life cycle processes Purpose n A new international standard (ISO/IEC 12207:1995(E) that –establishes a common framework for software life cycle.
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne, office K115A. –
Software Engineering For Beginners. General Information Lecturer, Patricia O’Byrne. – Times: –See noticeboard outside.
COBIT Framework Introduction. Problems with IT? – Increasing pressure to leverage technology in business strategies – Growing complexity of IT environments.
Project Initiation Meeting Presented By: > > Office of the Chief Information Officer >
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 7 Quality Management Achieving technical performance.
Quality Management System for Educational Institute Application and benefit of ISO 9001:2008, an international quality management system, for educational.
A NASSCOM ® Initiative Security and Quality Kamlesh Bajaj CEO, DSCI May 23, 2009 NASSCOM Quality Summit Hyderabad 1.
Software Engineering Reuse.
PGD-1303 Software Project Management?. What is software? Software  Computer programs and associated documentation Documentation includes  requirements.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Software Project Management Introduction to Project Management.
Cybersecurity: Engineering a Secure Information Technology Organization, 1st Edition Chapter 7 Software Supporting Processes and Software Reuse.
Association for Biblical Higher Education February 13, 2013 Lori Jo Stanfield Evaluator Team Training for Business Officers.
Vijay V Vijayakumar.  SOX Act  Difference between IT Management and IT Governance  Internal Controls  Frameworks for Implementing SOX  COSO - Committee.
Overview:  Different controls in an organization  Relationship between IT controls & financial controls  The Mega Process Leads  Application of COBIT.
Roles and Responsibilities
Performance Measurement 201: Best practices in performance measure design & implementation Ia Moua, Deputy Director, Grants & Program Development Patrick.
Service Transition & Planning Service Validation & Testing
CONNECT Roadmap Draft version as of February 4 th,
Important informations
Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.
Effective Alarms Management: Towards a Rail Industry Specific Development Project Process Suzanne Heape Siemens RA 16 September 2015.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
EPA Geospatial Segment United States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Segment Architecture.
Version 3.3 ITIL – IT Service Management An overview program for IT Service Management good practices.
What is the role of Intl. Organisations in addressing data management requirements? The Colour of Ocean Data - The Palais des Congrès, Brussels, Belgium,
Project management Topic 8 Quality Review. Overview of processes Prepare for Quality Review Questions list Meeting Agenda Review Meeting Sign-off Product.
Assessment Design and its relationship to NARS and ILOs Arthur Brown Advisor to the Quality Assurance and Accreditation Project Republic of Egypt.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
<< DTC >> << Project Name >>
Introduction to Codes, Standards, and Regulations Chattanooga State CC.
Dr. Salwa El-Magoli Chairperson of the National Quality Assurance and Accreditation Committee. Former Dean of the Faculty of Agricultural, Cairo university.
Information System Analysis Implementation & Security.
Introducing Novell ® Identity Manager 4 Insert Presenter's Name (16pt) Insert Presenter's Title (14pt) Insert Company/ (14pt)
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
MEA Document Overview Slides 26 February About these slides This slide pack is designed to provide market participants with an introduction to.
Indicator 5.4 Create and implement a documented continuous improvement process that describes the gathering, analysis, and use of student achievement.
Oversight “The NPPO of the exporting country has the responsibility for ensuring that systems for exports meet the requirements …”
Software Engineering Process - II 7.1 Unit 7: Quality Management Software Engineering Process - II.
USDA 2016 Financial Management Training Transforming Shared Services Change Management Presented by Ron Gros.
John Gatimu University of Nairobi/University of Washington Research Laboratory What Is Not Mentioned In User Manuals: A Case Study of Quality Control in.
MANAGEMENT INFORMATION SYSTEM
Forrester and Novell Novell ® Identity Manager 4 Webcast I Insert Presenter's Name (16pt) Insert Presenter's Title (14pt) Insert Company/ (14pt)
On completion of the scenario, students will be able to: Learning Outcomes 1 Critically analyse and prioritise information security risks. 2 Systematically.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Configuration Management
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Configuration Management
Quality control & assurance.
Quality Management Perfectqaservices.
Software Requirements
Making Information Security Manageable with GRC
Guidance notes for Project Manager
SAP Value Assurance plan and safeguard service package for SAP S/4HANA Cloud Business Needs Need to follow leading practices and reduce risk of project.
SAP Value Assurance for SAP S/4HANA Implementation support for DVM Apps You want to be able to monitor your entire SAP landscape to understand the Data.
Assessment of Quality in Statistics GLOBAL ASSESSMENTS, PEER REVIEWS AND SECTOR REVIEWS IN THE ENLARGEMENT AND ENP COUNTRIES Mirela Kadic, Project Manager.
Engineering Processes
Recent Developments in National Training Programme
Improving assessment moderation processes at my RTO
Presentation 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 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.

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.

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.

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

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