How to design, code and TEST the software and (still) remain GDPR compliant
GDPR came to life over six months ago. It had a significant impact on the data privacy laws. To which extent has it impacted our SDLCs? Let’s discuss some easy-to-follow steps to embed GDPR requirements into SDLC. By following these, you will ensure that GDPR requirements are correctly identified, planned, designed and TESTED in our software projects.
During this session following aspects will be discussed:
- How to identify applicable GDPR requirements?
- How to build in the rights of the data subject into the software solution?
- How to ensure the right to erasure (‘right to be forgotten’)?
- How to design, code and TEST the software and remain GDPR compliant through the whole SDLC?
GDPR requirements are quite hard to interpret. The law departments are not very helpful, as they are not speaking the IT language, nor they understand the IT side of the GDPR. As the result GDPR requirements are often misunderstood.
The “GDPR compliance” is often part of the requirements for the built solution. But what does it mean in practice?
IT often does not understand what GDPR really ask for. As a result, GDPR is often misinterpreted, leading to not-necessary work or confusing request form the business.
Unternehmen: Philip Morris International
Zielgruppe: Project Managers, SQA teams managers, requirement engineers