EQMS TECHNOLOGY & TOOLS OF THE FUTURE PRESENTED BY: OLIVIER KLOSS, PRINCIPAL APPLICATION DEVELOPER & KEVIN BYRNE- LANGLOIS, SOLUTIONS ARCHITECT

EQMS TECHNOLOGY & TOOLS OF THE FUTURE PRESENTED BY:

OLIVIER KLOSS, PRINCIPAL APPLICATION DEVELOPER &

KEVIN BYRNE- LANGLOIS, SOLUTIONS ARCHITECT

SOLABS QM USER GROUP MEETING

INTRODUCTION

Hello!

My name is Olivier Kloss and I’m the Principal Application Developer at SOLABS,

I’ve been at SOLABS for a while now,

…& I’m known to my colleagues—& to some of you—as ‘the software guy’.

AGENDA

1. Tools of the future 2. Choices

3. Database structure & benefits 4. Why SharePoint?

5. Goals

6. Automated Deployments

7. Shifts in the IT and Pharma Industries 8. Approaches

9. Pre-configured deployment via cloud 10. Questions

EQMS Technology

:

Tools of the Future

• Microservices

• Package Managers

• In-Memory Databases and NoSQL • Making Choices

Applications

can be thought of as

MICROSERVICES

Monoliths and Microservices

BEFO

WE WERE EARLY ADOPTERS

SOLABS QM has been web-ready, right from the start.

• Java • JBoss

• J2EE / JEE

A FEW BENEFITS

• Available Scalability

• Better Fault Tolerance • Easier Upgrades

PACKAGE MANAGERS

• Ensure dependency between packages and

their versions are maintained.

• Ensure the right version all the time. • Applying the patterns of package

IN-MEMORY DATABASES AND NoSQL

• Very active space

• Hype dying down, to the great benefit of

the relational model

• Staying with SQL Server

MODELING OF PROCESS DATA

• Following the relational model • Easier reporting

TO SUM IT UP…

We have seen an explosion of services, from which are emerging common protocols &

QUESTIONS

&

CONSIDERATIONS

• How do we choose?

• What did we choose in the past?

HOW DO WE CHOOSE

?

• Popularity • Licensing

• Track record/maturity • Java

WHAT DID WE CHOOSE

?

• Solr

• Jboss

• SQL Server • jQuery

WHAT WILL WE CHOOSE

?

We don’t currently know.

We’re looking much more closely at:

• Okta

• One Drive • SAML

WE ARE CURRENTLY TESTING

We’re in the process of testing…

Increased popularity means more possible choices on which to do

tests:

• Using Selenium to automate integration tests • Looking at integrating it in installs & updates • Web services for load testing like Blaze Meter

WEB INTEGRATION TESTING WITH SELENIUM

• Tried in 2007/2008

• SOLABS QM too complex from a web

integration testing perspective

• Was difficult; now (almost) easy

• Looking at integrating it in installs & updates • Web services for load testing like Blaze Meter

INTRODUCTION

Hi! I’m Kevin, SOLABS’ Solution Architect.

I’ve been in the industry for almost 20 years now, and at SOLABS for about 5.

I’ve worked pretty extensively throughout the IT industry:

as technical support, network administrator, security specialist, Systems Integrator and as a Solutions Architect

.

DATABASE STRUCTURE

&

BENEFITS

WHY SHAREPOINT

?

• Centralized portal • Data visualization

• Easy to navigate & access objects • Business intelligence capabilities

• Manageable access rights • Create your own

GOALS

• Deploy safer & faster

• Exercise complete control over the process • Release fixes quicker

• Maintain complete transparency on changes made • Ultimately: give more control to the user

AUTOMATED DEPLOYMENTS

• Standardization • Less error-prone

• More easily repeatable

• Lowers IT skill required to deploy • Releases are easier & faster

• Save time

• Transparency on changes • Change history

SHIFT IN THE INDUSTRY: IT

• Moore’s Law, as stated in its current definition, appears to have

come to an end

• New computer hardware pace and speed are slowing down • Innovation is slowing down

• Trend: take an existing product, but make it better and cheaper • The industry seems finally ready to look at the content, and not

SHIFT IN THE INDUSTRY: PHARMA

• A new openness to cloud solutions

• An evolving openness to ‘outsource’ their software management • The need to minimize some of their software qualification &

validation burden

• The requirement to stay in control and compliant at all times

APPROACHES

• Continuous integration

• Continuous deployment • Automated deployment • DevOps

• Source Control: Mercurial • Database Source Control

ULTIMATE GOAL

• Complete Control over the process • Transparency

• Full Reporting capability: • Ticket information

• Code changes

• Test and Performance test results • Deployment steps, results & logs • Changes on your server

QUESTIONS

&

THANK YOU

!

•

Questions?