Delivering solutions, shaping the future. Prozessorientiertes Testmanagement bei Aptargroup. Benjamin Jahnes

Transcription

1 Delivering solutions, shaping the future Prozessorientiertes Testmanagement bei Aptargroup Benjamin Jahnes

2 Agenda 1 Who is Aptar 2 BPM at Aptar 3 Requirements for testing in validated environments 4 Actual situation 5 Outlook 2

3 Who is Aptar 3

4 Our Background Leader in the dispensing solutions niche of the packaging industry Providing brand differentiation and consumer convenience Consistent long-term focus, stability, and financial results 4

5 Who is Aptar Beauty Gift & Promotion Food Beverage Consumer Health Care Prescription Home Care Injectables Personal Care 5

6 What are our products 6

7 What are our products 7

8 Where we are 8

9 History of Aptar 9

10 BPM at Aptar 10

11 BPM history at Aptar 7 Brands Cooperation Standard Terranova AURORA (ISOG) Aptar 1 Pharma Segments EMSAR Pfeiffer SPD Brand Brand Brand Brand Common products and markets Brand Brand Brand B & H F & B BPM BPO EPM Different Processes Interface Processes Same Processes Organizational Change Process management

12 Process Roles IS Segments Alignment BPAM BPO KUC Analyst KU BPO: Business Process Owner BPAM: Business Process Alignment Manager KUC: Key User Coordinator KU: Key User 12

13 Process Usage Documentation Optimization Measurement Simulation Testing 13

14 Requirements for testing in validated environments 14

15 Type of testing Functional Testing after customizing / developments in the Realization Phase Integration Testing at the beginning of the Implementation Phase Regression Testing before transport to production Performance/stress testing 15

16 Validation requirements Requirement all requirements of a release Deployment User Requirement Specification (URS) Functional Specification (FS) Development Specification (DS) test against test against test against Regression Test Integration Test (PQ*) Functional Test (OQ*) Unit Test during development Development *OQ and PQ means with validation of the test result, but same test as without validation 16

17 OQ Framework - Validation OQ Plan (done by Validation) OQ Report (done by Validation) OQ Test OQ Scripts Test Form OQ Test Form Validation approval needed before execution of scripts OQ Test executed OQ Test Evidence OQ Test Defects 17

18 QC.03 PN.13 SAP ECC MD Packi ng Instructi on MD Sales Conditi on SAM Customer Service R Representati ve Customer Master Credi t i s n... Create Line Item Sales Order Information R TN Standard Sales Order with... SAP ECC determine reference document SAP ECC VMI Customer Processi ng Standard VMI sales order has t... SAM Customer Servi ce Representati ve TN Create Sales Order (1) E-VA SOM Web Order Entry SAP ECC SAP ECC Is customer blocked for sales orders Create Sales Order (2) R TN TN EVA SOM Cal Off Or Standard... TN SAM Customer Servi ce Representati ve SAP ECC Standard Sales Order without... Determine Sales Area Information Sales Area Information Determined Enter Sales Area Data Sales Area Data Entered Enter Header Sales Order Information Sales Order i nformation entered E-VA SOM Forecast Applicati... R TN R TN R TN MD Customer Material Info Record Block Not Removed Inform the customer Customer is i nformed SAM Customer Servi ce Representati ve SAM Customer Service Representative MD Customer Hi erarchy SAM Customer Service Representative R R TN Customer Master Credit i... Inform Fi nance and ask for... Customer Credit Limit has been... Customer Down Payment FI Credit Manager R SAM Customer Service Representative TN SAM Customer Servi ce Representati ve Fi nance informed Credit Scoring Credit management view of the... Overview Business Processes Template project Template project Roll In project Roll In project Roll In project Roll In project URS FS RACI Functional Tests Roll In project Business Test Requirement Roll In project Integration Tests E2E Scenarios E2E Scenario Project Integration Test Project ARIS Test Designer 18

19 Integration Tests with ARIS E2E scenarios are useful for testing but also to understand how the crossorganizational business processes are enabled by multiple systems APTAR Enterprise Library Process Landscape Management Suppliers Strategic Operational Planning Business Core Business Strategy Business Intelligence Business Process Management Customers Product Life Cycle Management Sales Customer Service Supply Chain Management Business Support Finance Controlling Human Capital Management Asset Life Cycle Managment E2E e.g. Purchase To Pay (PTP) Contract To Cash (CTC) Asset Life Cycle Mgt (ALM) Quality Management Master Data Management Information System Management 19

20 Example of a Scenario 20

21 Actual situation 21

22 Change definition Change The addition, modification or removal of anything that could have an effect on IT Services or processes Standard Change Normal Change Emergency Change A Standard Change is a routine change to a service or infrastructure change for which the approach is pre-authorized by Change Management Standard Changes enables rapid implementation of frequent changes while managing the risk Normal Change is a Nonstandard and Non-emergency Change that follows the full life cycle of Change Management Normal Changes are often nontrivial changes to services, processes, and infrastructure An Emergency Change is the highest priority change that needs to be evaluated, assessed, and either approved or rejected within a short span of time 22

23 Test process and release process Requirements to Deploy Demand Design Development Test Deploy Project / RfC URS / FS / DS Unit test Functional test Integration test Validation Approval Regression test Monthly deployment Different starting conditions Bugfix Problem description Unit test Functional test Validation Approval* No Regression test Twice a week deployment Emergency Problem description Unit test Doesn t make sense Doesn t make sense No Regression test Immediate deployment Release timing Month 1 Month 2 2nd week Approval of changes 3thrd week Start of development 1st week Start of user acceptance tests 3thrd week Release deployment DS: Development Specification FS: Fucntional Specification RfC: Request for Change URS: User Requirement Specification *only on impacted domain only on OQ test (Functional Test) Test process cycle must be strongly aligned to the release cycle. 23

24 Test process and release process Requirements to Deploy Demand Design Development Test Deploy Project / RfC URS / FS / DS Unit test Functional test Integration test Validation Approval Regression test Monthly deployment Different starting conditions Bugfix Problem description Unit test Functional test Validation Approval* No Regression test Twice a week deployment Emergency Problem description Unit test Doesn t make sense Doesn t make sense No Regression test Immediate deployment Release timing Month 1 Month 2 2nd week Approval of changes 3thrd week Start of development 1st week Start of user acceptance tests 3thrd week Release deployment DS: Development Specification FS: Fucntional Specification RfC: Request for Change URS: User Requirement Specification *only on impacted domain only on OQ test (Functional Test) Test process cycle must be strongly aligned to the release cycle. 24

25 SAP Testing environment Sync Sync 25

26 MES Testing environment (*) 1) Test Scripts developed by using Excel files (XLS) by FDM, KU 2) XLS upload in ALM performed by IS TM (*) Same approach applied to all business processes NOT in ARIS 26

27 Outlook 27

28 New test scenario process Fully transparency through the requirement to deploy scenario Requirements to Deploy Demand Design Development Test Deploy 28

29 Outlook to the future Requirement Test Template Process oriented + Test documentation Deploy Process Process Process ARIS SolMan HP ALM Additional Process Information Additional Transaction Information & Document templates Test Documentation Create ticket and RfC Create Requirements (object) Map to Transaction Map to Process Synchronize Test Models from ARIS Create Project and synchronize and filter Test Models from SolMan Transport to production Store in DMS Store in HP ALM URS FS Test Documentation Demand Design Development Test Deploy 29

30 Advantages Support of all kind of testings Alignment to the strong timeline of releases Higher automatization due to higher volumes of tests in future Standardized test stucture Enables an end-to-end validation from requirement to deployment (requirement by validation) Ensures proper creation of test documentation and alignment to test cases Uses much better existing systems End-to-End traceability between RfC/Bugfix/Emergency and deployment of result Less effort due to re-usability ot test cases and structure 30

31 Q & A 31

32 Test process and release process Requirements to Deploy Demand Design Development Test Deploy Project / RfC URS / FS / DS Unit test Functional test Integration test Validation Approval Regression test Monthly deployment Different starting conditions Bugfix Problem description Unit test Functional test Validation Approval* No Regression test Twice a week deployment Emergency Problem description Unit test Doesn t make sense Doesn t make sense No Regression test Immediate deployment Trainings on tool Project / RfC Create test structure Support test creating Import tests in tool Reporting* Activities Test Team Bugfix Emergency Existing test object / structure will be used Extend existing test object No activities Reviewing test scrips, test results and test documentation Release timing Month 1 Month 2 2nd week Approval of changes 3thrd week Start of development 1st week Start of user acceptance tests 3thrd week Release deployment 32

33 Test Management services Support Projects and Changes Create test structure Support test creating Import tests in the tool Support in creating automated test scipts Reviewing test scrips, test results and test documentation General Test Management Services Providing Trainings Providing Reports Providing Framework, Information and Documentation Tool Support and Administration 33